yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Bigjim1488:
Not sure on a release date and I would also bet money that Verizon will probably get it first since don't have the gsII
[Samsung Epic 4G Touch] Alex1x:
Agreed. So... To keep or not to keep?
[Samsung Epic 4G Touch] Bigjim1488:
I'd keep it. Worse case you can sell it on eBay or Craigslist and pick up the prime when it comes out.
[Samsung Epic 4G Touch] Bigjim1488:
But I would go and exchange yours because the screen shouldn't be giving you touch response issues.
[Samsung Epic 4G Touch] AvatarOfFrost:
Nobody knows if the Nexus Prime will even come to Sprint. This phone is king right now so I don't know what your problem is. Splitting hairs a little too much maybe? Nothig will ever be perfect for some people. No offense. 3 months after the Prime comes out something else will be better then people will complain about that.

But if you're that unhappy stick to your E3D and return this one.
[Samsung Epic 4G Touch] Alex1x:
Sprint No NFC

ATT & Tmobile Yes NFC

Verizon nexus prime Yes NFC

NFC will rule by end of the year
[Samsung Epic 4G Touch] fetalp:
NFC really? Not that big a deal right now very and I mean very few places even use it yet. Future proof sure but for the next year you'd be fine NFC lol. It will be great when it gets more mainstream. As for screen I haven't seen any screen lag either. Keyboard try another keyboard. USB plug works on PC and MAC just fine, got drivers? :rolleyes:
[Samsung Epic 4G Touch] r3a1ist:
pretty sure the prime isn't going to have the Exynos processor. I think the prime is going to basically be the samsung hercules for sprint with the 1.5 ghz qualcomm processor. An inferior processor. I'll see you when I'm running kernels and roms months from now trying to break the 5500 mark barrier and beyond on quadrant overclocked. This thing is raw power in the nicest package you can get it in. U want NFC go at&t and lose the screen. Sounds like you don't like the extra real estate anyways. The prime is gonna be the same screen.
[Samsung Epic 4G Touch] jayv1717:
Rumors say 1.5 ghz ti omap 4460.. So we don't know how good the processor will be.. And from what I read that processor was delayed until early 2012 so wit the tell knows what the prime will have now
[Samsung Epic 4G Touch] r3a1ist:
There are only 150,000 locations across the entire continental United States that currently accept NFC. You do know that we don't even have the resources to install the NFC receivers even if there was demand within years yet alone a year right? NFC if it became very popular and essential for business's due to demands would take years to become widespread. At least 3 years at the very earliest. Well outside of everyone's plan agreements. I even expect a very slow start due to peoples comfort with credit card transactions and initial worry about possible security liabilities amongst the general public.
[Samsung Epic 4G Touch] maramos:
You need to enable USB Debugging if you want to be able to view the phone to show up as a USB Drive. I'm not sure about the keyboard lag and the screen has been plenty responsive for me though it's not the most responsive screen ever which isn't necessarily a bad thing.
[Samsung Epic 4G Touch] r3a1ist:
From what I gather the Exynos set up with it's GPU won't be matched by the 4460. The Exynos will out process the 4460 across the board. Also I read that samsung is forced to use the 4460 because it supports 42 + HSPA for t-mobile and the like. It's a weaker processor set up that supports a special kind of wireless connectivity is why samsung is forced to use it. If I'm not mistaken it will be in the t-mobile variant of the GS II so we'll have benchmarks within a matter of weeks. Now mind you, t-mobile was the only carrier not to allow access to their phone at the samsung press event. I would gather it's because their phone benchmarks lower than the sprint and att versions.
[Samsung Epic 4G Touch] Dulanic:
I want NFC myself, but you're kidding youself if you think NFC will become even popular within the next 2-3 years. I give it 5 years before it becomes kind of mainstream. Even paypass isn't full deployed yet and it has been around for more than 10 years.
[Samsung Epic 4G Touch] GadgetMonger:
The list of things this device doesnt have keeps getting longer. I could deal with the old tech resolution, no NFC... Yeah that sucks, but whatever. It's still pretty early in that game anyhow. But the thing that bugs me most is that it's looking more and more like no Rev B when Sprint upgrades its 3G network. Would have at least let the wife keep mine, but not now. Sending it back. If it turns out later the device supports Rev B and the Prime doesnt come or isn't what it's hyped up to be, I might consider picking up another GSII.
[Samsung Epic 4G Touch] netchip:
I hope we can so pull stock firmware off samsung servers ...

