I tried to flash the Android L Developer Preview(http://developer.android.com/preview/setup-sdk.html) onto my Nexus 5 (no custom ROM or bootloader) following the steps at https://developers.google.com/android/nexus/images. When using flash-all.bat, I ALWAYS get stuck on
erasing 'cache'...
The only thing I can do is reboot the phone by holding down the power button until it is off. Then when I boot again I see the Google logo followed by the green Droid which probably means recovery mode. Sometimes under the Droid there is a blue progress bar, just like the one that comes up when updating, but it does not show a progress but rather just indicates action. When the Droid is up I also cannot reach the phone with fastboot or adb.
I also tried reverting back to Andrid 4.4.4, but I get the same error. Nobody else seems to have this problem, they all erase their cache in a matter of seconds and then format it.
It would be really cool if anybody could help me with either reverting to Android 4.4.4 or successfully flashing Android L.
Benedikt
Is your phone with unlocked bootloader? If no, type in console:
fastboot oem unlock
After that you should to enter in bootloader, open shell and write:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Start "flash-all" script again and enjoy your Nexus.
Related
I really hope somebody can help me with this.
I have xperia z5 premium, power button stopped working a month ago or something, but the phone was working perfectly fine. Of course, I made a mistake and did not charge it in time and it turned off. Now I can't get it to turn back on because the button is not working.
I explored all my options and I realized I can do fastboot reboot through fastboot and adb. However, I can't seem to get my phone to go into fastboot mode.
I hold volume up button (which I know for a fact is working), I plugin usb, and instead of getting that blue led light everybody keeps talking about, I just get a red led and then a green one after the sony logo that signals the phone is charging.
I installed ADB and xperia z5 premium drivers and I still can't get it to work. When I type fastboot reboot it says when I try adb reboot or adb reboot bootloader it says "error: device not found".
I've also installed xperia companion app and when I plugin my phone it shows a screen where it says: "Your device is locked
Unlock require
Unlock the device using password or fingerpint if needed
Allow data access
On your device, select the option to allow data access"
I've tried doing the same thing with adb on two different pcs, always get the same result. Phone just gets to charging screen and keeps charging instead of going into any mode.
I also tried holding volume down button and plugging in usb which is supposed to be recovery mode or something, but that doesnt work either, I also get charging screen. And I'm 100% sure both my volume up and volume down buttons are working.
What am I doing wrong?
P.S - Debugging mode is not on, im 100% sure since i never turned it on.
Somebody please help!
Thanks!
try downloading the sony xperia flashtool and boot your device in fastboot mode by holding down the volume down button and inserting the usb cable a blue light should appear, open up the flash tool and wait for the device to be detected if not detected, goto c drive then inside the flashtool folder there should be a folder named drivers, open it up then install the drivers for your device. back to the flashtool... when your device is detected, click on the lightning bolt icon and select fast boot mode, then you should see a window pop up and click reboot device into system.
hope this solves your problem
Google glass 2 stuck on the "Glass" screen, I tried restarting it, but it shows the logo and nothing changes.
I tried to make a factory reset - holding the camera button, clicking on the power button, and continue holding the camera button. I show me the recovery screen with options, but nothing is selectable, clicking on camera button won't let me select or click anything.
Is there any way to make a full factory reset to fix this "Glass" screen issue to make it working again?
As i am not allowed to put a comment i give you following answer....
Have you tried to do a factory reset with ADB as described here:
How can I do factory reset using adb in android?
How to factory reset android using adb
This is the factory reset commands with adb in your command line:
adb reboot bootloader //device will restart
fastboot devices //this will print a device code if it worked right
fastboot erase userdata
fastboot erase cache
Then manually reboot device. You'll need adb and fastboot.
If that doesn't fix the problem, and you don't care about keeping a warranty intact, you can re-flash the firmware. If you care about a warranty... use the warranty.
The firmware is available for the Explorer Edition here, if it's Enterprise E2 it'll be here. Enterprise E1 firmware isn't available freely as far as I know, so if it's EE1 you're out of luck.
The firmware files come with a text file which contains the adb commands you need to run. Run them all in the order they're written. The final one will restart your device. Voila. Clean slate.
If it still doesn't work after that, it's a hardware problem.
I had rooted my Yu Yureka plus by unlocking the bootloader using adb fastboot method, then flashing the TWRP recovery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that.
But while playing a game the phone automatically rebooted and ever since have been stuck on "Preparing to start.. Starting apps.."
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls, but can't access anything
Any suggestions what I should do now?
I have tried doing a factory reset from recovery but the problem persists and none of the hardware buttons are working, had to remove battery to access the recovery (still cyanogen recovery is opening).
Please HELP!
you can us this tutorial to get back to stock rom
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Last week, while updating my phone, something went wrong resulting in my phone not booting properly. When turning on the phone it got stuck on the OPO logo. Thus, I first tried to wipe cache, didn't work. Then I tried something else and accidentally deleted the "system" data. I was now looking for a way to put the OS back on my phone with terminal (I work on Mac). The problem is that my computer doesn't detect my phone (when typing "adb devices"), and I think it is because the ADB-debugging box in the developer tools isn't checked on my phone. The problem is that I cannot check that box because I can't boot my system.
Who has a suggesting for what to do?
Thanks in advance,
Gijs
There is a thing like ADB called Fastboot mode. Look up how to boot your oneplus into fastboot mode (it's just a key combo) and then you can do things that you could on ADB with fastboot like loading a new ROM.
I have (or rather had :( ) a Glass running the XE8 version of software. It did not receive any automatic updates since it was rooted (as expected).
I tried to update it to XE12 using the system image from https://developers.google.com/glass/tools-downloads/system, and now it won't boot.
I can see the screen light up for a moment when it tries to boot, but the Glass logo does not come up. Instead, it just reboots itself over and over. Sometimes the screen flashes white instead of the usual reddish-gray.
I can still boot to bootloader using the hardware method. I have tried flashing XE11 but the result is the same.
I have a couple of questions that I think could be related to the problem:
1) There is a note on the system image download page regarding a "firmware change" in XE10 that prevents installation of earlier system versions (which includes XE8). Could that be my problem? Does that refer to low-level firmware change? How is that update applied when using the OTA update mechanism and can I apply it manually?
2) There is a relatively large userdata.img file in the system image .zip, however it does not get flashed using the fastboot update method:
fastboot -w update glass_1-img-947604.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 0.5
Baseband Version.....:
Serial Number........: [device serial]
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot' (4528 KB)...
OKAY [ 0.208s]
writing 'boot'...
OKAY [ 1.670s]
sending 'recovery' (5334 KB)...
OKAY [ 0.243s]
writing 'recovery'...
OKAY [ 1.797s]
sending 'system' (485525 KB)...
OKAY [ 21.414s]
writing 'system'...
OKAY [ 64.458s]
erasing 'userdata'...
OKAY [145.384s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.002s]
erasing 'cache'...
OKAY [102.827s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.002s]
rebooting...
If I try to flash userdata.img explicitly I get the following error:
fastboot flash userdata userdata.img
sending 'userdata' (137046 KB)...
OKAY [ 6.049s]
writing 'userdata'...
FAILED (remote: : Sparsed Write)
Is the userdata image supposed to be written to the device?
3) Is there any way of getting the boot log using fastboot to determine what causes the crash?
Thanks.
UDPATE: I have flashed the XE8 image back and now the Glass is stuck on the empty battery screen despite being plugged in for a couple of hours. However I have had charging issues with this unit before, hopefully it gets resolved overnight.
UPDATE #2: Having been left to charge overnight the device was displaying the empty battery icon with a question mark when I got back to it in the morning, however after forced reboot it seems to have booted up fine into the old XE8 system. My next step will be to restore it to unrooted state and attempt to update it using the OTA update mechanism.
I have managed to get the update working.
If you are still running a pre-XE10 system, chances are that straight reflashing of the system image to a post-XE10 version is not going to work. My best guess is that it has something to do with lower level firmware that cannot be updated simply through flashing the boot/system partition.
So if you have a rooted pre-XE10 Glass, the way to get it to update to XE12 or later is to restore it to unrooted state by flashing the boot.img from an unrooted system image.
If you have already flashed a post-XE10 version and the device won't boot, make it boot to the bootloader using the hardware method as described here: Having issues seeing GLASS in Fastboot
and flash the whole system image of a pre-XE10 version.
The links to old pre-X10 images are no longer available on the Glass developers page, however the files are still there and can be located with a bit of googling.
I am not sure that restoring the oem lock after flashing the unrooted boot partition image is required, but I did that just in case:
fastboot oem lock
Reboot the Glass afterwards and it should be able to auto-update to the latest XE version. The check for updates can be triggered by plugging the USB cable in.
When the update is complete, just repeat the original rooting steps if you need it rooted.