Related
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
inwarse said:
I decided to update my old oneplus 2 to lineageos 15.1 with, but when I tried to flash the file with TWRP, it shows an error. Since the TWRP version I was using was old, I decided to update it first. Keep in mind at this point i had completely wiped my device. So, I downloaded the "twrp-3.2.1-0-kenzo.img" file, as per a youtube video where the dude managed to flash the update successfully, and gave it a go. It showed up as successful. Then i shut the whole device off, and tried to boot back in to recovery to flash the ROM again, but the thing won't boot. It's stuck on this boot screen (with the oneplus logo and 'powered by android' at the bottom), and refuses to go further. I'm stuck in a situation with the phone having no OS, no recovery and the thing won't show up when I connect it to the pc either. Well, the pc makes the 'device connected' notification sound when I plug it in, but nothing shows up on the file explorer or the device manager.
That's my dilemma, please i need help!
Thanks in advance.
Click to expand...
Click to collapse
You downloaded the KENZO (this is not oneplus2! ) TWRP and flashed it on another phone (oneplus2), just normal that it doesn't work and your phone is messed up.
If you can enter fastboot (vol up and power button to boot) you can rescue your phone:
-enter fastboot (vol up + power, while phone is completely off, u can also hold it until you can see "fastboot" written on the screen)
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
If something is not clear, use google, because this is most likely basic stuff you have to know when flashing your phone
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
inwarse said:
I can in fact go to fastboot mode by holding the power+volume up keys. When I the phone to my pc it does show a fastboot device (9597b869 fastboot). What do i do from here?
Click to expand...
Click to collapse
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
wertus33333 said:
As I wrote above (it's a step-by-step guide, u only have to READ )
-connect device to a computer with fastboot installed
-type "fastboot oem unlock" into a terminal/cmd window if there is no error, you are good to go, otherwise your bootloader relocked, use this thread to recover
-if your bootloader is still unlocked, download the ONEPLUS2 TWRP IMG, ALWAYS make sure to only flash the roms, kernels, recoveries or zips for YOUR phone otherwise you can really DESTROY your phone!
-now type into terminal/cmd: "fastboot flash recovery *drag the oneplus2 twrp image into terminal/cmd window* and hit enter
-use vol down + power to reboot phone into recovery and wipe all partitions
-Install a ONEPLUS2 ROM of your choice
Click to expand...
Click to collapse
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Oh, the link is dead, sry for that. try this one (GDrive links are up and working).
inwarse said:
i tried to follow the guide. but the bootloader, as per you description is relocked. the download link for the driver you provided shows up as empty/no longer available. that's where i'm getting stuck.
P.S, i can enter fastboot mode on the phone via power+volume up.
thanks for the help so far, i can't seem to find much help other than from you so far
Click to expand...
Click to collapse
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Do you still have TWRP? If yes go to TWRP and shut down the phone there, afterwards you should be able to enter qualcomm mode again.
otherwise you have to try (i think 10s power button will shut the device completely down). You should be able to enter qualcomm mode if the device is fully shut off (your scenario sounds as if the device is not fully shut off when u connect it to the pc).
Just to go sure: You are absolutely sure to have a oneplus2, are you?
inwarse said:
so i managed to get into qualcomm mode, updated the drivers, and ran "MSM8994DownloadTool.exe" in administrator mode. it went as it's outlined in your guide. however, at the end of that process, the phone got stuck in a bootloop (the oneplus logo flashes for a moment and restarts). and can't get into qualcomm mode now, since when i connect the usb to the pc while the phone off, it lights the display (to show that it's charging, i think). any way back from this?
(i can still get into fastboot mode)
Click to expand...
Click to collapse
Could you resolve the issue?
wertus33333 said:
Could you resolve the issue?
Click to expand...
Click to collapse
nope. kept running into issue after issue, so got dejected and gave up.
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.
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also
amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!
I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...
I post this because none of the guides on the internet worked for my phone, and I had to cut my own way through the jungle. Maybe, this helps someone out there. I have found it extremely difficult to flash LineageOS on my LG G5 (H850). It seems that LG changes that device every now and then, and the installation guides on the internet do not fit any more. Flashing Cyanogen on my Samsung S2 was a cakewalk compared to this.
Here is how I - finally - managed to flash LineageOS: I will explain it as a modification to LineageOs.org‘s installation-wiki for the LG-H850 (wiki.lineageos.org/devices/h850/install) and for Linux.
Firstly, I had difficulties with fastboot. It does not work just to download adb and fastboot. You have to properly install them so that you can run them from any directory. Installation guides are all over the net. Fastboot can only be used when you are in the bootloader. That means you have to run „adb reboot bootloader“ first. Other than adb, you have to run fastboot as administrator (i.e. sudo fastboot devices). You will probably forget adding „sudo“ every now and then.
Trying to tackle my fastboot problems I installed the entire Android SDK; I do not know if that is a requirements. People discuss driver problems; fastboot seems to use other drivers than adb. However, from what I can tell the core-issue is to run fastboot as administrator.
Secondly, rebooting into recovery is also extremely tricky. Entering recovery worked for me by pressing volume down + power and releasing only power for a blink of an eye once the LG logo appears. Most instructions tell you that you will enter a fully-fledged recovery menu. My phone presented me a menu which only offered factory data reset. That you have to do although one hesitates to reset the phone.
However, this will only bring you into the TWRP recovery when you earlier have taken the correct exit after flashing TWRP. You should not have left the bootloader by entering „sudo fastboot reboot“, which will simply restart your phone and you have to shut it down again after it has rebooted. If you enter recovery and do the factory data reset then, the phone will not go into TWRP recovery but simply do a factory reset, and you can start from the scratch.
Instead of rebooting, I had to end the bootloader by disconnecting the battery. When I went into recovery by using the above button-combination and did the factory reset, that lead me into the TWRP recovery menu.
Another lesson I have learned is not to use the system update but to run updates manually through TWRP recovery. The system update does not work properly, and the phone will keep booting into recovery. Another flaw well documented all over the net. And don‘t forget that you have to become a developer and to enable debugging again before you can use adb to manually access recovery...
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.