Related
Stuck in a boot loop after attempting to restore my T-Mobile 801.
It boots up to the T-Mobile splash screen does its little ding a ling thing then 10 seconds later restarts the loop.
I used this http://forum.xda-developers.com/showthread.php?t=2432476
Any other ideas?
Looks like I got it, I did a factory reset on top of it and seems to be working again.
Can you tell me exactly what you did? I seem to be having a similar problem with the Verizon G2 and can't get anything working.
DeBuggz said:
Can you tell me exactly what you did? I seem to be having a similar problem with the Verizon G2 and can't get anything working.
Click to expand...
Click to collapse
After I ran the factory flashing tool, the phone would boot loop (I think most likely because the settings and profile from the last rom wasn't reset by the tool.)
So what I did was use the factory recovery option in the phone by doing the following.
1. Power down the phone (Hold power for 15 Seconds)
2. Press and Hold Vol Down and Power
3. Quickly after seeing the LG logo release the power (while holding Vol Down still) then pressing and holding the power again. You should get a white screen asking if you want to reset your phone press Power to Confirm twice.
A little android pops up and does some work then reboots your phone. The phone should boot after that.
I had originally installed the wrong version of a ROM, D802 instead of VS980. Got stuck in an error with fastboot only, and I ended up following the directions here :
http://forum.xda-developers.com/showthread.php?t=2582142
But I must have messed something up. Now the phone does not start at all. Pushing power buttons does nothing, no buzz, no lights, no logo, no combination of power button, power button + volume down, all 3 buttons, plugged in or not, none of it seems to do anything. The only thing that DOES happen, is that plugged into Windows it shows up as QSHSHUB_BULK device, and that's it. So something in there is on, I guess?
Don't know what to do. Might be completely gone. Anyone have any ideas?
I dont have the intellect to help you now, but for future referance if you flash the wrong thing and end up in fast boot, just use the hard keys to enter your recovery. As opposed to trying to enter fastboot commands, and flash your backup, or a different rom.
Send a pm to xdabbeb. Hes pretty compitent with fastboot
jgaughran said:
I had originally installed the wrong version of a ROM, D802 instead of VS980. Got stuck in an error with fastboot only, and I ended up following the directions here :
http://forum.xda-developers.com/showthread.php?t=2582142
But I must have messed something up. Now the phone does not start at all. Pushing power buttons does nothing, no buzz, no lights, no logo, no combination of power button, power button + volume down, all 3 buttons, plugged in or not, none of it seems to do anything. The only thing that DOES happen, is that plugged into Windows it shows up as QSHSHUB_BULK device, and that's it. So something in there is on, I guess?
Don't know what to do. Might be completely gone. Anyone have any ideas?
Click to expand...
Click to collapse
its not fully dead. when u connect it to the pc does it show u 8 hard drives ? i had this same issue but it was turning on and saying somr sort of error on a black screen. it was detecting as QSHSHUB_BULK . all u need to do is get the files for your version and follow the instructions of that thread. it should work
no hard drives
Can we do anything if it is not even showing up the drives?
Please help me. I am in a sort of panic right now.
I have a ZTE Blade C2 v809, sold here in Portugal as Meo Smart A12. It was rooted and working fine. I was however getting some error 24's trying to install apps. I thought this might have had to do with using Titanium Backup to remove TouchPal (I did make a backup first), so I decided to restore TouchPal. There were however some errors in the restore and it was stuck there, so I decided to reboot the phone.
Chaos. Now it wont boot. If I press the button normally, the phone boots, I see the android logo, the screen goes black (Not shutdown black, a sort of light black background) and nothing happens. If I try to boot into Recovery mode by holding the power button and the volume down key, I just get the android logo stuck there, nothing happens. If I hold the power button and the volume up key, I get the picture of that laying down android with the message error.
Any more info I must provide please tell me, I am desperate for a solution, If I lose this phone I wont be able to get another one.
Okay I fixed it. Turns out the recovery menu DID work if I waited for a long time and tapped the screen. Used the update.zip available from the site, and it works like a charm
Yay, I bricked my phone, too.
I did something similar, changed recovery-from-boot.p name to recovery-from-boot.p-bak and install-recovery.sh to install-recovery.sh-bak
Now the phone doesn't boot properly, in fact it's stuck in a boot loop:
>starts
>shows white ZTE logo on screen
>restarts
Tried connecting the phone via USB cable and used fastboot devices & adb devices commands, no devices found.
Also tried pressing "power + vol down" and "power + vol up", nothing. I can't enter recovery mode or bootloader.
Apparently the remaining way to get in it's trough the SD slot, or maybe there's another way.
I kindly ask for help, couldn't be possible that I ruined this cell phone so fast.
Ideas, somebody?
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
Hi Masters,
Need your advice here.
My p9 lite cannot boot up and only shows your device is booting now screen.
I cannot power off even force power off, and there is no responding whatever key combinations i pushed.
The step taken to this error is I did unlock my p9 lite and tried to flash twrp by following the guide, then I cannot enter fastboot mode and recovery mode after that.
I tried take out the battery and let the phone disconnect with power supply, after i put back the battery, i push the power key it still shows same screen as your device is booting now.
Any idea how to resolve this? I assume some fatal error with the motherboard, but i can say nothing after i unlock the phone.
Your suggestion and advice are much appreciateļ¼ thank you!
I had the same problem,what I did was force power off by holding power button for ,well idk how long but until device booted down,then I held volume down and connected it to pc,so it enters fastboot,but you have to do it fast,as it will reboot once its turned off.Then I tried various twrps,revolution recovery etc,and the only one that worked was meticulus twrp.I know you said you cant force power off,but try holding power key long
Once you hold the power off button, the phone will never power off, instead, the phone will reboot and bring you to the error page "your device is booting now" and stuck there. I tried to push the power up or power down button before i see huawei logo, but it will show me the same page.
Yes,when you hold power off phone will reboot,and you have to be fast with volume down and cable.Pre-plug the cable it computer ,bring it near phone,power off and before it boots plug it in while holding volume-
thank you for your suggestion. I tried many times, no matter how quickly i am, I only able to see the device booting page. I have mentioned one point above, i did take out the battery, and i see the error screen after i put back the battery, so i assume the problem with motherboard.
How many of you did return the faulty and unlocked phone to service centre then get "free" services?