Hi,
According to many articles I've read, stock Android rewrites the recovery partition with a stock recovery image at each boot. So to make a custom recovery stay we're asked to remove a file called "recovery-from-boot.p" in /system which does work.
But WugFresh's Nexus Toolkit flashes a file called "perm-recovery-signed.zip" to make it say. And to revert to stock recovery, it downloads and flashes the stock recovery image and then flashes a file called "undo-perm-recovery-signed.zip".
I'd have guessed just flashing the zip would make the ROM replace the Custom Recovery with the Stock version. Why does it flash the recovery? What do these files do?
Clarification is appreciated.
Thanks.
Related
Does TWRP recovery for the One S (S4) T-Mo require me to flash a seperate boot.img when I flash a rom, say Trickdroid v8.0? I want to flash either CM10 or Trickdroid but I'm not sure if TWRP will automatically access the boot.img in the ROM.zip. Any help would be greatly appreciated:fingers-crossed:
try just flashing the .zip and if it doesn't work then boot back into recovery and wipe then boot into bootloader -> fastboot, extract the files from the .zip on your computer, then flash the boot.img manually through fastboot, then boot into recovery and install the .zip. trial and error. it's how we learn
p.s. i know that cwm recovery automatically flashes the boot.img but twrp might not
Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks
You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.
So i flashed back to stock using Odin, took the three updates to fp8, but now when i flash cwm it doesnt take.... always goes back to Android recovery. What am i doing wrong??
Thanks guys for all your continuing support with this device!
You need to boot directly into recovery after odining cwm recovery - there's a script that runs (/system/etc/install-recovery.sh) that overwrites recovery with stock when you boot up - you need to remove/rename/disable that script (either while in recovery or after flashing superuser/supersu so you can have write access to /system after booting, though the latter approach requires you to again odin recovery once you are done) to make the custom recovery "stick". Hope that helps
dwitherell said:
You need to boot directly into recovery after odining cwm recovery - there's a script that runs (/system/etc/install-recovery.sh) that overwrites recovery with stock when you boot up - you need to remove/rename/disable that script (either while in recovery or after flashing superuser/supersu so you can have write access to /system after booting, though the latter approach requires you to again odin recovery once you are done) to make the custom recovery "stick". Hope that helps
Click to expand...
Click to collapse
TOtally worked!! Thank you!
I flashed CWM in odin,but when i boot up into CWM it boots the stock recovery.Also,do i need to flash the bootloader and radio if coming from 4.1.2? I must be getting old..I did it on my last relay,but i don't remember how.Do i have to flash the bootloader first?
Thanks
The 4.1.2 stock image apparently has code within its start up routine to overwrite a custom recovery if one is detected at boottime. After flashing with ODIN, did you reboot into the system, or did you directly boot into CWM? If you're on 4.1.2 stock, there will be no need to update the bootloader or modem, you're on the latest. Try flashing CWM, and then immediately booting into recovery. You can also delete the files Stock calls to reflash the recovery from the image once you're able to get in via CWM, and utilize adb.
Magamo said:
The 4.1.2 stock image apparently has code within its start up routine to overwrite a custom recovery if one is detected at boottime. After flashing with ODIN, did you reboot into the system, or did you directly boot into CWM? If you're on 4.1.2 stock, there will be no need to update the bootloader or modem, you're on the latest. Try flashing CWM, and then immediately booting into recovery. You can also delete the files Stock calls to reflash the recovery from the image once you're able to get in via CWM, and utilize adb.
Click to expand...
Click to collapse
Yes,i booted into the system,then restarted into CWM...I'll try reflashing,and booting right into recovery and let you know,Thanks for the reply!
Yep,that did it...Got it up and running..Thanks again Magamo..
I have a N5 rooted and with custom recovery.
I plan to install the factory image via fastboot.
I don't want to lose my userdata, so I plan to extract the different .img files and flash them one by one (except userdata.img)
Can I not flash recovery.img so I can keep my custom recovery?
What are the .img files that I must flash for keeping my files, settings and my custom recovery?
Thank you on advance. You are the best!
I flashed the system and boot img's
Then booted into recovery and wiped caches
Then flashed the modified kernel for root and supersu 2.19 before booting and I've kept data and recovery fine
This boot img - http://forum.xda-developers.com/showthread.php?p=56702681
Sent from my Android 5.0 Nexus 5
Do I need other kernel for being able to root? I was only thinking of installing superSu for getting my root back.
Then, the only .img that I need to flash are the system.img and the boot.img. Am I right?
Thank You!
You need the other kernel, cf-autoroot does this for you.