Related
Dear XDA users,
I tried flashing FireFox OS on my N7...without making a back-up. Of-course, it didn't work so I was trying to acces my device on my pc while in CWM. I gave up. Sometime later I decided to try it again... but I just can't get into bootloader mode. When being hooked up to my pc, I hold all the buttons on the N7. Windows gives the device found sound and tells me my N7 is an Qualcomm HS-USB QDLoader 9008 (COM4). The screen on my N7 stays completely black.
I really don't know what to do :crying: I am so scared that I screwed up my N7 and can't use it anymore.
Please XDA, help me!
mcgloud said:
Dear XDA users,
I tried flashing FireFox OS on my N7...without making a back-up. Of-course, it didn't work so I was trying to acces my device on my pc while in CWM. I gave up. Sometime later I decided to try it again... but I just can't get into bootloader mode. When being hooked up to my pc, I hold all the buttons on the N7. Windows gives the device found sound and tells me my N7 is an Qualcomm HS-USB QDLoader 9008 (COM4). The screen on my N7 stays completely black.
I really don't know what to do :crying: I am so scared that I screwed up my N7 and can't use it anymore.
Please XDA, help me!
Click to expand...
Click to collapse
Unplug your N7 from your computer. Hold volume up + power buttons. That'll get you into the bootloader. Then, you can plug the N7 into the computer and should be able to use fastboot.
Sent from my Nexus 5 using xda app-developers app
Volume up and power is recovery mode.
Volume down and power is download mode.
Hi All,
This is my first post here - I hope this is the correct section.
My phone is totally standard and unmodified.
Last week my phone downloaded an OTA update, this installed fine and the phone worked for a few hours after, then whilst typing a SMS the phone seemed to crash and power off. It now doesn't respond to any of the buttons, won't enter recovery mode etc.
Things I've tried:
Battery out for extended time, back in - nothing
Plug into power - nothing
Plug into PC (windows 8.1) with battery in the phone - windows reports device not enabled/possibly malfunctioned.
Power + volume down - nothing
Hold volume while plugging into usb - nothing
Plug into PC without battery - phone appears as "Qualcomm HS-USB QDLoader 9008" in the COM section on device manager.
I've attempted guides on various posts on this forum; when using this post: (http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853) I managed to access the files on the device, but was unable to re-write the stock files. I got an error for phone not in download mode.
I've also tried accessing via adb and fastboot; adb devices does show the device (with battery not in phone) but when i try adb reboot bootloader nothing happens and the phone disapears from adb devices.
Fastboot does not find the phone.
I'm wondering if it could possibly be a battery fault? Would the phone boot up while connected to power but no battery?
Any help very much apreciated!
Phate4tw said:
Hi All,
This is my first post here - I hope this is the correct section.
My phone is totally standard and unmodified.
Last week my phone downloaded an OTA update, this installed fine and the phone worked for a few hours after, then whilst typing a SMS the phone seemed to crash and power off. It now doesn't respond to any of the buttons, won't enter recovery mode etc.
Things I've tried:
Battery out for extended time, back in - nothing
Plug into power - nothing
Plug into PC (windows 8.1) with battery in the phone - windows reports device not enabled/possibly malfunctioned.
Power + volume down - nothing
Hold volume while plugging into usb - nothing
Plug into PC without battery - phone appears as "Qualcomm HS-USB QDLoader 9008" in the COM section on device manager.
I've attempted guides on various posts on this forum; when using this post: (http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853) I managed to access the files on the device, but was unable to re-write the stock files. I got an error for phone not in download mode.
I've also tried accessing via adb and fastboot; adb devices does show the device (with battery not in phone) but when i try adb reboot bootloader nothing happens and the phone disapears from adb devices.
Fastboot does not find the phone.
I'm wondering if it could possibly be a battery fault? Would the phone boot up while connected to power but no battery?
Any help very much apreciated!
Click to expand...
Click to collapse
Can you boot into download mode? Flash KDZ.
Can you do a hard reset? Reset to factory settings.
Do a Google search to find out how to enter download mode or perform a hard reset.
Please report back what happens or what fails.
sprremix said:
Can you boot into download mode? Flash KDZ.
Can you do a hard reset? Reset to factory settings.
Do a Google search to find out how to enter download mode or perform a hard reset.
Please report back what happens or what fails.
Click to expand...
Click to collapse
I can't do a hard reset or enter download mode - the phone does not respond to any of the buttons.
When I try and turn it on I don't get any boot screen, LG logo etc which is common on most threads I've read so far.
Could it possibly be the battery? It seems strange that it connect to the PC without the battery, but not with it in the phone.
Thanks for your help so far.
Would the phone boot without a battery in whilst connected to USB or does it need a battery? I'm not sure if the battery is at fault.
So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!
Same proble with mine but i bricked mines when update to lollipop and never turn on again . still waiting to some one help to revive my LG
If I come across any solution I'll post it here. In the meantime I've tried the following method on a freshly formatted laptop and I still get "Unknown Device" in Device Manager..
http://forum.xda-developers.com/showthread.php?t=2785089
same here
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:
jc.delgado11 said:
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:
Click to expand...
Click to collapse
I tried using a boot usb drive to see if ubuntu saw the device but it didn't. Maybe there's some things needed that I didn't do. The thing I don't understand the most is why do windows see it as an unknown device only with the battery out while if I connect the G3 with the battery on, it doesn't show anything on device manager..
Nubrig said:
So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!
Click to expand...
Click to collapse
Hi there.
Please check these 2 threads out and see if any of it will help you. The one for the G2 can also be used for G3.
Here are the links:
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091 With this technique you would have to find the software online somewhere but this method does revive dead G3 with these symptoms.
http://forum.xda-developers.com/showthread.php?t=2475045
If I helped somehow, hit the THANKS button.
Good luck!
The thing is I can only get the device to be recognized as an Unknown Device in Device Manager and only with its battery out. If I keep 'volume up' pressed nothing happens, it's only shown after I simply connect the USB cable and it pops up after 10 seconds or so. It's very consistent in the way it behaves..
A small update, sometimes when I pull and put the battery again, I connect the phone to a pc while holding down vol- and the pc makes the connected usb sound while the phone led is blinking red for a couple of minutes, then it stops. That's about all there is concerning the phone giving signs of life..
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
1a)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
1b)goto Google and search for Qualcomm qd loader.download,install and restart your pc.
2)After restarting,Extract the file from OPPO UNBRICK TOOL and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry it isn't corrupted,just follow through↓
4)disconnect your device battery,then open the software and press start,after that connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button
5)please wait patiently as it is reflashing stock rom to your device.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
P/S:if your device is softbricked,you just should disconnect your battery,and then open the software and press start,then connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button.
If your device is hard bricked(like mine)only holding the power button could work as well
*UPDATE* 24/2/2019
-If you guys still have any concerns kindly contact me through twitter (0728mal)
*UPDATE* 4/7/2020
-yes it is still working guys,no worries kayy
-no you don't need internet for it to work,the software already has all the files needed to flash the device,which is why the file is pretty big.
best regards,
Akmal
Link updated :good:
akmlfhm said:
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution which make my phone came to life again-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
-make sure to charge the phone first even if you do not know if it charging or not
1)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
2)Extract the file and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry its not corrupted,just follow through
4)Connect your phone to PC and press the power button until you heard some like mounted usb alert on windows.(its ok aslong windows does not detect it on device manager but its ok if you can hear the alert sound.
5)back to the software,no need to mess around with it.Click on start until its downloading a "new life" to your phone.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try to turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
best regards,
Akmal
Click to expand...
Click to collapse
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
On Mac's OS, you can always install Windows on its proprietary virtual machine and get the process going that way.
babyenchantress said:
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Click to expand...
Click to collapse
hello there!I'm really sorry for not checking this that often and really sorry if i let you down because im too busy with my schools work
btw before my computer can detect my phone i have to download a driver which detect qualcomm processor for my oppo then it can be detected by my pc therefore i can do the unbrick process:good:
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
yeah you can try WINE also but i never have any experience with mac os before so i cant guarantee that it will work considering that you're configuring your drivers,which can go wrong if not done correctly
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
true_friend2004 said:
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
Click to expand...
Click to collapse
Hello there.have you tried downloading the "Qualcomm"
Driver software on your PC?
is it necessary to remove the battery? I don't have tools for opening my phone and it's battery is non-removable
Perhaps an important step is missing. The Qualcomm qd loader driver is may not signed. I had to boot into the extended start menu on Windows 10 and disable the driver signature check - point 7 - and could now successfully debrick my find7.
Hey all,
So i've unlocked by bootloader, flashed a custom recovery to then proceed with LineageOS flashing. However it went completely wrong as on reboot i'm stuck with the bootloader unlocked warning and then a blackscreen.
I still have access to fastboot mode however it's impossible to flash a customer recovery ("No Such Partition") and also impossible to directly "fastboot boot recovery.img" as the phone simply reboots on the warning and then blackscreen.
The only solution seems to get the device to qualcomm EDL mode and reflash all with the MSM tool (which I have as well as all the drivers) however I cannot get my Oneplus 9 pro to EDL mode...
I've tried all the fastboot commands (fastboot oem EDL, fastboot reboot EDL, none of them work) as well as the combination volume UP + volume DOWN + plugging the cable (it just boots the fastboot mode.
Honestly would greatly appreciate any help as it is the first time in a decade I hard bricked a phone like this as it seems all the partitions are broken.
Make sure you have it unplugged when you do the button combos, as it will just start to boot while it's plugged in. Also, if you can reach fastboot, you can almost definitely reach EDL. Try unplugging and holding power+vol up for a bit which forces it to completely power off. Then try getting into EDL through the normal button combo/plugging. This is what I had to do since once it got into the booting/no-booting cycle I couldn't get to EDL.
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Good advice above.
Last time I couldn't reach EDL with my previous phone, it turned out to be an issue with the drivers I had installed. I uninstalled all Android-related drivers including some generic thing that showed up in device manager when plugging in the phone, then reinstalled the latest Qualcomm drivers.
Also possibly try a different USB cable if you have one. My OP9P didn't show up when the cable it came with was plugged into my USB-C port for some reason, but it worked fine with a generic Type-A to C cable I had sitting around.
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Tornadeur said:
Thanks a lot for the different guidelines !
i'm 100% sure the drivers are working. I have another oneplus 9 pro that is detected when booted on EDL mode on the PC. The faulty one however cannot reach it. Also it cannot get any charge as whenever I plug it on it just goes on a boot loop. Tried to leave it to charge for a full night but still shows the "out of battery logo" with the red cable.
When plugged to the PC while pressing VOLUME UP + VOLUME DOWN I keep getting the windows sound of device plugged/unpluged, etc etc...
To be honest I think the flashing messed up the partitions as it is now hard to do anything with this device...
Click to expand...
Click to collapse
I can fix it bro pm me telegram .. @Hunar71
Hunar999 said:
I can fix it bro pm me telegram .. @Hunar71
Click to expand...
Click to collapse
Can you help me too, I have exactly the same problem…
If you use Windows, you need to see "QDLOADER 9008" in Device Manager > Portable Devices.
When you got this it will work, 100% .
It worked for me a few days ago. My laptop runs on Windows 11 x64. And only have usb 3.0. NO usb 2.0.
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Alberhasky said:
was having the hardest time as well, it's not that the device wasn't going to EDL mode, it was but it had the wrong driver installed, thus making MSM tool not detect it in time, it is a very small window that you have where the device goes into EDL mode and the MSM tool detects it, makes a handshake with it and starts the process, but if you have the wrong driver, MSM tool will not detect the device and the device will just turn back into fastboot mode, I'm attaching a picture of the device manager where the said driver is under "Ports" ( COM & LTP ) make sure you download the above mentioned drivers, if there is any other driver under Ports, uninstall it and whenever you plug in your phone with the VOL + VOL - combo, you will see the device appear under PORTS, upgrade the currently installed driver for the one called qcmdm.inf which you'll find after you extract the .cab file that you downloaded previously, after that open MSM Tool and hit start, the port number should match the one on the device manager, now unplug the cable from your phone, power it off and do the button combination and then plug in the cable, MSM should instantly recognize the device and start the restoration.
Click to expand...
Click to collapse
Yeah make sure it's exactly the same name of that driver - worked for me on oneplus 9
If you have access to fastboot still. Try switching slots. Then going into EDL
For anyone looking for help, please DM me.
djsubterrain said:
1] Make sure you have it connected directly to your computer via USB port rather than via a USB Hub, I've seen that cause the device not to show up in the device manager.
2] You might have to restart your computer with driver signing disabled, check here for instructions for that
3] I've uploaded the Qualcomm drivers here
4] Make sure you use POWER + VOL DOWN + VOL UP and watch your device manager to see if the device is there
5] Make sure you choose the correct MSM tool from here for your region/provider
6] Remember to use MsmDownloadTool V4.0.exe, choose "User type : Others" and choose the correct device/region under the top "Target" dropdown.
7] If you don't see any COM device showing connected then try changing USB port or rebooting the device back into EDL mode.
Click to expand...
Click to collapse
Thanks a lot man. Saved my Day. First 9Pro successfully restored ;-) Thank you and merry Christmas to all.
Guys I do not need to use the MSM Tool Anywhere until I reach the step where my device is being successfully detected as "QDLOADER 9008" in my windows device manager correct?
Or does the MSM Application need to be running when I reboot to EDL mode?
I am following this guide.
Please help
I always have phone powered off, and while holding both volume keys I plug it into USB cord(that is already plugged to pc) and then click on enum(button in msm screen) until it says connected then hurry and click start. Once it starts I can let go of volume keys.. Also more than likely u will need to click the box to "use lite firehose" or "Sahara communicaion" will keep failing.
make sure you have oneplus 9 pro drivers and " qaulcomm incorporated - Ports" Driver) and ("qaulcomm communications inc-Net" Driver) so your phone in edl which will be already most likely be running before you plug it in. just hold down both volume buttons and plug in to the usb port to your pc and release once plugged in and start the msm tool and hit enum it should say connect provided that you have all the necessary drivers above so the pc usb port will be able to communicate/recognize you device. its never usually A 1 and done type of thing. everytime i brick my phone its always the 100th try before i get a com port connected and the software communicating successfully, so just be patient and take your time. you will get it back up and running,
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
can't get into edl mode
how can I get oneplus 9 pro into edl mode while it's refusing to turn off? keep in mind that I can't use adb. but was able get fastboot devices command to work and I did not use any third party roms, didn't unlock the bootloader, and do not have...
forum.xda-developers.com
awsan said:
Hey, I wanted to ask in here instead of starting a new thread.
Right now I have an OP9p that wont boot to EDL (Only fastboot or Corrupt page)
I tried the fastboot commands but it won't work and it won't shut down, I have fixed multiple phones using MSM and know all the small issues and how to get around them but it's the first time finding a device that won't shut down and will keep rebooting tried volume up + Power for several seconds tried holding only power or the three.
Nothing it keeps rebooting and won't shut down for me to get into EDL.
Any ideas?
Thanks
Click to expand...
Click to collapse
Well you have a corrupted boot.img or you would not be trying to edl. Also you probably are holding down multiple buttons to power off to your phone and your either not remembering or forgot that these combination of buttons are booting you into other modes fastboot, recovery or system.