Database Users

Can you load a new recovery image via fastboot?

Something went haywire when trying to update Amon_RA's new recovery image. I now can't get into recovery and my ROM wont load. All I have is fastboot. I need to load a new recovery image to get into recovery but haven't been able to using the ADB. I've tried the various methods I've seen online with no success. Any advice?

I only rooted my phone around 6 hours ago, so I'm hoping this is what you meant. I was able to use fastboot to boot into a recovery ROM. Try using:
fastboot boot XXX.img
That should allow you to boot straight into it.

Yes I can...will you try copy recovery to SDK\tools?

Reavern said:
I only rooted my phone around 6 hours ago, so I'm hoping this is what you meant. I was able to use fastboot to boot into a recovery ROM. Try using:
fastboot boot XXX.img
That should allow you to boot straight into it.
Click to expand...
Click to collapse
Its a .zip file tho. I've tried "fastboot flash_image recovery..." command but it didn't work.
SarDroid...huh? What do you mean?

staunty said:
Its a .zip file tho. I've tried "fastboot flash_image recovery..." command but it didn't work.
SarDroid...huh? What do you mean?
Click to expand...
Click to collapse
I think you can only flash official images using fastboot. I'm you can use "fastboot boot recovery.img" to load something like Cyanogen's recovery image you will get ADB access. From there you should be able to flash anything.

put recovery in your sdk tools folder
and boot to fastboot
and
fastboot flash recovery recoveryxxxx.img
also check Amon_RA's post where you got the recovery from it tells you how to do it

sitimber said:
put recovery in your sdk tools folder
and boot to fastboot
and
fastboot flash recovery recoveryxxxx.img
also check Amon_RA's post where you got the recovery from it tells you how to do it
Click to expand...
Click to collapse
OK, I'm still not having any luck. Here is what I've done...I found the .img file for a previous recovery image. All the newer ones seem to be .zip files. For the recovery image, it won't recognize a .zip. So, I put the "recovery-RA-dream-v1.3.2.img" image in my AndroidSDK\tools\ folder. Then, in fastboot, I did "fastboot flash recovery..." and it said okay. Rebooted but it still didn't reboot to recovery when I held down home button.

staunty said:
OK, I'm still not having any luck. Here is what I've done...I found the .img file for a previous recovery image. All the newer ones seem to be .zip files. For the recovery image, it won't recognize a .zip. So, I put the "recovery-RA-dream-v1.3.2.img" image in my AndroidSDK\tools\ folder. Then, in fastboot, I did "fastboot flash recovery..." and it said okay. Rebooted but it still didn't reboot to recovery when I held down home button.
Click to expand...
Click to collapse
do
Code:
fastboot boot recovery.img
let the phone reboot, dont touch and anything. you could also try
Code:
fastboot flash recovery recovery.img

have you unzipped the zip files they mght just be .img inside

I have the same issue. but when I follow the steps to flash or boot the recovery.img cmd prompt just says
sending 'recovery' <4166 kb>... FAILED <remote: not allow> finished.
cd to sdk tools (placed recovery.img here)
fastboot boot recovery.img
fastboot flash recovery recovery.img
tried it again and

Install androidsdk and get a copy of a recovery image for your device. Copy the .img to the tools folder in \androidsdk and rename file to recovery.img (for simplicity later). Connect the phone to PC with USB. Power up phone while holding volume down. Get to fastboot USB, open up command prompt (elevated if vista or 7) and cd to androidsdk\tools. then "fastboot erase recovery" then "fastboot flash recovery recovery.img" then "fastboot reboot".

HI,
before begining you must put the android sdk in the root of the c;/, and suitch off your phone , and hold the back bouton and the end call bouton until you see the 3 android in your fone so ,you try this command to see if the pc reconize your phone :
C:\AndroidSDK>fastboot devices
List of devices attached
XXXXXXXXXXXX fastboot
if you cannot see your IMEI listed you must instal the drivers utilities on your pc
if you see the pc listed the IMEI ,then you can flash the recovery .img .
-Place the recovery image downloaded into the androidsk/tools folder and rename it to recovery.img and try with this command :
fastboot flash recovery recovery.img
that all good luke

Hi guys, how I can achieve this with S-ON? I can't flash SPL because I haven't sdcard and using ADB don't know, any help on this?

