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, [email protected] (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.
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!
(Zip attached includes fix and stock folders. Use the fix folder FIRST to get completely booted. You can use the stock folder if you want to get 100% stock after you have a running unrooted system but have RA recovery.)
Steps to resolve:
(You SHOULD have a Nandroid backup of some sort, if not download a ROM... Fresh1.1??)
1) Boot the phone to black screen
2) Plug phone into PC/MAC - The HTC logo should appear at this point
---- If you've been doing anything else, rerun the RUU and let it fail and reboot to the HTC logo.
3) PC - fastboot oem boot | MAC - ./fastboot oem boot
(Make sure you turn on USB Debugging under Settings --> Applications --> Developer)
4) Root your phone using asroot2
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
5) This is where your Nandroid backup comes into play.
(Browse to your nandroid folder, find your first backup and copy all of the .img files except system and cache to your SD card root directory)
NOTE: At this point you should dismount the SD card if you mounted inside of Android OS(Sense/Launcher)
6) run adb shell (PC - adb shell | Mac - ./adb shell)
7) type su
8) Run the following commands (if you get out of memory errors, type su again and try once more)
NOTE: Do not copy the "#"'s in the commands, the # just means you are running as SU, as opposed to the "$"
Code:
# flash_image recovery /sdcard/recovery.img
# flash_image boot /sdcard/boot.img
# flash_image misc /sdcard/misc.img
9) now... type reboot recovery
This time you should get your recovery menu, should have been RA or whatever you used... from there I did a complete nandroid restore and my system booted.
Also, after I did this I did try to let it boot without doing a recovery and it wouldnt go anywhere... but I'm fairly impatient... it may have wanted to load. I figured it best to do an entire Nandroid restore though.
-------------------------------------------------------------
100% Stock Configuration Work Around
-------------------------------------------------------------
Non-Rooted Nandroid Backup:
nandroid.7z
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. I'm not sure how to go about posting a 127MB file, what do you think it the best place?
After restoring the Nandroid backup I tried this:
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
$ su
su: permission denied
Then I rebooted to recovery (I used RA 1.5.2)
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb remount
remount succeeded
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
/ # cd /sdcard
/sdcard # flash_image recovery /sdcard/Stock/recovery.img
flashing recovery from /sdcard/Stock/recovery.img
/sdcard # reboot recovery
I was booted to the Triangle and exclamation mark... I pulled the battery and booted up normally.
Stock Kernel - 2.6.27-533ce29d [email protected] )
Stock Build - 1.56.651.2 CL85027 release-keys
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.
[email protected]
Anxiously waiting your news. Just encountered this problem today.
Updated ...
imekul said:
Anxiously waiting your news. Just encountered this problem today.
Click to expand...
Click to collapse
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
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://forum.xda-developers.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!
I attempted flashing a new recovery image this way with no avail... I also attempted only
Code:
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.
chavo2005 said:
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://forum.xda-developers.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!
Click to expand...
Click to collapse
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
blankd3ckskat3r said:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
Click to expand...
Click to collapse
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
This!
Thanks Regaw
regaw_leinad said:
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
Click to expand...
Click to collapse
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?
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.
imekul said:
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?
Click to expand...
Click to collapse
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.
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.
If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. [email protected] if you're in.
imekul said:
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.
Click to expand...
Click to collapse
Sounds awesome. Thanks. I'll e-mail you now.
Dun Dun Dun... The results are in!
imekul said:
Sounds awesome. Thanks. I'll e-mail you now.
Click to expand...
Click to collapse
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
imekul said:
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
Click to expand...
Click to collapse
We ended up just needing to run
Code:
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
I know you had to push a reboot file to get it working on some Hero ROMs. What about the EVO version?
The Hero way works.
FIRST, install Quickboot from the market. Run it and enable it in the superuser permissions screen.
Download the reboot.txt file I attached and rename it to "reboot" (take off the ".txt"). Move it to where ever your "android-sdk-windows/tools" folder is.
Connect your phone to your computer (make sure it is "charge only") and boot into recovery...
Code:
adb shell
reboot recovery
Start your "Windows-recovery.bat" (if using windows) and let it do it's thing in the CMD prompt. Keep that prompt open.
In a CMD prompt OTHER THAN the one opened by recovery.bat type...
Code:
adb shell
mount /dev/block/mtdblock4 /system
exit
This will keep your system mounted but get you out of shell. Now type...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
Once you're back up, run Quickboot and choose either reboot or recovery (both will now work). It takes about 5 seconds to start rebooting but it does work.
What does this do? does it make recovery stick?
watzone69 said:
The Hero way works.
Download the reboot.txt file I attached and rename it to "reboot".
Once you're in recovery...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
EDIT: It takes about 5 seconds to start rebooting but it does work.
Click to expand...
Click to collapse
Woo! Thanks!
Edit: Didn't seem to work for me. Damn.
joeavery2 said:
What does this do? does it make recovery stick?
Click to expand...
Click to collapse
No, this just lets you use the QuickBoot app from the Market to reboot your phone.
TheBiles said:
Didn't seem to work for me. Damn.
Click to expand...
Click to collapse
Code:
adb shell
cd /system/bin/
ls
See if the reboot file actually got pushed to the directory. If so, try this:
Code:
chmod 755 /system/bin/reboot
The only other thing I can think of is that I installed Quickboot BEFORE doing all of this. Did you get the SU permission screen when you tried to run it?
Any luck??
Did I mention that the Quickboot "recovery" button works also? Much easier than opening a shell and typing it in.
Of course you still have to run the recovery.bat to get the custom recovery but at least it's one less step.
Still no dice. I also already had QuickBoot installed and granted it root permission prior to pushing the reboot file.
any update to this?
thanks
joey3002 said:
any update to this?
thanks
Click to expand...
Click to collapse
It doesn't work for you?
I updated my earlier post to give more instructions for getting into recovery and pushing the "reboot" file. I hope it helps!
I have a ROM ready to go that changes a couple icons and quickboot works with no probelm. Wifi tether is the only thing I don't have working. I can post it if you would like. I also removed sprint apps and some widgets
I made an update zip that got Quickboot working for me. This is using watzone69's reboot file.
Run from Toast's recovery. http://forum.xda-developers.com/showthread.php?t=690762
watzone69 said:
It doesn't work for you?
Click to expand...
Click to collapse
yes i got it working last night by reading this thread from top to bottom.. then repeated.. thanks
Rooted my Transform and went in to the superuser APK.... I'm disappointed that it has very limited content vs. my buddies HTC EVO. I'm new to Androids, but anyone know if there would be a way to port the superuser APK from the HTC EVO to the Samsung Transfrom, or is it even Feasible?
Can you go into more detail on how you rooted your Samsung Transform. I have tried SuperOneClick but the root never sticks. I would lose superuser randomly.
I just rooted with Super One Click, now, i dont know what to do with it lol. It sticks with me though.
No need for a superuser port. Just download from the market after rooting
via skeeterslint sdx:
Heres is a one click recovery installer for people that don't want to do it by hand.
http://www.mediafire.com/?jl21knp1d0lbf17
This is a still beta but working version of SDX Recovery version 3.1.1.
Things known to work.
Backups and restores.
Clearing dalvik cache.
Clearing cache partition.
Flashing kernel zImages.
Flashing zip files.
Adb works in recovery.
Also mounting the sdcard to your computer works.
Anything else in the options is still in need of testing I am not responsible if your phone gets bricked.
THIS MAY BRICK ALL PHONE MODS YOU DO AT YOUR OWN RISK!
OK now that thats out of the way heres the files needed.
1. http://www.mediafire.com/?862j3wlzftenwef This is the recovery image.
2. http://www.mediafire.com/?67an7lkm9qtmf5b until there is a custom recovery you will need this program to flash recovery. Its called flash_image.
3. http://www.mediafire.com/?5dcv3r14sjvsfdq rage.bin temporary exploit to get root.
4. You will also need the Android SDK so you have a working adb to be able to push files over to your phone.
If you are flashing this from a phone running my rooted kernel you can skip steps 4 and 7 and just su over to a root prompt.
OK these are the steps to install this recovery.
1. Make sure adb is installed and working there are how to's on the forum to get this setup or just use google.
2 adb push recovery.bin /data/local/tmp to move the kernel to the phone.
3 adb push flash_image /data/local/tmp to move flash_image onto the phone.
4 adb push rage.bin /data/local/tmp to move rage.bin onto the phone.
5. Run adb shell to get to a shell prompt on the phone.
6. Run chmod 755 on flash_image and rage.bin chmod 755 rage.bin chmod 755 flash_image.
7. Run ./rage.bin and let it go run through untill it exits you out of adb.
8. adb shell you should now have a root shell on the phone.
9. Run ./flash_image recovery recovery.bin to install the kernel.
Once its installed to get into recovery use Volume down Camera and power to get into recovery.
Volume up and down scroll through the option.
Menu should be the enter key.
Back button is back.
Search key is delete.
You will need to create the directorys on your sdcard that recovery needs to flash zip files make backup and flash kernel and recovery from.
Create directory called sdx on the root of the sdcard and inside it create 3 folders zips update and backup.
At this time it seems that factory restore is not working correctly and anyone else can confirm please let me know.
And for better recovery via vampirefo on sdx:
his is my first recovery, I made the change to the first screen to show that this is a transform recovery rather than a moment recovery. Also I got console to work in recovery, it wont rotate but works just fine.
http://www.4shared.com/file/bBTlN7UZ/recoveryrfs.html
You can flash this via swupdate, or if you already have skeeters recovery installed, just extract recovery.tar to /sdcard/sdx/updates
boot to recovery
Scroll down to
Backup, Restore, Flash
Scroll down to
Flash Recovery
After flash is complete
press back button
Under Reboot options choose Reboot to Recovery to see new recovery
Hey,
Ok so a little backstory before my problem: So I was in the middle of putting a new ROM on my captivate. I had one before but i wanted to change so I put the rom in update.zip and installed it will clockworkmod recovery. It installed fine I think but then when I tried to boot it gets stuck on the boot screen. So i tried to boot in recovery mode. I geld down both the volume buttons and the power button until it reboots twice, then I let go of the power button. but it still gets stuck on the boot screen and does not go into recovery mode. So i plugged it into my computer and using
Code:
adb devices
it shows up under recovery mode. So far so good. I can use the
Code:
adb reboot
and
Code:
adb push
commands fine. but when i try to use
Code:
adb shell
it says
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
So i can not reflash the recovery image. I read that I just needed to mount the /system file. But i do not know how to do this. the "mount" command does not work with adb. I would appreciate anything to help me to either reflash the rom or restore to factory or anything where i can work off of. thanks
I have exactly the same problem.
Did you get to a solution to this?
Good luck, dude.
Is there a solution to this without using a Motorola Factory cable? I don't have the resources to make one and I don't have money to buy one.
I'm not sure putting the rom into "update.zip" was the right choice.
adb shell could fail because the partition is not mounted, the sh binary is not installed, or not at the correct location
If you can still get the captivate into download mode, you could use odin/heimdall to flash a working ROM.
First of all...thanks to everyone that has EVER posted in the XDA forums! I've spent days reading them and I came across one that had a suggested solution for my problem. So let's start...
1) Bricked
2) ADB is finally working again...so..not a problem any longer
(Don't ask me how I got it to work again....I have no idea. System was wiped while using TWRP from a bootloop)
3) Now...with system wiped I have no '/system/bin/sh'
4)adb shell will not work because of this. adb root does not work because of production model. adb remount is not permitted.
Now....I came across a thread that suggest using r2.6.2.kindlefire.boot.insecure.img and zergRush. I have the zergRush file, but I need the r2.6.2.kindlefire.boot.insecure.img to push with adb.
Does anyone know where I can get the r2.6.2 at? Filesonic is disabled and Multiupload will not return page.
Link I came across: addictivetips /mobile/gain-root-adb-access-with-insecure-boot-image-for-kindle-fire/
I have a 2015 gen 5 OS 5.1.1 HD 8. I am trying to get it back to stock just to refresh. I try going to settings and doing a system refresh restarts and nothing.
click update shows no updates available. place up[date.bin file in the root of the device, shows update available. Then I click start update, validates update then restarts nothing.
My device is rooted and i dunno what else to do. I thought maybe its one of the packages thats disabled so I went to adb shell then su. Then ran pm list packages -d to show all disabled ones, then enabled those.
So i read that you can adb sideload an update.bin, so I go to put the device into recovery mode. Vol Down + power. Nothing Amazon screen boots then black then amazon screen then the fire screen.
tried every combination and dont know what to do.
So i've tried everything and cant seem to get it to work. Any suggestions?
Fixed
I fixed it. Guess I Messed up my recovery partition. Anyway I remembered from an old post that i had someone post the recovery file.
You must have root.
So copy recovery.img to the root of the device or /sdcard
then go to your command shell.
adb shell
su
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
dd of=$DEV if=/sdcard/recovery.img
exit
exit
adb reboot recovery
should reboot into recovery
then after downloading correct update.bin
adb sideload then filename of your update.
worked and am on my wiped device.
Thanks ...... to myself for messing it up and fixing it.