Develop Bugs

[Q] Galaxy Nexus bricked after Android 4.3 upgrade

Hi guys!
As soon as Google released the factory images for our GNex I downloaded the yakju one and flashed it. All was running fine.
Then I tried to root with Galaxy Nexus Toolkit option for yakju 4.2.2
SuperSU was installed but said no su binary available.
After searching for a while I saw the Chainfire's root method was doing the job for the Galaxy Nexus with 4.3, and applied it to my Nexus.
I can't remember exactly but I think the first restart was fine but I'm not sure.
Now my Nexus is stuck in a boot loop and it can't pass the boot animation. The phone start and show the Google logo, then most of the times I can see the boot animation but suddenly it restarts and the process start again.
Things I've tried before posting:
- Full wipes
- Installing CM10.1 and Gapps from CWM Recovery.
- Restore a backup from CWM Recovery
- Clean install of factory images (takju and yakju, 4.1, 4.22, 4.3)
- Restoring the factory image with ODIN as said in the HOWTO guide in this forum.
- Factory reset with factory images (tajku and yakju, 4.2.2, 4.3) with Galaxy Nexus Toolkit
- OMAP Flash trying to restore some flash memory issues?
By now, nothing works and I'm starting to think that there might be a hardware problem with my Nexus.
So, what you think? Can anybody help me?
Thanks in advance!

have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

lovejoy777 said:
have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, each Android stock version or custom ROM I've tried, was with it's bootloader.
I mean, bootloader #3 for 4.2.2 and #4 for 4.3

strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta

lovejoy777 said:
strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you a lot, I read you in other posts from today and yesterday looking for a solution to my problem.
By now nothing solved it, but I'll keep on trying.
All your help is welcome, thanks!

Even after installing factory image takju jwr66v I'm stuck in the boot loop:
- Google logo -> boot animation -> restart.
- (sometimes) Google logo -> restart.
I've flashed it with flash-all.bat script and manually and nothing.
Any idea?

u tried odin flash? i
Sent from my Galaxy Nexus

paarthdesai said:
u tried odin flash? i
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes, I tried.
After 20 or more reboots, it showed the screen:
"Android is upgrading...
Optimizing app XX of XX"
And then, bootloop again.......
So extrange.

For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.

ledoweb said:
For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.
Click to expand...
Click to collapse
So sorry to read another case.
In mine I can see the bootanimation most of the times.
I really can't understand how the Nexus can't boot properly even after a full wipe or a factory reset using the official factory images (or after ODIN)
As I told before, I'm starting to think about hardware problems, caused or not by the 4.3 upgrade.

i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.

ashclepdia said:
i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.
Click to expand...
Click to collapse
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!

||M^nnu|| said:
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!
Click to expand...
Click to collapse
its sounding more and more like the time i accidentally left mine in a freezer(worked in a kitchen. set it down after using in an industrial freezer that goes -10F !! for over and hour. it just wouldnt boot. after warming up it was as if /data was corrupted. i couldnt do ANYTHING.)
i was pleasantly surprised when it just fixed itself after insane amount of tries of wipes, installs, restores.
good luck! i hope it gets back in working order.
(im also wondering if it might have something to do with the supersu install, as ive read that there has been issues with it and people not being able to get to the symlinked /data things such as the legacy symlink. have you checked to see if there is a "supersu removal" zip you can flash? just in case that helps? or maybe try to fastboot boot the 4.2.2 boot.img? wondering if installing cm10.1 and then fastboot boot the CM stock boot img just in case something isnt installing right with that)

Try fastboot erase commands instead of factory reset in recovery

Maybe this can sounds stupid but, did you check MD5 of the downloaded image? I don't know, just to discard some reasons

Sdobron said:
Try fastboot erase commands instead of factory reset in recovery
Click to expand...
Click to collapse
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data

ashclepdia said:
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data
Click to expand...
Click to collapse
Thanks haha..didn't think about anyone doing that but you never know lol.
MD5 check would be advised too.

just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

OP what computer OS are you trying to do this from? I am wondering if something isnt flashing right due to a windows issue and as others like Sdobron mentioned check the MD5 of the tar.

lovejoy777 said:
just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
i am using the shiny ota rom from baldwinguy
you can find it at rootzwiki. i dont know if its posted over here
i havent had any issues at all.(i am also now running faux kernel, he tweeted the 4.3 update just now. running awesome right now)
here is the link
http://rootzwiki.com/topic/36706-ro...tock-android-43-jss15j-no-bugs/page__st__4810

[Q] Problems loading stock radio and recovery

I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.

resplin said:
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
Click to expand...
Click to collapse
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.

Still no stock recovery
wantabe said:
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Click to expand...
Click to collapse
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?

resplin said:
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
Click to expand...
Click to collapse
I'm sorry about the link, not that it does any good now but the link is corrected. Using fastboot to flash the images is correct, I too often use adb as a generic term for both. When you boot into the stock recovery you will see the android with the exclamation mark and that is normal. Finally got the new 2012 N7 I bought as a gift and was updating it. Been a while since I've booted into a stock recovery. So... Boot into stock recovery, when the Android with the red exclamation mark appears, hold down power first, followed quickly by volume up. You should now see the recovery menu. Whoop, Whoop! :laugh:

