I succesfully installed TWRP when phone had stock ROM.
I booted into it, and i flashed CM11
And after that, i couldn't go into TWRP anymore.
I tried flashing diffrent versions of TWRP, and even CWM but still it doesn't boot into recovery
I tried to reboot advanced options, to reboot into recovery from CM11, but still, it doesn't reboot into it, it just hangs at "rebooting to recovery"
I know key combinations, because i flashed CM11 via TWRP, but suddenly it dissapeared.
I don't want to reflash stock ROM, because of this, in fact, i just want to flash zip file, fde.ai , but recovery is not available, so i can't flash it.
I tried flashify, and rashr, they all don't do their job as adversited.
So my only fix is , to somehow bring back TWRP into which i can't boot
Related
While starting to upgrade from CM10 to CM10.2/10.3 on MB526, I flashed TWRP zip file downloaded from Team-win website.
steps:
1) downloaded recovery and copied to SDcard.
2) reboot into custom recovery (CWM)
3) Flash zip of TWRP recovery
Since than, I am getting black screen after clicking on custom recovery from Bootmenu.
Device is working fine,
but with no custom recovery, my hands are tied...
can't restore backup, can't flash rom or do anything..
tried installing zip from stock recovery.. Installation aborted appears
Is there any solution to get recovery working without starting from scratch (flashing SPF and 2ndinit, and so on.... )
warewolf4586 said:
While starting to upgrade from CM10 to CM10.2/10.3 on MB526, I flashed TWRP zip file downloaded from Team-win website.
steps:
1) downloaded recovery and copied to SDcard.
2) reboot into custom recovery (CWM)
3) Flash zip of TWRP recovery
Since than, I am getting black screen after clicking on custom recovery from Bootmenu.
Device is working fine,
but with no custom recovery, my hands are tied...
can't restore backup, can't flash rom or do anything..
tried installing zip from stock recovery.. Installation aborted appears
Is there any solution to get recovery working without starting from scratch (flashing SPF and 2ndinit, and so on.... )
Click to expand...
Click to collapse
I think stock recovery can't help you now, you should start from scratch...
It isn't so hard, just takes time...
From CM10 to CM10.2, you don't need to change recovery, just install it. From CM10.2 to CM11 you should install update-recovery.zip, reboot, install CM11 + GApps.
Hope it helps... :highfive:
warewolf4586 said:
While starting to upgrade from CM10 to CM10.2/10.3 on MB526, I flashed TWRP zip file downloaded from Team-win website.
steps:
1) downloaded recovery and copied to SDcard.
2) reboot into custom recovery (CWM)
3) Flash zip of TWRP recovery
Since than, I am getting black screen after clicking on custom recovery from Bootmenu.
Device is working fine,
but with no custom recovery, my hands are tied...
can't restore backup, can't flash rom or do anything..
tried installing zip from stock recovery.. Installation aborted appears
Is there any solution to get recovery working without starting from scratch (flashing SPF and 2ndinit, and so on.... )
Click to expand...
Click to collapse
Start from scrach >.>
I am trying to replace CWM with TWRP but not having any luck. I installed GooManager and used the option to install open recovery script, but I still have CWM. So I downloaded the twrp image and used the terminal method
dd if=/mnt/extSdCard/twrp.img of=/dev/block/mmcblk0p34
This completed successfully, but after reboot then reboot into recovery I still have CWM.
I am currently running latest Cyanogenmod Rom.
Why do you want to replace it, anything that TWRP can do better than CWM? If you still want to switch, you should flash TWRP via Odin.
And/or flashing TWRP zip file through CWM recovery
I like the TWRP interface over CWM. I guess I'll try the odin route.
Well I was able to flash a recovery zip file, but now if I attempt to boot into recovery it just stops at the Google Logo (Google edition phone) and I have to pull the battery, boot into download mode and select restart to get out of it.
Just flash the recovery with Odin. Uncheck auto-reboot in Odin. If it doesn't work the first time, flash it 2 times in a row.
I was having a problem with Odin crashing when I attempted to flash. I finally got it working, apparently I had the wrong img file and dd statement. So now everything is working great.
Making Nandroid Backup first thing.
I'm running ResurrectionRemix-M-v5.6.5-20160316 with the latest TWRP recovery and Xposed.
The last time I used the recovery was on 22/03 to make a backup of my ROM (I've entered the recovery more than a dozen times before this backup with no issues).
Today I wanted to switch from Ressurrection Remix to crDroid (Ressurrection for some reason becomes laggy after use and only a reboot resolves this issue).
I downloaded all of the zips I required (ROM, GAPPS, SU etc.)
I selected to reboot to recovery using the advanced reboot option.
The phone rebooted and displayed recovery booting in blue as per the norm.
The TWRP splash screen showed for around 10 sec or so then the phone rebooted (this never happened before).
Thinking that this was a bug with the recovery, I tried turned off the phone via the power menu once my I got into MM and then removed the battery and used the power + up button combo to enter recovery however still no go.
Next I tried flashing the TWRP 3.0.0.tar file via odin, still no luck.
The question I have is how do I resolve the issue?
Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.
Ok to downgrade?
GDReaper said:
Try flashing a different version of TWRP.
Or flash an twrp.img file via the app Flashify.
Click to expand...
Click to collapse
So it's ok to downgrade to say 2.8.60 with F2FS support?
Fixed!!!
jdhot2 said:
So it's ok to downgrade to say 2.8.60 with F2FS support?
Click to expand...
Click to collapse
I found a custom version of the recovery made by the JDC team http://forum.xda-developers.com/gal.../jdcteam-twrp-touch-recovery-3-0-0-0-t3312115.
I flashed the recovery using flashify.
All fixed now
Hi all,
My Samsung Galaxy S5 G900H, I updated it to stock Samsung Android 6.0.1. Now I want to root it. AS I've read in some of the other threads that flashing TWRPand then the latest SuperSU works. I went ahead and flashed TWRP using ODIN. Odin was successful and my phone rebooted and phone is working fine. But when I try to go into recovery, stock Android recovery pops up. I wonder why?? Can anyone point me out?
try this recovery you will be solved...
juz flash it with Odin 3.09
https://www.androidfilehost.com/?fid=24459283995296044
As rewards hit Thanks
Use twrp 3.0 by fevax i was had same problen but when u flash it reboot to recovery then to systen
I flashed this same recovery earlier. It is not working for me.
It's the same one I flashed earlier. Not working for me. Should I try to reflash the stock firmware and try again??
"flash it reboot to recovery then to system" Important point. This worked. Instead of rebooting directly after flashing. I flashed recovery, then removed battery to turn device off. Then rebooted into recovery. It WORKED.
I think rebooting into system first rewrites TWRP with stock recovery.
guru_iyer's Avatar
Edit
"flash it reboot to recovery then to system" Important point. This worked. Instead of rebooting directly after flashing. I flashed recovery, then removed battery to turn device off. Then rebooted into recovery. It WORKED.
I think rebooting into system first rewrites TWRP with stock recovery.
Hey everyone.
I'm really hoping someone can help me. I just got my Redmi 2 Prime today, and before even properly setting it up I had rooted it. It wasn't long before I decided to try a different ROM. I decided on Resurrection Remix and TWRP recovery, both of which I flashed an ran flawlessly. RR booted up, everything was great.
I then tried flashing SuperSU again, after installing RR. Flashing the .zip file resulted in a boot loop, with no access to recovery, only fastboot.
What I've tried (with no success):
- Re-flashing TWRP (through Fastboot).
- Flashing CWM instead (through Fastboot).
- Flashing stock recovery (through Fastboot).
None of these have proven successful..... Can anyone give any advice on how to get out of this mess? I hardly feel up for having to take my phone into a shop without even having had it for 24 hours.....
TIA!
Fastboot flash Redmi 2 ROM. Download ROM file from MIUI forums and read the instructions there. Go to this link http://en.miui.com/a-234.html
i dont know if this comes at the right time,since fastboot is accesbile ,boot into fastboot, and flash recovery into boot(this may sound foolish but you can do it)
fastboot flash boot recovery_twrp.img
reboot,you will be taken into twrp
you can take a backup here,
now wipe all and flash the ROM.zip
anfd it should all work fine
I had the same problem when I switched from MIUI 8 4.4Kitkat to CM13 6.0
But I was able to solve it without fastboot.
RessurectionRemix and most roms esepecially CM based have "built-in" superSU manager.You just have simply to re-enable it on the developer settings.No need to flash supersu.zip,it would just make things worse.Download Flashify to boot in TWRP manually since flashing different ROMs will temporarily remove the TWRP(doing the button combination wouldn't boot into recovery,instead bootloop like you mentioned).
Then I was able to perform a restore on stock MIUI 8.
You have to download Flashify in order to manually force the phone to boot in recovery mode,since doing to volume up+power wouldn't let you.
I don't know if this is because my TWRP version only supports KitKat....or switching from 4.4-6.0 is a big gap.
Thanks for the responses!
I ended up solving the issue, though there wasn't really an issue to begin with. Turns out the button combination to enter recovery is different than stock (both volume buttons and power), though I did re-flash to the latest version of TWRP.
I'm now running Resurrection Remix without flaws!
But yeah, I realize now that CM based ROMs have a baked-in SU manager, it was foolish of me to flash the file without doing proper reading up beforehand!