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!
Related
================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
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!
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Pretty sure you are using msmdownloadtool wrong. Completely shut down the phone. Make sure to DISCONNECT the phone form pc. Hold vol up and vol down for 5 sec. And it should unbrick hour phone
Hold power and volume up till the phone shuts off...
Now with the device completely powered off hold both volume buttons down at the same time for about five seconds then while continuing to hold both volume buttons plug USB in from pc to your phone the screen will be black and it's normal.... After this it should be showing up in the MSM tool....
It showed up in the MSM tool, but when i click start it goes for 4 seconds and then tells me that it doesnt recognize the image.
dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Yes, i was on the NoLimits rom and wanted to stop using it since i felt it was impacting a few things on my phone that i didnt like, but i really enjoyed Viper4Arise. So i was trying to flash V4A and after i was done flashing it wouldnt load past the unlocked bootloader screen, and i was stupid enough to not create a backup before i started because i didnt think V4A would be that harmful. After trying to wipe my phone and start fresh, i got stuck in the recovery loop.
dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Also, whats a good thread to get the system image?
Bildo41383 said:
Also, whats a good thread to get the system image?
Click to expand...
Click to collapse
If you are booting into recovery, first try formatting your data. In OnePlus's recovery, select English, and somewhere there is an option to "ERASE EVERYTHING." This will format the partition for OOS. On TWRP, go to Wipe--> Format Data. That may fix the bootloop.
If this does not fix it, the MSM download tool is a good option, however, I see it did not work for you. You can download OnePlus's official ROM from here, and for that, you want to flash it in TWRP like any other mod, then reboot. If you are still boot-looping after that, try formatting your data again for good measure.
For the MSM Download tool, you MUST be on Windows, and you must have extracted the archive fully, which can be done by right-clicking on the ZIP and selecting "Extract all." Then, turn the phone completely off, no USB attached. Press and hold Volume Up + Volume Down, and connect the device to the computer. You should then be able to launch the MSM tool, selecting the normal one for the stock variant, and the factory_mcl for the McClaren variant. If your device does not show up, make sure you have installed Qualcomm drivers from here.
Good luck and I hope you get your phone working!
Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
That happened to me as well with the 9.0.1.2 version.
What I did is I used an older version 9.0.1.1 works all the time. No matter what Rom you had previously installed, So try an older version.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
This saved my butt 100 times...whenever I mess with slot A and B and end up booting to recovery mode again n again
After using the Axon 7 G happily with [ROM][AROMA][A2017X][B03 8.0.0][stock] SL!M7 DF!NR (magisk rooted+BL unlocked) for 3 months it shut off without warning after I disconnected an bluetooth audio device from the fon. I remember updating magisk+ bluetooth sbc enhancer a couple days ago.
Now it wont boot into sytem/twrp via start menu nor buttons. it just shows the start menu and the red led is on->flashes->off. I can select everything in the Options/Start menu, but it only works for "fastboot". it wont show up in win in this mode.
I can use EDL tool after using vol up+ vol down + pwr. I am able to make the backups there and i did them all. Besides I have no clue if I can just flash TWRP/ROM/Magisk without deleting all the data.
I need to acces some files on the fon. Is there a way to access the backup via pc? The *.bin data wouldnt mount in win10.
drahtwurst said:
After using the Axon 7 G happily with [ROM][AROMA][A2017X][B03 8.0.0][stock] SL!M7 DF!NR (magisk rooted+BL unlocked) for 3 months it shut off without warning after I disconnected an bluetooth audio device from the fon. I remember updating magisk+ bluetooth sbc enhancer a couple days ago.
Now it wont boot into sytem/twrp via start menu nor buttons. it just shows the start menu and the red led is on->flashes->off. I can select everything in the Options/Start menu, but it only works for "fastboot". it wont show up in win in this mode.
I can use EDL tool after using vol up+ vol down + pwr. I am able to make the backups there and i did them all. Besides I have no clue if I can just flash TWRP/ROM/Magisk without deleting all the data.
I need to acces some files on the fon. Is there a way to access the backup via pc? The *.bin data wouldnt mount in win10.
Click to expand...
Click to collapse
You can flash TWRP from there. Just put the recovery in the folder called recovery abd you can flash one. It'll probably not work though.
i'll help you later
It'll probably not work though. i'll help you later
Click to expand...
Click to collapse
since you are not shure...are you shure flashing twrp will it leave the personal data untouched? i dont know that.
drahtwurst said:
since you are not shure...are you shure flashing twrp will it leave the personal data untouched? i dont know that.
Click to expand...
Click to collapse
Of course it will. The only thing that will "touch your personal data" would be changing ROM (if you were encrypted, i bet you were) or maybe wiping data, which you're clearly not doing.
Whatever you do, don't touch the data partition because you'll lose the encryption key.
In these cases you might need to use fastboot, it might as well work. The command "fastboot boot file.img" (file being the recovery name) will simply try to boot the recovery on the phone without installing it. You should try some recoveries with decryption capability, and if any one of them boots you can get the stuff out via usb.
Another thing you could do from twrp is uninstall Magisk (there is a zip for that, topjohnwu provides it) and see what happens. Also there is a magisk manager zip that lets you disable modules from the recovery. If you think Magisk is the culprit then this might be useful
...Or just follow the guide that that other guy sebt you a couple hours ago. Lol
as you guessed, flashing TWRP_3.2.1-8_axon7-Oreo.img
probably not work though
Click to expand...
Click to collapse
.
Since I dont know how to do it the other way you suggested
use fastboot, it might as well work. The command "fastboot boot file.img" (file being the recovery name) will simply try to boot the recovery on the phone without installing it.
Click to expand...
Click to collapse
I did successfully as jtalamas said.
If you care to explain the fastboot option, it might be helpfull in the future?
Not sure I am posting in the right spot, but pretty sure the people that can answer are in this section.
After putting it off for months, I upgraded my 6T T Mobile converted to international to OOS 10.3.3 with the ElemetalX kernel, and xxxNoLimits 10.2. Did this several days ago, no problems. Great battery, smooth performance. Even getting 2 days with my VPN on and mock location set to "always".
I went into app ops and noticed almost every app now has "access location from media" and started going through and denying that permission for almost, if not all, the apps. I remember a couple of system apps I did that to. Google play framework being one of them, and, I think, google play services. There may have been 1 or 2 more system apps I did this with also.
I do not have a google account on my phone. I don't want to make it any easier for my pocket tracking device to track me than I have to.
I added an open source mock location app a day or so ago, not problems.
About 5 or so minutes after finishing up in app opps, I went to get the kiddo some food and looked down and noticed my phone rebooting. Now, it is in an endless boot loop.
I can hold power + up volume and get it to power down, but can't get back into TWRP recovery. Figured a quick reflash puts me back to zero and I can start over.....more carefully....but the phone is not cooperating.
I should be able to use adb and flash TWRP that way and use adb to reboot to recovery ( going to have to brush up on the how to before I start though.).
Any thoughts as to WHAT I have done and WHY I am now stuck on endless boot( w XXX animation )??
Is there an easy fix I am overlooking?
Thanks in advance,
JC
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool
Can you get into fastboot? Then you might be able to boot TWRP again temporarily?
Thanks, that gets my into TWRP, unfortunately, my dumb ass deleted the last OTA update after I flashed it. Should be able to side load it onto the phone, then flash it via TWRP.
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
PattayaGlock said:
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
Click to expand...
Click to collapse
Flash twrp recovery via adb commands, you'll find tutorials on several XDA forums or YouTube