It works!
Thank you very much for your patient explanation. That helps a lot.
I hadn't realized that there was an additional step after the display of the warning android in order to enter stock recovery. All that time I spent trying to fix something that wasn't broken! <sigh>
I was unable to get the device to display the stock recovery menu, because it appears to require a very precise timing (I just keep rebooting it back to the system by accident). However, encryption did work fine. My confusion with the encryption was compounded by the fact that encryption of the Nexus 7 in 4.4 doesn't always work the first time (see this thread at android central: forums.androidcentral.com/google-nexus-7-tablet-2013/337078-experiencing-difficulty-encrypting-my-2013-n7-after-4-4-build-krt16s-upgrade.html). After trying 4 times in a row, the device encrypted. I was then able to put Team Win Recovery back on the device, and everything works perfectly.
Thank you again for your help. I don't see how to mark the thread as solved, but I am glad that everything appears to work now.

Bricked Nexus 7 while installing Lollipop - fastboot kinda works

Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.

Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..

kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.

kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now

Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?

This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app

atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!

DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.

Use wugs but make sure you tick tablet is in bootloop, worked for me.

atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!

Device will not flash any recovery in fastboot

My device decided to randomly encrypt itself after using the CM12 port that is available. How this happened is beyond me. Anyhow, I tried to do a factory reset... Nothing would mount because the device was encrypted. So, I thought it would be a great idea to flash a different recovery. By now, I have flashed over 6 recovery images (all different) even the stock. Fastboot says that the transfer went through successfully only to find when I try to boot into recovery, it boots into fastboot instead.
Yes the device is unlocked.
I don't know if there is a ROM on it, but when i try to start it normally, it wont boot past the splash screen (before the boot animation)
Please help, as this is the only phone I am stuck with for a long time

Here's a thread with people that have a similar problem. There are some suggestions of what to do in there, but personally none of them worked for me. I ended up having to send it back to Amazon.

iananderson said:
Here's a thread with people that have a similar problem. There are some suggestions of what to do in there, but personally none of them worked for me. I ended up having to send it back to Amazon.
Click to expand...
Click to collapse
Thank you. Still no success :/

BLEXXAR said:
My device decided to randomly encrypt itself after using the CM12 port that is available. How this happened is beyond me. Anyhow, I tried to do a factory reset... Nothing would mount because the device was encrypted. So, I thought it would be a great idea to flash a different recovery. By now, I have flashed over 6 recovery images (all different) even the stock. Fastboot says that the transfer went through successfully only to find when I try to boot into recovery, it boots into fastboot instead.
Yes the device is unlocked.
I don't know if there is a ROM on it, but when i try to start it normally, it wont boot past the splash screen (before the boot animation)
Please help, as this is the only phone I am stuck with for a long time
Click to expand...
Click to collapse
Never factory restore when you have a Custom ROM as it isn't made to reset with the devices stock hardware and causes things to go crazy.
Always use a nandroid of the original system with root, then unroot, then factory restore from that.
Also. YouTube search - HTC Desire 816 root unlock bootloader.
Use the .exe recovery from that video in fastboot at least twice without exiting fastboot or rebooting.
Now try the recovery.
Sent from my 710C using XDA Free mobile app

Didn't work. Thanks though.

BLEXXAR said:
Didn't work. Thanks though.
Click to expand...
Click to collapse
When you were on the stock recovery, could you wipe partitions?
Also what model do you have?

Bootloop and corrupted recovery

So I got an adapter (Finally) for my nexus 5x. Went home and got the WugFresh nexus toolkit. Made a backup, and things were going fine, and then hit root and install twrp. It installed and booted into twrp, and it gave me the not rooted message and rooted me. I restored the backup. So I rebooted it, saw it was doing the boot animation, and came back this morning to it being dead (I had it plugged into my desktop, thought it wouldn't have lost more than 1% of battery when I woke up). I tried booting it up, and it was booting forever and I concluded was bootlooped. Now, when I try to boot into recovery, I get the little android guy dead with the red triangle on top of him. Please help, I'm 14 and don't really know what to do because all my previous rootings went fine. Thanks!

You are on stock recovery. Flash TWRP if you want custom recovery and flash/wipe, or use the factory images to go back to stock. Any experience with adb and fastboot? I'd recommend using fastboot so you have an idea of what's going on and understand how to fix your phone in the future.

Keithn said:
You are on stock recovery. Flash TWRP if you want custom recovery and flash/wipe, or use the factory images to go back to stock. Any experience with adb and fastboot? I'd recommend using fastboot so you have an idea of what's going on and understand how to fix your phone in the future.
Click to expand...
Click to collapse
I know fully well about adb and fastboot. I've rooted all my phones before this manually via them, and i just tried the toolkit because a friend referred it to me. Like i mentioned before i'm in a bootloop and i have no access to it in adb. It just doesn't get recognized.

Hold power + volume down till you boot into the bootloader. Flash away.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Hold power + volume down till you boot into the bootloader. Flash away.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
yeah when i try and boot into recovery is when i get the red triangle above the android guy. there is literally no recovery there. Otherwise, yeah i would flash the firmware

Help!!! My Nexus device is totally messed up. It has ______ problem. What do I do?? @ wugfresh.com since you're already using that toolkit.
if your pc/NRT doesn't recognize your phone check the drivers and consider reinstalling them (the toolkit apparently has an option for that as well). also try playing around with the rotation of your adapter/cable. yes, usb c is supposed to work both ways, but some (cheap) cables seems to have different properties depending on the rotation.

Kevinisyoung said:
yeah when i try and boot into recovery is when i get the red triangle above the android guy. there is literally no recovery there. Otherwise, yeah i would flash the firmware
Click to expand...
Click to collapse
There is, its just the stock recovery. Go to the bootloader and flash TWRP using fastboot. If you have driver issues you might have to manually select the driver I normally have to the first time.