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.
Related
Disclaimer: I have done these steps multiple times and haven't come across any issues, but before you continue please read this fully, and follow the steps completely. Any issues or damage to your phone that occurs while doing this I am not responsible.
That being said below will be everything you need to make sure this all goes smoothly:
Windows or Linux Laptop/PC
Atleast 50% battery on OP3T
Usb Cable for OP3T
Internet Access
Patience
Now to Begin the process to return to stock:
Step 1: Go to http://downloads.oneplus.net/devices/oneplus-3t/ , and download the 4.0.2 version. Again these are the steps I do so that I can make sure the process is done correctly and also that I can get rid of the annoying dm-verity warning. Don't worry at the end of this you will have the latest version for you're device.
Step 2: Go to your phone and reboot to twrp, once in twrp go to wipe>Advance Wipe> Tick everything but usb otg (I do this to make sure my phone starts out in a completely clean state>then swipe to wipe. Once it's finished press back twice to get back to the main screen for twrp.
Step 3: Please reboot device back to twrp. (I found the best way to do this without issues is on the main screen for twrp go to reboot>power off>when the unlocked bootloader warning comes on click the volume up button quickly>use the volume down button when another menu comes on and go to recovery. Again I did it this way because the with twrp version 3.0.4-1 gave me issues when trying to reboot twrp within twrp. Also you will get an No OS installed this is normal as you wiped the system completely. Don't worry just reboot back to twrp.)
Step 4: Once back to twrp you will get the screen where is says to allow modification. Please swipe to allow. Next please connect phone to pc/laptop, and transfer the 4.0.2 you downloaded to your phone. One completed go back to phone and click install and click on the file you just transferred and swipe to install. Once completed reboot device. (Warning: at this time you will get the Dm-verity warning, but dont be alarmed we will take care of that in the up-coming steps.
Step 5: Once the phone reboots and comes to the setup screen don't go through and add your accounts because we will be doing another reset. Quickly get to the home screen of your phone and go to settings>about phone>tap build number 7-10 times>back once>developer options>make sure oem unlocking is ticked, advance reboot is ticked, and usb debugging is ticked(If none of them are please tick them). Since your phone is connected to the pc/laptop after you turn on usb debugging a allow authorization box will show on your phone. Please allow that for this to work.
Step 6: Next go to this link: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.0.3/ , and go all the way to the bottom where it says download Oxygen Recovery (optional), and download that file, and place it on desktop.
Step 7: Now this is assuming you have adb/fastboot setup on you're pc/laptop. Please open up a Command prompt window with phone connected and type these commands in:
1) adb devices ( this will show your device ID Number). If it shows it please continue, if not there is an issue with adb/fastboot set up on your computer, or you typed that command in wrong. Once u get the issue resolved try the command again.
2) adb reboot bootloader (this will reboot your device to bootloader mode)
3) fastboot devices ( again this will show your device ID number as from before)
4) fastboot flash recovery [click and drag the recovery file you downloaded from oneplus website and saved to the desktop here, press enter, and once completed go to your phone and use either the volume up or down button till u see the word Start in green and then press the power button. This will reboot your device, and again you will still have the dm-verity warning on. We are almost done.
Step 8: Once your device is rebooted we need to get rid of all traces of twrp so go to your computer>file explorer>this PC tab>your device should be listed there since its still connected to pc> internal storage>locate twrp folder and delete. Now after you are done with this and you want to lock bootloader go to step 9, but if u don't want to relock the bootloader please just factory reset device, setup your device and then go back to oneplus.net and download the 4.03 version and adb sideload it, and dm verity is gone.
Step 9 Relocking bootloader is easy, and will reset your device. While on your phone go to settings>about phone>tap build number 7-10 times>back once>developer options> make sure that OEM unlocking is ticked, advance reboot is ticked, and usb debugging is ticked (again u may get the allow authorization pop up on your phone please allow). Go to command prompt for adb/fastboot and type in these commands:
1) adb devices ( this will show your device ID Number). If it shows it please continue, if not there is an issue with adb/fastboot set up on you're computer, or you typed that command in wrong. Once u get the issue resolved try the command again.
2) adb reboot bootloader (this will reboot your device to bootloader mode)
3) fastboot devices ( again this will show you're device ID number as from before)
4) fastboot oem lock; once you click enter go to your phone, and use your volume up or down buttons to click on lock bootloader. Let finish. This will reset your device again. Once this is all completed and reboot you have gotten rid of all the warning screens, and your device is like it was when you first got it. Set up device with your accounts and you will get a notification of a update. Download and install.
Congrats your phone is back to stock. If anyone has questions please pm me.
Again these steps are longer than what most of you may do. A few others including myself have done this multiple times to confirm. None of us had issues. It works
**Special Thanks**
The guys that tested this with me to confirm my steps are accurate
Google for well google
Oneplus for yet another awesome device and software.
***UPDATE***
Thanks to @ashokmor007 he made the video below on the steps.
https://www.youtube.com/shared?ci=xDFI-287K-Q
If there is anything else that someone may want a guide on how to do and there isn't one currently on xda. let me know and i can get a guide out. We are currently figuring out if this will work on the oneplus 3.
Very helpful tutorial
if anyone here has tried this please comment, and if u need help please pm me.
the_rooter said:
Thanks to @ashokmor007 he made the video below on the steps.
https://www.youtube.com/shared?ci=xDFI-287K-Q
Click to expand...
Click to collapse
If possible add to the main thread
ashokmor007 said:
If possible add to the main thread
Click to expand...
Click to collapse
done and finished thanks again for the video
TWRP - Mount Decrypt Data?
Good afternoon, the_rooter... Thanks for posting this. I'm trying to get back to stock and found this. I'll explain from the beginning...
My 3T will not boot now. Stuck on “Powered by Android” Screen. Here’s the sequence of events that led to this:
1. Flashed TWRP 3.1.0-1
2. Did a backup of phone (Orig OS… Just got phone a few days ago)
2. Flashed Sultan’s ROM
3. Installed Xposed.
At this point… Everything was working just fine… This morning I decided to install the Xprivacy Module and then I rebooted phone. When I did that, the phone just hung at the “blue android” start screen. I then did the following:
1. Held power button until shutdown
1. It took a while, but I was finally able to boot into TWRP.
2. Did a Wipe – The regular one
3. Restored my backup and rebooted. (Would not boot into the OS)
This is where I think I screwed it up even further… … Here’s what I did… I grabbed a shotgun and… LOL… No… but I was thinkin’ it… LOL… I did this:
1. Booted into TWRP
2. Did the Advanced Wipe and just wiped Everything(Internal Storage as well) except USB OTG
Also getting "Mount Decrypt Data" message when I boot to TWRP... Not sure why that's happening...
Now I can’t copy any files to the phone… Tried with Linux(Ubuntu) and a Windows system... Before all of this I could copy to the phone just fine. I tried disabling MTP in TWRP but that didn't work either. So I'm stuck on copying things to the phone at this point...
Can you set me straight?
Edit: Crisis over... Was able to load ADB drivers on a Windows Box and copy ROM back to phone... I'm back and smiling again.
Just use these tutorial for return 100% stock,it worked very good but the last dm verity message only dissappeard for me after step 9 updating to last 7.1.1 using adb sideload.
Thank You very much!!!!!
Is there a reason why you have to swipe to allow modifications? Can't you just keep TWRP read only and then the stock recovery will automatically be flashed so you don't have to do it manually? Also there will be no dm-verity warning.
Thanks for this guide, it worked great.
When you flash the downloaded 4.0.3, the ota of 4.1.0 will fail because somehow a partial ota is for some reason not possible. Anyway this is no problem because the phone will perform an automatic retry and downloads the full ota which worked for me and let the dm-verity warning disappear. I imagine future partial otas will work.
Therefore I think it is important to start with a version that is not the newest version (but e.g. with newest version - 1) or otherwise use some other way to get rid of the dm-verity warning.
Took the 4.0.3 update OTA but other than that followed exactly. Worked beautifully!
I didn't relock bootloader.
I also removed the default encryption.
I've followed all the steps, but dm-verity warning is still showing. I'm still on OOS 4.0.2 though. Someone with simmilar experience? How to get rid of that dm-verity warning?
Edit:
Manually upgraded to OOS 4.0.3 and dm-verity warning gone! Not sure why I was not receiving OTA update though.
What about returning to stock for 4.1.1??
I was coming from the beta channel, and after the initial wipe I was unable to boot into either recovery or the software. I had to reflash TWRP, and then I was able to install 4.02.
After unlocking, I was still getting the dm verity warning. The software attempted an OTA, but it failed. After this it downloaded the complete 4.1.3 via OTA, which worked and got rid of the dm verity warning.
Thanks for the guide!
Followed Tutorial 100% :/, Didn't get any error doing Flashing, Worked perfectly but still the DM-Verity warning.
That official TWRP 3.x is prone to cause dm-verify error and due to that I even has many files in /data lost! Better use TWRP 3.1 bluspark version. Though it's Unofficial its work best.. I also upgraded from 3.0 to 3.1 TWRP without getting the dm-verify error back..
arvindgr said:
That official TWRP 3.x is prone to cause dm-verify error and due to that I even has many files in /data lost! Better use TWRP 3.1 bluspark version. Though it's Unofficial its work best.. I also upgraded from 3.0 to 3.1 TWRP without getting the dm-verify error back..
Click to expand...
Click to collapse
How can I upgrade to the 3.1 version?
To return it to stock I just
1.flash the oneplus's Oxygen Recovery
2. full wipe in Oxygen Recovery
3. ADB sideload 4.0.3
4. lock oem in fastboot
and all the warning would disappear and every return to stock
diego97yey said:
How can I upgrade to the 3.1 version?
Click to expand...
Click to collapse
Just flash latest TWRP from recovery by clicking Install Image file or flash from fastboot...
x10000 said:
To return it to stock I just
1.flash the oneplus's Oxygen Recovery
2. full wipe in Oxygen Recovery
3. ADB sideload 4.0.3
4. lock oem in fastboot
and all the warning would disappear and every return to stock
Click to expand...
Click to collapse
Thanks bro ,, working Fine :good::good:
I *just bought Mi A1, and I want the Night Light feature. And the blue accents (I love it).
I enabled OEM unlocking, enabled USB debugging. adb recognized my phone, and I rebooted it to bootloader (fastboot).
HOWEVER, fastboot devices brought up no devices - the phone is not being recognized.
I used the AIO tool here, and I'm getting the same results. Interestingly, when I reboot to the bootloader, the phone switches off after 30 seconds or so, and instead starts charging (cuz it's connected to my laptop) but it stays in fastboot if I use Vol - and power button.
I could be missing USB drivers, I supposed. I had installed drivers from the AIO tool, am I missing something?
Help appreciated, thanks!
If phone switches off/reboots in fastboot mode, it usually means that drivers are installed incorrectly. Find phone in device manager and install drivers manually from there.
_mysiak_ said:
If phone switches off/reboots in fastboot mode, it usually means that drivers are installed incorrectly. Find phone in device manager and install drivers manually from there.
Click to expand...
Click to collapse
Thanks! Where can I download the drivers? Through Windows update itself or from any other source?
kvn95ss said:
Thanks! Where can I download the drivers? Through Windows update itself or from any other source?
Click to expand...
Click to collapse
For example here and just follow the video guide in the post for both ADB and Fastboot drivers installation.
With your phone in fastboot mode, look in device manager, there is probably a device that does not have drivers. If you have already installed them, you can try having Windows search for them. Then you would validate by doing a fastboot devices command from command prompt.
I have managed to get it working, I've flashed TWRP, however it goes into a bootloop with linux penguin, then a white background with Google colors and an open lock at the bottom, reading "Unlocked".
Strangely, if I flash TWRP with the AIO tool, the phone boots into system rather than loading into TWRP ?
Any reason for the peculiarity!?
Also, I can't reboot the phone.
And for some reason, my phone is encrypted!
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk..
Why do you want to keep phone decrypted? There is zero performance hit with encryption and it's, well, more secure
_mysiak_ said:
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk.
Click to expand...
Click to collapse
Oohh.. okay. Right now I'm downloading the Dec. update. I'll flash that with MiFlash tool (saving the user data) and then install Magisk with TWRP.
Before that, should I try flashing stock recovery?
Why do you want to keep phone decrypted? There is zero performance hit with encryption and it's, well, more secure
Click to expand...
Click to collapse
Well... I thought that the encryption is preventing my phone from booting. Strangely, flashing TWRP 3.2 using the AIO boots my phone to system, so at least I can use my phone.
_mysiak_ said:
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk.
Click to expand...
Click to collapse
ALSO, do I have to install magisk on both the slots?
I suppose that you want to root your system in the easiest possible way, I'd suggest:
1. flash December fastboot ROM (MiFlash or via fastboot directly, keep user data). This will flash full December ROM to BOTH slots and set slot A as active. At this point you have fully stock device.
2. unlock bootloader
3. fastboot into TWRP
4. flash Magisk
That's it. Magisk will be installed only into the active slot A. There is probably no reason to install it also in slot B. If you want to return to stock, it is enough to restore boot.img, either from Magisk app directly, or via fastboot.
_mysiak_ said:
I suppose that you want to root your system in the easiest possible way, I'd suggest:
1. flash December fastboot ROM (MiFlash or via fastboot directly, keep user data). This will flash full December ROM to BOTH slots and set slot A as active. At this point you have fully stock device.
2. unlock bootloader
3. fastboot into TWRP
4. flash Magisk
That's it. Magisk will be installed only into the active slot A. There is probably no reason to install it also in slot B. If you want to return to stock, it is enough to restore boot.img, either from Magisk app directly, or via fastboot.
Click to expand...
Click to collapse
So, I flashed the December fastboot ROM, unlocked my bootloader, booted to TWRP and installed Magisk v14 (latest). It installed without issues, but when I try to boot, it goes into a boot loop.
Also, when I boot using TWRP (no modifications) my hotspot doesn't seem to work, I have to restart my phone to fix it.
Well, I guess I'll try it once more...
Damn, it worked! Magisk installed and phone boots well. The phone gives a warning before booting, that it can't be checked for corruption (probably because of the unlocking I guess).
Now, onto installing the Magisk module which gives me to use GCAM (HAL3) and nightlight.
Just a note, Magisk v14 doesn't work well with dual partitions, this might explain strange behavior. Use official Magisk beta v 14.4 or 14.5.
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.
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.
Help me guys. I deleted my Oneplus 6T SystemUI.apk. Bootloop. Please teach me how to fix it.
Maybe this thread could be useful
https://forum.xda-developers.com/showthread.php?t=1637847
Is your bootloader unlocked? If so, you can just boot TWRP via fastboot (boot the img, not installing the zip) and dirty flash the latest OTA.
If nothing works, boot into EDL mode and use msmdownloadtool as last resort, but you will lose ALL your data in the process. Don't mess with the cable when msmdownloadtool is working or your phone is going to be permanently bricked. You should only use msmdownloadtool if you've tried everything and nothing is working, or you entered Qualcomm crash dump mode and fastboot/recovery isn't working.
I don't understand
komodo_1 said:
Maybe this thread could be useful
https://forum.xda-developers.com/showthread.php?t=1637847
Click to expand...
Click to collapse
I don't understand this
Then
adb shell
su
rm system/app/SystemUI.apk
exit
basedtobeh said:
Is your bootloader unlocked? If so, you can just boot TWRP via fastboot (boot the img, not installing the zip) and dirty flash the latest OTA.
If nothing works, boot into EDL mode and use msmdownloadtool as last resort, but you will lose ALL your data in the process. Don't mess with the cable when msmdownloadtool is working or your phone is going to be permanently bricked. You should only use msmdownloadtool if you've tried everything and nothing is working, or you entered Qualcomm crash dump mode and fastboot/recovery isn't working.
Click to expand...
Click to collapse
My 6t bootloader unlocked and i don't have boot img
undrahbayar said:
My 6t bootloader unlocked and i don't have boot img
Click to expand...
Click to collapse
Since you uninstalled SystemUI.apk, I'm going to assume you have Magisk and adb/fastboot installed on your PC.
Do you have TWRP installed? If so, just boot into it and dirty flash the latest OTA.
If not, download twrp-3.2.3-2-fajita.img here https://dl.twrp.me/fajita/ and boot into it via fastboot.
On your PC, download the latest OxygenOS from OnePlus website. move the .img you downloaded earlier to your fastboot folder, hold Vol Up + Power until you enter fastboot, back to PC - type into the search bar "cmd" then press enter, type fastboot boot "twrp-3.2.3-2-fajita.img" and press enter. Your phone should boot into TWRP, now copy the OTA file into your phone and install it into both slots (just to be sure).
You're going to lose Magisk if you do this, but you can just reinstall it and it's much better than having a $600 paperweight
Remember that you need to have a working adb and fastboot on your PC to do this.
Some tip: You can backup your data while you're in TWRP via USB mass storage, it's a good idea to do it now just in case your phone is bricked even worse than before.
basedtobeh said:
Since you uninstalled SystemUI.apk, I'm going to assume you have Magisk and adb/fastboot installed on your PC.
Do you have TWRP installed? If so, just boot into it and dirty flash the latest OTA.
If not, download twrp-3.2.3-2-fajita.img here https://dl.twrp.me/fajita/ and boot into it via fastboot.
On your PC, download the latest OxygenOS from OnePlus website. move the .img you downloaded earlier to your fastboot folder, hold Vol Up + Power until you enter fastboot, back to PC - type into the search bar "cmd" then press enter, type fastboot boot "twrp-3.2.3-2-fajita.img" and press enter. Your phone should boot into TWRP, now copy the OTA file into your phone and install it into both slots (just to be sure).
You're going to lose Magisk if you do this, but you can just reinstall it and it's much better than having a $600 paperweight
Remember that you need to have a working adb and fastboot on your PC to do this.
Some tip: You can backup your data while you're in TWRP via USB mass storage, it's a good idea to do it now just in case your phone is bricked even worse than before.
Click to expand...
Click to collapse
i don't want lost my data. my phone twrp installed. https://l.facebook.com/l.php?u=http...v2tKWpgjtH1uNa9qGkEpux3yPIjNDUTQIEPCPb_dVJD7U i don't understand it
He had to delete the wrong systemui apk first, with the commands you quoted
then comes those for apk installation
Code:
adb push SystemUI.apk system/app/SystemUI.apk
reboot
i never tried something like that so I dunno if it would work on all devices, or just on rooted or on no one @ all.
undrahbayar said:
I don't understand this
Then
adb shell
su
rm system/app/SystemUI.apk
exit
Click to expand...
Click to collapse
undrahbayar said:
i don't want lost my data. my phone twrp installed. https://l.facebook.com/l.php?u=http...v2tKWpgjtH1uNa9qGkEpux3yPIjNDUTQIEPCPb_dVJD7U i don't understand it
Click to expand...
Click to collapse
Dirty flashing doesn't wipe your data, but you should definitely back up your data in case something goes wrong.
If you have TWRP installed, just do what I typed on my previous reply. To make it clearer:
1. Download the latest OxygenOS for OnePlus 6T here https://www.oneplus.com/support/softwareupgrade/details?code=9
2. Boot into TWRP (Vol Up + power/Vol down + power, I don't remember which one is for recovery). If it asks for password, enter your PIN number
3. USB mass storage should now be available, you can copy/move files from your phone to PC while in this mode. It's a good idea to backup your data now if you haven't.
4. Copy the OTA file you downloaded into your phone
5. Press Install on TWRP, and select the file you downloaded earlier. It's going to take a while, don't panic.
6. When it has finished, DON'T reboot into system. Instead, go back to TWRP.
7. Press Reboot and choose the other slot (opposite of current slot, so if your current slot is B, press A. if it's A, press B)
8. Install the OTA again (This flashes stock OOS into both slot)
9. Again, DON'T reboot into system, go back to TWRP.
10. Press Reboot in TWRP and choose your previous slot.
11. Boot into system
You're not going to lose data if you do this correctly. But, you're going to lose Magisk if you do this (or maybe TWRP too). Just install Magisk again.
Don't permanently install TWRP on OP 6T because it's going to conflict with Magisk. If you need TWRP, just boot into TWRP.img via fastboot instead of permanently installing it.
I don't exactly know how to flash ROMs on A/B partition devices, but this is what I do and it works everytime. Some steps might be unnecessary, though.
basedtobeh said:
Dirty flashing doesn't wipe your data, but you should definitely back up your data in case something goes wrong.
If you have TWRP installed, just do what I typed on my previous reply. To make it clearer:
1. Download the latest OxygenOS for OnePlus 6T here https://www.oneplus.com/support/softwareupgrade/details?code=9
2. Boot into TWRP (Vol Up + power/Vol down + power, I don't remember which one is for recovery). If it asks for password, enter your PIN number
3. USB mass storage should now be available, you can copy/move files from your phone to PC while in this mode. It's a good idea to backup your data now if you haven't.
4. Copy the OTA file you downloaded into your phone
5. Press Install on TWRP, and select the file you downloaded earlier. It's going to take a while, don't panic.
6. When it has finished, DON'T reboot into system. Instead, go back to TWRP.
7. Press Reboot and choose the other slot (opposite of current slot, so if your current slot is B, press A. if it's A, press B)
8. Install the OTA again (This flashes stock OOS into both slot)
9. Again, DON'T reboot into system, go back to TWRP.
10. Press Reboot in TWRP and choose your previous slot.
11. Boot into system
You're not going to lose data if you do this correctly. But, you're going to lose Magisk if you do this (or maybe TWRP too). Just install Magisk again.
Don't permanently install TWRP on OP 6T because it's going to conflict with Magisk. If you need TWRP, just boot into TWRP.img via fastboot instead of permanently installing it.
I don't exactly know how to flash ROMs on A/B partition devices, but this is what I do and it works everytime. Some steps might be unnecessary, though.
Click to expand...
Click to collapse
i don't fix it. don't work it.