My phone prompted me to update to 4.1.2. Everytime I press install, it would boot and then stops half way with a red triangle icon. A few minutes later it will boot to 4.1.1. Someone suggested that it may be due to build.prop file. I mucked around with the build.prop trying to get google wallet to work. I don't care about the wallet anymore. All I want is to upgrade to 4.1.2 with no data loss.
Someone on this forum suggested using the GNex TOOLKIT V9.1 to flash Google Stock Image to phone and then the OTA update would work. If I do that, will I lost any data on the phone?
Sorry, NB to android. Thanks.
you messed with system files, the OTA will not install because of that.
you need to replace the files you modified with the original build.prop and any other files that you modified
if you want to go to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Ahh ... it took me a while to get my gnex configured to the way I want. That method sounds like a clean method but at the same time will wipes everything I have configured so far.
I should probably create a second thread to ask a different question, is there a way to disable the 4.1.2 OTA notification nag? I will keep this phone for another month or so before I pass it to someone else.
If you don't care about any changes you've made to the system partition, you can just flash the boot and system images. This will keep your data.
I upgraded this way before the official OTA was out. It will, of course, blow any changes you've made to /system away, but it will keep your user data and all your settings, etc. You normally don't upgrade by "dirty flashing" over top of another system, but nobody I've seen has reported any issues with going from stock 4.1 to stock 4.1.2 this way. I did it, and have had zero issues. Always take a nandroid backup if possible, just in case.
Follow efrant's guide, just only flash boot and system (and NOT userdata)
Related
For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.
becktionary said:
For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.
Click to expand...
Click to collapse
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.
efrant said:
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.
Click to expand...
Click to collapse
Ok, since then I had rooted my phone but decided to reverse it. I've since used WugFresh's Nexus Root Toolkit to flash back to stock, unroot and lock the phone.
Even after doing all of that I'm still getting the same stock recovery image. I haven't done anything since flashing it back to the stock image aside from setting up my google account on it.
Even when returning to stock you likely didn't flash all parts of the image, so you're missing something like the proper bootloader, radio, or recovery for that specific build. This is another great example of why toolkits are a bad idea. You have no idea what you've flashed.
op, go and ask your question in that toolkit thread
Sent from my i9250
Hi guys,
I have a problem upgrading my nexus to the latest 4.1.2 update.
My device found an update, downloaded it and rebooted to CWR.
It's starting to install and then I get error status 7. Installation failed.
I also tried to donload the update manually but same results.
My devices is rooted with an open bootloader.
TAKJU.
I've tried to seach the forum/stickies but couldn't find a solution.
can anyone please advise?
Thanks in advanced,
Do you have modified system files? Like did you modify your build.prop?
Having the su and superuser.apk does not matter, OTA will still go through.
Most likely because OP altered something within the /system/ or is using another radio other than the one supplied from OTA.
This is why I always say if you're going to root, don't "half-a.." it. Go for the whole thing. Rooting is a gateway drug to flashing
I did not modify system files etc..at least not on purpose..
zephiK - I'm not sure what you meant there. I don't remember how I rooted, but do you think the root was corrupted?
Can you help me fix this somehow?
I don't care to wipe if needed.
thanks!
Got the same situation as you, the update won't proceed as it can't pass the check to ensure the rom in your Nexus is the one valid for update. Search the thread and web, and the message that follow the error 7 code hint you what's the thing that's not match.
You scenario should not be the same as mine since everyone of us mess with our own Nexus in our liking. But I'll share my case to see if it get's you some insight.
First OTA and manual flash won't work, stop almost immediately as shown by the CWM progress bar. I saw the screen said something about system/calculator - Then I remember that I have use TB to backup and uninstall the stock calculator, image, and email.
Restore those 3 using TB, and try again.
This time, the progress bar moves, and it actually check and stop halfway in between before showing the Status 7 msg.
Then do some web search, someone said about the radio version, and I got bad battery drain anyway, so flashed the radio version, restart and reflash again.
This time progress a little bit longer, and still no dice. Status 7 msg says something about system/build.prop
Check my system folder on the Nexus, and find build.prop.bak, then remember I have messed around with build.prop before, trying to change the device name shown on the DHCP table on wifi routers.
Revert the change. Try flash again, and viola, it work. And now got my 4.1.2 running nice and smooth.
So pay an attention at what the string said in the status 7 msg, and you know why it won't start the update.
Hey, you mentioned you have a unlocked bootloader.
If you still can boot into android, download TitaniumBackup and backup all user apps and data, then pull the TitaniumBackup folder to your computer.
Then use fastboot to flash 4.1.2 image from Google.
Then finally use Titanium Backup to restore your stuff.
28907126 - Thanks for the info! It might help to others. I really didn't play with radio or system files.
Mach3.2 - Can you please direct me to a guide on how to flash the image?
Thanks for the help everyone.
naorca said:
Mach3.2 - Can you please direct me to a guide on how to flash the image?
Click to expand...
Click to collapse
There's a sticky at the top of this forum.
Just recently purchased an almost new Nexus that was originally purchased from Google.
Just got the notification that there was an update avail, 4.1.2 but it failed with an error and I see CWM listed.
How can I remove ClockWorkMod and get back to stock android?
Thanks
If you really are running stock 4.1.1 but with CWM (I highly doubt that), then yes flashing stock recovery would let that OTA install.
The reason why I say that's unlikely is that the only reason someone would flash CWM and have it on the device is to use it as a way to modify the device further. I highly doubt that the phone is 100% stock other than recovery. Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Considering you bought the phone used and it's been modified by the previous owner, I'd 100% flash it back to stock with Google factory images. I would never trust a previous owner's firmware that they flashed. If they were "smart" enough to mess around with it, then they're likely "dumb" enough to put something on there you don't want.
http://forum.xda-developers.com/showthread.php?t=1626895
martonikaj said:
If you really are running stock 4.1.1 but with CWM (I highly doubt that), then yes flashing stock recovery would let that OTA install.
The reason why I say that's unlikely is that the only reason someone would flash CWM and have it on the device is to use it as a way to modify the device further. I highly doubt that the phone is 100% stock other than recovery. Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Considering you bought the phone used and it's been modified by the previous owner, I'd 100% flash it back to stock with Google factory images. I would never trust a previous owner's firmware that they flashed. If they were "smart" enough to mess around with it, then they're likely "dumb" enough to put something on there you don't want.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thank you very much for the link. I'll have to make sure I don't loose anything since it's my wife's phone. I should have looked more closely when the install bombed out but I saw CWM and there was the typical list of things that you have to increment thru to get to what you want to install. Maybe the big system in the sky will try to do another OTA update before I get around to reinstalling.
All stock but cannot update
martonikaj said:
Other things are likely modified that would cause the OTA to fail even if you had a stock recovery on it.
Click to expand...
Click to collapse
What else can cause it to fail? I was originally on the samsung version of yakju, but I flashed takju (4.0.2) following instructions from XDA. I have everything stock, but I am unlocked and rooted, and my system has updated OTA all the way till 4.1.1. Whenever I get the "Update to 4.1.2" thing, though, I restart and install.
I see:
Android standing with a spinning blue-edged thing (Installing)
The blue bar at the bottom reaches about 1/4 to 1/3 of the way to the end
Android is on its back with an exclamation mark above (Recovery)
Trying to use the menu just lets me restart, install from ADB or USB, revert to factory settings, or wipe cache
Not doing anything causes it to reboot back into 4.1.1
I've looked around, and I couldn't find anyone with the same problem. (It's usually having CWM installed etc.)
Not sure if this is the right place to post it. Should I make a new thread?
Note: I have no access to computers right now. My laptop charger short-circuited and started a small fire. I have a new one ordered, which should arrive sometime these two weeks.
masasin said:
What else can cause it to fail? I was originally on the samsung version of yakju, but I flashed takju (4.0.2) following instructions from XDA. I have everything stock, but I am unlocked and rooted, and my system has updated OTA all the way till 4.1.1. Whenever I get the "Update to 4.1.2" thing, though, I restart and install.
I see:
Android standing with a spinning blue-edged thing (Installing)
The blue bar at the bottom reaches about 1/4 to 1/3 of the way to the end
Android is on its back with an exclamation mark above (Recovery)
Trying to use the menu just lets me restart, install from ADB or USB, revert to factory settings, or wipe cache
Not doing anything causes it to reboot back into 4.1.1
I've looked around, and I couldn't find anyone with the same problem. (It's usually having CWM installed etc.)
Not sure if this is the right place to post it. Should I make a new thread?
Note: I have no access to computers right now. My laptop charger short-circuited and started a small fire. I have a new one ordered, which should arrive sometime these two weeks.
Click to expand...
Click to collapse
2nd post of this thread
http://forum.xda-developers.com/showthread.php?t=1419170
Read it. Part of it is true for official (directly from gservers to the device) updates. If you want, you can then update yourself (read also 1st post) like instructed or put it like it needs to be and use normal update from within android again.
Read the stickies people, before pressing the "new thread/reply to" button.
Sent from my i9250
I have a stock ATT Galaxy Note II except that I am rooted so I could use Titanium Backup and a few other things. Also I hid or deleted some ATT Bloatware (not sure which ones -- probably should have recorded what I did). Anyway, the previous OTA update from ATT worked fine. But this time the update to I317UCAMH3 always fails. It downloads, reboots and then fails about when it says 25%. I have been searching here for ideas what to do. Tried to unhide the ATT apps that I could find. That didn't solve the problem. Used Triangle Away to get the counters back. Still no luck.
Did a lot of searching on threads here on what to do but none of the suggestions seemed to work. I think I still have stock recovery but not sure. Is there any way to tell?
Any ideas? Do I need to reinstall the ATT ROM from scratch (including reinstalling apps, etc)?
Based on what I am hearing from friends, I expect ATT to soon release the 4.3 update for this phone. So I think I would like to be stock for now plus root.
Any help would be appreciated.
Thanks
-- Charley
Your answer is here:
http://forum.xda-developers.com/showthread.php?t=2448927
I'll be doing this shortly as well.
I had the same trouble. I made a TiBU backup of user apps and their data (no system apps or system data). I made the zip file also.
Then I did a factory reset. After that, the phone completed the update.
charley000 said:
I have a stock ATT Galaxy Note II except that I am rooted so I could use Titanium Backup and a few other things. Also I hid or deleted some ATT Bloatware (not sure which ones -- probably should have recorded what I did). Anyway, the previous OTA update from ATT worked fine. But this time the update to I317UCAMH3 always fails. It downloads, reboots and then fails about when it says 25%. I have been searching here for ideas what to do. Tried to unhide the ATT apps that I could find. That didn't solve the problem. Used Triangle Away to get the counters back. Still no luck.
Did a lot of searching on threads here on what to do but none of the suggestions seemed to work. I think I still have stock recovery but not sure. Is there any way to tell?
Any ideas? Do I need to reinstall the ATT ROM from scratch (including reinstalling apps, etc)?
Based on what I am hearing from friends, I expect ATT to soon release the 4.3 update for this phone. So I think I would like to be stock for now plus root.
Any help would be appreciated.
Thanks
-- Charley
Click to expand...
Click to collapse
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
rangercaptain said:
I had the same trouble. I made a TiBU backup of user apps and their data (no system apps or system data). I made the zip file also.
Then I did a factory reset. After that, the phone completed the update.
Click to expand...
Click to collapse
Well tried that. Still fails.
I suspect there is some app or setting that I have to have for ATT to allow me to do it. Others have commented that you need all the ATT Bloatware and other stuff. I am not sure what I have wrong.
Read back one.. I was typing while you were sending
Zen Arcade said:
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
Click to expand...
Click to collapse
Thanks. Probably the best thing for me to do is just to wait until after 4.3 comes out. By that point, you guys will have figured it all out. Then I can either go from scratch (Odin to stock and the update) or I can pick the best ROM from here. I will probably do the latter.
I am leaning towards one of the ROMs that is close to stock such as Clean Rom or Jedi unless someone has a better suggestion.
Thanks everyone for your help.
Zen Arcade said:
The MH3 OTA update will fail if any of the files it attempts to patch or replace is missing on the phone. It also expects to see the stock version of kernel, modem, and recovery from whichever firmware it detects - typically MC3 or MA4.
If you don't have those missing system apps available for restore in TiBu, your only current option to get to MH3 is to use Odin to load UCALJ2 or UCAMA4 firmware (available from sammobile.com), then run the OTA process. This will wipe your phone back to pure stock and ymmv on what tibu can restore (stay away from restoring system apps, use caution when restoring data along with any other apps - i.e. only when necessary).
Lastly - I wouldn't be surprised to see the 4.3 update come with a locked bootloader. There may be a way to get into that firmware with root intact but the current state of the sgs4 is a pretty good indicator of what to expect when 4.3 arrives on our att i317.
Click to expand...
Click to collapse
Thanks for this info, very helpful.
Though I am rooted and on a custom ROM and all that, I'm far from an expert on this stuff. I plan on trying the AT&T 4.3 update when it drops, but I am also currently contemplating trying to go to MH3 stock, and maybe then re-root on MH3 and make a full Rooted stock backup available "just in case"...
With that in mind - Question: Can you tell me if getting the stock LJ2 or MA4 firmware via sammobile and loading it via Odin takes care of *completely* "stock"-ing your phone, all in one shot, including resetting the flash counter to "0" and all that good stuff? OR - would I still need to then CF-Auto-Root, Triangle Away, and then do a "Full Unroot" in SuperSU to accomplish all this? Just want to make sure I get it right
Thanks in advance. Been searching but have not found a clear-cut answer to this just yet.
Anonymously_Unknown said:
Your answer is here:
http://forum.xda-developers.com/showthread.php?t=2448927
I'll be doing this shortly as well.
Click to expand...
Click to collapse
Will this work if I have TWRP installed?
Hi all,
I have an HTC One M8 which is SOFF, Rooted, and bootloader unlocked via Sunshine but otherwise completely stock. Today I installed the new security update that's supposed to fix the Stagefright MMS vulnerability, and now the phone won't boot past the HTC splash screen.
I did some searching and found out how to power down the phone and get back into recovery, which I can do, but clearing the cache didn't seem to fix the problem. Anything else I can try while I'm away from my PC to get the phone to boot? I also tried removing the SD card in case that was the problem, but that didn't work either.
Once I get home from work I can do things with ADB if necessary.
I haven't seen the update, though I did see a weird notification yesterday. However, I would point out that rooted means you are not stock, and Lollipop updates seem to never work unless you are 100% bone stock.
yea i haven't really researched it, but if not mistaken stock lollipop does a sort of hash check on the system partition and if it doesn't match to what they have on file ie. being rooted which causes system changes. It becomes problematic so your best bet is to either restore from a backup or reflash which ever rom you have. Hopefully you can reflash without loosing all your data (custom rom instead of an RUU).
As for the patch. Wait until a rom developer incorporates it into their own roms. Or if its as simple as a system apk update or file change you can extract it from the update and replace it yourself.
If you were using a nonstock/custom kernel. Try reflashing just that kernel since maybe its as simple as that update containing a boot.img which you can reflash without much fuss. Unless the stagefright fix is within the kernel itself.
Balls!
The update was only 40MB or so, so I figured it wouldn't mess with anything major. However during the process it rebooted back into I assume recovery and/or the upgrading screen with the little progress bar and pic of the phone in it, so it must've been reworking something.
Hopefully I can mount the volume and pull my pictures and whatnot off when I get home. I should've known better not doing a backup first!
If I have to reflash, maybe I'll try the GPE ROM for a while or go back to good ole fashioned CM.
Firehawk989 said:
Balls!
The update was only 40MB or so, so I figured it wouldn't mess with anything major. However during the process it rebooted back into I assume recovery and/or the upgrading screen with the little progress bar and pic of the phone in it, so it must've been reworking something.
Hopefully I can mount the volume and pull my pictures and whatnot off when I get home. I should've known better not doing a backup first!
If I have to reflash, maybe I'll try the GPE ROM for a while or go back to good ole fashioned CM.
Click to expand...
Click to collapse
if anything you should be able to use twrp to make a back up of your data partition and reflash your current rom, install the update (while fully stock) and restore your backed up data partition on top of your stock build (kernel/ true cause depending) without much issue. But thats a 50/50 shot.
If the update did a reboot to RUU mode (black screen HTC logo with progress bar) it more than likely updated a partition whether it was a new stock recovery or boot partition.
haha balls... I'm slight intoxicated
Tachi91 said:
if anything you should be able to use twrp to make a back up of your data partition and reflash your current rom, install the update (while fully stock) and restore your backed up data partition on top of your stock build (kernel/ true cause depending) without much issue. But thats a 50/50 shot.
If the update did a reboot to RUU mode (black screen HTC logo with progress bar) it more than likely updated a partition whether it was a new stock recovery or boot partition.
haha balls... I'm slight intoxicated
Click to expand...
Click to collapse
Thanks for that! I'll throw TWRP on there and back that data up.
And now I just got this song stuck in my head:
www.youtube.com/watch?v=WL2txMU50CI