Stuck on 'The bootloader in unlocked' screen - OnePlus 6T Questions & Answers

Hi
Have an unrooted international version of OnePlus6t. decided to upgrade from 9.0.17 to 10.0.1 and root. Decided to follow [Ultimate-Guide] ★ OnePlus 6T OOS-10 TWRP-Root-Magisk from OOS-9 guide, Method 3.
Installed 10.0.1 , phone booted OK,
restarted to bootloader
Stock Recovery >> "Wipe data and cache" > "Erase everything" > Reboot to Bootloader
fastboot flash boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img
Changed to Slot B
reboot to recovery
Stock Recovery >> "Wipe data and cache" > "Erase everything" > Reboot to Bootloader
fastboot flash boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img
Now phone is just showing "The bootloader is unlocked and software integrity cannot be guaranteed blah blah blah' screen. What can i do?
Please advise
Thanks in advance
P.S. Power+VolumeUp buttons combination just turns phone off. When I turn it on again, phone stucks on the same screen
UPD: OK I am able to get into fastboot mode. What can be done next?
UPD 2: Using mauronofrio's AllInOne tool I was able to boot twrp for Pie, change slot back to A and voila! I have TWRP and Andriod 10.0.1 back again. Hooray!
Now the only thing that bothers me is that seems that I have Q on SlotA and Pie on SlotB. Can it cause any unwanted effects?

How did you force getting into bootloader please? I'm in same boat!

Well the first thing is that you can't flash twrp as a boot partition. Twrp is a recovery, not a kernel. You are supposed to to fastboot boot twrp

557953 said:
How did you force getting into bootloader please? I'm in same boat!
Click to expand...
Click to collapse
Disconnect phone from computer, press VoulmeUp+Power keys together to turn off the phone, then press VolumeDown+Power keys to get into bootloader

You erased everything? I guess you have to flash your image again (10.0.1). Just don't use twrp if you don't need it. Go back to stock recovery, install 10.0.1. let it boot. Then after everything is done, flash the patched boot.img (install magisk manager first though).

bokkoman said:
You erased everything? I guess you have to flash your image again (10.0.1). Just don't use twrp if you don't need it. Go back to stock recovery, install 10.0.1. let it boot. Then after everything is done, flash the patched boot.img (install magisk manager first though).
Click to expand...
Click to collapse
I already did that and my phone is working now with OOS 10.0.1. I wonder should i get to TWRP somehow, change to SlotB and flash stock 10.0.1 again?

BesoC said:
I already did that and my phone is working now with OOS 10.0.1. I wonder should i get to TWRP somehow, change to SlotB and flash stock 10.0.1 again?
Click to expand...
Click to collapse
Why do you need TWRP?

Same issue caused by same process. Not able to get into bootloader screen using the method described. Ugh
Luckily I still have my last phone I can use until I figure this out. Yay Nexus 5X!

Same boat...
g90814 said:
Same issue caused by same process. Not able to get into bootloader screen using the method described. Ugh
Luckily I still have my last phone I can use until I figure this out. Yay Nexus 5X!
Click to expand...
Click to collapse
...I was able to get into bootloader (fastboot mode?) by holding Vol up & down as well as power button (all three depressed together) for about 15 seconds
entered -
fastboot flash boot twrp-3.3.1-28-fajita-Q-mauronofrio.img
at least I have a recovery now...in slot A

bokkoman said:
Why do you need TWRP?
Click to expand...
Click to collapse
Just to flush stock 10.0.1 to SlotB

g90814 said:
Same issue caused by same process. Not able to get into bootloader screen using the method described. Ugh
Luckily I still have my last phone I can use until I figure this out. Yay Nexus 5X!
Click to expand...
Click to collapse
Did you turned off your phone? You should hold VolUp+Power buttons until phone turns off - about 10-15 seconds. Then Press VolDown+Power to get into bootloader