Sent from my GT-I9100
[Samsung Epic 4G Touch] jerdog:
This key does not exist in my registry - I believe they've changed some things:

Here's what does exist:

[HKEY_CURRENT_USER\Software\Samsung\Kies\Connect\]

[HKEY_CURRENT_USER\Software\Samsung\Kies\Connect\WiFi]

[HKEY_CURRENT_USER\Software\Samsung\Kies2.0\CRM_INSTALLER\]

[HKEY_CURRENT_USER\Software\Samsung\Kies2.0\FUS\]

[HKEY_CURRENT_USER\Software\Samsung\Kies2.0\Setting\]

[HKEY_CURRENT_USER\Software\Samsung\Kies2.0\Setting\SETTING_GENERAL]

Are you wanting to keep track of Hardware Version?

Home > Settings > About Phone > Hardware version

Mine is D710.10
[Samsung Epic 4G Touch] pyrostic:
I also believe that they removed the ability to reinstall drivers using kies.

Posted from a Galaxy II far far away.
[Samsung Epic 4G Touch] zedomax:
seriously? I didn't know that, good to know.
[Galaxy Tab 10.1 Accessories] irishtexmex:
Is this possible? I'm not sure if the textured back of the metallic gray would allow this, but I'd like to know for sure.

As an alternative, would any decals for an iPad work? Or would the textured back also prevent a good adhesion?
[Galaxy Tab 10.1 Accessories] Tivo7:
If you're just looking to add some customization or pizazz to it, try http://skinit.com
[Galaxy Tab 10.1 Accessories] pokey9000:
Laser marking plastics really depends on the type of plastic. I think that plastics molded to look rough will probably etch to a much lighter shade. This is done a lot on high-end keyboards, where a laser etcher is used to mark the letters on rough keycaps. You'd need to experiment to know how it will turn out. Go ahead and get it done, and if you don't like it put a sticker on top.
[Galaxy Tab 10.1 Accessories] Step666:
There's a guy on here who smashed his Tab, maybe you could buy it cheap to experiment on...
[Off-topic] eejayyeahuuh:
Tonight I awoke at 247 am ?? For no obvious reason at all. The feeling of excitement is what has awaken me and I do not understand completely what is going on. Maybe I am having a anxiety or panic attack? I do not understand why I am so excited?
[Off-topic] Dirk:
Somebody put Rohypnol in your drink. Are you handcuffed to your bedposts by any chance?
[Off-topic] sakai4eva:
Reverse succubus. I had that once. Friends say it's something I ate and digested while sleeping that triggered the brain to wake. Enjoy it for the 6 hours, then suffer the inevitable crash.
[Off-topic] m0jo:
Ghosts. Obviously Ghosts..
[Off-topic] Archer:
If it was a panic attack then you certainly wouldn't describe it as being excited, believe me! Maybe you just had a sexy dream and just don't remember it ;)
[Off-topic] LordManhattan:
Oh my, Code got to second base! High five!
[Off-topic] cobraboy85:
it was le sexy dream, how muuuch
[Galaxy S II General] yuyo555:
LG U+ write prl and something in nam3,who knows some software which can change data in nam3?

or,who knows the "master subsidy lock" of M250l"?
[Galaxy S II General] duansindo:
please see this http://www.diypda.com/viewthread.php?tid=368394

if do not know chinese.contack me with gmail duansindo@gmail.com
[HTC 7 Pro] xboxmod:
XBmod ROM 7720 V 1.01 for HTC 7 Pro,Gold.

The principe:

With XBmod Rom you can send cutom cab packages to device.

The packages modify the rom itself so they stay in place even after a reset and can update any part of the rom (SLDR,NK,LOGO...) and update the build without reflashing the Device.

we believe that this process is the simplest way:

-for users to customize the rom as they likes & avoid constant reflash for update.

-for developer to try differents tweaks

-for cookers to send their own corrective packages,without need to recook and reflash!

-for any developpers and designers to make custom packages for WP7 community.

-----------Requirements: -----------

1• DFT HSPL/RSPL

INFO:

OS only rom no spl,radio,ect......

ROM Languages:

English, German, French , Italian, Spanish (look cab thread for more)

Keyboard Languages:

English US, English UK, German, French, Italian, Spanish (look cab thread)

OEM version:

2250.21.40600.4..

Windows Phone version:

7.10.7720.68 -Updatable

----

Features

----

- Ability to Install Custom Cab

- Ability to Install Developers Update Cab.

- Updatable via zune (for future build wait confirmation before apply)

- Root, chevron and unlock features already in and reaplied after an update(more info soon)

- backup & restore enabled

- Some Oem Apps from HTC Omega.

ROM DOWNLOAD LINK:

http://www.multiupload.com/Z08CJVIBNP

Hard Reset after flash.

-Then Go to the cab customisation & tweak thread to install your operator cab,bootlogo,apps,tweak & more.....

if you have xap deploy problem

apply unlockremove.cab

then apply unlock.cab

Soon For Mozart.....
[HTC 7 Pro] Budniu:
Nice and good job (but not for me I like my language - Polish).

Anyway:

For Gold ??? That is forum about HTC 7 Pro aka Gold so what ROM is in first post ?
[HTC 7 Pro] Vulcayne:
Wooow, have you bought a HTC 7 Pro on cdiscount? ahah!

Good job, I'm surprise to see you here with your rom, so thank you! ^^:rolleyes:
[HTC 7 Pro] shooter3406:
this is the rom for HTC 7 Gold and it works perfect. Thank you very much!

xbmod can you please make a cab for updating this rom with internet share

currently not working because following error:

================================================
START OF UPDATEVALIDATOR ERROR MESSAGES
================================================

ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\FC901A82-2F5C-4EC8-8FF1-D14FFAA90D1B.1.pks\new.cab.pkg	FROM Version: 0.0.0.0	TO Version: 2250.21.51003.445	GUID = {A2A5F44F-FE02-496E-8926-6EDDC8CF9B44}

ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_OS_WIRELESS cannot find a path to highest expected version of: 2250.21.51003.445
ERROR: UpdateOrderFromFileList: MAIN OS Update: MAIN OS Update Failed with HRESULT : 0x80180048

=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================

UpdateOrderFromFileList failed with code 0x80180048
BAD PACKAGE:	new.cab.pkg	ERROR CODE: 0x80180008	Total number of Bad Packages: 1

Process Failed with code 0x80180048
UpdateValidator finished at 08:00:41 01/06/1980
[HTC 7 Pro] xboxmod:
Hi

install official gold oem. http://xboxmod.sylvester20007.com/temp/gold_2250.21.51003.401_oemupdate_release.cab.pks_CD210FFC808B338B7B18A5A4C5F303A2FEBA71F6.cab uploading....46.9Mo
[HTC 7 Pro] Vulcayne:
thank you! ^^

---------- Post added at 09:06 AM ---------- Previous post was at 08:33 AM ----------

Don't work... :(

First try :

Second try :

Third try :

and last try :

Sorry but on HD2, no problem to update with cab or zune, but on 7Pro... not work well! :confused:
[HTC 7 Pro] shooter3406:
Hi, just used the 40mb cab, and received same error.

