Database Develop

[Q] Stuck in Bootloader

After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?

cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
What happens when u choose reboot in fastboot mode in the bootloader??

cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
Can you reboot into recovery again and enter to fastboot mode?

Can go between fast boot and the Bootloader menu but if I hit reboot, it just comes back to Bootloader. If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.

cknuth said:
If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
Click to expand...
Click to collapse
fastboot erase cache

nkk71 said:
fastboot erase cache
Click to expand...
Click to collapse
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"

cknuth said:
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
Click to expand...
Click to collapse
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)

nkk71 said:
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
Click to expand...
Click to collapse
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB

cknuth said:
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
Click to expand...
Click to collapse
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...

nkk71 said:
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
Click to expand...
Click to collapse
ok so the guide walks me up to the point of installing fastboot for unbuntu using a couple cmd lines but for my specific situation will I need any files saved in specific locations? I have never used Ubuntu or Linux before so youll have to bear with me.

Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.

cknuth said:
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
Click to expand...
Click to collapse
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.

nkk71 said:
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
Click to expand...
Click to collapse
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?

cknuth said:
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
Click to expand...
Click to collapse
doesn't sound like a brick at all, as long a hboot (ie bootloader is fine) no brick should be involved.
but i have to call it a night, hopefully someone will be along shortly, and take over... (timezones ) take it ease, DO NOT PANIC, DO NOT RUSH things!!

Cool, all your help is greatly appreciated. So I should hold off on the trip to the phone store?

Any other ideas to get communication to the phone?

Different Computer, USB Port, and USB Cable. Without saying FASTBOOT USB on the phone, can't do anything.

Help with Nexus 6 possible Brick

Alright I am looking for some help here. I was attempting to unroot to update my Nexus 6 to Android M. Not sure how this happened but here it goes. I can boot the phone into recovery TWRP and into boot loader but the OEM is locked....In recovery I have no backups or ROMs o flash and my mac is not connecting with the Nexus 6. It seems like there is no ROM on the phone at all and I cant use Terminal commands I keep getting Failures. I have run the 1 click root and unroots for mac and still nothing. I also have no access to Developer options since I cant load into a ROM...So I cant select allow OEM unlock... Please let me know if there is anything I can do to fix this. Thanks for your help everyone!

Try to uninstall all drivers then re install to see if mac recognizes your phone then sideload a rom to recovery or adb

Had this before. I believe when connecting to your computer, you have to delete every nexus 6 previous connections so it would be as if your phone never connected to your computer before. Then after you do that, it should install drivers and recognize your phone. I'm not sure if I remember correctly but I believe its from your toolbar on your computer where it normally pops up "eject USB " warnings. Sorry if I couldn't help

Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.

or fastboot wipe user data and cache.

nhizzat said:
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
Click to expand...
Click to collapse
I have been working on this since last night 7pm... I tried adb push and it just sits there and says starting adb sideload for about 10 min then vibrates with a cancellation. I tried removing Android File Transfer and reinstalling it and I still get the can not find device error. Im thinking this might be a loosing battle.

simms22 said:
or fastboot wipe user data and cache.
Click to expand...
Click to collapse
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....

ibaldwin85 said:
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
Click to expand...
Click to collapse
did you have any roms on your phone before all this? if you did, did you try to search if they are in a different location in your storage now?

Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
he has no rom and bootloader locked. nrt cant do anything.

simms22 said:
he has no rom and bootloader locked. nrt cant do anything.
Click to expand...
Click to collapse
But if he has TWRP......he can transfer a ROM from the PC and flash it......

paclaco said:
But if he has TWRP......he can transfer a ROM from the PC and flash it......
Click to expand...
Click to collapse
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"

simms22 said:
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
Click to expand...
Click to collapse
True, but have a Mac, and it is rare that being in recovery and connected to the Mac, do not recognize ....
then wait a Windows computer then ....

FIX! we got it!
Thanks for all the responses guys! We spend another 4 hours on this Sunday and finally got it! We ended up using this forum step by step. http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
While my friend was installing all of the ADB drivers on his PC I attempted the steps on my mac. It made it through the first to lines of code but when rebooting into Boot loader it came back with a fail notice to unlock the OEM.
When he got all drivers installed we used the same lines of code (modifying C: for the location he had the ADB drivers) and it accepted all codes. Seeing that screen change into the OEM unlock select yes screen was a GREAT moment lol. After that we used NRT to flash Marshmallow...
All in all it was fun trying to figure this out! Not so much fun thinking I had to drop another $300 to get a new phone! Again thanks everyone for the help!

