yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] cciehkc:
up！

I agree. I've been a full time Android user

hope the ROM for NAND，flash it
[Touch Pro, Fuze Android Development] volcan123:
Yup, thats what I am talking about. I wonder if the chefs for XDANDROID know about this? :)
[Touch Pro, Fuze Android Development] TheDeadCPU:
These threads are about how USERS can put an NAND build on their phone..

Okay I'm going to tell you guys this just once.

First the developers have to get everything finished so that we don't need the few bits from WinMo we still do.

Then they can make a NAND build.

And BELIEVE me, they know how to do it. It just won't work at the current state of things.

And the XDAndroid team knows just as much about porting as the Vogue guys. The only difference is that we got more advanced phones and therefor it takes a LOT more time to make a port.
[Touch Pro, Fuze Android Development] hamagc:
x2 right now the biggest thing is drivers. since there were never any drivers made for the touch pro/fuze for android, none exist.

since none exist, we must use winmo to initalize alot of the hardware that android uses.

once the drivers are sorted out (they are being worked on) and we don't need winmo to initalize everything for android, android can be moved to nand.
[EVO 4G General] Spartoi:
http://developer.sprint.com/site/global/develop/mobile_platforms/android/android.jsp#

I thought it was a TFT LCD screen.
[EVO 4G General] avalst:
LOL just like sprint to possibly print the wrong specs on their own website. I guess from a development stand point it doesn't matter if the screen in AMOLED or TFT. I worry about AMOLED considering the stuff being reported about the nexus one screen though.
[EVO 4G General] billobob:
as someone using an AMOLED phone I'm glad it has a high quality TFT instead. My phone is absolutely atrocious to view in sunlight. While Super-AMOLED takes care of this problem, it isnt available on any non-Samsung phones and Samsung probably wants to keep it exclusive for a while
[Hero CDMA Android Development] dfbonney:
Update - 2/21/2011

If you have bricked an HTC EVO this will likely NOT work for you and this is the wrong info to be reading. I have gotten a few emails from this link about EVO 110 errors.

12/26/2010 - This thread is super old now:

If you ran the 1.56 RUU and your phone no longer turns on visit htc.com, go to support, choose Hero (Sprint) and download the 2.1 system update.

Remove battery from your phone and start it up again, then run the exe file that you just downloaded -

http://member.america.htc.com/downlo...2.27.651.6.exe

------All the info below is kept for reference -------

(As of 3/31/2010 - I am 10 for 10 for getting these back and working!! 3/3 of going back to 100% stock)

Edit: I have no longer kept track... its been over a month and I know personally I've done about 15 more of these... with about half being return to stock.

If you need to contact me, PLEASE EMAIL instead of using private messages, it'll probably turn into a google talk chat anyways, so add me on there, dfbonney@gmail.com (Its just easier than having to log in here and reply to private messages, since I get emails on the go as well.)

So you just ran the 1.56 RUU and got a 110 error. Now your screen turns on and stays black and if you plug the phone into USB you see the HTC logo. Unplug it and see the RUU menu.

Like you, I decided to attempt to roll back using the RUU 1.56. I was hit with the 110 error, and nothing but fastboot would work, I was able to launch ./fastboot-mac oem boot to get into the system.

I tried ./fastboot-mac boot image/bootname.img and a billion other things like everyone else who is having the issue, but just like them I had no success. In the second post below are the steps to resolve this issue. This will either take you to your first Nandroid backup or to whatever ROM you choose to flash once you get recovery back. I have not found a way to get back to 100% stock, but at least your phone wont be a brick.

:eek:EDIT:As of 3/30/2010 @ 8:30 PM I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. See Post number 2 for the right way to do this.?

I've helped a few people over log me in now.

I'm willing to continue doing this but it is cutting into my family time, I will do this for a "respectable" amount of money.

Feel like I've helped you??

Buy me some coffee!
[Hero CDMA Android Development] dfbonney:
Other things that should be mentioned:

If you used RA 1.6.2 - I was unable to get my boot.img or the stock boot.img from the RUU's rom.zip to flash back to the recovery partition. I had to use the RA 1.6.2.img and "flash_image recovery /sdcard/recoverynamegoeshere.img"

It seems that if you've flashed the radio update, the RUU does not write the radio back successfully. Others have had issues going back to the stock radio using the upgrade.zip option as well.

