I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?
No one can help here?
ganiman said:
I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?
Click to expand...
Click to collapse
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.
jsgraphicart said:
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.
Click to expand...
Click to collapse
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).
ganiman said:
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).
Click to expand...
Click to collapse
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.
jsgraphicart said:
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.
Click to expand...
Click to collapse
From https://source.android.com/source/running.html#booting-into-fastboot-mode
Booting into fastboot mode
During a cold boot, the following key combinations can be used to boot into fastboot mode, which is a mode in the bootloader that can be used to flash the devices:
manta Press and hold both Volume Up and Volume Down, then press and hold Power
Hopefully, this thread is still followed....
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Related
I unlocked the bootloader and flashed a custom recovery. I then rebooted the device. Now it is stuck at the bootloader (white Google logo on black background) and I can't get it to do anything else. I've rebooted it a bunch of times including with the vol + and vol - buttons held down to no avail. I've also let the battery run out and then tried to boot it up again and the same thing happens. adb nor fastboot see the device and it doesn't show up in the logs on my machine (Mint 13) as coming online at any time.
Most of the times I reboot it with the power switch it reboots to the Google logo even without me letting go of the power button. Sometimes I can get it to fully power off but I haven't figured out what combination of vol keys and reboot does that.
Anyone have any ideas what could be wrong? Any help would be much appreciated!
You are not bricked if you can still get into the bootloader.
Download the factory image from here, and flash it with fastboot. If you don't know how to do that, read this thread.
I wish I could get fastboot to see it then I could definitively flash that img.
I can't get into the bootloader and can't get fastboot or adb to see it. It's stuck at the Google logo now and when i hold the power key it reboots back to the Google logo with the unlock logo at the bottom.
Thanks for the help
You've tried holding volume down+power for 10+ seconds? That should power off the device, then hold both vol up+down down and power up
Ya I've tried to hold vol + and power for 10+ seconds and it reboots back to the Google logo even if I don't off the power key. Same happens with all the other combinations of keys being held with the power button. I can't get it to turn off now unless I let the battery die
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Tried that and still stuck at the Google logo. I have to go to work for a couple hours and then will hack on it when I'm back. Hope I don't have to deal with Googles rma process seeing how disorganized the rest of that company is
Sent from my HTC one s
No luck with any button combos but the vol + and power actually turned it off. All out of ideas over here. I'm thinking it really is bricked
I'm in the same spot. I can get it into recovery occasionally but once there it locks up after trying to flash or clear the cache.
I'm wondering if a contributing issue is CMR v6.0.0.6? I updated it from 6.0.0.4 that was running fine. But no fastboot or adb so that is doubtful.
This is frustrating and not a great start with this N7.
thank you
giveen said:
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Click to expand...
Click to collapse
this worked. you have to be fast. as soon as screen goes black release power button then quickly, very quickly repress along with vol up and down.
You will still be able to get into the bootloader! Force kill the tablet by holding the power button for ages. Then hold volume up and volume down and the power button together, which will boot to fastboot.
It looks like a CWM bug as I feared. Anyone in the same boat try here - http://forum.xda-developers.com/showthread.php?t=1782932
Nothing has worked and I've literally tried everything that those three buttons can do. Thanks again for all the help guys. Had a great time trying to resurrect it but guess it's time for it to go back home
Just as I suspected. Google puts out buggy junk once again.
I just wanted to report a similarly event. I have a rooted, unlocked Nexus 7, with TWRP recovery. I have previously rebooted without issue. Tonight I booted into bootloader mode to check something and the hit power button to choose start. I got stuck on the boot logo. After finding this thread, I started with the simplest combination and held power button until screen went dark, then added volume down and once again in bootloader. This time choosing start led to a regular system boot. It's as if the device froze and needed a hard reboot.
Sent from my SCH-I535 using Tapatalk 2
I was attempting to boot into recovery and kept getting the 'Google' logo (I am unlocked/rooted with twrp recovery). I wasn't aware that one had to be plugged in via usb in order to *not* hang....
Any way around this?
Once I plugged it in and attempted to boot into recovery it worked fine.
I had a similar issue after using the Nexus Root Toolkit to flash to nakasi 4.2 with CWM recovery - just got stuck on the nexus boot screen, flashing in a loop for over 15 minutes.
I ended up powering down the device, holding power for about 5-10 seconds - then QUICKLY holding both the power and volume up+down keys, it then went into the fastboot screen.
After it was there, plugged it into my PC.
Now, this should work for you - assuming you have all the fastboot/usb driver stuff installed.
I extracted the contents of nakasi-jop40c-factory-6aabb391.tgz into the same directory as the fastboot.exe provided by WugFresh with his Nexus Root Toolkit (google search or xda search for this if you dont have it, i dont think i can post links due to my low postcount) - typical filepath: C:\Program Files (x86)\WugFresh Development\data
By the files in there, I mean drilling down inside the tgz to where the image files were inside so that files like bootloader-grouper-4.13.img, image-nakasi-jop40c.zip etc were extracted into the directory and sitting alongside the fastboot.exe - NOT in a subfolder.
Once its all here, running flash-all.bat (this is provided by google in the nakasi-jop40c-factory-6aabb391.tgz) from the command line or by double clicking on it from explorer should kick off the process. After about 2-3 minutes, it was complete, and my Nexus then booted up within about 3 minutes after that.
Also worth noting, device remained unlocked, but I lost root/root binary
I recently got the update for 4.4 notification, clicked it but then the installation froze on a picture of android with an exclamation in his belly.
After that I could no longer boot to bootloader or recovery.
I tried fastboot but I cant not install the drivers as I cant boot to bootloader.
So I tried NRT and managed to get my recovery back (TWRP), but still no bootloader.
I have the option to return to stock on NRT but I am afraid it will fail and brick my N7.
I have SuperSU, flashify and TWRP apps running now with TWRP recovery also bootable.
How can I get my bootloader back?
Siddy1200 said:
I recently got the update for 4.4 notification, clicked it but then the installation froze on a picture of android with an exclamation in his belly.
After that I could no longer boot to bootloader or recovery.
I tried fastboot but I cant not install the drivers as I cant boot to bootloader.
So I tried NRT and managed to get my recovery back (TWRP), but still no bootloader.
I have the option to return to stock on NRT but I am afraid it will fail and brick my N7.
I have SuperSU, flashify and TWRP apps running now with TWRP recovery also bootable.
How can I get my bootloader back?
Click to expand...
Click to collapse
Hi, Siddy1200...
If you had no bootloader... nothing would work... at all.
The bootloader underpins everything you do with your Nexus 7. Nothing happens without one... in which case , you'd be effectively HARDBRICKED.
The fact that stuff is working indicates that your bootloader is fine.
To access the bootloader manually... shut down the Nexus 7 completely.
Press and hold the VOL DOWN button...
Whilst holding, press the POWER ON button, for around 5-10 seconds...
You should now boot into the bootloader.
This key press sequence should also work if you CAN'T shut down the Nexus 7 normally... for example, if you're bootlooping. I've had a few scary moments myself in the past, and the VOL DOWN+hold, POWER ON sequence has always thrown me back into the bootloader...
Rgrds,
Ged.
GedBlake said:
Hi, Siddy1200...
If you had no bootloader... nothing would work... at all.
The bootloader underpins everything you do with your Nexus 7. Nothing happens without one... in which case , you'd be effectively HARDBRICKED.
The fact that stuff is working indicates that your bootloader is fine.
To access the bootloader manually... shut down the Nexus 7 completely.
Press and hold the VOL DOWN button...
Whilst holding, press the POWER ON button, for around 5-10 seconds...
You should now boot into the bootloader.
This key press sequence should also work if you CAN'T shut down the Nexus 7 normally... for example, if you're bootlooping. I've had a few scary moments myself in the past, and the VOL DOWN+hold, POWER ON sequence has always thrown me back into the bootloader...
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for the reply Greg.
I can't boot to boot loader, that means when I power on with vol- pressed, then select boot loader and press power , it doesn't work. The screen flashes for a second and it is back to the previous screen to where I can choose restart, recovery, boot loader,etc.
This also happened with recovery but I fixed it, now I'm trying to fix the bootloader
Siddy1200 said:
Thanks for the reply Greg.
I can't boot to boot loader, that means when I power on with vol- pressed, then select boot loader and press power , it doesn't work. The screen flashes for a second and it is back to the previous screen to where I can choose restart, recovery, boot loader,etc.
This also happened with recovery but I fixed it, now I'm trying to fix the bootloader
Click to expand...
Click to collapse
Apologies, Siddy1200... but I'm a little confused... based upon my reading of your post... I think you're already in the bootloader!!.
"...it is back to the previous screen to where I can choose restart, recovery, boot loader,etc..."
The bootloader features a green android, lying on its back, with it's belly open - some really tiny text at the lower left hand side of the screen giving details about the current bootloader version and it's lock state. At the upper right hand side of the screen, adjacent to the power button, are selectable options via the POWER BUTTON, which can be cycled through with the VOL BUTTONS... and these options are START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF... and then START again.
Somewhat similar to your above quoted description.
Selecting RESTART BOOTLOADER will just bring you back to where you already are... ie., the BOOTLOADER.
Also, if you can't access the bootloader, how are you managing to boot into TWRP?... as this is normally done via the bootloader... ie, by selecting the RECOVERY MODE option.
Rgrds,
Ged.
GedBlake said:
Apologies, Siddy1200... but I'm a little confused... based upon my reading of your post... I think you're already in the bootloader!!.
"...it is back to the previous screen to where I can choose restart, recovery, boot loader,etc..."
The bootloader features a green android, lying on its back, with it's belly open - some really tiny text at the lower left hand side of the screen giving details about the current bootloader version and it's lock state. At the upper right hand side of the screen, adjacent to the power button, are selectable options via the POWER BUTTON, which can be cycled through with the VOL BUTTONS... and these options are START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF... and then START again.
Somewhat similar to your above quoted description.
Selecting RESTART BOOTLOADER will just bring you back to where you already are... ie., the BOOTLOADER.
Also, if you can't access the bootloader, how are you managing to boot into TWRP?... as this is normally done via the bootloader... ie, by selecting the RECOVERY MODE option.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for your persistence Greg, I think I was confused as what the bootloader actually is, now I can see I am already in bootloader :silly:
I will return to stock with NRT and try the 4.4 update now.
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
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.
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