Database Users

New/Stock Oneplus Two, unable to boot into recovery

Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!

redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?

Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!

You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!

Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue

Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.

Bricked Recovery

I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).

Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Your recovery is not corrupt. That is the stock recovery boot that you are seeing.
Anyways, how come you can't access ADB or fastboot? Because right now, that would be the easiest and fastest way to install TWRP back.

Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck

dadvs1 said:
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck
Click to expand...
Click to collapse
When you get that Android lying down, press the Power Button followed by Volume Up. That will put you into recovery.

Could you not live boot the recovery? fastboot boot twrp.img.

Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch

tonystarks260 said:
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch
Click to expand...
Click to collapse
Hello, we appreciate your help
But from what I read and understand, the user, Nexicovx thinks that the Android bot with the exclamation mark, is a sign of corrupt recovery. While it is only the regular behaviour of the stock recovery.
When you boot into stock recovery, he would not be taken to it straight away. It will first show the screen, where the Android bot with some sort of warning sign appears. At that point, he would just have to press the Volume up key, and tap the power button once. This will trigger the stock recovery.
Now, to what you can do @Nexicovx. You need to access a PC and the USB cable. Boot your 6P into bootloader mode by powering it off first, and then press and hold the Volume Down and Power keys altogether until you see the bootloader mode. From there, you can flash the TWRP recovery. Download the latest image from here: https://dl.twrp.me/angler/
And now use the following command to flash it:
Code:
fastboot flash recovery twrp-3.0.2-0-angler.img
Once that is done, you can reboot into TWRP and flash your desired ROM.

Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.

Nexicovx said:
Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.
Click to expand...
Click to collapse
Good to know that. :highfive:

I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.

Nexicovx said:
I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.
Click to expand...
Click to collapse
It could be a vendor issue.

Good to know!

Can't get past TWRP

Phone was working fine yesterday. Went to sleep and woke up to the phone booted into recovery. Now I can't get it to reboot past recovery. Anyone know why this happened or how to fix it?
Thanks in advance.

Check and see if system is mounted. Also are you sure that it didn't attempt an update last night?

The EXACT same thing happened to me this morning! Unfortunately I had to get to class before I could figure out how to fix it. When I get back home tonight I will try to get my phone to boot like normal and will tell you how I did it.

my_handle said:
Check and see if system is mounted. Also are you sure that it didn't attempt an update last night?
Click to expand...
Click to collapse
I have no way of knowing if it attempted an update last night. I was asleep. I tried restoring a nandroid backup from 8 days ago and it still won't boot past TWRP.
Help please! I'm at the Cleveland Clinic with my wife and just found out that my grandmother died today and have to drive back to Michigan tonight. I need a phone and Waze!

animator776 said:
The EXACT same thing happened to me this morning! Unfortunately I had to get to class before I could figure out how to fix it. When I get back home tonight I will try to get my phone to boot like normal and will tell you how I did it.
Click to expand...
Click to collapse
I'm sorry to hear, but glad I'm not alone in this. Hopefully we can figure something out.

Sorry about your lose. But click mount and see if system is checked. That's what happened to me before. Making sure system was checked let me boot back up.
If that doesn't work plug your phone into your comp if possible and check to make sure you still have everything on your phone. Another time I had accidently wiped everything and only way to get back up was using the kdz
pieces of cake said:
I have no way of knowing if it attempted an update last night. I was asleep. I tried restoring a nandroid backup from 8 days ago and it still won't boot past TWRP.
Help please! I'm at the Cleveland Clinic with my wife and just found out that my grandmother died today and have to drive back to Michigan tonight. I need a phone and Waze!
Click to expand...
Click to collapse

my_handle said:
Sorry about your lose. But click mount and see if system is checked. That's what happened to me before. Making sure system was checked let me boot back up.
If that doesn't work plug your phone into your comp if possible and check to make sure you still have everything on your phone. Another time I had accidently wiped everything and only way to get back up was using the kdz
Click to expand...
Click to collapse
I checked system under mount, rebooted and still won't go past TWRP.

Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.

midmadn said:
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.
Click to expand...
Click to collapse
Dude, I love you. I'm back! Just in time for my 3 hour drive home!