I attempted to use the boot.img, recovery.img, from the RUU's rom.zip with no success. I might try it again. I was able to get to stock recovery (Triangle and exclamation) and to the Hboot menu... but from hboot I had to run the RUU and rebrick the device cause I couldnt get anything at that point, even fastboot oem boot wouldnt load.

There have been times when I get weird issues writing the flash recovery, boot, or misc and when you reboot and load "fastboot oem boot" it wont look like it goes anywhere.... check "adb devices" and your device should be listed. From there do an "adb remount" and then "adb shell" and reflash once more and then "reboot recovery".

If all else fails, I'm available for a small fee.

dfbonney@gmail.com
[Hero CDMA Android Development] imekul:
Anxiously waiting your news. :-) Just encountered this problem today.
[Hero CDMA Android Development] dfbonney:
Updated ...
[Hero CDMA Android Development] mrinehart93:
Wow! If you've fixed this, I think you're everyone's hero now. We won't have to worry about using the RUU now :)
[Hero CDMA Android Development] chavo2005:
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..

I was reading over the forum post in http://xdaforums.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
[Hero CDMA Android Development] dfbonney:
I attempted flashing a new recovery image this way with no avail... I also attempted only

flash_image recovery /sdcard/recovery.img

and still was unable to boot the phone into recovery. I think it had to have been something with doing boot.img and recovery.img at the same time... I dont know what the misc.img does and I'm assuming data.img is userdata... but I did them all and then it worked...

Other users also tried flashrec and with no success... right track though. :)
[Hero CDMA Android Development] blankd3ckskat3r:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
[Hero CDMA Android Development] regaw_leinad:
if your using a pc type fastboot oem boot

if your using a mac type ./fastboot oem boot
[Hero CDMA Android Development] dfbonney:
This!

Thanks Regaw
[Hero CDMA Android Development] imekul:
Trying this right now.

So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
[Hero CDMA Android Development] dfbonney:
If you get errors like...

adb shell

su

flash_image recovery .........

(out of memory... etc)

Then...

just su again... so you really su twice

its what I had to do.
[Hero CDMA Android Development] imekul:
Trying it a second time, and so far am getting a bunch of Out of memory errors. After the first one "finished," I did as you recommended and typed "su" a second time, and then typed the "flash_image recovery /sdcard/recovery.img" command.

So far, looks like it's giving the same errors the second time around.
[Hero CDMA Android Development] imekul:
This second attempt, it ended with "error writing recovery: No space left on device."

Just to be sure, I checked the SD card, and that has over 1 GB of free space.
[Hero CDMA Android Development] dfbonney:
If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. dfbonney@gmail.com if you're in.
[Hero CDMA Android Development] imekul:
Sounds awesome. Thanks. I'll e-mail you now.
[Hero CDMA Android Development] dfbonney:
Dun Dun Dun... The results are in!
[Hero CDMA Android Development] imekul:
dfbonney is the man!!

After a friendly little session on LogMeIn Express, I am good as new! :-) How awesome!!
[Hero CDMA Android Development] dfbonney:
We ended up just needing to run

adb shell
reboot
fastboot oem boot
adb shell
su
//flash commands here

that seemed to do it. so make sure if you're having issues to restart the device and try again!

Edit: Also, we didnt get data.img to work so we only did boot, recovery, and misc.img's
[Hero CDMA Android Development] eggfoolyung:
OIC.... because i flashrec'd RA made a nandroid backup before i flashed the rooted rom, so i have a nandroid of my phone just before it was rooted.

so, if i wanted to be 100% stock, would u recommend that i just restore my stock nandroid image and then flashrec my stock recovery image rather than using the RUU?

thx
[Hero CDMA Android Development] dfbonney:
That is the best option.
[Hero CDMA Android Development] eggfoolyung:
awesome! thx for the advice!
[Hero CDMA Android Development] lostinroot:):
I Fuc#ing Love you!!!!!!!!!!!!! you have save my phone from the round file bin!!
[Hero CDMA Android Development] arh1192:
I just got the 110 error trying to unroot my phone.

Could someone please help me?

