Related
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 reading up and being waived off the Official TWRP I originally used the open source (which I cant find on my phone or desktop) TWRP for my recovery.
I've been playing around with different ROMS on my Oneplus5 and ran into a TWRP loop after restoring from one ROM to another. It was suggested, and I followed the advice, to flash the Official TWRP and no more TWRP loop.
A week or so later, trying to restore from the Resurrection ROM to xXx ROM and I'm back in a TWRP boot loop.
I've tried different wipes before restoring and still looped.
Tried flashing this version of TWRP to recovery https://forum.xda-developers.com/oneplus-5/development/twrp-oneplus-5-wip-t3626134 and it was no help.
Any suggestions?
Try flashing no verity op5.zip
I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.
jhs39 said:
I don't think official TWRP can restore backups that include system data on the OP5 without going into a bootloop. Blu Spark TWRP works much better. I've never gotten a boot loop restoring any backup I made with that version of TWRP.
Click to expand...
Click to collapse
Thanks, it was getting a bit frustrating and before your solutions posted, in the interim I used Method 2 from here:https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727 loading the stock bootloader wiped my device clean (all pics, my files, my TB folder gone) but I was able to load a ROM and boot (I hate Goggle, they can f up just about anything, but that god for their backup/restore, it got me up and running from scratch quickly ). I will give the blu spark a shot and @ se7ensde take a look at your suggestion.
It is a shame that TWRP restore is such a problem, and a random one at that. I have restored from ROM to ROM to compare them without an incident until....
So, I decided to upgrade my OP6T with Renovate on it. Booted into TWRP (official from their website), did a Nandroid Backup. Now, I did remove my fingerprint and other security before starting. Flashed the full 9.0.14, reflashed TWRP, rebooted into TWRP, flashed Magisk, and then trid to boot into system. Got a bootloop where the phone was jumping in and out of the bootloader message. I tried to stop it by pressing power and volume down and it ended up booting into safe mode. I didn't like that so I booted into TWRP and restored my Nandroid. And that's when the fight started.
It won't boot into anything but TWRP now and everything is encrypted. I have been here before but last time, I got the device totally corrupt message and used MSM to recover. But that was within two weeks of owning the phone. Now it's been three months or so and I do not relish loosing all the pictures and other setting/changes I've made to my apps etc. I am NOT liking this decryption stuff.
So, is there something, anything I can do short of a fastboot rom and/or MSM tool that we all know will wipe out all data. What if I used the unofficial TWRP? Sideload the ROM again?
Any help is appreciated. I hope I didn't make this too long, but long enough to give enough detail of how I got here and that I somewhat know what I'm doing. Been doing this since the OG Motorola Droid almost 10 years ago.
That's usually why backup is always a good idea and in some case, mandatory.
It usually depends on what TWRP version you are using, the recent unofficial TWRP can decrypt the whole /data directory no problem. However, it's possible to brick a slot, and be able to salvage your files in other slot. I have this problem, so I will have to figure out how to remove the encryption keys after backing up my stuff off the phone so I can have both slots functional (Slot A in my OnePlus 6T is bricked, so right now I'm on Slot B, with AOSiP, FrancoKernel and TWRP 3.3.1-6 on it). Dual-boot setup can be both your friend and enemy.
Nevertheless, I would give TWRP 3.3.1-6 bootable image via fastboot a try, and see if you could be able to recover your files from thereon.
Sent from my ONEPLUS 6T using Tapatalk
I tried asking about this in the twrp thread no replies as of yet.... man I miss the days of epic4g touch (s2) days I could flash a rom , brick my phone and just restore my twrp or clockwork mod recovery back ups...I used to show off all the roms I had from back ups....I tried making a back up when we first got root and twrp for this phone and I definitely had to use msm tool to get my phone back up and running
mlock420 said:
I tried asking about this in the twrp thread no replies as of yet.... man I miss the days of epic4g touch (s2) days I could flash a rom , brick my phone and just restore my twrp or clockwork mod recovery back ups...I used to show off all the roms I had from back ups....I tried making a back up when we first got root and twrp for this phone and I definitely had to use msm tool to get my phone back up and running
Click to expand...
Click to collapse
Me too. This a/b partition crap and force decryption takes all the fun out of trying new roms. So far it seems to be pointless taking a Nandroid if restoring it just soft bricks your phone. And from what I'm reading, flashing even a updated ROM almost always has to be done very clean, heck it seems like wiping your 'sdcard' is also mandatory. I'm just hoping the above suggestion of trying the different TWRP will allow me to at least get some stuff off my 'sdcard' but I secretly hope I can get into system once just to take a titanium.
Then it's wipe and trade for the oneplus 7 pro, root it and rom it once and call it a day.
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
ozzmanj1 said:
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Just curious, what TWRP version are you on? I checked the TWRP website and they only have 3.2.?.? available there while mauronofrio (who is named as maintainer at TWRP) has 3.3.1.6 available in the thread here at XDA:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
So. Today I tried to get this thing up and running. I went to the TWRP thread mentioned above and downloaded the latest files. Booted into bootloader, ran flashboot boot xxx.img and it booted into 3.3.1.6 just fine. The 'sdcard' was still encrypted so I couldn't copy the .img file and flash it via the newst instructions, , so I did an adb sideload of the installer file. That flashed just fine and I used TWRP to reboot recovery. Check. 'sdcard' still encrypted. Since this encryption issue seems to happen if you upgrade to a newer security patch and I had tried to do an nandroid restore of an earlier version, at the end I tried this (I did try those steps with 9.0.12 full ROM first, the version of my nandroid):
adb sideload of the full 9.0.14 rom (the upgrade that got me into this dang fix). Then adb sideload of the TWRP installer. Then adb sideload of Magisk since I have read that this needs to be done after TWRP to make your phone boot. Still no good. Won't boot into anything but recovery. Tried the 3.3.1.6 advanced 'fix recovery reboot' or whatever it is, still to no avail.
At least I still have the yellow exclamation point and not the red one. And TWRP 3.3.1.6 stuck, so I am at the latest TWRP there is, at least from what I know.
Any more help or ideas so I can at least boot into my system one last time so I can do some Titanium or even the OnePlus backup? I just have some data that to backup correctly, I need to be able to boot system without wiping my data.
Please?
teddyearp said:
So. Today I tried to get this thing up and running. I went to the TWRP thread mentioned above and downloaded the latest files. Booted into bootloader, ran flashboot boot xxx.img and it booted into 3.3.1.6 just fine. The 'sdcard' was still encrypted so I couldn't copy the .img file and flash it via the newst instructions, , so I did an adb sideload of the installer file. That flashed just fine and I used TWRP to reboot recovery. Check. 'sdcard' still encrypted. Since this encryption issue seems to happen if you upgrade to a newer security patch and I had tried to do an nandroid restore of an earlier version, at the end I tried this (I did try those steps with 9.0.12 full ROM first, the version of my nandroid):
adb sideload of the full 9.0.14 rom (the upgrade that got me into this dang fix). Then adb sideload of the TWRP installer. Then adb sideload of Magisk since I have read that this needs to be done after TWRP to make your phone boot. Still no good. Won't boot into anything but recovery. Tried the 3.3.1.6 advanced 'fix recovery reboot' or whatever it is, still to no avail.
At least I still have the yellow exclamation point and not the red one. And TWRP 3.3.1.6 stuck, so I am at the latest TWRP there is, at least from what I know.
Any more help or ideas so I can at least boot into my system one last time so I can do some Titanium or even the OnePlus backup? I just have some data that to backup correctly, I need to be able to boot system without wiping my data.
Please?
Click to expand...
Click to collapse
This is the actual way to install or upgrade an OS
Boot to TWRP
ADB sideload oos 9.0.14
ADB sideload TWRP installer
Reboot system (Yes boot to system not TWRP..don't flash Magisk too now)
Let the phone boot
Go back to TWRP
Install Magisk
teddyearp said:
So, I decided to upgrade my OP6T with Renovate on it. Booted into TWRP (official from their website), did a Nandroid Backup. Now, I did remove my fingerprint and other security before starting. Flashed the full 9.0.14, reflashed TWRP, rebooted into TWRP, flashed Magisk, and then trid to boot into system. Got a bootloop where the phone was jumping in and out of the bootloader message. I tried to stop it by pressing power and volume down and it ended up booting into safe mode. I didn't like that so I booted into TWRP and restored my Nandroid. And that's when the fight started.
It won't boot into anything but TWRP now and everything is encrypted. I have been here before but last time, I got the device totally corrupt message and used MSM to recover. But that was within two weeks of owning the phone. Now it's been three months or so and I do not relish loosing all the pictures and other setting/changes I've made to my apps etc. I am NOT liking this decryption stuff.
So, is there something, anything I can do short of a fastboot rom and/or MSM tool that we all know will wipe out all data. What if I used the unofficial TWRP? Sideload the ROM again?
Any help is appreciated. I hope I didn't make this too long, but long enough to give enough detail of how I got here and that I somewhat know what I'm doing. Been doing this since the OG Motorola Droid almost 10 years ago.
Click to expand...
Click to collapse
What you should have done is not flashed magisk, but booted back to recovery, flashed oos again so you have it on both slots. Flashed TWRP again, booted back to recovery then flashed magisk and then to system.
If you had encountered encryption, you could either start fresh with MSM and have to re-root. Or you could have wiped data and sideloaded OOS & TWRP from an OTG or PC so you wouldn't have to go through the process of using adb and re-rooting.
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
That's a classic symptoms of the loss of encryption keys for the /data directory (for some reasons, despite the dual-boot setup sharing the same /data directory, but uses two separate different keys for each slots - a definite bad idea).
Sent from my ONEPLUS 6T using Tapatalk
teddyearp said:
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
Click to expand...
Click to collapse
Okay, to start off, before you started any of this what was you OS were you running?
That's what you need to try and sideload to try get the encryption back to normal because of the mismatch in security patches.
teddyearp said:
Well, thank you two very much, but . . . . crud. Here's what I've done now:
per sanjeev7 I did this:
Code:
boot to TWRP (it won't boot to anything else, lol)
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot system
It didn't boot to system, but booted back into TWRP so the additional step to sideload Magisk was moot.
So, then I went with what ebproject said above which on the surface looked more promising(?):
Code:
Boot TWRP
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot to TWRP via phone
adb sideload OnePlus6TOxygen_34_OTA_021_all_1905281358_e3b3.zip
adb sideload twrp-3.3.1-6-fajita-installer.zip
Reboot TWRP via phone
adb sideload Magisk-v19.3.zip
Reboot System
Still would not boot into system, but just back to recovery (TWRP).
I know I could probably do a data wipe after sideload TWRP installer, but I'm being stubborn. I have an app called Fuel Log that I track all my vehicle expenses on. I can make a backup within the software that I can then copy from the 'sdcard'. And I also have pdf maps which I would like to be able to access my 'sdcard' to get the most recent maps from, but it would be easy enough to get the two or six newest maps since my last backup of the files from my 'sdcard'. And then there's my stock tracking app which I don't think I can backup my current stuff without doing a Titanium. Still could be done manually. So at the end of the day, I really wish I could get into system just once to backup fuel log.
None of it is the end of the world, as I am going to receive a Oneplus 7 Pro tomorrow. I just wish I could make as seamless a transition as possible. I do have Titanium backups from a few months ago for all these above named apps, but like I said, if anyone has any ideas, please let me know.
What if I did the second set using OOS 9.0.12 instead of 9.0.14 since that is the version of the Nandroid backup that I restored? Or, and this is a long shot I know, what if I flashed a different ROM altogether? I do know that dirty flashing a different ROM is almost impossible, but maybe?
Click to expand...
Click to collapse
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
sanjeev7 said:
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
Click to expand...
Click to collapse
U can WhatsApp me on +918898340211
I would like to help u coming out! I have some experience in this!
If you are not sure how to boot into either slots in Fastboot, here's the slot switch command;
fastboot --set-active=a
(Set to Slot A, substitute with B if you want to boot into Slot B.)
Afterwards, reboot (you can alternatively reboot into the bootloader by typing into "fastboot reboot-bootloader" so you can retry the data salvation via fastbooted TWRP).
Sent from my ONEPLUS 6T using Tapatalk
ebproject said:
Okay, to start off, before you started any of this what was you OS were you running?
That's what you need to try and sideload to try get the encryption back to normal because of the mismatch in security patches.
Click to expand...
Click to collapse
I was on 9.0.12. I did already sideload the 9.0.12 app then sideload TWRP (version I mentioned above) then sideload Magisk. I obviously took a bit of a break, rec'd my OnePlus 7 Pro last night. And of course, like any good Andoird'er I had to get it all rooted and stuff, you know, first things first, lol. So tonight I will probably try some more.
As in I'll sideload 9.0.12, sideload TWRP, reboot system and if it works I'll not really worry about magisk since I will be in.
Thank you very much.
sanjeev7 said:
I replicated ur situation...and I have one cheat code for u
Boot into SLOT B if u r in SLOT A or vice versa!
The other SLOT is taking backup of current system before flashing successfully!! Try this!
---------- Post added at 11:31 AM ---------- Previous post was at 11:29 AM ----------
U can WhatsApp me on +918898340211
I would like to help u coming out! I have some experience in this!
Click to expand...
Click to collapse
Wow, thanks. I don't have Whatsapp and as my signature says, I usually try to read read read, then after doing some steps with fail, I give up and post, lol. So I was done by the time I posted.
Like I said in my previous post, I rec'd my 7 Pro last night and got it ready to be set the rest of the way up, so tonight I will try this new method. Just curious, should I do the slot switch within TWRP or should I do it as Dr. Mario said and use fastboot to switch?
Thanks a bunch everyone.
teddyearp said:
Wow, thanks. I don't have Whatsapp and as my signature says, I usually try to read read read, then after doing some steps with fail, I give up and post, lol. So I was done by the time I posted.
Like I said in my previous post, I rec'd my 7 Pro last night and got it ready to be set the rest of the way up, so tonight I will try this new method. Just curious, should I do the slot switch within TWRP or should I do it as Dr. Mario said and use fastboot to switch?
Thanks a bunch everyone.
Click to expand...
Click to collapse
U can simply go to TWRP and click on REBOOT...u will get option...SLOT A....SLOT B....try both the slots...one one time...I hope u boot!!
I was able to!
Either fastboot or TWRP, you can use either methods of switching the active slots. TWRP is much easier though.
Sent from my ONEPLUS 6T using Tapatalk
Well boys, I can't say I/we didn't give it the old college try. Dang it!
So, I'm not going to put out as much detail as I did before since by now you know what I'm doing step by step. I'll point out that the 9.0.12 file (yes I used that one) I used is this one: OnePlus6TOxygen_34_OTA_019_all_1901231347_fb09dd2d4.zip
So:
Boot into TWRP
sideload ROM
sideload TWRP
Went to reboot menu (in TWRP) saw that I was on slot a, but just used the Recovery reboot button. Once back into TWRP, I went again to the Reboot menu and saw that I was already now on slot b. Repeated above and then sideloaded Magisk. Reboot. Back to TWRP only. Ugh! Tried it again, but instead of rebooting TWRP after the one slot, just changed slots without rebooting TWRP and repeated. Did not sideload Magisk. Still a fail.
I'm about done here, but there was one message on my computer within the command window that was shown after the second flash of the ROM on both tries:
ADB: Failed to read command: no error.
What a journey! Thanks guys. And/or girls if any of you are girls, hehe.
ozzmanj1 said:
I can back up and restore nandroid no issue although I remove any pin code/face unlock/fingerprint prior to backing up. No issues.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
Click to expand...
Click to collapse
teddyearp said:
<snip> Now, I did remove my fingerprint and other security before starting. <snip>
Click to expand...
Click to collapse
Thank you, but I do believe that I did do that.
I was wondering if there is alternative option for Oneplus 6T/fajita recovery, like OrangeFox, RedFox, or other recoveries beside TWRP. TWRP doesn't work to restore on OP6T after backup. If I try to restore from previous backup, I will always end up in a continuous boot loop :'( and to resolve is issue, I have to flash the original ROM again but that affects some of my apps, so I have to check each app and reinstall them. In general TWRP doesn't work well on OP6T like other phones, and I couldn't find any alternative recovery options, and I wish someone is working on this.
Please let me know, even if there is beta or unofficial version that works with full ROM Backup and restore.
Thank you
FYI- I tried TWRP on different Pie custom Roms and OOS9 but the result is always the same, endless boot loop.
Nothing exists
You just taking a wrong steps while restoring. I've already done a two or three successful restores
Just backup these partitions:
1. Boot
2.System image
3.Vendor image
4.Data
romixer said:
You just taking a wrong steps while restoring. I've already done a two or three successful restores
Just backup these partitions:
1. Boot
2.System image
3.Vendor image
4.Data
Click to expand...
Click to collapse
I tried in that order and it doesn't work. I always end up in the boot-loop.
I even tried the following steps.
1. Boot to twrp recovery after full backup
2.Restore System image only
3.Reboot to twrp recovery
4.Restore Vendor image only
5.Reboot to twrp recovery again
6.Restore Data only
7.Restart
=>End result is the same, boot-loop.
I think TWRP is only good to flash zip files on Oneplus 6T .
duckduck2020 said:
I tried in that order and it doesn't work. I always end up in the boot-loop.
I even tried the following steps.
1. Boot to twrp recovery after full backup
2.Restore System image only
3.Reboot to twrp recovery
4.Restore Vendor image only
5.Reboot to twrp recovery again
6.Restore Data only
7.Restart
=>End result is the same, boot-loop.
I think TWRP is only good to flash zip files on Oneplus 6T .
Click to expand...
Click to collapse
You must be doing something wrong, perhaps using the wrong outdated version? The latest "unofficial" version posted here works, I can personally attest to that, but the older "official" version available on the TWRP site doesn't. It's outdated, and only works with Oreo and older ROMs.
There were issues with the "unofficial" TWRP and "Q" up until a couple of months ago that required the flashing of an additional file to get it to work properly, because of encryption errors, but even during that time period it was still working as expected on Pie.
Double check what you're doing, as you are making a mistake somewhere. The problem isn't with TWRP.
Link to the OP in the TWRP developer's thread here.
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
Did you get twrp installed? Wipe data by typing yes after flashing?
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
You can follow this. If you want to install lineage os and want Google service make sure follow the "non gapp version" under installation method.
Havoc Flashing Notes for OnePlus 6 /6T from OOS 11 [Using TWRP Recovery]
1. Clean Flash : 2. Dirty Flash 3. Update oos base 1. Clean Flash : 🔊 Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; we're going to format the data partition and you're going to lose everything from internal storage. Basic requirements ○...
telegra.ph
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my 6T.
dequadim said:
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my
Click to expand...
Click to collapse
OnePlus definitely didn't do anything to make it harder. You need to fastboot boot twrp.img then flash the twrp installer zip. I'll attach both In next post. Reboot to recovery. Then install OOS, twrp installer, reboot to recovery. Install oos again, twrp installer again, reboot to recovery. Now install lineage, twrp installer, reboot to recovery. Install lineage again, twrp installer again, reboot to recovery. Factory reset and wipe data by typing yes. Boot to system
The img is for fastboot boot
The zip is for installing in twrp
Thanks for your reply.
I'm still wondering how to speed up the boot.
dequadim said:
Thanks for your reply.
I'm still wondering how to speed up the boot.
Click to expand...
Click to collapse
If everything is installed correctly it won't take long to boot
Brettroth said:
If everything is installed correctly it won't take long to boot
Click to expand...
Click to collapse
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really wrong
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really
dequadim said:
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
Click to expand...
Click to collapse
You sure you didn't try 3.6.0_9?
Clearing your cache might help with current boot. But once you install a new os everything will run smooth like it should
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
dequadim said:
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
Click to expand...
Click to collapse
That twrp version always will crash dump on a11. Use the one I sent
I followed these steps:
after having managed to make MSM Download Tool detect the phone in EDL mode, I proceeded by reinstalling OOS v9.0.13, after which I reconfigured the phone and restored the apps backup stored in my Google account.
Later, I don't remember the details well, I received the update notification for OOS v10 and later for OOs v11.1.2.2.
I don't remember exactly where the boot started to stretch, however this is more or less the process I followed to bring my 6T back to life.
Brettroth said:
That twrp version always will crash dump on a11. Use the one I sent
Click to expand...
Click to collapse
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
dequadim said:
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
Click to expand...
Click to collapse
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Brettroth said:
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Click to expand...
Click to collapse
Keep your finger crossed...
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
dequadim said:
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
Click to expand...
Click to collapse
Or you could use USB OTG. Or a PC and use adb sideload