I have the exact same issue.
I only have fastboot access however I always get remote: not allow. ( Perfect SPL )
Phone Stats
HTC Magic 32A S-ON H
HBOOT 1.76.0010 (SAPP50000)
CPLD-12
RADIO 6.35.16.19
I have created a gold card and tried flashing a sappimg.zip file but that gave me wrong model ID.
Anyone have any idea what I can do?

is my phone bricked? can't mount sd

hi, i've searched the threads and tried everything but nothing has helped. found a very similar thread but their solution didnt' work for me...
tried a new rom (froyo), wiped, flashed, rebooted then it had sdcard mount problems thought it was the rom so i wiped and then tried to flash with no luck it says
build: RA-sapphire-v1.5.2H
E:Can't mount /dev/block/mmcblk0p1 (or dev/block/mmblk0)
(No such file or directory)
E:Can't mount SDCARD
Boots RA-sapphire-v1.5.2H and fastboot just fine
SAPPHIRE PVT 32B ENG S-ON H
HBOOT-1.33.2005 (SAPP30000)
CPLD-10
RADIO-2.22.23.02
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck

Try this from command line, boot into fastboot and type:
fastboot oem enableqxdm 0

no good,
...INFO [ERR] Command error !!!
OKAY
HELP!!!!!!!

Oops, didn't see that you were using 32B
try this(You need recovery image first):
Code:
fastboot -c board_sapphire.disable_sdcard=0 boot [b]<recovery image name>[/b]
From here, you should be able to flash another ROM.

to be clear... if my recovery image was renamed to recovery.img i simply type this into fastboot?
fastboot -c board_sapphire.disable_sdcard=0 boot recovery.img
NEVERMIND, ok the recovery image has been flashed but it still doesn't let me access the SD CARD to install a rom...
i'm still not understanding what to do after i put in your command. still no access to sdcard
ok so should i just throw my phone against the wall or something...
anyhting i want to flash from fastboot gives me FAILED (remote: signature verify fail)
except the recovery image i was able to flash with the code provided above. anyone know how i can flash a radio or rom from fastboot without getting that message? remember the phone is 32B and it cna't recognize my SD CARD (my problem in the first place)

I have the same problem, but just do this:
Go into recovery -> Backup/Restore ->
choose Nandroid backup but don't press home to start the backup; press back instead.
Do this last step 2 to 3 times and flashing from sd should work.

ok well ... i managed to unroot my phone by installing the sappimg.nbh
but now i can't get into recovery...
and my phone does not recognize my SD CARD in any shape or form. the SD card seems to be fine though when i put it in my PC
so at this point... phone is working with stock ROM but SD CARD can not be found.
HELP!!!

I'm going to close this because it is posted in the wrong section.
@Dannyfal, I'll open this back up when you can send me a private message with where you think that this should have been posted.
I know that you're all going to think that this is cruel and even counter-productive but I have to move over a dozen posts each night because some members just don't know what qualifies as "Development." To qualify for "Development" is must be regarding production or modification of Android software.
If you think that this is unreasonable then refer to this post here:
http://forum.xda-developers.com/showthread.php?t=545005

[Q] Phone will not boot up

I hate to do this but I this is my last resort to getting my phone back working. I currently can not get pass splash screen. Phone was already rooted running cm7 and I wanted to go back to one of my old nandroid so I flashed CW 2.5.1.2. It was working fine but was running slow so I did a data format and wipe cache and ever since then it will not boot up. I am getting a E:Cant' mount CACHE:recovery/command and log message when recovery loads up.
I can get into fastboot and recovery fine but I cant seem to flash any of my nandroids anymore. I have about 5 of them and none work. I can't flash any roms either. It seems as if my root may be gone because when Im in adb shell and run su it does not give me root and I cannot mount any systems in recovery. I tried everything from trying to flash to stock through hboot and even flashing new recovery in fastboot but that did not work since I do not have ENG HBOOT. Tried rerooting and unrooting it again but I always have to go into that /data/local but I am never able to gain access. I do still have S-OFF but that seems to be about it. Oh yeah and I cant even do a wipe data/factory reset. Says E:format_root device: can't find mmc partition.
So if someone knows anything else I could try to get this resolve that would be cool.

Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.