BesoC said:
Just to flush stock 10.0.1 to SlotB
Click to expand...
Click to collapse
You don't need TWRP for that. If you only want root with stock oxygenos, I'd recommend not to install twrp.
You don't need it, unless you want to install custom stuff (kernels, roms, patches etc) constantly.
If you just want stay on stock OOS. Just update through android and patch magisk after update with installing to inactive slot (before reboot).

BesoC said:
Just to flush stock 10.0.1 to SlotB
Click to expand...
Click to collapse
And what for? A/B devices are not meant to have the same rom on both slots.
Just run your Android 10.0.1 now, don't bother at all about slots, and on next update it will install on inactive slot, you'll just have to install Magisk on inactive slot before rebooting as said just above.
It you don't plan to flash custom ROMs you don't need twrp.

BesoC said:
Did you turned off your phone? You should hold VolUp+Power buttons until phone turns off - about 10-15 seconds. Then Press VolDown+Power to get into bootloader
Click to expand...
Click to collapse
As I stated, I followed the steps the OP had posted. The phone would turn off, but would not boot into bootloader mode, it just showed the initial screen. Believe me, I tried!
I've sent the phone back to OnePlus for repair/replacement, I was well under the warranty period.

BesoC said:
Hi
Have an unrooted international version of OnePlus6t. decided to upgrade from 9.0.17 to 10.0.1 and root. Decided to follow [Ultimate-Guide] ★ OnePlus 6T OOS-10 TWRP-Root-Magisk from OOS-9 guide, Method 3.
Installed 10.0.1 , phone booted OK,
restarted to bootloader
Stock Recovery >> "Wipe data and cache" > "Erase everything" > Reboot to Bootloader
fastboot flash boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img
Changed to Slot B
reboot to recovery
Stock Recovery >> "Wipe data and cache" > "Erase everything" > Reboot to Bootloader
fastboot flash boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img
Now phone is just showing "The bootloader is unlocked and software integrity cannot be guaranteed blah blah blah' screen. What can i do?
Please advise
Thanks in advance
P.S. Power+VolumeUp buttons combination just turns phone off. When I turn it on again, phone stucks on the same screen
UPD: OK I am able to get into fastboot mode. What can be done next?
UPD 2: Using mauronofrio's AllInOne tool I was able to boot twrp for Pie, change slot back to A and voila! I have TWRP and Andriod 10.0.1 back again. Hooray!
Now the only thing that bothers me is that seems that I have Q on SlotA and Pie on SlotB. Can it cause any unwanted effects?
Click to expand...
Click to collapse
I am currently experiencing the same issue, how did you get it to go into fastboot mode? I've been traying for hours!

Related

A2017G Bootloader mode on 7.1.1?

EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally​ it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?

Nougat update

