Database Users

Acer a501 not booting only power light on and off

I really need help if anyone can help out.
I followed guide at http://forum.xda-developers.com/showthread.php?t=1622425
to the T with no errors all looked good until it got hung for 3.5 hrs on this message
Flashing Recovery (SOS) stage one - formatting partition..
I try cmd and adb to see if i can see my devices still listed and it was not. I waited a bit more. than reboot the tablet and to my bad luck only the power button light up. nothing on the screen, even tried to do rest via the reset button, no go, held down the vol button with the power still not luck.
Anyone have a fix for this ??????
Rob

rdukes said:
I really need help if anyone can help out.
I followed guide at http://forum.xda-developers.com/showthread.php?t=1622425
to the T with no errors all looked good until it got hung for 3.5 hrs on this message
Flashing Recovery (SOS) stage one - formatting partition..
I try cmd and adb to see if i can see my devices still listed and it was not. I waited a bit more. than reboot the tablet and to my bad luck only the power button light up. nothing on the screen, even tried to do rest via the reset button, no go, held down the vol button with the power still not luck.
Anyone have a fix for this ??????
Rob
Click to expand...
Click to collapse
If your light is on, and the display is black, you are probably stuck in APX mode. Long press the power button and it should go off.
I would also plug into a charger if I were you, before doing anything else.
You will probably need to NVFlash the bootloader and recovery. If it didn't work well the first time, then you should probably be checking drivers. With the tablet in APX mode (hold pinhole button, press and hold PWR, count to 3 seconds, release PWR, then 1 more second and release pin hole.). Tablet should have black display with lit pwr button.
Plug into USB, and make sure windows recognizes it as a Recovery Device. If not, load the right drivers (I use Google USB Android drivers). Might have to load them manually.
Now, I know you wrote down your UID number somewhere, as you will need it.
I uploaded an old ver3 NVFlash package;
http://www.4shared.com/zip/Lgp9DhiH/NVFLASH_Blackthund3r_3bootload.html
Open a CMD window in the directory you extracted, and type run_all
Make sure you get your tab in APX mode, and windows recognizes it. Then follow the prompts. At the end, if good, it should say "Pass"
It doesn't require USB Debugging. If you can get into APX mode, it may work for you. If not, you might post in the bootloader threads.
Link to converting your UID to SBK is found in the guide you posted earlier.
Good Luck!
MD

download at the top afterota and there should be a get out of apx mode, but in apx mode you hold down the power and the light will go of then you hold it again and it will boot
AFTEROTAhttp://forum.xda-developers.com/showthread.php?t=1675939

Moscow Desire said:
If your light is on, and the display is black, you are probably stuck in APX mode. Long press the power button and it should go off.
I would also plug into a charger if I were you, before doing anything else.
You will probably need to NVFlash the bootloader and recovery. If it didn't work well the first time, then you should probably be checking drivers. With the tablet in APX mode (hold pinhole button, press and hold PWR, count to 3 seconds, release PWR, then 1 more second and release pin hole.). Tablet should have black display with lit pwr button.
Plug into USB, and make sure windows recognizes it as a Recovery Device. If not, load the right drivers (I use Google USB Android drivers). Might have to load them manually.
Now, I know you wrote down your UID number somewhere, as you will need it.
I uploaded an old ver3 NVFlash package;
http://www.4shared.com/zip/Lgp9DhiH/NVFLASH_Blackthund3r_3bootload.html
Open a CMD window in the directory you extracted, and type run_all
Make sure you get your tab in APX mode, and windows recognizes it. Then follow the prompts. At the end, if good, it should say "Pass"
It doesn't require USB Debugging. If you can get into APX mode, it may work for you. If not, you might post in the bootloader threads.
Link to converting your UID to SBK is found in the guide you posted earlier.
Good Luck!
MD
Click to expand...
Click to collapse
Hey MD,
I didn't get that file from you still, but i got my tablet to shwo the logo and the white text again by running the a500apflashtool\nvflash.exe but still not luck with passing Flashing Bootloader (EBT) stage one - formatting partition...
I would love to get more info on how to get pass this.
Robert