How do I fastboot? Is that when you restart the phone holding home button? If so, that is not working.
[Hero CDMA Android Development] riggsandroid:
check out the first two posts of this thread. It is pretty clearly laid out.
[Hero CDMA Android Development] AustinKnight45:
Does anyone have a nandroid backup they could up so I can flash this hero back to stock, the nandroid.7z file on this forum isn't working it says "Error :run 'nandroid-mobile.sh' adb! I've got all the way here from it not booting and I just want to be done with this thx ahead of time.

Edit: I got it all working back to stock good guide but I still have root gonna read some more and see if I can fix it

Edit Edit : got it all back to stock THx for all info on here !
[Hero CDMA Android Development] NHuffman:
Yes you may say that it is right there in the first 2 posts im sure it is. But what happenes if this happened to me and I have no idea what yall are talking about? This is my first Droid and I just got it recently. I'd like to have knowlege of my Droid like I did my previous iPhone. But I don't. So if you can give me a dummies way of fixing my phone after my 110 error that would be amazing! Thanks yall!
[Hero CDMA Android Development] riggsandroid:
The dummies way is listed in clear steps on the first 2 posts.....

Sent from my HERO200
[Hero CDMA Android Development] anthoo47:
HELP!! I tried back and forth and how to do that "fastboot oem boot" I dont know how to to type it in on my pc. and the asroot code how do I do that also?
[Hero CDMA Android Development] dfbonney:
Hey, the 2.x update from htc doesnt brick your phone, click this link (or go to htc.com ---> support ---> htc hero (sprint) and look at the download.)

Run this RUU instead of the 1.56 and you'll be good.

http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC Sprint Hero MR 2.27.651.6.exe

:D
[Hero CDMA Android Development] dsteinmann:
When i try fast boot it just sits at the white screen "htc evo 4g"

INFOTAG:Ramdisk OK

INFOTAG:smi ok, size = 0

INFOTAG:hwid 0x0

INFOTAG:skuid 0x27F04

INFOTAG:hero panel = 0x1

INFOTAG:engineerid = 0x0

INFOMCP dual-die

INFOMCP dual-die

INFOTAG:mono-die = 0x0

INFODevice CID is super CID

INFOCID is super CID

INFOBackup CID is SPCS_001

INFOsetting->cid::SPCS_001

INFOserial number: HT0C6XXXXXX

INFOcommandline from head: no_console_suspend=1

INFOcommand line length =480

INFOactive commandline: board_supersonic.disable_uart3=0 board_s

INFOupersonic.usb_h2w_sw=0 board_supersonic.disable_sdcard=0 dia

INFOg.enabled=0 board_supersonic.debug_uart=0 smisize=0 userdata

INFO_sel=0 androidboot.emmc=false androidboot.baseband=2.15.00.

INFO11.19 androidboot.cid=SPCS_001 androidboot.batt_poweron=die_

INFObattery androidboot.carrier=COMMON androidboot.mid=PC3610000

INFO androidboot.keycaps=qwerty androidboot.mode=normal androidb

INFOoot.serialno=HT0C6HLXXXXXX androidboot.bootloader=2.10.0001 n

INFOo_console_suspend=1

INFOaARM_Partion[0].name=wimax

INFOaARM_Partion[1].name=misc

INFOaARM_Partion[2].name=recovery

INFOaARM_Partion[3].name=boot

INFOaARM_Partion[4].name=system

INFOaARM_Partion[5].name=cache

INFOaARM_Partion[6].name=userdata

INFOpartition number=7

INFOValid partition num=7

INFOjump_to_kernel: machine_id(2433), tags_addr(0x20000100), ker

INFOnel_addr(0x20008000)

INFO-------------------hboot boot time:5109 msec

FAILED (status read failed (Too many links))

finished. total time: 6.360s

???
[Hero CDMA Android Development] Asadullah:
This is for the sprint hero
[Hero CDMA Android Development] smw6180:
I must have missed something. The 110 error causes you to get stuck in fastboot...which means you don't GET adb. Or at least that's what happened to me. Sorry if I'm noobing this up, but did I miss a way to get back to adb some place?
[Hero CDMA Android Development] dfbonney:
Yep,

From fastboot the community discovered the command

fastboot oem boot

This command will boot your device to the stock ROM that was just flashed. It seems that one of the partitions isnt getting written to correctly.. (boot.img, recovery.img, misc.img or all of them...).

