Database Develop

Bootloader 'not allowed'

Dear XDA-Helpers,
First of all I want to apologize. Because likely the most of you will think the answers on my question are already posted. But I've searched and searched and I don't have found the solution. (Yes I saw this thread too: http://forum.xda-developers.com/showthread.php?t=487187 It's the same question but that didn't help too.)
So this is what I did:
I wanted to test out the Eclair 2.0 Rom, so I flashed that over Cyanogen. Then I wanted back to 1.6, and used this method. ( http://www.gphone.org.hk/cgi-bin/ch/topic_show.cgi?id=60&bpg=1&age=0)
So I was on 1.5 and rooted with the one click method. Then I flashed the signed-dream_devphone_userdebug-ota-14721.zip ROM. When that was finished I reboot my G1, and then I wanted to flash Cyanogen, but when I went back to recovery mode, the orignal HTC recovery was back and I was unrooted, now I also cannot flash any DREAIMG.nbh because when I go in bootloader it says "not allowed".
I really don't know what to do now.
Some specs about my G1:
Android G1 with Donut 1.6
Kernel Version: 2.6.29-00479-g3c7df37 [email protected] #19
Build Number: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
About the error of the bootloader:
0028002 not allowed
DREA110 PVT 32B
HBOOT-0.95.0000
CLPD-4
RADIO-2.22.19.261
Sep 2 2008
serial0v
Thanks!

You're not unrooted. You just didn't read the instructions carefully enough.
Use fastboot to flash a modified recovery (I prefer CM's).
Code:
start your phone in fastboot usb mode.
fastboot flash recovery recovery.img
fastboot reboot
Once that is done, go into the recovery and you can flash roms again.
This time FOLLOW the instructions...
After you've flashed the htc recovery image, do NOT restart the phone, simply flash cyanogens rom right after that, THEN reboot.

next time please post in the QnA section
you might also like to try RA-Dream-v1.5.2 - there are lots of extra options in there like partitioning your card for swap, apps2sd etc

garok89 said:
next time please post in the QnA section
you might also like to try RA-Dream-v1.5.2 - there are lots of extra options in there like partitioning your card for swap, apps2sd etc
Click to expand...
Click to collapse
Sorry for wrong section, I was used to use RA-Dream recovery, but since I don't have root anymore, I cannot flash a other recovery..

Bavilo said:
You're not unrooted. You just didn't read the instructions carefully enough.
Use fastboot to flash a modified recovery (I prefer CM's).
Code:
start your phone in fastboot usb mode.
fastboot flash recovery recovery.img
fastboot reboot
Once that is done, go into the recovery and you can flash roms again.
This time FOLLOW the instructions...
After you've flashed the htc recovery image, do NOT restart the phone, simply flash cyanogens rom right after that, THEN reboot.
Click to expand...
Click to collapse
Well, when I typ 'su'/'sudo' in Terminal Emulator, it says no permission or something, so I think I don't have root anymore.. will your method fix my Bootloader? I used to get a screen with some skateboard but now I get a screen with a few colours.. and then it says 'not allowed'

Well when you flash the htc recovery image and then reboot the phone it will flash the stock recovery. That's why you need to flash cyanogens rom right after it.
But I don't really see why you're at the stock bootloader again now.
So you're on 1.6 with the stock bootloader? And the bootloader won't flash the .NBH, Looks like you need a goldcard.

Thanks for your answer!
Bavilo said:
Well when you flash the htc recovery image and then reboot the phone it will flash the stock recovery. That's why you need to flash cyanogens rom right after it.
But I don't really see why you're at the stock bootloader again now.
So you're on 1.6 with the stock bootloader? And the bootloader won't flash the .NBH, Looks like you need a goldcard.
Click to expand...
Click to collapse
yes I'm on 1.6 with the coloured boot loader and I can't flash a .NBH file, it says not allowed. What is a goldcard? You mean this? http://revskills.de/pages/goldcard.html
It says I need to give them my SD Card Serial (CID), but I have no idea what it is and where I can find it..

Here now the problem is that you cannot flash anything from the bootloader coz its telling 'Not allowed' And not even flash through recovery coz its the non - Rooted Stock one...
So here you go may be this would help you to get out of this problem.
First try this...
1. Get Amon_RA Recovery image into any folder.
2. Then Start your Phone in Boot loader mode
3. Open Command Prompt on your PC (Windows > Run > Type 'cmd' > Enter)
4. Browse to the folder where the Recovery image is located using cd <folder>
5. Connect the Phone to the PC via USB
6. Type fastboot boot <recovery_img_name.img> in the cmd window.
The Phone may boot into the Rooted Recovery...
If Not Try this..
Remember when G1 was first rooted ?
We had to type telnetd and then it installed the telnet application...
Try it...
Put the downloaded recovery image into the sdcard means /sdcard/recovery.img
1) Go to the Terminal emulator & type "telnetd" and press enter.
2) Press Home
3) Goto the market and download "Telnet"
4) Open Telnet and connect to localhost : 23
5) Press enter and you should see a #
6) Now type the following and press enter at the end of each line
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery cm-recovery-1.4.img
cat /sdcard/recovery.img > /system/recovery.img
7) Now try going into Recovery mode hope this might work...
Then Post ur info here...

