[Q] Broken Recovery - G1 Q&A, Help & Troubleshooting

Hey there - hope somebody can help me!
* I've got a G1, which was ROOT and on Cynogenmod6.1
* I followed a guide to unroot my device and bring it back to 1.6 with normal SPL ..
Today, I wanted to root my phone again and update it again to Cyanogenmod6.1.
Installed RomManager and ClockwordMod-Recovery. Bootet to the Recovery and chosed "Update Zip". I wanted to flash the DangerSPL. That's the point everything crashed....
I can't start CWM-Recovery again, pressing HOME+POWER just brings me to the (original?) Recovery, which doens't accept any update.zip.
Hope I could fix it with Terminal or with TelnetD, but i can't.
What can i do? Help me please
FACTS:
Model: T-Mobile G1
Firmware: 1.6
Baseband: 62.50S.20.17U_2.22.19.26I
Kernel: 2.6.29-00479-g3c7df37
[email protected] #19
Build#: DRC92

Would be interesting to know, what SPL is installed.
If you had an engineering SPL, fastboot is you friend, you can flash a new recovery image directly.
Otherewise, if you do not have root access, I would suggest to boot the phone, install AndRoot / OneClickRoot or something like that and gain root access again. Then, having root access, you should be able to flash a new recovery using flash_image.

Hey there. It's the normal SPL. The one with the coloured background >.>
And, i've got root - but the flash_image thing isn't working. With no programm..
(Terminal/Flashrec/..)
):

Did you follow the instructions from here? There you can find a link to the flash_image binary, too.
You need to extract the zip, copy the flash_image binary on sdcard and probably you need to change the attributes to executeable (i am not sure). Then you need to copy the recovery.img to sdcard, too. After that, open the terminal application on your phone, go to super user mode and execute
/sdcard/flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse

Hey!
I made it the way with the Terminal and with the ADB, but both times i get the message "/sdcard/flash_image: permission denied.
--
Edit: Ok i just played around with ADB and it works now. Thanks for you help!

kamikatze004 said:
Hey!
I made it the way with the Terminal and with the ADB, but both times i get the message "/sdcard/flash_image: permission denied.
Click to expand...
Click to collapse
Is sdcard mounted? If yes, do a
chmod +x /sdcard/flash_image
Click to expand...
Click to collapse
and try it again.

Related

Unable to get root access...

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".

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!

biggest trouble ever installing 2.2

so back when i had 1.5 on my hero i had no problem at all installing roms. so when i updated to 2.1 stock awhile back i tried to root it and install a rom on it with the command prompt and unevoked method. it got it rooted and when i got to the recovery menu i nanidroid backedup and wiped and installed it. it then got stuck on the htc boot screen so i tried different rom and still would hang on it. so i said screw it and stayed on stock. i then later used the unlock univeral to root it but i can not stand the stock rom it is so slow and lags so i tried the offiical htc update from .6 to .7 to see if it would be faster but once it downloaded and i pressed install it would yet again hang on the htc screen. i cant even make calls with out lagging. so i tried once more to install 2.2 on it with a recovery img. i download rom manger and put froyo on the sd card but it would yet again hang when i click install rom from sd card. what do i do?!!!!!
update: i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
help please!
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
laie1472 said:
It might b the recovery ur using if your able to boot into any rom access terminal you can get it from the market try to flash a different recovery I recommend. Darchstar RA 1.6 once u download it place it on the root of ur SD card not in any folders / then open up terminal and type su once the # appears type flash_image recovery /sdcard/ recovery- name of recovery. img wen that's done type reboot recovery and you should boot into recovery then try and flash ur rom from there hope this helps good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
ill try this when i get home tonite. thanks!
i tried doing it through the teminal but it say flash_recovery not found
so i tried to do it through rom manger and it did the back up and installed it through the recovery menu but once it was done and rebooted it yet again is stuck on the htc boot screen.
I recommend you boot into recovery - wipe your system / cache / dalvik cache and then flash the 2.2 rom of your choice -
if you were just flashing rom after rom without flashing then that could be a lot of your troubles -
also - you mentioned that the recovery file was not found on your sdcard - did you remember to unzip it first before attempting to flash it through terminal emulator? because it wont work otherwise ...
if you have extracted it to the root of your sdcard you shouldnt have any trouble
type
su
flash_image recovery /sdcard/nameofyourrecovery.img
reboot recovery
and you should be good to go - let me know how you do and we'll see if we can't help you further if needed
good luck!
cbwhat said:
i tried doing it through the teminal but it say flash_recovery not found
Click to expand...
Click to collapse
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Vandelay007 said:
did you type:
su
flash_image recovery /sdcard/yourrecovery.img
or su
flash_recovery like your post shows - because you dont want to do it like that - just checking -
Click to expand...
Click to collapse
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
cbwhat said:
no it i type in
su
flash_image recovery /sdcard/recovery7.img
flash_image not found
Click to expand...
Click to collapse
you said that you are doing this in a terminal window? (i am assuming that is on the phone) is your phone connected via usb to your computer? is the sdcard mounted by the computer? if it is unplug the usb and try again. if the computer has mounted the sdcard you can't access it from the phone.
i dont have it plugged in when i use the terminal on the phone
cbwhat said:
i dont have it plugged in when i use the terminal on the phone
Click to expand...
Click to collapse
ok just checking.... that was the only thing that i could think of that would stop you from reading the sdcard.
It may sound silly, bt when I do it I always make sure I account for case sensitivity...
Like flash_image recovery /sdcard/RA-Darchstar.img
Have you tried that?
Sent from my HERO200 using XDA App
yep make sure everything that has a capitals in it i capitalized in the terminal
this may sound silly as well.. sometimes when i use adb to push i mistype the location for example: adb push myfile.ext /adcard
everything goes fine until i go to find the file....
don't know though.
i still can't figure out how to install a custom rom.
Try backing up you sd and reformatting it on ur pc then just place the recovery img on your sd and nothing else then try to flash it good luck feel free to pm me I know how u feel man so if I can help I will good luck
Root-Hack-Mod-Always™

