Database Info

[Q] Error with OTA update on Stock Android

So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.

Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.

beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?

beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.

Describe more.

The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly

I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.

kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?

kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.

Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!

Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.

[Q] Booting problem!

Hello,
I have Google Nexus 5 ,
suddently rebooted and never start again.....
it tried to load android but cant't .
i tried to flash factory img but every time i run the flash all script and the phone reeboot the bootloader locks and the opperation failes.
Any suggestion for my problem????
p.s the phone isn't rooted

panakeki said:
Hello,
I have Google Nexus 5 ,
suddently rebooted and never start again.....
it tried to load android but cant't .
i tried to flash factory img but every time i run the flash all script and the phone reeboot the bootloader locks and the opperation failes.
Any suggestion for my problem????
p.s the phone isn't rooted
Click to expand...
Click to collapse
What do you mean with bootloader locks?

zagorteney said:
What do you mean with bootloader locks?
Click to expand...
Click to collapse
when i unlock the bootloader (fastboot oem unlock) and try to flash the new images , the phone restarts and it is locked again

panakeki said:
when i unlock the bootloader (fastboot oem unlock) and try to flash the new images , the phone restarts and it is locked again
Click to expand...
Click to collapse
That's a sign your emmc is bad unfortunately. If you're still under warranty you'll have to use it.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
That's a sign your emmc is bad unfortunately. If you're still under warranty you'll have to use it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks
Just missed it by a month (phone is 13 months in use)
So nothing I can do?

jd1639 said:
That's a sign your emmc is bad unfortunately. If you're still under warranty you'll have to use it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your reply.
Do you know how many monts is the warranty from google play (I bought it from England but i am in Greece now)
If the emmc is bad, why i can flash the boot.img and i can't flash the radio.img and the recovery.img.???

panakeki said:
Thanks for your reply.
Do you know how many monts is the warranty from google play (I bought it from England but i am in Greece now)
If the emmc is bad, why i can flash the boot.img and i can't flash the radio.img and the recovery.img.???
Click to expand...
Click to collapse
http://www.datalight.com/solutions/technologies/emmc/what-is-emmc That's why. Welcome to forum. Please start using search engines.

Major problem

So i got my nexus 5 for like a year now and when i got it i flashed twrp recovery and kernel franco cause....I dont really know.
So i wanted to reset my phone so I did a factory reset and turns out i didnt turn off my freedom app...
So now i cant connect to google services and i cant turn off freedom cause u need a google account to enter the app.
Dont know what to do I need help......

FapMaster784 said:
So i got my nexus 5 for like a year now and when i got it i flashed twrp recovery and kernel franco cause....I dont really know.
So i wanted to reset my phone so I did a factory reset and turns out i didnt turn off my freedom app...
So now i cant connect to google services and i cant turn off freedom cause u need a google account to enter the app.
Dont know what to do I need help......
Click to expand...
Click to collapse
Worst case, just flash the factory image. Stay on stock if you don't know why you flashed twrp and a custom kernel.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Worst case, just flash the factory image. Stay on stock if you don't know why you flashed twrp and a custom kernel.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Im not sure either why i did that...
I tried to flash factory image but the fastboot.exe just crashed after something like 10 seconds

FapMaster784 said:
Im not sure either why i did that...
I tried to flash factory image but the fastboot.exe just crashed after something like 10 seconds
Click to expand...
Click to collapse
Exact fastboot error output, please.

nvm i solved it

Please update thread title to let other devs know your issue is solved.
Sent from my Nexus 5

FapMaster784 said:
nvm i solved it
Click to expand...
Click to collapse
How did you solve it?
Sent from my iPhone using Tapatalk

The simle way would be to use the file manager in TWRP to wipe the offending file....
SENT BY ENTANGLEMENT

Latest OTA update unable to install - produced "Error" screen on reboot

A few days ago, I received a notification on my N5 for a new system update of size 10.1 MB. When I choose to install the update, the phone reboots as expected, shows the "Google" startup logo, shows a screen that indicates that it is installing the update for a few seconds, and then finally ends at an "Error" screen (please see the attached image).
The phone stays on this screen for quite a while (more than a minute), then finally the device restarts and the system update notification is still present.
I've tried rebooting the phone manually and installing the update again, both when charging and when off the charger, but this has not helped. I've also searched to see if others have been having this problem, but I haven't been able to find anything. Has anyone else been experiencing this issue with the latest update, or are there any suggestions for how I can go about getting the update to install properly?

I would suggest you flash the system.img and boot.img using fastboot. The latest factory image ends in 48i, Google nexus factory image and download that image, extract it and inside is another zip file, in there you'll find the system and boot images.
Sent from my Nexus 9 using XDA Free mobile app

Thank you for your speedy reply! I will do as you've suggested and respond with my results.

I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?

Why don't you just do what jd1639 suggested?
Sent from my Nexus 5 using Tapatalk

So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
cj182 said:
I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?
Click to expand...
Click to collapse
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.

TomCatullo said:
So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.
Click to expand...
Click to collapse
If your bootloader is unlocked just flashing the system and boot images does not wipe your device. If everything goes right there will be no re-setting up required, you will have to re-root if you're rooted but that's just a matter of flashing supersu in a custom recovery.
Sent from my Nexus 5 using XDA Free mobile app

