I did the root without unlocking bootloader method up to the point before flashing the amon RA. I downloaded ROM Manager and installed it that way. When I reboot after installing via ROM Manager and go into recovery it works. If I power down and then back up again (holding vol down, choosing recovery) I'm back at stock recovery. Is this normal? If not, how do I get it to ALWAYS go to my custom recovery ROM?
It's normal. You need to rename your install_recovery.sh so that it doesn't run on bootup. It is in /system/etc/install-recovery.sh
OutlawPro said:
It's normal. You need to rename your install_recovery.sh so that it doesn't run on bootup. It is in /system/etc/install-recovery.sh
Click to expand...
Click to collapse
I'm so new to this... Can you explain in further detail how to rename it? I don't know where to find or how to access "/system/etc/install-recovery.sh".
Related
hey guys i finally finished unlocking the bootloader on my 2.2.1 FRG83D build N1 but i couldnt get recovery.img to push to the N1 through adb.second option was to run "install-superboot-windows" for FRG83D build on bootloader screen from PC,soon as i did that N1 booted to the phone and i checked in the app menus and i have the latest "SUPERUSER" app.i really want to flash custom ROMS now.DO I HAVE RECOVERY or how do i get recovery now cuz i really wanna get started with flashing custom roms.any suggestions would help.thanx
1. Get a teminal emulator from the market and reboot recovery. or
2. Get quick Boot from the market and install/use that to boot into recovery or
3. Power down the phone and push the trackball+power to boot into recovery
If none of those 3 options work for you, your recovery did not flash and you will need to either reflash it. (making sure fastboot sees your phone with fastboot devices)
Or you could download ROM manager from the market. Using that, you can install clockwork recovery from the app itself.
Know-Fear said:
1. Get a teminal emulator from the market and reboot recovery. or
2. Get quick Boot from the market and install/use that to boot into recovery or
3. Power down the phone and push the trackball+power to boot into recovery
If none of those 3 options work for you, your recovery did not flash and you will need to either reflash it. (making sure fastboot sees your phone with fastboot devices)
Or you could download ROM manager from the market. Using that, you can install clockwork recovery from the app itself.
Click to expand...
Click to collapse
i dont think i have any recovery,i just tried installing clockwork recovery and try to get in the recovery,it froze my N1 and i had to hard reset the N1.
Flash the recovery via fastboot, not adb...
Sent from my Nexus One using XDA App
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
Monday i receive my IncS, as im making the switch from a iPhone.
So iv'e been reading in here to learn about Andorid and how to flash custom ROM.
However, I have a question after reading various strings in here, and I'm sorry if it's stupid one...
I will get S-OFF with a XT-Clips, so i can install a custom ROM.
But how about Recovery?
Is it enough to install madmaxx82 4EXTRecovery to be able to boot into Recovery by pressing Power and Vol down?
Or do i have to install RomManager also to be able to boot into Recovery, so i can flash .zip's?
And where is the Recovery image stored?
That's all for now ;-)
If you have a software version lower than 2.30.405,1, you can root and s-off without a xtc clip. You can install the 4EXTRecovery and get into recovery with power and vol down. I'd recommend installing clockworkmod so you can use rom manager with it. Rom manager also lets you boot into recovery,
Do you need to install clockworkmod for booting into Recovery and flash 4EXT Recovery?
Or can you boot into Recovery with a new phone and flash 4EXT?
I guess my question is, if you have a new phone, how do you boot into Recovery to flash madmaxx82 4EXT?
When i boot a new phone with power and vol down and choose Recovery, i get a a red triangle with an exclamation.
PerP DK said:
I guess my question is, if you have a new phone, how do you boot into Recovery to flash madmaxx82 4EXT?
When i boot a new phone with power and vol down and choose Recovery, i get a a red triangle with an exclamation.
Click to expand...
Click to collapse
If you get a recovery image this is in a zip file, then you simply copy it to the root of your SD card and rename it PG32IMG.zip. Then the next time you boot into bootloader mode, it will find the PG32IMG.zip file and install it.
Then you can get into recovery.
tpbklake said:
If you get a recovery image this is in a zip file, then you simply copy it to the root of your SD card and rename it PG32IMG.zip. Then the next time you boot into bootloader mode, it will find the PG32IMG.zip file and install it.
Then you can get into recovery.
Click to expand...
Click to collapse
Thank's, now i get it, and im ready to get started ;-)
I apparently flashed a bad .zip file that won't load, and now all I can do is sit at the Motorola logo. I've tried the hard reboot with power+vol up and down but, for whatever reason, that won't reboot to the bootloader like it used to. So, I can't get back into recovery at the moment. I can ocassionally get it to reboot to the fastboot menu, but I don't know what commands or anything to use to get me back to recovery. If I could just get back to the recovery I would be fine because I have a few older ROM zips I could flash.
Can anyone give me some advice on what to do here? My computer has ubuntu, so I'm not sure if Myth tools or anything would work?
Parham112 said:
I apparently flashed a bad .zip file that won't load, and now all I can do is sit at the Motorola logo. I've tried the hard reboot with power+vol up and down but, for whatever reason, that won't reboot to the bootloader like it used to. So, I can't get back into recovery at the moment. I can ocassionally get it to reboot to the fastboot menu, but I don't know what commands or anything to use to get me back to recovery. If I could just get back to the recovery I would be fine because I have a few older ROM zips I could flash.
Can anyone give me some advice on what to do here? My computer has ubuntu, so I'm not sure if Myth tools or anything would work?
Click to expand...
Click to collapse
You can do the following while on bootloader (Volume DOWN + Power button):
fastboot flash recovery recovery.img
Where recovery.img is your custom recovery image. Just make sure is in the same folder that your fastboot archive. After this, you should be able to access to recovery and flash another ROM.
OR... You can flash to stock with RSD Lite and then do everything again.
Use Myth Tools to flash stock ROM or recovery.
So im running CM12.1 and im trying to flash the CWM recovery i used for installing CM and i can get into fastboot mode and flash it, but then every tutorial says then go into recovery through the UI on the screen, but my bootloader screen is just black and obviously cause im in fastboot mode i cant boot directly into recovery without rebooting the device which will reflash the stock recovery
What can i do?
Cheers
Reboot and press the volume keys up and down simultaneously to boot into recovery.
I have cm12.1 but the problem is, the recovery is showing black screen. I tried flashing from fastboot twrp image file and xzdualrecovery only to cause boot loops.
Is there any method to install recover on cm12.1 without causing bootloops?
Sent from my Nexus 7 WiFi using Tapatalk
Try this.
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Sent from my Nexus 7 WiFi using Tapatalk