Update Path for Base Package HTC_8x50_OS_WIRELESS:
Name: HTC_8x50_OS_WIRELESS Version: 2250.21.30201.401
Name: new.cab.pkg Version: 2250.21.51003.445

ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\2F4A822A-D635-47CB-8CFA-01424BF96F90.1.pks\new.cab.pkg	FROM Version: 0.0.0.0	TO Version: 2250.21.51003.445	GUID = {A2A5F44F-FE02-496E-8926-6EDDC8CF9B44}

VerifySignatures failed for graph with base name of HTC_8x50_OS_WIRELESS. Trying to find another path.
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_OS_WIRELESS cannot find a path to highest expected version of: 2250.21.51003.445
BuildReturnValues: Returning HRESULT 0x80180048
ERROR: UpdateOrderFromFileList: MAIN OS Update: MAIN OS Update Failed with HRESULT : 0x80180048

=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================

UpdateOrderFromFileList failed with code 0x80180048
BAD PACKAGE:	new.cab.pkg	ERROR CODE: 0x80180008	GUID = {A2A5F44F-FE02-496E-8926-6EDDC8CF9B44}

ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\2F4A822A-D635-47CB-8CFA-01424BF96F90.1.pks\new.cab.pkg	FROM Version: 0.0.0.0	TO Version: 2250.21.51003.445	GUID = {A2A5F44F-FE02-496E-8926-6EDDC8CF9B44}

ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: HTC_8x50_OS_WIRELESS cannot find a path to highest expected version of: 2250.21.51003.445
ERROR: UpdateOrderFromFileList: MAIN OS Update: MAIN OS Update Failed with HRESULT : 0x80180048

=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================

UpdateOrderFromFileList failed with code 0x80180048
BAD PACKAGE:	new.cab.pkg	ERROR CODE: 0x80180008	Total number of Bad Packages: 1

VerifyTempDirectory:: The temp directory already exists, GetFileAttributes = 16
1980-01-06T08:00:40Z:: The value of szErrLogFilePath = \OsRoot\UpdateErrors.log
1980-01-06T08:00:40Z:: SUCCESS: Updatevalidator: LogMajorErrors : Sucessfully Wrote to UpdateErrors.log file

As i can see my phone doesnt delete the update packages, if it fails to update.

Is that right?

Should i reflash my phone and then try to update it with the official update? (I'm pretty sure I've tried that)
[HTC 7 Pro] killerb255:
If this ROM supports Internet Connection Sharing (USB or WiFi--I don't care which), then it's definitely worth a try!
[HTC 7 Pro] Kr3i0s:
Is it possible to re-upload the links of the rom as they are down and I am not able to download the rom file. Thanks.
[HTC 7 Pro] DAC324:
Updates?

Hello all,

as there were several updates in the meantime available via Zune, I am wondering if you consider to make them available for the XBOXMOD ROM users, too.

Unfortunately, updates via Zune do not work for the XBOXMOD ROM (which is already a known problem - the dreaded "certificate chain" error).

Or is it now time to drop the XBOXMOD ROM and go for another, updateable one?

Thank you very much for any helpful hints in advance and kind regards,

DAC324
[G2 and Desire Z Android Development] Koush:
I've been hearing that there are issues with flashing Clockworkmod recovery to 5.x recently. Jeagoss (teamdouche member) and I tried to troubleshoot this today, and we may have a solution, and what we have learned.

First, we found that booting into recovery while USB is connected works every time.

Here is what he did to fix it randomly:

Flash 5.0.2.6 (via the alternate recoveries button).

Flash 5.0.2.0

5.0.2.0 should not boot fine every time.

Here is the fix I put into ROM Manager that sort of does the above.

1. First make sure you are on wifi.

2. Make sure you are on the latest ROM Manager.

3. Flash 5.0.2.0. The new flashing process will write zeroes your current recovery before flashing the new one.

This *should* fix it. Please let me know your results.

Koush

Messaging me on twitter or on Google+ is by far the easiest way to get a hold of me. I am quite active on those, but not so active on forums.

Twitter

@koush

Google+

https://plus.google.com/103583939320326217147/posts
[G2 and Desire Z Android Development] tun4f1sh:
Testing your workaround method now.

I can say with absolute certainty that it *DOES* lockup when connected to USB (albeit rare). Just a simple 'reboot recovery' via ADB gets me into recovery when that happens.

It happens far more often when not plugged in.

Thanks for everything you do for this community.

edit: Just tested your workaround.

- Connected to wifi

- USB/charger disconnected

- ROM Manager 4.5.0.1

- Flashed 5.0.2.0 (via RM)

So far I'm 3 for 3 getting into recovery without getting stuck at the bootsplash.

edit2: Booted into recovery from RM 5 times now, never stuck. Either I'm getting lucky or you fixed that ****. :)

edit3: Well, I'm sad to report that on the 7th reboot into recovery, I got stuck again. Anything I provide to help troubleshoot?
[G2 and Desire Z Android Development] Koush:
Do you remember if the 3.0.2.4 version had charge mode support? If not, that may be what is causing the problem.
[G2 and Desire Z Android Development] tun4f1sh:
I'm pretty sure 3.0.2.4 had charge mode support (assuming that means the ability to charge the phone when it's off?)
[G2 and Desire Z Android Development] Nipqer:
Don't really have time to test now, but flashed the 5.0.2.6 recovery yesterday via fastboot (fastboot erase recovery, fastboot flash recovery) and upon selecting recovery from the bootloader menu it would not get to it.

