Database Develop

Flashing Amons recovery via Fastboot

In my G1, I cannot boot into recovery or into Android. So, I'm trying to flash Amons recovery via fastboot, which, according to the how-to, I can't, I need Engineering SPL, which I don't have. How can I fix my problem here? I have Amons recovery image in the root of my sd. and fastboot. How can I fix my problem?

Derkek said:
In my G1, I cannot boot into recovery or into Android. So, I'm trying to flash Amons recovery via fastboot, which, according to the how-to, I can't, I need Engineering SPL, which I don't have. How can I fix my problem here? I have Amons recovery image in the root of my sd. and fastboot. How can I fix my problem?
Click to expand...
Click to collapse
Search here: http://forum.xda-developers.com/showthread.php?t=566669
Now run away cause the mean people will be here shortly.

Thankyou
Thank you muchly. I've been there before but for some reason, when I went to it again, it all clicked. I needed to do this in command prompt. *runs away before the meanies come*

[Q] Nexus One dead, no screen Response

Hi everybody, I unlocked a N1 using fastboot and clockwork recovery. At the time to install the CM6 I encountered and error related to the version of de HBOOT.
I found a guide by Amritttt for reverting HBOOT to 0.33.0012, when I flashed PASSIMG following reboot the screen has become dead.
I tried to re-flash the phone with Amon_Ra recovery (1.8.1 and 2.0) but I can't enter in any mode. The only way I found is entering in the Bootloader and pushing files using fastboot... so I tried to restore the original system using the following:
PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed
Passion-VF-FRF91
with this method: uncompress, flash userdata, system and recovery.
But it did't work, in the last flash the phone hasn't the SIM inside and I realized that the trackball blincked in red two or three minutes after rebooting. So I am wondering if I have a SLCD N1 what can I do to solve this disaster??
thanks!

Look at my signature, go there, see "Unroot/restore your Nexus", reflash EVERYTHING - either with fastboot (and you need to reflash HBOOT too), or do the PASSIMG method - with FRG33, and then upgrade to FRG83.

actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch

Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks

ptrigomou said:
Thanks, I'll try. I can't use PASSIMG method because my screen ism't working, or there's other way to do?
When you say all, you refer to use "fastboot flash all FRG33" Doing that I reflash alse the HBOOT or I need to do something more?
Thanks
Click to expand...
Click to collapse
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"

bagofcrap24 said:
Can you not get your working hboot.img
boot to fastboot by Powering off
Power on by holding power & Trackball (will take you directly to fastboot)
then do "fastboot flash hboot hboot.img"
Click to expand...
Click to collapse
The hboot files i have are hbootxxxxxxxxx.nb0, it's ok?

bagofcrap24 said:
actually ignore me, that wont work for s-on, yeah, u gunna have to go through the pass-img method, completely reverting back to stock and start from scratch
Click to expand...
Click to collapse
Yeah, but my screen is not working, and ADB is not reconizing the phone. I only can send files using fastboot and the screen is not working
There is a method for doing the pass-img method using fastboot?
or maybe the only problem is the HBOOT?

OK, here we go
Download Latest Amon-Ra
http://forum.xda-developers.com/showthread.php?t=611829
copy it to your android-sdk/tools/ folder and rename recovery.img
boot to fastboot, (Power & Trackball)
open up a shell (cmd prompt) and
cd (path to sdk/tools)
fastboot devices (make sure your device is there)
fastboot boot recovery.img
your phone should boot into recovery image
use your method for flashing through adb now if you can
if you can't then try flashing the korean wwe update
hit enable usb-ms
download this, its a korean FRF91 build. it is known to have the updated 0.35.0017 Hoot in it which i believe has support for slcd displays, http://forum.xda-developers.com/showthread.php?t=722281
copy to your SD
hit trackball to disable usb-ms, go to wipe, wipe all data
then goto flash image from zip,
choose the korean frf91 that you just downloaded hopefully when you reboot you will have updated your hboot again

i tried the baove method but i cannot get the recovery .......i have the same problem my display is dead !! i have gone into recovery but i cant see it and hence cant do a wipe and flash the zip can nyone please help me!!!!

Jack gave you the response you need.
Follow the unroot/restore guide from the wiki, using the PASSIMG method:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
The long to the files is on the word "here" on step 2. Use FRG33.
This is done from the bootloader - you don't need to use recovery...
Sent from my Nexus One using XDA App

actualy i cant see anything cant see fastboot menu nor the bootloader! so i will not be able to do from step 2...please can nyone tell me wad to do?? is my fone bricked?? do i have to giv it to htc??

Its HBOOT, not recovery.