rdukes said:
Hey MD,
I didn't get that file from you still, but i got my tablet to shwo the logo and the white text again by running the a500apflashtool\nvflash.exe but still not luck with passing Flashing Bootloader (EBT) stage one - formatting partition...
I would love to get more info on how to get pass this.
Robert
Click to expand...
Click to collapse
IF yr recovery drivers have loaded when you are in apx and yr cpuid is correct
then u may have a tab that has issues with the "bct"... the devs are working on a fix for this....
most of us with this issue rolled back to HC using timmydeans EUU then reflashed the bootloader from there with no probs...go figure???
EDIT: the EUU is for a500 you will not have 3g but its just to get back to HC with - when it comes to flashing the bootloader again be sure to
flash yr chosen ics rom first...
as far as more info take a look at civs b/l or F/R extreme rom threads (last 5-6 pages) - the flash itself should take no more than a minute
or two, i use nvflash as it provides a bit of feedback to you if things aren't quite right
you will need td's EUU link in my sig
and jazzyjames tutorial on how to rollback to HC
you will lose ALL your data not only b/c the EUU wipes it but also
ics system apps dont take kindly to being dragged back to HC so make sure you do a full wipe and format any chance you can
for running a glitch-free ICS

rdukes said:
Hey MD,
I didn't get that file from you still, but i got my tablet to shwo the logo and the white text again by running the a500apflashtool\nvflash.exe but still not luck with passing Flashing Bootloader (EBT) stage one - formatting partition...
I would love to get more info on how to get pass this.
Robert
Click to expand...
Click to collapse
Heck, I e-mailed it to you also earlier.
Well, Dibb's is pretty good on this stuff, so I'll pass it to him. Try his steps. He's pretty good on unbricks also.
For me, it's a bit late. Work tomorrow mate.
Also, make sure you are using a good USB cable. You can't always use phone cables. The newer HTC USB cables work for me. This has been known to make things go wonky.
MD

boot loop after trying to flash twrp 2.2.1

Okay so I seem to have run into a little problem I was planning on updating cleanrom up to 1.2.5 but was on cwm. I had managed to switch over successfully to twrp 2.2.0. I went ahead and used goo manager to download the updated zip of 2.2.1 and tried flashing it thru twrp. Now I am stuck in google bootloop and cant get into recovery or more importantly bootloader. I have been trying last 30mins to hold power and both volume buttons but it either keeps rebooting back to the google screen or not doing anything at all just have to repress to to turn it off but it will turn back on automatically. I tried hooking it up to my usb and labtop but it looks like it wont even recognize it. I just fully charged it so I am good for now just a little worried cant get out of this mess.

I ran into a problem like that with clockwork recovery it kept on rebooting in recovery but I could still go into download mode I was at work away from my computer so I had no choice but to keep trying that three button magic until it finally restored a backup I had on my external card.just keep on trying to pull the battery then try to go into recovery. You might 've gotten a bad download
Sent from my SGH-T999 using xda premium

problem is I cant get into recovery. or the green screen to get to bootloader. It just completely stuck in a bootloop on the google screen mocking me... I am really contemplating opening it up and taking out battery but is that a good idea? Or is there anything else I can do?

so I pulled off the back cover but really dont want o disconnect the battery might mess something up but I cannot get the device to shut off.

disconnecting the battery does nothing it shuts it off and keeps it off but when I connect it to the charger the battery symbol pops up for a second and then goes completely blank. I went ahead and tried again to boot into bootloader pressing power vol up + down and all combinations of power vol -, power vol +
power turbo press vol +/- but no luck still in google screen.

If you're in a bootloop you need to connect your Nexus 7 to a computer. Then you will be able to access recovery via the Power button and volume buttons.

is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.

clago87 said:
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
Click to expand...
Click to collapse
It's supposed to do that when you're trying to go to recovery from bootloader without the USB cable plugged into a computer, may need to have the drivers installed on said computer. It's an issue with the nexus 7 bootloader and every one of them does it. What your experiencing is perfectly normal if you tried to go to recovery from bootloader with the bolume buttons and then got the google screen bootloop.
If it doesn't work when you plug it in and try, then try unplugging it, manually rebooting with it plugged in first, or vice versa
Update: I can get on Team Viewer and remotely reboot you into recovery through the PC if you want, or at least give it my best shot.

ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?

