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!

help installing cm - too many different guides, any verified?

hi there,
so i am slightly new at this and have searched for hours and hours trying to find a consistent formula for rooting and installing my g1 to cyanogen mod 4.2 (or latest stable one, thus not cm 5). I seriously stayed up until 1am last night and now i am at work (started at 8) still searching.. I have used google, youtube, and several other cm sites. Basically the problem is there is not one guide and I am not sure if because I followed the CM wiki guide if i can switch because I am having problems with that one. So one question: does anyone know which is the latest and verifiably the best CM 4.latest guide to installing?
I am pretty sure i have rooted the phone because I successfully downgraded to RC29, the old school android OS. However when I try completing this guide: [cant put a URL in but the webpage title is: "G1 CM4.2 installation" and I already completed this wikiguide title: "Full Update Guide - G1/Dream Firmware to CyanogenMod" but it continues into the next page to install cm)
I get freaking stuck. I put all three files on my SD and when I try to push "Alt-A" there is not an option there for it, its not an option on my recovery mode menu. I tried putting the files back there after reformatting several times but still no 'alt-a' so I am stuck on step 5 because there is no option for step 5 on my recovery mode on the above web guide..
Does this mean I did not install something? should I try and install the ota radio, cm update, drc83 zip files separately (like load one on the sd card and install it, then reformat the sd card and then repeat with the other two files?) ? If so what order should I do that in??
Sorry I suck and have not been able to find these answers, there are just a plethora of guides and I am not confident in my modding to start deviating away from the wiki guide in case I brick my beautiful g1..
thanks so much, this has been a huge headache for me.. i literally spent 4 hours yesterday trying to get to this step.. aww...

At Step 5 select "apply any zip from sd" in Recovery.
Select "DRC83_base_defanged.zip" on your SD.
Press Home to confirm flashing.
Then select "update-cm-4.2.x-signed.zip" on your SD to flash CyanogenMod.
After everything is completed reboot your Phone normally.
Edit:
Here is the Link to the Tutorial.

zerocoolriddler said:
At Step 5 select "apply any zip from sd" in Recovery.
.
Click to expand...
Click to collapse
Yup you hit the nail on the head. Sorry I must not have been too clear on what was I was saying earlier. That is exactly the problem, you see I would select that in recovery mode, But "apply any zip from SD" is not there! Did I load some file wrong??
It only gives me:
Android system recovery utility
E: Can't open /cache/recovery/command
Home+Back - reboot system now
ALt+L - toggle log text display
Alt+S - apply sd:update.zip
Alt+W - wipe data/factory reset
could it be this: "E: Can't open /cache/recovery/command" that is the problem? I only found one reference to this message during my internet searches and the guy said it always says that..