Rusty! said:
Its HBOOT, not recovery.
Click to expand...
Click to collapse
What's HBOOT, not recovery?
Sent from my Nexus One using XDA App

[Q] Is Fastboot the answer to my woes?

I want to flash a new radio and kernel to my G1 that is running CM6. My signal is atrocious and I get a few random oddities each day.
I have tried the recovery flash for the radio at least 6 times now in various ways following various guides and every time I do it it crashes my phone and I end up flashing the image, rooting, etc, to get back to CM6. it takes me over an hour to get back to normal and it just plain sucks!
So my question is..... Can I use fastboot flash to flash the image files for the radio and the kernel without being on the special Hboot 1.33.0013d and such?
I was planning to use the instructions from the ezterry kernel page and just want to check that I wont bork up my phone. I seem to recall that the fastboot flash bypasses all the need for FR-remove and such but want a second opinion before I take the dive this way.

Not trying to drive you away from CM 6, but have you tested other ROM to see if it has the same problem or similar.
I personally myself could not get CM6 to work properly on my G1 back when I was trying to use it.

I couldn't get the radio to recovery flash even on the stock ROM after rooting.
I guess I could try a different ROM.
I just now have proven to myself that i cant flash the EzTerry kernel from Rom Manager and clockwork recovery as I am in the midst of yet another image flash, re-root, and such after it wouldn't go past the reboot screen afterwards
This phone is just an extra toy but I am determined to figure it out.
I suppose I will just try the radio.img flash from fastboot tonight when I get home.
As long as I dont brick it I can always start over from scratch.

so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.

FireRaider said:
so I copied the image I want to flash onto the root of my sd card
did the camera+power boot
pressed the back key and I am at the screen with the red fastboot usb box
I plug into the computer (adb already installed and working fine) and go to the command prompt and type
fastboot flash hboot hboot-1.33.0013d.img
the screen says error: cannot load 'hboot-1.33.0013d.img'
Did I put the image file in the wrong place?
Edit: I put it in the root of the computers c: drive and typed
fastboot flash hboot c:\hboot-1.33.0013d.img
seems to have worked.
Click to expand...
Click to collapse
do the same thing with the radio and recovery

maximo360 said:
do the same thing with the radio and recovery
Click to expand...
Click to collapse
I got the recoveryand the hboot to flash but damned if I can get any radio to flash.
I get
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
this is with both version of the radio downloaded from the links in the EzTerry thread
What in the world am I doing wrong that I cannot flash a new radio?

installed the spoofSPL... didnt help
edit: Started over again from scratch, rooted, flashed RA recovery, dangerSPL, then fastbooted and managed to install the hboot and the new radio. I guess CM6 hates the newer radios.
edit: Pretty sure CM6 does hate the radio because now its hung up on the install screen.
off to do more research.

People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App

AndDiSa said:
People ... you should read before flashing around.
Ok, let me try to help.
1) As long as you have a fastboot enabled SPL, there is no need to 're-root'. Boot into hboot and flash the things you want.
2) Going to 1.33.0013d you *lose* most of your fastboot capabilities, e.g. flashing a new SPL/radio/recovery is no longer working. The only chance is to flash a signed nbh-file (e.g. fully signed rom)
I suggest you to read Terry' thread carefully (a link is in my signature) and then to retry ...
Btw: If you have installed the "new" radio/spl combo you need an adopted kernel, too, otherwise you will get bootloops.
Sent from my Gingerbread on Dream using XDA App
Click to expand...
Click to collapse
I managed to get everything work and am running CM6.1+2708 and 0013d with the .27 radio.
Why do we go to the 0013d if it screws up the fastboot? I notice in your signature you are running it also?
And say I want to flash a different rom now? I can only do it from RA recovery, Correct?
But as it stands now I ought to be able to experiment around with the other radio and other roms using recovery without any more issues? Or do they need to have certain parameters?

Once rooted, (to my knowledge) you do not required to re-root it again.
You can use RA Recovery to flash other ROMs with out having to re-root. (as to what I was told) And I recommend RA Recovery instead of ROM Manager/ClockMod Recovery (bad experience with it personnaly).
So as long as the ROM that you want to try is compatible with your current SPL/radio. You should be fine.

[Q] Cant flash Amon Ra, Recovery just shows Exclamation!

Hey Experts,
I cant 4 the life of me understand how to flash Amon Ra 2.2.1.
I have followed the wiki/Xda to run "fastboot flash recovery recovery image from Adb
It says its successful on Cmd n stuff, but i still think i m on stock reCovery
I have tried to put the recovery.img on sd card, and tried i just get a screen witha Exclamation sign with a lil android guy.
I m trying to do an nandroid backup and wipe data/dalvik b4 flashing Cm7.
Thats y i m trying to get onto Recovry:
Specs:stock 2.3.4, Bootloader unlockd (not roooted still!!)
Can som1 help? thx