Once booting to stock ROM via fastboot you can enable debugging (ADB) again... from there you root the phone and flash the img files and then reboot to recovery/hboot/rom
[Hero CDMA Android Development] smw6180:
Got it. Wonder how I missed it, sorry.

But this seems to be great news. It means I don't need to be scared to RUU my phone again....considering I wrecked my first Hero that way. Great find, thanks!
[Hero CDMA Android Development] dfbonney:
Yeah, I had good luck on my first phone so I wasn't really that paranoid about it... not so lucky this time around.
[Hero CDMA Android Development] blankd3ckskat3r:
can someone post a nandroid backup?
[Hero CDMA Android Development] dfbonney:
here are boot.img and recovery.img that I used... try these to get a recovery, then you can try to flash whatever rom you want or just let the system boot... it should work to get you booting.

(I still think you should use your own, these are from a "With Google" phone from 2/10/2010, Make sure you unzip the two img files and place them in the root of the /sdcard.)
[Hero CDMA Android Development] cracker099:
I tried those files from archive.zip and it won't fastboot anymore either :(
[Hero CDMA Android Development] dfbonney:
unplug the phone, remove the battery for a few (is it still charged?).

put the battery back in, no usb or power cable and press power, does your backlight light up?
[Hero CDMA Android Development] cracker099:
Yea, I still get backlight and "fastboot devices" still shows up.

What no longer works is "fastboot oem boot"

Maybe if I try to reflash RUU 1.56 again?
[Hero CDMA Android Development] dfbonney:
Redo RUU and see where we are at. Do you have some type of instant messaging app? I think google talk might be best for this since I've already released my gmail address.
[Hero CDMA Android Development] cracker099:
Just flashed RUU 1.56 again (110 error again)

But I'm able to fastboot again, gives me hope that official 2.1 release will be able to fix this issue.
[Hero CDMA Android Development] dfbonney:
Doubtful that it will... but grab on to those strings.

Can you download logmein express and send me an email with your code to log in. I'll help you resolve it now if you have the time.
[Hero CDMA Android Development] cracker099:
okay, installing...
[Hero CDMA Android Development] cracker099:
GOT IT FIXED! Thanks to dfbonney who helped me through the whole thing.

I have the a "with Google" phone and had the 110 error flashing to RUU 1.56

This is what we did:

Since I didn't have a nandroid backup, I had to flash a rom.

After we "fastboot" to get the phone started again,we flashed the 3 files he posted up (at your own risk), rebooted into recovery mode and flashed the new rom. Waited about 5 mins for it to reboot and everything is back to normal.

Thanks again to dfbonney
[Hero CDMA Android Development] dfbonney:
You're most welcome. If anyone has done this successfully on their own please post here to let me at least know its working for others... I know there has to be more than just 3 people having this issue... unless you all already traded your phones in ;).
[Hero CDMA Android Development] unCoRrUpTeD:
Haven't RUU'ed yet, but I am saving this pages to my computer just in case I have to. With all the problems that came up in the last couple of days in regards to the PRI I was going to RUU, but after reading horror story after horror story on how this F***ed up the phone I just waited and luckily got a fix.

You will be a savior to everyone else that tried RUUing and bricked their phone..

Great Job
[Hero CDMA Android Development] Mistamike17:
Would be good to have this stickied or put in some sort of FAQ or something at the top of the section. Mods?
[Hero CDMA Android Development] dfbonney:
I just got done doing another one over logmein.... thats 4!
[Hero CDMA Android Development] looneylu:
wow man!!! congratulations!!! so since you are having so much success, do you have any idea what is causing the brick???
[Hero CDMA Android Development] dfbonney:
When I was watching the rom.zip from RUU 1.56 flash from fastboot (without using the RUU program) it fails when writing the recovery/boot portion... I dont know why, but there isn't much we can do about it. It could be anything that HTC changed.. including a small increment in a partition size.

With that said, the closest I've come back to "stock" is my nandroid backup with root access. It doesnt boot after you flash the img files until you either do a restore or flash a ROM.
[Hero CDMA Android Development] smw6180:
So this DOES get you back from the 110 error, but you still don't have a stock flashed, I take it?

Not that it matters that much. Just curious. I'm going to RUU my phone later and see what I see.
[Hero CDMA Android Development] dfbonney:
Yep, I got back to my first recovery..