BladeRunner said:
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
Click to expand...
Click to collapse
Agreed, but its convenient as all hell.
Sent from my Nexus 6 using Tapatalk

turbo stuck in loop.

my friend has a stock turbo, running latest ota. no root or unlock, stock.
it is stuck in a loop. i can unlock the phone or double tap windows button and multitasker pops up though i cannot interact with anything because this keeps popping up:
"Unfortunately, the process com.android.phone has stopped" sometimes it says another process like com.motorola.process.system
can't factory reset because the photos haven't been backed up.
how can i get it out of this loop so i can run KINGROOT and get a real rom going? thanks :cyclops:

any advice?

Roflcopter_Down said:
any advice?
Click to expand...
Click to collapse
Clear cache from stock recovery. If that doesn't work I would try pulling the files using a PC and factory reset from recovery.
Sent from my XT1254 using Tapatalk

Can't you plug it in still and get the photos off?

mrkhigh said:
Can't you plug it in still and get the photos off?
Click to expand...
Click to collapse
hey, usb storage isnt enabled so when connected to computer, drive doesnt mount. cant get to settings to turn on usb storage. thats what i really need to figure out, i suppose
tried clearing cache

Roflcopter_Down said:
hey, usb storage isnt enabled so when connected to computer, drive doesnt mount. cant get to settings to turn on usb storage. thats what i really need to figure out, i suppose
tried clearing cache
Click to expand...
Click to collapse
I am not positive that a factory reset deletes your pictures.
That said I wouldn't risk it since I am not positive.
You should be able to pull your files via adb/fastboot.
Then after you have copied it all do a factory reset or simply flash a stock ROM.
Edit: from adb
You can try:
Adb pull /sdcard/dcim

mrkhigh said:
I am not positive that a factory reset deletes your pictures.
That said I wouldn't risk it since I am not positive.
You should be able to pull your files via adb/fastboot.
Then after you have copied it all do a factory reset or simply flash a stock ROM.
Edit: from adb
You can try:
Adb pull /sdcard/dcim
Click to expand...
Click to collapse
how do i enable adb/fastboot from stock recovery? its been a couple years since i had an m7. iirc there was an option after you flashed a custom bootloader or something. i dont see the option now in recovery or boot

Fast boot is boot loader mode. But apparently you can't pull from there.
Try booting the device,
Then try plugging it in and typing
Adb devices and see if your device responds
If it does you can simply use the adb pull command
This assumes you have adb installed and ready on your system.
I think it is included with android SDK and there are tutorials out there.
Sent from my DROID RAZR M using XDA Free mobile app

Stuck in Fastboot

Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.

Here's what I'm talking about just in case someone asks

Try installing a stock factory image from fastboot.

runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone

adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.

runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon

Pixel 5 Stuck on boot loop

Hi All,
I'm hoping someone will be able to help as I've spent most of the day chasing my tail it seems.
My 'stock' (non-rooted/non-flashed) Pixel 5 went into a boot loop randomly last night.
I've restarted, I've gone into the recovery mode and have tried to flash an OTA via ADB (which may not sound like much but is an achievement for someone with my limited technical skills), it's getting to 94% and then I'm receiving an error on the cmd prompt saying 'adb: failed to read command: No error' but on the phone itself it says that is was a 'success' status 0.
I've tried the current OTA and the developer version and I'm getting the above issue on both.
I tried copying the 'zip' to a USB stick and have plugged that in using the USB A to USB C dongle that comes with the pixel but I'm receiving an error stating that it cannot be initiated.
Can anyone suggest a possible next step? I have some files that I've realised don't go to my cloud backup and they are important to me so I'd like to if possible not have to wipe the device.
Many thanks.

Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.

l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for taking the time to respond. Everything was downloaded yesterday so is up to date. I re-downloaded just now and checked again and am still getting the same.
(~94%) adb: failed to read command: No error on cmd
Install from ADB completed with status 0 on the phone.
Is there a simple guide on how to flash-all (for someone as not technical as me) that you can point me towards?

Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.

did you try a different cable or usb port? borrow your friend's pc perhaps?

