Related
I tried to downgrade from 3.2 with that tool and every time it shows me that the operation had failed
Now i am stuck in APX mode help
please anyone????
jimmis1996 said:
please anyone????
Click to expand...
Click to collapse
Reinstall your USB drivers and try again.
And make sure your tablet is in apx mode.
How :
Connect tablet with USB cable when it is off.
Now with paperclip press the reset button and power button together for 3 seconds, then release power button and one second later you release the reset button ( screen of tablet stays black but you will see that in device manager on your pc under USB devices you should see Acer Picasso recovery driver listed , then you know your tablet is in apx mode and connected.)
Now you can Start.
civato said:
Reinstall your USB drivers and try again.
And make sure your tablet is in apx mode.
How :
Connect tablet with USB cable when it is off.
Now with paperclip press the reset button and power button together for 3 seconds, then release power button and one second later you release the reset button ( screen of tablet stays black but you will see that in device manager on your pc under USB devices you should see Acer Picasso recovery driver listed , then you know your tablet is in apx mode and connected.)
Now you can Start.
Click to expand...
Click to collapse
i done it a lot of times but i still says tha the operation cannot be completed.
Could i leave APX mode and boot normally?
HELP PLEASE
OOF!!!!
Well i managed to boot again by using an other pc
Thanks for your help
Hello, I have a problem with my storm. Two days ago I received it and flashed the then latest cm13 and its corresponding recovery. Everything seemed to work just fine until yesterday when there appeared to be an ota update. After the download finished, the phone rebooted itself and is since then stuck with a black flickering screen. Every attempt to start the phone using recovery or bootloader seems to fail, as the phone keeps showing me the black flickering screen, no matter the combination of keys (vol+/vol-) I use to turn it on. If during the black screen I plug the phone to the computer adb can actually see the phone but says it's not authorized to perform any command. On the other hand fastboot won't even see the device.
Is there anything else I can try before sending it back to wileyfox?
Thank you in advance
I've made some progress, I found out that the device can be forced to Qualcomm HS-USB QDLoader 9008 mode by turning it off and then connecting it to usb while holding vol+ and vol-.
I've also found the stock firmware at https://cyngn.com/support.
Now it would be great if somebody could help me, and the others in my situation, to figure the wole QFIL unbricking out, because I'm overwhelmed, and can't seem to find the right info on google.
Thanks to anyone who'll care to help, or share some info
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
miSAKe said:
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
Click to expand...
Click to collapse
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
maxxie00 said:
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
Click to expand...
Click to collapse
Sorry to hear you are still having trouble, it does sound like the same issue, was a CM13 update from the last couple of days, upon reboot I saw the wileyfox logo but when the Cyanogen logo would normally show during boot it displayed a black screen, which would flicker every few seconds. Holding vol- and power to reboot resulted in the same thing so I was unable use recovery.
When the display was black and connected via USB I was able to see the device using ADB but like you no commands were authorised.
Leaving the phone plugged in via USB and holding down vol+ and power until it rebooted I was able to enter fastboot, once the fastboot prompt was displayed on the screen I attempted using fastboot to boot from a custom recovery, unfortunately that just resulted in the same blank screen for me. I also tried booting the stock recovery with the same result, I admit I did not try many older CM recoveries, but I wanted to revert to CM12.1 anyway, as the accelerometer and gyroscope not working in CM13 at the moment is no good for me.
Only thing that worked was a stock restore, so I think something beyond the recovery got broken as you could not even boot a previously working recovery.
For the sake of sanity it may be work getting someone else try booting it into fastboot before resorting to Wileyfox support. Though your phone is really new so could claim a refund or replacement from the seller, that would probably be faster.
FYI if you do end up sending it to Wileyfox support they do flash it back to stock, I had a broken screen replaced, was repaired and back to me in just under 2 weeks.
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
maxxie00 said:
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
Click to expand...
Click to collapse
Hi,
Just tried a few combinations to check timings for you.
Powered off, not plugged in, holding vol+ while plugging in phone end of usb connected to computer, keep holding vol+ -> boots straight to fastboot.
Powered on, already connected to computer via usb, holding vol+ and power, release power when vibrates to indicate reboot but keep holding vol+ -> boots straight to fastboot.
Are you seeing the black and white Wileyfox logo when first booting? When going to fastboot it should skip that. If you are not seeing the logo it might not show the fastboot screen either. You can try following the steps above and then issuing fastboot devices from a command/shell session to see if you are in fastboot mode.
I hope that is of some help.
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
maxxie00 said:
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
Click to expand...
Click to collapse
No problem, I hope you have more luck with the replacement.
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
maxxie00 said:
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
Click to expand...
Click to collapse
Hello again,
So these 5 methods work for me, someone else may have other experiences:
Phone powered off, hold vol+ while connecting USB, other end of USB already plugged into PC, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on, already connected to USB, other end of USB already plugged into PC, hold vol+ and power until reboot vibrate, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on and in OS, already connected to USB, other end of USB already plugged into PC, debug enabled, from ADB console, adb reboot fastboot or adb reboot bootloader
Phone powered on and in OS, advanced reboot options turned on, hold power, select reboot, select bootloader, reboot
Phone powered on and in Recovery, select reboot to bootloader
Currently I am running stock everything.
Perhaps try different USB cables or ports, though I still get to fastboot without the USB cable plugged in.
My Storm was a pre-order so is one of the first releases, it is possible they have changed something since.
Edit: I have come across a thread on the Cyanogen forums which implies this may be related to encrypting your device: http://forum.cyanogenmod.org/topic/117661-bootloader-hangs/ - I see you have been there already
as reference mine is not encrypted at the moment
I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help
Patala1 said:
I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help
Click to expand...
Click to collapse
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.
mayankjet said:
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.
Click to expand...
Click to collapse
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help
Patala1 said:
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help
Click to expand...
Click to collapse
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.
mayankjet said:
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.
Click to expand...
Click to collapse
Fixed it, thank you a lot my friend, saved my ass
Patala1 said:
Fixed it, thank you a lot my friend, saved my ass
Click to expand...
Click to collapse
:good:
OK I have added the fix in guide
I was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!
Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?
Alaunus said:
I was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!
Click to expand...
Click to collapse
Dload method. Put sd card in other phone or some card readers and put appropriate files.
nemanjsb said:
Dload method. Put sd card in other phone or some card readers and put appropriate files.
Click to expand...
Click to collapse
I've already tried that. I've placed the appropriate files into my SDcard but I can't use any button commands including volume up+down+power. When I press them my device just boots into the EMUI logo and nothing happens.
Edit: It boots into the EMUI logo even if I only press the power button. Pressing volume down + usb also boots me into the EMUI logo
DaarkZek said:
Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?
Click to expand...
Click to collapse
I measured once and not trice before cutting... I was also not paying enough attention/in a hurry...
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
Ok, it seems like not all is lost about my phone. I managed to get into fastboot. In my situation, pressing volume down + usb cable while the battery was plugged into the phone did not work. That was before I opened up my phone's case and disconnected the battery cable.
As I mentioned before, I had opened my phone and disconnected the battery cable because that was the only way to shut it off.
What I did after I disconnected the battery cable was the following:
1 - Hold volume down and don't release it
2 - Plug in USB
3 - Plug in the battery cable into the phone's mobo.
That booted me into fastboot. Right now, the phone says my bootloader in unlocked and my FRP is locked. What would be the best way to flash the new stock OS on my phone?
Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
I have downloaded THIS and THIS for the new OS but by talking with Alexxxx1 in THIS discussion I learnt that Huawei has implemented a security patch in their latest update, which I've most likely installed, that prevents you from rolling back your OS version. That means I need to install the .386 version, which should be the last if I am not wrong, instead of the .378 correct? Though I heavily dislike patches like this I guess I can't do anything about that...
Hoping someone can shed some light. Rushing to root phone again to send back warranty replacement, in my haste my laptop died mid flash and now can only boot in Fastboot and Crashdump Mode.
I am attempting to restore to factory via the MSM tool but cannot for the life of me enter EDL mode.
With phone powered off and pressing the vol up and down keys while plugging into the PC, it only enters Fastboot mode
I have tried to do it with phone off, rebooting from Crashdump mode, from fastboot and it seems that no combination allows me to do so.
I have also tried just vol up and vol down. App loaded at the flash screen, not loaded, etc.
Thanks in advance
quy said:
Hoping someone can shed some light. Rushing to root phone again to send back warranty replacement, in my haste my laptop died mid flash and now can only boot in Fastboot and Crashdump Mode.
I am attempting to restore to factory via the MSM tool but cannot for the life of me enter EDL mode.
With phone powered off and pressing the vol up and down keys while plugging into the PC, it only enters Fastboot mode
I have tried to do it with phone off, rebooting from Crashdump mode, from fastboot and it seems that no combination allows me to do so.
I have also tried just vol up and vol down. App loaded at the flash screen, not loaded, etc.
Thanks in advance
Click to expand...
Click to collapse
What I did when I was in Crash Dump Mode was,
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to pc while still holding the buttons. Done. MSM tool will detect your phone.
NOTE : Also keep the Device Manager window open on the PC while u connect the phone to pc and check if it shows up there.
quy said:
Hoping someone can shed some light. Rushing to root phone again to send back warranty replacement, in my haste my laptop died mid flash and now can only boot in Fastboot and Crashdump Mode.
I am attempting to restore to factory via the MSM tool but cannot for the life of me enter EDL mode.
With phone powered off and pressing the vol up and down keys while plugging into the PC, it only enters Fastboot mode
I have tried to do it with phone off, rebooting from Crashdump mode, from fastboot and it seems that no combination allows me to do so.
I have also tried just vol up and vol down. App loaded at the flash screen, not loaded, etc.
Thanks in advance
Click to expand...
Click to collapse
It always seems to take me several tries to get it right. I think if I don't hit the vol +/- keys right at the exact time that's the problem. Just be patient and keep trying. The first time I did it, it took me what seemed forever. Thought maybe my phone was broken.
Sent from my IN2025 using Tapatalk
rmiles7721 said:
It always seems to take me several tries to get it right. I think if I don't hit the vol +/- keys right at the exact time that's the problem. Just be patient and keep trying. The first time I did it, it took me what seemed forever. Thought maybe my phone was broken.
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
I have been doing custom roms since the old win ce devices....and yet you sir have been able to make me feel like an idiot haha. Thanks for this. you had it spot on!! thanks so much
Hello Folks. So i have found myself in this situation as well. MY phone wont go off and keeps restarting to CrashDump Mode. As such can't seem to get into EDL mode inorder to flash. Any tips? I have tried all the above methods nothing seems to work. Is there a different key combination or a fastboot command i can use to achieve EDL? Help a brother i'm going nuts. Device IN2020
HaronM said:
Hello Folks. So i have found myself in this situation as well. MY phone wont go off and keeps restarting to CrashDump Mode. As such can't seem to get into EDL mode inorder to flash. Any tips? I have tried all the above methods nothing seems to work. Is there a different key combination or a fastboot command i can use to achieve EDL? Help a brother i'm going nuts. Device IN2020
Click to expand...
Click to collapse
You just need to keep trying it. Make sure you hit vol+/- at the same time and hold for a few seconds, plug in the USB cable, then let off the vol keys. It's difficult to do and get right with two hands. Recently did it again as I wanted to upgrade to the 11 beta from a clean system. Seems like it took me forever to get it this time but eventually I did.
Use usb 2.0 port.
After using 2.0 instead of 3.0 and the phone connected stable for a while (after many tries)
able to finish the msm operation successful ..
But phone not booting .. getting black screen after 1+ logo
at this point I thought to clear cache but My phone is locked I cannot use any recovery .. I cannot even go into oneplu recovery LOL .. It seems like I am doomed
For me personally I could only get it to work on USB2.0 ports. On USB3.0 it just puts me back into fastboot mode or when it does go into EDL MSM tool just fails with a communication error immediately.
I kinda bricked mine as well messing around with GSI ROM's and flashing too hastily and to the wrong partition lol.
It has always worked for me with USB 2.0 port and non oneplus cable.
originable cable would not work for me on usb 3 or USB 2 port, but 3rd party cable start immediately with USB 2 port.
I've had the issue where EDL mode works..... for a few seconds, then the phone reboots.
Very frustrating!
The MSM Download Tool does spot the phone, but since the phone seems to reboot, I don't have enough time to do anything!
Any ideas why this is happening?
OneOfThePetes said:
I've had the issue where EDL mode works..... for a few seconds, then the phone reboots.
Very frustrating!
The MSM Download Tool does spot the phone, but since the phone seems to reboot, I don't have enough time to do anything!
Any ideas why this is happening?
Click to expand...
Click to collapse
You need to already hit start on msmtool BEFORE plugging in phone
1- start MSM tool (prepare the settings and choose the right oos)
2-keep the cable connected to one end (I prefere to keep it connected from the phone side first)
3-keep holding volume up/down for 3-4 sec and connect the other end of the cable to your PC
4-your device will be connected directly stop holding volume up/down and in msm tool press start wait for ≈300 sec
5-now your device should work as it was before
OneOfThePetes said:
I've had the issue where EDL mode works..... for a few seconds, then the phone reboots.
Very frustrating!
The MSM Download Tool does spot the phone, but since the phone seems to reboot, I don't have enough time to do anything!
Any ideas why this is happening?
Click to expand...
Click to collapse
After rebooting my pc, and fiddling with drivers, I got it all sorted finally.
Thanks for your help, folks.
Niranjan Bapat said:
What I did when I was in Crash Dump Mode was,
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to pc while still holding the buttons. Done. MSM tool will detect your phone.
NOTE : Also keep the Device Manager window open on the PC while u connect the phone to pc and check if it shows up there.
Click to expand...
Click to collapse
This is a royal pita! I remember when it used to be fun....
Anyway, I've been trying every trick in the book, and then some, but shiznit just isn't going right! The holding of the up and down buttons would be easier if this was the pixel, but it is a tad hard to not mistakenly hit the power button on the other side.
The device manager shows the Qualcomm QDLoader and the msm Downloader is showing the infamous waiting for device... I've been at it for 8 straight hours and if there was a local OnePlus store that sold the international version of the OP8P, that's where I would be heading in a few hours.... It's really frustrating to say the least.
Anyway, when I'm in the bootloader, the device manager shows the Android phone, so I'm thinking that maybe I am in the edl mode when the Qualcomm port shows up, but like I said, the msm is waiting....
tried everything and it is constantly booting into bootloader. I even tried an adjusted fastboot script to boot into EDL but it still boots into bootloader. I have booted into EDL before on a OnePlus 7T, and I have tried multiple times by pressing the OnePlus 8 pro volume buttons at the same time, but always bootloader. Just to check, I tried doing it on my OP 7T again and it worked perfectly fine. Help????
I have had to flash stock 4 times because I land in crash dump mode and it has always been a tricky situation to get into edl.
What worked for me 100% of the time was following the steps in the youtube guide below.
From 2:30 onwards
Hope it helps
I had the same issues, but fixed once read comments as per above. Let me summarize what I did:
1. installed driver Qualcomm HS-USB QDLoader 9008 (I'm using Windows 10) - driver in a cab file should be unpacked using command expand (with proper switches) to preserve folders.
2. launched MSM DT and had it configured and then pressed Verify\Start, as EDL is available only for very short time - 2-3 secs with screen turned off.
3. as my phone was stuck in booting loop I was just keeping presses Vol+/- waiting for EDL to be entered, MDM will find the phone and start uploading data.
Just don't give up trying.
quy said:
Hoping someone can shed some light. Rushing to root phone again to send back warranty replacement, in my haste my laptop died mid flash and now can only boot in Fastboot and Crashdump Mode.
I am attempting to restore to factory via the MSM tool but cannot for the life of me enter EDL mode.
With phone powered off and pressing the vol up and down keys while plugging into the PC, it only enters Fastboot mode
I have tried to do it with phone off, rebooting from Crashdump mode, from fastboot and it seems that no combination allows me to do so.
I have also tried just vol up and vol down. App loaded at the flash screen, not loaded, etc.
Thanks in advance
Click to expand...
Click to collapse
Try different ports. My usb 3 port would force it into fastboot but usb 2 was fine.
What to do if the device doesn't have any usb 2.0 port?