I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
Flash your stock recovery back! Twrp is not A11 compatible
Shubham1211 said:
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
Click to expand...
Click to collapse
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
Yes and next time you should better read the threads.
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
OMG...how did this slipped through my mind. Damn thank you for this.
Kollachi said:
Yes and next time you should better read the threads.
Click to expand...
Click to collapse
I read many threads dear sir but this point totally slipped my mind about the android. Really appreciate the tip. Thank you.
pyry666 said:
Flash your stock recovery back! Twrp is not A11 compatible
Click to expand...
Click to collapse
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?
Shubham1211 said:
ok but how do I flash my stock recovery back?
since the only thing I can access is fastboot mode, I tried flashing a stock fastboot rom but that clearly states that it cant be used to downgrade and currently there are no android 11 fastboot rom available so now what am I supposed to do wait?
Click to expand...
Click to collapse
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this
pyry666 said:
Dl your current full rom and extract it from it using payload dumper. There are step by step guides how to do this
Click to expand...
Click to collapse
I just did this. So what I did was since there were fastboot stock roms available but not for android 11, I downloaded one...ran it through payload dumper and copied these files to overwrite the one from 10.5.13. But when I did that and everything went 100% as it should. My phone was not turning on now...no response on button presses and no sound when connected to computer...I thought did I really became the first one to hardbrick a oneplus....then I just checked in device manager and it was showing as 9008 at the end..which meant it is EDL mode...that was exactly what I wanted. I immediately started MSM Tool and there it was then I just started and now my phone is back to normal along woth having OOS 10.5.13 exactly what I wanted so thank you for pointing my foolish mistake.
Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.
Danmanlott said:
Just replying here because this was the only google result when searching the error messages. I could only get into fastboot, no edl, and recovery gave the error message about download mode. I noticed when holding both buttons down and plugging in it would come up as the Qualcomm USB thing 9008, but every 10s it would reboot again and if I wasn't holding the keys go into fastboot. The solution was...
Have the MSM tool started and ready
In the 5-10s you have while the device shows as Qualcomm USB (QUSB 9008 something) hit the start button
This kept it in that mode and although the screen never showed anything it went through the 300s restore and I was back to stock.
Click to expand...
Click to collapse
Bare in mind that EDL mode doesn't last very long (least it didn't for me)
So make sure you're ready to press start on MSM, once the process has initialized it'll keep it in that mode.
Found it out by trial and error. I too thought I couldn't get into EDL but it's probably the last thing that would fail on the phone, if fast boot is working then EDL almost certainly is too.
Related
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Americ said:
Alright, yesterday I decided to root my phone and install LineageOS through bkores' Axon 7 toolkit, starting from a A2017U on B19. Unlocked the bootloader, rooted, flashed TWRP with no problems. Then, I was a dumbass, and flashed LineageOS without first installing the Universal Bootloader or appropriate modem, which resulted in only being able to access the Fastboot and Recovery menus. Then, I panicked and decided to be an even bigger dumbass and locked the bootloader, which has lead me to this point.
For now, when I try to start the phone "normally," it just cycles through the screen with the blue ZTE logo a few times.
I can't get into EDL mode no matter what I try- I even hacked together a deep flash cable.
I can get into Fastboot mode if I hold down both volume buttons as soon as the ZTE screen pops up. From there, I can select "Start," which just takes me to the first boot loop, "Restart bootloader," which just takes me back into Fastboot, "Recovery mode," which doesn't take me to recovery mode and only puts me in the first boot loop, and "Power off," which does exactly what it says it does.
Device Manager recognizes it as "Android Sooner Single ADB Interface" when it's plugged in Fastboot mode. When not in Fastboot mode, it's recognized as "Handset Diagnostic Interface(DFU) (COM3)," with a model of "QUSB__BULK". Typing "adb devices" into the command line results in no connection in either mode.
Miflash recognizes it as a device when plugged in Fastboot, but any attempts to flash anything results in an error message saying "can not found file flash_all_except_storage.bat".
I've tried pretty much every method to restore it back to a usable state- Axon7Toolkit, MiFlash, axon7tool, all with no luck. All of the other threads on here with people in similar situations seem to be for those with AU2017G models, which hasn't helped. Is there anything I can do, or is it FUBAR?
Thank you in advance for the help.
Click to expand...
Click to collapse
Ouch, DFU brick. I don't know if you can really do anything from fastboot, maybe unlock the bootloader again? fastboot oem unlock?
I'm wondering how you managed to lock the bootloader without having been warned tgat your phone would become a brick if ANYTHING was out of place (for example a custom recovery, or root) Every guide to relock has a big flashy warning. Did you use the toolkit to relock? If that's the case I'd say @bkores needs to add a warning to the option, maybe something like the "Type yes to continue" kind.
Okay, on to the other stuff. There are two ways to fix a DFU brick: send to ZTE, say it broke itself (Or be honest and pay $80, your choice) or take apart your device (I did this on my A2017G, with a lot of care and patience it works). There might be a solution that uses fastboot, but I'm unsure about flashing a system with fastboot, maybe it is possible though. You want EDL mode to use MiFlash and reinstall a working system on the phone. You are on DFU mode instead of EDL. google "4th category brick repair guide" for the actual guide that you need to use (it's here in XDA but it's faster to find via google). Just a small comment:
To download the stuff easily without having to translate the whole 4PDA page (the guys who made the method are Russians from 4pda), find the "MiFlash and Drivers" link. Open it, you'll find a bunch of spoilers. If you open them all you'll see that the actual files that you need to use have non-cyrillic titles, so download the A2017U_FULL_EDL (like 3 GB), and the MiFlash and drivers. Once you have everything you can simply follow the XDA guide and get it up and running again. Remember to keep the battery plugged to the motherboard though, it won't work otherwise
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.
Hi I bricked my 6T. I tried to flash HavocOS ROM. But it wasn't installed properly where the systemUI wasn't working properly and I should've wiped my phone beforehand. I rebooted back into recovery and the internal storage was corrupted. I wipe data, but that didn't work and I wiped the system to get into a mode where the MSMDownload Tool can access it. But instead I'm stuck in Fastboot mode, but I could boot into TWRP.
But I followed this thread to recover my 6T through Fastboot, most of the commands worked not the system 'fastboot flash system_a system.img' this was the same for '_b' as well. It kept on saying 'error: cannot load 'system.img'' and now I can't boot into TWRP. Every option in fastboot mode just reboots to fastboot. I tried to get my situation across in each thread (Havocos and Fastboot rom thread) But no reply, I am running out of options and losing hope
If fastboot commands work, type in " fastboot reboot EDL "
then run the msm tool
kdog12 said:
If fastboot commands work, type in " fastboot reboot EDL "
then run the msm tool
Click to expand...
Click to collapse
It didn't work
You found the fastboot ROM thread, did you try flashing everything again from fast boot? Don't just flash what you think you need, reflash all of them. I got stuck in this loop recently and after flashing everything my phone booted as normal, and then I just started over, installing TWRP and rooting etc. Reloading AOSP.
Kept me from having to use the MSM Tool.
Extreme_Ninja2099 said:
It didn't work
Click to expand...
Click to collapse
What didn't work. How didn't it work. Didn't go to EDL mode? Or msm tool didn't work
kdog12 said:
What didn't work. How didn't it work. Didn't go to EDL mode? Or msm tool didn't work
Click to expand...
Click to collapse
The command didn't work
Extreme_Ninja2099 said:
The command didn't work
Click to expand...
Click to collapse
Is very simple to fix this....
Unplug... Hold power plus volume up till the device shuts off
Now with the device turned off and unplugged still.....
Hold both volume buttons for about five seconds and while continuing to hold plug in the USB..... Screen will stay black that's normal cause because the device is now in edl and the msmtool should be detecting it.......
Deleted
I was having issues with the android 11 so thought to downgrade. Since the system wouldn't allow me to do it from the local storage, I thought I will just install TWRP and then flash the OS that way but in the process, I don't know what went wrong but fastboot will flash the recovery but when I tried to boot to it with the command it put me to Qualcomm crash dump mode. I downloaded the MSM Tool as I have gone through this process before but for the millionth time, I just can't put my phone to EDL mode. Every time I try with the volume up+volume down, keep pressing it until I plug the cable into it, the phone just goes to fastboot mode.
TL;DR - only have access to fastboot, no recovery, can't even install recovery because of crashdump issue. Phone not entering into EDL mode tried pushing it from fastboot to EDL using commands but doesn't work. Since it is at fastboot every time, device manager sees it as android bootloader platform. Device manager sees it as Qualcomm HS-USB Diagnostics 900E.
I've almost tried everything and I know device manager is supposed to see the device as 9008 for the MSM tool to work but it is NOT GOING INTO EDL MODE!!!!!
*sigh* any help will be really appreciated guys. Thank you.
[Thread Closed] Continue here.
Hi guys,
I am having an issue with my OnePlus 8 Pro and I hope you can help me. I am open to all suggestions.
My phone bricked after trying to flash a custom rom. I have access to fastboot mode and TWRP. I am operating a linux machine and have windows10 running in virtualbox. I don't know if this is the reason but when I am trying to boot in to EDL mode (ony possibility is via TWRP) my device does not pop up in devicemanager. I followed all the steps in the thread about the MSM tool. When I try to get in to EDL mode with the hardware butons and the original cable from OnePlus I can not get in to EDL mode at all. Tried different cables and different USB ports on my computer but with no success. The correct qualcomm drivers are installed in windows so in theory it should work. Because of this I can not use the MSM tool to get my phone up and running. It simply does not pop up as a qualcomm device in devicemanager when I reboot in EDL mode.
I tried to flash the fastbootrom for my oneplus8 pro but after the last command it restarts and gets into stock recovery. In the command window it says 'waiting for any device' and nothing happens (I waited for about 20 minutes). In the post is mentioned: If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end. Because nothing seems to happen I saw further in the post If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.There is no option available to wipe data and cache/ erase everything in the recovery menu. When I choose to reboot to recovery in the recovery menu my phone powers off. The other option is to reboot into fastbootmode. When I do that there is an error in the command window FAILED Flashing is not allowed for Critical Partitions. I don't know how to fix this. I tried both Linux to flash the fastboot rom manually and in windows also and with the flash-all.bat file. Everytime I end up in fastboot mode when I boot up my phone.
Instead of trying to flash the original OS with the fastbootrom I tried to flash different custom ROMS but somehow it will not install any ROM at all...the device reboots everytime to fastboot mode. Last option I tried is a different recovery. I flashed lineage recovery and tried to flash Lineage OS and AICP and this resulted also in only able to boot into fastboot mode.
I spend a lot of time on the web trying to figure out what is wrong and how to fix it but I have not found a solution yet.
Is there a solution available to get my phone up and running?
SakasakaHeyhey said:
Hi guys,
I am having an issue with my OnePlus 8 Pro and I hope you can help me. I am open to all suggestions.
My phone bricked after trying to flash a custom rom. I have access to fastboot mode and TWRP. I am operating a linux machine and have windows10 running in virtualbox. I don't know if this is the reason but when I am trying to boot in to EDL mode (ony possibility is via TWRP) my device does not pop up in devicemanager. I followed all the steps in the thread about the MSM tool. When I try to get in to EDL mode with the hardware butons and the original cable from OnePlus I can not get in to EDL mode at all. Tried different cables and different USB ports on my computer but with no success. The correct qualcomm drivers are installed in windows so in theory it should work. Because of this I can not use the MSM tool to get my phone up and running. It simply does not pop up as a qualcomm device in devicemanager when I reboot in EDL mode.
I tried to flash the fastbootrom for my oneplus8 pro but after the last command it restarts and gets into stock recovery. In the command window it says 'waiting for any device' and nothing happens (I waited for about 20 minutes). In the post is mentioned: If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end. Because nothing seems to happen I saw further in the post If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.There is no option available to wipe data and cache/ erase everything in the recovery menu. When I choose to reboot to recovery in the recovery menu my phone powers off. The other option is to reboot into fastbootmode. When I do that there is an error in the command window FAILED Flashing is not allowed for Critical Partitions. I don't know how to fix this. I tried both Linux to flash the fastboot rom manually and in windows also and with the flash-all.bat file. Everytime I end up in fastboot mode when I boot up my phone.
Instead of trying to flash the original OS with the fastbootrom I tried to flash different custom ROMS but somehow it will not install any ROM at all...the device reboots everytime to fastboot mode. Last option I tried is a different recovery. I flashed lineage recovery and tried to flash Lineage OS and AICP and this resulted also in only able to boot into fastboot mode.
I spend a lot of time on the web trying to figure out what is wrong and how to fix it but I have not found a solution yet.
Is there a solution available to get my phone up and running?
Click to expand...
Click to collapse
Sounds like a Qualcomm driver issue. You need that for msm
jamescable said:
Sounds like a Qualcomm driver issue. You need that for msm
Click to expand...
Click to collapse
I am affraid so jamescable. I was hoping for a fix via fastboot mode...
What is strange is that flashing another recovery via fastboot is no probleem but a Rom is... don't know why my device is doing this.
SakasakaHeyhey said:
I am affraid so jamescable. I was hoping for a fix via fastboot mode...
What is strange is that flashing another recovery via fastboot is no probleem but a Rom is... don't know why my device is doing this.
Click to expand...
Click to collapse
You can only install Qualcomm drivers in windows, not linux
jamescable said:
You can only install Qualcomm drivers in windows, not linux
Click to expand...
Click to collapse
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
Click to expand...
Click to collapse
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Click to expand...
Click to collapse
SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
Click to expand...
Click to collapse
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume up AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Thanx jamescable. I am going to do this as you described later this week and will post an update in this thread.
Have a nice day friend!
jamescable said:
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume up AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Click to expand...
Click to collapse
Hi jamescable,
Just done exactly as above...my devices boots into edl mode, but msm tool does nothing and in devicemanager my device does not pop up either. I do not hear a sound when I plug in the One+ cable...tried different usb ports on the computer also.
Do you have any ideas what I can do more?
SakasakaHeyhey said:
Hi jamescable,
Just done exactly as above...my devices boots into edl mode, but msm tool does nothing and in devicemanager my device does not pop up either. I do not hear a sound when I plug in the One+ cable...tried different usb ports on the computer also.
Do you have any ideas what I can do more?
Click to expand...
Click to collapse
It has to be a driver issue then. Windows in virtual machine obviously won't work for this
jamescable said:
It has to be a driver issue then. Windows in virtual machine obviously won't work for this
Click to expand...
Click to collapse
O no then I really have a problem....I only have linux as an operating system....I thought windows in a virtual machine running does the trick but I guess I am wrong.