Background, I downgraded my firmware to 23.0.a.2.93, rooted with locked bootloader using giefroot v3, then installed NUT's Z3-lockeddualrecovery2.8.3-RELEASE.installer, after which I flashed 5.0.2 to preserve root.
Now my phone refuses to boot into TWRP (skips it altogether, I've tried booting into recovery from app like Flashify, TWRP manager and also using adb command). Phone restarts, but never boots into recovery, and goes straight to the android system. I know I have it installed because TWRP manager shows that it is installed, but when I try to flash a .zip file phone just restarts and nothing happens. I wanted to flash xposed's .zip file, otherwise it won't work.
So my question is, what could be the problem? I reinstalled NUT's dualrecovery several times, still no results.
Seriously, have you been on another planet lately? Sorry for sounding a bit harsh.
It's a known issue that Dual recovery isn't still available for Lollipop.
Related
I have the Samsung Galaxy S4, jflteatt, SGH-I337, AT&T, rooted, and I tried to install TWRP from a IMG file using the TWRP Manager app because nothing else was working. I can go into detail if you want but that is the summarized version. I used a DD file from the twrp website and I downloaded it to my phone, then selected it and selected install in the TWRP Manager app. It said flash successful but when I rebooted to recovery using the app my phone went into download mode. It said "Could not do normal boot" ODIN Mode. On Knox Kernel it says "Lock" Does that mean that my boot loader is locked? I think when I tried to install TWRP incorrectly it did this because my boot loader is locked. Is this true? I know I when I tried to flash TWRP from a DD file that I did it incorrectly now. Didn't do my research and tried to flash a file in the TWRP manager app that was meant to be flashed in Terminal Emulator. Dumb move on my part.
Well anyway now that Flashify is working again I tried to install TWRP from there but it just goes into Download mode every time I try to reboot to recovery even though it said "Successful". I can't even get to my stock recovery since I messed up my phone. It just goes into download mode no matter what I try. I know that TWRP will be correctly installed on my phone if I use Flashify because it has worked for everybody else but I don't know if the fact that my bootloader could be potentially locked that it could be messing it up and not allowing the custom recovery to be installed. How to I make it stop going into download mode every time I try to go into recovery mode?
Could unlocking my bootloader any trying to flash TWRP again solve my problem?
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
Hi guys, I flashed the latest factory image, then flashed the latest TWRP but can access it 1 out of 10 tries.. What am I doing wrong? Is it a faulty replacement phone? Never had this issue with my other nexus 5 (same recovery file but lollipop and not marshmallow) and now I have this problem.. Tried to riflashato the factory image 5 times, boot to recovery without installing but nothing changed.. Thanks in advance!
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
beekay201 said:
If you just just flashed TWRP, then booted into Android, then reboot into recovery.. Android will overwrite TWRP with the stock recovery.
a hammerhead wrote this.
Click to expand...
Click to collapse
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
carlese said:
Never happened before.. How can I prevent this? Sometimes I can't even boot to twrp after flashing and not rebooting to android..
Click to expand...
Click to collapse
do you finde fix
slavisa037 said:
do you finde fix
Click to expand...
Click to collapse
Downloaded twrp again and used flashify..
carlese said:
Downloaded twrp again and used flashify..
Click to expand...
Click to collapse
This is not really a fix, since to use Flashify one needs to be rooted already.
What I did to work around this was reflash LMY48M. After reflashing that, fastboot correctly boots/flashes twrp.
I've read that the issue arises when trying to boot and/or flash twrp with MRA56K installed, AND the device is connected to USB.
Ok, i got some of problems here, i tryied to root my Nexus 5 with other Android 6 version, it was the first one launched after development version. Now i have MRA58K version.
Problem 1 : I have no stock recovery, i first rooted original version of Marshmallow with CWM and i soft bricked, so no backup, no factory images. Installed MRA58K and there is no stock recovery, thanks god i can use bootloader. I can install TWRP, but i want to install the old recovery, Tell me how to do it.
Problem 2: Actual version of Marshmallow ask me to install a patch, but when installing i got stuck in TWRP, it cant install it (yes, android was rooted, but i installed twrp before root, and the update were before it.)
Thanks.
You can flash a stock ROM using the flash-all file in a command prompt. This will install stock ROM with stock recovery. Make sure the phone has an unlocked bootloader and you should be fine.
Official OTA updates cannot be installed with a custom recovery.
I tryied 3 times to install OS with flash-all. All the problems start after i installed CWM and try to root the phone, but after that, i used a stock rom image that was different build than actually one.
I`m not sure yet who`s fault is.
Any ideas?
I don't recommend using CWM, only TWRP.
After you flash TWRP always boot into it, and since you're flashing a custom recovery I'm going to assume you don't care about OTA's, swipe to allow system to be mounted. TWRP will automatically patch the system to survive android trying to overwrite it. Reboot into TWRP a second time to be safe. TWRP should stick from now on until you flash over it or restore stock system partition.
Yes, now i have TWRP as recovery, but i want to replace it with stock recovery.
Problem is, when i upload stock recovery and try to boot in recovery mode, i got the green dead android with red triangle.
But after TWRP uploading and booting in recovery mode, TWRP is there..
I really don`t know what`s wrong.
Flash stock recovery, select recovery from the fastboot menu, hold the power button and press volume up button.
Is it possible to instal the compatible cwm recovery at huawei P8max and how? I tried different versions using FlashFire and one apk with loader.zip, but without success. After rebooting recovery, i got some strange rescue screen with 2 faults: 11. recovery and 2: boot (update your system).
Unlocked Bootloader?
Why not use the working TWRP that existing?
same problem after b210 from dload on sd card it seems emui 4 does not support thre local cwm
@Hirs
I wrote already that i have a lot of problems with "working TWRP". When i flashed it the first time, it was ok, but later, rebooting sytem was not working, every time i was reverted to twrp screen. I flashed the stock recovery, then twrp again, the same situation.
drpainster said:
@Hirs
I wrote already that i have a lot of problems with "working TWRP". When i flashed it the first time, it was ok, but later, rebooting sytem was not working, every time i was reverted to twrp screen. I flashed the stock recovery, then twrp again, the same situation.
Click to expand...
Click to collapse
Thats normal that you cant reboot to system sometimes with a installed TWRP, then you flash stock back and reboot.
You can easily flash TWRP do the things you want and then reboot to bootloader flash stock and use the phone.
I dont think there is a CWM especially for the P8Max, but you can try the P8 one.
Hi All,
I've been trying to install TWRP, Root etc on my XZP since yesterday. I've done something wrong at some point, and now my phone will not boot at all.
I had no troubles unlocking bootloader, installing TWRP etc initially. I then tried to install a custom rom from these forums and that's where things spiraled downwards for me.
As part of that procedure, I needed to flash the latest sony firmware first. That went fine.
However, now TWRP is not able to decrypt storage, so I'm not able to flash anything else. Perhaps this is because I booted into the new sony firmware and forgot change the pattern/fingerprint to pin/fingerprint.
So I'm not able to unlock the storage via TWRP by entering a password.
I tried to reflash the same firmware again using newflasher. But the phone won't boot at all. It turns off immediately after the Unlocked bootloader warning. It's not going into a boot loop. Just turns off.
I then tried to flash the TWRP recovery image using adb fastboot command, and the flash seemed to execute properly, but I still can not boot into recovery.
Is it possible the main storage is still encrypted, so nothing can flash to it? Bricked? If so, how do I proceed?
I read something about reformatting partitions? But I'm not able to get into TWRP recovery menu to do this.
*EDIT: I reflashed trwp recovery image, and am not able to boot into recovery. I still can not unlock (unencrypt) the main storage though.
*2nd EDIT: I followed the instructions here:https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I was then able to flash the stock ROM back onto my device, and I'm able to boot my phone up. I'll look at installing a custom ROM at a later date.
Thread closed at OP request