Tried 3 or 4 'adb reboot recovery' while it was hanging on the splash screen before giving up and reflashing 3.0.2.4 (Which I'm pretty sure supports charging)

-Nipqer
[G2 and Desire Z Android Development] steviewevie:
Maybe I'm misunderstanding, but did you mean "should *now* boot fine every time" ?

Also, yes, 3.0.2.4 charges fine with the phone switched off, that's what I am currently running.
[G2 and Desire Z Android Development] dixxa:
Ok,

Fed up with people crying:

" Recovery this, recovery that....."

download this http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vision.img

adb reboot bootloader

fastboot erase recovery

fastboot flash recovery recovery-clockwork-5.0.2.0-vision.img

And enjoy the magic ......
[G2 and Desire Z Android Development] OriginalGabriel:
If by "magic" you mean "sporadic HTC screen hang" then yes, it's magic.
[G2 and Desire Z Android Development] tun4f1sh:
I think dixxa is trying to say that erasing the recovery via fastboot before flashing the new version is the fix (as opposed to simply overwriting it with a new version, like ROM manager does)
[G2 and Desire Z Android Development] androidtoy09:
Man, people are mean to each other nowadays. Relax guys, it’s just a hick-up for now. I’m sure Koush and his team will solve it eventually.

If you can't stand the 5.x.x.x sporadic behavior, switch back to 3.0.2.4 or 4EXT Recovery(basically the same source code as Koush’s Recovery but reliable for now).

Go out and breath some fresh air. Look around you, there are other things to appreciate for.

And thank you, Koush for your work and commitment to the community.
[G2 and Desire Z Android Development] dixxa:
That's it!

never got that htc splash screen after wiping completely the recovery and reflashing it.
[G2 and Desire Z Android Development] robmarms:
Yeah... it seems less probable of freezing now but still freezes
[G2 and Desire Z Android Development] martonikaj:
You can select the option in ROM manager to erase recovery before flashing FYI.
[G2 and Desire Z Android Development] ChronoReverse:
Thanks for the attention, I've give this a go as soon as I have a moment.
[G2 and Desire Z Android Development] noneabove:
It's weird.. for entering recovery I actually only have a problem when I'm telling the phone to enter it while it's on (IE from reboot screen or from rom manager to do a backup/restore/flash a zip) but even when it freezes with ROM manager, I simply have to pull the battery, turn phone on with vol down, go into recovery, and it does whatever I had told it to do before... Don't know if that's the case with everyone or if I'm an odd exception, but yea.
[G2 and Desire Z Android Development] G1ForFun:
Been reported a lot at this point. Take a gander around the forums. Also its not always simple for everyone to pull the battery. If you have an Otterbox then it can be a pain.
[G2 and Desire Z Android Development] steviewevie:
I decided to try this out last night, having been on 3.x all this time.

I flashed 5.0.2.6 and then 5.0.2.0. The first time I rebooted into recovery it worked, the second time it hung on the splash screen, and I went back to 3.x.

Then I tried flashing straight to 5.0.2.0 from 3.x, and I booted (from power off, no USB connected) into recovery fine at least 10 times. So it looks good to me so far.
[G2 and Desire Z Android Development] robmarms:
Yeah... I with the old 5.0.2.0 I was getting a freeze about 1/5 reboots into recovery... with this one I get them almost exactly half of the time 1/12... still happens though... this never happens in 3.0.2.4. I'm not sure that I am content with these sorts of freezes even at fairly low frequency.
[G2 and Desire Z Android Development] LayZeeDK:
I upgraded from 3.x to 5.0.2.0 through ROM Manager and it worked perfectly :)
[G2 and Desire Z Android Development] John5788:
is 5.0.2.6 unstable or something? why are we flashing from 3.x to 5.0.2.6, then to 5.0.2.0? why not go from 3.x to 5.0.2.0 or stay at 5.0.2.6?
[G2 and Desire Z Android Development] tsubus:
use 3.x or 4ext if you don't want issues
[G2 and Desire Z Android Development] costipl:
Same here, no issues so far.
[G2 and Desire Z Android Development] steviewevie:
I am on 5.0.2.0 and I have no issues, successfully booting into recovery a dozen times or more. I believe that wiping recovery before installing has fixed the previous issue.
[G2 and Desire Z Android Development] dannejanne:
Yeah. Before upgrading to 5.x, uninstalling 3.x and then install 5.x has left me without any issues at all. There is an option in rom manager to uninstall old version before upgrading with new version.
[G2 and Desire Z Android Development] dhkr234:
I'm having a hard time understanding what you people are all going on about. A recovery image is just that... an image. It is a linear binary file that is directly written over a chunk of flash memory. Whether you downgrade or not, whether you manually erase it or not... no difference since the flash process will wipe and overwrite it with the new image, precisely identical no matter what weird voodoo process you apply before it.

