Develop Bugs

[Q] Is my phone brick? stuck on google boot image

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

[Q] Device stuck at Google logo, even after installing factory images

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.

Unfixable Google Loop - So frustrated

I bought my Nexus 7 2013 shortly after they were available and it was a good device until the release of KitKat. After the KitKat OTA it's been a piece of junk.
After the KitKat OTA it developed a problem where the tablet was on but the touchscreen was unresponsive. The only way to fix it was to shut it down by holding the power button. Eventually it started being stubborn and I'd have to power cycle it several times before it would clear the Google screen. That gradually progressed to having to do a system reset before it would come back to life.
On December 15th it finally refused to go past the Google splash. Attempting to boot into recovery also left you stuck at the Google logo. At the time I tried the WUGFresh tools to do a stock recovery and while I was successful in unlocking no amount of flashing / formatting / erasing would give you a normal boot or a recovery screen.
I sent it off to ASUS on 12/17 and got it back this past Monday (1/13). It worked fine until Tuesday night when once again the screen was unresponsive and I had to shut it down by holding the power button. It's now stuck at the Google screen and no amount of flashing / formatting / erasing using FreshWug or fastboot directly via command line has brought it back.
Here's what I've done so far:
Spammed flash-all at least 6 times
fastboot format of /boot /system /userdata /cache multiple times
Multiple runs of WUGFresh
Flashed 4.4.2 and 4.3 images
What else is there I can do aside from sending it back to ASUS?

Does it boot to bootloader?
Sent from my Nexus 7 using Tapatalk

As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
This
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
Yes to all of those, I just did them again to verify. FYI WUG opens a command shell as it runs fastboot so you can see what it's up to.
Anywhoo I reflashed kot49h (manually) and got the same result, stuck at Google. If this thing wasn't still under warranty I'd snap it in half and light the two halves on fire.
Any other ideas?

What if you tried a custom recovery and custom ROM?

So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?

buelldozer said:
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
Click to expand...
Click to collapse
any updates? is it working fine now? any random reboots? god i hated that on my 1st nex7fhd, im on my 2nd one, its and perfect aside from the 'low speaker volume' stock

Might be an hardware issue, don't get stuck with software too much, send it again until they replace it.

I'd be interested in what ASUS did to it.
Did they include a list of parts replaced, etc?

I'm also curious.
As long as the flashes are done correctly it should boot fine.
However, I had a similar issue flashing stock.
The fix was to flash stock. Boot.
If it boot looped restart and wipe dalivik cache and cache and reboot. It should start then. just an FYI...
Sent from my Galaxy Nexus using xda app-developers app

If u get boot loops = lemon, it will develop those anno ying reboots
Via my NeXus™ 7 FHD on Tapatalk⁴ Pro

So it did it again but following the previous directions I was able to unloop it immediately the big story though is WHY it was looping.
I have a minisuit BT keyboard / case ( http://www.amazon.com/Minisuit-Blue...=UTF8&qid=1390433882&sr=8-3&keywords=minisuit ). The thing is dynamite and I love it and it worked great! The keyboard has a low power battery saver state so after you don't use it for a few minutes it basically goes to sleep until you tap a few buttons and wake it up.
I went a week with no issues but I wasn't using the keyboard. When I did finally use the keyboard I would stop typing and let it go to sleep as I always do. When I tapped a few keys it would wake up and then wake up the N7 and it's screen but the screen would -not- accept touch input. I had to hold the power button down and force the N7 to shut off. When I powered it back up...BAM...LOOPED.
It didn't do this before the Kit Kat upgrade. It's obvious that something is wrong with the BT stack in 4.4.2 and when a HID goes into a low power state it hoses the touch input. Since the touch input is hosed you can't shut it down correctly and the file system corrupts, likely the /system partition.
If I use the N7 without the keyboard it's perfectly fine.
userdelroot I couldn't clear dalvik on mine because I couldn't boot to recovery. All boot options lead to a Google Loop.

I have had exactly the same experience, basically. Just got mine back from ASUS, worked for about a day, and then BAM, back to the same DAMN thing! I think you may be on to something about the BT stack. If there is any common thread to both my breakdowns, its that my Nexus got screwed not long after i paired a BT headset with it. Its late and I'm frustrated as all hell so please forgive my short rant. So what to do? Do I send it back to ASUS and hope they actually replace it this time? (The invoice I got back from them was very strange incidentally. I couldn't tell what they did, except among four parts listed, they seemed to replace a "cracked, broken screen" which was not the way it was when I sent it to them???!) Or should I just keep reflashing and hope it takes, as it seemed to do for you? But then can I risk pairing my BT headset again?! This sux.
Update: Woke up this morning, turned it on, and it booted up! WTF? Not complaining I guess. Taking it easy this time, unlocked bootloader still of course, but holding off rooting, and not going to pair any BT with it for awhile. Although its kinda BS I should have to try it this way...

It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.

buelldozer said:
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
Click to expand...
Click to collapse
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?

Demian87 said:
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Click to expand...
Click to collapse
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.

buelldozer said:
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
Click to expand...
Click to collapse
Thank you a lot! I'll try to leave it turned on for the whole night. I left it only for 45 minutes before that. Probably, that was not enough.

My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.

buelldozer said:
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
Click to expand...
Click to collapse
My tablet is now at 9:15 hours and still at Google logo. I'm guessing that the time is not the only matter for normal boot up.
---
Now after 11 hours I gave up. =(

[Q] [HELP] Bricked Galaxy Nexus (maguro)

Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance

I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that

Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload

Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.

7.1.1 factory image soft bricking my device/bootloop

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