So it appears that some people (myself included) are having issues with their new Nexus 7. Specifically, where it is failing to install the second OTA update, which brings the tablet to version JSS15J. The first update (which is almost instant) works, but the second 50+MB one fails after rebooting into stock recovery.
It is failing because the file "/system/app/PrebuiltGmsCore.apk" is failing the sha1 checksum check. Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. I tried various standard work arounds but came up with no fix to get the OTA update, as is, to install. Then I decided to see if that was the only issue present and develop a work around.
I'm pleased to say that:
1) The PrebuiltGmsCore.apk file is the only one that breaks the OTA update. Everything else is fine.
2) I was successful in fixing this by creating a custom OTA update zip and installing it on my tablet.
3) I'm providing this modified update.zip for people to load on their tablets if they are having the same issue.
A couple of notes first...
Obviously, flash this at your own risk.
You NEED TO HAVE A CUSTOM RECOVERY for it to work. TWRP has already been ported over, so install that first.
Once you are in custom recovery, flash this file just like any other update.
Lastly, you should only download/install this if you are having the problem where the second OTA update fails. If you are currently running JSS15J, this update will fail (as it should).
This is 98% stock OTA update. All I did was some minor tweaks to fix the issue. Specifically:
1) I removed both the check for the PrebuiltGmsCore.apk file as well as the patching of it (since this fails).
2) I took the full JSS15J version of PrebuiltGmsCore.apk and built it directly into the update.
3) I removed the parts of the OTA update that mess with custom recovery. It will not install the /system/boot-from-recovery.p or /system/etc/install-recovery.sh files.
Once you install this, your tablet should be running identically to one that didn't suffer this issue.
Outside of using this, the only other option (AFAIK) is to wait until Google releases the full factory images and flash everything manually.
A big thanks to ATGAdmin for providing the stock JSS15J system dump that let me extract the updated PrebuiltGmsCore.apk file.
So without further ado, here is the update:
http://core.routed.com/JSS15J-Update.zip
Enjoy, and let me know if you have any questions.
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
shredder47 said:
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes.
And I bought mine from Best Buy, which seems to be a common denominator with both of those issues.
However, I just checked, and I have that wallpaper now after installing this update.
Yeah sounds like that's the common denominator... I'm out right now but I'll try this out when I get home, thanks man!
Sent from my Nexus 4 using xda app-developers app
Thanks so much! This worked for me after trying other options failed. Mine was from Best Buy also.
Oh, one other quick note:
As I wanted to leave this as close to the stock OTA update as possible, this WILL remove root. Technically, the 'su' binary will remain, but it will lose it's suid permissions. It will also remove the daemon launcher (which is installed as the install-recovery.sh file).
So make sure to flash the root zip after installing this update.
One more thing:
While there aren't many mods out there yet that will mess with the update, eventually there will be. This custom update will check and verify that everything else (except that one file) is stock. So if you made any other modifications to any other system file (ie: build.prop, etc.), it will fail just like any other OTA. Your best bet is to install this before tweaking.
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Nburnes said:
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
Click to expand...
Click to collapse
Awesome, glad to hear! And sure, that's perfectly fine with me.
It's on a 100Mb pipe, but the data center occasionally has some bad routing that makes certain destinations slow. Can't complain since I get a dedicated server for $59/month .
fosser2 said:
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, I believe it to be a minority of tablets. Maybe just a bad batch that all happened to get sent to Best Buy. As time goes on and more people get them we'll see how wide spread it is. I'm curious to see what Google's official fix will be.
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
paranoid android85 said:
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
phonic said:
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
Click to expand...
Click to collapse
I brick my nexus. Can someone upload nandroid backup please?
phonic said:
... Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. ...
Click to expand...
Click to collapse
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Bob Smith42 said:
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Click to expand...
Click to collapse
I'm not really sure. After looking at the first OTA update that oldblue910 posted, it definitely indicates that it was modified by that. If so, it had to have initially passed that first check. Why some units fail the second check makes little sense to me. The lack of the official wallpaper is also weird.
Additionally, that first OTA clearly shows that these devices were rushed. The fact that they were sent out with developer keys is just really bad QA.
My device, hardware wise, seems to be perfect. So I don't want to roll the dice and try to get another one, especially if the only issue is some minor software glitch that I already corrected. I haven't had a chance to really play with it yet, as I've been spending my time backing up/restoring files, so I'll see how it goes.
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
stab244 said:
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, you should reapply the root zip.
The OTA update does two things in this regard. It removes the two 'recovery recovery' files, and it also removes the suid bit from the su binary. The TWRP su fix will reapply the suid bit to 'su' (thus making it actually work), but it doesn't put back the SuperSU daemon launcher (/system/etc/install-recovery.sh). By applying the root zip again, it will fix both of these.
I thought about removing the part of the update that deletes this file, but again I wanted to keep it as stock as possible. Also, for people who hadn't rooted yet but do have a custom recovery, it would help keep it custom and not require them to manually remove those files that would (stock) reset the recovery back.
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
xene97 said:
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
Click to expand...
Click to collapse
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
phonic said:
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
Click to expand...
Click to collapse
Thanks for the clarification!
Related
Hey folks,
maybe someone can help me.
In the morning on my A500 appeared an update available message. I tried to install it, but it failed in the middle. So I got a brick, which I solved with the chinese update. Afterwards I pushed my saved system.img.
BUT: Now the Build Number says Acer_A500_1.112. instead of Acer_A500_1.112.01_EMEA_CUS7
I checked the build.prop but there the correct build number is written.
Also another check of update gimme the message, that my system is up-to-date.
Is anyone able to provide help, like EMEA flexrom.img, boot.img, or some useful advises?
There is a EMEA signed update.zip floating around. Try to restore with that one and see what happens.
I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?
gotta push flexrom
You gotta push your flexrom image onto the tablet too then "FACTORY RESET". The flexrom (mmcblk0p6) has the information of the update... that is where you are getting the difference from (if i am not mistaken)...
Try that and see if it helps ... I believe it should... jejeje
xo96 said:
I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?
Click to expand...
Click to collapse
Nope, mine was rooted with gingerbreak 1.20 and worked fine.
did you delete/rename any phone apks???
or delete/rename any stock software???
I have not messed or removed anything, was rooted, root-explorer/titanium loaded and updated without issue.
reran gingerbreak afterwords and all is well....
Have never seen any OTA update in Australia :|
Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)
ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje
threedfreek said:
Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)
Click to expand...
Click to collapse
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.
Another thing that can cause the update to hang would be any edits to your build.prop (ie. Netflix early fixes, etc). Changing back to the original resolved the triangular fail icon for me and completed the update with root still installed, gingerbreak did have to be I installed again but root is still attainable.
Sent from my A500 using XDA Premium App
Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.
fcmugen said:
Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.
Click to expand...
Click to collapse
You are correct, there is a thread in the general fourm with a link to all the apk's that came stock on the system.
I can't post links yet, but either thread about the OTA update you will find your required apk's.
mapaz04 said:
ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje
Click to expand...
Click to collapse
Full charge, 3 hours... phone 40pct... overall so far more laggy.. nice update
daveid said:
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.
Click to expand...
Click to collapse
Alright... how long has that been there? THANKS!!!
I have the /system/app folder uploaded if u need it... Here is the link...
http://forum.ppcgeeks.com/acer-iconia-a500/143826-system-app-recovery-acer-a500-iconia-tablet.html
Sent from my T7575 using Board Express
Reset back to stock and still cant update.
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?
Where u @ gravy? Some people still haven't gotten the update yet. I didn't get it this morning when I tried but am hoping I get it tonite when I get home... jejeje
PS... I'm in tennessee
Sent from my T7575 using Board Express
I was having all kinds of problems not getting the update to run and kept Triangle halt..
I resolved it by the following:
you dont need to do anything with Gingerbreak, its ok. The problem is for those that changed any system files. In my case, i wanted exchange, so i was using a different email.apk, well as learned from another thread here, if you look in Cache/recovery/logs, you will see a file where you can see where the update went wrong. Like i said, in my case, i saw the file size was not what was expected for email.apk. I removed the exchange account, used rootexp and renamed email.apk.old (the original) to email.apk and the obex file then the update worked correctly.
I was going crazy as i was messing with this instead of watching my heat vs the bulls 1st half.
gravyplaya said:
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?
Click to expand...
Click to collapse
look at your /Cache/recovery/logs for an error and post results
I had to try about 7-8 times looking in the recovery log after each time to see what .apk that i forgot that I had deleted, then put it back and try again. I finally was successful and haven't seen much difference other than no random wake ups. Maybe a little snappier.
I had mine hang in recovery every unsuccessful update which is NOT THE SAME AS BRICKING.
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
GAKB said:
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
Click to expand...
Click to collapse
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Solution
ceefercat said:
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Click to expand...
Click to collapse
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
It's worth a try!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
That's fair enough, I tried a factory reset first myself to no avail. If you do get your nexus replaced, please let me know if the update works!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
I'm considering taking it back because it is not updating as it is supposed to, as it is designed to. A message comes up on the screen that a system update is available. I go through the procedure to download and install said update. The update doesn't install, though the system now says that it is up-to-date.
Bootloader? I don't even know what that is. I don't know that the problem is caused by the bootloader and neither do you. It may be a joke to you but to me its just a pain in the neck.
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
Bootloader issues are a pain in the neck. My bootloader is locked and i cannot erase, flash, format ANYTHING on my Nexus 7... :S
Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
obviously the guy doesn't have working knowledge of ADB, rooting/unlocking or any other development terms we use to describe what we are doing to our devices.
The only jokable premise here is some nerd in his mother's basement thumbing his nose at random people because the world he lives in is so narrow it couldn't possibly comprehend the existence of someone honestly asking for advice and then doing the only logical thing he can think of to do as a consumer unfamiliar with a product at a developmental standpoint.
Not everyone wants to root. And not everyone who owns a Nexus has background experience in tinkering with electronics. I've been rooting since my Dinc and I actually want to keep mine as stock as possible. I find more problems come to me when I start messing with the device instead of just leaving it alone.
---------- Post added at 12:58 AM ---------- Previous post was at 12:46 AM ----------
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I appreciate the fix. trying it out now to see if I can get stock 4.2 to update properly
Edit: Worked like a charm thanks bro for the advice
just wondering if anyone else has received this update? it was a small 17.18MB. not sure exactly what it did. still on 4.2.1 attached is a screen shot.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
kurtis.austin2 said:
just wondering if anyone else has received this update? it was a small 17.18MB. not sure exactly what it did. still on 4.2.1 attached is a screen shot.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Just checked after reading this and downloading it now ota. It says it for system stability. About to install we'll see.
wonderful, so i'm not dreaming that it just happened. i just got home from a 12 hour day at work, and opened up my tablet and the notification was there waiting for me. don't know where to check on the asus website for change log or anything?
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
kurtis.austin2 said:
wonderful, so i'm not dreaming that it just happened. i just got home from a 12 hour day at work, and opened up my tablet and the notification was there waiting for me. don't know where to check on the asus website for change log or anything?
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
Yea just installed ok. Haven't gotten into it to if there were much changes yet. Probably nothing immediately noticeable except it reoptimizes the apps on first start up. If looking for log here's the site but doesn't yet look like it was posted and probably won't be for couple days but when does can check here.
http://support.asus.com/download.as...300T&p=28&s=1&os=32&hashedid=8BmzkQ4yoz5WzBrW
The other things to check is to see if motochopper and other root methods work and if any one loses root we'll have to see if any one with root by motochopper method loses it which tell you truth probably not too much danger in that as it's only a minor update. I'm still waiting to root myself but would like to see what happens? If some one tries to root after the update if any thing changed.
System update failure
I received a notification of an update which I downloaded and told the system to apply. It shut down the system and began the update and then failed with a dead android with a red explanation point and the message update failed.
I rebooted my tablet and got a message that the original configuration was restored.
If anyone has had success in applying the update (US version) please let me know where I can get a valid copy to try. The links to the Asus site seem to point to the old 4.2.1 version.
Thanks.
Who can lay out an update?
tomlogan1 said:
I received a notification of an update which I downloaded and told the system to apply. It shut down the system and began the update and then failed with a dead android with a red explanation point and the message update failed.
I rebooted my tablet and got a message that the original configuration was restored.
If anyone has had success in applying the update (US version) please let me know where I can get a valid copy to try. The links to the Asus site seem to point to the old 4.2.1 version.
Thanks.
Click to expand...
Click to collapse
Sorry to hear that but it'll be on asus website it just takes them a couple days to a week or so to post it. Were you rooted by perhapse the motochopper method. There's cases if there are frozen apps and etc and if everythings not back in place as in normal use it would fail. Not sure it always applies but have heard of this. Also not sure if you want to try a factory reset and see if you get a prompt for the update again again works in some cases but not always and if that doesn't work the last thing you can do is if your not unlocked and can still get otas is to downgrade back to 4.1.1 and just go through update process again after it reboot the downgrade.
I wonder if the update addresses some of the issues we have been experiencing, random reboots, bluetooth permissions issue. There are a couple others that were brought up on the CROMI ROM thread.
On a stock firmware no random reboots, it only on CROMI
Updated (europe). All good. I had to do a 'restore root' and reboot twice with Voodoo OTA, to successfully restore root.
I am on the 4.1 style launcher and I noticed the clock font (bottom-right) has changed in this update. Looks bold and condensed now. Obviously this hints to more than just stability changes. Anyone on the 4.2 style launcher? I am curious to see if it has been improved in this update.
ASUS TF300T Firmware Update v10.6.1.15.3
I'm running it now, checked online for release notes before installing but found nothing but this thread so screw it, I just installed.
I'm not rooted as I don't want to void my warranty just yet and I'm cool with the stock rom.
I did switch to stock 4.2 launcher before installing the update to see if any changes there as Evan_ was curious.
Don't like 4.2 launcher myself because of the location of the buttons swap to middle and the ASUS Custom settings bar is odd to me.
Anyways, its running and I'll check back in if I find any changes.
Successful System Update
JOP40D.US_epad-10.6.1.15.3-20130416
Noticed Time & Date in status bar drop-down. (Don't recall that shown)
Switching back to 4.1 Launcher. (Prefer it as configuration is better, I hate the back button in the middle on 4.2.)
Noticed a Font change for the clock and all the stock ASUS widgets.
Once again tbdawg has been kind enough to provide the new firmware download for those who didn't receive it.
Please see post #234 0f this thread and give him a thanks!
Here is the link for the download. - dlpkgfile_4.2.1_Update2
tobdaryl said:
Once again tbdawg has been kind enough to provide the new firmware download for those who didn't receive it.
Please see post #234 0f this thread and give him a thanks!
Here is the link for the download. - dlpkgfile_4.2.1_Update2
Click to expand...
Click to collapse
Thanks for the link. What is the process to manually install this update? I have only done the OTA updates. I am rooted, but otherwise stock.
tomlogan1 said:
Thanks for the link. What is the process to manually install this update? I have only done the OTA updates. I am rooted, but otherwise stock.
Click to expand...
Click to collapse
This post courtesy of atzhory
dlpkgfile install manual for unlocked dev
http://forum.xda-developers.com/show....php?t=1803090
Manually update rooted stock
tobdaryl said:
This post courtesy of atzhory
dlpkgfile install manual for unlocked dev
http://forum.xda-developers.com/show....php?t=1803090
Click to expand...
Click to collapse
I have placed the update file on a MicroSD card and the tablet just wants to unzip it It shows the zip file then the following:
FOLDER META-INF
FOLDER patch
FOLDER system
blob
At the bottom of the screen there are options to
Cancel Text encoding Extract
I am not sure how to proceed.
Thanks
tomlogan1 said:
I have placed the update file on a MicroSD card and the tablet just wants to unzip it It shows the zip file then the following:
FOLDER META-INF
FOLDER patch
FOLDER system
blob
At the bottom of the screen there are options to
Cancel Text encoding Extract
I am not sure how to proceed.
Thanks
Click to expand...
Click to collapse
I'm having trouble myself. This had worked in the past but is failing on this update.
I'll update you when I find the answer. I am feverishly searching.
Alexey71 said:
On a stock firmware no random reboots, it only on CROMI
Click to expand...
Click to collapse
No read the Q%A section, a lot of people were complaining about how horrible the OTA update was .
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
aerdely said:
Sorry to hear that but it'll be on asus website it just takes them a couple days to a week or so to post it. Were you rooted by perhapse the motochopper method. There's cases if there are frozen apps and etc and if everythings not back in place as in normal use it would fail. Not sure it always applies but have heard of this. Also not sure if you want to try a factory reset and see if you get a prompt for the update again again works in some cases but not always and if that doesn't work the last thing you can do is if your not unlocked and can still get otas is to downgrade back to 4.1.1 and just go through update process again after it reboot the downgrade.
Click to expand...
Click to collapse
Since I am not unlocked, what is the process to downgrade to 4.1.1? Every attempt to upgrade from the MicroSD have failed, and, yes, I have tried multiple MicroSD cards from 4 GB to 32 GB and had failures in each instance.
Thanks.
tomlogan1 said:
Since I am not unlocked, what is the process to downgrade to 4.1.1? Every attempt to upgrade from the MicroSD have failed, and, yes, I have tried multiple MicroSD cards from 4 GB to 32 GB and had failures in each instance.
Thanks.
Click to expand...
Click to collapse
Really no need for sdcard. As long as you downloaded the 10.4.2.20 firmware from asus website in my case I didn't have to rename it. Just download and unzipped once and placed on root internal memory. You can just initiate the update by either inserting or removing the sdcard if it on root of internal. Just to be safe after unzipping once make sure it's name {US_epad-user-10.4.2.20.zip} or depending on firmware version put WW or CN and etc. In place of US. Should pick it right up.
Just to be clear are you trying to upgrade or downgrade?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
aerdely said:
Really no need for sdcard. As long as you downloaded the 10.4.2.20 firmware from asus website in my case I didn't have to rename it. Just download and unzipped once and placed on root internal memory. You can just initiate the update by either inserting or removing the sdcard if it on root of internal. Just to be safe after unzipping once make sure it's name {US_epad-user-10.4.2.20.zip} or depending on firmware version put WW or CN and etc. In place of US. Should pick it right up.
Just to be clear are you trying to upgrade or downgrade?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I was attempting to get the new OTA upgrade that failed on my tablet. Found out something interesting about this upgrade approach. If I put in an upgrade of the same level like 10.6.x.x and was already at 10.6.x.x the system ignored it. But if I put in 10.4.x.x the system identified it and offered to do a downgrade, but would have erased everything and I wasn't ready to do that, but I may have to do so.
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tobdaryl said:
I'm having trouble myself. This had worked in the past but is failing on this update.
I'll update you when I find the answer. I am feverishly searching.
Click to expand...
Click to collapse
I have tried the SD card upgrade method with no luck but found that if I put in a lower level like 10.4.x.x the system saw it as a downgrade and would downgrade the system but would erase all my data, which I was not ready to do, but at least I have a path to should I so select.
Sorry for the caps everyone, but THIS IS IMPORTANT! People like myself and TheManii who keep track of OTA updates for Nexus devices need this information!!
When you first turn on your N7, the minute you connect it to WiFi, it will do a force OTA update that you CANNOT defer.
Before you boot up your N7 for the first time, could someone please do the following steps:
1. Boot into fastboot mode by holding down volume down while you power it on.
2. Unlock the bootloader with "fastboot oem unlock"
3. Boot up TWRP for the new N7 using "fastboot boot twrp.img". Please DO NOT use "fastboot flash recovery twrp.img" because that will overwrite the stock recovery.
4. Do a full Nandroid backup.
5. Post the Nandroid somewhere for us.
6. Have our eternal gratitude.
We would be most appreciative. Thank you!
oldblue910 said:
Sorry for the caps everyone, but THIS IS IMPORTANT! People like myself and TheManii who keep track of OTA updates for Nexus devices need this information!!
When you first turn on your N7, the minute you connect it to WiFi, it will do a force OTA update that you CANNOT defer. Before you boot up your N7 for the first time, could someone please boot straight into fastboot mode, unlock, flash TWRP and get two pieces of info:
1. The bootloader version displayed on screen in fastboot mode.
2. The build.prop file in /system. You can pull that via adb once you boot into TWRP.
3. Totally optional, but we wouldn't complain if you would do a full nandroid backup of the ROM and post it somewhere.
We would be most appreciative. Thank you!
Click to expand...
Click to collapse
Hey, I'm just down the road in Raleigh, I can bring my new Nexus 7 16GB to a local Starbucks if you want to do this yourself. I have it fully charged but not yet turned on. Send me a PM and I'll give you my phone #, email.
Thought you were going to be here, anyway I posted the 2nd update, JWR66N to JSS15J, here (if it helps in anyway)
http://forum.xda-developers.com/showpost.php?p=43984053&postcount=5
Edit: See that you already have it on your Razor page!
Bob Smith42 said:
Hey, I'm just down the road in Raleigh, I can bring my new Nexus 7 16GB to a local Starbucks if you want to do this yourself. I have it fully charged but not yet turned on. Send me a PM and I'll give you my phone #, email.
Click to expand...
Click to collapse
Dude, PM me. I'm on it.
If this isn't done by the time I get mine tomorrow, I'll get it done
Sent from my Nexus 7 using Tapatalk HD
Flippy125 said:
If this isn't done by the time I get mine tomorrow, I'll get it done
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks, but BobSmith came to the rescue. I met him at a McDonalds and got everything. What happened is that somebody at Google messed up big time. The ROM that comes preloaded on the N7 is 4.3/JWR66N, but it's erroneously signed with development keys and not release keys. This is a huge problem, of course, since lots of apps that rely on DRM won't work right on dev-keys ROMs. So this forced OTA update simply updates you from JWR66N/dev-keys to JWR66N/release-keys. We don't know the URL to the OTA file since it's not in the normal place on Google's servers, but I managed to get the OTA update file out of /cache on BobSmith's device. The OTA file is available on http://randomphantasmagoria.com/firmware/nexus-7/razor.
Interesting.
Thank you for sharing that first OTA. I found something interesting...
If you hadn't heard, some of the new Nexus 7s, particularly those at Best Buy, are failing on the second OTA update due to a sha1sum mismatch on PrebuiltGmsCore.apk. According to the first OTA update, it too patches that file.
Looking at OTA1 and OTA2, it looks like it was supposed to go:
9392ccc5b4753684b73adf89b790b607f6a29388 -> f6193294456e67aad2a2d7e5ae03a2865d8544f6 -> 8e01a021b1edcfcc31266bc3193dec82c601f0bd
from out of the box -> OTA1 -> OTA2.
But in my case, and others, the sha1sum was something else (starting with 123 IIRC).
It's weird that the first OTA would verify and patch the file, which means it had to have the original 9392... sha1sum, but then fail on the second update. I wonder what would have caused it to break, and why it's only affecting a handful of devices.
phonic said:
Interesting.
Thank you for sharing that first OTA. I found something interesting...
If you hadn't heard, some of the new Nexus 7s, particularly those at Best Buy, are failing on the second OTA update due to a sha1sum mismatch on PrebuiltGmsCore.apk. According to the first OTA update, it too patches that file.
Looking at OTA1 and OTA2, it looks like it was supposed to go:
9392ccc5b4753684b73adf89b790b607f6a29388 -> f6193294456e67aad2a2d7e5ae03a2865d8544f6 -> 8e01a021b1edcfcc31266bc3193dec82c601f0bd
from out of the box -> OTA1 -> OTA2.
But in my case, and others, the sha1sum was something else (starting with 123 IIRC).
It's weird that the first OTA would verify and patch the file, which means it had to have the original 9392... sha1sum, but then fail on the second update. I wonder what would have caused it to break, and why it's only affecting a handful of devices.
Click to expand...
Click to collapse
I hadn't heard that, but that's very interesting. I wonder if we're going to see a new OTA from Google soon that has a full version of that file rather than a patch. It's happened in the past.
oldblue910 said:
I hadn't heard that, but that's very interesting. I wonder if we're going to see a new OTA from Google soon that has a full version of that file rather than a patch. It's happened in the past.
Click to expand...
Click to collapse
I made my own
http://forum.xda-developers.com/showthread.php?t=2380258
Fortunately, someone was kind enough to make a backup of a JSS15J that I was able to pull that file from.
On a completely unrelated note, does anyone have any idea why I am unable to access apk.gz backup files from TiBu? I'm trying to copy my apps from my old N7 to the new one, but am running into a very weird issue. Nothing I've tried (including adb pull) seems to be able to access them. I can move/delete the files, and I can make TiBu recreate them from scratch, but I can't copy them off of the device or even to another directory. I tried making a backup with tar via the shell, but that fails too. I can't even cat the file:
-rw-rw-r-- root sdcard_rw 2550494 2013-07-27 00:13 stericson.busybox-05fe3b964848cdb5fb3c07890734e899.apk.gz
sh: cat: stericson.busybox-05fe3b964848cdb5fb3c07890734e899.apk.gz: Permission denied
The properties and data files are not affected by this, only the apk.gz files...
This reminds me of the weird issue with the earlier versions of custom recovery, where you could make nandroid backups but couldn't delete them.
---------- Post added at 12:52 AM ---------- Previous post was at 12:43 AM ----------
NM. I changed the directory TiBu was using and I can access the new backups now. Instead of using /storage/emulated/0/TitaniumBackup, I now have it as /sdcard/TitaniumBackup.
Six in one hand, half a dozen in the other.
Weird bug....
We still need a dump of JWR66N/dev-keys (or specifically just /system)
The JWR66N/dev-keys -> JWR66N ota doesnt touch anything beyond stuff in /system.
As I already have a complete dump of JWR66N, I can regenerate a complete dump of JWR66N/dev-keys if i had a dump of it's /system.
While I dont expect it to be terribly useful for anyone, I like to collect these things for historical purposes.
What you have to do is make a nandroid before letting it connect to wifi and updating.
I do as soon as get mine pm me if need it
Sent from my LT28h using xda premium
tejasvi1 said:
I do as soon as get mine pm me if need it
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
I'm all set now thanks to BobSmith42. Thanks, though.
oldblue910 said:
Thanks, but BobSmith came to the rescue. I met him at a McDonalds and got everything. What happened is that somebody at Google messed up big time. The ROM that comes preloaded on the N7 is 4.3/JWR66N, but it's erroneously signed with development keys and not release keys. This is a huge problem, of course, since lots of apps that rely on DRM won't work right on dev-keys ROMs. So this forced OTA update simply updates you from JWR66N/dev-keys to JWR66N/release-keys. We don't know the URL to the OTA file since it's not in the normal place on Google's servers, but I managed to get the OTA update file out of /cache on BobSmith's device. The OTA file is available on http://randomphantasmagoria.com/firmware/nexus-7/razor.
Click to expand...
Click to collapse
so if the Forced OTA patches the Dev signed keys to Release Keys then why do you /we need the Nandroid dump BEFORE the patches? what will that do for you/us considering that after the OTAs we are fine and wont have any issues?
nextelbuddy said:
so if the Forced OTA patches the Dev signed keys to Release Keys then why do you /we need the Nandroid dump BEFORE the patches? what will that do for you/us considering that after the OTAs we are fine and wont have any issues?
Click to expand...
Click to collapse
It's more just for archival purposes to have the JWR66N/dev-keys ROM since there will never be any factory images released. Plus, it's good for seeing exactly what was changed between the devkeys and releasekeys ROMs.
good job bob
Please someone provide a stock Jwr66n build.
I had to manually check, but it's here on my phone .
For some reason the screenshot wouldn't upload, so here it is on imgur.
http://imgur.com/a/09FTqvK
Yep. Here in the Seattle area, the Verizon Android 10 update is here for the Moto Z4. Update went without a hitch...phone runs well and smoothly.
Anyone know how to get rid of this? It just started after the updated lol.
I think they put that there to remind us that once Android 11 is released, we'll be stuck on Android 10.
jwhistler said:
I think they put that there to remind us that once Android 11 is released, we'll be stuck on Android 10.
Click to expand...
Click to collapse
?. Trolled by Moto lol
slaytanic said:
Anyone know how to get rid of this? It just started after the updated lol.
Click to expand...
Click to collapse
It's there because developer tools are enabled, if you turn them off that message disappears.
I had the update last week, but was waiting for it to come up on Software update center since I have retail version, but now update is gone and it hasn't been released on the update center.
Could someone pull the update and post it here for the rest of us to manually update??
There is a new one today, it said critical, and applied itself, no option to delay it, it's called Update 5+.
I agree we really need the system image for this update. My phone will not update using the update system option, it only tells me it's already up to date. I tried using the tool from Verizon, same thing, up to date. I called verizon, after the second tech they want to send a new phone. But I don't really want a new phone. Also they had me do a factory reset just to be sure. I had a lot of apps disabled, and had other modifications through adb. Turns out those weren't the issue.
Pretty Please with Sugar on Top.
I'm sure all it would take is for someone to use the Verizon update tool or whatever it's called and select reinstall but keep my days then it'll download and extract. You just have to grab it once it starts extracting the zip and copy it somewhere so that when it finishs extracting it doesn't get removed. The app deletes the system image/zip when it finishes extracting. You could also unplug your phone when it starts extracting and it would touch your device.
Edit...... Then upload it anywhere.
This is an excellent idea, however it'll only work for people already on 10. Myself and others cannot update neither OTA or using the update tool. Using this aforementioned method of extraction would be absolutely fabulous, and I myself would buy some beers for anyone that would pull the update whatever way they can and upload???
Just manually checked and the update was there. I didn't think of it but there used to be an app that a Dev put out for Moto phones that would copy the update. Probably to old to work anymore though.
I did the same thing a couple days ago.
It's finally in the repository
shane1 said:
Just manually checked and the update was there. I didn't think of it but there used to be an app that a Dev put out for Moto phones that would copy the update. Probably to old to work anymore though.
Click to expand...
Click to collapse
Ive used LMSA (lenovo motorola smart assistant). Just set the download folder to someplace you recognize, then copy it out of that folder before lmsa extracts the zip
There is a new update, QDFS30.130-42-1-2, or System Update 6, installing now
Edit: It's May 1st security patch
moxtrom said:
There is a new update, QDFS30.130-42-1-2, or System Update 6, installing now
Edit: It's May 1st security patch
Click to expand...
Click to collapse
Be careful that build of Android 10 has problems with blue tooth according to forums.motorola.com.
pan815kev said:
Be careful that build of Android 10 has problems with blue tooth according to forums.motorola.com.
Click to expand...
Click to collapse
%#*%^$^%$#$(&!! I've been scouring the web all evening trying to figure out why my bluetooth stopped functioning recently...all worked fine until this new update that came across on my phone yesterday. I haven't been able to find any info on this, I was starting to think I was the only one having issues after that update. Is there a fix for this?