Hi, I have a oneplus one running cyanogenmod (one of the first lollipop nightlies, not sure which). The phone is rooted, and has been working fine since march. I was simply in the car using it and upon leaving, next thing I know it's stuck in a boot loop.
I get:
Vibrate
1 sec black (but on) screen
oneplus "powered by android" boot up screen for ~6 seconds
1 sec black (off) screen
Just repeating.
Holding down the power button does nothing. Holding down volume down & power will turn the screen black, until the point at which I let go of the buttons, when it goes back into the loop.
Holding down volume up & power gives you the "fastboot mode" message, but then goes back into the loop after a few seconds of showing that.
So far I have left it charging for 6+ hours, had it discharge fully (which was the only thing that stopped it from constantly restarting) . I have plugged it into my computer, and it is recognised and the drivers start installing (haven't plugged it in since formatting computer), but it turns off before they can be installed.
I was advised to come here from reddit, hope you can help
Have you tried this?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Heisenberg said:
Have you tried this?
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
I didn't want to try it because from their description, my phone isn't hardbricked. The oneplus "powered by android" screen comes on, and it will say fastboot mode if you boot it into fastboot mode, it just restarts after a few seconds of saying that.
bumfluff29 said:
I didn't want to try it because from their description, my phone isn't hardbricked. The oneplus "powered by android" screen comes on, and it will say fastboot mode if you boot it into fastboot mode, it just restarts after a few seconds of saying that.
Click to expand...
Click to collapse
Exactly how long do you have access to fastboot for?
Heisenberg said:
Exactly how long do you have access to fastboot for?
Click to expand...
Click to collapse
About 5 seconds
Hmm, probably not long enough. Will it give a response if you issue this command?
Code:
fastboot oem device-info
Related
closed. solved.
Not solved.
Installed SDK to get drivers, so phone is recognised, running CF auto boot but stays stuck on <waiting for device>
sunil237 said:
Not solved.
Installed SDK to get drivers, so phone is recognised, running CF auto boot but stays stuck on <waiting for device>
Click to expand...
Click to collapse
have you actually put your phone in fastboot mode? this is done by first turning it off, then (i dont have my n5 yet to check) but usually hold the volume up and down keys, and hold the power button... and keep holding... fastboot mode should then fire up
dannstarr said:
have you actually put your phone in fastboot mode? this is done by first turning it off, then (i dont have my n5 yet to check) but usually hold the volume up and down keys, and hold the power button... and keep holding... fastboot mode should then fire up
Click to expand...
Click to collapse
Yep, I'm meant to get instructions on my phone/computer but it doesn't get past waiting for device.
Tried different USB ports and restarting computer.
OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US
If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.
Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.
Hold power button until phone turns off. Turn phone on while holding volume down.
tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.
lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again
Just took the Lollipop OTA update from stock 4.4.2. Upon completion my phone rebooted and is stuck on the LG boot logo. I tried entering download mode (holding volume up button and plugging phone into computer) but my phone doesn't enter it. Attempting to power off the phone doesn't work either, since the phone just powers off for a second and turns back on to the boot logo. I tried factory reset (power + volume down) and after proceeding with the reset the phone is still stuck on boot logo. What should I do?
105108 said:
Attempting to power off the phone doesn't work either, since the phone just powers off for a second and turns back on to the boot logo.
Click to expand...
Click to collapse
You can power off if you hold power button longer. wait till logo appears, and still hold, till it gone away second time, and hold even a little longer.
Turns off but still stuck at logo when turned on
LazyG said:
You can power off if you hold power button longer. wait till logo appears, and still hold, till it gone away second time, and hold even a little longer.
Click to expand...
Click to collapse
I have the same problem with the friend who posted first. There is no way on how to get to fastboot mode and when turned on it just restarts and back to logo. Hard reset is the only thing it allows me to try but no result. Any possible way to get to fastboot or download mode??? Help somebdyy
costas1696 said:
I have the same problem with the friend who posted first. There is no way on how to get to fastboot mode and when turned on it just restarts and back to logo. Hard reset is the only thing it allows me to try but no result. Any possible way to get to fastboot or download mode??? Help somebdyy
Click to expand...
Click to collapse
check these topics http://forum.xda-developers.com/showthread.php?t=2582142 and http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
105108 said:
Just took the Lollipop OTA update from stock 4.4.2. Upon completion my phone rebooted and is stuck on the LG boot logo. I tried entering download mode (holding volume up button and plugging phone into computer) but my phone doesn't enter it. Attempting to power off the phone doesn't work either, since the phone just powers off for a second and turns back on to the boot logo. I tried factory reset (power + volume down) and after proceeding with the reset the phone is still stuck on boot logo. What should I do?
Click to expand...
Click to collapse
After i flashed the Lollipop firmware, it looked like the phone got stuck with LG logo but i gave it good 5 to 6 minutes and all was fine. The phone just needed to breathe a little.
My friend's Pixel won't boot up. It only shows Google Logo for a few seconds and then turns off... I tried going into recovery by holding the Power button and Vol - button and then selecting Recovery Mode, but that doesn't work too. Neither going into Fastboot mode from there. Doing any of these two, will show Google Logo for a few seconds and then turn off... I tried going into Safe Mode too, but that too doesn't work... Is there any other thing I can try?
Note: The phone is most probably not rooted, and the bootloader is still locked. The phone also doesn't have USB Debugging enabled. ADB doesn't recognise the device.
Thanks
I did a huge mistake. I wiped the System and the cash and data on the phone and reboot it, then the phone stuck in google Logo. The problem is I can’t go to Recovery mode because Both up and Down Volume Botton are broken. Is there any way to activate the adb, in this case, to turn the Recovery mode, then flash a new Rom? I tried the adb reboot command, but the phone was not recognized.
please i need Help
I don't know if this will be of help, but turn off your phone completely. Plug a charger, wait till offline-charging animation starts, then try ADB.
I remember I rescued a Galaxy Note3 this way, but it was embraced by Resurrection Remix. So maybe the Kernel allowed ADB .. IDK.
Mohamedkam000 said:
I don't know if this will be of help, but turn off your phone completely. Plug a charger, wait till offline-charging animation starts, then try ADB.
I remember I rescued a Galaxy Note3 this way, but it was embraced by Resurrection Remix. So maybe the Kernel allowed ADB .. IDK.
Click to expand...
Click to collapse
didn't work. device not found
Can you turn off the phone and reboot to recovery or fastboot
LR7875 said:
Can you turn off the phone and reboot to recovery or fastboot
Click to expand...
Click to collapse
no I can't. it is just stuck in the google logo and when I hold the power button to turn it off it reboots to the google logo.
At the instant it reboots, press volume up.
LR7875 said:
At the instant it reboots, press volume up.
Click to expand...
Click to collapse
the main Problem is both Volumes up and Down buttons are Broken so I can't access the recovery/fastboot mod.