Database Info

[Q] Boot freezes/crashes after flashing images

Hello, I'm having some problems with my Nexus 5 LG-D820 32GB
Here is everything I did in order:
1 - Was using stock 4.4.4
2 - Tried to install OTA lollipop following this:
1) Install Minimal ADB and Fastboot.. This will allow you to run commands on your phone.
2) Install Android USB Drivers. This will add the proper driver to recognize your device.
3) Install Universal Android USB Driver. This will automatically add the driver when you go into recovery mode. It's a different driver than the one above.
4) Open Minimal ADB and Fastboot (your phone should be plugged into your USB now)
5) Make sure your phone is recognized (enter 'adb devices'. A long number plus the word "device" should show up).
6) enter "adb reboot bootloader"
7) Use the volume rockers on your phone until it says "recovery mode," then hit the power button.
8) When you get the android with the exclamation, hold power and tap volume up. Don't hold, just tap it.
9) Use the volume rocker to choose "apply update from adb."
10) Go back to the minimal adb and fastbook command prompt, and enter "adb sideload filename.zip". Filename should be the path and the name of the zip file. You can rename the zip file so it's easier to type in. You can also type in "adb sideload" then just drag and drop the zip file into the command prompt if you'd prefer.
11) It should now sideload. Once it finishes on your screen, it will go back to the bootloader and you should reset your system once it's finished.
12) Watch in anticipation as your apps get optimized.
13) Play with your phone.
Click to expand...
Click to collapse
3 - It apparently worked, no errors or anything. But, when the phone tried to boot, it got to the upgrading android screen, with the optimizing apps list (1 of 82), it kept freezing, crashing, showing graphical glitches, and rebooting.
4 - I went into recovery and did a full reset/wipe, thinking it might have been because of an app it was trying to optimize. It still did the same thing.
5 - I thought it might have been happening because I was trying to upgrade OTA instead of a clean full install, so I got the factory image from the google page and tried to flash it following this:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
Click to expand...
Click to collapse
6 - Apparently it went ok, no errors or anything. But the same thing kept happening, it got to the optimizing app screen and would glitch up
7 - I got scared and tried to flash 4.4.4 back with the method in number 5. It worked, the phone was finally usable again. Thinking I had a way to always reset, I decided to keep trying to flash 5.0
8 - Tried again method number 5 with android 5.0, still glitched at optimizing apps
9 - Tried using Nexus Root Toolkit v1.9.4 to flash android 5.0, no apparent error, but got the same results at the optimizing apps screen
10 - Tried using Nexus Root Toolkit v1.9.4 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
11 - Tried using the method in number 5 to flash back to 4.4.4, and this time it froze at the twirling balls loading screen
12 - ??? I don't know what to do now. I was thinking of trying to flash 4.4.3 using the method in number 5 to see what happens >_>
Any help is appreciated, does anyone know why it kept freezing and showing graphical glitches at the optimizing app screen? Am I doing something wrong? The thing that bugs me is that every attempt went nicely, it isn't like I couldn't flash the images. I did flash them with no apparent error but they didn't work..
Thanks for any help

Hi,
I still have not been able to successfully boot into any usable version of android, they keep freezing and restarting the phone, but no errors appear during the flashing process. Can anyone shed some light?
Thanks

Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.

RoyJ said:
Are you seeing the same boot animation after trying to flash 4.4.4 & 5.0?
Since you used fastboot to flash the factory images, it should have worked. Only thing I can think of is your eMMC died.
This happened to me once on my old Galaxy Nexus. Basically no matter what ROM I would try to flash it would boot to Paranoid Android. Even after flashing factory images with fastboot (encountering no errors) I'd be greeted with the old JellyBean PA boot animation. Never got any errors, but nothing actually worked.
That's why I asked if you're seeing the different boot animation between KK & LP. To me it kind of sounds like your eMMC fried.
Click to expand...
Click to collapse
The animation is different, twirling pseudo 3D balls for 5.0 and 4 2D balls meeting in the centre for 4.4.4
And every time it stops at a different point. Right after I flash is when it goes the furthest, and then it goes less and less each subsequent boot
I really don't know I think I'll try flashing using the LG Flashtool to see if anything changes

It didn't work... I'm basically out of ideas
Guess I'll try the same things I've already done but with another computer, in the off chance the pc was corrupting something

I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.

mr2620 said:
I'm having the exact same issue. I received the OTA and it failed on install. I tried to install the update through toolkit and it installed fine, but it kept freezing on the initial phone setup. I went back to 4.4.4 through the toolkit and again received the OTA. This time the OTA installed without issue, and I was able to actually get the phone set up, but it kept having graphical glitches, would freeze and requiring a reboot. Went back to 4.4.4 and then followed the procedures on the Google factory images page and installed the update without issue. Again, it won't get through the initial setup without the graphics issues and freezing. I wiped the cache, did a factory reset, and installed the factory image again, with no change. 4.4.4 is working without an issue. I have a friend that is also experiencing similar issues. I'm out of ideas how to get the update to work.
Click to expand...
Click to collapse
At least you can revert to 4.4.4, mine freezes on the balls/once it did on the initial screen
Using another PC just made things worse, it froze while writing the system image and now the usb recognition is flimsy, sometimes it says the pc can't recognize the device when plugged in and sometimes it works, but now I can't flash things anymore
Welp. It's a less than a month old phone too, and I really think it's gone

Mine has froze a couple of times at that screen as well. I was able to force it into recovery mode with the power and volume down buttons and I was able to use the soft brick function in the toolkit to get it back to 4.4.4.
Sent from my Nexus 5 using XDA Free mobile app