[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!

corrupted recovery

I have HTC Hero CDMA obviously lol
but anyways i have the latest HBOOT without S-OFF and i have a corrupt recovery i have tried restoring with the latest offical RUU with no luck as i get the 170 usb error connection error
Why not just reflash your recovery ???
#Root-Hack\Mod*Always_
""Shooter on Deck""
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
evoandroidevo said:
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
Click to expand...
Click to collapse
Go to my signature and click on the CWM link. Then unzip a version and place the recovery.img on the root of your SD card. Now download Busybox installer, and terminal emulator. Install busybox and after installing open terminal emulator and then enter these commands:
Code:
$ su
# flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される。
i did all that installed busybox and all that stuff and i always get flash_image not found or something like that
EDIT:
Got it to work jsut need to go to 2.27.651.5 instead of 2.27.651.6
I seem to be having nearly this exact same problem. Maybe If I can flash a recovery to my hero I wont need to create a thread of my own asking for help.
What did you mean by "need to go to 2.27.651.5 instead of 2.27.651.6"?
I have root... or at least the "su" command in terminal gives me a #. I have placed the recovery image on the root directory of my sd just as dastin said and run the command but I am getting the flash_image not found error.
That's the RUU version.
Sent from my PG86100 using xda premium
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Jacob_newton said:
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Click to expand...
Click to collapse
Install busybox.
私のEVO 3Dから送信される。
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Jacob_newton said:
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Click to expand...
Click to collapse
Why not just flash the recovery ??? From terminal,hooot, or adb.
#Root-Hack\Mod*Always_
""Shooter on Deck""
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Jacob_newton said:
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Click to expand...
Click to collapse
Were did you place the recovery img at ??
#Root-Hack\Mod*Always_
""Shooter on Deck""
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Jacob_newton said:
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Click to expand...
Click to collapse
Let me ask you this are you trying to flash this from terminal or from adb ?? If there isn't a copy of the recovery img in your adb tools folder then trying to flash it threw adb wouldn't take because the image isn't there. Since the img is on your SD card then you should flash it threw terminal if your not trying it already. If you want to flash it threw adb then place a copy of the recovery img in your adb tools folder and then run the commands from cmd terminal VIA pc/laptop. Also have you made sure that the recovery img is named correctly ?? Also will you post your setup, as in rom,kernel,baseband/radio, and hboot. Also how did you obtain root ??? Thanks
#Root_Hack-Mod*Always\
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
I think you should ruu back to stock and reroot again. Reason why I suggest this is because of how you gained root. If something wasn't done correctly we could be at this for hours and days trying to figure this out. But before you take that route I'll send you a pm with something I would like you to try that might work.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Click to expand...
Click to collapse
Quick??? Are you able to boot up into your Rom ???
#Root-Hack_Mod*Always\
I'm not sure what you mean by that, but I decided to flash stock the other night so now I'm going to try and re-root and flash a custom ROM.
I am considering this method for re-rooting: http://forum.xda-developers.com/showthread.php?t=909258&highlight=root
Any suggestions before I get started?
What I meant by have to be on the 2.27.651.5 RUU instead of 2.27.651.6 RUU as the flash_image is not in thr 2.27.651.6 RUU so you need to be on the 5 version of stock in order to use flash_image
Sent from my Shooter using XDA

Categories

Resources