Hi All,
I'm usually not one to post unless I have completely exhausted my google-fu.. My shiny new nexus 5x is stuck in a bootloop.
Cause:
Depleted battery to zero (I was mortified). Plugged it in, and after a few minutes attempted to turn it on. Black and white Google logo shows up, then the 4 dancing coloured balls. Then the balls persisted indefinitely.
Situation:
The phone is completely stock. No custom roms. No custom boot loaders. No developer mode by pressing version number 7 times. No USB debug mode setup to recognize my laptop.
Can access Fastboot screen. Can access Recovery mode. Can access Download Mode.
Google SDK tools installed.
Cannot access adb.
LG Mobile unified drivers for nexus 5x installed.
Phone never shows up under Portable devices in Device manager.
Phone shows up in Other devices in device manager when in recovery mode sideload screen.
Boot looping to 4 dancing balls indefinitely.
Tried:
Clearing cache from recovery mode. No effect.
Wiping to factory default from recovery mode. No effect. (I suppose I can always take more photos)
# adb devices --> no devices listed
# fastboot oem unlock --> FAILED (remote: oem unlock is not allowed)
# fastboot -w update image-bullhead-mdb08l.zip --> FAILED (remote: oem unlock is not allowed)
Can someone with more skill than I provide a solution?
Cheers
bump
Perhaps it is reencrypting the data partition. If so, it could take a long while. Change it completely then turn it on and let it sit for an hour or so.
Sent from my Nexus 5X using Tapatalk
If all else fails, download nexus root toolkit install the driver if needed and let it download all dependencies and files.. Get into fastboot mode and plug it in. Select your model, android version and select soft bricked/bootloop. (Unlock boktloader first of course, from what I've heard do not relock it after) then click on flash stock + unroot. Should fix you issue.
Edit: merely a suggestion for easy fix, you can always use flash all.bat from the downloaded factory image or flash each image separately.
Related
Hi everyone,
thanks for taking a look at this. I bought a Nexus used and I have spent hours trying to root it. I was able to successfully unlock it a few months ago but I cannot root it.
I boot into flashboot mode using the adb command:
adb reboot bootloader
then flash the recovery:
C:\nexus> fastboot flash recovery cwm.img
sending 'recovery' <6272 KB>...
OKAY [ 0.828s]
writing 'recovery'...
OKAY [ 0.953s]
finished. total time: 1.781s
I have SU in the root directory of the SD card. After flashing the recovery i volume down to recovery and select it. The black Google screen comes up with an unlocked padlock and that is as far as I can get. It will sit on that screen for days if I let it. I've tried other, similar methods as well and get the same result. What should I try now? I've re-installed the drivers several times but that does not seem to help. I have tried this process on my XP laptop and win 7 laptop.
Also, when i try to do a factory data reset on the phone in the system settings it does the same thing.
Also another strange note... when I follow the instructions and hold the vol up and down buttons to get into fastboot mode it does not work. I have to hold only the vol up botton and power button. I do not know if that is relevant but i'm putting it out there just in case.
Any help would be very much appreciated and rewarded!
Are u able to get beyond the screen of Google the if not theb download the nexus factory images Google it out and download and extract and put it in SDK folder where all the adb and fastboot are present the go into fastboot mode and unlock ur boot loader by fastboot oem unlock by opening up a cmd by shift and right click and open cmd here then fastboot reboot boot loader and search for nexus 4 tool by mskip on Google or xda and follow the thread and follow the toolkit to root ur phone
Sent from my XT910 using xda premium
Mohhamad,
I can get past the black Google screen if I just boot up normally.
I have the Toolkit from skip and have tried that process as well. It worked for unlocking but not rooting. I will attempt it again now and see how it goes. Thanks for you suggestion i will update this shortly.
So i tried to boot to my cwm.img file using the toolkit. It put my phone into fastboot mode, installed the image and now my phone is on the black Google screen with 'fastboot status - okay' at the bottom of the screen. I heard the phone disconnect from my PC but it does not reconnect and stays stuck on this screen until i pull the battery.
Relock and then unlock
fastboot oem lock
fastboot oem unlock
make sure you have the right recovery for your phone. You might also have a corrupted recovery partition.
I would try to flash a stock rom so it can put everything back to stock (including stock recovery) then try again.
I've noticed I can not get into Fastboot mode either with UP+DOWN+Power. I can do UP+Power for recovery, thats it. Might be a 4.3 thing.
I locked and then unlocked it, rebooted, and the phone is back to stock. Not sure how that happened... or maybe that was supposed to happen. I tried to to a factory wipe just to see what it would do, sits on the black google screen with the padlock. I think you are right about my recovery partition being corrupted. I am going to see if I can flash a stock ROM like you suggested. Thank you for your help so far!
http://www.wugfresh.com/nrt/ try this and tell me if it helps
Sent from my XT910 using xda premium
Tried it Mohhamad... it's not making any difference. I tried to flash a stock ROM using wugfresh but i get failure to write errors.
I have also tried to go into download mode and see if I could get ODIN to work. Hold the volume down and power button does not work. I'm at a loss I have no idea what to do now. Any other suggestions? What method can I use to flash a stock ROM?
So a couple nights ago everything was working just fine. Locked my Nexus 7 and went to sleep. The next morning I try to unlock it, but I just have a completely black screen. No backlight or anything. I force shut it off and try turning it back on. It gives me the TWRP loading screen and freezes there (I'm rooted with custom recovery but no custom rom). It does this twice, then booting gives me nothing. No Google logo, no boot animation, nothing. I boot into the bootloader and figure I'll re-flash my recovery and see if I can get to that. No commands will send via fastboot. I'm able to execute "fastboot reboot-bootloader", but nothing else works.
Now I'm familiar with switching USB ports and USB cables, but even after using two different cables (Nexus 7 2013 and Nexus 4) and about 6 different USB ports (both USB 3, and USB 2), nothing. I can't send a new recovery, new bootloader or anything.
So I figure I'll try re-locking the bootloader and then unlocking so it'll hopefully do a factory reset and might help. Well locking worked fine, however when I run "fastboot oem unlock" it brings me to the confirmation screen. I'm able to press the up volume button and press the power button to confirm, but after this it freezes and I have to do another force restart. I've reinstalled the USB drivers, reinstalled the Android SDK, and tried it on a different computer with no Android drivers at all. I've installed the offical Google USB drivers, used the Nexus Root Toolkit to install them, and used PDAnet to install drivers.
It's driving me crazy. It was literally working perfectly the night before, and the next morning it's like there's some catastrophic damage to the device.
Does anyone have any experience with this sort of extreme scenario?
Any help at all would be appreciated! Thank you!
Have you downloaded the factory Google image, then boot to the bootloader, and use fastboot commands to completely erase and reflash the stock image?
- Sent from my Galaxy S3
RMarkwald said:
Have you downloaded the factory Google image, then boot to the bootloader, and use fastboot commands to completely erase and reflash the stock image?
- Sent from my Galaxy S3
Click to expand...
Click to collapse
I was able to erase the boot image, recovery, user data, ect.. because I read to do that if you have intentions to reflash the factory images. However, this was still after my problem of not being able to unlock the bootloader. I think I may be able to flash the factory images if it weren't for the fact that every time I try to unlock the bootloader it freezes completely.
Did you let the tablet reboot after running "fastboot oem lock"?
---------- Post added at 02:46 PM ---------- Previous post was at 02:38 PM ----------
Did you flash the factory images after erasing them? After you run "fastboot oem lock", the device will reboot, but if you erased everything and didn't flash the images, nothing is there to boot to.
Download the Nexus 7 JSS15R OEM image.
Extract the compressed file to the folder where your fastboot.exe lives. Typically this is the platform-tools directory in the SDK.
Open a command prompt window where your fastboot.exe lives.
Type in the following commands and press enter after each one.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader razor-jss15r/bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update razor-jss15r/image-razor-jss15r.zip
Wait for the image to flash. The tablet will automatically reboot, let it do so. Once done, rush through initial device setup, don't worry about Google credentials right now or anything. Once to the homescreen, reboot back into fastboot to run:
Code:
fastboot oem unlock
Then let the tablet reboot.
THESE INSTRUCTIONS ARE ASSUMING THIS IS THE WIFI VERSION ONLY. THEY'LL WORK FOR THE LTE, JUST REPLACE FOLDER AND FILE NAMES AS NEEDED.
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED <remote: flash write failure>
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
Cheers
Mattia
Did you update to the latest sdk tools? I think fastboot has been updated. Also, make sure you are using a good cable in a good port. I had trouble flashing with a USB 3.0 cable in a USB 3.0 port. It worked in a USB 2.0 port just fine.
I suspect your device is in a dirty state- it wants to wipe data to unlock the bootloader, but it didn't complete, so it is unwiped, but still considered encrypted. Maybe try flashing the stock system using fastboot -w update some-update.zip. The update zip is inside the factory image- you'll need to untar it. This is a destructive flash and will erase your data! If it works, let the system boot up since it will take a while to encrypt so that it is in a sane state.
I think download mode is for factory programming. I've been there a few too many times already, and I think it is vol up and power. It'll tell you not to disconnect the cable and the percentage bar will be stuck at 1%. I'll let you guess on how to get out of it.
Make sure you update android sdk like ^ he said, I spent 3 hours trying to get back to stock and trying to figure why fastboot system image wasn't workking -_-
HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks
Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img
Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072
Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.
i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.
I was attempting to update my unlocked and rooted phone to 9.0. Did the usual process of extracting the factory image and removing the -w from the flash all script.
Used fastboot to attempt to flash the update and it seemed to succeed. I then attempted to reboot the device, but it began to bootloop many times just after the G logo appeared. I shut down the device and when I turned it back on it went to the bootloader screen.
Now when I tell it to start it simply returns to the bootloader screen. Fastboot and adb do not detect any devices. If i send it to recovery and attempt to perform a factory reset it says it goes through, but after rebooting it then returns to the bootloader screen. It also says my device state is still unlocked, which seems like it shouldn't be the case after a successful reset.
Any help would be greatly appreciated
I think that you should try reinstall your adb and fastboot drivers and use deuce script. You can try also small things like changing USB slot or rebooting your computer. Hope that I will help you.
gerrard8pool said:
I was attempting to update my unlocked and rooted phone to 9.0. Did the usual process of extracting the factory image and removing the -w from the flash all script.
Used fastboot to attempt to flash the update and it seemed to succeed. I then attempted to reboot the device, but it began to bootloop many times just after the G logo appeared. I shut down the device and when I turned it back on it went to the bootloader screen.
Now when I tell it to start it simply returns to the bootloader screen. Fastboot and adb do not detect any devices. If i send it to recovery and attempt to perform a factory reset it says it goes through, but after rebooting it then returns to the bootloader screen. It also says my device state is still unlocked, which seems like it shouldn't be the case after a successful reset.
Any help would be greatly appreciated
Click to expand...
Click to collapse
First, reset won't change lock state which is good.
Power it off then hold power and volume down. That will get you to fastboot mode. Since you already reset it put the -w back in and flash it again.
TonikJDK said:
First, reset won't change lock state which is good.
Power it off then hold power and volume down. That will get you to fastboot mode. Since you already reset it put the -w back in and flash it again.
Click to expand...
Click to collapse
My device isn't showing up in fastboot or adb so I'm not able to send it any commands. I've tried different computers and ports.
gerrard8pool said:
My device isn't showing up in fastboot or adb so I'm not able to send it any commands. I've tried different computers and ports.
Click to expand...
Click to collapse
Resolved. I was eventually able to access fastboot via the skipsoft toolkit. Unfortunately, still not certain what caused the initial issue.