clago87 said:
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
Click to expand...
Click to collapse
Have you installed the right drivers on the computer you're using, for ADB and the device drivers, when you unlocked and rooted?
Answer to your question is yes try that. But I wouldn't be disconnecting and reconnecting it, I can't recommend that and then learn tomorrow that static zapped something important.

yea I am getting nothing by connecting to pc. I have all the drivers adb and fastboot installed when I rooted and unlocked couple weeks back but it looks like device is not being recognized or read at all by the pc.

connecting to the pc holding the volume + button gets it recognized for a second and tries to install a driver apx but unsuccessfully.

I am not making any progress whatsoever kinda sucks starting the weekend like this. I have gone thru some bad stuff with my atrix but nothing like this were I cant even access my bootloader boot into recovery or even fastboot. Should I try and get it to just stay off and see if overnight it works its own magic? Hate going to sleep witht his on my mind but I think with a clear mind in the morning something good will happen.

I can get it to stay off by holding both vol+ and vol- but trying to turn it off with just the power button just keeps it turning back on/off...

so I slepted on it thru the night let the tablet rest but went back this morning and I still cant get into bootloader or recovery. Is there anything I can do?

Has anyone else had this problem where they cant boot into recovery or bootloader? It's like the power button and vol keys are unresponsive even though they still work to turn on the device.

are you sure that you flashed the right recovery? but you should still be able to get the bootloader. are you pressing power + volume down(volume down, not both volume buttons. i noticed you wrote both volume buttons) to get into the bootloader?

I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck

clago87 said:
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
Click to expand...
Click to collapse
good luck!
yea, only power button and the volume down button.

quick question before I connect the battery does it make a difference whether or not I have it plugged in charging or connected to the PC while trying to boot into bootloader?

[Q] Unbricking Zte Blade 3

First of all thanks for not caring. I spend days on Internet trying to find a solution. I have Blade which I bricked thanks to my noob skills with flashing and similiar ****. I just want my normal phone back. Couldn't give a **** bout roms anymore. Sorry for the lang but Im mad. When I boot it up it just sits there on green android logo not going past. I can enter download mode if it matters. As soon as I back it up Im getting rid of cwm mode and bull****. I use my sister phone to transfer files on my sd card. I cant enter my recovery mode since I installed that **** of cwm.When I try the key combo-android logo stuck with red light on. My phone has 90-100% battery Im sure. I need a solution where I can do something from pc with download mode or something that will automatecly start when I boot up my phone that I transfered on my SD card. Please guys let me have some sleep. I've been staying all night long just to unbrick it. Dont mention any flashing rooting ****ing...I developed alergy to those words. I want it simple ..please...any help is appreciated. And sorry for my language.

Solution.
I Love The Register Video said:
First of all thanks for not caring. I spend days on Internet trying to find a solution. I have Blade which I bricked thanks to my noob skills with flashing and similiar ****. I just want my normal phone back. Couldn't give a **** bout roms anymore. Sorry for the lang but Im mad. When I boot it up it just sits there on green android logo not going past. I can enter download mode if it matters. As soon as I back it up Im getting rid of cwm mode and bull****. I use my sister phone to transfer files on my sd card. I cant enter my recovery mode since I installed that **** of cwm.When I try the key combo-android logo stuck with red light on. My phone has 90-100% battery Im sure. I need a solution where I can do something from pc with download mode or something that will automatecly start when I boot up my phone that I transfered on my SD card. Please guys let me have some sleep. I've been staying all night long just to unbrick it. Dont mention any flashing rooting ****ing...I developed alergy to those words. I want it simple ..please...any help is appreciated. And sorry for my language.
Click to expand...
Click to collapse
Calm down dude. If you can get in Download Mode , you are lucky. I even know people who had not get to Download Mode and had began to cry , cause the phones were only 3-4 Weeks old. Back to your problem.]First download here the stock rom.[/URL]
Then you need the Android SDK and the platform-tools from Google , so download it , cause you need ADB. Click here to get Android SDK.Then you need the ZTE drivers. Click here to get the drivers.Now get into download mode and connect the device via USB to your PC. Copy the boot.img (or recovery.img if it is in the ZIP package) and flash it via Fastboot (command: fastboot recovery.img) . Now you got the stock recovery. Now push the FULL update.zip at your sdcard , and now go to recovery , and update from sdcard , choose the update.zip ... Flashing takes a while. DO NOT WIPE ANYTHING BEFORE OR AFTER CHOOSING "UPDATE.ZIP" . Now your Phone should fully works normally

