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
Related
Update: I was able to get it recognized via fastboot and used NRT to flash back to stock under the bootloop option.
Now rooted with factory 5.0.1 !
The way I got it to recognize the tablet was to press the middle part of the volume switch (effectively pressing up AND down volume) and the power button and then the bootloader loaded and I could use fastboot but not adb. I read in another thread about pressing the middle of the sound button. Never heard of that before.
Hopefully someone can help me out.
i updated via abd using the flash all script. Now when it boots up it's stuck on the logo of flying color dots. (yes, I waited 15-20 min at least)
Anyway, now I can boot into fastbboot mode but the computer doesn't recognize it.
If I try to boot into recovery (which I think got corrupted) then I just get the android icon with a red exclamation point.
I have no way to clean anything up cause I can't communicate with it.
Edit: I'm stuck in a boot loop also. If I just let it boot it stays on the logo forever. When I try to turn it off it just reboots to the logo.
If I use the keys to boot to fastboot it just sits there and now I can't even change the option at that point and there's no way to completely shut it down!
Thanks for any assistance you might have.
Pressing both volume buttons and the power button will get you into fastboot mode. It's always the last fallback position and I've never known it to fail. I had the same with a bad flash on Tuesday when trying to solve my wifi problems.
Glad you got it sorted
Thanks.
I was getting to the bootloader screen but couldn't get the PC to see it. I always used to use power/vol down combo to boot into bootloader and didn't even know u could press both vol up and down at the same time.
Or maybe I'm imagining it all.
GrenW said:
Pressing both volume buttons and the power button will get you into fastboot mode. It's always the last fallback position and I've never known it to fail. I had the same with a bad flash on Tuesday when trying to solve my wifi problems.
Glad you got it sorted
Click to expand...
Click to collapse
Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?
apsommer said:
Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?
Click to expand...
Click to collapse
When you plug it in while holding volume up what happens?
TheVan28 said:
When you plug it in while holding volume up what happens?
Click to expand...
Click to collapse
Nothing. LED flashes red every few seconds. The same response if plugging it in without holding volume up. Along these same lines, holding the power button on for a few seconds causes the small vibration haptic feedback to occur as if it is turning on normally ... but nothing happens the phone remains dead. Similarly, holding volume down and the power key causes a small vibration haptic feedback as it was booting into recovery ... but nothing happens the phone remains dead. I haven't seen anything on the screen appear, or the phone turn on it any way, since executing the fastboot sequence previously described.
Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk
Ilko said:
Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
Ok, that would be great. I would be thrilled to get the stock ROM back, at this point getting the phone to turn on at all would be a victory! Would you please describe precisely how to do enter flash mode with the phone in the current state? To reiterate, the phone will not turn on in any way (normally, or volume down + power to boot into recovery). The only life in the device is a slow blinking red LED when it's plugged in, and a quick vibration after holding the power button. The screen has not turned on in any way, or the LED shown any color other than red, since executing the fastboot sequence previously described.
hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats
The power key has nothing to do in this context. It is used only to boot into recovery or force OFF.
While holding VOL ↑, plug the USB cable to your PC to enter into fastboot mode (blue light)
While holding VOL ↓, plug the USB cable to your PC to enter into flash mode (green light, or maybe nothing)
TheVan28 said:
hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats
Click to expand...
Click to collapse
Nothing. Device still unresponsive as described.
does your PC detect the device ? (new device sound notification)
Ilko said:
does your PC detect the device ? (new device sound notification)
Click to expand...
Click to collapse
No, the PC does not currently detect the device. All drivers are correctly installed as the phone was recognized accurately prior to the described fastboot sequence.
This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.
Ilko said:
This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.
Click to expand...
Click to collapse
I'm getting something here which is very encouraging! Executing your sequence causes the device manager to blink (refresh) as if it sees something, however no new devices are recognized in the tree. The phone LED goes to a solid green, reminiscent of a fully charged battery, stays on for about 30 seconds, briefly blinks red and then back to green, etc. The device manager is certainly reacting here it just doesn't recognize the device.
So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)
Ilko said:
So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)
Click to expand...
Click to collapse
Unbelievable! You saved me! I'm back up with the stock ROM and peace of mind to attempt the custom ROM process again. Saved me $350 ... thank you!!
That's great : )
It is almost impossible to hard brick a Xperia. If something goes wrong, remember flashtool ^^
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight
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?
So I was trying to flash a rom on this phone for the first time, I failed miserably...
Was following instructions from this thread: [ROM][OFFICIAL] Omnirom Q for OnePlus6T [Every Sunday]
After flashing the omnirom.zip I immediately tried to reboot in recovery and ended-up in a boot loop (see attached image).
I tried multiple times to go back to fastboot mode with vol-up-power combination, it did'nt worked. Always boot back to that screen.
I tried all imaginable combinations of buttons and timing but always ened-up on that screen... exept just one time where I finally ended-up in fast boot.
I dont know how I did it!
So then I pushed TWRP, I saw that the ROM's files were in both partitions, wiped the data and rebooted and returned to that same "unlocked boot loader" screen.
I've been stuck here for 3 days now, I want to go back to fastboot mode so I can push TWRP and restore my nandroid backup.
Anybody knows how I can do this?
Try holding power, volume up and down all at the same time without any cable plugged in to shut it down then while holding the volume up button plug the USB cable that's connected to your computer in. It should boot to bootloader screen.
DrAgNbOi said:
Try holding power, volume up and down all at the same time without any cable plugged in to shut it down then while holding the volume up button plug the USB cable that's connected to your computer in. It should boot to bootloader screen.
Click to expand...
Click to collapse
Thanks for your reply.
Thank you so much. I had'nt tried this specific combination. It worked.
ebab said:
Thanks for your reply.
Thank you so much. I had'nt tried this specific combination. It worked.
Click to expand...
Click to collapse
No worries. Glad it works as I was in the same situation before myself.
Well I'm grateful that I was able to get the device shut down without a hot dead battery. I wasn't able to get it into fastboot by the volume up and plug in. I'm thankful it's off. Do you have any other ideas Im not concerned about data at all. I just would like to get my device back up and running..
Please help me out! Thanks