BlackSHELF said:
Ok lets start don't panic all is not lost yet you can still have root with S-OFF and have access fastboot and recovery. I am not sure why you reverted back to older CWMR2.5.1.2 as if you had CWMR3.0.0.6 you could have done it without fastboot but makes no diff now.
First go try "fastboot erase system -w" and then boot in to recovery and do full factory wipe and then flash as you normally would do.
Click to expand...
Click to collapse
I reverted back to that one thinking that it would enable me to flash a none cm7 rom.
Here is what I got. From my understanding I am getting this because I do not have ENG HBOOT but please correct me if Im wrong
C:\android-sdk-windows\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.020s

Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.

BlackSHELF said:
Hmmm I just reread your OP and you saying you somehow lost root trying to unroot and reroot, so I am not sure about the current status.
NOMRAL CASE:
http://forum.xda-developers.com/attachment.php?attachmentid=516463&d=1297577207
^ download that and unzip it and get the recovery.img for 3.0.0.6 and try "fastboot flash recovery recovery.img" as that would do if not try the below.
EXTREME CASE:
http://www.filefactory.com/file/caa....140e_26.03.02.26_M_release_155771_signed.zip
File: PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.1 40e_26.03.02.26_M_release_155771_signed.zip
MD5: 49D07F0EE7DE1765A6A84CB12FA53110
Size: 312 MB
^ go download the file and then rename it from "PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60. 140e_26.03.02.26_M_release_155771_signed.zip" to "PD15IMG.zip" (make sure its not PD15IMG.zip.zip) and put it in root of your SDCard. Go in to bootloader and follow the instructions. This will get you to stock rom/radio from there you can redo all your stuff.
Click to expand...
Click to collapse
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3426 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.180s
The other file did not work either. It had "Fail-PU" for all the files it tried to flash

Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.

BlackSHELF said:
Did you try the PD15IMG.zip from bootloader? Download it make sure its not corrupted that is why I provided you with md5 hash to verify. Then put the file in root of your sdcard and then boot in to bootloader, it will scan it and follow the instruction to revert back to original.
Click to expand...
Click to collapse
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu

lilterro said:
Yes I just verified it and it is not corrupt. Thats the way I did it and came up fail-pu
Click to expand...
Click to collapse
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.

BlackSHELF said:
Hmmm never seen or heard of that I am taking fail pu means failed partition update. What does your HBOOT ver say on the screen? I am not sure what happened but seems like it soft-brick ATM still not sure how you lost root. Hopefully someone who has little more knowledge can shed some light.
Click to expand...
Click to collapse
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000

perm-brick no fix
lilterro said:
Ok thanks anyway. I am normally able to wok my out of alot of these issues that come up with flashing but this one got me stumped to.
HBOOT-0.86.0000
Click to expand...
Click to collapse
I am having the very same problem i am very good at fixing my mistakes but this one is impossible i get that same fail-pu but only difference is mine is s-on and it was never rooted only temp-root i was trying to perm-root and that's when it crashed will not boot up any more and i can't boot into recovery because it never been rooted and i don't know how to do ( C:\android-sdk-windows\tools>fastboot flash recovery recovery.img ) looks like something for the pc and i tried factory reset it will just freeze with the 3 androids skating i go to fastboot and i see bootloader, reboot, reboot bootloader and power down but those did nothing i even offered $100 through paypal to the first person how fixes it but it's an impossible task so there is a full brick out there people say its not but i see different.
perm-brick no fix

S.O.S Help me flash Ginger Yoshi 1.2.1!!

So my niece bought a Mytouch 3g 32a (3.5mm jack)
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
RADIO-2.22.28.25
JUN 2 2009,17:27:03
Is what got so far(i am rooted of course), Ive been trying to flash this ROM for 4 hours now(stubborn)
Can anyone tell me as far as components what am i missing? Ive read my ass off, watched numerous videos and it seems that there 30 different configurations for all these different roms availible..
If anyone can point me in the right direction that would make a 13 yr old girl who got her first android very happy..
Btw, is the superwipe method use in the video from the OP vital?
Thanx in advance for your help

