TWRP Bootloop - OnePlus 6 Questions & Answers

Hey, is there any change i can get my OP6 back working when I did these steps:
fastboot boot twrp.img
and then in twrp i flashed twrp to /boot which obviously wasnt a good idea. now im stuck in twrp bootloop
any ideas how to fix that?

Did you flash magisk zip afterwards? Ut could be the reason for the bootloops. Good luck.

Gr8man001 said:
Did you flash magisk zip afterwards? Ut could be the reason for the bootloops. Good luck.
Click to expand...
Click to collapse
No i didnt, im not even sure now that flashing twrp to boot is right :s
I tried this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
but it cant find my device, but thats probably an ADB issue because i can see it in recovery with my ADB version installed.
EDIT: i could resolve it with the restore tool from the linked thread. the problem was the tool wasnt working correctly and i had to reboot the phone (no idea why it wouldnt work the first boot into fastboot)

If you can get back into fastboot then this might work https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

Related

Fastboot loop - device won't load recovery

Hi all,
so after system update of OOS which ended up in a boot loop and losing the TWRP recovery (back to stock)
I was trying to get TWRP (back again) via fastboot I was able once to get TWRP loaded once and was even lucky to able to load the Nandroid backup "successfully".
but unfortunately, after restarting...nothing... always getting back to fastboot main screen with no success of booting normally or into recovery mode.
also, not able to re-flash the twrp.img to reach again for the backup.
is there another way to get back TWRP and load my backup file? by using fastboot commands?
I just had the same issue.
I managed to fix it using a fastboot image https://drive.google.com/open?id=1fqvjJ-lC7w2wtcxYwlbmZ4pRW60psODV
After the flash completed I booted into the OS then rebooted back to fastboot and from there I was able to use fastboot command to boot into TWRP
Had a similar issue after installing a rom a while back. Posted about it here https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-trying-to-install-omnirom-t3849882
Google the mega unbrick guide on the OnePlus forums. Let me know if this helps at all. Or give the other link posted there a try as well.
dekela said:
I just had the same issue.
I managed to fix it using a fastboot image https://drive.google.com/open?id=1fqvjJ-lC7w2wtcxYwlbmZ4pRW60psODV
After the flash completed I booted into the OS then rebooted back to fastboot and from there I was able to use fastboot command to boot into TWRP
Click to expand...
Click to collapse
Nice, we're from the same city.
anyhow, have you flashed this by doing "fastboot flash XYZ.zip" ? & afterwards flashed the TWRP again?
nicb1 said:
Had a similar issue after installing a rom a while back. Posted about it here https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-trying-to-install-omnirom-t3849882
Google the mega unbrick guide on the OnePlus forums. Let me know if this helps at all. Or give the other link posted there a try as well.
Click to expand...
Click to collapse
Thanks for the tip. so after this operation/guide will I'll be able to restore my Nandorid Backup or with will erase it completely ? just a new ROM with stock recovery, right?
QIQgame said:
Nice, we're from the same city.
anyhow, have you flashed this by doing "fastboot flash XYZ.zip" ? & afterwards flashed the TWRP again?
Thanks for the tip. so after this operation/guide will I'll be able to restore my Nandorid Backup or with will erase it completely ? just a new ROM with stock recovery, right?
Click to expand...
Click to collapse
Np. I cant remember exactly but i think it wiped the phone. You won't be able to restore that backup unless you happen to have copied it externally from your phone before the brick.
Let us know if you manage to get it all fixed and going again. Know its frustrating having your phone bricked. Pretty much brought it back to its factory shipped state from what I remember.
QIQgame said:
Nice, we're from the same city.
anyhow, have you flashed this by doing "fastboot flash XYZ.zip" ? & afterwards flashed the TWRP again?
Thanks for the tip. so after this operation/guide will I'll be able to restore my Nandorid Backup or with will erase it completely ? just a new ROM with stock recovery, right?
Click to expand...
Click to collapse
Use this to flash a fastboot image:
https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993

Open Beta 2 Magisk problem.