if this dosnt work
use twrp file manager to go find the fota and mis folders,
or boot into fastboot and send these comands
fastboot erase misc
fastboot erase fota
data/mis
data/fota
something like this is its path.
data/etc/misc
data/etc/fota
this 2 spots have the update commands that cause twrp loop.
i have a help post in my rom with full walkthrough.

Bootloop into TWRP recovery
Thank you so much, I too was having a panic attack after I flashed a custom rom and it some how altered this and put me in a boot loop into TWRP. I had a couple of questions in regards to ROMS that have native tethering enabled. 1. Is there one that allows Native tethering enabled for sprint? and 2. Is there one that you can update the PRL and profile settings and also one that does use an APN that has DNS issues and a proxy that blocks certain sites? currently I downloaded the ROM that is on the Dirty Santa site its called LS997-deODEXd-signed and it has a hidden proxy that blocks DNS from certain sites also you cannot update.

pwoolston2 said:
Thank you so much, I too was having a panic attack after I flashed a custom rom and it some how altered this and put me in a boot loop into TWRP. I had a couple of questions in regards to ROMS that have native tethering enabled. 1. Is there one that allows Native tethering enabled for sprint? and 2. Is there one that you can update the PRL and profile settings and also one that does use an APN that has DNS issues and a proxy that blocks certain sites? currently I downloaded the ROM that is on the Dirty Santa site its called LS997-deODEXd-signed and it has a hidden proxy that blocks DNS from certain sites also you cannot update.
Click to expand...
Click to collapse
Download one of my 11 roms ive currently put out.
they all work 100% as far as dns stuff
for tether you need to add the "dun" to your apns. There isnt currently a built in mod.
as well as using shortcut master to add the "dun" to your apns also gets you to where you can change them
prl and profile updates work also as well as fm radio, wifi calling, fingerprint, comfort view etc.

midmadn said:
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.
Click to expand...
Click to collapse
I had to do this again today. This is not good. How can we stop this? I rely on my phone as an alarm clock and this could really screw me if it happens again at night.

Have you frozen or disabled the apps that look for updates?
Supposedly this is what causes it. The bootloader looks for update files in the folders where updates are downloaded and if it finds a file there it reboots recovery.
You have to remove those files, ( I think it automatically deletes them if you go through the factory reset process with the volume down, power button sequence).
And you have to freeze or disable the update apps.

These are the apps I froze. The 3 near the bottom that are blue.

i did this https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328

Most bootloops are caused by an update file residing on the internal memory. It is not necessary to do all of the stuff in that post. You just need to do the volume down / power button trick to go through the 2 factory reset screens.
---------- Post added at 12:40 AM ---------- Previous post was at 12:39 AM ----------
Have you tried power on and volume down to go through the factory reset screens.
A bunch of us had this problem and it was because an update downloaded on it's own and the bootloader snoops it out and forces recovery to boot.
Just do the volume down + power button - as soon as you see the lg logo release power only then immediately re-press power and continue holding power and volume down until the factory reset screen pops up. Select yes and yes, (don't worry - if you have twrp recovery it can't reset). It will boot you into TWRP and I'm pretty sure it will delete the update files in fota folder.
In TWRP select reboot - system and it should boot normally like nothing happened.

Stuck on wallpaper after Android 10 update but system won't start

So I updated my rooted 6t to Android 10 using Magisk, and everything went as expected prior to rebooting. I hit uninstall and restored images via Magisk, downloaded and installed the Android 10 update package to the inactive slot, downloaded the TWRP A/B partition module then finally installed Magisk to the inactive slot as well. Finally, from there I rebooted and it seemed to boot normally, hung a bit longer on the animation than normal but no more than 30 second or so.. it then skipped the lock screen and went straight to my wallpaper (the same one i has set, not default) BUT the system doesn't start. No icons. Can't pull up the app drawer, can't pull down the notification menu. No notification bar... Nothing.
The only thing I can do is restart the phone by holding PWR button but that just brings me right back to the same deal. I tried fastboot>TWRP recovery and was able to determine that all the system data is in fact present anyway but rebooting from TWRP also lead to the same situation.
I'm asking for advice BC the last time I messed around without knowing fully what I was doing, I hard bricked it. I'm using Blu_Spark TWRP if that makes any difference at all...
It's possible that I just need to wait longer, I read a number of reports of pixel users needing to wait hours after OTA updates but they were stock on the boot logo/animation. I'm beyond that point, only it skips the lock screen, goes straight to my wallpaper and that's it. I can't do anything at all from there.
PLEASE HELP?
Thanks!
QNE

