Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.
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,
I'm not very experienced with those root things and followed a tutorial to do so.
I unlocked the bootloader, had TWRP installed and root. This worked. Now I wanted to remove Root and TWRP and go back to the original state. I couldn't find the stock recovery file, so I installed the P996A04V1.3.0B13_MR2_sd_ssl.zip via TWRP from the SD Card. Till here it worked. I could enter the stock recover and boot the phone.
Then Android wanted to install a security update. I allowed it and this is where the problem started.
The install process stood still on 25% for minutes. I thought it stuck and pressed and hold the power button to reboot that I can wipe the memory. But nothing happened. But the installation Process continued suddenly. I had the feeling that this power key worked like a skip key. So maybe it didn't install a file where it was stuck.
After the installation reached 100% the screen switched to black and nothing worked anymore. I couldn't restart the phone or anything but I think the phone was doing something cause it consumed electricity. When I checked the phone hours later I noticed it was empty.
I can reach the unlocked bootloader now, but none of the selections works. Doing nothing to boot or select Recovery lead to black screen and stuck. Then I have to wait until the battery is empty again. Fastboot, Power Off just restart the phone and I end in the Bootmenu again. I can't even fully charge the phone. As soon as it has enough power to start the Bootmenu appears. So I don't see the display of the charging process.
I don't understand how this could happen. I tried different key combinations when the phone had enough electricty to start. The phone always restarts and end in the bootmenu. Only when I press all three keys it's standing still on the ZTE Logo screen but as soon as I release the keys I end again in the bootmenu.
How can I force another Update?
regards
Let' start with the basic questions:
Do you have proper backup of your data?
Which Android Version did your Axon had before it went unusable?
You could try to reflash TWRP.
Boot your phone into bootmode.
Download a proper TWRP Image on your PC (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Open a cmd shell (press the windows key and type 'cmd' -> press enter)
Navigate to the folder where the TWRP Image is stored ('
Code:
cd C:\Users\[I]YOUR_USER_NAME[/I]\Downloads\
')
Type: '
HTML:
fastboot flash recovery [I]TWRP_IMG_NAME.img[/I]
'
Afterwards you could try to reboot into recovery mode.
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Stevie123 said:
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Click to expand...
Click to collapse
I don't know of any.
But you could boot into EDL Mode (Press and hold Both Volume button and then press the power button) and flash a Stock EDL rom from the Download Center i have linkd before.
It's not visible for the PC. The only thing I see is the charging screen when its total empty and you can't even boot as. As soon as it has enough power to switch to the normal screen the bootloader appears and when I do nothing the screen turns black and nothing happens. I don't even know if it is charging. The LED is off.
Follow this guide to unbrick it and then use MiFlash and flash an EDL ROM
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Yesterday my device hardware buttons stopped working all of a sudden. I rebooted it using the scheduled reboot feature in the phone settings, because I had no other choice.
It automatically entered Fastboot mode and I can only reboot it by keeping the power button pressed (which now works), but it restarts in fastboot mode again.
I've never installed any custom ROM on this device, nor unlocked the bootloader. I've only used the stock ROM and updated it with official OTA updates from time to time, however yesterday there was no update I'm aware of.
How can I make it boot the normal Android system again?
I've found a partial solution myself: just keeping VOL-UP and POWER buttons pressed for about 10 to 20 seconds reboots it into normal Andoid system, however it still happens it goes into fastboot again when I reboot it normally. I know how to exit fastboot loop, but I don't know why it keeps entering it.
Hello i am trying to root my 1year old heavy used phone . I am Stuck at the very first step.
Also it should be mentioned that it got a little bit wet by rain someday and then the volume down button was stuck (not mechanicly) it forced the volume setting to zero and had no sound.
I soft reset it . Than no change. had a hard time getting into recovery but i finally got there somehow i dont remember how.
Then hard reset it.No change....
After one day the volume key fixed itself and everything is working fine.
now after one month i was curious if i could root it. But i am not able to get into bootloader state.
I tried everything.
Debug options and oem bootloader unlock switch enabled, usb debugging enabled.
Usb adb says no permission (serial n visible)
Entering Recovery mode at power off state by
Pressing vol up and power button gets normal boot everytime but much faster logo visible at about 3sec.
pressing power + vol down = it takes 25sec
Booting normal .. and the same happens when pressing both vol keys.
I am releasing the keys at zte logo visible everytime
Something was strange : one time when i was trying something it bootlooped 3 times and then it was safe mode.
could there something in the volume button be broken? but the button work fine. I dont know.
Thanks for reading
update:
ok the permissions was a linux issue(start the adb-daemon with su), i can use adb now on this phone,
i can boot it in recovery now, but cant boot into bootloader
adb reboot bootloader leads to normal boot
in recovery, the reboot into bootloader option also normal boot