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.
Related
My G1 is stuck on Amon RA recovery....I tried to use firerat's method and after i flashed foroyo rom its stuck in the recovery...but it doesnt show any options...
Just
Build : RA-dream-v1.7.0
thats it i cant do anything....
i know i didnt brick my phone...please help...
[Solved]
solution : install fastboot and you can erase the system...
C:\\ .......android-sdk-windows\tools\fastboot devices
C:\\ .......android-sdk-windows\tools\fastboot -w
C:\\ .......android-sdk-windows\tools\fastboot flash recovery [recovery path with ".img"]
walla your recovery is overridden by the new one...
Most likely you did not completely follow the instructions how to install mtd, but nevertheless what SPL do you have installed? If you have 1.33.2003 I suggest to flash recovery again using fastboot and you are rescued.
Otherwise ... I don't know. Even if you are able to connect via adb I do not expect you can flash a new recovery while beeing in recovery. For sure you are able to go into bootloader install dreamimg.nbh, etc. but this would mean to do the hole rooting process again.
AndDiSa said:
Most likely you did not completely follow the instructions how to install mtd, but nevertheless what SPL do you have installed? If you have 1.33.2003 I suggest to flash recovery again using fastboot and you are rescued.
Otherwise ... I don't know. Even if you are able to connect via adb I do not expect you can flash a new recovery while beeing in recovery. For sure you are able to go into bootloader install dreamimg.nbh, etc. but this would mean to do the hole rooting process again.
Click to expand...
Click to collapse
thankx man for replying....i kinda fixed it ...i followed this step
http://forum.xda-developers.com/showthread.php?t=807183&page=13
post number 160
but afte i Flash FR-recovery-v1.5.3-CustomMTD_S.zip and reboot to recovery my amon recovery goes blank...kinda funny....
actually you can do anything with fastboot...erase system...flash recovery...i couldnt flash a rom..but was able to override the recovery....that all i needed...
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
Hi XDA, as title says, i cant get boot into recovery...
I have an HTC Dream (Spanish version of G1), and Im having problems with the recovery boot.
I have root done on the phone and i've tried to install a new recovery via Clockwork app, adb shell, also via Fastboot and via "RECOVERY FLASHER"...
All of them look to finish succesfully, but I still cant boot onto recovery.
Every time I try to boot on recovery, the phone gets hang on the company logo... until I get out the battery to turn it off.
I dont know what can I try more...
Any idea ?
Thanks
If you cannot boot into recovery by holding down Home and Power, then you're bricked, I believe. What were you trying to do?
Sent from my HTC Dream using XDA App
I can boot normally, and I run apps that need root correctly, but I want to boot into recovery to flash a custom ROM...
Clockwork mod needs to reboot into recovery to reflash a Custom ROM, so I cant get another rom that way neither.
Any idea (again)?
Do you have terminal on your phone? Download amon RA recovery 1.7.0 for HTC Dream and use that instead Clockwork because it is most recommended. Rename it to recovery.img and move it to the root of your SD card.
Go to terminal on your phone and type:
cd sdcard
flash_image recovery recovery.img
Now try to boot into recovery mode.
Sent from my HTC Dream using XDA App
If you have root access, then you can try to (re-)install your recovery image using adb.
Open a shell using the command
adb shell
and then from there you can try to flash the recovery image by entering
flash_image recovery recovery.img
where recovery.img is the name of the recovery image you want to install and it should be located in the current directory.
Edit: two people same ideas ... ;-)
Both things re-done...
Nuthin'
Anything else ?
Thanks for the answers anyway
Bump...
Any help ?
Fastboot is working for me, but I have the default SPL and I cant use "fastboot flash new_recovery.img" ---> Not allowed.
Theres a way to flash another SPL using phone terminal, or using fastboot ?
Thanks
I'm not sure, but if I was in the same boots as you, I would download the DREAIMG.nhb and flash that in fastboot. Once done, you'll be on Stock RC29. Yep, you're going to have to root again and re-install a custom recovery.
This is also safe to do since you're on HBOOT-0.95.000.
Sent from my T-Mobile myTouch 3G using XDA App
removed ...
Thanks for everything guys...
But now im looking for a "Howto unbrick G1"...
I dont have fastboot, recovery boot or normal boot...
Alright, I give up.
I've wasted one full day and all I do is keep going in circles. I have an unlocked bootloader but I am not able to flash custom recovery to it. When I do:
fastboot flash recovery recovery-RA-passion-v2.2.1.img
it is successful but am having the problem mentioned here:
"Make sure that init.rc isn't calling any install-recovery.sh script, otherwise you'll boot back to stock recovery (exclamation mark with a little Android)."
http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638
So, no custom rom because I cant turn off verification in order to flash custom rom zip file. Now the problem is that I can't even fix this problem because I don't have root so I can't delete the following files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
When I try adb shell it keeps saying "permission denied"
It gets better - I've managed to mess things up royally even further. I tried flashing FRG83 system image using "flashboot update update.zip". It was successful but now my phone is going in boot loop!!
Can someone please help me before I lose hope in humanity?
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
You can either flash a pre-rooted GB, flash the su.zip and then you'll have su access to delete the files when in system or adb, or flash this zip which will remove the two files...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA App
danger-rat said:
Recovery is only restored when you boot into system, so the idea is that you flash recovery, and go straight into it via the on phone menu, and then install what you need to...
Click to expand...
Click to collapse
I totally did not know this. Thanks a lot buddy
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
revery0 said:
My phone is almost bricked
I was trying to install sevenrov v3.2 while i was on v3.1 and i ****ed up everything while doing a fullwipe
Right now there is only fastboot&rescuemode available
twrp is not working, because it does no read the digitizer(i cannot press anything)
i can install cwm but should i ?
I believe that is best to flash images through fastboot.
But what images should i flash?
Where to find them?
How should i flash them?
Click to expand...
Click to collapse
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
arthios said:
Oh dear! You are in a mess. All I can suggest is that you flash the stock recovery and then install a stock ROM for your phone using the force update (dload) method that has been described in other threads. Then you can return to a custom ROM of your choice. As far as I know CWM for this phone is only in Chinese so it may be of little value unless you understand the language.
Click to expand...
Click to collapse
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
revery0 said:
cwm has english also but it has no use for me
Only fastboot works
dload method does not complete, the blue progress bar goes up to to 85% and stays there forever...
I am looking for a mathod to create a flashable zip for fastboot
to use fastboot flash filename.zip command
or flash each partition seperatly , i tried the method with huawei extractor
extracted the images system,root,boot,cache,cust,userdata
flashed each one on their partitions
but without success
Click to expand...
Click to collapse
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
87insane said:
Why you do not flash twrp recovery in fastboot mode and then install a flashable ZIP?
Edit:
In this thread, are the same probs:
http://forum.xda-developers.com/showthread.php?p=56634210
Short: install recovery and try to flash a rom again.
I See your post in this thraed that this not work for you but i think you have to try it again. In fastboot mode you can flash recovery and cust. Its that working?
Can you explain step by step what are you doing?
Click to expand...
Click to collapse
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
revery0 said:
First of all thank you,
Right now my phone is in a bootloop(not more than 6 sec duration, with short vibration)
3 buttons , power button tricks and combos don't seem to work
The only way to exit the bootloop is by sending the fastbbot reboot recovery command and wait for some loops while you are doing the vol+vol-power combo
Then the phone enters fastboot rescue mode
I get reply when sending the fastboot devices command,
And the phone has unlocked bootloader (OEM command)
I can flash images extracted from the official 135 ROM
I tried cust boot user data system cache recovey , and the are all flashed correctly
But I can't get into recovery mode aftethe reboot (yes I am doing the 3 buttons trick)
I tried different SD cards with different update.app each time, from b135 official and sevenrom3 (yes I put them in /dload folder)
I even tried flashing cwm and twrv recovery images in the recovery partition, but I got in a bootloop after the reboot again
So I am asking if there is anyway to flash the partitions correctly from fastboot or maybe send a kernel image with some offset and run it with the fastboot command
Of course adb does not work, not responding
Maybe reparation the storage?
I don't know
And I am desperare...
Click to expand...
Click to collapse
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
87insane said:
Okay...
your system is so messy. we must bring fully to factory condition first time.
Plesse try to flash stock recovery img. (In your post you write only that you have tryed twrp/cwm).
And then try update in recovery.
I not think your phone is broken. You can try my tool (http://forum.xda-developers.com/asc...eandadjust-t2941186/post56774286#post56774286). There is a stock recovery img in it. In your case you have to flash cust img to.
Click to expand...
Click to collapse
Thank you but I already did flash the official recovery image, both extracted from a factory update.app and your recovery.IMG also... None of them worked.... Iam still in the same bootloop.
I am starting to believe that the partitions have been ****ed up.
Any way to repartition?
Also is there a procedure to create a flashable zip with huawei software extractor? I edited the accompaning XML to add the p7 device on the list (copy data from p6 and changed the name) created the zip but fastboot doesn't flash the zip because its missing 2 XML files which I can't remember their name.
And at this point I would like to give my 2 cents of advice to everyone who might listen,
Before you flash anything from a microsd, first verify the card with h2testw, and always use high quality microsd and never ever stop a flashing procedure by any means. . i would like to make it more extreme and advise to use a software with copy verification (like richcopy) when you copy files that are going to be flashed.
I tend to believe that a faulty microsd is the cause of my problems... Even though I checked the microsd afterwards and didn't got any errors.
I would advise the ROM creators to append this on their posts!