Related
Okay so I seem to have run into a little problem I was planning on updating cleanrom up to 1.2.5 but was on cwm. I had managed to switch over successfully to twrp 2.2.0. I went ahead and used goo manager to download the updated zip of 2.2.1 and tried flashing it thru twrp. Now I am stuck in google bootloop and cant get into recovery or more importantly bootloader. I have been trying last 30mins to hold power and both volume buttons but it either keeps rebooting back to the google screen or not doing anything at all just have to repress to to turn it off but it will turn back on automatically. I tried hooking it up to my usb and labtop but it looks like it wont even recognize it. I just fully charged it so I am good for now just a little worried cant get out of this mess.
I ran into a problem like that with clockwork recovery it kept on rebooting in recovery but I could still go into download mode I was at work away from my computer so I had no choice but to keep trying that three button magic until it finally restored a backup I had on my external card.just keep on trying to pull the battery then try to go into recovery. You might 've gotten a bad download
Sent from my SGH-T999 using xda premium
problem is I cant get into recovery. or the green screen to get to bootloader. It just completely stuck in a bootloop on the google screen mocking me... I am really contemplating opening it up and taking out battery but is that a good idea? Or is there anything else I can do?
so I pulled off the back cover but really dont want o disconnect the battery might mess something up but I cannot get the device to shut off.
disconnecting the battery does nothing it shuts it off and keeps it off but when I connect it to the charger the battery symbol pops up for a second and then goes completely blank. I went ahead and tried again to boot into bootloader pressing power vol up + down and all combinations of power vol -, power vol +
power turbo press vol +/- but no luck still in google screen.
If you're in a bootloop you need to connect your Nexus 7 to a computer. Then you will be able to access recovery via the Power button and volume buttons.
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
clago87 said:
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
Click to expand...
Click to collapse
It's supposed to do that when you're trying to go to recovery from bootloader without the USB cable plugged into a computer, may need to have the drivers installed on said computer. It's an issue with the nexus 7 bootloader and every one of them does it. What your experiencing is perfectly normal if you tried to go to recovery from bootloader with the bolume buttons and then got the google screen bootloop.
If it doesn't work when you plug it in and try, then try unplugging it, manually rebooting with it plugged in first, or vice versa
Update: I can get on Team Viewer and remotely reboot you into recovery through the PC if you want, or at least give it my best shot.
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
clago87 said:
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
Click to expand...
Click to collapse
Have you installed the right drivers on the computer you're using, for ADB and the device drivers, when you unlocked and rooted?
Answer to your question is yes try that. But I wouldn't be disconnecting and reconnecting it, I can't recommend that and then learn tomorrow that static zapped something important.
yea I am getting nothing by connecting to pc. I have all the drivers adb and fastboot installed when I rooted and unlocked couple weeks back but it looks like device is not being recognized or read at all by the pc.
connecting to the pc holding the volume + button gets it recognized for a second and tries to install a driver apx but unsuccessfully.
I am not making any progress whatsoever kinda sucks starting the weekend like this. I have gone thru some bad stuff with my atrix but nothing like this were I cant even access my bootloader boot into recovery or even fastboot. Should I try and get it to just stay off and see if overnight it works its own magic? Hate going to sleep witht his on my mind but I think with a clear mind in the morning something good will happen.
I can get it to stay off by holding both vol+ and vol- but trying to turn it off with just the power button just keeps it turning back on/off...
so I slepted on it thru the night let the tablet rest but went back this morning and I still cant get into bootloader or recovery. Is there anything I can do?
Has anyone else had this problem where they cant boot into recovery or bootloader? It's like the power button and vol keys are unresponsive even though they still work to turn on the device.
are you sure that you flashed the right recovery? but you should still be able to get the bootloader. are you pressing power + volume down(volume down, not both volume buttons. i noticed you wrote both volume buttons) to get into the bootloader?
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
clago87 said:
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
Click to expand...
Click to collapse
good luck!
yea, only power button and the volume down button.
quick question before I connect the battery does it make a difference whether or not I have it plugged in charging or connected to the PC while trying to boot into bootloader?
Update: I was able to get it recognized via fastboot and used NRT to flash back to stock under the bootloop option.
Now rooted with factory 5.0.1 !
The way I got it to recognize the tablet was to press the middle part of the volume switch (effectively pressing up AND down volume) and the power button and then the bootloader loaded and I could use fastboot but not adb. I read in another thread about pressing the middle of the sound button. Never heard of that before.
Hopefully someone can help me out.
i updated via abd using the flash all script. Now when it boots up it's stuck on the logo of flying color dots. (yes, I waited 15-20 min at least)
Anyway, now I can boot into fastbboot mode but the computer doesn't recognize it.
If I try to boot into recovery (which I think got corrupted) then I just get the android icon with a red exclamation point.
I have no way to clean anything up cause I can't communicate with it.
Edit: I'm stuck in a boot loop also. If I just let it boot it stays on the logo forever. When I try to turn it off it just reboots to the logo.
If I use the keys to boot to fastboot it just sits there and now I can't even change the option at that point and there's no way to completely shut it down!
Thanks for any assistance you might have.
Pressing both volume buttons and the power button will get you into fastboot mode. It's always the last fallback position and I've never known it to fail. I had the same with a bad flash on Tuesday when trying to solve my wifi problems.
Glad you got it sorted
Thanks.
I was getting to the bootloader screen but couldn't get the PC to see it. I always used to use power/vol down combo to boot into bootloader and didn't even know u could press both vol up and down at the same time.
Or maybe I'm imagining it all.
GrenW said:
Pressing both volume buttons and the power button will get you into fastboot mode. It's always the last fallback position and I've never known it to fail. I had the same with a bad flash on Tuesday when trying to solve my wifi problems.
Glad you got it sorted
Click to expand...
Click to collapse
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
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Was it stock (including recovery) or modified?
I would try to fastboot the TWRP over and then boot into that (Power & Vol+). But then... I seldom run stock.
SoNic67 said:
Was it stock (including recovery) or modified?
I would try to fastboot the TWRP over and then boot into that (Power & Vol+). But then... I seldom run stock.
Click to expand...
Click to collapse
No, it wasn't stock and I dont know what happened.. I was running the latest CM13 and rebooted this morning and it freezes up with the ASUS logo and saying "Fastboot Mode!!!" at the top... I've tried flashing twrp via fastboot but not getting anything.. I need a copy of the stock firmware with the boot system and recovery image in it but I'm having a hard time finding it.
BiasedThunder said:
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Click to expand...
Click to collapse
I too had this issue. Tried lot of key combinations. Didn't work. My solution was to connect to PC and run
fastboot continue
Then it booted normally. Everything stock.
Hope this helps.
BiasedThunder said:
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Click to expand...
Click to collapse
Phones boots into fastboot mode in two situations
1. Pressing vol up and power button simultaneously for rebooting
2. Your phone doesn't have recovery AND any OS installed
I guess your vol up button is constantly in pressed state.
Second situation cannot occur unless you wipe your system and recovery manually. So you are in the first situation
Your phone's vol up button is constantly in pressed state or electrically shorted may be due to water entering the case
Solution: You will have to open your phone's case and clean the area near the volume button. I guess you had opened the case/body and didn't fit it properly.
sziraqui said:
Phones boots into fastboot mode in two situations
1. Pressing vol up and power button simultaneously for rebooting
2. Your phone doesn't have recovery AND any OS installed
I guess your vol up button is constantly in pressed state.
Second situation cannot occur unless you wipe your system and recovery manually. So you are in the first situation
Your phone's vol up button is constantly in pressed state or electrically shorted may be due to water entering the case
Solution: You will have to open your phone's case and clean the area near the volume button. I guess you had opened the case/body and didn't fit it properly.
Click to expand...
Click to collapse
something happened when it rebooted and it lost recovery.. I fastboot flashed the new TWRP and reflashed the rom and all seems fine now.
Thanks for the quick responses!!
even I've witnessed a similar problem.. please help me.....out
BiasedThunder said:
No, it wasn't stock and I dont know what happened.. I was running the latest CM13 and rebooted this morning and it freezes up with the ASUS logo and saying "Fastboot Mode!!!" at the top... I've tried flashing twrp via fastboot but not getting anything.. I need a copy of the stock firmware with the boot system and recovery image in it but I'm having a hard time finding it.
Click to expand...
Click to collapse
Can any one please suggest where to find the stock firmware with the boot system....Please help me out here
Hello the second situation is happening to me. What can i do? In desperate
Help Me
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
grafikermc said:
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
Click to expand...
Click to collapse
Reinstall twrp from fastboot & install rom
I got a replacement device from OP and I was unlocking the bootloader and rooting it. The guide i used had the incorrect patched boot image and everything went bad quick.
I can't go anywhere except fastboot now, can't boot to OS, no OS installed.
TWRP WAS booting from fastboot, I pushed the rom from there and flashed it...said no OS installed after, I installed it on both slots.
I can't get into EDL mode, the volume keys work...I think, but the second I let go of them when it's plugged in it defaults back to fastboot immediately. I tried the bat file that people use, says it worked, phone stays in fastboot.
I even tried holding the volume keys the entire time but the MSM tool wouldn't read it enough to flash anything, although it did read it enough to register some data, but was stuck on "waiting for device".
I am in need of some major help. Now I can't even temp boot to twrp, getting an error failed authorization. I'm afraid I really messed things up.
I have 5 days to send my old device back. Please help!
May be a longshot, but does the stock recovery work? Maybe try sideloading the full OTA zip from there?
Sent from my IN2025 using Tapatalk
For EDL mode, you need to hold the buttons then plug it in while continuing to hold the buttons. It won't work if the phone is already plugged into a usb port and then you try and get into EDL.
Really hard to brick a OnePlus device in my experience.
FernBch said:
May be a longshot, but does the stock recovery work? Maybe try sideloading the full OTA zip from there?
Click to expand...
Click to collapse
Recovery doesn't work. I was able to get to one of the steps to approve going into fastboot, advanced, reboot to fastboot, but not anymore.
Mike02z said:
For EDL mode, you need to hold the buttons then plug it in while continuing to hold the buttons. It won't work if the phone is already plugged into a usb port and then you try and get into EDL.
Really hard to brick a OnePlus device in my experience.
Click to expand...
Click to collapse
I was doing just that. It seemed to work initially but after I plugged it in and released the buttons it went back to fastboot and disconnected from MSM.
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Please read this https://forum.xda-developers.com/showpost.php?p=82508527&postcount=67
and this https://forum.xda-developers.com/showpost.php?p=82658631&postcount=85
both work for me.
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
I ended up using the fastboot ROM flash all.bat from this thread: https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
I am now booting into the OS and the stock recovery came back. So good news is the phone isn't bricked.
Glad you sort it out
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
It work, thanks
You're a life saver