Database Users

Recovery Problems

I used this guide to root my TF and install CWM. But I have never been able to boot into Recovery. I still get the green Android with the exclamation mark.
I thought I would retry running the cwm.bat again from that guide to see if maybe it just didn't install correctly, but now I can't get ADB Devices to show my device when it's in APX mode. With the device on I can get ADB Devices to show it, but when I power off, and then do Power + Vol Up it boots into APX and my computer makes the sound that a USB was attached... but it never shows up in ADB Devices.
So, I can't update CWM, I can't reinstall it... what do I do?

Any takers?

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

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

Instantly reboots after booting into recovery

I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help

Patala1 said:
I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help
Click to expand...
Click to collapse
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.

mayankjet said:
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.
Click to expand...
Click to collapse
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help

Patala1 said:
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help
Click to expand...
Click to collapse
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.

mayankjet said:
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.
Click to expand...
Click to collapse
Fixed it, thank you a lot my friend, saved my ass

Patala1 said:
Fixed it, thank you a lot my friend, saved my ass
Click to expand...
Click to collapse
:good:

OK I have added the fix in guide

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