Database Users

Help trying to flash amon ra

i am trying to flash amon ra,s recovery image on my nexus one. i have unlocked it and rooted. for some reason it keeps on telling me file not found. iam doing this thru the treminal app. is there any other way of doing it ?

go to Amons recovery page.... he has posted lot of ways to flash it...... if all fails come back here and ask.......

chowdarygm said:
go to Amons recovery page.... he has posted lot of ways to flash it...... if all fails come back here and ask.......
Click to expand...
Click to collapse
ive already did that still wont install

go to Amons recovery page.... he has posted lot of ways to flash it...... if all fails come back here and ask.......
Click to expand...
Click to collapse
ive already did that still wont install
Click to expand...
Click to collapse
Oh... thats really sad... did u rename the recovery image as per the commands u r giving ?
-------------------------------------
Sent via the XDA Tapatalk App

chowdarygm said:
Oh... thats really sad... did u rename the recovery image as per the commands u r giving ?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
yea is there a way of flashing it thru terminal on mac? like the way i unlocked it and rooted

helpppppppp

flashboot-mac flash recovery recovery-RA-nexus-v1.7.0.img
is this wrong?

Hey man, it sounds like either you don't know how a filesystem works, or how a terminal works. Unless you skipped the step on downloading fastboot-mac. If you didn't skip that step, you need to actually change into the directory where you downloaded that file to be able to run it.

If you have fastboot installed. Make sure you have the recovery.img file in the same directory as fastboot to flash. Preferable in the 'tools' directory.

timal said:
If you have fastboot installed. Make sure you have the recovery.img file in the same directory as fastboot to flash. Preferable in the 'tools' directory.
Click to expand...
Click to collapse
Or you can just do fastboot-mac flash recovery *drag image onto terminal window*

I believe when you flash through terminal on mac it should be ./fastboot flash recovery ./recovery-RA-nexus-v1.7.0.img

mich11128 said:
I believe when you flash through terminal on mac it should be ./fastboot flash recovery ./recovery-RA-nexus-v1.7.0.img
Click to expand...
Click to collapse
I completely forgot about that! I modified my bash_profile so all I have to do is type adb or fastboot and then the command.
Instructions here:
http://forum.xda-developers.com/showpost.php?p=5691126&postcount=319

oh ok I hadn't tried that when I first rooted so I just stuck to typing out "./" but that's good I'll give that a try in the future

Need Help on HK version HERO OTA update ><

Hello Developers,
I am a HK Version Hero user. My region started the OTA 2.1 update for HERO.
I have already restore my Nanbackup to the first 1.5 backup.
When it finished the download, my phone reboot to the recovery mode and start the update and prompted:
E:No signature (231 files)
E:Verification failed
Installation aborted.
My need rom version should be 2.73.721.91.
Anyway that I can update to the new stock rom?
Thanks for the help !!

I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again

hero-err said:
I got the link for the first OTA download, but I am a new user I cannot post it out.
Is it I just delete the recovery.img file? and it will work?
Thanks again
Click to expand...
Click to collapse
No, you'd have to re-sign the zipfile. If a file is added/removed or editted, the hashes don't match anymore and no one will be able to flash it.
Learn how to re-sign, or just upload it @ multishare as-is, and request re-signing of it. Mayb someone will help you out .

just take the recovery img out of the ruu and flash it then try to update.Should work then

I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?

sundrik said:
I have the same problem. I really didnt understand what you just said..
My file is a .zip and can not be flashed with flashrec.
can you explain better for a n00b like me?
Click to expand...
Click to collapse
you don't flash files with flashrec, you flash them from recovery mode.
and just because something is a .zip doesn't mean it can be flashed. it has to be signed with the appropriate update script.

It like this.
I got an OTA for the 2.1. This generated an error when updating. So i thought i just download the file and do it from recovery mode.
Downloaded the file from here: liveimage.htc.com//OTA_Hero_ChungHwa_3.31.751.1_R-2.73.751.13_release048gnt2ecw16ubyr.zip
The link is not active anymore.
But i still get the same error.
I tried to do a factory reset and do the update after that, but without any luck.
I know this is the update for my phone, but i cant do it. And you guys speak about signing the file before, but i dont know how.
Probably same error for topic starter.