So you have CM-Recovery?
Flash Amon_RA`s Recovery, it´s more comfortable to me. I´m using 1.6.2.
For G1: http://forum.xda-developers.com/showthread.php?t=566669
For MT3G(Magic 32b): http://forum.xda-developers.com/showpost.php?p=4029315&postcount=1

Nope. I am also using Flash Amon_RA's recovery.. (v1.6.2)
I loaded it up on the flash drive and also used telnet app to flash it in (wrong terminology? I typed it in the telnet box and hit return and it gave me the # # which I read means I did it right)

Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img

maybe i get something wrong
but did you boot into the recovery menu already? (press home and power when you turn the phone on)
from there you can choose your task with the trackball nice and easy...
(you r from vienna?)

zerocoolriddler said:
Try flashing again using fastboot.
Following Points should be listed:
1. Reboot system now
2. Go to console
3. USB-MS Toggle
4. Backup/Restore
5. Flash zip from sdcard
6. Wipe
7. Partition sdcard
8. Other
9. Power off
Install via Fastboot:
Copy recovery-RA-dream-v1.6.2.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img
Click to expand...
Click to collapse
those points are not listed!
I did not try flashing via fastboot before but rather via terminal app.. Do I need some special software for fastbooting? Amon_RA's post says i need "Requires engineerings SPL!" which I do not have ..
and I now I loaded it via fastboot and I cant get out of it! how do I reboot out of fastboot? Because I can do not know how to "fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.6.2.img" .. can you explain that in more detail?
skarboy- no i am not from vienna but the USA. and yea I tried to boot from the recovery menu but when i am there it does not show the option of flashing zip from sd (see above)

You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.

mejorguille said:
You did not succesfully apply the recovery image then. Find amon_ra 1.6.2, rename it to recovery.img (make sure that you don't accidentally name it to recovery.img.img because of windows explorer on your computer). Put it on the root of your sdcard. From there, open the telnet app and type "su", then type "flash_image recovery /sdcard/recovery.img" power back on to recovery (home+power), and apply DRC83, CM4.2.15.1, and radio 2.22.23.02.
Click to expand...
Click to collapse
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful

austriker27 said:
oh okay. shoot.. I followed your instructions. do I hit return after typing 'su' in telnet? I did and then typed in the flash image stuff and hit return again. it gave me '##'
i am not rebooting in recovery.. hopefully it will work .
can i have all 4 files on the SD card at the same time? or should i erase it then load the DRC83, CM4.2.15.1, and radio 2.22.23.02 files??
also if i dont get the alt+a option should i just keep trying ??
EDIT: NOPE IT did not work, maybe I should just rename the file recovery, i looked under file properties last time but it didnt say it was hiding the file extension.. I am not quite sure what I am doing wrong.. if someone could show lead me through each individual step by step that would be swell.. of post a video (not outdated).
awwwwwww this is soo painful
Click to expand...
Click to collapse
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)

okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..

You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)

mejorguille said:
First make sure you have all the files needed (recovery.img, DRC83_base_defrangled, CM4.2.15.1, and radio 2.22.23.02). Tell me if you are missing anything. Load them all up on your sdcard. Make sure that none of the files are in any folders. Next you are going to want to download the "terminal emulator" app from the market (by ZTA). Once downloaded, open the app and type "su" (enter). After that, type "flash_image recovery /sdcard/recovery.zip"(enter). Type "reboot recovery" (enter). If you do not see this image below, then something went wrong.
(note, that image shows 1.7 but you are going to want to install 1.6.2. v1.7 is for CM5-based roms)
Click to expand...
Click to collapse
okay so I tried all that.. and freaking a! awwwwww no success it just gave me the old screen like before
when I typed in "su" it said permission denied so I think I have to go back and do something that I missed. I cant keep track of how many times I have done everything, then erased then tried again.. I wish someone would be specific and just walk me through this without skipping a single detail..

zerocoolriddler said:
You don't need to unzip. They're zipped to flash via Recovery.
Flash the Recovery via Fastboot.
PS: It's called Terminal, not Telnet. ;-)
Click to expand...
Click to collapse
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step

austriker27 said:
okay, so after a much needed break of watching the US draw with England (world cup!!) i am back..
yes I have all of those files but my radio file is different (older?).. It is "ota-radio-2_22_19_26I".. should I have the radio file you mentioned? can you link it to me?
EDIT: Okay I found that file that you referenced and downloaded it. I will throw it in my sd card instead of the 26I because it sounds like it is a better radio flash..
also the 'radio', update cm, and DRC83 files are really zipped folders (.zip) that I have not extracted. Do I need to extract the contents into a folder and put the files from these extracted folders on the SD card root (so that there are ZERO folders on the sd? (no one mentioned this)
and so I use terminal emulator as opposed to telnet?? I was using telnet before because the CM wikiguide says so..
Click to expand...
Click to collapse
the 2.22.23.02 radio is newer and its supposed to have better reception and less battery usage as compared to the .26I radio but the difference should be minimal. Everything is supposed to be in a zipped folder exept for the recovery image. Terminal is similar to telnet in that you can put in commands but it works a little different. It is what I usually use to flash recovery's, etc, so since telnet was not working for you I though terminal might make a difference.
Again, open terminal and type:
Code:
su(enter)
flash_image recovery /sdcard/recovery.img(enter)
reboot recovery(enter)
Tell me if this works.
Edit:look at my next post

austriker27 said:
this is exactly what i am talking about everyone is saying something different:
here is the CM site telling me to use telnet:
Open Android Telnet Client and type (include all spaces)
flash_image recovery /sdcard/recovery.img [enter]
If completed correctly you will simply see # # appear on your screen beneath the line you've just typed. If you get the "permission denied" message, type "su" (without quotes), press enter and repeat the previous step. If you get a file not found message, you may need to remount your sd card or make sure you typed the file name correctly.
Press Home key and proceed to next step
Click to expand...
Click to collapse
The "su" command signifies root access. If it says permission denied, then that means that you are not rooted or you skipped a step.
CYANOGEN WIKI said:
Rooting the phone
You need to have root (or 'admin') access to the phone so that you can install whatever software you want and not just what your provider gives you. This is not the same as unlocking your phone.
Finish booting up your phone, and sign-in to your Google account.
If you don't have access to a 3G network, then follow the G1 logon to google via wifi guide to sign-in via wifi. The original guide to do this is out of date.
You could try and add your networks provider's APN. To do this press Menu key -> APN Settings, press Menu again -> Add APN and enter 4 things: Name, MCC (Mobile Country Code), MNC Mobile Network Code and APN - all this info should be available here: http://en.wikipedia.org/wiki/Mobile_network_code and on your network provider's site. The image you booted with might also have the extensive APN list. If so, and you can't get a data connection, then you might try the wifi guide.
Once you're at the Home screen, open the keyboard, and press the Enter (Return) button twice.
Type
telnetd [enter]
Typing will bring up the Contacts screen, but you can just ignore that.
There will be no indication to let you know you did it right. Just continue on to the next step.
If you get an error when trying to connect (step 5), try pressing Enter twice and type "telnetd" and press Enter again
Open the Android Market, and install "Telnet" by ClockworkMod (Formerly by Koushik Dutta)
Open Android Telnet Client, enter "localhost" in the large text box and press connect. (You may have to enter "23" in the smaller text box on the right)
Click to expand...
Click to collapse
Do those steps again.

okay so I am in the telnet client and have entered localhost and 23 and hit return. so now i am in a black screen. i typed in what cm wikiguide told me and it gave me :
## (good sign!)
now do I turn off the phone and go into recovery mode or this where I am missing a step??
Sorry I am so ornery (wow and i can spell) there are just a number of things frustrating me.. besides me knowing this should only take like 2 hours at the most and knowing I keep messing up some mundane detail or something.. Also I am doing it in windows on my macbook and the wireless keeps disconnecting. Also I would take photos of the screens to show you but I do not have any photo software on the windows partition of my laptop (i mostly use mac os x) so I cannot... and i am very tired from working 6 days a week (and only getting 6 hours of sleep last night due to this issue) and frustrated from this whole fiasco.. And I have a headache.. yup call me a whiner if ya want but i am just trying to explain why i am kinda mad...

HALELUJAH! it worked and the android system recovery looks like your image mejor!!!!!!!! hopefully this works, i will let you know.. thanks soo much! i have no idea what i did differently

YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
wow so that wasnt a giant headache, although now i pretty have the process memorized and have learned tons in the process. I think I may have the longest time to root a g1 record so far of any human haha... Lets see I worked on it yesterday from 8pm-1am while kind of watching world cup. This morning for about 2 hours from 9-1130 at my job. And this afternoon for about 2 hours..So like 9 hours give or take an hour of two.. NEW RECORD!! haha
THANKS SO MUCH for you help guys I love you. Especially mejor because he/she lead me down the finishing stretch... Now to install apps2sd (after my class 6 card comes) and take a nap

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

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

[Q] Flashing CM7

Hi all!
Last week I bought a used but still good-looking T-Mobile G1 (HTC Dream). The previous owner has rootet it (Android 1.6 is installed) and this are the infos:
Firmware-version: 1.6
Baseband-version: 62.50S.20.17U_2.22.19.26I
Kernel-version: 2.6.29-00479-g3c7df37
[email protected] #19
Build-number: DRC92
Click to expand...
Click to collapse
I looked through the forums here on XDA and found a laggy ICS-port, so I want to flash Gingerbread (CM7).
I've already flashed my Galaxy S, a friend's Galaxy R and my Asus Transformer tab, without any problems.
But flashing HTC-devices seems a little bit more complicated.
So what do I need to do? In the CyanogenWiki there's 'Danger_SPL' mentioned, guess I'll need it?
I don't need a looooong step-by-step-guide the correct threads or pages would be enough.
Thanks,
Lunch

need to know more about your phone, boot into bootloader mode (hold power + camera)
write down everything on this screen

DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial 0
Click to expand...
Click to collapse
(at the moment it's connected with my PC for chrarging, this should explain Serial 0, right?)
Hope this helps.

ok so even if it is rooted the radio and spl need to be updated, which recovery is on there. (power on holding home button)

Ok, I bought it like this and didn't change anything...
Recovery: Android system recovery <2e>
(blue font)

ok you want amonra's recovery found here
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
this guide will help you root and update your phone, being your phone is rooted do not flash the dreaming.nbh or you will be reverted back to android 1.0 and loose root
you want to skip that step and go to flash amonra via terminal emulator
then update radio via recovery
then update to danger spl (must have radio updated first or you will brick!)
then i recommended flashing cm5 + gapps found in this link
once you finished this and confirmed all is working you want to update radio and spl further to be able to flash the newest roms, info here:
http://forum.xda-developers.com/showthread.php?t=831139
good luck and let me know if you get stuck (also the search function in xda is great and most of your question will have been answered, peek around a bit its more rewarding than having your hand held)

Thanks a lot for your help, I'll try it!

One quick question about the Telnet-app: do I have to write flash_image recovery /sdcard/recovery.img into the left text field and 23 in the right?
Error while connecting to server: localhost/127.0.0.1:23 - Connection refused
What do I do wrong? With Terminal Emulator the command isn't found...

telnet may not work thats ok
in terminal emulator you need to give yourself superuser permissions first
type su
then say yes to prompt
you are rooted right? do you have superuser.apk in app drawer?

Yes, I'm rooted and I'm su in Terminal Emulator.
Then there's this message: flash_image: not found
But the file is on the root of the sdcard, named recovery.img ...
And when navigating to /sdcard via Terminal Emulator and typing ls I see the recovery.img-file...

if you use windows it will auto add extentions, ie if you name it recovery.img it will read recovery.img.img
try naming it just recovery
also if it came in a .zip make sure you extract it so its a .img
Sent from my HTC Vision using xda premium

No, it's definetely named recovery.img ...
Is there another possibility to flash the recovery-file (via ADB for example)?

yes adb should work fine. i cant remember the command to type when you in adb but just by typing adb into the cmd you will get a list of commands including how to push the file/image you need.
Sent from my HTC Vision using xda premium

cd <adb-folder>
adb devices
adb shell
su
adb flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Would this be possible (I can't test it now, phone is charging atm).
Thanks

that might just be perfect, but you said that didnt work from terminal emulator and a shell is nearly the same,
its worth a shot. being you are rooted you can try the orange.nbh and you will have an engineering spl where fastboot commands work and i can easly explain those (i dont use adb much but have used fastboot many time) so if adb dosent work for you check out one of the many guides out there or try ornage.nbh and fastboot
Sent from my HTC Vision using xda premium

Same message: flash_image: not found, but with ls I can see it...
Ok, my phone is rooted, I have the Superuser-app in my app drawer, I'm root when accessing the sdcard, I see the file when typing ls. What do I do wrong?
I've never run in trouble when rooting my Galaxy S or my Transformer tab. But my G1 seems quite defiant.

well not being there its hard to say, now try the ornage.nbh
youll find this file in the development section under ezterry's thread under 2708+ update 14mb ram hack. rename the image dreaming.nbh and put it on sdcard. now boot into hboot (power+ camera) and say yes to the prompt. this will allow you to use fastboot and allow you to flash recovery, radio and spl. when/if this all works then boot into recovery (home + power) and flash rom
Sent from my HTC Vision using xda premium

Ok, I'll try, thanks!
Just to go sure:
- I download orange-1.58......nbh from here: http://forum.xda-developers.com/showthread.php?t=831139 , rename it and put it onto my sdcard
- Flash it in fastboot (fastboot = hboot?)
- Flash Amon_Ra-recovery from cyanogenwiki
- flash spl (radio needed too?)
- ?

Don't want to mix in, but just some few stuff you should know:
Fastboot is a sort of recovery on your pc, although this has much more safety measures.
That .nbh file is a file that is a fresh new start to your phone: Like you have a new phone
From Fastboot you can flash a recovery, that you can take with you everywhere
The SPL/RADIO are BOTH needed to succeed. Cheers and if I made any mistakes, please point me to them

fastboot is within the bootloader. it is a .exe program in your sdk package and works similar to adb. the orange.nbh needs to be renamed dreaming.nbh and when you boot into your bootloader it will rewrite your recovery, radio, system, spl etc
the new hboot you get will have a fastboot option in it. connect the phone via usb and when in fastboot mode you will see fastboot usb in red on your phone. you will open a cmd in the same way as adb and will type fastboot devices just live adb to make sure you are attached.
the rest is explained in the op of that thread
Sent from my HTC Vision using xda premium