Database Users

Stuck in "Erasing"

I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?

No one can help here?

ganiman said:
I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?
Click to expand...
Click to collapse
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.

jsgraphicart said:
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.
Click to expand...
Click to collapse
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).

ganiman said:
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).
Click to expand...
Click to collapse
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.

jsgraphicart said:
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.
Click to expand...
Click to collapse
From https://source.android.com/source/running.html#booting-into-fastboot-mode
Booting into fastboot mode
During a cold boot, the following key combinations can be used to boot into fastboot mode, which is a mode in the bootloader that can be used to flash the devices:
manta Press and hold both Volume Up and Volume Down, then press and hold Power

Hopefully, this thread is still followed....
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!

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

Hardware button don't work in bootloader?

Hey guys. I just got LG G6 H870 model. Unlocked bootloader without much problems, but issues came later. While being in bootloader I can't do anything, hardware buttons seem to not work. The only way to get out of bootloader is to use "fastboot reboot" command, but that prevents me from getting into custom recovery after flashing it. Only entering download mode works (holding volume up and plugin in usb cable). Non other key combination work until I boot into system.
Can this issue be somehow resolved?

I had similar problem myself with entering recovery more and the reason behind it was that I didn't press the button combo in proper way. what you actually have to do is while you in fastboot mode you press down and hold power button and volume down button. phone reboots after a moment and you should still be holding these keys and when lg logo appears you let go of power button for brief second and then press it back again and then when a prompt on white screen appears just go yes two times and phone shall boot in recovery mode . I had watch a tutorial movie to figure that out. other easy way is just to have adb enabled and reboot it with adb reboot recovery command via USB cable

non.verbal said:
I had similar problem myself with entering recovery more and the reason behind it was that I didn't press the button combo in proper way. what you actually have to do is while you in fastboot mode you press down and hold power button and volume down button. phone reboots after a moment and you should still be holding these keys and when lg logo appears you let go of power button for brief second and then press it back again and then when a prompt on white screen appears just go yes two times and phone shall boot in recovery mode . I had watch a tutorial movie to figure that out. other easy way is just to have adb enabled and reboot it with adb reboot recovery command via USB cable
Click to expand...
Click to collapse
No, because I had G5 and I know the proper way to do that. Problem is I can hold the power button as long as I live and the phone won't reboot, regardless of pressed combination or power button solo.

and the adb command way ?

Well... Nevermind, turns out vol down button isn't working at all.

still good way around is adb reboot recovery

mate 9 was bricked, any help?

before brick, it had being prompted for a while to upgrade the system software, I always tab later to postpone it. but yesterday accidentally hit the "upgrade now" then it was bricked after the phone was rebooted.
the screen stayed at the huawei logo and powered by Android at the bottom. I am able to push/hold the power button to power it off, but not able to power it up by any buttons or combination. it will automatically turn on (randomly) and stayed at the huawei logo for ever.
when the phone is on at the Huawei logo, connecting it to PC but either "adb devices -l" or "fastboot devices" shows nothing, no devices.
could anyone please share some light?
Thanks

saltedfish said:
before brick, it had being prompted for a while to upgrade the system software, I always tab later to postpone it. but yesterday accidentally hit the "upgrade now" then it was bricked after the phone was rebooted.
the screen stayed at the huawei logo and powered by Android at the bottom. I am able to push/hold the power button to power it off, but not able to power it up by any buttons or combination. it will automatically turn on (randomly) and stayed at the huawei logo for ever.
when the phone is on at the Huawei logo, connecting it to PC but either "adb devices -l" or "fastboot devices" shows nothing, no devices.
could anyone please share some light?
Thanks
Click to expand...
Click to collapse
Did you ever unlock bootloader? Could you enter fastboot mode? (hold volume - and power button). Or eRecovery (plug usb cable, hold volume + and power, until Huawei logo appear, release power button)?

gazavn said:
Did you ever unlock bootloader? Could you enter fastboot mode? (hold volume - and power button). Or eRecovery (plug usb cable, hold volume + and power, until Huawei logo appear, release power button)?
Click to expand...
Click to collapse
unfortunately, I didn't unlock bootloader, so I can't enter fastboot mode actually. as I mention in the original post, I can only power it off when it's at the Huawei logo, but not able to power it on with any combination, it will randomly power itself on.

You have a corrupted /data partition, happened to me one day, on another huawei device (p9lite). You should, I said should, be able to reboot to huawei e-recovery, using power+volume up, release power after huawei logo shows up. Unfortunately you have to arm yourself with lot of patience and try to use an "unbrick guide" from another device. I'll try to find any info I can for you, but in the mean time you should look as well.
PS:/ I didn't even tried to install anything custom on this mate9, since it;s an expensive phone for me and I cannot afford to brick it up.

Cannot access fastboot or recovery

LG G6 H871 unrooted
I just can't get into fastboot or recovery mode. I've tried everything on the internet.
I've tried turning off the phone. Holding down the volume down button and then plugging in the USB cable.
I've tried adb command "adb reboot bootloader" which just reboots the phone until I can see the "enter your PIN" screen
The closest I got to the recovery mode was using "adb reboot recovery" which gave me the "no command" screen.
Any tips on this?

Have you enabled OEM Unlock option under Developer settings?

Yes. "Enable OEM unlock" and "USB debugging" enabled.

both oem unlock is on and usb debugging on and my computer has accepted the fingerprint from teh device to shake with adb. . still cant get into fastboot mode.what to do.

Is your phone rooted? If so use flashify to reflash recovery. You do know that if you want to boot in recover you have to let the power key go and repress it once your screen goes on right?
You can also try phone off. Holding volume up while you insert usb cable. Might be a tool that allows a command to be send to reboot it in fastboot mode? If not downgrade its firmware..

ErlendAnderson said:
LG G6 H871 unrooted
I just can't get into fastboot or recovery mode. I've tried everything on the internet.
I've tried turning off the phone. Holding down the volume down button and then plugging in the USB cable.
I've tried adb command "adb reboot bootloader" which just reboots the phone until I can see the "enter your PIN" screen
The closest I got to the recovery mode was using "adb reboot recovery" which gave me the "no command" screen.
Any tips on this?
Click to expand...
Click to collapse
If I understand correctly, when you got to the No Command" screen, you were actually in Recovery. From my experience, the No Command screen is like a "greeting", if you will. Once you see that screen, you need to fiddle with the power & volume buttons. I believe the correct combination is to press and hold the power button. Then press and release the volume up button but continue to hold power button. If that is not the correct sequence you will need to Google for the correct order. Reference.
Considering that you are not rooted, there is not much you can do in the stock recovery.
EDIT 2 - Realized that this thread is over a year old and the OP has probably moved on. Didn't realize another member revived it. Sorry.