Had TWRP 2.8.1 for a long time without updates and without running for a while. I just flashed the latest TWRP 3.1.1 using fastboot command. But when trying to get into TWRP, it got stuck at splash screen. I waited like 1 min, do I have to wait much longer? Or is there something wrong? BTW I am on Marshmallow (TruePureXMM). Thank you.
namartlu said:
Had TWRP 2.8.1 for a long time without updates and without running for a while. I just flashed the latest TWRP 3.1.1 using fastboot command. But when trying to get into TWRP, it got stuck at splash screen. I waited like 1 min, do I have to wait much longer? Or is there something wrong? BTW I am on Marshmallow (TruePureXMM). Thank you.
Click to expand...
Click to collapse
Boot the phone, make a copy of the TWRP directory to SD card and then delete or rename the one on internal storage, then reboot and start TWRP. It is quite common to have a configuration issue that causes this slow startup of TWRP when moving from 2.x to 3.x.
Thank you! tried that and it worked now. I also waited longer (than the 1 min) and eventually it booted to TWRP. thanks again!
Related
Okay heres what happened: I was attempting to flash a ROM. After making a new backup and flashing that new ROM the device would not boot. So like any normal person would do I then went back into recovery and attempted to restore my backup. Upon restoring the backup, halfway through the device just decides to reboot and boot into the ROM (which was a half restored backup). I tried to boot back into recovery and start the process over however now the device will not boot into the recovery at all. It continues to loop the bootloader logo over and over. Is this a soft brick? Either way, all I want at this point is to be able to restore that backup so I can atleast have it working again. All help is much appreciated.
EDIT: okay i managed to get the recovery loaded, what i may end up doing is loading a saved ROM up and starting from scratch there (TWRP continues to Stop my restore halfway through and reboot the recovery --very frustrating tbh). My question then however would be is there a way to get my data back from my backup once I start fresh? Does tibu allow this or something comparable? I really don't want to lose all that data. Thanks again.
Edit 2: managed to fully resolve issue. delete if neccessary.
HarmonyFlame said:
Okay heres what happened: I was attempting to flash a ROM. After making a new backup and flashing that new ROM the device would not boot. So like any normal person would do I then went back into recovery and attempted to restore my backup. Upon restoring the backup, halfway through the device just decides to reboot and boot into the ROM (which was a half restored backup). I tried to boot back into recovery and start the process over however now the device will not boot into the recovery at all. It continues to loop the bootloader logo over and over. Is this a soft brick? Either way, all I want at this point is to be able to restore that backup so I can atleast have it working again. All help is much appreciated.
EDIT: okay i managed to get the recovery loaded, what i may end up doing is loading a saved ROM up and starting from scratch there (TWRP continues to Stop my restore halfway through and reboot the recovery --very frustrating tbh). My question then however would be is there a way to get my data back from my backup once I start fresh? Does tibu allow this or something comparable? I really don't want to lose all that data. Thanks again.
Edit 2: managed to fully resolve issue. delete if neccessary.
Click to expand...
Click to collapse
How did you get back into recovery? I had paranoid android flashed and i did a factory reset like an idiot. Now i cant boot into recovery - "teamwin" logo freezes and reboots into a continuous loop. I can get into the bootloader but nothing works?
sashennaidoo1 said:
How did you get back into recovery? I had paranoid android flashed and i did a factory reset like an idiot. Now i cant boot into recovery - "teamwin" logo freezes and reboots into a continuous loop. I can get into the bootloader but nothing works?
Click to expand...
Click to collapse
I'll tell you what I literally did.
When the device was bootlooping the teamwin logo, I booted into fastboot and powered my device completely off. I then waited an hour as I was a little tired with what was happening to take care of something. After that hour I turned it on and it suddenly booted into teamwin recovery. That's exactly all I did. So what I would do is turn the device off for a little bit then try to see if it boots the recovery. If not you will likely have to use the nexus 10 toolkit to reflash the recovery.
Hope that helps.
HarmonyFlame said:
I'll tell you what I literally did.
When the device was bootlooping the teamwin logo, I booted into fastboot and powered my device completely off. I then waited an hour as I was a little tired with what was happening to take care of something. After that hour I turned it on and it suddenly booted into teamwin recovery. That's exactly all I did. So what I would do is turn the device off for a little bit then try to see if it boots the recovery. If not you will likely have to use the nexus 10 toolkit to reflash the recovery.
Hope that helps.
Click to expand...
Click to collapse
Thanks mate! really appreciate it! I have no clue what i did but on one of the reboots, it booted into TWRP and i re-flashed the paranoid android rom and gapps and it worked.
Thanks for above response. Much appreciated!
Just for future reference, both TiBU and ROM Toolbox will restore from a Nandroid backup.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Just for future reference, both TiBU and ROM Toolbox will restore from a Nandroid backup.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
So I am in this same boat and will probably have to use some toolkit since I have not been able to boot up TWRP. I know I am on 2.4.4.0 or something for TWRP, not 2.5 but would CWM be a better choice since I have run into this now a couple of times? This is the first where it hasn't stopped the recovery boot loop.
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
thanks for everything
On the official Oppo forum's there's a guide on how to install the latest Omnirom. Under known issues it says:
5)After installing the TWRP recovery the Screen Touch firmware update goes on for more than 5-7 minutes, do a hard reboot and you would be fine,
Click to expand...
Click to collapse
I haven't tried it myself since I didn't get the problem when flashing Omni and Asylum, but it seems to be worth a shot.
In case you are looking for the topic, search for "How to Install OmniRom 4.4".
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?
fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.
I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.
disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?
Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..
I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.
Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..
So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.
After I got my axon 7 it was on android 6 mm. I unlocked the bootloader, then installed twrp. With twrp I tried to flash a bootstack and a nougat. It didn't boot so I flashed stock recovery from twrp and installed official nougat update from there. Now when the phone opens there is that screen says "lock bootloader again, wait 5 seconds phone will boot". Everything is fine and phone really boots but when I try to install twrp again it gets stuck on that screen and doesn't boot in 5 seconds.
So right now:
I have unlocked bootloader and stock recovery
And I am looking for a way to install twrp and nougat rom
Thanks in advance :good::good:
ahalak said:
After I got my axon 7 it was on android 6 mm. I unlocked the bootloader, then installed twrp. With twrp I tried to flash a bootstack and a nougat. It didn't boot so I flashed stock recovery from twrp and installed official nougat update from there. Now when the phone opens there is that screen says "lock bootloader again, wait 5 seconds phone will boot". Everything is fine and phone really boots but when I try to install twrp again it gets stuck on that screen and doesn't boot in 5 seconds.
So right now:
I have unlocked bootloader and stock recovery
And I am looking for a way to install twrp and nougat rom
Thanks in advance :good::good:
Click to expand...
Click to collapse
Install TWRP, right after you install it boot to TWRP, format data (check that it formats with ext4) and install Magisk or SuperSU. Your problem may be dm-verity, and magisk or supersu patch the kernel to fix this.
What is weird is that usually if you install TWRP and just boot to system, the system should boot normally, but it should replace TWRP with the stock recovery... This doesn't happen, right?
Choose an username... said:
Install TWRP, right after you install it boot to TWRP, format data (check that it formats with ext4) and install Magisk or SuperSU. Your problem may be dm-verity, and magisk or supersu patch the kernel to fix this.
What is weird is that usually if you install TWRP and just boot to system, the system should boot normally, but it should replace TWRP with the stock recovery... This doesn't happen, right?
Click to expand...
Click to collapse
So much thx. It worked this time.
For your question; twrp was still there after I tried to boot into system.
ahalak said:
So much thx. It worked this time.
For your question; twrp was still there after I tried to boot into system.
Click to expand...
Click to collapse
Because it didn't actually boot, it failed to boot. But it should have booted afaik
Whatever, it works now
Choose an username... said:
Install TWRP, right after you install it boot to TWRP, format data (check that it formats with ext4) and install Magisk or SuperSU. Your problem may be dm-verity, and magisk or supersu patch the kernel to fix this.
What is weird is that usually if you install TWRP and just boot to system, the system should boot normally, but it should replace TWRP with the stock recovery... This doesn't happen, right?
Click to expand...
Click to collapse
Thanks bruh..just got this phone yesterday and just when I think it's all come together this happens..but all resolved thanks to you.:good: