Recently got this phone off Swappa, its unlocked and not rooted. I'm getting the OTA notification to upgrade to 4.4.3. It downloads reboots, goes through the install animation after the install and android falls on his back with the exclamation and error under it. When I reboot i'm still on 4.2.2, any suggestions?
I'll suggest you try this excellent thread for help....
http://forum.xda-developers.com/showthread.php?t=2523217
?
bicho6 said:
Recently got this phone off Swappa, its unlocked and not rooted. I'm getting the OTA notification to upgrade to 4.4.3. It downloads reboots, goes through the install animation after the install and android falls on his back with the exclamation and error under it. When I reboot i'm still on 4.2.2, any suggestions?
Click to expand...
Click to collapse
If I just got a new (used) phone the first thing I'd do is flash the latest factory image in fastboot. Then make sure everything is working right. If you go this route see rootSU's sticky rollup in the general forum.
Sent from my Nexus 5 using XDA Free mobile app
Related
I have a rooted NS4G with custom kernel Matr1x #5. Im currently on 2.3.4 and have not added any roms or updates. I kept recieving the OTA updates every 1/2 hr. im assuming for the 2.3.5. OTA was 22mb.
I was holding off for a while to not to update but finally gave in. I went to install OTA and my phone turned off and look as tho it was going to update my system. I let 15-20mins go by and I was still at a screen where there was a triangle with an exculmation and the android.
I thought it shouldnt take that long to update so I pulled the battery. I rebooted my phone and it still has 2.3.4 as my android version but when I click on system updates it says my system is up to date which is not the case.
If anyone install this OTA how long did it take for the whole process??
How do I fix this is with my system saying its up to date but clearly its not since im on 2.3.4???
I no longer get the notification to install a OTA. I would like to install an OTA instead of doing it manually.
I still want to be able to receive updates OTA when the are released. Im afraid I messed something up
Any assistance would be greatly appreciated
Thanks
http://forum.xda-developers.com/showthread.php?t=1185812
Flash this in clockworkmod it should update u and u keep root.
Sent from my CM7 powered Nexus S 4g using XDA Premium App
Rooted phone + OTA = fail
You need a stock recovery to install an ota....
Sent from my Nexus S 4G using xda premium
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Tbalon said:
Nexus S i9020A , completely stock, running 4.0.4
Got an OTA update the other day, went through the update, no errors, rebooted, still 4.0.4 ????
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
try to flash CWM via fastboot then update via a zip file throw cwm.
if not u can get ur phone back to clean stock using adb and then u will receive again the ota and u can try to update again
Tbalon said:
System Update shows my phone is currently up to date
It looks like the OTA update failed, but I'm not sure why or how to determine why.
Any help would be appreciated... again, my phone is stock, no custom rom, non-rooted ...
Click to expand...
Click to collapse
It is not necessary to flash in order to get the OTA update again. Instructions to force another OTA update are here (basically: clear data on the Google Service Framework app, this resets the time the phone last checked for an update).
However, I'm facing the same problem and even after re-downloading the 4.1 update on my stock Nexus S, the update still fails. The phone reboots and starts to install the update then shows the dead droid with red exclamation before rebooting to 4.0.4.
I've seen other suggestions to get the device back to stock so I guess that's my next course of action (and likely yours).
Are these instructions appropriate? http://forum.xda-developers.com/showthread.php?t=1785672
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
I9020A needs two OTA's to get jellybean. The first OTA will make you keep 4.0.4 but will update your bootloader. This first ota, the one I think you got, is about 1MB in size. You will soon get another OTA, this one will bring you to jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
That is what appears to have happened. I was just confused regarding this and assumed my previous update was to 4.1.
I tried several times to "checkin" and eventually I got the update to 4.1.1 which, unlike the update I did a few days ago,
took longer ( about 10minutes ) to update. I now have 4.1.1 JRO03E , very snappy
Thanks !
No problem, man! Us I9020A's gotta stick together!
Sent from my Nexus S using xda app-developers app
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
mortified21 said:
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
Click to expand...
Click to collapse
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
If you have 4.3 stock firmware you can root and that's it, no custom recovery, no custom rom, kernel, nothing, and just a heads up there are like 10 threads where people don't read and have done what you have, you need to flash the Odin 4.3 image for you phone to work again, never take an ota, enjoy your locked down device now
Sent from my SCH-I535 using XDA Premium 4 mobile app
SlimSnoopOS said:
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
Click to expand...
Click to collapse
Worked perfectly! Thank you so much!
mortified21 said:
Worked perfectly! Thank you so much!
Click to expand...
Click to collapse
My pleasure but all the thanks is owed to ThePagel, make sure to post your success in his thread. The more people that report their success with that method, then the less fear someone else may have in using that should they suffer the same experiences. :victory::good::good:
If you need any updates on the state of TW 4.3 then keep this discussion thread bookmarked.
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
AURMEND said:
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
Click to expand...
Click to collapse
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
buhohitr said:
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
Click to expand...
Click to collapse
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
AURMEND said:
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
Click to expand...
Click to collapse
Yep! sucks big time!!
All I am sorry if this has been asked as I cannot find the same issue when I search
I was offered the lollipop upgrade via OTA today. I downloaded and rebooted as it asked. Then since I have my phone rooted with TWRP the TWRP screen came up and I tried and install.. that failed obviously, again rebooted into TWRP and then chose to boot to system, it looked like it was upgrading packages and then i looked a few minutes later and it showed my phone was not updated.
Now when I go to the options/about phone/software upatdate it says that I am up to date and I am at 4.4.4..
Can anyone help? I would really like to get lollipop on there without losing all my data.
TIA
Hi, have a look here, it worked perfectly for me and i didn't lose any data.
http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072
Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
joehouin said:
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
Click to expand...
Click to collapse
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
pricedpizza said:
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
Click to expand...
Click to collapse
Hello, do you mind sharing the link to preview 2, i googled it but didn't see an exact mention of "preview v.2"
Is it one of the ones found on this link?
https://developers.google.com/android/nexus/images#shamu
Thanks in advance,
Julian
I have this same message on my Nexsus 6. Neither Google, Motorola or Sprint can help me get my phone to turn on again. It's past the one year warranty, so no one will replace it. Can anyone help me?
cam30era said:
Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Click to expand...
Click to collapse
I hit the same message loading CM13 on a Nexus 9. Google explains here - support.google.com nexus answer 6185381? I wiped all partitions and loaded stock Marshmallow - the error disappeared. After re-flashing TWRP 3.0.2 the "corrupt" error came back. I then rooted with BETA-SuperSU-v2.66 which got rid of the error. Have since added Google account, updated apps etc. Still booting without error.
So would you say twrp is the reason it gives that error? I rooted my phone today, but when I went to my recovery to check to see if I indeed had a nandroid back up, I didn't... I made one using titanium backup, but didn't show in twrp. Anyhow, about that error message... I didn't know what to do after I had the pop up error message so many times... so i just unrooted my Nexus 6p. I really would like to keep my phone rooted, but I didn't like seeing that concerning error message. Any ideas of what I can do. I would be starting from scratch again. Any links would help! Thank you in advance.