to do what i said you have to boot the phone in recovery.take the files out of the update.zip (or if it a RUU go HERE) in the .zip file should be boot.img,recovery.img,userdata.img,system.img,HBOOT and a few others....
Take out the recovery.img
and flash via fastboot (turn phone one holding back)
open cmd window (windows key + r) type cmd
fastboot flash recovery (drag and drop recover.img into cmd window) press enter
Then try updating

I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.

sundrik said:
I dont get it to work.
I take out the recovery.img
Turn the phone on by holding 'back' while power on. (Screen with three android skaters)
Then i plug in the usb.
The text 'FASTBOOT' change to 'FASTBOOT USB'
Open cmd (windowskey + r and type cmd adn enter)
Drag and drop the recovery.img to command window and press enter.
This makes the DVD burning application on the computer to start and wants to burn the file.
Click to expand...
Click to collapse
Maybe you should use fastboot - the program for your pc?
The steps that were told to you were right, but I think you didn't do the last one as you should. Once in the command-line, you have to type "fastboot flash recovery " (yep, there's a space at the end) and then write the path of the recovery image (i.e., if it's in C:\asd\recovery.img, it would be "fastboot flash recovery \asd\recovery.img"), or drag and drop the file to the cmd, and it will write the path.

You know where to get this fastboot program...
I only find this from 2008. Should be a better one with not so much tweaking?
http://forum.xda-developers.com/showthread.php?t=463627

Nope, not really, I use linux.

Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)

