I am trying to recover my bro -in law's phone who bricked his phone during an OTA update. I don't know what happened. I have followed several of the how to's here but i ran into the error updating Firmware shown in a black box.
I have an AT&T Galaxy S4.
I have been trying using kies, going to "tools", then "Firmware Upgrade and Initialization." and followed the instructions and agree to everything.
It continues to download the Firmware which takes about 30 minutes then it changes screen and looks to begin the download to the phone
but right away has an error "failed to upgrade due to unexpected error, do you want too run emergency recovery now? And wants a recovery code.
That's as far as I get, I'm exhausted in my ability to fix this. Can anyone help?
http://forum.xda-developers.com/showthread.php?t=2926642
Hello i have a problem with a friends LG G2 I flashed it lolipop 5.1 and then i wiped the whole internal storage clean and installed new firmware on it i tried flashing 4.4 the second time then the phone did not boot up and the screen was stuck to an error message cant quite remember it.
Anyway my friend sent it to lg and they said to him that the phone was double flashed and it could not be fixed... I need to know if i can recover the phone and if so detailed steps if possible.
Thank you very much (The phone has access to TWRP recovery.)
Please guys it is very important i need help with the matter
It can be unbricked. Your problem was probably flashing wrong bootstack since you got security boot error.
First, if you can get into download mode, do tot/kdz. There is guide here on xda
http://forum.xda-developers.com/showthread.php?t=2432476
UPDATE: Solution below!
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
UPDATE: Google posted signed OTA zips that can be used to recover from this situation. You can now use adb sideload to side load the full OS in OTA form. Go to https://developer.android.com/preview/download-ota.html to download.
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
kalinskym said:
Will I be able to recover if this happens by unlocking the bootloader and enabling USB debugging then install Android N preview? I'm feel for you. Good luck.
Click to expand...
Click to collapse
If you unlock the bootloader and enable USB debugging prior to installing the Android N preview (via OTA), you should be fine. You're essentially leaving yourself a backdoor to flash the factory image should the OTA fails.
Yes, I wish I know this earlier, and now I have a bricked Nexus 9 with me. :sad
Ouch, had that issue and went here looking for help. Should have waited before I tried it ?
THIS IS CRAZY! OTA should work :-\
So crazy to hear that you are all having the same issue with the Android N Developer Preview on Nexus 9!
I have had exactly the same experience today when I enrolled my device for the OTA. It downloaded and started to install fine, but got stuck with the android on his back with the red exclamation mark. It then rebooted and is now stuck on the Google logo. I have tried using adb to push files, factory reset/wipe cache & nexus root toolkit. However, I had NEVER set the OEM unlock option and that seems to have left me stuck!
I'm hoping someone will figure out an amazing fix! Just in case no one does, I called Google and as I purchased it from the play store they have offered me a replacement. Sadly I'm living in Thailand and they can only arrange it to my home country, Australia. So sorry they wouldn't help you Naddie
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
sashinde said:
I didn't unlock the bootloader and I'm also facing exact same issue, my tablet is now almost bricked .
I can go to "recovery" mode, so I tried to do "adb sideload" with OTA image for MMB29V from MMB29R (got from gist.github.com/jduck/744a6c8a9042e9c792b7), but my device is already at MMB29V so it complains with below error:
"system partition has unexpected contents"
Will I be able to flash OTA image through recovery once we get it for MMB29V to AndroidN_version? And where should I get it from?
What other option do I have to recover the device?
Click to expand...
Click to collapse
Gee, I hope we're still on MMB29V... But since the OTA seemed to have failed during the update, the system partition may be partially whatever build this Android N preview is and partially MMB29V - which is to say ... It's completely borked for ANY OTA update to fix it via side loading.
Does anyone even have the OTA zip for MMB29V to N preview for we poor souls to try?
Sent from my iPad using Tapatalk
Hello. Sorry for my english. The same from here. I called Google and they offered me a replacement. I said yes. Waiting for a new Nexus 9. I hope you will find the solution.
Enviado desde mi Nexus 6P mediante Tapatalk
Naddie, have you contacted HTC or Google yet about getting a replacement?
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
I tried updating via the beta program, but there was an error and now my Nexus 9 is softbricked. I can get to fastboot and recovery, but can't boot into Android. And, worst of all, I don't have USB debugging enabled, so I can't do an ADB flash or even OEM unlock.
Can anyone help me out?
naddie said:
There is a chance the OTA will fail, as this have happened to some users already:
http://forum.xda-developers.com/nexus-9/general/nexus-9-android-n-preview-t3332715
You might be able to recover if you have USB Debugging turned on PRIOR to performing the OTA update. (Will need to flash factory image).
The problem is the factory image will require you to unlock the bootloader to flash it. To unlock the bootloader, you need to enable USB Debugging. BUT if the OTA fails, you can't boot into the OS to enable USB Debugging. You will end up with a brick.
Here's my experience:
I enrolled my Nexus 9 in the Android N Beta Preview program, and a minute later I got a notification that I have a system update. I went through with the update like any other update. I got to the part where you see an Android laying on it's back and it says "updating system" (or something to that effect) and it has a progress bar. After a few minutes, I see the same Android on it's back, but with an exclamation mark and the words "ERROR!". It would then reboot itself after a few minutes later, but get stuck at the Google logo.
If you leave everything stock, unrooted, and bootloader locked (like a good user), don't try to get the preview via OTA without enabling USB Debugging first! This way, you can at least be able to flash the factory image if the OTA takes a dive.
Since I bought the tablet on Amazon, Google is washing their hands from tech support. Instead, they gave me HTC's support line (which is currently closed). I don't know what I will have to face tomorrow morning when I call.
Click to expand...
Click to collapse
Nexus 9 is FAMOUS for OTA's failing and leaving you with a "brick".
The good news is that the sky IS NOT falling, even with the bootloader locked and debugging OFF, you can still recover it. All you need to do is reboot into recovery, and "adb sideload" the update.zip again.
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
greiland said:
My update failed too and I cannot boot. I did not have the OEM unlock switch flipped, so I can't unlock my bootloader. I chatted with Google last night and since I didn't buy it from the Google Store, they wouldn't replace it. They gave me the HTC phone number instead. I haven't tried calling them yet.
Click to expand...
Click to collapse
The switch unflips every reboot anyway, so that wouldn't have helped you to begin with.
What "Update" would I sideload? I did my original update via OTA.
Fixed Brick on Nexus 9 OTA Android N update
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Good to know. I just signed up for the beta program. My bootloader is unlocked from day one because I always flash the stock image of the security updates. The USB debugging is on
Sent from my Nexus 6 using Tapatalk
inthelandofnod said:
I had the same problem yesterday with a failed OTA update.
I solved it by booting into Fastboot ( hold down volume up and power button until you see Fastboot options). Then choose recovery. The Nexus 9 should try to reinstall the update.
For me this worked and I now have a working Nexus 9 on Android N beta.
Hope this works for you folks !
Click to expand...
Click to collapse
Can you please explain more detailed? Are you sure it's volume up because recovery is volume down. And what to do then in recovery?
Please, give us more info!!!!
Enviado desde mi Nexus 6P mediante Tapatalk
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
So this might be resolvable if someone has found the Android N OTA...
srideep said:
I am on MMB29V with unlocked bootloader, TWRP recovery, rooted. I opted in for OTA. It downloaded and seemed to install. After restart it booted to recovery and nothing else happened. When I restarted to system I was still on 6.0.1. No errors, nothing! Any clue?
Click to expand...
Click to collapse
OTAs won't apply if you don't have stock recovery.
HI all,
So I today I messed up and I need your help :crying:. Basically here's whats going on: I decided to root my phone since I found that battery was complete garbage, so I decided to root the phone with TWRP and Odin and after flash a new kernel for my phone as well as SU. Everything went fine. However, when i tried to reboot my phone to get a custom rom i wanted, it keps telling "kernel is not seandroid enforcing" and would be stuck in a boot loop (which apparently is normal and would just need to flash a rom for it to work). Finally I just decided to boot factory, so I can get to my files and put that damn custom rom. Long story short, I was able to put it, wiped system in TWRP and flashed this new rom only to get another error "THis package is for device trltetmo, this device is trltexx". Now I couldnt even factory reset anymore. At this point I decided to flash my back up that I did before and yet ANOTHER problem "cannot restore system mounted read only". After couple of hours of research, I needed to change the name of the file to system.image.mbn i think, I changed a file called system.ext --> system.image.ext. Needless to say that it didnt work. Final thing I decided to do is simply to flash a stock rom with odin and reverse the root, so I downloaded a stock rom for note 4, started the whole process with odin and now it is stuck at system.img.ext4....and i have no clue what to do, I dont know even know what I did before is the problem or it is something else, all i know is that odin is stuck at that message. Should I just let it go, should I stop it? Help! please
Wow, true hardship you get it back running?
Try using Kies and doing firmware upgrade mode to see if it can download and load the stock firmware for that device.
My father gave me his dead phone to fix. He said he dropped it in water and has been working nice until he rebooted to "installing sytem update", then goes the yellow triangle with dead droid and the stock recovery comes up.
No custom recovery, no root, no custom rom.
I naturally tried to flash a stock firmware (6.0.1, BP6), and failed. I tried with a 4 files firmware (same, 6.0.1, BP6) and aye, it passes on Odin but boots exactly the same (installing system update etc).
Then I tried to downgrade, to root, to everything, but the FRP LOCK is On and seems to screw up.
I tried to find a 4 files 5.1.1 firmware but couldn't find any working, maybe I didn't find the right one I don't know (France, XEF).
I get a different fail on Odin each time I'm trying to flash something, like there is always a reason to fail.
The best I get is with the 4 files 6.0.1 but still, I'm stuck on stock recovery.
What can I do ? I can't believe I'm stuck forever, I'm pretty sure it can be fixed, unless you guys tell me I'm wrong and the battle is over...
I can't believe no one has any idea
did you tried any other country software for this?
give it a shot.it might work
Yes I did
I gave it to a guy who has a box to get rid of the google limitation..