Hello all I'm having a problem with the OB2 and magisk. It seems to randomly work. The first time i tried to install it it would just get stuck in fastboot mode. And every time i try to install it in Magisk manager I get a unsupported/unknown image with both the official and canary builds. But two of the times I have tried it all worked using the same files i did before. But as soon as I reboot I'm stuck in fastboot mode again. Anybody know what could be causing this?
Did you do a Fresh install or Update from what?
You are Unrooted and it wont install itself via the app. you need to flash a patched boot image via fastboot.
I was just following the guide flashing in the app was just to test. It wouldn't flash in TWRP either which is what all the guides say to do. Thats when it just goes to fastboot mode. I am also coming from the OB1 which i did the exact same thing along with previous pie versions and worked with no problems. Even tried the All in one tool and does the same thing.
If TWRP is working then do a full wipe and install OB2 off a USB with an OTG cable. Flash OB2 and TWRP then reboot back into recovery and Flash Magisk 19.4
The same issue happen with me, i guess i will revert to Android 9
Follow this guide
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
null0seven said:
Follow this guide
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Click to expand...
Click to collapse
Yep followed it and diden't work. But now I have a bricked problem trrying to fix this. Stuck in bootloader/fastboot mode.
Try Fastboot rom by Mauronofrio. You need a working Fastboot
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
If it still not work MSM tool.
null0seven said:
Try Fastboot rom by Mauronofrio. You need a working Fastboot
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
If it still not work MSM tool.
Click to expand...
Click to collapse
OK got it fixed starting from scratch using the How to convert TMobile OP7 to International guide over again. Thanks for your help.
Anybody got ok Google working on the open beta 2
CptKlink said:
Hello all I'm having a problem with the OB2 and magisk. It seems to randomly work. The first time i tried to install it it would just get stuck in fastboot mode. And every time i try to install it in Magisk manager I get a unsupported/unknown image with both the official and canary builds. But two of the times I have tried it all worked using the same files i did before. But as soon as I reboot I'm stuck in fastboot mode again. Anybody know what could be causing this?
Click to expand...
Click to collapse
Did you disable magisk modules

Anyone please let me know the OOS 10 and TWRP/Magisk Situation...

I am currently on OOS 10 OB2/31 and can't seem to find a way to install TWRP and Magisk. Found ways to install TWRP and Magisk via patched boot images on OOS 10 stable but not for OB2/31.... anyone know why it's not as simple as flashing TWRP via fastboot?
I also have a problem
'OOS10beta31' Root
XcutionerX said:
[...] anyone know why it's not as simple as flashing TWRP via fastboot?
Click to expand...
Click to collapse
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
Thank you for your help, gonna try following those. Hopefully I don't f up and have to do a msm restore. But why would they disable that command?... Just to make everything complicated? Guess I will not stick to Oneplus next year.
XcutionerX said:
But why would they disable that command?
Click to expand...
Click to collapse
Security? Deprecated or soon-to-be-deprecated command? Dunno really, lol.
XcutionerX said:
... Just to make everything complicated?
Click to expand...
Click to collapse
To be fair, the only difference between this method and the old method is just one word and manually rebooting to recovery. You still have to flash the twrp.zip after flashing from bootloader file to install TWRP, so it's not too radically different.
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
adeklipse said:
Because OnePlus upgraded the bootloader in their OOS10 release. One of the changes was disabling the fastboot boot command that you usually needed to boot to TWRP. Without that command, you had to flash the TWRP img files onto the boot partition first in order to be able to boot TWRP.
There are many -- maybe a bit too many -- guides on how to install TWRP on OOS10. Here and here are some I found.
The gist of it is to boot to TWRP by running the fastboot flash boot twrp_file.img command, rebooting to recovery, then flashing the twrp zip file. And that's pretty much it.
PS In my case, I wasn't able to reboot to TWRP by using mauronofrio's twrp-3.3.1-14 version, and had to use his twrp-3.3.1-11 instead.
Click to expand...
Click to collapse
I have successfully installed TWRP and Magisk with the help of those links. Thank you again for your help.
quizzina said:
this can help
https://forum.xda-developers.com/showpost.php?p=80897567&postcount=332
Click to expand...
Click to collapse
Thank your for the in-depth explanation.
Just download oxygen updater and install 10.0.1 and be done with it

flashed TWRP over boot slot B

