CAUTION!! By upgrading HBOOT to 1.00+ you loose the ability to S-OFF your Legend!!!
Preface
Because there are too many ppl without any knowledge spreading false findings and statements I decided to write this HOWTO.
Audience
This HOWTO is primarily ment for those who already have rooted Legends but they recently experienced problems flashing CM's or new Vodafone FroYo boot.img.
Background
HBOOT is like a BIOS in our PCs and to cut a long story short it also contains partition table for phone's internal storage. That means it has info on where exactly certain partition starts and how big it is.
At HTC they decided to partition Legend's internal storage this way:
misc 640 kB
recovery 4,375 MB
boot 2,5 MB
system 240 MB
cache 40 MB
data 185 MB
...but as we found out (first with CM nightly) boot partition was a little short for the boot.img to fit in if we had one or more bad cells (sectors) on it. Eventually we found out that quite some Legend's had bad cell on boot partition and those unfortunate souls that owned such phone were unable to upgrade to Vodafone FroYo rooted ROM too.
I think that HTC also recognized that Legend's boot partition was kinda small so they rearanged partition table in HBOOT 1.00 a bit making boot partition bigger (now it is 3 MB) by shrinking recovery partition a little.
So now we know that some of us actually need HBOOT 1.00 in order to flash FroYo's boot.img without a problem. But how do we keep root then?
Prerequirements
Android SDK (primarily adb)
working USB drivers (for adb to work)
goldcard (in case you are trying to flash ROMs with different CID than your phone has)
ClockWorkMod recovery (if your Legend is already rooted)
Rerequirements
Vodafone FroYo OTA update (actually just firmware.zip from OTA)
Legend rooting tools (just testimage.zip)
Hack 4 Legend v5(just misc1-2.img and flash_image)
VISIONary r13(r14 is out also but i haven't tested it yet)
Instructions
I will split instructions into two parts... for already rooted phones and phones that were already updated with Vodafone OTA thus they lost root.
Already OTA updated with HBOOT 1.00
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Unzip r4-legend-root.zip and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip. You can then reboot into bootloader issuing:
Code:
adb reboot bootloader
...from command prompt. Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard. Make your sdcard gold and try again. After successful flash and reboot you may remove LEGEIMG.zip from sdcard. Next step is upgrading of rooted FroYo ROM. Put FroYo update ROM zip to your sdcard and install it via ClockworkMod recovery. You may also flash backed up misc partition after that. Still in recovery mode and hooked with your PC switch to command prompt and restore it back:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Rooted Eclair Voda FroYo or CM with HBOOT 0.43
Since you have already rooted phone we can prepare everything before we start. Hook your phone to your PC. Put FroYo ROM update zip to phone's sdcard. Put also misc1-2.img and flash_image from hack4legend-v5.zip and testimage.zip from r4-legend-root there. Extract Vodafone FroYo OTA and put firmware.zip to your phone's sdcard renaming it to LEGEIMG.zip. Reboot into bootloader from command prompt:
Code:
adb reboot bootloader
...bootloader will find LEGEIMG.zip extract it into RAM and check its integrity. If you get CID error at this point you don't have gold card. Make your sdcard gold and retry the procedure.
After successfull flashing of LEGEIMG.zip (firmware.zip from FroYo OTA) you have HBOOT 1.00, new (unrooted) recovery, new (unrooted) boot but old and intact system with superuser.apk and su. Reboot. When system is available, tick "USB debugging" in Settings->Applications->Development. After that you will be able to adb shell into your phone. Fire up some command prompt and issue:
Code:
adb shell
su
...while phone screen is still on. Superuser will pop-up. Grant it. Now make a backup of misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
...now copy flash_image from sdcard to internal storage, change its permissions, and flash misc1-2.img:
Code:
cp /sdcard/flash_image /data/local/
chmod 755 /data/local/flash_image
/data/local/flash_image misc /sdcard/misc1-2.img
...rename LEGEIMG.zip to firmware.zip and testimage.zip to LEGEIMG.zip:
Code:
mv /sdcard/LEGEIMG.zip /sdcard/firmware.zip
mv /sdcard/testimage.zip /sdcard/LEGEIMG.zip
...exit from adb shell and reboot into bootloader:
Code:
exit
adb reboot bootloader
Phone will reboot, find LEGEIMG.zip and flash it over. You will end up with HBOOT 1.00 and downgraded and rooted recovery. Boot into ClockworkMod recovery and flash Voda FroYo custom update of your choice from your sdcard. You may also want to restore backed up misc partition after updating is done:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Goldcard (no remove, no format, no data loss)
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .
BlaY0 said:
Reserved...
Click to expand...
Click to collapse
awosome , I think you must have found some method to crack the SPL? just as desire do ?
waiting
There's actually no cracking of SPL involved...
Hi blay0,
I follow your link to vodafone ota update and appoint me to the website, where is the the link to download it?
Thanks.
Sent from my HTC Legend using Tapatalk
BesFen said:
Hi blay0,
EDITED: I got it, thanks
Click to expand...
Click to collapse
THX
@blay0:
thanks you are great developer.
so if you could temproot automated so you could build pc software to root legend with one click automatically like as wildfire desire ......
thx again
Hmm, I don't understand what are you trying to say???
Sent from my HTC Legend
BlaY0 said:
Hmm, I don't understand what are you trying to say???
Sent from my HTC Legend
Click to expand...
Click to collapse
in htc wildfire rooting process will do Unrevoked 3 for Wildfire
is it possible to automated above process?
VISIONary has an option to "temproot" on every boot.
But I don't see why you would do that if you can root the way I described.
Sent from my HTC Legend
Thanks Blayo ...
@ Blayo
I have some doubts regarding OTAs .. Please check your PM
The primary use of OTA here is just to extract firmware.zip flashing it to upgrade HBOOT. This is not HOWTO for updating the whole system via OTAs.
Sent from my HTC Legend
After flashing firmware.zip, the phone wont boot. Stuck at the HTC logo. What should I do?
Hey guys , im really troubled gettin permission denied on push.
any suggjestions? googled loads of it but nothing related to my issue
Edit: i got root tru visionary yes , it aply's well and su promts for permission so i guess i got root
so was wondering why i keep gettin permission denied on any command in adb
Second EDIT : Nevermind total noobness , forgot i cant push within adb shell.
Hats off to BlaY0 for another amazing work.
rajasyaitan said:
Hats off to BlaY0 for another amazing work.
Click to expand...
Click to collapse
Yes indeed m8 , thanks for your efforts!
Finaly unlocked the Hboot 1.00 running rooted ota froyo
/bow 2 BlaYo.
You're awesome.
Amazing, thanx a million!!
Keeps the Legend running smoothly with custom Froyo Modaco rom.................
I used this guide after my downgrade to Rom 1.31 with HBoot 1.00 and it worked like a charm ! Thank you !
wow You're awesome
Related
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
yvesg said:
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
Click to expand...
Click to collapse
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
yvesg said:
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Click to expand...
Click to collapse
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
lucky 69 said:
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
Click to expand...
Click to collapse
I ashamed, but I didn't do the backup :-( .....
yvesg said:
I ashamed, but I didn't do the backup :-( .....
Click to expand...
Click to collapse
Try what Harry wrote.
harry_m said:
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
Click to expand...
Click to collapse
Hi,
Thanks a lot.
I'm now able to get root access and I'm about to flash the G1.
I thaught I replaced the SPL, but I'm not sure .... I've tried so much things since I have this phone (since last sunday) .....
Again, thank you for your help.
Yves
ooops,
"Installation aborted", during the apply of update.zip.
Now the phone is bricked.
I'm going to format my sdcard and retry the flash ....
Same error :
(No such file or directory)
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
Installation aborted.
redownload the rom
Spon4ik said:
redownload the rom
Click to expand...
Click to collapse
Meanwhile, I try with another rom and it seems to work ....
Thanks again for your help.
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
If you ask me ... the above mentioned error
Code:
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
has nothing to do with a wrong-signed rom!
SPL
yvesg said:
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
Click to expand...
Click to collapse
would this have to do with the SPL? similar to not being able to flash a EUR ROM on a USA phone .. you have to flash the HardSPL etc in order to switch ROMs
Or you could just gain root access manually the way those of us who had RC30 did...
You are may be right about the HardSPL.
When I try to flash it, (with Camera + Power), I get "not allow".
Ok so I am in a serious situation here... I have been using my nexus one (STOCK) for few months now and i love the phone right..I am new to the android interface but I reaallly am tempted on getting my phone rooted...btw its running on froyo 2.2, FRF91, Mod 6.0.0-N1-RC3.
Here is the problem... the more I research into it the more I'm getting confused for some reason...
Is there any one who can just go thru the steps I need to get it all done please.
for example: what should i be doing first, root, bootloader unlock, nandroid backup, rom install, mod install.....and so on? just need a little overview on everything once...
also as i have the mod 6.0.0, does it need to be upgraded to some other version or does it need to be flashed?!
please help me on this as I will seriously pray for your long life !
AK
There are loads of guides on here already:
http://forum.xda-developers.com/showthread.php?t=705460
Or even googling nexus one root steps gave plenty of guides:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
- First step : Root...
If root is the only thing you want, then you're finished.
If you want to flash alternate ROM's, then:
- Flash alternate recovery(Amon_RA or Clockwork)
- Do a nandroid backup(is just a backup from your current ROM, so you can go back if the next step fails)
- Flash a ROM.
You don't have to unlock the bootloader.
Guides for the above you can find in the Nexus Forums.
How do I get those crazy animations at the startup? don't I need to unlock the boot loader for that??
How do i get those crazy animations at the startup, would i need to unlock the bootloader for that ??
Just curious, but can you type the full mod version again, because that looks extremely like a Cyanogen mod...?
Sent from my Nexus One using XDA App
YoMarK said:
- First step : Root...
If root is the only thing you want, then you're finished.
If you want to flash alternate ROM's, then:
- Flash alternate recovery(Amon_RA or Clockwork)
- Do a nandroid backup(is just a backup from your current ROM, so you can go back if the next step fails)
- Flash a ROM.
You don't have to unlock the bootloader.
Guides for the above you can find in the Nexus Forums.
Click to expand...
Click to collapse
You have made me extremely curious with your statement:
You don't have to unlock the bootloader.
I am contemplating partitioning my SD card so that I can take advantage of "Apps2SD". My phone is rooted w/ Froyo 2.2.1 FRG83D, but I haven't proceeded with flashing the Cyanogen recovery image because I was under the impression that unlocking bootloader is a requirement.
If it is possible to flash a recovery image and/or a custom ROM without unlocking bootloader, why bother unlocking bootloader?
Yes I'll admit, I'm a NEWBIE.
Master N1 said:
You have made me extremely curious with your statement:
You don't have to unlock the bootloader.
I am contemplating partitioning my SD card so that I can take advantage of "Apps2SD". My phone is rooted w/ Froyo 2.2.1 FRG83D, but I haven't proceeded with flashing the Cyanogen recovery image because I was under the impression that unlocking bootloader is a requirement.
If it is possible to flash a recovery image and/or a custom ROM without unlocking bootloader, why bother unlocking bootloader?
Yes I'll admit, I'm a NEWBIE.
Click to expand...
Click to collapse
Unlocking a bootloader makes it a lot easier to flash stuff. And some people had their bootloader unlocked because there were no ways to actually flash without unlocking before...now, new techniques appeared and you can do it without.
gravufo said:
Unlocking a bootloader makes it a lot easier to flash stuff. And some people had their bootloader unlocked because there were no ways to actually flash without unlocking before...now, new techniques appeared and you can do it without.
Click to expand...
Click to collapse
Would utilizing ROM Manager (Flash ClockworkMOD Recovery) be one of those new techniques?
I'd like to partition my SD card just in case I decide to take advantage of "Apps2SD (or similar)" in the future. In doing so a recovery image is required, but would like to avoid unlocking bootloader at this stage.
BTW, would you happen to know if the suggested SD partitions are still the same?
32 MB linux-swap partition
512 MB ext2 partition and
remaining free space as a fat32 partition
Master N1 said:
Would utilizing ROM Manager (Flash ClockworkMOD Recovery) be one of those new techniques?
I'd like to partition my SD card just in case I decide to take advantage of "Apps2SD (or similar)" in the future. In doing so a recovery image is required, but would like to avoid unlocking bootloader at this stage.
BTW, would you happen to know if the suggested SD partitions are still the same?
32 MB linux-swap partition
512 MB ext2 partition and
remaining free space as a fat32 partition
Click to expand...
Click to collapse
First, a custom recovery (such as ClockworkMod and Amon_Ra) are the result of either unlocking the bootloader or using adb.
Basically, with ADB, you need to be rooted and then download a custom recovery of your choice as well as flash_image onto the root of your sdcard (i.e. in no folders) and run the following commands:
NOTE: These commands will assume that you renamed the recovery image to recovery.img instead of whatever name was there before. It will also assume you have the android SDK w/ adb + usb drivers installed as well as checked the USB Debugging setting under Settings > Applications > Development in your Nexus
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
As for your a2sd, the values look correct to me but I am no expert in partitioning optimally, wait for some linux guru to help you in there
gravufo said:
First, a custom recovery (such as ClockworkMod and Amon_Ra) are the result of either unlocking the bootloader or using adb.
Basically, with ADB, you need to be rooted and then download a custom recovery of your choice as well as flash_image onto the root of your sdcard (i.e. in no folders) and run the following commands:
NOTE: These commands will assume that you renamed the recovery image to recovery.img instead of whatever name was there before. It will also assume you have the android SDK w/ adb + usb drivers installed as well as checked the USB Debugging setting under Settings > Applications > Development in your Nexus
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
As for your a2sd, the values look correct to me but I am no expert in partitioning optimally, wait for some linux guru to help you in there
Click to expand...
Click to collapse
Thanks so much for your feedback.
To answer your earlier question.
Yes - you can also install a custom recovery via ROM Manager.
Sent from my Nexus One using XDA App
Ok guys I noticed a lot of people are getting stuck with this myself included and for me it was because the information I needed was fragmented all over the place, So here is all the information that I used some parts have been edited to fit the purpose of rooting 1.01 as there is no definative guide at the minute.
1st thing to do is make a goldcard even if you already have a working goldcard make it again mine was working for other phones but wouldnt work for this.
All credit for the goldcard guide goes to BlaY0
BlaY0 said:
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .
Click to expand...
Click to collapse
The 2nd guide you will need to use is also by BlaY0
BlaY0 said:
Preface
Because there are too many ppl without any knowledge spreading false findings and statements I decided to write this HOWTO.
Audience
This HOWTO is primarily ment for those who already have rooted Legends but they recently experienced problems flashing CM's or new Vodafone FroYo boot.img.
Background
HBOOT is like a BIOS in our PCs and to cut a long story short it also contains partition table for phone's internal storage. That means it has info on where exactly certain partition starts and how big it is.
At HTC they decided to partition Legend's internal storage this way:
misc 640 kB
recovery 4,375 MB
boot 2,5 MB
system 240 MB
cache 40 MB
data 185 MB
...but as we found out (first with CM nightly) boot partition was a little short for the boot.img to fit in if we had one or more bad cells (sectors) on it. Eventually we found out that quite some Legend's had bad cell on boot partition and those unfortunate souls that owned such phone were unable to upgrade to Vodafone FroYo rooted ROM too.
I think that HTC also recognized that Legend's boot partition was kinda small so they rearanged partition table in HBOOT 1.00 a bit making boot partition bigger (now it is 3 MB) by shrinking recovery partition a little.
So now we know that some of us actually need HBOOT 1.00 in order to flash FroYo's boot.img without a problem. But how do we keep root then?
Prerequirements
Android SDK (primarily adb)
working USB drivers (for adb to work)
goldcard (in case you are trying to flash ROMs with different CID than your phone has)
ClockWorkMod recovery (if your Legend is already rooted)
Rerequirements
Vodafone FroYo OTA update (actually just firmware.zip from OTA)
Legend rooting tools (just testimage.zip)
Hack 4 Legend v5(just misc1-2.img and flash_image)
VISIONary r13(r14 is out also but i haven't tested it yet)
Instructions
I will split instructions into two parts... for already rooted phones and phones that were already updated with Vodafone OTA thus they lost root.
Already OTA updated with HBOOT 1.00
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Unzip r4-legend-root.zip and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip. You can then reboot into bootloader issuing:
Code:
adb reboot bootloader
...from command prompt. Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard. Make your sdcard gold and try again. After successful flash and reboot you may remove LEGEIMG.zip from sdcard. Next step is upgrading of rooted FroYo ROM. Put FroYo update ROM zip to your sdcard and install it via ClockworkMod recovery. You may also flash backed up misc partition after that. Still in recovery mode and hooked with your PC switch to command prompt and restore it back:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Click to expand...
Click to collapse
So by now you will be on an unrooted Eclair rom. The third guide I used was by David Cogen
David Cogen said:
I. Before You Begin
1. YOU MUST BE ON VERSION 1.31 IN ORDER TO ROOT THE LEGEND, IF YOU ARE NOT YOU CAN DOWNGRADE USING THIS PROCEDURE.
2. This will erase all the data on your phone so please at least sync your contacts with Google before continuing.
3. You must have HTC Sync version 2.0.33, not a newer version. Uninstall HTC Sync and install this version instead.
1. Download the Rooting Tools
Legend Rooting Tools
2. Unzip them to the C: drive on your computer (so the file path is C:\r4-legend-root\)
3. Turn off your phone and turn it back on by holding down Back and Power until you see Fastboot come up on the screen. Push the Power button while highlighting Fastboot on the phone and Fastboot should show up in red now on the phone (if it doesn’t push Power again until it does).
4. Plug the phone in via USB cable to the computer.
5. Open the folder you extracted to the C drive and double click “step1-windows.bat” and wait for it to finish.
6. Once you see the menu on the phone come back up, navigate to BOOTLOADER and push power, then navigate to RECOVERY using the volume buttons to navigate and the power button to select and the phone should boot to the ! screen.
7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish. (UPDATE 12.13.10 – You MUST have HTC Sync version 2.0.33 not a newer version for step2 to work. Please uninstall HTC Sync and download and install this version instead, unplug then plug your phone back in, then rerun step2-windows.bat).
8. Now you should see a custom recovery screen, using the optical trackpad navigate to Wipe and push on the trackpad to select it. Then navigate to Wipe data/factory reset and select that.
9. Once that is done, push volume down to go back to the main menu and select Flash zip from sdcard and select the rootedupdate.zip file and wait for it to flash. All done, you have root access and can use any root required app! Enjoy!
IV. Load a Custom ROM etc (Optional)
1. Head over to our How To Load a Custom ROM on the HTC Legend procedure and continue with that to load custom ROMs and other fun stuff!
Thanks to Paul at Modaco for his awesome scripts!
Click to expand...
Click to collapse
By now you should have HBOOT 1.01 with a rooted Ecclair ROM and Clockwork Recovery Mod So you can flash any custom rom that you like although I would recommend you try B 0.2
If you use this guide, you do so at your own risk.
wow...nice tutorial
I've requested that this goes in the stickies. Well done mate
FeaRThiS said:
The 2nd guide you will need to use is also by http://forum.xda-developers.com/member.php?u=609649
So by now you will be on an unrooted Eclair rom.
Click to expand...
Click to collapse
Question: So the second guide is to downgrade Froyo 3.5 to Eclair 1.3?
smartsreenath said:
wow...nice tutorial
Click to expand...
Click to collapse
Thanks glad it helped.
TheGrammarFreak said:
I've requested that this goes in the stickies. Well done mate
Click to expand...
Click to collapse
Cheers m8 Might not be the best way but it was the only way I managed to root mine on 1.01.
nxdu said:
Question: So the second guide is to downgrade Froyo 3.5 to Eclair 1.3?
Click to expand...
Click to collapse
Fist FroYo is 2.2 not 3.5 and Eclair is 2.1 not 1.3 but yes it is to downgrade to Eclair so that you can root and then upgrade back to FroYo so you end up with rooted FroYo.
FeaRThiS said:
Fist FroYo is 2.2 not 3.5 and Eclair is 2.1 not 1.3 but yes it is to downgrade to Eclair so that you can root and then upgrade back to FroYo so you end up with rooted FroYo.
Click to expand...
Click to collapse
FroYo is HTC WWE 3.x, and éclair is 1.x and 2.x
Thank you!, so it doesn't matter which version of Froyo you're on but what the Hboot version of your phone is on that varies what guide you'll be using ? mine is asia's 3.15.707.3
Yes , one last thing;o how do I check whether all my contacts are properly syncd with Google ? As gmail does not display any of my contacts, if so how would I go about doing it ?._.
Sent from my HTC Legend using XDA App
TheGrammarFreak said:
FroYo is HTC WWE 3.x, and éclair is 1.x and 2.x
Click to expand...
Click to collapse
Ahh I was talkin Android version not HTC version more confusion.
Sent from my HTC Legend using XDA App
FeaRThiS said:
You will be doing this from command prompt:
Code:
adb shell
su
Click to expand...
Click to collapse
Creating a goldcard procedure
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem? sorry._. new to this
Hi Folks,
If you don't mind me asking, do you reckon this will work for HTC Wildfire running 2.2 RUU from shipped ROMs with Hboot of 1.01? TIA.
First I was like... but then I was like
Hey Guys,
I hope someone can help me. I followed some tutorials about rooting the HTC Legend. I followed some steps but when I had to downgrade my HTC Legend it went wrong, whatever I try every methode keeps saying, permission denied. And when I use the RUU Bootloader it says some kind of error:S I really want my Legend to get rooted! Can anyone help me?
Kind Regards Tom
After rebooting the bootloader in the second guide, it can't find LEGEIMG.zip. It says image is wrong. I have the LEGEIMG.zip in goldcard root. please help!
haha123 said:
After rebooting the bootloader in the second guide, it can't find LEGEIMG.zip. It says image is wrong. I have the LEGEIMG.zip in goldcard root. please help!
Click to expand...
Click to collapse
Format your SD card in a card reader, as FAT32, then create the Goldcard as described in the first post in this thread.
Make sure you get a NEW goldcard.img as Blay0 describes in the quoted post, my old Goldcard image I used with the 2.1-update1 no longer worked and I needed to get a new one. I think the CID changed when upgrading to 2.2.
This was my problem and doing what I described above solved my problem.
TheLegendaryJay said:
Format your SD card in a card reader, as FAT32, then create the Goldcard as described in the first post in this thread.
Make sure you get a NEW goldcard.img as Blay0 describes in the quoted post, my old Goldcard image I used with the 2.1-update1 no longer worked and I needed to get a new one. I think the CID changed when upgrading to 2.2.
This was my problem and doing what I described above solved my problem.
Click to expand...
Click to collapse
What about this?:
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem?
justcookiesncream said:
What about this?:
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem?
Click to expand...
Click to collapse
you could try visionary r14 but r13 worked fine for me and many others.
Is this safe?
(or safe as it can be?)
I was previously rooted, but then the microphone on my handset broke, and I replaced it under warranty.
I now have a new handset, but it's back to the stock Vodafone UK Froyo build, with HBOOT 1.0
I'm really liking the look of Blay0's ROM, but fearful of breaking the phone...
brypie said:
Is this safe?
(or safe as it can be?)
I was previously rooted, but then the microphone on my handset broke, and I replaced it under warranty.
I now have a new handset, but it's back to the stock Vodafone UK Froyo build, with HBOOT 1.0
I'm really liking the look of Blay0's ROM, but fearful of breaking the phone...
Click to expand...
Click to collapse
I would say its as safe as it can be and BlaY0's rom is amazin 1500+ score on quadrant with data2ext
I have personally used this method to root my phone without any problems but if you are on hboot 1.00 there may be a easier/safer way of rooting but I am unsure about that.
Trying it now...
In the 2nd guide, I can't crete the misc_backup.img --> "read-only file system".
Is this the S-ON / S-OFF thing?
How can I get around this?
Thanks.
brypie said:
Trying it now...
In the 2nd guide, I can't crete the misc_backup.img --> "read-only file system".
Is this the S-ON / S-OFF thing?
How can I get around this?
Thanks.
Click to expand...
Click to collapse
Nothing to do with s-on looks like you dont have root when you type su in adb do you get a # ?
FeaRThiS said:
Nothing to do with s-on looks like you dont have root when you type su in adb do you get a # ?
Click to expand...
Click to collapse
Yep - tempRoot using Visionary
EDIT - just figured it out - I still had the SD Card connected as a disk drive to my PC D'oh!
Yes, I'm a noob
so I got my Moto XOOM and rooted it with adb and flashed a new kernel and installed ROM Manager and got a new recovery in it and all that and it was smooth as butter. I'm not a fan of ROMs but the kernel does make a huge difference already. Now, I did that as soon as I took the XOOM outta the box so I had no data to lose when rooting...
I've had my N1 for about a year now, been using 1-click root exploits because I didn't feel like starting over and losing all data even though I can have backups I know... but just putting the settings back, losing high scores in games, etc... is annoying enough.
But I'm starting to think now's the time.
So:
1) Best backup solution to not lose anything? My last titanium backup is from about two month ago when I lost root after the Gingerbread OTA
2) does it still stay rooted now with gingerbread? basically adb --> fastboot oem unlock and that's it?
3) I've read the wiki and it's great but not "omg I'm such a noob" proof... so the steps:
- I backup my stuff
- Reboot in recovery
- from my PC, run the command in adb --> fastboot oem unlock
- yes
- my nexus one is now unlocked, rooted but is back to factory...
after that, get the 2.3.3 update zip file from XDA and flash that. flash a new kernel via kernel manager (which one you guys recommend for speed and stability without all the fuss?)
that's it, finito?
thanks if you respond!
A - there are exploits available for Gingerbread, so you don't need to unlock the bootloader (though don't let that stop you)...
http://forum.xda-developers.com/showpost.php?p=13090966&postcount=67
B - unlocking the bootloader doesn't give you root. You also have to install a custom recovery and flash the su zip to gain root...
C - flashing an update zip will probably cause you to lose root (unless it's a pre-rooted zip, in which case you would need a custom recovery to flash it)...
hmm so I skipped a step, after unlocking bootloader I need to do what exactly? (commands/links if possible!)
it seemed simpler on the xoom.... unless it's the same thing?
adb reboot bootloader
fastboot oem unlock (wait for reboot)
adb reboot bootloader
fastboot flash boot rootboot.img
fastboot reboot (wait for reboot)
adb remount
adb shell push su /system/bin
adb shell ln –s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
that's it? are the Nexus files different? (got a link?)
as for Gingerbreak, I kinda got sick of always waiting a long time for 1-click roots after each update. I will try to get it working (so far no go, gonna stick a blank sd in my phone and try that) just so I can do a full Titanium backup and maybe a recovery if possible
Gingerbreak worked - stuck a blank micro-sd, rooted, put my 16gb micro-sd back in - all is well
running full Titanium now...
FOR SPRINT M8 NON-H/K MODELS ONLY
Well everyone I'm here to bring you a little tool set i use to take official OTAs.I am not a dev nor do I take credit for the work. This is mainly just a collection of things I used to get OFFICIAL OTA updates. I've used this on 2 Sprint m8's with STOCK Hboots so I am sure this will work. Please feel free to share this with others JUST GIVE CREDIT WHERE IT IS DUE.
To start off there are some requirements...
S-OFF is needed
STOCK HBOOT
HTC One M8 (Sprint non-Harmon Kardon)
UNLOCKED Bootloader (If you are LOCKED and rooted PLEASE use UNLOCK Bootloader method included in zip. DO NOT use HTCDEV to unlock... Your internal storage will be wiped if you do. YOU HAVE BEEN WARNED
MAKE SURE TO UNLOCK BOOTLOADER before doing any of this (instructions are included in zip)
1. Copy the stock nand to backup folder in twrp
2. Make a backup of your setup
3. Restore the stock nand provided
4. Flash stock recovery provided
5. Boot up and do all otas up to latest
6. Flash custom recovery
7. Restore your backup
8. Flash modified firmware
9. Lock bootloader
10. Flash asdp for hk mod.zip in ruu mode (same as flashing FIRMWARE) if audio is not working in htc music
Locking-Unlocking & Remove Tampered flag
***NEED TO BE S-OFF!!***
TO LOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***LOCKED***
TO UNLOCK BOOTLOADER
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should be ***UNLOCKED***
TO REMOVE ***TAMPERED*** text
1. Phone on with adb debugging enabled to confirm this open cmd prompt type adb devices should show device serial number
2.Type adb shell
3.Type su to get # prompt
4. Copy paste exactly as is
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
5.Type exit you may need to enter that command 2x to get out of adb shell
6.Type adb reboot bootloader You should not see ***TAMPERED***
Flashing Firmware
IN HBOOT MODE
1. Label the file to exactly 0P6BIMG.zip
2. Put zip in root of external SD card
3. Boot into HBOOT to flash (bootloader should detect zip automatically and prompt you to flash)
IN FASTBOOT MODE
1. Boot device into FASTBOOT mode (device should show FASTBOOT USB)
2. Put the firmware file to be flashed in the folder with fastboot.
3. Open a command prompt from the folder where fastboot is located.
4. Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 0P6BIMG_M8WHL_x.xx.xxx.x_firmware.zip (the name of the zip should match the name of the file you're flashing)
5. Once complete, you can fastboot reboot or fastboot reboot-bootloader depending on what you want to do next. If you choose bootloader, you can confirm that your radio is now updated to the one from the file you flashed
Links needed ...
For Locking and Unlocking bootloader (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Removing Tampered Flag (ONLY WORKS WITH ROOTED ROM AND S-OFF!!)
For Modified Firmware
I'd like to give thanks to the people that have made this possible
if i forget someone I'm sorry send me a pm I'll add you to the list
Team420 for taking me in showing me the basics
BADSEED for allowing me to break so many test roms lol
BD619 for hooking me up with adb files
scotty1223 for making those awesome guides
Captain_Throwback for providing the collection of firmware ... Oh yeah and the TWRP recovery
TEAMWIN for making TWRP in the 1st place
HTC for making such an awesome phone
DISCLAIMER: I AM IN NO WAY HELD LIABLE FOR DAMAGES MADE TO YOUR PHONE OR IF YOUR DEVICE TRANSFORMS INTO A DECEPTICON CAUSING WORLD DESTRUCTION...YOU ARE FOLLOWING AND FLASHING THIS AT YOUR OWN RISK
DOWNLOADS
Main Link on Mega HERE
Mirror Link on AFH HERE
And this as well
Hi,
Added to FAQ Guide Q15
Nice work Miggs:thumbup:
Sent from my HTC M8
Great work Bro, very helpful. Thank you
Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8
Magnum_Enforcer said:
Just one thought on your thread title. You might change it to "How to Return to Stock" since most of those steps aren't needed to take a OTA. Very useful for those who need to go back to a stock device though.
Sent from my HTC M8
Click to expand...
Click to collapse
GOOD CATCH!! THANKS ... That was actually how this idea came about lol
Good work Miggsr!
Need stock apps to take OTA
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
Why not just keep a backup of the latest stock rom on your sdcard?
BD619 said:
Why not just keep a backup of the latest stock rom on your sdcard?
Click to expand...
Click to collapse
Or look in the first post of this thread for stock backups:
http://forum.xda-developers.com/showthread.php?t=2736048
Sent from my HTC M8
Piroman024 said:
I'm in need of a list of the stock apps so I can figure out what ones I'm missing so I can take the OTA. Also has someone made a zip of the stock apps. Any help would be great.
Click to expand...
Click to collapse
in my zip i have included a STOCK backup made with TWRP that is also included in the zip it has ALL stock apps that you may be looking for to make things easier just copy that folder to your TWRP backup folder whether its on your internal sd or external sd restore that and boot up
Tring to upgrade "dirty"
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?
Piroman024 said:
I do keep a copy of the stock rom for when stuff hits the fan. I also have a backup i made before I went S-off. I deleted a few of the system apps that were bugging me before I learned that OTA also checks apps.
I'm trying to get the OTA without wiping my phone and all the setup time I have so far spent on it.
I just try to install the OTA again this time i checked the log. I get "/system/app/Plusone.apk" has unexpected contents. I guessing this is caused from my removing apps. I'm thinking i can use this to find what the installer thinks is missing.
My last question, is there a way to extract .apk and .odex files from the ruu?
Click to expand...
Click to collapse
okay with the first half of what you said... i have not had an ota check for apps... when removing google plus you probably left a second apk that works with it hence your error message. if you are looking to be able to take an official ota you should NOT be rooted. honesty if you meet ALL REQUIREMENTS i listed then just follow the guide you should be fine. the backup i have there is based on initial rom that came with the device. so you will have to do 3 ota updates to be exact. i made it that way out of personal preference. now for the second half of your post ... as i mentioned i am not a dev unfortunately i can not answer that question for you... slightly above my pay grade. not to put you on the spot either i'd like to keep thread on topic in OP.
so Harmon Kardon edition can not be unroot?
hhhstonehhh said:
so Harmon Kardon edition can not be unroot?
Click to expand...
Click to collapse
Sure it can...same steps just use HK files
BD619 said:
Sure it can...same steps just use HK files
Click to expand...
Click to collapse
I could not have said it any better lol
Great Tut Miggs !!!
cbrown245 said:
Great Tut Miggs !!!
Click to expand...
Click to collapse
thanks CB i just making things easier for others