Is there any way to update to android 7.0 emui 5 from stock marshmallow without deleting data?
sirjumpsalot said:
Is there any way to update to android 7.0 emui 5 from stock marshmallow without deleting data?
Click to expand...
Click to collapse
if you already have bootloader unlocked is ok.
if not, after unlock will be a factory reset...
gtdaniel said:
if you already have bootloader unlocked is ok.
if not, after unlock will be a factory reset...
Click to expand...
Click to collapse
My bootloader is unlocked,rooted and twrp installed.I have VNS-L31C432B160.So first,I have to unroot,and then install nougat via proxy method or flash via twrp? After that I dont have to factory reset? Or do I?
sirjumpsalot said:
My bootloader is unlocked,rooted and twrp installed.I have VNS-L31C432B160.So first,I have to unroot,and then install nougat via proxy method or flash via twrp? After that I dont have to factory reset? Or do I?
Click to expand...
Click to collapse
What i do:
1. Unlock bootloader folowing by Automatic Factory Reset. - already done by you
2. Flash TWRP - already done by you
3. From TWRP flash Meticulus TWRP
4. Reboot to TWRP and flash update.zip and update_data_full_VNS-L31_hw_eu.zip, both flash ends with errors, without reboot between flashes.
5. After that, reboot device and boot in system ok, start configuration, etc.
6. Reboot to fastboot and flash Nougat Recovery reworked by @BadWolfYe
gtdaniel said:
What i do:
1. Unlock bootloader folowing by Automatic Factory Reset. - already done by you
2. Flash TWRP - already done by you
3. From TWRP flash Meticulus TWRP
4. Reboot to TWRP and flash update.zip and update_data_full_VNS-L31_hw_eu.zip, both flash ends with errors, without reboot between flashes.
5. After that, reboot device and boot in system ok, start configuration, etc.
6. Reboot to fastboot and flash Nougat Recovery reworked by @BadWolfYe
Click to expand...
Click to collapse
Thank you so much Will do it right now.About the 6th step,the Nougat Recovery one,that is optional right?
sirjumpsalot said:
Thank you so much Will do it right now.About the 6th step,the Nougat Recovery one,that is optional right?
Click to expand...
Click to collapse
I do not called optional, because in Nougat you do not have recovery...
gtdaniel said:
if you already have bootloader unlocked is ok.
if not, after unlock will be a factory reset...
Click to expand...
Click to collapse
But when I unlock the bootloader, I do not lose my data.
I type the code, when I validate on the phone, (1: volume +, then 2: power to validate). It must go quickly.
I press down on volume and power to return to fastboot mode and then install twrpMM, reboot.
At restart, there is all my data.
Then install the two files nougat, reboot, there is always my data.
Chisetdel31260 said:
But when I unlock the bootloader, I do not lose my data.
I type the code, when I validate on the phone, (1: volume +, then 2: power to validate). It must go quickly.
I press down on volume and power to return to fastboot mode and then install twrpMM, reboot.
At restart, there is all my data.
Then install the two files nougat, reboot, there is always my data.
Click to expand...
Click to collapse
Yeap, is very tricky...
From 4-5 times i succeeded 2 times...
gtdaniel said:
Yeap, is very tricky...
From 4-5 times i succeeded 2 times...
Click to expand...
Click to collapse
Just forget fastboot reboot forever.

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

Stuck on "Fastboot Mode" screen