Use MSM tool.
Download MSM tool. Unzip it on PC desktop. ConnectUSB typC cable to PC. Shutdown your OnePlus 6. Open msm download too. Click start. Press volume up and dn key simultaneously(don't touch power button). Now connect cable to phone. Progress bar of MSM download too will be active. Let it completed. Phone will boot to os. Now upgrade to Android 10. That's it.

I ended up factory resetting prior to your response, but thanks just the same. Fortunately, I didn't lose root which was my main concern anyway so no harm done. Thanks again!

HELP! I'm stuck on bootloader unlocked warning screen.

Hello, any help would be appreciated as I have seemed to have gotten Myself stuck on the screen that warns Me about the bootloader being unlocked. I hope this is in the right section of the forum.
So I have enabled at least 10 Magisk Modules at the same time, carefully read the files attached to them within the app, tried to make sure they didn't do too much to the system where I'd have to worry about this sort of thing happening but of course, with My luck, it did anyway. I plugged My device into My laptop to try to just flash the magisk_patched.img and it just brought Me back to the same screen, sometimes it would reboot itself several times before stopping when plugged in to My laptop. I've read somewhere that the Miracast module might be the culprit so I sought to enter TWRP through fastboot and delete the module BUT IT'S NOWHERE TO BE FOUND. I have also tried all these button combinations I kept seeing people talk about on various forums, like pressing all 3, Power+Volume Up, etc and holding them for various amounts of time and none of this has gotten Me past the warning screen. I seen something about uninmod but I've heard that this doesn't work on v.19+ and I can't seem to even find the magisk folder anywhere at all to begin with. I couldn't backup My phone because Google kept saying "waiting to backup" so I'm screwed if I have to just restart and hope it doesn't have to come to that.
My questions are:
Is there any folders I may be missing?
Is there any way to backup My device through TWRP or fastboot now even though TWRP won't mount and I can't boot into the OS?
Is there a way to delete Magisk or the modules that I can try, that I haven't mentioned/don't know about?
Thanks in advance!

Sorry didn't see this until today. Did you end up giving up and starting over with a clean flash or still having issues?

Hw4ng3r said:
Sorry didn't see this until today. Did you end up giving up and starting over with a clean flash or still having issues?
Click to expand...
Click to collapse
It's all good. No I wasn't going to mess with it until I done enough research or someone had replied and I had the time. I was thinking about doing something today or this weekend. I read some things online that I bookmarked about using the "pull" command on ADB, being able to save the image from TWRP after using the fastboot command to boot into TWRP, and I seen some other post on XDA about a certain method they used to stop bootloops. Even though I don't have bootloops, I'm just stuck, maybe it'll be helpful information. At this point though I'm wondering if I even want to save anything, like will restoring it have Me stuck right back on the same screen? I'm sure I did something wrong because I have none of My old phones app DATA, and I think I thought the Google Backup or OnePlus Switch App was going to put the whole APK on My phone (which I don't want) or the data only, which is what I want. Any help would be appreciated because someone is trying to buy this S10+ but I'm still using it.

First questions: what phone are you trying to fix, s10+ or 7T Pro McLaren?
Second: If you answered 7T Pro McLaren, what mode (recovery, fastboot, etc) can you get into?

I'm trying to get off the Root Warning Screen for the 7T Pro McLaren. I can get into fastboot, recovery mode, and TWRP via fastboot command.

iAMe100XP said:
I'm trying to get off the Root Warning Screen for the 7T Pro McLaren. I can get into fastboot, recovery mode, and TWRP via fastboot command.
Click to expand...
Click to collapse
Are you referring to the bootloader unlocked warning? The only way to get that off is to relock the bootloader (will lose personal data when you do this).

Hw4ng3r said:
Are you referring to the bootloader unlocked warning? The only way to get that off is to relock the bootloader (will lose personal data when you do this).
Click to expand...
Click to collapse
I don't want to lock the bootloader or care to get rid of the warning atm. I just can't get past the screen and into the OS. There is possibly a Magisk module I flashed but I can't find the Magisk folder or the modules in TWRP via Fastboot.