Thank you!
sangeet.003 said:
Here now the problem is that you cannot flash anything from the bootloader coz its telling 'Not allowed' And not even flash through recovery coz its the non - Rooted Stock one...
So here you go may be this would help you to get out of this problem.
First try this...
.....
If Not Try this..
...
Then Post ur info here...
Click to expand...
Click to collapse
Thank you for your answer!
The first method did not work because, when I go in Bootloader my PC don't detect that the G1 is connect, it just don't do anything.
The second method didn't work too, because when I typ in terminal 'telnetd' it says no permission...

He can't flash from the boot loader as he doesn't have the engineering boot loader installed.
The other option might work though. If not, a goldcard will be the only way out.
This process is a bit tricky though.
First of all you will need the cid of your sdcard, to get this, type the following command in the terminal emulator.
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid > /sdcard/serial.txt
The cid will be saved within the root directory of your sdcard.
Now comes the tricky part, you need to reverse the string byte-wise. Here is an example.
This is what your cid can look like.
Code:
03534453553038478021021a320087be
Now split it up in pairs.
Code:
03|53|44|53|55|30|38|47|80|21|02|1a|32|00|87|be
Next, reverse the string byte-wise.
Code:
be|87|00|32|1a|02|21|80|47|38|30|55|53|44|53|03
Your reversed cid will look like.
Code:
be8700321a0221804738305553445303|
Now, take that cid and plug it into the goldcard generator you posted earlier and enter your email.
https://ssl.webpack.de/revskills.de/pages/goldcard.html
You will be send an goldcard.img file.
This last part is important and requires knowledge with linux and the dd command
1. Format your sdcard with Fat32.
2. Open a shell and type dd if=location_of_goldcard/goldcard.img of=/dev/sdx(where x is the letter that stands for your sdcard)
3. When it gives you a prompt saying the write was successful, drag the .NBH to the root of the sdcard, plug it in your G1, and try again.
You are welcome to hit me up on MSN if you need further assistance.

thierrz said:
Thank you for your answer!
The first method did not work because, when I go in Bootloader my PC don't detect that the G1 is connect, it just don't do anything.
The second method didn't work too, because when I typ in terminal 'telnetd' it says no permission...
Click to expand...
Click to collapse
That's because you're on 1.6. I believe this only worked in 1.0 where the keyboard was attached to a root console, so anything you typed on the keyboard would go straight to the console with root permissions. This flaw has been fixed.

Bavilo said:
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid > /sdcard/serial.txt
Click to expand...
Click to collapse
And again, permission denied

Problem solved, a goldcard was needed.
This thread can be closed.

Solved!
okay, it's solved! Thanks to Bavilo for helping me out on msn
Thanks al others for helping!

How to flash stock recovery.

Hi guys,
I have to send me N1 to htc for fix some problem.
I have RA recovery with lock bootloader, and I want to flash the original, but "fastboot" way doesen't work (signature fail ).
How can i flash it in other way?
Ty
(sry for my eng )

