Related
hey guys, read a lot, complicated root procedure, found this one:
1. install droid explorer (google yourself)
2. get amon recovery image, put into c:\program files\droid explorer\sdk\tools
3. fastboot (hold back + power), cmd: fastboot boot recovery.img
4. then run these
adb shell
mount /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Done
why so much hassle
*also, you dont have to get root to flash custom rom, just fastboot with amon and flash any rom you like.
Get root is kind of like jailbreak concept in iphone
Will this work for the My Touch 1.2 though? What if you are having problems even getting the damn SDK crap to work on your computer system? That **** is driving me nuts!
Hrrm not newb but feel like one now
I tried this,
I installed Droid Exolorer, it sees my 32A
I downloaded the recovery img
I fastbooted (power + back) now it shows this white screen with
----
PVT SHIP S-ON H
HBOOT-1.76.0010 (SAPP50000)
CPLD-12
RADIO-6.35.10.10
Jan 14 2010,00:14:50
FASTBOOT USB (in red)
<VOL DOWN> HBOOT MODE
<SEND> Reset device
<ACTION> Restart to HBOOT mode
<MENU> Power Down
----
From pc cmd window, in /tools dir, I type fastboot boot recovery.img and I get an error,
---
C:\Program Files\Droid Explorer\SDK\tools>fastboot boot recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
finished. total time: 0.002s
---
recovery.img is recovery-ra-hero-v1.6.2.img renamed (as recommended for 32A and spl 1.76)
What next?
Thanks
Cheers
pw
FASTBOOT USB
Hi, I'm a noob. I've been reading through this site lately and thought I'd finally jump in and try to root. but I am having the same error as pdawookie here.
I did some searching and this method is useless for us users with perfect SPL as told in this thread (since I'm new it won't let me paste an url, but look up "showthread.php?t=529167") looks like it won't work for us US mytouch owners since it doesn't allow fastboot over USB.
BTW, I have a mytouch 3g 1.2 with the 3.5mm headphone jack.
@pdawookie:
I think you get the fastboot error remote not allow because you have an SPL that doesn't allow it. I get the same thing too, and I have HBOOT 1.33.0007. I read about ways to hack the perfect SPL but none of it worked for me
Right. This will only work if you have an engineering SPL with S-OFF.
Use other rooting methods, they're available here and on the unlockr site.
@MRCLrider: You can't root your phone without the android SDK installed. Sorry.
I've get MAgic 32A with issues..
First off all my keys is remaped(search, home, menu, back instead of home,menu,back,search).
i tryed from http://forum.xda-developers.com/showthread.php?t=671600
and when i type
fastboot oem readsku
i've got
c:\android-sdk-windows\tools>fastboot oem readsku
... INFO[ERR] Command error !!!
OKAY [ 0.004s]
finished. total time: 0.005s
c:\android-sdk-windows\tools>
When i go to fastbooti get
saphire unknown 32A ship s-on h
hboot-1.76.0008 (sapp10000)
cpld-12
radio-6.35.08.29
I try to flash RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe
but when ruu try to go in bootloader magic stuck ...
I think i have 1.5 android on it. when i press trackball magick stuck..
Please help, i dont know what to do
Thanks
Root HTC Magic
A lot of people have been looking for a way to root their HTC Magic which has been updated by the Sense UI RUU provided by HTC (RUU 3.05.***) The roms that can be rooted are listed below.
1) 3.05.861.2 1.76.0008H 6.35.08.29 N (Australia)
2) 3.05.631.7 1.76.0010H 6.35.10.18 N (Canada)
3) 3.05.401.3 1.76.0009H 6.35.08.29 N (Europe)
4) 3.05.720.3 1.76.0009H 6.35.08.29 N (India)
To root the Magic follow the steps listed below:
1. Download the test signed rom from the following link
http://www.multiupload.com/XQEH9NVGY7
2. If your HTC Magic is from Australia, Canada or India, you need to create a gold card to install this RUU Update. In order to do this, follow the step on the website linked below:
http://theunlockr.com/2010/03/10/how...te-a-goldcard/
3. After successfully creating the gold card, update your phone via the downloaded RUU with the gold card inserted in your phone.
4. When your phone has been updated, go to the link below and download the latest HERO recovery. (Save it to tools in Android SDK folder downloaded while creating the gold card)
http://forum.xda-developers.com/showthread.php?t=530492
5. Now in your phone go to settings>development and check USB debugging.
6. Open command prompt and go to the Tools folder in Android SDK that you downloaded to create the gold card.
Assuming that you have not changed the file name of the recovery, use the following commands:
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img (file name of the recovery you downloaded)
7. After the recovery has been flashed, go to the following link to download the ENG SPL for HTC MAGIC 32A (SPL: 1.76.2007)
http://www.4shared.com/file/21114537...07-signed.html
8. Now copy the SPL to your memory card.
9. Restart your phone using the home + power key till it boots up into the recovery mode.
(or just type 'adb shell reboot recovery')
10. Using the 'Flash zip file' option from the recovery, select the SPL file from the memory card and flash the HBOOT on your phone.
11. Congrats, your HTC Magic is now ROOTED!!
Try this to root your magic (Aj probaj to da mu odradis root)
I can't update ruu
when start ruu, all is ok. next, next. and when phone try to go in bootloader i've got just black screen and ruu can not see my magic anymore..
Anyone?
10 char
I've menaged to do
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
but i can't reboot in to recovery
Maybee because my keys is remaped ...
Any 1 help me to put engineering spl whitout go to recovery?
Maybe with fastboot comands?
I need this spl because i'cant remape keys without him
on this threed http://forum.xda-developers.com/showthread.php?t=671600
said this.
Thanks
Wrong section. I'll move to General for you so that you can get the help that you need.
liderzre said:
I've menaged to do
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
but i can't reboot in to recovery
Maybee because my keys is remaped ...
Any 1 help me to put engineering spl whitout go to recovery?
Maybe with fastboot comands?
I need this spl because i'cant remape keys without him
on this threed http://forum.xda-developers.com/showthread.php?t=671600
said this.
Thanks
Click to expand...
Click to collapse
Execute this from the shell and you should be in recovery.
Code:
su
reboot recovery
mumilover said:
Execute this from the shell and you should be in recovery.
Code:
su
reboot recovery
Click to expand...
Click to collapse
Nothing
Reboot, but i've only got black screen
So sad
Maybee this phone is 32B? (with 32A spl or so...?)
How can i check this?
Thanks
Power down.
Hold volume - ("-" and not +) together with power.
You should see fastboot screen.
Post here all the info. ALL!
mumilover said:
Power down.
Hold volume - ("-" and not +) together with power.
You should see fastboot screen.
Post here all the info. ALL!
Click to expand...
Click to collapse
I have posted in 1st post but here is again:
saphire unknown 32A ship s-on h
hboot-1.76.0008 (sapp10000)
cpld-12
radio-6.35.08.29
Nov 3 2009,15:56:29
HBOOT
<Back> FastBoot Mode
<Send> Simlock
To make attention: that my back key is search key, and when i press action key phone block , when i press back(search) i get:
FASTBOOT
<VOL DOWN> Hboot mode
<SEND> REset Device
<ACTION> Restart to hboot
<MENU> Power Down
Thanks
Any ideas...please.
Recycle bin?
Sorry, did not see that you already posted your fastboot info, but you did ask how to get to fastboot screen :0)
liderzre said:
Any ideas...please.
Recycle bin?
Click to expand...
Click to collapse
No, you device is all ok.
We just have to fix some things.
liderzre said:
I've menaged to do
cd C:\AndroidSDk\tools
adb push recovery-RA-hero-v1.6.2.img /sdcard/
adb shell
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
but i can't reboot in to recovery
Maybee because my keys is remaped ...
Any 1 help me to put engineering spl whitout go to recovery?
Maybe with fastboot comands?
I need this spl because i'cant remape keys without him
on this threed http://forum.xda-developers.com/showthread.php?t=671600
said this.
Thanks
Click to expand...
Click to collapse
You just have to combine the recovery flash with the "reboot recovery" command and you should be good to go.
You could also make a dump of what you see in the command shell when you execute the commands, so we can follow the progress all the way, and maybe identify what's going wrong!
If all goes wrong, we can still fix it.
Execute this from fastboot mode and post back the results
Code:
fastboot getvar version-main
fastboot getvar cid
mumilover said:
Sorry, did not see that you already posted your fastboot info, but you did ask how to get to fastboot screen :0)
No, you device is all ok.
We just have to fix some things.
You just have to combine the recovery flash with the "reboot recovery" command and you should be good to go.
You could also make a dump of what you see in the command shell when you execute the commands, so we can follow the progress all the way, and maybe identify what's going wrong!
If all goes wrong, we can still fix it.
Execute this from fastboot mode and post back the results
Code:
fastboot getvar version-main
fastboot getvar cid
Click to expand...
Click to collapse
ok.
Here it si:
c:\Program Files (x86)\Android\android-sdk-windows\tools>fastboot getvar version
-main
version-main: 3.05.401.1
finished. total time: 0.002s
c:\Program Files (x86)\Android\android-sdk-windows\tools>fastboot getvar cid
cid: 11111111P≈│m
finished. total time: -0.000s
c:\Program Files (x86)\Android\android-sdk-windows\tools>
Execute this from fastboot mode and post back the results
Code:
fastboot getvar cidnum
Did you try to flash the recovery again ending in "reboot recovery"?
mumilover said:
Execute this from fastboot mode and post back the results
Code:
fastboot getvar cidnum
Did you try to flash the recovery again ending in "reboot recovery"?
Click to expand...
Click to collapse
ok
c:\Program Files (x86)\Android\android-sdk-windows\tools>fastboot getvar cidnum
cidnum: 11111111P≈│m
finished. total time: 0.001s
c:\Program Files (x86)\Android\android-sdk-windows\tools>
Yes i try. But same thing.
Flashing recovery is ok (no error report), but i cant go into recovery (i try everything)
I think that my bootloader is broken, and i dont know why in the first line of fastboot screeen said SAPPHIRE UNKNOWN ???
read your pm
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.
My Hero come from service center clean and updated to latest RUU so i trying to get custom bootloader.
First i try to downgrade Hero to 2.73.405. But on my computer with Win7 fails with error 171. Then i tried on friend machine with Win XP and there i got error 140. I tried RUU from xda ftp and one from HTC and after this fails i tried other RUU from xda ftp. (i created and have gold card)
After that i try different approach. I rooted Hero using one click apk and then use latest flashrec. Flashrec gives me error "Flash FAILED: Could not run command."
After that i tray this:
Code:
C:\and\platform-tools>adb shell reboot bootloader
C:\and\platform-tools>fastboot boot rec.img
and i got this error
Code:
downloading 'boot.img'... FAILED (remote: not allow) finished. total time: 0.000s
if i try
Code:
C:\and\platform-tools>fastboot flash recovery rec.img
sending 'recovery' (3972 KB)... FAILED (remote: not allow) finished. total time: 0.000s
I maybe do i very very stupid thing and extracted flash_image from some Hero ROM and using cat put it in /system/bin/
I am desperate and i don’t know what to do next.
Hero:
3.36.405.1
HBOOT 1.76.0007 (HERO 1000)
Radio 6.35.15.11
try this
run cmd
cd C:\and\platform-tools>
fastboot boot rec.img
i am not sure about it
Try place recovery on your SD card, name it recovery img. Then run via terminal or adb:
su
flash_image recovery /recovery.img
reboot recovery
Press enter after each line
sent with love from me to you
Habarug said:
Try place recovery on your SD card, name it recovery img. Then run via terminal or adb:
su
flash_image recovery /recovery.img
reboot recovery
Press enter after each line
sent with love from me to you
Click to expand...
Click to collapse
It says ran out of memory :/ It's very annoying I've had the same problems as op and still can't do it.
Did you use goldcard to downgrade? AFAIK all bootloaders from 1.5 were locked down. Is error 140 mismatched. CID? If it is, you need a goldcard.
EDIT: just noticed you said you made a goldcard. Are you sure it stuck? Some sdcards aren't suitable for being a goldcard.
Sent from my GT-I9100 using XDA App
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.