big nu said:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
RADIO-2.22.28.25
JUN 2 2009,17:27:03
Click to expand...
Click to collapse
The sapphire Unknown 32a is what usually happens when you put the 1.33.20XX SPLs on a MT2.1/Fender phone with the audio jack.
for all the functionality of the MT2.1/Fender to work you must use the 1.33.0013/1.33.0013d SPLs.
First install adb/fastboot on your PC if you do not already have the programs installed. (Search for it since I just build/put the linux binaries on my path)
Download dream_2708kit.zip
Unzip the dream_2708kit.zip on your PC; you will see 2 files:
>> hboot-1.33.0013d.img (MD5: c35ff1159828a6186cb98a9cfaa81613) Place this somewhere easy to access (such as on your C: drive if you have windows)
>> radio-2.22.27.08.img This file is not needed delete it
Download [http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-sapphire-v1.7.0G.img]recovery-RA-sapphire-v1.7.0G.img[/URL] (MD5: 8b3b5ff90575eba0c5bfc13c0fa6b8ea) (file from this thread)
Place recovery-RA-sapphire-v1.7.0G.img in the same place as you did hboot-1.33.0013d.img
Open your command line/terminal on your PC and run (per your fastboot instructions) the following:
Code:
fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
fastboot erase system -w
(note if you placed recovery-RA-sapphire-v1.7.0G.img and hboot-1.33.0013d.img on your C: drive make sure you either are in C: when calling fastboot at the command line, or easier just provide the full path to the file eg: fastboot flash recovery C:\recovery-RA-sapphire-v1.7.0G.img)
Now you ought to have the correct SPL and recovery
You can now power off (press menu on the phone) and then boot into recovery (press home while turning on)
Once in recovery flash a rom as usual;
if the files are not on the root of your SD card mount the MS Card via recovery to your computer then copy into the root of the sdcard:
>>in the case of ginger yoshi:
ginger yoshi 1.2.1 fix 1.zip (from the media file link on the ginger yoshi OP)
ezgb-2636-v1.5_S.zip (from here)
Then eject the sdcard on your computer (on windows that’s: safely remove hardware)
Then flash the ginger yoshi 1.2.1; in recovery followed by the kernel
>>in the case of ezGingerbread:
From the second post get:
GINGERBREAD-DS-Beta-20110716.zip AND gapps-mdpi-gb-20110709_S.zip
Then eject the sdcard on your computer (on windows that’s: safely remove hardware)
Then flash the Beta followed by the gapps
(Note I'm not the one to ask about any problems with adb/fastboot on windows; Also I don't particularly support ginger yoshi, my ezGingerbread rom eats plenty of my time.. so make sure you ask any questions here and don't PM me .. as you will get a reply much faster posting here)

u da ish!!
ezterry said:
The sapphire Unknown 32a is what usually happens when you put the 1.33.20XX SPLs on a MT2.1/Fender phone with the audio jack.
for all the functionality of the MT2.1/Fender to work you must use the 1.33.0013/1.33.0013d SPLs.
First install adb/fastboot on your PC if you do not already have the programs installed. (Search for it since I just build/put the linux binaries on my path)
Download dream_2708kit.zip
Unzip the dream_2708kit.zip on your PC; you will see 2 files:
>> hboot-1.33.0013d.img (MD5: c35ff1159828a6186cb98a9cfaa81613) Place this somewhere easy to access (such as on your C: drive if you have windows)
>> radio-2.22.27.08.img This file is not needed delete it
Download [http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-sapphire-v1.7.0G.img]recovery-RA-sapphire-v1.7.0G.img[/URL] (MD5: 8b3b5ff90575eba0c5bfc13c0fa6b8ea) (file from this thread)
Place recovery-RA-sapphire-v1.7.0G.img in the same place as you did hboot-1.33.0013d.img
Open your command line/terminal on your PC and run (per your fastboot instructions) the following:
Code:
fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
fastboot erase system -w
(note if you placed recovery-RA-sapphire-v1.7.0G.img and hboot-1.33.0013d.img on your C: drive make sure you either are in C: when calling fastboot at the command line, or easier just provide the full path to the file eg: fastboot flash recovery C:\recovery-RA-sapphire-v1.7.0G.img)
Now you ought to have the correct SPL and recovery
You can now power off (press menu on the phone) and then boot into recovery (press home while turning on)
Once in recovery flash a rom as usual;
if the files are not on the root of your SD card mount the MS Card via recovery to your computer then copy into the root of the sdcard:
>>in the case of ginger yoshi:
ginger yoshi 1.2.1 fix 1.zip (from the media file link on the ginger yoshi OP)
ezgb-2636-v1.5_S.zip (from here)
Then eject the sdcard on your computer (on windows that’s: safely remove hardware)
Then flash the ginger yoshi 1.2.1; in recovery followed by the kernel
>>in the case of ezGingerbread:
From the second post get:
GINGERBREAD-DS-Beta-20110716.zip AND gapps-mdpi-gb-20110709_S.zip
Then eject the sdcard on your computer (on windows that’s: safely remove hardware)
Then flash the Beta followed by the gapps
(Note I'm not the one to ask about any problems with adb/fastboot on windows; Also I don't particularly support ginger yoshi, my ezGingerbread rom eats plenty of my time.. so make sure you ask any questions here and don't PM me .. as you will get a reply much faster posting here)
Click to expand...
Click to collapse
@ezterry
Awesome! this is exactly what i needed.. im up and running 2.3.4 sweetnes!!
Thanks a million

my g1 32b doesnt get past boot screen for gingeryoshi as well as ezgingerbread
i have 2708 radio and spl..im currently using froyo by laszlo..
do i need to flash any kernel or need to have other radio..
i waited for about 30 mins after rebooting..
please help me out guys..

When trying to flash the recovery onto my phone after I've booted the SPL from here, I get this error--
Code:
sending 'recovery' (4520 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Any ideas?

oakraider4life said:
When trying to flash the recovery onto my phone after I've booted the SPL from here, I get this error--
Code:
sending 'recovery' (4520 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Any ideas?
Click to expand...
Click to collapse
Download the recovery image again, it seems to be corrupted or somehow broken. If you want to be sure, check its MD5 hash if it is correct

I solved my problem. It turned out that after flashing the SPL, my security had reactivated, so it was a simple matter of loading sapp.img up again. For some reason though, after flashing a new recovery onto my phone, my phone won't boot into it... If anyone knows of a way to flash ginger yoshi using fastboot, please share!

Proper Kernal for Ginger Yoshi
A solution I have found to getting the Ginger Yoshi ROM on a MyTouch 1.2 with a 3.5 jack is to after you flash the ROM, flash the Proper Kernal for the MyTouch 1.2 over the ROM.
I don't have the link for the right Kernal offhand,
but I have been using Ginger Yoshi since 1.2 or 1.3 by doing that, and am currently using the 1.5.
If you PM me I can send you the kernal I use and you can try it.

[GUIDE] How To Root HBOOT 1.02/1.07 and gain S-OFF

I am in no way responsible if you turn your phone into an expensive brick. Unlocking bootloaders is technical, and can be hazardous to your devices health if you don’t understand what you are doing.
REQUIRED: ADB, fastboot, and all related drivers setup and working on your pc. If you do not have adb setup download this http://dinc.does-it.net/Guide_Root_New_Hboot/adb_fastboot.zip, and extract the files to some place like C:\adb and also download these required drivers http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install.
1. Head over to HTC Dev http://www.htcdev.com/bootloader/.
2. Create a account or sign in (you must use your real email address).
3. Go to unlock bootloader.
4. Select “HTC DROID INCREDIBLE*”.
5. Follow the directions and install all the software provided and you will end up with a unlocked bootloader with s-on. Save a copy of the unlock_code.bin to your pc, so you have it after dooing the froyo ruu.
6. Enter FASTBOOT again on your phone.
7.Open the command prompt again on your pc to where adb.exe is. (ie. C:\android-sdk\platform-tools or C:\adb
8. Download this - CWM recovery 5.0.2.0 http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, and place it in the same folder as fastboot (where you put unlock_code.bin ie. C:\adb).
9. For simplicity’s sake rename the above file to recovery.img if it doesn’t already save it as recovery.img.
10. In your command prompt navigate to the folder containing your fastboot files and recovery.img
11. Enter the following in the command prompt:
Code:
fastboot flash recovery recovery.img
Code:
12. Once that completes navigate to recovery on your phone and press power to select it.
13. Once CWM recovery boots on your phone use the volume up and down to pick "Mounts and storage" press the trackball to select it.
14. Select "Mount usb storage".
15. Take this zip and drag it to the root of your SD card http://dinc.does-it.net/Guide_Root_New_Hboot/su.zip
16. On your phone press the trackball to unmount your usb storage.
17. Select go back.
18. Select install zip from SD card.
19. Choose zip from sd card.
20. Select the su.zip file we just downloaded and press the trackball to flash.
21. Reboot the phone.
22. Once your phone is booted go to the market and search "superuser".
23. Download and install superuser.
24. Search "busybox".
25. Use one of the busybox installers and install busybox (hit allow on the su notification).
26. Enter superuser app, press the menu button on your phone, select preferences, then scroll down to su-binary.
27. Hit update, and allow the prompt, if all the output is in green then you have full root congrats!!!.
For Those who wish to take it one step further and achieve s-off with unrevoked.
This process will format your phone I recommend making a nandroid, and running a program like Titanium Backup along with MyBackup to backup all your apps/data, and sync your contacts to google before you go any further.
28. Reboot your phone, and enable usb debugging.
29. Place these 2 files, unzipped on the root of your SD card. Do not put them in a folder, just drop the files right to your card. http://dinc.does-it.net/Guide_Root_New_Hboot/flash_mtd.zip
30. Set your phone to charge only.
31. Open the command prompt on your PC and navigate to the same folder as your fastboot files in the step above for example: cd c:\android-sdk\platform-tools\ or C:\adb
32. Type the following into the command prompt pressing the enter key at the end of each line:
Code:
adb shell
You should get a dollar sign $
Code:
su
You should now get a pound sign #
Code:
cat /sdcard/flash_image > /data/flash_image
Code:
chmod 755 /data/flash_image
Code:
/data/flash_image misc /sdcard/mtd0.img
33. Now set your phone to disk drive mode and place this zip on the root of your SD card (do not unzip) http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip
34. Rename the above file to PB31IMG
35. Set your phone to charge only
36. At this step you have 2 options you can pull the battery of your phone and put it back in then hold volume down and pres power to enter the bootloader or you can go back to your command prompt and type the following:
Code:
exit
Code:
adb reboot bootloader
37. When your bootloader is done loading press volume up to flash the PB31IMG.zip
38. Your phone will reboot the bootloader once during this process, don’t be alarmed just wait for it to finish, when done it will ask you to press volume up to restart the phone
39. When done remove the PB31IMG file from your sd card
40. Congratulations you are now back to stock 2.2 froyo
41. Put the unlock_code.bin file in the same folder with the fastboote.exe file if its not already there. Go to fastboot on the phone. Open a commant prompt to the folder where the files are.
42. Type the folowing:
Code:
fastboot flash unlocktoken unlock_code.bin
Code:
43. Fastboot flash cwm recovery.img again.
Code:
fastboot flash recovery recovery.img
Code.
44. Flash the su.zip file thru recovery.
45. Flash the unrevoked forever s-off patch thru recovery http://dinc.does-it.net/Guide_Root_New_Hboot/unrevoked-forever.zip
You should now be rooted and s-off.

Reserved

do you know if this method enables fastboot? I never could get fastboot working on my slcd Inc and I don't know if there is an eng hboot that works for it.
Sent from my Galaxy Nexus using Tapatalk

tiny4579 said:
do you know if this method enables fastboot? I never could get fastboot working on my slcd Inc and I don't know if there is an eng hboot that works for it.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?

cmlusco said:
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?
Click to expand...
Click to collapse
is there a reason why update hboot? any thing good come with it?

synisterwolf said:
is there a reason why update hboot? any thing good come with it?
Click to expand...
Click to collapse
No reason to update and is reccomended that you dont. This is just for people who got an inc recently that came with the new hboot.

cmlusco said:
I believe it does. The new hboot is fastboot compatible, it is required to get the info for the unlock code. The 0.92 hboot is also fastboot compatible, i have always been able to use fastboot on it. Is that what you ment?
Click to expand...
Click to collapse
I can use fastboot but I mean commands like fastboot flash and fastboot boot never worked for me. They should as I'm s-off but my conclusion is that the current boot loader doesn't allow fastboot to flash to a device.
I want it mainly to boot a boot.img without having to flash to the boot partition. Good for testing purposes.
Sent from my Galaxy Nexus using Tapatalk

cmlusco said:
No reason to update and is reccomended that you dont. This is just for people who got an inc recently that came with the new hboot.
Click to expand...
Click to collapse
thank you.

tiny4579 said:
I can use fastboot but I mean commands like fastboot flash and fastboot boot never worked for me. They should as I'm s-off but my conclusion is that the current boot loader doesn't allow fastboot to flash to a device.
I want it mainly to boot a boot.img without having to flash to the boot partition. Good for testing purposes.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I know the fastboot flash works for recovery and misc img, not sure about boot. I wrote this thread after helping my cousin root his inc with the new hboot that was ***locked*** (oow) s-on. After doing htc dev unlock, it did allow us to use fasboot to flash the cwm recovery img and the misc partition, and allow him to downgrade to 2.2. Then used unrevoked like normal to get s-off. He is now true s-off while still being on the new hboot. Now it says ***unlocked*** (oow) s-off.

cmlusco said:
I know the fastboot flash works for recovery and misc img, not sure about boot. I wrote this thread after helping my cousin root his inc with the new hboot that was ***locked*** (oow) s-on. After doing htc dev unlock, it did allow us to use fasboot to flash the cwm recovery img and the misc partition, and allow him to downgrade to 2.2. Then used unrevoked like normal to get s-off. He is now true s-off while still being on the new hboot. Now it says ***unlocked*** (oow) s-off.
Click to expand...
Click to collapse
To test you can dump the current boot.img or pull one from a nandroid to your pc and do fastboot flash boot boot.img. I'm just curious if that works for you as I couldn't do it but I might try again this evening.
Sent from my Galaxy Nexus using Tapatalk
Edit: Here is what I tried and it shows that fastboot boot fails for me:
Code:
D:\Users\Andrew\Desktop\droid>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.470s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.480s
D:\Users\Andrew\Desktop\droid>fastboot flash boot boot.img
sending 'boot' (3072 KB)...
OKAY [ 0.470s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.470s
D:\Users\Andrew\Desktop\droid>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)...
OKAY [ 0.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.700s

tiny4579 said:
To test you can dump the current boot.img or pull one from a nandroid to your pc and do fastboot flash boot boot.img. I'm just curious if that works for you as I couldn't do it but I might try again this evening.
Sent from my Galaxy Nexus using Tapatalk
Edit: Here is what I tried and it shows that fastboot boot fails for me:
Code:
D:\Users\Andrew\Desktop\droid>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.470s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.480s
D:\Users\Andrew\Desktop\droid>fastboot flash boot boot.img
sending 'boot' (3072 KB)...
OKAY [ 0.470s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.470s
D:\Users\Andrew\Desktop\droid>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)...
OKAY [ 0.698s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.700s
Click to expand...
Click to collapse
Yeah it does the same thing on mine 0.92 remote not allowed. I will check on my cousins phone next time i see him, and see if the new hboot can do it.

congrats on making it to the portal
http://www.xda-developers.com/android/root-and-s-off-for-the-htc-incredible-with-hboot-1-02-0000/

synisterwolf said:
congrats on making it to the portal
http://www.xda-developers.com/android/root-and-s-off-for-the-htc-incredible-with-hboot-1-02-0000/
Click to expand...
Click to collapse
Holy crap lol. I had no idea, thanks for telling me.

cmlusco said:
Holy crap lol. I had no idea, thanks for telling me.
Click to expand...
Click to collapse
your welcome.

When I try to run unrevoked for root and s-off it fails with Internal error: failed to unlock NAND flash?
I have no idea where to go from here anyone have advice?
Edit: I have run everything else in the guide successfully. I am downgraded to 2.2.

warpurlgis said:
When I try to run unrevoked for root and s-off it fails with Internal error: failed to unlock NAND flash?
I have no idea where to go from here anyone have advice?
Edit: I have run everything else in the guide successfully. I am downgraded to 2.2.
Click to expand...
Click to collapse
What version of unrevoked did you use 3.32, you should use version 3.22 http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe. Also make sure to go to the unrevoked menu and select custom recovery, and use this cwm img http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img before starting the process.

I did use 3.32 first. Then I decided to try 3.22.
I just read your post about using to custom recovery image and I just tried that with 3.22 unsuccessfully with a Failed to flash recovery image.

Can you access recovery, and when booted do you have root?

I can access the HTC recovery if that is what you mean. I lost root when I did the downgrade from 2.3.4 to 2.2

warpurlgis said:
I can access the HTC recovery if that is what you mean. I lost root when I did the downgrade from 2.3.4 to 2.2
Click to expand...
Click to collapse
Try flashing cwm with fastboot like in step 11. Then if you can access it flash the su binary, boot, install su app and busybox, and then try unrevoked again.