Database Users

Stuck on Google logo boot screen -- Bricked??

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

[Q] Nexus 7 bricked on laying robot with red exclamation mark

Right... I spent the last 6 hours reading through the forum and Googling about this problem. I learnt a lot (!), but cannot solve the problem, and I now hope someone can help me
Sorry for the lenghty post, but there's a lot of information to share...
Yesterday, my long-awaited Nexus 7 (8Gb) finally arrived. It worked just fine for an hour or so: I got online without any issue, Calendar, Photos, GMail and Contacts were nicely synching and I was really starting to get impressed about the speed and features.
I did download a couple apps, more specifically Aldiko & Moon+ Reader ebook reader apps, and Facebook).
Suddenly --I believe I just started the Facebook app-- the screen turned black and showed strange stripes. The device rebooted and got stuck on the black screen with the white "Google" text. I let it sit there for a while and then instinctively tried to power-off the device by holding the power button for 10 seconds or so. It did indeed reboot, but when the tablet booted up, it popped back to the black Google screen and just sat there.
FYI: The USB cable was connected all of the time, and the first time I plugged the Nexus in, my Win 7 64bit machine recognized the tablet and loaded the drivers for it.
When it got stuck, I decided to continue charging it, thinking that maybe the battery wasn't fully charged and the cause of the problem. I hooked it up to the official charger in a wall socket and let it sit there for a while, while I started searching the web for a solution. After about 30 minutes, when I had read about the power+volume button combination, I tried this combination (until then the Google page showed for more than 30 minutes). The Nexus indeed showed the Fastboot screen, and I had to plug it back in the PC's USB to get the buttons "start", "recovery mode", "power off" and "restart bootloader" working. None of them had any effect.
The fastboot screen showed the product name "grouper", the lock state as "locked"; the bootloader as version 3.34 and the HW version as ER3.
I downloaded the "Nexus root toolkit" from WugFresh and tried to flash it back to "stock" with Android 4.1.1 JRO03D. The tool did show my serial number, btw.... Until then, I had good hopes, but then it went wrong: the tool downloaded the files, unpacked them and said something about "wiping flash" and everything froze. After about 20 minutes, I concluded it had locked-up and unplugged the device.
It now seems to be completely "bricked"...
I can no longer get to the fastboot screen; Not even with the 3-button trick... it always shows the Google screen and immediately shows the "dead robot" screen with the exclamation mark.
The Nexus does not start up Android, so I cannot activate ADB/ USB debugging...
The device is no longer recognized by my PC; the PC doesn't make the "USB hooked up/disconnected" sound anymore
I tried uninstalling the drivers and installed the "naked drivers", no solution -- they show up with yellow exclamation marks
I installed the SDK, and "fastboot.exe devices" shows nothing
I downloaded the "Nexus 7 Toolkit 2.0"; I cannot access the tablet, no serials show, drivers cannot be installed
FYI: I did not try to root it or unlock it. I rebooted my PC, I power-cycled the Nexus, I changed USB ports, sigh...
I'm afraid I actually bricked my device... If so indeed, and given the fact that I cannot access the device with any of the tools/toolkits, is there anything I can do to put it back to factory settings?

Someone else may chime in with some help, but I think using the toolkit screwed you. Had you just used fastboot while you had the bootloader up you could have reflashed the stock rom yourself using the file from here and these commands.. but since you can't get into the bootloader now I think its hosed, but I could be wrong though.

I just noticed that when I press the power + volume up button, my PC detects it as an "Asus Transformer Prime APX Interface"?
Would this be another "way in"? (found something about NVflash on Google?)

Here are two threads on the topic, however I don't think they restore it that way since mostly its done thru the bootloader
http://forum.xda-developers.com/showthread.php?t=1879228
http://forum.xda-developers.com/showthread.php?t=1882753

and people still continue to use toolkits because its easier. in reality its just easier to mess upon your device. reading through the forums i have yet to see someone that messed up their device with fastboot oem unlock amd fastboot flash recovery recovery.img.

To be honest; I feel the toolkits are great for people that know what they're doing and understand the process and are just looking for a quick way to do it.
People that are new to the rooting scene and don't understand the process are the people that SHOULDN'T be using these toolkits. They need to learn about the process and do it a few times manually before even attempting the toolkits.