Others that I have helped had NO Nandroid backups at all. PLEASE, PLEASE everyone run a Nandroid backup, its very important for you, not me!

For these cases one person chose to put Damages 2.1r2 on and the other used fresh1.1 and they both were successful.
[Hero CDMA Android Development] smw6180:
I have about 15 nandroids. Don't worry, plenty of backups to restore from :)

But again, if the RUU fails, there's no way to get back to stock, right?
[Hero CDMA Android Development] dfbonney:
I think if we extracted the img files from the rom.zip from the RUU individually we could get back to completely stock. I never planned on being 100% stock so... I really didnt look into it.
[Hero CDMA Android Development] dfbonney:
Also... Just an FYI for all of you who might try this... I did the 1.56 RUU again today just to try it and it bricked me again, so this doesn't fix the RUU issue... it just gets you back to a working phone.
[Hero CDMA Android Development] smw6180:
Might be something to play with (for someone who knows more about it than I do...I'm good with a lot of this stuff, but I haven't messed with extracting/signing/etc yet) just in case it becomes necessary to have stock.

But in any event, sorry for side-tracking your thread. I'll RUU (I expect the 110 error since I had it on my last phone) and let you know how it goes :)
[Hero CDMA Android Development] dfbonney:
I'll be looking forward to your post, if you have any need for assistance I will be randomly available through the night, all updates on this thread go to phone as well as emails.
[Hero CDMA Android Development] mjhuffer:
any way to get stock romhero unrooted

Is there any way to get the phone stock and unrooted from the loaded fastboot oem boot. I have the newer hero with the "with google" on the back. the 1.29 and the 1.56 just brick my phone. I want to get back to stock so I can make sure I can get the 2.1 update in a couple of weeks. I've already talked to dfbooney about this whole process but I just really need to get my phone to stock. If I dont here anything by tomorrow, I'm going to take my phone into sprint and say it messed up.
[Hero CDMA Android Development] GURUGTS:
Where to get the RUU?

Here is my thread that I started. I'm new to CDMA and I was on the GSM stuff for a long time and most of those threads had "how to restore" guides.

Here is my thread that I had started, dfbonney suggested that we combine them somehow:

http://xdaforums.com/showthread.php?p=6023047#post6023047

We also should get a tally of the HERO Variants:

New Google Branding On Back

Hero200

Baseband: 1.04.01.09.21

PRI 1.70_003

PRL 60662

There were some complaints on Damage's original v2.0 thread about changing the title about the ROM being 100% but he refuted it properly and did not want to change the name, however I believe the ZERO bugs and Zero issues statement should be taken out because it's quite misleading.
[Hero CDMA Android Development] smw6180:
Make that 5/5 ;)

I got the 110 error as expected, followed your instructions (with a couple of little bumps: Have to re-enable debugging (which I forgot to do at first) to get adb to work, that kinda thing).

I also had this problem:

# flash_image data /sdcard/data.img

flash_image data /sdcard/data.img

can't find data partition

But I ignored it and it worked anyhow.

Also your directions say NOT to put the cache.img into /sdcard but then say to flash_image cache /sdcard/cache.img which will obviously fail :)

Right now I'm going to rip those images out of the ROM and see if I can make this look like stock. ;)

Edit: Or not. I forgot the thing's signed and I have no idea how to open it up. ;)

Edit again: Bwahahaha...winrar opened it right up. Time to play.

Another edit: I've decided that the better part of valor in this case lies in someone else who knows what they're doing trying this. The images that are available in rom.zip are 'radio' 'recovery' 'boot' 'hboot.1.41.00000' 'nv' 'system' and 'userdata'.

While it'd PROBABLY be ok to flash boot, recovery, and userdata I'm not actually brave enough to try it. ;) That having been said, I've RUU'ed my phone twice (110 errors both times) and recovered using this method. Works fine. :)

Final Edit (Maybe?): Confirmed: you don't have to nandroid after flashing those images. The system will indeed boot without a nandroid restore. At that point you're as close to stock (assuming the images you used were from the first nandroid you should have done immediately after getting your recovery image flashed when you first rooted your phone) as you can get without the RUU working. Right boot image, right ROM version. Doesn't change the radio or kernel.