Just flash the stock rom with the recovery image like frf92 original.

evilkorn said:
Just flash the stock rom with the recovery image like frf92 original.
Click to expand...
Click to collapse
How? Through recovery? Because "fastboot" hates me, and won't work.

I'd suggest using a passimg for frf85b and then maybe updating to 91 (or just leave it at 85), you can always re-root when you get it back.
________________________
N1 w/ XDA App

got it, thk to cyanogen wiki
Plug the phone into the computer
Reboot into fastboot by holding TrackBall + Power (you should see three Androids on skateboards and the words 'fastboot USB' in red)
On the computer, open a command prompt cd to the sdk/tools directory (we will assume the SDK is located in C:\android-sdk and the recovery file is in the root of the sdk/tools directory for the following steps)
With the phone connect via USB, open up a cmd prompt
Code:
adb reboot recovery"
Code:
adb devices
​A device name and 'recovery' should be returned
Code:
adb push recovery.img /sdcard/recovery.img
​recovery.img is located on android-sdk/tools dir
Code:
adb shell flash_image recovery /sdcard/recovery.img
​This permanently flashes the recovery.img to your phone, you can now boot into it by holding Vol- while powering on the device
Reboot

nrdmtt said:
got it, thk to cyanogen wiki
Click to expand...
Click to collapse
Thanks for searching!
I hope this encourages other users new to ADB, flashing ROMs, etc. to continue to search after asking for help.
Way to go nrdmtt!!

[Q] Stuck at Fastboot usb screen

I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?

If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?

How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.

I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.

ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s

1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.

casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.

ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.

casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.

ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.

I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.

ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks

Did you fix this yet?

Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!

Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!

[GUIDE] How To Root HBOOT 1.01

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!

[Recovery] ClockworkMod 5.0.2.0 Official

I just noticed it now, grab it here:
S-OFF
recovery-clockwork-5.0.2.0-buzz.img
S-ON / fake-flash
recovery-clockwork-5.0.2.0-buzz.zip
Haven't tested it, try it at your own risk but should be safe
S-OFF: flash with fastboot with
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
S-ON: simply rename to update.zip and put it on your SD card

Eh!!! Confused!!!!! cwm 5.0.2.0 been around for ages????
"sent from me2u"

I just didn't see it posted lol, did a search and didn't see the official 5.0.2.0, only older and customized versions

Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!

Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium

So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )

Qarl said:
Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!
Click to expand...
Click to collapse
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
nogoodusername said:
Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
With S-ON, you can only use the fake flash by renaming the .zip to update.zip and "flash" it from the stock recovery to launch CWM...
nejc121 said:
So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )
Click to expand...
Click to collapse
No idea

Kwen said:
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
Click to expand...
Click to collapse
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English

See http://developer.android.com/guide/developing/device.html
"If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:"

Qarl said:
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English
Click to expand...
Click to collapse
This word in'valid
Change Legend to buzz
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse

If you're on Windows, have you that in the recovery installation folder?:
AdbWinApi.dll, adb.exe, fastboot.exe and recovery-X.img

Good call, copy paste error
Also if you don't have the fastboot command, you'll need to download the "Android SDK Platform Tools" (under "Tools") from the SDK manager (how did you get adb working though without the platform tools?!)
Should be under the same directory...

Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"

First, I go to "android-sdk/platform-tools" with the terminal.
Then, run this command:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
And the terminal return this:
Code:
< waiting for device >
What's happen? If I run "adb devices", my HTC Wildfire is founded.
Regards!

Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that

Kwen said:
Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that
Click to expand...
Click to collapse
Problem solved!!!
I believed that the device reboots to fastboot when the command executed it.
Sorry ¬¬
Thank you very much!

slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
I think you'll need a flashable zip, the one koush provides is just a img and a fake flash .zip

@Kwen, yes copy/past error xD

how can i call the yes/no event in this recovery with an updater-script?
other phones have recovery that have a list of comand,that you can add to an updater-script to call some recovery functions.
also this?

slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
How do I do this if the OS itself is crashed and I get a white screen and HTC logo???