OK guys, I got the message and yep, shouldn't have used the toolkit. **guilty** :cyclops:
But what advise do you guys have? Would the APX/NVFlash path make sense?
Or can you advise how to get support from Google/Asus in Belgium (bought tablet in Staples US )
thanks!

Considering it doesn't seem anyone has used NVFlash to restore it looks like you are going to have to return/exchange/RMA whatever option is available to you, unless its figured out

i see you pressing volume up and down and power button to get into the bootloader.. but thats wrong. its power button + volume down to get into the bootloader(maybe thatll make a difference for you). but yea, chances are that youll need to go for an exchange/repair.

Nvflash should work though. I haven't used it since.my last tablet and.unfortunately I forget how to use it. I don't think zip files can be used. I think someone could help him that knows how to set up a folder of files for nvflash.

simms22 said:
i see you pressing volume up and down and power button to get into the bootloader.. but thats wrong. its power button + volume down to get into the bootloader(maybe thatll make a difference for you). but yea, chances are that youll need to go for an exchange/repair.
Click to expand...
Click to collapse
hi, the combination did the job before, but just to be sure, I have tried them all:
power + vol up + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol up: Goes into APX mode (and PC chimes)

bigooze said:
hi, the combination did the job before, but just to be sure, I have tried them all:
power + vol up + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol down: black Google screen, followed by the dead robot with exclamation mark sign...
power + vol up: Goes into APX mode (and PC chimes)
Click to expand...
Click to collapse
robot with an exclamation is the stock recovery. it wants to be flashed with the stock google image https://developers.google.com/android/nexus/images#nakasi

simms22 said:
robot with an exclamation is the stock recovery. it wants to be flashed with the stock google .img
Click to expand...
Click to collapse
Hmm... And how would one do this? What tool should be used?

bigooze said:
Hmm... And how would one do this? What tool should be used?
Click to expand...
Click to collapse
read the page and links provided there, the instructions are there.

simms22 said:
read the page and links provided there, the instructions are there.
Click to expand...
Click to collapse
Dont think you can flash those files thru recovery, I already posted that link for him unfortunately without the bootloader I think hes hosed
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
Click to expand...
Click to collapse
When the android with the red mark comes up, press power+vol up, does the recovery come up?

simms22 said:
read the page and links provided there, the instructions are there.
Click to expand...
Click to collapse
Oops... getting late here -- didn't notice the link...
Anyway, the instructions indicate the use of the fastboot tool, which do not work :crying:

[Q] Possible Brick?