Or try recovery (stock) and find the flash update from cache (might work)
Sent from my LG-D722 using XDA Free mobile app

That doesn't work. The update checks for changes to the system (root, etc.) and needs stock recovery to install.

I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?

It doesn't wipe your data... many of us have done it.

jrosado said:
I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?
Click to expand...
Click to collapse
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app

Telyx said:
It doesn't wipe your data... many of us have done it.
Click to expand...
Click to collapse
jd1639 said:
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.

jrosado said:
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.
Click to expand...
Click to collapse
Sorry about that, I meant it DOES NOT wipe the device.
Sent from my Nexus 9 using XDA Free mobile app

I'm sorry to say that it wipes all data and applications

jrosado said:
I'm sorry to say that it wipes all data and applications
Click to expand...
Click to collapse
Did you flash just the system.img and boot.img? Just doing that will not wipe your data. I do that with every update. If you flashed other images, userdata.img, then you device will be wiped
Sent from my Nexus 9 using XDA Free mobile app

Only system and boot..don't know why, but it wiped all

jrosado said:
Only system and boot..don't know why, but it wiped all
Click to expand...
Click to collapse
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, i had to do it..otherwise it would not write the firmware..is there any way to do it without unlock the bootloader?

This is why the first thing you should do when you get a nexus is unlock the bootloader...

twrp help

i have my sch-1925 rooted with Kingroot. Now I am following these instructions:
androidbits how to install Android 6.0 Marshmallo CyanogenMod 13 [CM13] Rom on Verizon Samsung Galaxy Note 10.1 SCH-I925 [Simple Steps]
will not let me post the link you will have to google it
I have TWRP downloaded from Google Play and when I open that App and try to do the install inside the app I get an error message that says
Something went wrong
Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now? No Yes
Yes makes the app unresponsive.
Any Suggestions

MIKEOS98 said:
i have my sch-1925 rooted with Kingroot. Now I am following these instructions:
androidbits how to install Android 6.0 Marshmallo CyanogenMod 13 [CM13] Rom on Verizon Samsung Galaxy Note 10.1 SCH-I925 [Simple Steps]
will not let me post the link you will have to google it
I have TWRP downloaded from Google Play and when I open that App and try to do the install inside the app I get an error message that says
Something went wrong
Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now? No Yes
Yes makes the app unresponsive.
Any Suggestions
Click to expand...
Click to collapse
Hi,
I think that your problem is due to the fact that your Note 10.1 is a Verizon one, which means that the bootloader of your tablet is probably locked and will be difficult to unlock. You will not be able to install TWRP nor any other custom recovery without unlocking this bootloader
Sent from my GT-N8013 using XDA-Developers mobile app

DroidHiker63 said:
Hi,
I think that your problem is due to the fact that your Note 10.1 is a Verizon one, which means that the bootloader of your tablet is probably locked and will be difficult to unlock. You will not be able to install TWRP nor any other custom recovery without unlocking this bootloader
Sent from my GT-N8013 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah. I am in the same boat. Have been looking up and down to see what I can do but nothing so far.
Hmmm.... https://wiki.cyanogenmod.org/w/Install_CM_for_i925 ???

dimitriz75 said:
Yeah. I am in the same boat. Have been looking up and down to see what I can do but nothing so far.
Hmmm.... https://wiki.cyanogenmod.org/w/Install_CM_for_i925 ???
Click to expand...
Click to collapse
Maybe this could work, but honestly I don't know if it will.
I also owe a Moto X 2014 and I know that some peoples who owe the Verizon version managed to unlock their bootloaders with a tool called Sunshine, which they had to pay for (25$ ) but which worked well. I don't know if this could work with your Note 10 because it's an older device than the Moto X 2014, but maybe this could be a solution.
Sent from my GT-N8013 using XDA-Developers mobile app

DroidHiker63 said:
Maybe this could work, but honestly I don't know if it will.
I also owe a Moto X 2014 and I know that some peoples who owe the Verizon version managed to unlock their bootloaders with a tool called Sunshine, which they had to pay for (25$ ) but which worked well. I don't know if this could work with your Note 10 because it's an older device than the Moto X 2014, but maybe this could be a solution.
Sent from my GT-N8013 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nah, They only support Moto and HTC. I saw nothing about Samsung on their website.
Somebody in another thread said that it's possible through ADB. I am gonna give it a shot when I am back at work on Monday.
Stupid Verizon!, lol. They whine about having unlocked devices on their network as being a problem yet all the Xoom's we have at work can be bootunlocked without any problems.
They seriously about to loose our business account over this stuff as I gotta purchase 50+ tablets.

Adb
Any luck with adb?

MIKEOS98 said:
Any luck with adb?
Click to expand...
Click to collapse
Sorry, was dragged out on a business trip.
Will add to my calendar for Monday test.
Update on Monday!

dimitriz75 said:
Sorry, was dragged out on a business trip.
Will add to my calendar for Monday test.
Update on Monday!
Click to expand...
Click to collapse
Ok, I just tried but nothing
when I issue "adb reboot bootloader" it reboots but goes back to OS.
not sure I am a n00b at this., lol
I also set it to Download mode but adb doesnt see the tablet.