Can I flash CM boot.img with this?
https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Also do the new nightlies have TWRP or CWM?
Or this:
https://play.google.com/store/apps/details?id=com.cgollner.flashify
No. And even if you could, your phone would refuse to boot until you flashed a stock kernel again (in case you have locked bootloader, and probably have -- otherwise you would just flash the desired kernel directly through fastboot)...
Related
I went back to odin to get a fresh of my gs3. I did the 4.1.1 update and now i have an issue.
I can't seem to install any recovery on my samsung galaxy s3 in order to root it.
I have tried just about all the downloadable clockworks out there and even tried twrp...its no go. I do not know why this is happening because I never had this problem before when rerooting my gs3.
Any one faced this before? suggestion?
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
bikrame said:
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Click to expand...
Click to collapse
I do, personally I only flash via odin....root66...is that a rom? how do I flash that without rooting?
Aerowinder said:
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
Click to expand...
Click to collapse
I am not quite sure what you are saying here about needing to access recovery mode after I flash...I flash the clockwork recovery mode and when i go to access it, i only see the stock.
I i reflashed odin again and decided to root using 4.0.4 ics...now it worked..I guess we can't flash over 4.1.1 anymore?
anyway, thank you both ^.^
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Aerowinder said:
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Click to expand...
Click to collapse
Oh now that make a lot of sense. So I was not suppose to reboot before going into recovery with 4.1.1...will keep that in mind next time!
Even though you're rooted, flash the 4.1 root66 in Odin. You don't want to go from ICS to JB via recovery, it doesn't flash all partitions. After you flash root66 in Odin, you will already be rooted. Then you can just flash a custom recovery.
Sent from my SGH-T999 using Tapatalk 2
If I remember correctly you can still root normally on the later builds, you just have to pop out you battery after you flash, don't let it auto-reboot, then you can put the battery back in and get to clockwork recovery.
I noticed that when using the last dev preview for my N7 2013, it keeps killing TWRP and putting back the stock recovery. Now the final release does this. If I flash TWRP again, it just gets overwritten after a normal boot then back to recovery.
Why? Is there a way to stop this? This is the first time I've dealt with this. Nothing else does this to me. I haven't found a clear answer yet to this while searching this site or others.
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
rguilamo said:
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
Click to expand...
Click to collapse
Well it is just 5.0 that does this.
Since I posted this there is a sane reason for them to do this - it might be the way they enforce the factory reset protection. It has to use their recovery to do so. Still annoying.
But thanks for a workaround, that it simply is the kernel, or boot image. That and I want root
You can try Chainfire's CF-AutoRoot, It modifies Boot.img so root is granted in boot time, I already had a custom kernel when I rooted, but you can try to root first and see if it stops auto-writing the stock recovery.
Here's the download link: http://download.chainfire.eu/347/CF-Root/CF-Auto-Root/CF-Auto-Root-flo-razor-nexus7.zip
Extract it, and run root-windows.bat (or the one suitable to your OS) while in fastboot.
I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?
SethPDA said:
I just noticed a few things. The stock based roms are using the Dual Recovery in their rom, but CM based roms, like Resurrection Remix, uses Cyanogen Recovery.
So when I flash RR, it automatically replaces my recoveries with the Cyanogen Recovery.
Is there any way to avoid that? Or is there any way I can flash my Duel Recovery back after installing RR?
Click to expand...
Click to collapse
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.
levone1 said:
It's not all cm-based ROMs that use cm recovery. Each ROM is different. It's discussed in the RR thread, and it's in the 2nd post that cm recovery is built in to that ROM. There's links there for other recovery options. I like to always have Rashr on hand to easily flash IMGs, so I can access my backups from other recoveries. Dual recovery is just not going to work on every ROM.
Click to expand...
Click to collapse
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse
levone1 said:
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.[/QUOTE
I haven't used RR since 1st build, but I know it's been addressed in the thread. I would be glad to try it out to help. Meanwhile, I would try to flash twrp with fastboot, (you said you used Flashtool - maybe the same, but worth a try), and also try flashing M5, (which you need recovery to do, but you could use a temp. boot.img to get into recovery, then flash M5), which may work better with recovery. There's also Nut's PC installer. And search the RR thread.
I'll attach a copy of twrp 2.8.7.0 to try. Hope this helps.
(File too big to attach. Let me know if you want it and I'll send a link)
Click to expand...
Click to collapse
You can't because CyanogenMod uses its own Recovery based of CWM ( I think? ). You could try however, using a custom kernel that has its own Dual recovery ( for e.g. PhilzTouch and TWRP )
Click to expand...
Click to collapse
SethPDA said:
Okay so here is what I did:
I flashed latest RR rom
This of course, overwrote my TWRP recovery so right now I have Cyanogen recovery.
Now I flash with Flashtool, the FOTA TWRP recovery which you pointed me at.
Device does not boot
I flash CM kernel from the multirom thread, which gives me acces to the previously flashed FOTA recovery BUT!
Device boots, Stuck at boot
What am I doing wrong?
EDIT: I tried flashing recovery with Rashr, it does nothing.
Click to expand...
Click to collapse
I just remembered something else. See my post here- http://forum.xda-developers.com/showpost.php?p=62114382&postcount=534 - latest version of Rashr doesn't seem to work on some ROMs. Try this one...
Edit - I just successfully flashed twrp 2.8.7.0 on latest RR using Rashr. Make sure to use this version, not the latest Play Store.
Okay so I tried what @levone1 said. I installed that Rashr which you uploaded. I tried flashing the recovery with this, and it worked! Thank you very much guys for your help!
hey thanks to levone1 i got twrp running on crDroid rom.:good::good::good:
i did it like he said: Use his Version of rashr and flash his twrp. done!
The recovery images all over this site seem really sketchy, but roms often come with great recovery and updates. I can flash the rom's boot.img during the update, but I also see that fastboot has a flash to recovery option. Is it OK to flash the boot.img to recovery or do I have to somehow extract recovery out of the boot.img? If I do a flash to recovery does that make TWRP permanent or can it still be overwritten by flashing new roms?
bananabytes said:
The recovery images all over this site seem really sketchy, but roms often come with great recovery and updates. I can flash the rom's boot.img during the update, but I also see that fastboot has a flash to recovery option. Is it OK to flash the boot.img to recovery or do I have to somehow extract recovery out of the boot.img? If I do a flash to recovery does that make TWRP permanent or can it still be overwritten by flashing new roms?
Click to expand...
Click to collapse
Get twrp from here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827 and flash with Rash for non-stock roms. For stock roms, net's xzdr is best - http://nut.xperia-files.com/
If a rom has a recovery included, it will probably overwrite your recovery. For best staying power, make sure you use real recovery - http://forum.xda-developers.com/son...ral/bootloader-devices-real-recovery-t3117568 but even then you might still have to reflash your img, depending on the rom you install.
levone1 said:
Get twrp from here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827 and flash with Rash for non-stock roms. For stock roms, net's xzdr is best - http://nut.xperia-files.com/
If a rom has a recovery included, it will probably overwrite your recovery. For best staying power, make sure you use real recovery - http://forum.xda-developers.com/son...ral/bootloader-devices-real-recovery-t3117568 but even then you might still have to reflash your img, depending on the rom you install.
Click to expand...
Click to collapse
Thank you so much. I had the latest TWRP from the AICP rom but it was within the boot image and I couldn't seem to find a plain TWRP image that wasn't on some sketchy thread.
Also I was unaware that my firmware was out of date. When I was installing a rom I saw a number that related to the latest firmware so I assumed I had it. I was confused why using flashboot to flash to recovery wasn't working. It looks like the recovery image was always within the boot image and was getting wiped out with roms that didn't include a recovery image in there (AH HEM PARANOID ANDROID). It seems that I was able to flash the img to the special recovery now and I don't think it's getting wiped out. Thanks very much.
Im using the ElementalX Kernel but its causing issues for my phone. I have it rooted with magisk too. how can i either go back to the stock kernel, or a different custom one?
Just download the factory image, unzip it, open the system.img and extract the stock boot.img
Then go into fastboot and flash the stock boot image to both slots and reboot.
This restores your stock kernel, and you're done if you just wanted to go back to stock. Now you can re-root it, and/or install another kernel.
You need to be stock before installing another kernel, so you have an untouched ramdisk.
id need to do it for the factory image i used for this one right? (in my case, the may 2020 image),
hey so, i wasnt sure what you meant by opening the system.img but i flashed the boot.img to both slots and rebooted to the slot i was originally using with bliss rom, and now it wont boot..