I ended up flashing TWRP over my boot slot (B) and now I just boot into TWRP. I have already installed TWRP on boot slot (a). I can't remember which version of oxygenOS I have installed and couldn't find a way to confirm. How can I fix this? Also want to update to latest version of oxygenOS and android. No data on phone yet. phone still connects to computer, adb sideloader and fastboot commands still work work. Thanks
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
redpoint73 said:
Are you saying you did fastboot flash boot of the TWRP img? You should be doing fastboot boot TWRP img, then flash the TWRP installer zip.
You can get the OS back up and running by flashing the correct boot.img via fastboot. Or use one of the fastboot stock ROMs.
Click to expand...
Click to collapse
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
doctor_whooves said:
ya, I fastboot flash boot the TWRP img following this video youtu.be/3oSycujvmP8?t=296
I guess I'll start flashing boot images until I land on the correct OS version, thanks
Click to expand...
Click to collapse
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
plasticarmyman said:
never follow youtube guides...
follow the guides that are up to date here on XDA.
Look for the TWRP thread and follow the steps there.
boot to fastboot
boot TWRP image
Flash TWRP installer
success
Click to expand...
Click to collapse
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
tech_head said:
But to recover his phone, the OP will need the original boot.img from his OS version.
OP has already messed up the boot partition.
That has to be fixed first.
Click to expand...
Click to collapse
in this case the best thing to do is just unbrick using MSM
plasticarmyman said:
in this case the best thing to do is just unbrick using MSM
Click to expand...
Click to collapse
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
doctor_whooves said:
Yes, I had to unbrick using msm. It worked. Was able to get phone rooted and stock recovery replaced with TWRP but it was a much bigger pain than I expected.
Click to expand...
Click to collapse
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
hey guys. Not able to flash oos through twrp.
getting "error flashing zip".
tech_head said:
Glad you got it recovered.
There is an application called "Partitions Backup".
It allows you to back up all the phone partitions. The one you really want to backup from now on is the boot_a and boot_b.
Since you are rooted when you do an upgrade, grab the boot_a and boot_b before installing Magisk after the install.
This allows you to go back to stock. After you back them up, copy them to a computer.
Click to expand...
Click to collapse
Doesn't TWRP back up everything including boot partitions?
Is there nothing that will take the entire internal storage and just make a 'bare metal' image of it for restoring.. the whole entire thing, byte for byte? If not, why doesn't this exist? It just seems so logical to me and would be so incredibly useful. Phone borked? No problem. Just re-image it form the archive you made. To me, that is what TWRP is all about, at least conceptually if not technically.

[Help Needed] Semi Bricked - Remove substratum overlay or somehow backup my data

Hey Guys,
So my idiot brain decided to mess around with substatum themes after I updated and rerooted my OP7P. I rooted with magisk but forgot to put TWRP recovery on.
Anyways, got the phone semi bricked when applying one of the overlays. The phone boots and I can see my lock screen wallpaper but the screen is just flashing on/off.
I cant use the fingerprint or pin to get it. Is there a way for me to backup my pictures and data or somehow remove substratum?
Biggest problem is that for whatever reason, the update revoked my ADB authorization so it looks like I cant do anything with ADB.
If someone has any way to salvage my situation, please reply. Factory reset is my last resort due to no backup.
Thank You
Try booting into TWRP and using ADB there.
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
tech_head said:
Try booting into TWRP and using ADB there.
Click to expand...
Click to collapse
pranacrockz said:
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
Click to expand...
Click to collapse
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
morphius88 said:
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
Click to expand...
Click to collapse
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
pranacrockz said:
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
Click to expand...
Click to collapse
Rebooted to fastboot, entered the PIN but Fastboot is a no go. Just keeps saying <waiting for any device> and nothing happens. Would that be because the authorization keys were not accepted after the update?
I am downloading the MSM Tool and will try that if I cant get it to work with fastboot. Will update if it works.
Thanks for suggestions
Ended up using the MSM tool. Did not know it wipes data and also put me back to Android 9.
Oh well, lesson learned. Gotta make monthly backups, make sure twrp is installed and working before messing around with substatrum.
Thanks for the help.

Categories

Resources