I suggest that there appears to be an element of RANDOM CHANCE involved in whether it will fully/successfully boot or not. That being the case, you can't just boot the thing 10 times to see if it is better or not. You need to test by booting it ten thousand times in order to generate statistically relevant observations and then calculate the failure rate. I know that none of you are doing 10,000 tests before and after to measure the failure rate..... Sorry, but NOTHING any of you have done has resulted in a verifiable change in the success rate of booting these recovery images. There is some DEFECT in the recovery images that needs to be tracked down. Simple as that.
[G2 and Desire Z Android Development] John5788:
just want to report success flashing it over adb in OS mode.

adb push recovery-clockwork-5.0.2.0-vision.img /sdcard/
adb shell
cd /sdcard
erase_image recovery
flash_image recovery recovery-clockwork-5.0.2.0-vision.img
reboot recovery

rebooted into recovery and it has been working flawlessly.
[G2 and Desire Z Android Development] Tom in AZ:
Glad I found this thread.... Had my wife flashing 5.0.2.x while I was driving the car and it locked up on her, and she freaked out pretty good as she was rebooting with the vol- and thought that the phone was bricked. After pulling the battery 3 times we were able to load into the OS and used Rom Manager to roll back to 3.0.2.4. It has been perfect and stable since.

Thanks for all you do as devs!! I am sure that you will get it solved.

Tom