I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?
soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.
Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..
THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.
Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (

Stuck in Bootloader with Magisk, Boots Correctly Without Magisk

Phone: A6010
OOS: 9.0.17
TWRP: twrp-3.2.3-x_blu_spark_v9.91_op6
Magisk: Magisk-v19.3
PC OS: Manjaro Linux with Android SDK tools
Hello folks. This issue started happening last night. I rebooted the phone (hold down Power button, hit Restart), but when it rebooted, it stayed on the "bootloader unlocked" warning screen for a long time, and would then enter the bootloader. This has never happened before, even after the latest OTA update to 9.0.17 (after which the phone was successfully re-rooted following these instructions.)
If "Power Off" was selected, the screen would turn off without the corresponding buzz from the internal vibrator to show that the phone was powered down. Instead, it would reboot into Fastboot mode and then into the bootloader.
I've tried the following steps to troubleshoot:
1. fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img
adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip and reboot into recovery
adb sideload Magisk-v19.3.zip
Result: stuck at "bootloader unlocked" warning screen & enters bootloader
2. Tried the same steps in #1 but with Magisk v19.4 and 20.0. Same result.
3. Same steps in #1 but flashed Magisk-uninstaller-20191011.zip as the final step. Result, phone boots up correctly but without root.
4. Rebooted into bootloader
fastboot boot twrp-3.3.1-8-fajita.img
copied the same file to phone & Advanced -> Install Recovery Ramdisk -> twrp-3.3.1-8-fajita.img
reboot into Recovery & adb sideload Magisk-v19.4.zip
Same result as before, stuck at warning screen and then into bootloader.
5. Re-did #3 i.e. back to twrp-3.2.3-x_blu_spark_v9.91_op6 and uninstalled Magisk. Phone once again boots up correctly but without root. This is where I am now.
The phone can successfully boot to Recovery from Bootloader. I also tried to power down the phone from Recovery mode, which it did correctly (with corresponding vibrator buzz), but when powered back on would go back to "warning screen"/bootloader issue when Magisk was still installed.
Without Magisk, the phone powers down correctly, boots up correctly, and reboots correctly albeit all without root.
At this point, i've no idea what's going on or how to proceed further. There are some threads discussing MsmDownloadTool but the latest version available is for 9.0.16 in this thread, which i think can't be used for 9.0.17.
Suggestions on how to proceed would be most appreciated. Thank you in advance for your time.
SkyLukewalker said:
Phone: A6010
OOS: 9.0.17
TWRP: twrp-3.2.3-x_blu_spark_v9.91_op6
Magisk: Magisk-v19.3
PC OS: Manjaro Linux with Android SDK tools
Hello folks. This issue started happening last night. I rebooted the phone (hold down Power button, hit Restart), but when it rebooted, it stayed on the "bootloader unlocked" warning screen for a long time, and would then enter the bootloader. This has never happened before, even after the latest OTA update to 9.0.17 (after which the phone was successfully re-rooted following these instructions.)
If "Power Off" was selected, the screen would turn off without the corresponding buzz from the internal vibrator to show that the phone was powered down. Instead, it would reboot into Fastboot mode and then into the bootloader.
I've tried the following steps to troubleshoot:
1. fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img
adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip and reboot into recovery
adb sideload Magisk-v19.3.zip
Result: stuck at "bootloader unlocked" warning screen & enters bootloader
2. Tried the same steps in #1 but with Magisk v19.4 and 20.0. Same result.
3. Same steps in #1 but flashed Magisk-uninstaller-20191011.zip as the final step. Result, phone boots up correctly but without root.
4. Rebooted into bootloader
fastboot boot twrp-3.3.1-8-fajita.img
copied the same file to phone & Advanced -> Install Recovery Ramdisk -> twrp-3.3.1-8-fajita.img
reboot into Recovery & adb sideload Magisk-v19.4.zip
Same result as before, stuck at warning screen and then into bootloader.
5. Re-did #3 i.e. back to twrp-3.2.3-x_blu_spark_v9.91_op6 and uninstalled Magisk. Phone once again boots up correctly but without root. This is where I am now.
The phone can successfully boot to Recovery from Bootloader. I also tried to power down the phone from Recovery mode, which it did correctly (with corresponding vibrator buzz), but when powered back on would go back to "warning screen"/bootloader issue when Magisk was still installed.
Without Magisk, the phone powers down correctly, boots up correctly, and reboots correctly albeit all without root.
At this point, i've no idea what's going on or how to proceed further. There are some threads discussing MsmDownloadTool but the latest version available is for 9.0.16 in this thread, which i think can't be used for 9.0.17.
Suggestions on how to proceed would be most appreciated. Thank you in advance for your time.
Click to expand...
Click to collapse
MSM is your way to go. It will downgrade your phone to 9.0.17 and lock your Bootloader. After that you can unlock it and take the OTA Again. You will lose all your Data. Another thing you can try is to Format Data in TWRP. That will also cause you to loose all your Data but you might be able to boot up with Root.
Mannan Qamar said:
MSM is your way to go. It will downgrade your phone to 9.0.17 and lock your Bootloader. After that you can unlock it and take the OTA Again. You will lose all your Data. Another thing you can try is to Format Data in TWRP. That will also cause you to loose all your Data but you might be able to boot up with Root.
Click to expand...
Click to collapse
Thank you for the reply.
At this point, I'm kinda resigned to losing all data, so i did a backup this morning. However, I need my phone to be functional over this weekend, and will do as you have suggested on Monday after another backup.
Will start with the Format Data in TWRP method first, since i'm running Linux and have to setup a VM with USB passthrough to run Win7 and Msm.
Just to confirm, since i'm already running 9.0.17, is it okay simply to use MsmDownloadTool v4.0.59 if it comes to that? Thanks in advance.
On a sidenote, since data loss is inevitable, once it's confirmed that the phone boots up correctly with root and stock OOS, it may just be worth moving to LOS16 thereafter.
Mannan Qamar said:
MSM is your way to go. It will downgrade your phone to 9.0.17 and lock your Bootloader. After that you can unlock it and take the OTA Again. You will lose all your Data. Another thing you can try is to Format Data in TWRP. That will also cause you to loose all your Data but you might be able to boot up with Root.
Click to expand...
Click to collapse
I had time today, and tried Format Data. Didn't work. Installing Magisk landed the phone in the same error screen.
So the Win7 VM was fired up and the instructions for Msm were followed. The phone is recognized and the drivers were successfully installed, showing up as Qualcomm HS-USB QDLoader 9008 (COM3)
However, when MsmDownloadTool V4.0.59 -- 9.0.16 was launched and Start was pressed, the operation times out with the message "Sahara Communication Failed. Please try again after power off phone."
This is despite powering off using the normal method within OOS itself, or powering off from within TWRP.
Not sure how to proceed. Please help?
SkyLukewalker said:
I had time today, and tried Format Data. Didn't work. Installing Magisk landed the phone in the same error screen.
So the Win7 VM was fired up and the instructions for Msm were followed. The phone is recognized and the drivers were successfully installed, showing up as Qualcomm HS-USB QDLoader 9008 (COM3)
However, when MsmDownloadTool V4.0.59 -- 9.0.16 was launched and Start was pressed, the operation times out with the message "Sahara Communication Failed. Please try again after power off phone."
This is despite powering off using the normal method within OOS itself, or powering off from within TWRP.
Not sure how to proceed. Please help?
Click to expand...
Click to collapse
Could be an issue with the VM. I'd also try to change USB Port or try another Cable.
SkyLukewalker said:
Phone: A6010
OOS: 9.0.17
TWRP: twrp-3.2.3-x_blu_spark_v9.91_op6
Magisk: Magisk-v19.3
PC OS: Manjaro Linux with Android SDK tools
Hello folks. This issue started happening last night. I rebooted the phone (hold down Power button, hit Restart), but when it rebooted, it stayed on the "bootloader unlocked" warning screen for a long time, and would then enter the bootloader. This has never happened before, even after the latest OTA update to 9.0.17 (after which the phone was successfully re-rooted following these instructions.)
If "Power Off" was selected, the screen would turn off without the corresponding buzz from the internal vibrator to show that the phone was powered down. Instead, it would reboot into Fastboot mode and then into the bootloader.
I've tried the following steps to troubleshoot:
1. fastboot boot twrp-3.2.3-x_blu_spark_v9.91_op6.img
adb sideload twrp-3.2.3-x_blu_spark_v9.91_op6.zip and reboot into recovery
adb sideload Magisk-v19.3.zip
Result: stuck at "bootloader unlocked" warning screen & enters bootloader
2. Tried the same steps in #1 but with Magisk v19.4 and 20.0. Same result.
3. Same steps in #1 but flashed Magisk-uninstaller-20191011.zip as the final step. Result, phone boots up correctly but without root.
4. Rebooted into bootloader
fastboot boot twrp-3.3.1-8-fajita.img
copied the same file to phone & Advanced -> Install Recovery Ramdisk -> twrp-3.3.1-8-fajita.img
reboot into Recovery & adb sideload Magisk-v19.4.zip
Same result as before, stuck at warning screen and then into bootloader.
5. Re-did #3 i.e. back to twrp-3.2.3-x_blu_spark_v9.91_op6 and uninstalled Magisk. Phone once again boots up correctly but without root. This is where I am now.
The phone can successfully boot to Recovery from Bootloader. I also tried to power down the phone from Recovery mode, which it did correctly (with corresponding vibrator buzz), but when powered back on would go back to "warning screen"/bootloader issue when Magisk was still installed.
Without Magisk, the phone powers down correctly, boots up correctly, and reboots correctly albeit all without root.
At this point, i've no idea what's going on or how to proceed further. There are some threads discussing MsmDownloadTool but the latest version available is for 9.0.16 in this thread, which i think can't be used for 9.0.17.
Suggestions on how to proceed would be most appreciated. Thank you in advance for your time.
Click to expand...
Click to collapse
Why are you using TWRP from OP6 so old too? Here for OP6T there is newer https://github.com/engstk/android_device_oneplus_fajita/releases/tag/v9.101
elSkelet said:
Why are you using TWRP from OP6 so old too? Here for OP6T there is newer https://github.com/engstk/android_device_oneplus_fajita/releases/tag/v9.101
Click to expand...
Click to collapse
I have updated to the latest TWRP as you have mentioned. The issue still persists when Magisk is installed. Once again, Magisk had to be uninstalled before the phone would boot up properly.
Mannan Qamar said:
Could be an issue with the VM. I'd also try to change USB Port or try another Cable.
Click to expand...
Click to collapse
I tried with 2 different USB ports today. Tomorrow i will reboot the VM, remove the driver, let it re-discover and install the driver from MS (i installed a pre-downloaded driver today) and try again. The cable is the original one that came with the phone, and another one will need to be purchased if the efforts fail. Hopefully it is just the VM acting funny.
SkyLukewalker said:
I have updated to the latest TWRP as you have mentioned. The issue still persists when Magisk is installed. Once again, Magisk had to be uninstalled before the phone would boot up properly.
I tried with 2 different USB ports today. Tomorrow i will reboot the VM, remove the driver, let it re-discover and install the driver from MS (i installed a pre-downloaded driver today) and try again. The cable is the original one that came with the phone, and another one will need to be purchased if the efforts fail. Hopefully it is just the VM acting funny.
Click to expand...
Click to collapse
No that won't be necessary. As the drivers can't be downloaded from MS. Is your phone able to reboot to Recovery? i.e. do you have TWRP Installed? If so, then flash Latest OOS ZIP and TWRP Installer, Reboot and repeat the two above steps. After that Format Data and Reboot. This should allow you to boot up. After that, proceed to root as you normally would. Also, I'd look into getting a Windows Laptop if it doesn't work. As MSM is known to have issues with VM.
Mannan Qamar said:
No that won't be necessary. As the drivers can't be downloaded from MS. Is your phone able to reboot to Recovery? i.e. do you have TWRP Installed? If so, then flash Latest OOS ZIP and TWRP Installer, Reboot and repeat the two above steps. After that Format Data and Reboot. This should allow you to boot up. After that, proceed to root as you normally would. Also, I'd look into getting a Windows Laptop if it doesn't work. As MSM is known to have issues with VM.
Click to expand...
Click to collapse
Yes, i have twrp-3.3.1-x_blu_spark_v9.101_op6t currently installed without Magisk. Will do as you have said tomorrow, since i have also downloaded the full 9.0.17 OOS zip file.
Since budget is very tight at the moment, i will look into borrowing a Windows PC/laptop for awhile to use Msm if the other methods don't work.
SkyLukewalker said:
Yes, i have twrp-3.3.1-x_blu_spark_v9.101_op6t currently installed without Magisk. Will do as you have said tomorrow, since i have also downloaded the full 9.0.17 OOS zip file.
Since budget is very tight at the moment, i will look into borrowing a Windows PC/laptop for awhile to use Msm if the other methods don't work.
Click to expand...
Click to collapse
Wait, wouldn't flashing back to 9.0.17 lock your bootloader? Then you can't enable OEM unlocking, which means you can't unlock the bootloader. You would need to flash MSM 9.0.11 to enable OEM unlocking, then unlock the bootloader before proceeding further. I'm no expert, just thought I'd mention it. Best of luck!!
Sent from my ONEPLUS A6013 using Tapatalk
xRogerxC said:
Wait, wouldn't flashing back to 9.0.17 lock your bootloader? Then you can't enable OEM unlocking, which means you can't unlock the bootloader. You would need to flash MSM 9.0.11 to enable OEM unlocking, then unlock the bootloader before proceeding further. I'm no expert, just thought I'd mention it. Best of luck!!
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Didn't seem to be an issue, worked correctly and the bootloader remained unlocked.
Mannan Qamar said:
... Is your phone able to reboot to Recovery? i.e. do you have TWRP Installed? If so, then flash Latest OOS ZIP and TWRP Installer, Reboot and repeat the two above steps. After that Format Data and Reboot. This should allow you to boot up. After that, proceed to root as you normally would. ...
Click to expand...
Click to collapse
This worked, and now the phone is booted up into the system WITH Magisk 19.4 installed. Thank you very much! I didn't have to use Msm.
The steps for anyone else facing the same issue that i did:
Reboot into Recovery. This can be done via long-press power button in System and pressing Recovery if TWRP is already installed, or adb reboot bootloader to reboot into the bootloader, and fastboot boot recoveryImage_Filename.img (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.img)
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip (in my case, it was OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905.zip)
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.zip)
Back -> Back Arrow
Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip
Back -> Back Arrow
Wipe -> Format Data -> type "yes" and click the blue tick "Enter" key on keyboard.
Back Arrow to Main Screen -> Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload MagiskInstaller.zip (in my case, it was Magisk-v19.4.zip)
Back -> Back Arrow
Reboot -> Power Off to completely power down.
Long-press power button to boot the phone. The issue of being stuck at the bootloader unlocked warning screen was gone. The phone booted into System with Magisk Root installed and working.
Later today, I will install LOS16 with Magisk and report back on how that went. Once again, much gratitude and appreciation to Mannan Qamar for the solution!
SkyLukewalker said:
Didn't seem to be an issue, worked correctly and the bootloader remained unlocked.
This worked, and now the phone is booted up into the system WITH Magisk 19.4 installed. Thank you very much! I didn't have to use Msm.
The steps for anyone else facing the same issue that i did:
Reboot into Recovery. This can be done via long-press power button in System and pressing Recovery if TWRP is already installed, or adb reboot bootloader to reboot into the bootloader, and fastboot boot recoveryImage_Filename.img (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.img)
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip (in my case, it was OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905.zip)
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip (in my case, it was twrp-3.3.1-x_blu_spark_v9.101_op6t.zip)
Back -> Back Arrow
Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload OOSimage_Filename.zip
Back
ADB Sideload -> adb sideload TWRPzipFile_Filename.zip
Back -> Back Arrow
Wipe -> Format Data -> type "yes" and click the blue tick "Enter" key on keyboard.
Back Arrow to Main Screen -> Reboot -> Recovery, and wait for phone to reboot into Recovery
Enter password/pattern to unlock
Advanced -> ADB Sideload -> adb sideload MagiskInstaller.zip (in my case, it was Magisk-v19.4.zip)
Back -> Back Arrow
Reboot -> Power Off to completely power down.
Long-press power button to boot the phone. The issue of being stuck at the bootloader unlocked warning screen was gone. The phone booted into System with Magisk Root installed and working.
Later today, I will install LOS16 with Magisk and report back on how that went. Once again, much gratitude and appreciation to Mannan Qamar for the solution!
Click to expand...
Click to collapse
Glad to know it worked. MSM should be a last resort but most people use it as a first option to Nuke their phone. And if you want help on installing ROMs, don't hesitate to ask.
Mannan Qamar said:
Glad to know it worked. MSM should be a last resort but most people use it as a first option to Nuke their phone. And if you want help on installing ROMs, don't hesitate to ask.
Click to expand...
Click to collapse
LOS16 was installed successfully with Magisk and i spent nearly 7 hours setting up the phone since opbackup could not be seen by OnePlus Switch, and i had to do everything manually.
Suddenly the screen started flashing all sorts of colours. I rebooted, and the same problem came back, i.e. stuck at the warning screen.
So, i used the instructions you provided and got OOS 9.0.17 booted back up with Magisk 19.4. However, when i try to connect to the phone via USB, even with debugging enabled, the internal storage cannot be read. Says "enable MTP." This is also happening in TWRP even after disabling and re-enabling MTP.
How do i get the phone to see the internal storage again? Please help.
SkyLukewalker said:
LOS16 was installed successfully with Magisk and i spent nearly 7 hours setting up the phone since opbackup could not be seen by OnePlus Switch, and i had to do everything manually.
Suddenly the screen started flashing all sorts of colours. I rebooted, and the same problem came back, i.e. stuck at the warning screen.
So, i used the instructions you provided and got OOS 9.0.17 booted back up with Magisk 19.4. However, when i try to connect to the phone via USB, even with debugging enabled, the internal storage cannot be read. Says "enable MTP." This is also happening in TWRP even after disabling and re-enabling MTP.
How do i get the phone to see the internal storage again? Please help.
Click to expand...
Click to collapse
Format Data in TWRP. For some weird reason, Internal Storage gets messed up after flashing OOS. And the screen issue might have been a Magisk Module or some other error. Maybe an issue with the ROM. I'd certainly try another ROM
Mannan Qamar said:
Format Data in TWRP. For some weird reason, Internal Storage gets messed up after flashing OOS. And the screen issue might have been a Magisk Module or some other error. Maybe an issue with the ROM. I'd certainly try another ROM
Click to expand...
Click to collapse
I'm going to do the whole process all over again, just to be sure, and try to copy the necessary files over to internal storage before flashing Magisk. Will update once the process gets there. I'm going back to rooted OOS for now because nearly 7 hours of setup is not fun in the least for a daily driver phone.
Mannan Qamar said:
Format Data in TWRP. For some weird reason, Internal Storage gets messed up after flashing OOS. And the screen issue might have been a Magisk Module or some other error. Maybe an issue with the ROM. I'd certainly try another ROM
Click to expand...
Click to collapse
I managed to copy over the files in TWRP, with internal storage showing up as Internal Storage (A6013). However, once booted into system, it now shows up as Internal Shared Storage (A6010) with nothing in it. Using the phone's File Manager, the copied files do not show up either.
But going back to TWRP, Internal Storage shows up correctly with the copied files. Did Format Data in TWRP and rebooted into system. Still the same issue. Please help?
Edit: tried doing the same method all over again. This time, the MTP error shows up in TWRP also. Can't see anything anymore.
SkyLukewalker said:
I managed to copy over the files in TWRP, with internal storage showing up as Internal Storage (A6013). However, once booted into system, it now shows up as Internal Shared Storage (A6010) with nothing in it. Using the phone's File Manager, the copied files do not show up either.
But going back to TWRP, Internal Storage shows up correctly with the copied files. Did Format Data in TWRP and rebooted into system. Still the same issue. Please help?
Edit: tried doing the same method all over again. This time, the MTP error shows up in TWRP also. Can't see anything anymore.
Click to expand...
Click to collapse
Well. In such a case MSM is the way to go. I'd recommend using a Windows Laptop. Although as a last resort if try the Fastboot ROMs before MSM. Search OP6T Fastboot ROMs
Mannan Qamar said:
Well. In such a case MSM is the way to go. I'd recommend using a Windows Laptop. Although as a last resort if try the Fastboot ROMs before MSM. Search OP6T Fastboot ROMs
Click to expand...
Click to collapse
I found this thread and downloaded the appropriate Fastboot ROM (9.0.17). Just a couple of questions:
1. do i need to do the persist partition step?
2. where in TWRP do i have to go to do adb push and adb shell?
SkyLukewalker said:
I found this thread and downloaded the appropriate Fastboot ROM (9.0.17). Just a couple of questions:
1. do i need to do the persist partition step?
2. where in TWRP do i have to go to do adb push and adb shell?
Click to expand...
Click to collapse
Those things are not necessary. Just unzip and use the Flasher in the archive. The default one should be sufficient. The others aren't needed.
Mannan Qamar said:
Those things are not necessary. Just unzip and use the Flasher in the archive. The default one should be sufficient. The others aren't needed.
Click to expand...
Click to collapse
Hopefully it works from the VM. Otherwise i will have to do it manually from Linux terminal. Thank you for the advice. Will report tomorrow when the process is done.

Categories

Resources