Hey all, requesting some assistance...
I had used the nexus 7 toolkit to unlock the bootloader and root my tablet.
Earlier this afternoon, I decided to cave and flash cm10 on my tablet. Before doing so, instructions stated to wipe. In my ignorance, I wiped one too many things and also wiped the internal memory.
As a result, I am unable to get my tablet to fastboot and when I searched for the .zip to flash, I was presented with an ominously empty file directory to my sdcard's root. I have tried various things with the nexus 7 toolkit and have been unsuccessful in my endeavors, as many of those functions require the tablet to be in fastboot mode before any of them will work.
The device is stuck on the Google screen, and if I push the volume buttons with the power button, it will flicker and eventually return to this screen.
I do have a nandroid backup stored on my machine, but I am unable to use it as I am unable to even boot to the recovery (because I can't get to fastboot)... Any suggestions? I really hope I didn't brick this...

I believe you can get to fastboot mode with the v4.13 bootloader from any other mode so long as the battery is not dead and the screen is working.
When the battery has a good charge, hold the power button down until the google logo appears (could be up to 15-18 seconds). At that very moment that the black-and-white google logo image appears, press the Vol-down button.
Voila. Fastboot.
You do need to see that screen appear though; maybe that's the rub. Note that the timing is important - you only get one second or two to do this immediately after the image first appears.
As a bonus, glance at the bottom of that image. Shows an unlocked padlock for an unlocked bootloader, nothing if locked.

It worked! Thanks a bunch!

qwertyx7 said:
It worked! Thanks a bunch!
Click to expand...
Click to collapse
No worries. Glad it worked. Actually, I only stumbled across a reference to that button sequence a couple days ago.
If you see someone else reporting that they "can't get to fastboot", let them know - you can get there from ANY MODE.
[REF] Nexus 7 Button Combinations
Don't be this guy...

[Q] Google Screen Only. No bootloader at all. N7

I was trying to do the 4.2.2 upgrade via CWM 10.1 Everything seemed to be working ok but that the radio was working and could not connect with AT&T. Tried to go back to 4.1.2 with Nesux Root Toolkit. Now it will just sit there at the Google screen. I can't get into the bootloader at all. When I use fasttboot devices there is not list. Looking in device manager nothing is there. I've d/l'ed and re-installed the windows (7) drivers, re-installed Java as well as the SDK.
The only way I can get it to shut off is to hold all three buttons down. Not really sure where to go from here. I'd be happy to just get it back to stock.
UPDATE: I've not been about to get into it no matter what I've tried. I've held down VOL+DN Power for over 10 min. Nothing. VOL+UP gives me a black screen. I've tried different usb cable and different ports. Now, having it plugged into the computer and doing VOL+DN I hear it make a sound after about 30 seconds going up like da-TA than right back down like TA-da.
Not really sure what else to do at this point. I have no problem with opening it up at this point.
I've re-installed the win 7 drivers, system still will not see the N7. Should I just throw myself on the mercy of Google and send it in for repair/replace? What will they do and what will it end up costing me? I would just buy a new one, but I keep hearing that the second Gen is coming out in just a month...

aklesh3 said:
I was trying to do the 4.2.2 upgrade via CWM 10.1 Everything seemed to be working ok but that the radio was working and could not connect with AT&T. Tried to go back to 4.1.2 with Nesux Root Toolkit. Now it will just sit there at the Google screen. I can't get into the bootloader at all. When I use fasttboot devices there is not list. Looking in device manager nothing is there. I've d/l'ed and re-installed the windows (7) drivers, re-installed Java as well as the SDK.
The only way I can get it to shut off is to hold all three buttons down. Not really sure where to go from here. I'd be happy to just get it back to stock.
Click to expand...
Click to collapse
Hi, aklesh3...
The Google Logo (white text on a black background, with an unlocked padlock symbol if unlocked) IS the bootloader.. as is the white battery charging animation whilst charging.
You're just not in FASTBOOT mode....
From a fully powered down state... press and hold VOL DOWN, whist holding press the POWER button. Your device should now boot into the bootloader in FASTBOOT mode.
If you can't get shut the device down (eg. it's wedged/bootlooping), press AND hold both VOL DOWN and the POWER button for a good 30 seconds or more... the device should boot into the bootloader in FASTBOOT mode.
From here...
Code:
fastboot devices
...should yield a serial number indicating you have a FASTBOOT connection. You should now be free to run whatever FASTBOOT commands you like.
----------------------------------
Checkout this list of Nexus 7 button combinations for more specific details on how to break out of a bootloop....
http://forum.xda-developers.com/showthread.php?t=2133986
Rgrds,
Ged.

Nothing.
Thanks for the quick reply. I tried every one of the combos, but nothing. It still just sits at the bootloader screen. fastboot devices shows nothing in the list. What should I try next?
GedBlake said:
Hi, aklesh3...
The Google Logo (white text on a black background, with an unlocked padlock symbol if unlocked) IS the bootloader.. as is the white battery charging animation whilst charging.
You're just not in FASTBOOT mode....
From a fully powered down state... press and hold VOL DOWN, whist holding press the POWER button. Your device should now boot into the bootloader in FASTBOOT mode.
If you can't get shut the device down (eg. it's wedged/bootlooping), press AND hold both VOL DOWN and the POWER button for a good 30 seconds or more... the device should boot into the bootloader in FASTBOOT mode.
From here...
Code:
fastboot devices
...should yield a serial number indicating you have a FASTBOOT connection. You should now be free to run whatever FASTBOOT commands you like.
----------------------------------
Checkout this list of Nexus 7 button combinations for more specific details on how to break out of a bootloop....
http://forum.xda-developers.com/showthread.php?t=2133986
Rgrds,
Ged.
Click to expand...
Click to collapse

Bricked Storm

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