Hello, I have also bricked ZTE BLADE 3(I flashed a wrong kernel....). It only turns the red light on when i turn it on and blank screen, does not respond to vol + and vol - key, no android logo, but when I connect it to the computer via usb in Device Manager a COM port opens with the name ZTE DFU(Diagnostic interface). If anyone has experience of reviving this device from this mess? Thank you for your time

Zmaj5 said:
Hello, I have also bricked ZTE BLADE 3(I flashed a wrong kernel....). It only turns the red light on when i turn it on and blank screen, does not respond to vol + and vol - key, no android logo, but when I connect it to the computer via usb in Device Manager a COM port opens with the name ZTE DFU(Diagnostic interface). If anyone has experience of reviving this device from this mess? Thank you for your time
Click to expand...
Click to collapse
Your download screen is destroyed , but you are still able to get into it.
Try to get into it and flash the kernel with fastboot , the screen will bug during fastboot procedure.

My screen is completely blank and black, just the red light showing when i turn it on and it is always on. It does not respond on power button + vol. down, power button + vol. up, power button + vol. down + vol. up. When I connect it to the computer it does not show me a usb flash drive although I have the zte drivers installed and another sd card inside, but in Device Manager I can see it as a COM port(DFU) Diagnostic Interface. I tried accessing the bootloader via adb but it doesnt even list it with command "adb devices". I also tried flashing the recovery image via "fastboot recovery recovery.img" and "fastboot recovery.img" and still no luck, it just hangs at "waiting for device"...

Zmaj5 said:
My screen is completely blank and black, just the red light showing when i turn it on and it is always on. It does not respond on power button + vol. down, power button + vol. up, power button + vol. down + vol. up. When I connect it to the computer it does not show me a usb flash drive although I have the zte drivers installed and another sd card inside, but in Device Manager I can see it as a COM port(DFU) Diagnostic Interface. I tried accessing the bootloader via adb but it doesnt even list it with command "adb devices". I also tried flashing the recovery image via "fastboot recovery recovery.img" and "fastboot recovery.img" and still no luck, it just hangs at "waiting for device"...
Click to expand...
Click to collapse
When the red light still comes up , you still got chances to get it fixed...

I think so too.. but how? The only method left is JTAG... I saw a thread about using a TPT image to flash low level firmware using ZTEflash.exe but that thread was for ZTE Skate I think, I could not find the tpt.img file for zte blade 3.... Is there any other method via usb cable? Or send it to the shop?

Well, here is my situation:
Got a BLADE III Pro
Tried to root it and i played with few tools found on xda and other places (android forums). No luck at all. Tried to flash a CWM and NO LUCK neither. Tried to go back to flash stock CWM (as i was afraid of bricking it), searched for stock cwm and there is my BRICKED phone. When trying to hold volume down and power botton (both for over 20 seconds even) it will show a green android and its stuck there for hours. When trying to go to fast boot mode the same happens (with volume up and power botton).
While trying these two options the PC (Windows 7 64 bit) wont recognize the phone pluged in.
The only way the PC makes a sound is when i hold both volume up and down bottons and power it or plug it in the PC (without the battery even).
I need to know how can i fix it to boot only. PLEASE. Is this a "throw on can" phone now or it can be brought to life? PLEASE TELL ME PEOPLE.
pm me or any info as soon as you guys can.
I will respond to any question you might have.
Thank you in advance.

I have sent my phone to the shop and they said that they would need a jtag box specific for this model or a new motherboard for zte blade 3.... I think this the end for my zte blade 3

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

N7 (tilapia) stuck at logo - no fastboot access ...

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