EDIT: Fixed by holding volume down (only) like lucastracq mentioned before I put the charger in. All I had to do to fix the booting issue was to flash magisk uninstaller from this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I've been using lineage 14.1 for a few months with no issues. Recently I decided to install magisk and magisk manager. Within magisk manager it said there was an update available. I clicked to update, it asked me to reboot and I did so (actually a bit later I closed the prompt at first).
When the phone attempted to reboot it got stuck at "warning bootloader unlocked". I couldn't turn the phone off or go into fastboot. I just had to let the phone slowly drain its battery. Then when I charged it the next day the same thing happened only this time it was the regular "powered by android" boot screen and not the "warning bootloader unlocked". I still can't access fastboot and I can't turn the phone off. Every time I put the charger in it automatically tries to boot up.
Pretty sure I had 3.2.3-0 twrp but I guess that doesn't matter if I cant get into fastboot.
I also tried ADB but I cant find the phone through USB (debugging was on before the incident)
Any ideas of what I can do here? I tried searching around but I haven't found any results of anyone unable to access fastboot
just to be sure, did you try holding the volume down key when connecting it to power cable?
lucastracq said:
just to be sure, did you try holding the volume down key when connecting it to power cable?
Click to expand...
Click to collapse
For some reason this thought never crossed my mind, I was always trying both power and volume down. This worked, thanks!
Bevv said:
For some reason this thought never crossed my mind, I was always trying both power and volume down. This worked, thanks!
Click to expand...
Click to collapse
no problem.
Related
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
I recently broke the screen and the touchscreen of my OPO and bought a new Glass+LCD+Digitizer+Middle Frame from Aliexpress. I just installed all the parts and afterwards my OPO booted happily into recovery. Touchscreen and Display etc are working fine. I wiped everything via TWRP 2.8.7.0 and wanted to do a clean install of CM12.1. But no matter what I do now, the phone always(!) boots directly into recovery mode. I can't even get into fastboot! I already tried all sorts of things.. any ideas?
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
use this url
If I power off my phone and plug it into the computer it immediately turns on. If I leave it plugged in and then shut it off via recovery, it reboots instead of turning off. Only if I unplug it from the computer, I can shut it off. So I'm afraid this link won't work for me
Bannix said:
If I power off my phone and plug it into the computer it immediately turns on. If I leave it plugged in and then shut it off via recovery, it reboots instead of turning off. Only if I unplug it from the computer, I can shut it off. So I'm afraid this link won't work for me
Click to expand...
Click to collapse
did you press and hold volume up when plugging it to the computer?
Yes I tried everything. It will only boot in recovery.
brah it will work. i was in same situation. it fixed my phone. try it.
I managed to do the whole "unbrick" process... now my recovery looks a little bit different but I still can't get into the bootloader!
When I boot up the phone, a split second before it enters recovery mode this picture shows up. The recovery is now stock CM recovery. ADB now doesn't work either..
TWRP has an option to reboot to bootloader. Did you try that as well?
Yes, I did. It booted into recovery...
Bannix said:
Yes, I did. It booted into recovery...
Click to expand...
Click to collapse
When you connect your phone to your PC while it's in recovery does it show up as a drive?
Heisenberg said:
When you connect your phone to your PC while it's in recovery does it show up as a drive?
Click to expand...
Click to collapse
No, it doesn't. However if go into the "install update via adb sideload" option in the recovery, the phone gets recognized as A0001, but the driver on my PC doesn't work. ADB doesn't work either in this case.
deletedpost
I did it with color OS, and now the phone always boots into ColorOS recovery I replaced the ColorOS recovery.img with the TWRP one, and now i got TWRP and ADB back. Phone gets recognized as SD Card now. Could it be that something on the hardware side of things broke my bootloader?
Please help
Bannix said:
I did it with color OS, and now the phone always boots into ColorOS recovery I replaced the ColorOS recovery.img with the TWRP one, and now i got TWRP and ADB back. Phone gets recognized as SD Card now. Could it be that something on the hardware side of things broke my bootloader?
Click to expand...
Click to collapse
I got exactly the same now , let me know what worked for you?
Bannix said:
I did it with color OS, and now the phone always boots into ColorOS recovery I replaced the ColorOS recovery.img with the TWRP one, and now i got TWRP and ADB back. Phone gets recognized as SD Card now. Could it be that something on the hardware side of things broke my bootloader?
Click to expand...
Click to collapse
Well its possible, that one of the volume butten is pressed permanent(that u even don't take notice) due bad hardware and replacement. Therefore, the device would only boot into recovery, no matter what u try. Take a voltmeter and check the buttons.
BTW: stop using these dirty "toolbox" around here, they are pure cancer for your device
Hey, thanks for your reply. The volume down button being permanently pressed was actually the case! I found out myself and fixed it by soldering a new volume flex cable. Phone works fine again
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Pra7ul said:
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Click to expand...
Click to collapse
adb reboot bootloader
waterdaan said:
adb reboot bootloader
Click to expand...
Click to collapse
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Pra7ul said:
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Click to expand...
Click to collapse
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
noahvt said:
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
Click to expand...
Click to collapse
Even If my volume button dosent work then why wont it enter bootloader via advance reboot it just restarts to system after selecting reboot to bootloader,so i should hard brick my device once again, P.S. i have done that twice before though.
Hey, i have a really big problem. My Friend has a Razer Phone 1 and had magisk install on it. He did not want it anymore so he could use his online banking app. He opend the magisk app and clicked deinstall. Than it booted to TWRP and he restarted it. It was still booting to TWRP. So he startet the bootloader and did a factory reset. But now it's not doing anything. It just sits there in there on the splash screen. It's not saying anything about it that it has a unlocked bootloader. He did not lock the bootloader. I have downloaded the newest version from razer but i cannot use it because i cant go to the bootloader anymore. I tried to restart it but with no luck. Has anybody an idea on what can i try? He realy needs his phone.
Thanks.
Just ruling out some fundamental issues, did you plug in a USB cable to connect your Razer Phone to your computer (if you did, try another USB cable and/or another computer/even connect to another phone), Power Off the Phone, then turn it on and immediately press and hold the Volume Down button for Download Mode (or hold the Volume Up button for Recovery Mode).
EDIT: btw, opposite from what your friend did, I have Magisk installed so I can use banking apps. not sure why he wants to remove it.
OeTeJuNiOr said:
It just sits there in there on the splash screen. It's not saying anything about it that it has a unlocked bootloader. He did not lock the bootloader. I have downloaded the newest version from razer but i cannot use it because i cant go to the bootloader anymore.
Click to expand...
Click to collapse
Hold down Vol Down and Power until you can manage your way back into Fastboot/Bootloader mode and reflash everything from the system images provided by Razer.
At some point you should be able to interrupt the bootloop to be able to get the Vol Down button being held down recognized that the phone should go to Fastboot.
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.