As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
jjimenezjj said:
As the title says, I'm getting notifications to upgrade my Nexus 7 to 4.2 even though I have 4.2 already. If it were the 4.2.1 update that it wanted me to update to, wound't it say 4.2.1 instead of 4.2?
Info on the device:
Rooted
Bootloader Unlocked
Stock ROM
I went ahead and tried installing the update many times and while it shutdown to do its dirty work, it eventually error-ed out (while the little Android guy is on his back). I have even done a factory reset and I still get the prompts to update to 4.2... from 4.2. Errors are there as well. Thank you for your help.
John J
P.S There are pics
Click to expand...
Click to collapse
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
phonic said:
This has been posted about before.
Yes, the 4.2.1 upgrade says "4.2" in the update screen. Your device is trying to go from 4.2->4.2.1.
The upgrade however seems to be failing. Since you are using a stock recovery, there is no indication on what part is stopping it. It could just be a glitch or, more likely, you modified something. Did you install any mods or root and modify any system apps? Freezing them in TiBu/etc. will break it too.
Click to expand...
Click to collapse
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
jjimenezjj said:
I did read other posts but they didn't seem to help.
After I rooted the device, I went ahead and pasted the original browser.apk in the System/App folder and installed it from there. From what I read, that was most likely my problem. I deleted it but still got the error. After that I said "screw this" and applied a data factory reset thinking that would solve my problems
Thank you for your reply.
John J
Click to expand...
Click to collapse
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
phonic said:
Yes, that modification would certainly break the OTA update.
Doing a factory wipe won't help. That won't revert the old system apk back to stock. Nor will deleting it.
Your best bet is to download the full 4.2.1 image and flash that. Or, you could find and restore the original browser.apk.
This should serve as another reminder to people who make tweaks - always backup the original file!
Click to expand...
Click to collapse
It's not that bad. Everything works fine except for updating the thing. As for the restoring the original browser.apk, if you mean Chrome, I never touched it so it is there.
My guess is that I didn't install the CWM Recovery correctly because I can't boot into Recovery Mode. It just hangs and stays in a loop. I will re-install CWM and see if that helps.
John J
Re-installed CWM Recovery and flashed 4.2.1 from there. Lost everything but I had anything important backup already. All is good
Related
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
ogal said:
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
Click to expand...
Click to collapse
why dont u just make a nandroid, fastboot back to stock ics with rsd, dont root your phone or do if you think it doesnt matter which ur right ive flashed the leak and official multiple times already both rooted and not, boot back to recovery and try it again...i heard this might help although i never have had to but rename it update.zip.
heres the one i used have never had a problem:
http://forum.xda-developers.com/showthread.php?t=1982934
Hi, I've downloaded the OTA update from Verizon for my Razr M three times this morning because each install shows "The Software Update Failed". It'd be just peachy if they didn't make me download all 250 MB each time I tried. Sheesh.
Aside from that, it's still not updating. This phone is rooted, but has never had a custom ROM put on it.
Hmmm...now that I think about it, I do have a bunch of apps disabled, including some Verizon apps, etc. I'll try enabling them and trying this all again.
Hmmm...didn't work. Still getting the failed error message. Going to back everything up and do a Factory Reset.
lostpilot28 said:
Hmmm...didn't work. Still getting the failed error message. Going to back everything up and do a Factory Reset.
Click to expand...
Click to collapse
I am currently having the same issue in attempting to download/install the latest VZ update. I've done a factory reset and tried voodoo rootkeeper to temp unroot the phone to no avail. The only modifications I had made before the reset were deleting some of the bloatware manually with root explorer- those apps were subsequently restored from the reset.
Any idea how I can update the phone? Given that there is currently no way to install a custom ROM currently and can only delete bloatware, I'm thinking rooting this phone doesn't really help much if we are then not able to update it
Update
fiendebass said:
I am currently having the same issue in attempting to download/install the latest VZ update. I've done a factory reset and tried voodoo rootkeeper to temp unroot the phone to no avail. The only modifications I had made before the reset were deleting some of the bloatware manually with root explorer- those apps were subsequently restored from the reset.
Any idea how I can update the phone? Given that there is currently no way to install a custom ROM currently and can only delete bloatware, I'm thinking rooting this phone doesn't really help much if we are then not able to update it
Click to expand...
Click to collapse
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
ogal said:
Checked for the new JB update, downloaded it. I went to install it and it got about a third of the way there, failed, rebooted and I am still on 4.0.4
Then it gives me a notification saying the update failed to which I can only press OK.
I've tried to update three times now and it does the same thing.
My phone is rooted, but I don't think that should cause problems
At a loss here...
Click to expand...
Click to collapse
I upgraded to JB via OTA from Verizon, you will not lose anything if you upgrade that way, nor will you have to setup anything again. If you flash it through RSD lite than you probably will lose everything plus have to go thru the setup process again. Hope this helps. Make sure you uninstall safe strap recovery and if you're rooted make sure you backup and save root via the voodoo app, before accepting the OTA. I found out the hard way. If you don't uninstall the safe strap recovery the OTA will fail every time.
Being rooted does not have anything to do with the OTA failing. Its safe strap if you are using that.
Sent from my XT907 using xda app-developers app
fiendebass said:
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
Click to expand...
Click to collapse
I used this method phonearena.com/news/How-to-restore-your-Motorola-DROID-RAZR-M-back-to-stock-ICS-from-the-JB-leak_id35580 .
Followed all the links and tried to RSD back to stock and then OTA, but now Im bricked....any suggestions on flashing a fresh copy of ICS using RSD LITE??
fiendebass said:
I've restored the phone to stock ICS via the Fastboot method. This allowed me to automatically update to Official Jellybean.
Click to expand...
Click to collapse
Could you direct me to somewhere I can find out details about this? What is the fastboot method?
I was on 4.2.1, rooted, and with TWRP as recovery.
I wanted to get the OTA to 4.2.2 so I did full Titanium backup and then used the WugFresh toolkit to flash stock 4.2.1.
After flashing, I was offered the OTA which I allowed to install.
When finished, I got root back with Rootkeeper and restored all Apps and Data (not System data) with Titanium.
Everything was working, but on every reboot I got the message :
"System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
I also found that My Phone Explorer would no longer connect via USB so I decided to go back to 4.2.1.
I again flashed it with the toolkit and did another restore with Titanium. Again, everything seems to be working, but I still get this message on every boot.
I thought using Titanium Backup was a standard way of restoring apps and data.
How do I get rid of this message without wiping and reinstalling all my Apps individually, which means losing all my game scores, etc?
I also see that in Bootloader there is a line
"Signing - not defined yet".
I do not know if that was there before flashing back to stock.
same problem
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
windwhisper said:
system UIDs inconsistent, it keeps showing up after every boot.
i have nexus 7 GSM 32 gb rooted using nexus 7 toolkit with clockworkmod recovery, android version 4.2.1 build number JOP40D
i tried Rom manager fix permission the same problem, i don't like resetting it any suggestion
thank you
Click to expand...
Click to collapse
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
windwhisper said:
it took me time and I did it using clockwork mod recovery
advanced then fix permissions
but nothing happen , still the same.
should I try flashing TWRP recovery then..
if yes. could u help me with a simple guide
much appreciated
thank you
Sent from my Nexus 7
Click to expand...
Click to collapse
You can boot any recovery you want without hard-flashing it to the device (so long as the boot loader is unlocked).
With the device in bootloader/fastboot mode,
Code:
fastboot boot name-of-recovery-image-file.img
So download TWRP and give it a roll.
Hello,
I got the same "System UIDs Inconsistent" problem. I like to solve my problems myself but I've got no way out this time, so I'm asking for your kind help.
I'm on the SGS III, i9300, I rooted it then went to Omega ROM, and then to Paranoid Android. Everything went well until I got a battery problem (when charging the phone, it was not sufficient to bear with it functionning, so it powered out while charging). After that, the phone restarted and the UID problem appeared. Maybe it's just a coincidence.
So far, I : fixed permissions, did at least 10 factory resets with TWRP, changed ROM (went to CM and came back to PA as nothing changed).
I read the 6 first post about this in xda forum, and other forums too, but nothing came out as an evidence.
Last thing I did was upgrade my PA ROM : the phone couldn't even go beyond the booting process, failed to initiate the phone "first settings" app.
So I came back to the previous version of PA, and was able to use my phone again, but apps like Gmail, Color Note, won't work.
I want to get rid of that, and I wish someone told me, step by step, the things I could do to eradicate the problem. I will do what's necessary to achieve that, I only need someone who knows what to do, and how to do it. I saw some tricks that maybe could do the job but I don't have the knowledge to choose one.
That's my first message here so I hope I didn't break the rules of the forum ^^ If you want any informations about my device to help me, just ask
Thanks a lot, and I hope my english is not too bad ! Have a good day.
Thanks
I got this message too without having any other problem with this TWRP version or Hairy Bean 2.2
The message appeared after flashing the new 4.2.1 (?) modded bootloader for Hairy Bean and the ROM itself.
I'm not sure whether the ROM or bootloader are causing it but mine got fixed by fixing the permissions via TWRP.
Thanks for the tip! :good:
In my case only re-partitioning helped.
for me uninstalling quadrant did the trick
That did it
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
Quick and easy. Worked for me. Thanks
devra1 said:
I found the answer in another thread. I used TWRP (Advanced - Fix Permissions). It was instantly fixed.
I took a full backup before trying this, but didn't need it.
Click to expand...
Click to collapse
This worked for me, too. Thank you.
My situation was a little bit different:
- Flashed Paranoid Android 3.99
- everything was fine (for a few reboots) until I made a nandroid back up with CWM 6.0.3.6 ( which was surprisingly slow, almost 1,5h)
- rebooted
- UID consistency problem
- tried to boot temporary into TWRP - NOT POSSIBLE!
- flashed TWRP 2.6.0.0 permanently
- TWRP: advanced - fix permissions: SUCCESSFUL!
Maybe I'll keep TWRP, but I'm used to CWM for years now.
CWM has removed "fix permissions" since 6.0.3.5 (http://review.cyanogenmod.org/#/c/45945/ )
Fix Permissions
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
edbertin said:
For me worked fixing permissions through TWRP on CM 10.2 latest nightly (10082013).
Click to expand...
Click to collapse
Me too! TWRP on SlimRom 4.3
Thanks
I am also having this issue after I flashed SlimBean Beta 4 Weekly-409 on my i9300 (wipe data/cache/dalvik and clean install with gapps) and tried restoring a couple of apps like Any do and Temple Run 2 with Titanium Backup.
Is the TWRP being referred here mean the TWRP manager? I installed it from play store but I don't find 'fix permissions' option anywhere in it.
I remember of seeing it in SuperSU but I am unable to install that as well as it says the binary needs to updated.
Could someone please help me here?
Thanks!
--IH
Confirmed. Get into the TWRP n do a fix cache wipe/dalvik wipe/fix permission
Thank you for clarifying this fix
polarfrz said:
Quick and easy. Worked for me. Thanks
Click to expand...
Click to collapse
I just updated my S4 to 10.1 Hyperdrive and experienced this very same issue. Rebooting into safestrap and fixing permissions cleared up this very annoying issue on my phone.
I flashed gummy V4.4 yesterday works great. I went into rom toolbox and changed LCD density to 361 and rebooted, got the UID inconsistent message.
found this thread, fix permissions in TWRP, all fixed. bing bang boom.
thanks all, I also fixed with TWRP latest version, and try to roll back to CWM
I installed a new ROM and I got the System UIDs inconsistent error, then my S Planner FC. I went to find the txt file and it stated that the problem is related to Calendar Storage. I deleted the apk and placed a new one back in. Problem persists, I scratched my head for so long and then I found this thread.
THANK YOU, fixing permission for the Calendar Storage did the trick! Thank God I found this thread!
My rooted, but otherwise standard N4 has been telling me it has downloaded the 4.3 update every couple of days since last week, but it won't install. All I get is a dead Android with a red triangle and the word Error! written above him. The phone then starts playing up, re-booting etc and I have to go into recovery and clear the cache for it to work properly again, still on 4.2.2 (obviously).
Now I'm not overly fussed about this update, but I do take issue with something that won't work taking up space in my phone (I'm tight and bought the 8GB one!), so my question is; can I get into where this duff download is being stored in my phone and delete it?
You should find it in /cache
yes, my ota update was in /cache folder; just use root manager or something similar.
Or un-root it, apply update, then re-root again. Win win.
Sent from my Nexus 4 using Tapatalk 4 Beta
Thanks for that, I deleted it!
I never even considered unrooting the phone first, to be honest, but it looks quite long winded to do. I assume there will soon be 4.3 ROM builds where that won't be necessary?
simonali68 said:
Thanks for that, I deleted it!
I never even considered unrooting the phone first, to be honest, but it looks quite long winded to do. I assume there will soon be 4.3 ROM builds where that won't be necessary?
Click to expand...
Click to collapse
You need the OTA to flash the new boot loader, but you can do it manually too so....not a big deal
Nexus 4+ Franco + LTE
Right, it has now downloaded for the 3rd time, so I'm not gonna bother deleting it again. Does anyone know a method of removing the notification?
joshuab227 said:
Finally managed to stop the update from downloading though ...
Heres what I did :
Installed Autorun Manager from the Play store.
Then entered its recommended advanced mode.
Went into the settings and enabled system entries and system app disable.
Disabled com.android.gsf.update.SystemUpdateService$Reciever under Google Service Framework
Hope this helps everyone else facing this problem and thanks to mikebz5 for the original post.
Sent from my Nexus 4
Click to expand...
Click to collapse
this is from another thread. Worked for me
That did the trick. Ta very muchly!
What. In. The. World. Got the "System update downloaded" notification this afternoon, and was puzzled since I got this a little over three weeks ago for 4.3, an experience that soft bricked my phone and ruined by life for a few days:
http://forum.xda-developers.com/showthread.php?t=2387196&page=3
Well, lo and behold, today's system update claims to be for 4.3 again:
Only I'm already ON 4.3.
Finally got everything rooted again and set up the way I want, and it's like Google knows it's time to come in and bork my phone again. I did a little poking and saw that this is no doubt the update from JWR66V to JWR66Y:
http://www.droid-life.com/2013/08/2...ta-updates-for-the-nexus-7-hspa-galaxy-nexus/
Only after the last experience, I'm friggin terrified to mess with this and possibly end up in a bootloop or stuck at the X screen forever again. (I'm rooted, no custom ROM, just custom launcher.) EDIT: I should add that, since the last update, I've updated my radios to be able to use 4G LTE, installed the Android browser and all my bookmarks, and made a slew of other customizations, so I'm annoyed that this update comes three weeks on the heels of everything I set up.
Should I try the OTA install or flash the OTA zip files in CWM recovery like the article suggests? Most pain-free ways to ensure my current setup is reinstated without too many gray hairs? Any suggestions welcome. Thanks in advance!
It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4
The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4
zephiK said:
The update is occurring because there is a new OTA that is build JWR66Y whereas yours is the V build.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, thanks--I noted that. My question at the bottom of my post is, what's the best way to ensure I can back up/capture all the customizations I made since so I don't have to go through the nightmare of trying to take three weeks to set everything up again?
spaceman860 said:
It won't install because your rooted. The new root method relies on the recovery from boot.p file in system that SU changes.
You can flash this update zip file that has been modified not to check that file http://forum.xda-developers.com/showthread.php?p=44886292
BLACKED OUT LTE N4
Click to expand...
Click to collapse
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.
nikonjunkie said:
OK...I'm guessing that notification will go away once I've flashed that ZIP? My real question is whether once that's done if I have to re-set everything up all over again or if there's a way to backup my new radios/browser/etc.
Click to expand...
Click to collapse
I have read your edits to the OP and you have changed system files so the update won't install. You modified the build prop for lte and browser app maybe other stuff too. With this update your OK with not having the correct radio.
BLACKED OUT LTE N4
Wugs tool never detects my Nexus 10, I tried everything (it did when I first rooted it). I'm on 4.2.2 but for some reason I can't update to the newer versions via OTA, it always fails. I'm rooted. I tried flashing a clean 4.2.2, which I got directly from Google, TWRP fails every time, even after a full wipe. I'm lost.
Does having the AOSP browser installed have anything to do with this? I mean having it installed so that even when I factory reset, it still there.
SRCP said:
Wugs tool never detects my Nexus 10, I tried everything (it did when I first rooted it). I'm on 4.2.2 but for some reason I can't update to the newer versions via OTA, it always fails. I'm rooted. I tried flashing a clean 4.2.2, which I got directly from Google, TWRP fails every time, even after a full wipe. I'm lost.
Does having the AOSP browser installed have anything to do with this? I mean having it installed so that even when I factory reset, it still there.
Click to expand...
Click to collapse
The browser has nothing to do with it, but I will suggest to skip the toolkit as too many people run into issues with these
http://forum.xda-developers.com/showthread.php?t=2670400
Have a look at this thread, 3rd post in particular, it will help you get back to stock and then if you wish root manually and flash any ROM from that point
demkantor said:
The browser has nothing to do with it, but I will suggest to skip the toolkit as too many people run into issues with these
http://forum.xda-developers.com/showthread.php?t=2670400
Have a look at this thread, 3rd post in particular, it will help you get back to stock and then if you wish root manually and flash any ROM from that point
Click to expand...
Click to collapse
Thanks, I'll try it today.