Hello guys,
So today I was doing what I usually o with my Galaxy Nexus. Tested the last daily image of Ubuntu Touch, flashed factory images, then CM 10.1 and AK kernel, and started to use the phone.
A few hours later I had to get a file from my phone, connected it to my Ubuntu 13.04 machine and got the files. While I was there, I uploaded a zip to my phone too, but the screen went black and it did not woke up, so I performed a battery pull.
After that, the phone got stuck at Google logo. Sometimes it shows the ROM's boot animation, sometimes it just stays at Google logo. I thought I could have corrupted the file system, so I installed the 4.2.2 factory images again, but I'm still stuck.
Anyone know what could be happening and know how to fix this, please? Thank you in advance
did you flash the entire factory image or just system.img?
Zepius said:
did you flash the entire factory image or just system.img?
Click to expand...
Click to collapse
The entire image, using the flash-all.sh script.
try not using the flash all script and erase all the partitions before you flash them all
fastboot erase boot
fastboot erase system
fastboot erase userdata
*note: this will delete all data on the phone
then fastboot flash each individual img file.
Zepius said:
try not using the flash all script and erase all the partitions before you flash them all
fastboot erase boot
fastboot erase system
fastboot erase userdata
*note: this will delete all data on the phone
then fastboot flash each individual img file.
Click to expand...
Click to collapse
Will do that. Thanks for the advice
R: [Q] Device stuck at Google logo, even after installing factory images
It 'happened to me (not with Ubuntu OS) ... I just flash the stock ROM partition at a time with fastboot (un zip the stock and flash boot, system, data, recovery etc...), erase cache , reboot and thanks the sky
From Gnex with Tapatalk 2
Zepius said:
try not using the flash all script and erase all the partitions before you flash them all
fastboot erase boot
fastboot erase system
fastboot erase userdata
*note: this will delete all data on the phone
then fastboot flash each individual img file.
Click to expand...
Click to collapse
I think the device is gone. I erased the partitions, flashed all the files back and when the "X" boot animation appeared, the screen flickered and the animation froze. Then the phone rebooted and right now, it's still stuck at Google logo. So sometimes it boot to boot animation, sometimes it won't...
Is it really gone?
I guess I will try two more things: flash Ubuntu Touch to see if that works or flash Android 4.1.2. Otherwhise, bye bye Nexus...
Did you resolve the problem?
julian_fern said:
I guess I will try two more things: flash Ubuntu Touch to see if that works or flash Android 4.1.2. Otherwhise, bye bye Nexus...
Click to expand...
Click to collapse
I would like to know if you were able to resolve this issue. I am facing a similar problem and so far I have not been successful. For me, the device doesn't power on unless connected to a power source (in my case I'm using a USB cable) even though the battery is full. So far I have tried reinstalling the Android 4.4.2 factory image but to no avail. The device gets stuck on the 'Google' screen. This is so annoying.
Related
I am not a noob when it comes to android dev, but this has stomped me and I am asking for expert's help. I have a GSM version SGN that I flashed the official yakju ICL53F on it via fastboot. It has been working great for a month now. Suddenly today I felt it was vibrating in my pocket, took it out and discover it was stuck in boot loop--the google sign with the unlocked icon. I waited til I get home to put clockworkmod on it, but when I try to nandroid it first it gave me an error. Then I figure I would just fastboot the stock rom on it again, using fastboot mode like I did before. I even flashed the bootloader, radio, and system image. Still stuck on google icon with screen went blank, vibrate and repeat. Is there anything else I should try? odin mode is also available, but I am not seeing any instructions on it at the developer section so I am reluctuant to try it. I can still adb and fastboot to access my phone...help please?
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
lettcco said:
well I am no noob but I am no expert either. Apparently you cannot
fastboot flash system XXXXstock_image.img, you have to use
fastboot update -w XXXstock_image.img instead.
still I am baffled by why this happened in the first place. I was ready to lock the bootloader back up and send it in for warranty...glad I didn't have to resort to that.
Click to expand...
Click to collapse
I think you are mixing some things up.
The "update" parameter of fastboot is used to flash a group of images inside a zip file to you device.
The "flash" parameter is used to flash a single image to your device.
The following two groups of commands do the same thing:
fastboot update -w image-yakju-icl513f.zip
or
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot erase cache
I seemed to have bricked my device......... the phone just seems to hang on the white HTC screen.. I am very new to all this so please help with even the most basic and obvious steps.
Events that led to this:
Last night i unlocked and rooted my phone using clockwork recovery and then installed superSU. All was fine then.
I installed Nanobackup and took the backup as suggested.
then later today, after reading a lot i decided to try CYANOGENMOD'S root and then it all statred to fall apart.......
the phone never booted after that. first it used to get stuck on CYNOGENMOD's startup screen and it never moved forward. after reading some more I realised that i needed to update the BOOT.IMG file along with it which i missed. after this also nothing was happening.
I was thanking my stars that i took a complete back up and tried to restore it..... but as my luck would have it that also did not work.
Now i am stuck with a white boot up screen with the HTC logo on it. I can still connect to fastboot....... PLease help......Very desparate.
Thanks..... all and any help is appreciated.
flash the boot.img wich came with your rom then "fastboot erase cache" + go to recovery then wipe data + cache + dalvik cache then your good to go
No luck
The5alodi said:
flash the boot.img wich came with your rom then "fastboot erase cache" + go to recovery then wipe data + cache + dalvik cache then your good to go
Click to expand...
Click to collapse
Hi Thanks i tried all this again just to be sure.... but no help.
The command i am using for Fastboot is
Fastboot boot boot.img
This is correct??? Also just to be sure i have the correct boot file should i download the .zip file again.
Also i forgot to add that i installed CM downloader from Google play from there i directly downloaded the CM10 ROM. Is this why there could be a problem?
the correct command is: fastboot flash boot boot.img
Then fastboot erase cache
the command is "fastboot flash boot boot.img" the "fastboot erase cache" get the rom from this site its under original android development pick what ever you want
you will find steps in the rom page if you ddnt understand me
http://forum.xda-developers.com/showthread.php?t=1786696
original cm10
Still not luck
The5alodi said:
the command is "fastboot flash boot boot.img" the "fastboot erase cache" get the rom from this site its under original android development pick what ever you want
you will find steps in the rom page if you ddnt understand me
http://forum.xda-developers.com/showthread.php?t=1786696
original cm10
Click to expand...
Click to collapse
Ok tired this but still no luck. is there is way to tranfer the new downloaded .zip file to the sdcard as this is only option i see left.
anupamdalvi said:
Ok tired this but still no luck. is there is way to tranfer the new downloaded .zip file to the sdcard as this is only option i see left.
Click to expand...
Click to collapse
dude when you download the rom first extract the boot.img and flash it via fastboot + erase cache of course you are in fastboot usb in your one x
then go to recovery >mounts >mount usb storage then transfer the file and flash it by recovery
then erase dalvik cache + wipe data
any Q pm me if i helped click the thanks button
Hello I tried to install a new rom to my tablet today but have had nothing but problems. Here's a list of the events that happened:
1. Unlocked bootloader, rooted and installed TWRP
2. Flashed this rom and Gapps.
3. Rebooted and waited a long period of time at boot animation before powering down
4. Tried re-flashing multiple times with no luck
5. Restored TWRP backup to stock rooted
6. Flashed CWM touch
7. Flashed the same ROM and Gapps
8. Rebooted to the same issue as before
9. Attempted multiple re-flashes to no avail
10. Attempted to mount USB to try a different rom and was unable to mount usb
I don't know what to do next and I'm really worried that I've bricked my new tablet I'm relatively familiar with Android but I'm currently at a loss.
Any help would be greatly appreciated!
Thanks in advance!
You can flash the stock ROM using the appropriate file from here:
https://developers.google.com/android/nexus/images#razor
The flash-all.bat file within also flashes the stock recovery. You can flash TWRP after that, if you'd like.
Flash-all.bat should format things properly. However, for best results, I like using fastboot to do a full wipe before any flashing:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Thanks that seems to have worked!
Nice Job PanDae
Resolution and happy ending detailed in answer below.
I've been running 7.1 since its release. I've had Elemental X as my kernel, with SuperSU as well.
Today, I tried using the adb sideload for the ota.zip to 7.1.1. My computer here at work was refusing to recognize my XL when in recovery via ADB - ADB works just fine when the phone is booted, and fastboot works as well. Tried reinstalling Google drivers, and a different ADB/fastboot setup, and this didn't fix the issue.
Okay, so then I decide I'll try flashing the relevant .img's from the 7.1.1 NMF26O factory image. I flashed bootloader, radio, system, system_other, modem, and boot. I then flashed EX's kernel (elex.Image) instead of using the .zip for TWRP. I then booted the SR3 boot-to-root.img since I do not want to install TWRP at this time.
I got the few typical reboots, and now my phone goes directly to recovery and states "no command." Then the phone reboots itself after about 30 seconds, and keeps on doing this.
I tried re-flashing just the factory image files that I previously mentioned, without flashing EX and without booting the SuperSU img. I am still getting the same problem. I do not want to try a flash-all.bat and erase all my userdata if I don't have to. But I also saw someone else post that they ran into this issue of hitting "no command" on boot, and couldn't even flash the full factory image because it tries to flash recovery.img which is not part of the factory image files - what in the actual ****, why would the .bat try to flash recovery if it isn't there?
Right now I am trying to re-flash 7.1's files to see if I can just get back onto 7.1 with my userdata intact... but if anyone can provide insight on how I ****ed this up (because in my opinion, I did everything right), I'd appreciate it.
Edit: Tried flashing 7.1's files, and same issue... ridiculous. Trying the flash-all.bat and a factory reset now for 7.1.1.
Edit 2: Tried the flash-all.bat, and it successfully flashes bootloader and radio. It tries sending the .zip with the rest of the .img's, and fails because of insufficient space. I formatted userdata and did a factory reset in recovery as well, and am still having this issue... going to try the Unified Toolkit next to see if it can save me. This is bull**** though. Never have I had a Google device go this ballistic and unable to be EASILY recovered with the factory image!
Same thing happened to me. I don't know how I fixed mine, if that makes sense, but do you know what boot slot your on? A or B? Also what command are you using to flash all the images.
Are you doing
Code:
fastboot flash boot boot.img
or (x being the boot slot you are currently in)
Code:
fastboot flash boot_x boot.img
I chose this IMG as example. Nothing particular
I tried both. First was fastboot flash boot.img. Once I started having the recovery issue, I tried fastboot flash boot_a and boot_b with the factory images. I also just tried the flash-all.bat, and after it flashes the bootloader and radio, it says there is not enough space to send over the ~2 GB zip file with the other .img's to be flashed.
Using the Unified Toolkit with the factory image from Google worked. It does not use the flash-all.bat, and flashes each piece of the factory image with its own commands so there was no error relating to lack of storage space. Watching the flash commands go by, it appears my error may have been using "fastboot flash system system.img" because the Toolkit used "fastboot flash system_a system.img". I was using system_b for the system_other.img, but not system_a for system.img. NONE of the articles on the web relating to flashing the factory image for a Pixel/XL said anything about system_a, so they are likely using dated flash methods.
My phone is now alive.
This was also the LEAST PAINFUL factory reset I've ever done. Using the restore from cloud option during setup, and selecting my Pixel XL (last used today), it immediately restored my home screen layout (apps grayed out until downloaded), my texts are all back, and most app data is restored as well IF you allowed them to backup to Drive during your initial setup. I basically lost nothing but my time in doing all of this.
Thanks for sharing this! I will now use this tool from now on. Glad you were able to solve your problem
Hi,
I did try to search this problem but couldn't really find the words I needed to get enough specificity to differentiate it from other problems which weren't mine, so sorry if this post is a duplicate of something else.
My problem is that my 5X 16GB will power off consistently and boot itself up again. It isn't a bootloop because it isn't an instantaneous shut down, but can often stay on for about 2-5 minutes, sometimes staying on for almost an hour. There doesn't really seem to be any pattern or predictable nature to it, as sometimes when the device powers back on the default launcher and 'system' will stop working and the device will just give up, skipping straight to the boot animation and skipping the google logo.
I have tried erasing and formatting all partitions on the device i could get my hands on (namely recovery, cache, system, userdata, and boot), then flashing in the following order:
fastboot flash bootloader bootloader-bullhead-bhz11h.img
fastboot flash radio radio-bullhead-m8994f-2.6.36.2.20.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Sometimes I was able to get the device working for a long time such as two days with the device acting completely normally, and it would only enter its old state when it powered off. I can't really remember what I did to get the device working before, but I'm fairly sure it was something like flashing 6.0.0 (which would behave strangely, with the setup sometimes crashing and the device rebooting) and update the device OTA, which restored it to a state of normality.
Am quite lost right now and very frustrated- this is my second phone, the first being a Oneplus One which is also cocked up :crying:
Thanks for any help
bilboswaggins22 said:
Hi,
I did try to search this problem but couldn't really find the words I needed to get enough specificity to differentiate it from other problems which weren't mine, so sorry if this post is a duplicate of something else.
My problem is that my 5X 16GB will power off consistently and boot itself up again. It isn't a bootloop because it isn't an instantaneous shut down, but can often stay on for about 2-5 minutes, sometimes staying on for almost an hour. There doesn't really seem to be any pattern or predictable nature to it, as sometimes when the device powers back on the default launcher and 'system' will stop working and the device will just give up, skipping straight to the boot animation and skipping the google logo.
I have tried erasing and formatting all partitions on the device i could get my hands on (namely recovery, cache, system, userdata, and boot), then flashing in the following order:
fastboot flash bootloader bootloader-bullhead-bhz11h.img
fastboot flash radio radio-bullhead-m8994f-2.6.36.2.20.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Sometimes I was able to get the device working for a long time such as two days with the device acting completely normally, and it would only enter its old state when it powered off. I can't really remember what I did to get the device working before, but I'm fairly sure it was something like flashing 6.0.0 (which would behave strangely, with the setup sometimes crashing and the device rebooting) and update the device OTA, which restored it to a state of normality.
Am quite lost right now and very frustrated- this is my second phone, the first being a Oneplus One which is also cocked up :crying:
Thanks for any help
Click to expand...
Click to collapse
Request an exchange from LG or Google.
Sent from my Nexus 5X using Tapatalk
HW bootloop begins with random reboots. So bring back to LG right now.
(Flash stock, Lock the bootloader if unlocked etc)