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
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
Weird issue. Moto X play on stock 6.0 + unlocked bootloader + TWRP + rooted. I wanted to revert to stock to upgrade to 6.0.1, booted the phone to recovery and launched fastboot with "fastboot enter". It stayed on "Waiting for device" for a time so I thought I forgot to install the Motorolo drivers (which actually I didn't, checked after the fact and they're there). I pressed CTRL-C to kill fastboot... and now the phone doesn't boot up anymore and when plugging it to a USB charger the white notification LED is steady on but nothing appears on the screen :crying:
Can't boot it holding the Power button, can't boot to recovery, ... any ideas? TIA.
siddharta42 said:
Weird issue. Moto X play on stock 6.0 + unlocked bootloader + TWRP + rooted. I wanted to revert to stock to upgrade to 6.0.1, booted the phone to recovery and launched fastboot with "fastboot enter". It stayed on "Waiting for device" for a time so I thought I forgot to install the Motorolo drivers (which actually I didn't, checked after the fact and they're there). I pressed CTRL-C to kill fastboot... and now the phone doesn't boot up anymore and when plugging it to a USB charger the white notification LED is steady on but nothing appears on the screen :crying:
Can't boot it holding the Power button, can't boot to recovery, ... any ideas? TIA.
Click to expand...
Click to collapse
allow mobile to drain the battery then charge it, this method will work
:victory:Thanks!!!! That worked....after the battery drained completely it came back to life :victory:
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...
I tried flashing the stock firmware via ODIN but the process failed and now my tablet is dead and not responding to power button + vol up/down, nothing happens.
When I hook up the tablet to the Samsung charger that can with it or my PC, the tablet boots into download mode and shows the "an error occurred while updating the device software" message and then starts after about 1 sec. It's been charging all night, so the battery should be 100%.
If I hold the vol up+down is shows the long press to unlock the bootloader for about 1sec then reboots.
Any help to force my tablet to stay on and a way to fix my issue ?
same thing happens with mine (after trying to flash firmware via odin)
reboots over and over without letting you stay in download mode
i have mine in edl mode
It maybe in a black screen of death. Either vol up or down and power for at least 10 seconds. I had this happen to me once.
ygchawki12 said:
i have mine in edl mode
Click to expand...
Click to collapse
how do we boot the tablet into EDL mode? shouldn't we be able to unbrick the phone if we're in EDL mode?