Related
Hi.
Today I wanted to upgrade from CM11 to CM12.1, but I had to upgrade the bootloader first. It all worked and I'm now on bootloader version 41.18.
When I flashed the ROM it flashed in 20 seconds from an USB stick. It seemed a little to fast. When I rebooted it worked fine and I was on Android 5.1.1, but after installing SuperSU and rebooting I stuck into a bootloop.
I'm now in a bootloop and when I try to enter the recovery the TWRP splash screen comes up, but then it goes into the bootloop again.
I have the XT1032 and my TWRP version is 2.8.6.0 and I have a TWRP backup from CM11
If someone could push me in the right direction how I can access TWRP then that would be great.
Thanks in advance.
Quick update
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
zomgwalrus said:
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
Click to expand...
Click to collapse
I have the same issue, cannot get into twrp, how did you managed to boot into TWRP?
i had same issues in my moto g xt1032 i tried below CM12.1 works without issues.
go recovery --- wipe---- format data
and try step install steps like install rom zip & gapps
Ok, first what do you use to flash recovery, can you reflash recovery with the lastest TWRP version (2.8.7.0) and post back the logs here? Then tell me if you can get into recovery
Its common place that twrp cause bootloop with backups.
No problem try to
Install new twrp using fastboot mode it will be work fine
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.
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
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.
Dear op7p xda community,
A few months ago, I rooted my device and flashed TWRP succesfully. After a stock OTA (still Pie), I lost both. Today, I wanted to re-root and re-flash TWRP. I used mauronofrio's Tool All In One 2.0.0.7 for this. I didn't flash TWRP, but booted it and used that to flash Magisk 19.4. Now, I wanted to see if the rooting process was successful, so I booted the OS. Unfortunately, once it boots and reaches the lockscreen, the "shutting off..." prompt immediately shows and reboots me into the stock recovery.
Edit: I now flashed TWRP after booting TWRP again and ran Magisk to root it again. Unfortunately, the problem persists (only now reboots to TWRP instead of stock recovery). Help is much appreciated!
Can someone help me get my phone to work again? Thanks a lot in advance!
Regards,
Wouty
What version TWRP? Maybe try a different one?
redpoint73 said:
What version TWRP? Maybe try a different one?
Click to expand...
Click to collapse
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Wouty said:
Thank you for your reply. I am now on TWRP 3.3.1-4 (latest). I have tried to factory reset and wipe the phone in hopes of getting it to start properly again, but now the OS doesn't even boot and immediately reboots me into TWRP. I have now tried to flash 3 different stock, official ROMs, both International and Europe, like OnePlus7ProOxygen_21.O.14_OTA_014_all_1907281611. I used the recommended flashing instructions (flash ROM, flash TWRP, reboot TWRP, flash Magisk) But none of them boot at all. Only TWRP is usable now. I don't know what to do
Click to expand...
Click to collapse
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
boybkol said:
When it reboots back to TWRP try to format data if that doesn't work then you need to use MSM tool.
Click to expand...
Click to collapse
Thanks for your reply. I had indeed wiped data, but that worsened the situation (not booting at all, instead of rebooting once booted). I have now tried this https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424 and it now seems to be booting (booting animation on-going for quite some time now, though). I will keep you posted. If it doesn't work, I'll look into the MSM tool. Thanks for the suggestion!
Wouty said:
I am now on TWRP 3.3.1-4 (latest).
Click to expand...
Click to collapse
That is the latest official TWRP for this device. The official builds don't support Android 10, as decryption is not supported, so that may be part of your problem. The latest unofficial is -70, and I believe you need to use build -65 or later for Android 10.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Wouty said:
Thanks for your reply. I had indeed wiped data, but that worsened the situation
Click to expand...
Click to collapse
Wipe is not the same as format. In TWRP, go to Wipe section, and you will see a button "Format data".
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
milindpatel63 said:
If you are now stuck on a boot loop, try booting into twrp and clearing cache. If you still can't boot, then i recommend downloading the full official rom and flashing it via fastboot. This will remove twrp and u'll end up with stock recovery and everything. Then after that follow proper instructions to install twrp first, then clear cache. Then magisk, and clear cache.
Click to expand...
Click to collapse
Trying to flash an official ROM via fastboot for a second time did indeed solve the problem for me. Now able to boot. Now backing up everything to make sure I'm able to solve these issues faster in the future. Thanks to all for your input!