iAMe100XP said:
I don't want to lock the bootloader or care to get rid of the warning atm. I just can't get past the screen and into the OS. There is possibly a Magisk module I flashed but I can't find the Magisk folder or the modules in TWRP via Fastboot.
Click to expand...
Click to collapse
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.

Hw4ng3r said:
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Click to expand...
Click to collapse
OK, I will check these things out and report back. I believe I flashed TWRP and the patched Magisk image but maybe I didn't do the original boot image. The problem with the one suggestion is I don't see a 1+ image at all, it just stays on the warning screen forever. I do have advanced boot or whatever turned on I believe where it gives Me more options when holding the power button, provided I can get into the OS but that's not the case. I will try to just hold the volume down when I see the warning screen.

Correction: I see a 1+ logo but no matter what I did, any button combination or booting in with the power button after getting into Safe mode, none of these things did anything but bring Me to the same screen...

Hw4ng3r said:
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Click to expand...
Click to collapse
Jesus Christ! All I had to do was use the original boot image and push it using fastboot? Omg. I'm in My phone now lol. I can't believe it was that simple. I'm sure I original I didn't do this because I thought that it would erase everything or do something dire but apparently everything is still here... wow. Thanks man, I really appreciate it! Now do I re-boot the Magisk patched image through fastboot or do I uninstall modules first or what?

iAMe100XP said:
Jesus Christ! All I had to do was use the original boot image and push it using fastboot? Omg. I'm in My phone now lol. I can't believe it was that simple. I'm sure I original I didn't do this because I thought that it would erase everything or do something dire but apparently everything is still here... wow. Thanks man, I really appreciate it! Now do I re-boot the Magisk patched image through fastboot or do I uninstall modules first or what?
Click to expand...
Click to collapse
I've never ran into any Magisk issues before so I don't know what to tell you from this point on. I'd like to say that you can probably go into Magisk manager and disable/delete your modules, but I don't know enough about the inner workings of Magisk.
You should probably back up all your data at this stage before you do anything further lol

Hw4ng3r said:
I've never ran into any Magisk issues before so I don't know what to tell you from this point on. I'd like to say that you can probably go into Magisk manager and disable/delete your modules, but I don't know enough about the inner workings of Magisk.
You should probably back up all your data at this stage before you do anything further lol
Click to expand...
Click to collapse
Will do, thanks. Do you know if OnePlus Switch transfers APKs or Data? I just want the data and I already used it from My S10+ and wonder if it will be confused by files that already exist or create duplicates. What's the best way to back up if Google keeps saying it's waiting to backup.

iAMe100XP said:
Will do, thanks. Do you know if OnePlus Switch transfers APKs or Data? I just want the data and I already used it from My S10+ and wonder if it will be confused by files that already exist or create duplicates. What's the best way to back up if Google keeps saying it's waiting to backup.
Click to expand...
Click to collapse
I'm not sure about 1+ Switch since I've never used it before.
Check this post for an app others have used.

Hw4ng3r said:
I'm not sure about 1+ Switch since I've never used it before.
Check this post for an app others have used.
Click to expand...
Click to collapse
Don't mean to revive this post at random but I've been really busy lately. I just wanted to update:
I could only turn the phone on by Fastboot and I didn't have much on the phone so I just wiped the device but your help definitely let Me get into the OS and back/upload/see if there was anything I wanted or needed so I really appreciate it. I'll definitely donate when I can, I'm grateful for your help!

iAMe100XP said:
Don't mean to revive this post at random but I've been really busy lately. I just wanted to update:
I could only turn the phone on by Fastboot and I didn't have much on the phone so I just wiped the device but your help definitely let Me get into the OS and back/upload/see if there was anything I wanted or needed so I really appreciate it. I'll definitely donate when I can, I'm grateful for your help!
Click to expand...
Click to collapse
It's great that you posted the final result. Not enough people do this IMO.
Sorry some of the suggestions didn't really work out, but at least you could get back into the phone without complete loss of data.
No need for donations; I'm just an enthusiast/ordinary user wanting to help!