Flash it from fastboot. Which I think you did anyways but that is not adb.
Then you must boot directly into recovery. If you boot up the phone it will overnight it with stock. You flash from a computer. Not from SD......
Sent from my Nexus S using XDA App

fastboot flash recovery recovery.img
Why do people have such a hard time with literally one command?

GldRush98 said:
fastboot flash recovery recovery.img
Why do people have such a hard time with literally one command?
Click to expand...
Click to collapse
Dude, unfortuantely i have already run both "fastboot flas recovery" and also somting like "fastboot reboot recovery". on bootloader-fastboot
Ok, screw Amon-Ra!! if i get into recovery(to Actually do an Nandorid and wipe), i still get the android with exclamation
Just help me do an nandroid and wipe cache/dalvik
I ll take it on from there
thx sir!

Again. Put the recovery image in the same directory as fastboot on your computer. Issue the correct exact command. Fastboot flash recovery "put the exact file name here"
Now on your phone which is still in fastboot mode.... pick the recovery option. It is that simple.....

albundy2010 said:
Again. Put the recovery image in the same directory as fastboot on your computer. Issue the correct exact command. Fastboot flash recovery "put the exact file name here"
Now on your phone which is still in fastboot mode.... pick the recovery option. It is that simple.....
Click to expand...
Click to collapse
"Put the recovery image in the same directory as fastboot on your computer"
yeah, thats the one dude ! i had that Amon Ra 2.2.1 in the tool directory. Moved it to Fastboot and flashed su.zip from recovery.Silly me i had it in Tools instd of Fastboot
Im all set with a rooted 2.3.4 with Amon Ra! thx dude
i have mrkd ur post as thx n stuff so that this thread is resolved

If you are on a stock ROM, any custom recovery (like Amon_RA) will be overwritten on every boot with the stock recovery.
To make the custom recovery stick while using a stock ROM, you need to delete (or rename) the following two files:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
... as mentioned in the first post of the Amon_RA recovery thread...

efrant said:
If you are on a stock ROM, any custom recovery (like Amon_RA) will be overwritten on every boot with the stock recovery.
To make the custom recovery stick while using a stock ROM, you need to delete (or rename) the following two files:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
... as mentioned in the first post of the Amon_RA recovery thread...
Click to expand...
Click to collapse
/system/recovery-from-boot.p and /system/etc/install-recovery.sh!!
Where do i find these files?
Do u wnt me to dwnload some market app like root explorer/astroid file mgr etc to delete them?
Is there a way faster/better way of findin em and Deleting me?
thx ~

Read the guide in Wiki. The file to flash from recovery that does just that, is there.

Jack_R1 said:
Read the guide in Wiki. The file to flash from recovery that does just that, is there.
Click to expand...
Click to collapse
Yeah. Sad thing is, had he actually read the wiki and done what it said, he would have never had to make this thread. Sigh... people will never learn.

[Q] Accidentally wiped system and now I can't boot into recovery

I followed all of the instructions in the Nexus 6 Guide to unlock, root and flash a custom recovery.
I was trying to sideload a rom into my phone and was doing advanced wipe in TWRP. I accidentally choose system thinking it would be fine since I am flashing a new rom anyway.
I think I force shut down the phone and now it just stays and hangs on the google logo. I can only get into the bootloader/fastboot. When I try getting into TWRP recovery it just flashes for a second and then attempts to reboot.
I figure I should try flashing a rom via adb bootloader/fastboot but I attempted a few times and failed. Can someone help walk me through this?
Edit: I can access TWRP recovery now... I tried doing sideload several more times but for some reason I keep getting loading rom.zip cannot read rom.zip

Well i going to geuss you know to to get to recovery though bootloader thought your phone
But your phone is semi Bricked
You can download wugs toolkit
And i will show unroot/flash stock you will click bootloop/ bricked and go though the steps
And it will download the stock software and reovery and go though the steps you will be fine
If you want use the same toolkit and root and install twrp again

Do you use a USB otg drive? If you don't you can send a rom to twrp using some commands.
Try to redownload the ROM that won't work and put it on the phone via a USB otg drive or using your pc and don't forgot gaps.

If you're not, use the WUG toolkit to reflash the stock ROM. Then you can use that to flash your new ROM

Unless im missing somethimg, why not just flash the factory image through fastboot and start over?

Like mentioned above, or just flash TWRP in fastboot. Then boot into TWRP, and flash ROM.