hero-err said:
Thanks for all the help!! I finally upgraded.
I restore to my 1.5 backup and down the update part by part.
I pull out the recovery.img and zip it back and re-sign it, copy to my phone and rename it to Update.zip and flash the first part. Reboot and copy the OTA2 to the phone and also rename it to Update.zip, flash it again. Final reboot, its now the official 2.1 android update. Also the root is still there.
OTA1
Badongo file 23546527
OTA2
Badongo file 23546783
THANKS again!!!
(sorry about the link, they won't let me post it ><)
Click to expand...
Click to collapse
PM u, thank you.

Could you tell me the Second HK OTA Package filename?
I really need it, if anyone who know it, please tell me.
Thank you very much.

hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !

hello, I flashed RUU_Hero_hTC_Asia_HK_WWE_3.34.721.1_R_Radio_63.18. 55.06P_6.35.15.14_release_signed on my taiwaan hero using goldcard and now i cannot flash my RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river. . . please help me! it says error - invalid update tool! WTF ... i have used that ruu many times but now it aint working. it strucks at updating signature.
and even the flash recovery software aint working !

I think u need to restore it back to your 1.5 backup first.

Thanks for Hero-err.. I have solved my problem too by following his hints ^_^

i dont have flashed recovery so how would i do nandroid restore ?

Downgrade 2.1 > 1.5

Anyone ran the RUU and successfully downgraded this phone? If so how did you do it?
Tryed all the old methods to no success.

Are you the guy who commit Hero suicide for the benefit of the community?... Or have i made that up?
If you aren't,.... WHY ON EARTH DID YOU INSTALL 2.1 RUU?!??!?!?!?!!?
If you are,... BRAVO!!!!
Ok.... You've probably tried all this, but these are the things I would try if in your possition,...
Try installing custom recovery using flashrec latest?... if fail, try an older version of flashrec, 1.1.2 i think?
Fail?
Try flashing recovery through adb ...
Amon_RA said:
Code:
Copy recovery-RA-hero-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Click to expand...
Click to collapse
Fail?
Amon_RA said:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.6.2.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb shell reboot
Click to expand...
Click to collapse
NO?
Then I would start researching to see if you can modify the RUU and maybe put in the boot images from a 1.5 ROM to put into the 2.1 RUU?

.... try flashing the system.img,boot.img and recovery.img from a 1.5 RUU through adb or fastboot then try downgrading again.

Check this out for instructions on how to extract stuff from an RUU,....
Extracting ROM files from a HTC Android RUU

ddotpatel said:
Are you the guy who commit Hero suicide for the benefit of the community?... Or have i made that up?
If you aren't,.... WHY ON EARTH DID YOU INSTALL 2.1 RUU?!??!?!?!?!!?
If you are,... BRAVO!!!!
Click to expand...
Click to collapse
Correct. I did install the RUU as I want to keep trying for fixes to downgrade.
Just for info, tried replacing few files in the rom.zip but now it comes up with signage errors. Theres no way to sign that file.

I do have some ideas, but I'm not hopeful.
I'm on my phone ATM so I will tell you them when I get home.

Could you boot into hboot and tell me what you see? (volume down + power)

42turkeys said:
I do have some ideas, but I'm not hopeful.
I'm on my phone ATM so I will tell you them when I get home.
Click to expand...
Click to collapse
Don't forget to post. thanks.

42turkeys said:
Could you boot into hboot and tell me what you see? (volume down + power)
Click to expand...
Click to collapse
HBoot mode
if sdcard contain heroimg.zip device try to flash
"Loading...[HEORIMG.zip]"
working working
and then - "Main version is older! Reboot? y/n"

I mean the options you get in hboot.

42turkeys said:
Could you boot into hboot and tell me what you see? (volume down + power)
Click to expand...
Click to collapse
42turkeys said:
I mean the options you get in hboot.
Click to expand...
Click to collapse
<BACK> Fastboot Mode
<SEND> SimLock

Syrop said:
<BACK> Fastboot Mode
<SEND> SimLock
Click to expand...
Click to collapse
The fake ota method wont work then
No devs will really try & do this, because you can still downgrade from the ota which is what users will have done. sorry.

42turkeys said:
The fake ota method wont work then
No devs will really try & do this, because you can still downgrade from the ota which is what users will have done. sorry.
Click to expand...
Click to collapse
What should we see if we could do a fake ota? I have tried allsorts to overcome the locks but nothing.

andrewb84uk said:
What should we see if we could do a fake ota? I have tried allsorts to overcome the locks but nothing.
Click to expand...
Click to collapse
You can only do a fake ota if HTC updated the stock recovery & spl but they haven't so you can't do it.

42turkeys said:
You can only do a fake ota if HTC updated the stock recovery & spl but they haven't so you can't do it.
Click to expand...
Click to collapse
So are you saying he still has the older recovery and spl?
.... would he not be able to update recovery and spl to newer one (by extracting from new ROM and flash through adb/fastboot), then try your "fake ota" method?
EDIT...I HAVE NO TECHNICAL KNOWLEDGE WHATSOEVER... PLEASE DONT SLAG ME IF IM NOWHERE NEAR CLOSE TO A SOLUTION.

so ur saying that those who recieved the OTA update can downgrade back to 1.5? please do tell me how!! im on european hero and got both updates OTA and ive tried using the ROM.zip and then the volume down and powering up, it tries to read the ROM.zip but says that it doesn't detect any img files, i have opened the ROM.zip file and checked for the img files and they are all there

Notn4 said:
so ur saying that those who recieved the OTA update can downgrade back to 1.5? please do tell me how!! im on european hero and got both updates OTA and ive tried using the ROM.zip and then the volume down and powering up, it tries to read the ROM.zip but says that it doesn't detect any img files, i have opened the ROM.zip file and checked for the img files and they are all there
Click to expand...
Click to collapse
use the Europe 2.73.405.5 ruu from http://shipped-roms.com/shipped/Hero

where do u see a europe RUU? i found only ASIA RUSSIA and WWE
and ive tried downloading the official RUU from HTC support site with my device S/N, that was from the european HTC site...

Cant hurt to try the wwe version i suppose.

HTC have done good this time.
Methods attempted:
Run old RUU using Goldcard and hope it flashes - FAILS
Extract rom.zip from RUU, rename as HEROIMG.ZIP and HBOOT - FAILS
Try to send the zip via fastboot update - FAILS
Get adb access in recovery - FAILS (HTC have disabled this)
Unrevoked root exploit for 2.1 - FAILS
Edit the rom.zip/HEROIMG.zip and pretend that an old RUU is a new version - sigfails
Methods not attempted, which I doubt will work:
Extract rom.zip from RUU, rename as update.zip, try and flash through HTC stock recovery.
Try to use some OTA update.zips offically signed by HTC to downgrade.
Methods which MAY work:
ring0 exploit was fixed after the 2.6.29 kernel, if HTC/Android haven't patched this, I could compile it using the NDK/ Arm Compiler and hope for the best.
hope for a race condition by adb recovery (see: http://unrevoked.com/rootwiki/doku.php/public/adb_in_recovery )
hotswap the sdcard during update.zip signature verification. I found this out here: http://unrevoked.com/rootwiki/doku.php/public/adb_in_recovery

[Tutorial] Restoring Recovery Mode while working only Fastboot Mode*ALL METHODS HERE*

Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot​
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot​ checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD

hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance

Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery

ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.

WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.

lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is

lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support

Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.

Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.

behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App

i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be

ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
​
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)

hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?

try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd

ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?

breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.

AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho

I am hanging at booting while trying to do this any ideas?

Semi-Bricked myTouch 4G

Alright I have a semi-bricked mytouch 4G. (a friend's phone) I followed the gfree guide and did the hboot flash and now I'm in a boot loop. I have the original boot screen loaded and I can get to the recovery menu. S is off so the phone is rooted. How do I get CWM on the phone so I can install a new ROM and kernel so I can unbrick this thing. With my verizon fascinate I have options to go from where I am stuck (Odin and .md5 files). Where do I go from here? Can somone give me a step by step without pointing me to a different forum? I have searched for more than a couple of hours and this is where I have found myself.

Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.

darinmc said:
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
Click to expand...
Click to collapse
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.

fsuagentsmith said:
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
Click to expand...
Click to collapse
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.

neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
I get sending recovery failed... any help from there?

fsuagentsmith said:
I get sending recovery failed... any help from there?
Click to expand...
Click to collapse
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?

neidlinger said:
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
Click to expand...
Click to collapse
yes, I see that

fsuagentsmith said:
yes, I see that
Click to expand...
Click to collapse
ok I changed it to that screen on the phone while trying to push the recovery image. It worked!!!

Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.

neidlinger said:
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Where is the reboot recovery option? As I said in original post I'm familiar with Samsung Galaxy and CWM not so much this phone.

fsuagentsmith said:
Where is the reboot recovery option?
Click to expand...
Click to collapse
are you in Recovery or in Hboot? what color is the screen? black or white?

neidlinger said:
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
Click to expand...
Click to collapse
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?

neidlinger said:
are you in Recovery or in Hboot? what color is the screen? black or white?
Click to expand...
Click to collapse
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?

fsuagentsmith said:
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
Click to expand...
Click to collapse
Awesome!!! I see what you told me to do! When I select recovery this is CWM 3! Awesome. I will see where I can go from here. I still may have questions.

fsuagentsmith said:
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
Click to expand...
Click to collapse
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.

neidlinger said:
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
Click to expand...
Click to collapse
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.

fsuagentsmith said:
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
Click to expand...
Click to collapse
glad to see you got it going.
just make sure to do nandroid backups prior to flashing any new Kernels and make sure they are compatible with AOSP 2.3 ROMs.

neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down

steb0ne said:
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
Click to expand...
Click to collapse
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App

Nicgraner said:
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Well, I was rooted and had been running the leaked 2.3 stock rom. Decided I wanted to try CM7...and flashed it and it appeared to flash okay b/c I was able to boot up, but I couldn't get gapps to install, so I ended up trying to restore from my backup, and that failed, and I couldn't get back to CM recovery. So, I'm stuck in a constant boot loop.