l7777 said:
Are you using the latest ADB from the android SDK?
You can always try the factory image and remove the -w from the flash-all.cmd file.
Click to expand...
Click to collapse
Hi, thanks for this, I'll try another sideload with the April update and attempt it from another laptop, if that still doesn't work then I'll try the flash as you suggest.

swangjang said:
did you try a different cable or usb port? borrow your friend's pc perhaps?
Click to expand...
Click to collapse
I tried a different cable and port but not another laptop. I'll try that next after trying the April update.
Thanks.

tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.

WFHbot said:
Hi, no not yet. I think this will be the last step before I factory reset. Will try another cable, laptop and the April OTA this evening when I have time.
Thanks.
Click to expand...
Click to collapse
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .

The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call

Chad_Petree said:
The same thing happened to me, it must have been the April update, I updated my phone, everything seemed to work and then all of the sudden I was watching a video last night and the phone rebooted itself and kept being stuck in boot, it won't load the os but it keeps restarting itself.
I tried accesing recovery mode but on the bootloader screen it won't let me use the volume keys to start the phone in recovery mode or to try and hard reset it, while on the bootloader screen it resets itself... :/ I'll give google a call
Click to expand...
Click to collapse
That sucks. Hopefully they'll be able to do something more than just a factory reset.
I've tried sideloading the April update and that also failed at 94%. Will try another laptop in a while and see if that works, then try the flash as suggested above, if not then it's a factory reset for me.

ProjectAlly said:
Also a note on trying to use the web flash utility. Make sure to look at the advanced options on the installation page, it gives you an option to flash the latest update without wiping your device at all.
That could help in getting the phone running again so you can recover your important files, before deciding to do a compete wipe, if that's what you have planned.
Just look around the settings carefully before flashing and everything should go well .
Click to expand...
Click to collapse
Thanks, will have a look around and see what I can work out. It's looking like I'll have to go this route...
DO I need to unlock the bootloader do do this flash?

tinhsoftware said:
Have you try to flash your new firmware on the web? Go to web https://developers.google.com/android/images. Click on Flash and follow instructions.
Click to expand...
Click to collapse
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?

WFHbot said:
Thanks, will have a look and see if this works.
DO I need to unlock the bootloader do do this flash? If so, would this wipe the device?
Click to expand...
Click to collapse
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip

l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Thanks, I tried that. Edited the file and tried running the flash-all.bat file but it's giving me an error:
Setting current slot to 'b' FAILED (remote: 'Fastboot command (set_active: ) is not allowed when locked')
fastboot: error: Command failed
Not sure what I'm doing wrong. Am I missing a step? Should the phone be on a certain menu when running the bat file?

l7777 said:
You do not need to bootloader unlock to use official firmware. You've been trying to do an OTA update, you can try the factory images above. Use the "link" to get a download, unzip, edit the flash-all.bat file, remove the -w from the fastboot flash update line.
Code:
fastboot -w update image-redfin-rq2a.210405.005.zip
Code:
fastboot update image-redfin-rq2a.210405.005.zip
Click to expand...
Click to collapse
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.

bobby janow said:
Is that a fact? I haven't had a bl unlock for many years now but I thought I could only do an OTA flash from fastboot with a locked bootloader. I know I can factory reset but other than that .. So if I loaded the beta 12 I could go back and flash a factory image? I would certainly flip the OEM switch first just in case.
Click to expand...
Click to collapse
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?

l7777 said:
That's a good question. I assumed it was possible otherwise why have a factory image available. The consensus seems to be mixed though.
OP: I just did an update from January to April and yes I also got the error at 94% from ADB but the phone reported status 0. Booted up no problem. Have you tried booting into safe mode? Is USB Debugging on? Can you get a logcat of the attempted boot?
Click to expand...
Click to collapse
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.

WFHbot said:
Hi,
I've tried booting into safe mode by keeping the volume down button pressed but no luck.
I'm pretty sure that the USB debugging is enabled, but not 100% certain.
How would I go about getting logcat of the attempted boot?
Thanks for all the help thus far.
Click to expand...
Click to collapse
You'll have to factory reset in recovery. I had something similar happen yesterday morning. The reboot was done by me on the way to work though. A factory reset fixed it. Of course all user data was wiped, but Google backups did a good job of restoring almost everything I wanted restored (except for apps not on the G Play Store of course). You'll need to sign into everything again, but most things won't be lost including root.