Database Info

[HELP] Stuck on Recovery Bootloop after OTA Update (CM14.1) , can't access Fastboot

Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.

I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.

[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date

Same thing happened to me! Where did you get a copy of the stock recovery? Link?

resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.

Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.

corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse

resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!

First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.

Moto G Bricked?

Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.

Same thing happened to me!
Basidialfiddle said:
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Click to expand...
Click to collapse
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?

gaurav.kar said:
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
Click to expand...
Click to collapse
Hi, I found the solution time ago, sorry for answering to late, hope I can still be helpful.
Well, what I did is, I booted into TWRP, then I did a total format to the storage, after that I did something kind of crazy, I switched my storage format to anotherone and then I turned it back to how it was before (example: I was on fat32, I switched to exFAT and then I switched again to fat32) after doing that I tried to flash LinageOS and it allowed me, it booted and now my friend has Android Oreo on his Moto G1
Hope it works for you mate, those situations are very frustrating, good luck

Zip signature verification failure when flashing in TWRP

I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.

I had updated from my oneplus 2 to the oneplus 6. and with great ease was able to unlock,flash android P.
Bad to hear that you are facing such problems, as my switching was error free.
One of the solutions which you could try for the Zip signature verfication:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse

inderjeet.c7 said:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
Click to expand...
Click to collapse
I have tried TWRP with both the current 3.2.3.0 and the previous 3.2.3.2, both downloaded from twrp.me. Sideloading failed, too. Same zip signature error.
I may have to wipe the device and start over yet again. I'd blame myself for doing something wrong, which may very well the the case. But the zip signature issue was there before I installed anything with the stock system.

maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse
Try this https://www.bouncegeek.com/fix-signature-verification-failed-oneplus-devices/. I don't know if it'll work for your device as this is for one plus 5t but they are similar in this regard. I would also download all files fresh to make sure there is no corruption. Also disable any lock screen security (finger print, Pin, face lock, etc.)

Among the things I've tried were that I had happened to find that article earlier. Some of it, I can't do. Like clearing the cache of System Update. I'm not seeing that listed in the Apps on Oxygen like it may have been on Hydrogen. One thing I did do, though, almost the only thing, before unlocking and rooting, was to let the system update with an OTA from 5.18 to 5.19. So that could have played a role based on the article's premise.
In any case, I can't sideload, I still get the zip signature failure in spite of what the article says. I tried the other approach. I'll try again later.
This is frustrating. I bought this phone in no small part because it can be rooted and there is a dev community for it. But if I can't do with it what others are and what I want, it may not be worth keeping. I wish I knew exactly this failure is occurring. That it's not rare, I get. But maybe there's nothing wrong with the files. Can all these repeated downloads be bad ones? I've tried both transferring from my Mac via ftp and downloading directly from the web to the phone.

Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.

helioXverse said:
Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.
Click to expand...
Click to collapse
Yes, I'm booting into TWRP via that command line. It's not permanent. I tried to flash the TWRP zip, but signature verification failed. That was the first of my various failures. If I can't find a way to get this straight, I may return the phone, or at least try and get them to trade it to me for another.

Is your oem lock checked?

netgar said:
Is your oem lock checked?
Click to expand...
Click to collapse
Do you mean is "OEM unlocking" toggled on in Developer Options? If so, yes, it is and has been.

I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0

NickStrupat said:
I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0
Click to expand...
Click to collapse
Interesting. I didn't try going back that far. I ended up abandoning zip signature verification and am just flashing without it. So far, no problems.

Messed my honor 6x. Help me recover.

Update: I tried flashing TWRP by Askuccio through fastboot and I successfully did. Then I flashed PixyOS v2.4 and flashed it successfully then flashed Gapps and stock recovery then followed rest of the required steps and everything went smooth and right. Using PixyOs now. Great rom with great stability with Android P. ?
I was on Oreo on my 6x. I wanted to flash this pixyos rom on my Honor 6x. I unlocked the bootloader of my phone installed the Twrp successfully without any hassle. Now it was time to flash PixyOs and unfortunately I did not do any backup of any sort. The PixyOs Package showed some error when I tried to clean flash it. And here we go my phone had No Os now. I searched a lot and found this thread
https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I gave it a try step by step thinking about that it would work but after successfully following all the mentioned steps and flashing everything I got this "System failed" error when the device was booting. In other words it didn't work eventually.
I tried the dload method with the same update zip from the thread linked above but it failed too.
I tried erecovery to restore my device but it gave me "Getting package info failed".
I don't know what to do now. Please help me with this and help me restore my phone.

I had the same issue
i made something like this a month ago
only one temporary solution worked is flashing EliteRom via twrp and i got the phone working again but still can't flash a stock rom.

tanaybitw said:
I was on Oreo on my 6x. I wanted to flash this pixyos rom on my Honor 6x. I unlocked the bootloader of my phone installed the Twrp successfully without any hassle. Now it was time to flash PixyOs and unfortunately I did not do any backup of any sort. The PixyOs Package showed some error when I tried to clean flash it. A then nd here we go my phone had No Os now. I searched a lot and found this thread
https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I gave it a try step by step thinking about that it would work but after successfully following all steps and flashing everything I got this "System failed" error when the device was booting. In other words it didn5 work eventually.
I tried the dload method with the same update zip from the thread linked above but it failed too.
I tried erecovery to restore my device but it gave me "Getting package info failed".
I don't know what to do now. Please help me with this and help me restore my phone.
Click to expand...
Click to collapse
Can you boot to fastboot. What did the PC say when you ran the script. Try to flash TWRP if EMUI 5 and then press and hold Volume Up and Power to boot into it. If it works, good. If not then again boot to bootloader and try to flash TWRP of EMUI 8. Again try to boot into it. If it works, good. Anyway, once you're in TWRP don't let your phone turn off. Plug it in charging. Now go-to wipe, and format data

»FáRéS...?« said:
i made something like this a month ago
only one temporary solution worked is flashing EliteRom via twrp and i got the phone working again but still can't flash a stock rom.
Click to expand...
Click to collapse
I'd suggest you to try PixyOs (With Askuccio TWRP). It's a great and fluid ROM. Only downside is it doesn't have Stock Emui camera and I didn't even try flashing it because I read somewhere that it causes the device to get stuck in bootloop.

Mannan Qamar said:
Can you boot to fastboot. What did the PC say when you ran the script. Try to flash TWRP if EMUI 5 and then press and hold Volume Up and Power to boot into it. If it works, good. If not then again boot to bootloader and try to flash TWRP of EMUI 8. Again try to boot into it. If it works, good. Anyway, once you're in TWRP don't let your phone turn off. Plug it in charging. Now go-to wipe, and format data
Click to expand...
Click to collapse
Thank You for your reply.

S8+ failed TWRP install

I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!

Philnicolls89 said:
I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!
Click to expand...
Click to collapse
Seeing No command is normal, with an icon of a dead android lol, thats stock recovery, blue screen, i got that all time, but after waiting about 30 seconds and pressing the buttons, i got the mnue to pop up to reset cache, reboot phone, wipe data etc.
As for TWRP, are you flashing the correct one, dream2lte??, download the latest one, the dream2lte.img .tar file, from the TWRP official website - - https://dl.twrp.me/dream2lte/twrp-3.3.1-0-dream2lte.img.tar.html.
I had this issue trying to flash TWRP with standard odin, i had to use a modded version of odin to flash it, even prince cosmy version didnt work for me.
I have attatched the ODIN i use, its a 7zip file.

Thank you, after trying a few more things the twrp file you gave me worked. I now have a fully rooted s8!!!! Your a legend.