Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!
mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger
Related
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
t1j said:
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
Click to expand...
Click to collapse
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
In the end, I just flash a different rom, specially Candy5 as found here: http://forum.xda-developers.com/htc-one-s/development/rom-t2964931 and it worked.
It's possible I accidentally flashed a rom that was incompatible with my device, not sure.
EDIT: I also switched from CWM to TWRP. Not sure if that helped.
t1j said:
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
Click to expand...
Click to collapse
I have broken volume down button, what can i do? face the same problem
What does it mean by manually flash boot.img? After flashing a custom rom, do not reboot first but flash the boot.img via twrp which can be found in zip for the rom?
I don't think it's the "boot loop" problem. My issue is that when I hold the power button, the google logo comes up, but just stays there indefinitely. From there, holding the power button again will turn it off, but then back to the google logo. I can get into the fastboot menu by holding the vol-down button on the restart, and here's what the fastboot mode options do:
start - boots and freezes at the google logo
restart bootloader - turns off then returns to fastboot mode
recovery mode - screen turns dark, but still on, in which case I can't do anything but hold the power button
power off - turns the phone off
I cannot figure this problem out. I have read many forums and none seem to help. The phone is completely stock and the bootloader is not unlocked. I did not update anything right before this issue, nor have I ever unlocked the bootloader or flashed anything else etc. If it is not possible to get this phone to work again, I would at least like to be able to recover the data on it. I am hoping this is possible. When the phone is in fastboot mode, and I plug it into my windows computer, the device shows up in devices and printers, but I cannot get the files from windows explorer. If there is any other information I can provide, please ask. Thank you all so much.
When you're in recovery mode does anything happen when you simultaneously press and release the power and vol up buttons?
Sent from my [device_name] using XDA-Developers Legacy app
When I pressed recovery mode and it goes to the dark screen, I pressed vol up and power at the same time and nothing happened; it stayed on the dark screen. This dark screen is not off, the screen is still on but it is black.
I'm not sure what to tell you. I was hoping that even though the screen was dark you'd be able to get into recovery. If you can get into recovery it might be possible to use adb to pull files. But you'd need usb debugging enabled and even then it's a pita.
Sent from my [device_name] using XDA-Developers Legacy app
Even if there is no way to get the phone working again, is there any way of recovering the data? Can I plug it into my linux machine perhaps and rip the data that way?
I'm not very familiar with linux so I'm not sure. But you'd have to have USB debugging enabled and in recovery. You can't from the bootloader. But since it appears you can get into the bootloader, before I'd give up I'd try flashing the system and boot images from the factory image with fastboot. And then cache and vendor images.
Sent from my [device_name] using XDA-Developers Legacy app
I'm having the exact same problem though I can access ROM. Screen stays dark when I enter recovery mode. Rebooting to recovery from ROM shows google splash screen and immediately goes into fastboot mode. What's worse for me is that USB port is damaged, so I cannot access fastboot or adb
When I try to flash the images, it tells me it fails because it's not supported in locked devices. I suspect it is because I have not ever unlocked the bootloader. However, doing so wipes the data, correct? Is it time to give up on the local data?
forgetswift said:
When I try to flash the images, it tells me it fails because it's not supported in locked devices. I suspect it is because I have not ever unlocked the bootloader. However, doing so wipes the data, correct? Is it time to give up on the local data?
Click to expand...
Click to collapse
Did you enable developer options in settings and then enable oem unlock? You need to do that before you can unlock the bootloader. And, yes, unlocking the bootloader does for the device.
Sent from my [device_name] using XDA-Developers Legacy app
Okay, I have given up on the data on the device, now I just want it to work. I used the command "fastboot oem unlock" which took me to the "are you sure" screen on the phone, and when I said yes, it goes to the fastboot page and says "erasing..." on the bottom but gets stuck there. Anything I can do?
How long does it say "erasing data" after selecting "Yes" to unlock the bootloader? It should not take more than 15 minutes.
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.
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not