Well I was able to flash 4.4.4 again ( I guess it's really hard to get it completely bricked, always when I thought it was gone it was able to get to fastboot mode)
But it still freezes on the balls / starter config screens

I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app

You said you tried LG Flashtool and that didn't solve the problem either?

I haven't tried the LG flash tool. I'll have to try that tomorrow.
Sent from my Nexus 5 using XDA Free mobile app

mr2620 said:
I'm at a loss as to how to fix this and I'm not seeing much online about others having this issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, most problems are people receiving errors/not being able to complete flashing the images. What's crazy about this is that we follow the correct procedure, get no errors or anything, but it doesn't work

I'm still unable to boot. Will try contacting Google soon.

I still have been unsuccessful as well. I'm getting a replacement phone from Google. Should have it next week.
Sent from my Nexus 5 using XDA Free mobile app

Bootloop nexus 5

Hello,
So here it how it goes:
My N5 freezes suddenly and shortly after it goes into a bootloop ( stuck at Google logo ). And from there on, the only thing I can do is just go into the bootloader.
If I go to recovery mode I can see that I get "msm_sdcc.1/by-name/misc no such directory" or something like that.
The only thing that helps make this issue dissapear is performing an oem unlock in fastboot mode, but this is not a good solution since this is the 2nd time it has happened to me in the past 3 months.
What do you guys suggest I should check/do to prevent this issue from ever happening?
Thanks!

Does the bootloader relock itself at reboot? If it does, the emmc chip is going or gone.

@audit13
The bootloader doesn't relock itself. It remains unlocked even after reboot.
I just unlock it to perform this "trick" that helps me get out of the bootloop. ( also after unlocking it, I perform a fastboot oem lock, done this both times ).
Also, don't know if it is related, when i go into recovery mode i get the android with an X or an ! (forgot which one) which is most probably due to files missing.

The screen with the dead android is normal. No need to relock the bootloader in my opinion.
Have your tried flashing a completely stock rom, including th userdata.img file to see if that solves the issue?

@audit13 Wanted to keep the stock rom with which it had come. Also doesn't an update ( from L to M for example) change the rom completely?

An ota update will move the phone to the latest of the current version (e.g. 5.0 to 5.01). The the ota will move from LP to mm.
Personally, I prefer mm.

So.. The phone did it again today, same behavior, same result ( bootloop out of nowhere ). This time I performed a complete new install of the OS ( wipe cache, factory reset + reflashed a factory image).
At this moment the phone is working as usual and now I will wait and see if the issue reoccurs (hope not).
If someone else has any other ideas an how to prevent or read some logs from the phone ( even if I performed an oem unlock ) please reply.

Unable to recover my OPO

Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !

Did you try to "fastboot reboot" while in fastboot mode?

Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.

The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks

lenovo a2109a-f Bootloop (can still access with fastboot and the bootloader..)

EDIT: title is incorrect, model is actually S2109A-F
Hi, I'm pretty novice but have searched a solid 2 days about this topic on this device.
The lenovo a2109a-f I recently got (I know, its like 4-5 years old, but for 40$, not a bad 9+" tablet) was in fine working order, but did have some bloatware. Feeling ballsy, I attempted a root, and now it boot loops, meaning it will constantly reboot and show the animated splash screen, and play the synthetic chime sound. Each loop lasts about 1-2 minutes.
Since I can still access the fastboot and the boot recovery I've tried the following:
1) attempt the install of a new rom (original ICS or JB for this device) from a micro SD card inserted into the slot
- no go, it says it mounts the sd card, but wont read from it
2) attempt factor reset (cache, factory reset etc)
- no change and same root file still shows up in the tablet "/sdcard/"
3) Rerun the flash recovery process
- Tablet seems to accept linux (from windows) commands via cmd (fastboot -i <address/commands go here>), but no change for the boot loop
4) attempted other recovery images in fastboot mode
- thought I actually damaged it more. Since it stopped boot looping but wouldn't even boot to recovery at all. I then flashed the original recovery ("CWM_S2109.img") and was able to get the bootloader back and the bootlooping behavior again.
My question for you all, is there something I need to do via the fastboot method to clear the cache of the bootloader, or the memory of the device and install the bootloader that way and hope it accepts a basic OEM rom? Again, I'm no programmer, but am able to follow instructions and would love to be able to fix my 40$ mistake here sometime. Thanks in advance for all your help. I've used a lot of your tips and resources here over the years and have learned a lot from your skills and experience.

Nexus 5 optimizing apps bootloop

My stock Nexus 5 hardlocked today while attempting to connect to a wifi network. Upon restart, the boot-up animation took longer than usual, then displayed the 'Optimizing Apps' screen (which is not typical). It completed optimization on 5 apps, claimed to be starting Android, and then reset back to the boot-up animation, continuing the same cycle.
Unsuccessfully tried to boot into safe mode, although I can access Recovery Mode. Wiping system cache did not help. Installed ADB/Fastboot and sideloaded the original OTA without any improvement.
At this point, I'm hoping for either another path to get the device to boot or a way to extract some critical data (SMS, docs, etc.) off the device before doing a factory reset.

If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.

audit13 said:
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
Click to expand...
Click to collapse
Sadly no, fully stock phone.
Gave up and pulled the trigger on factory reset. We'll see if it helps.
On the plus side, this incident has motivated me to unlock and root my phone, hopefully expanding my options for the next time this happens.

Yup, an unlocked bootloader is definitely a plus in these situations.
I always unlock the bootloader unless it voids the warranty on the phone. Once the warranty is over, I unlock it if possible.

Factory reset seemed to work. Now unlocked and rooted!