An OTA software update was just pushed through the Virgin network last night and my phone notified me of it. It's version N98101.0B10, the details of which can be found here. However, being the semi-noob that I am, when I first got the phone and rooted it, I did some minor modifications (added .bak to the boot sound) and also deleted, instead for just freezing, the bloatware.
I (now) know that it's a good idea to change these things back before trying to install an OTA update and to freeze, not uninstall, bloatware because of this. But since I deleted them, I can't. Sure enough, when I tried to install the update, it failed, with the message saying that it couldn't find the Real Racing 3 apk, a bloatware game that was installed with the Virgin Mobile purchase.
I rebooted out of the install and all's good function-wise (no brick or anything). But the OTA update notification is gone, and the phone says I have the latest SW version when I try manually updating it through system preferences, even though I still have the old version listed (N98101.0BO6).
So, am I SOL on the SW update? Or is there a way for me to get it again, restore my phone, and install it?
If someone gets the OTA notice and allows it to download, then copies the zip from /cache to their sdcard before letting it do the update, I can make a flashable updater.
Wow I never seen that . I think if u hit update in the selection it should return if not u may need to do a factory data reset. That may get the push again
Wow I never seen that . I think if u hit update in the selection it should return if not u may need to do a factory data reset. That may get the push again
Yeah it was really dumb. I was in my file browser and was going to copy the update file and save it to my sd card but deleted the file instead. I tried checking for update again but no luck, it said Your system is up to date. I also did factory data reset and still no luck, says same thing. No choice but to wait now.
Yeah it was really dumb. I was in my file browser and was going to copy the update file and save it to my sd card but deleted the file instead. I tried checking for update again but no luck, it said Your system is up to date. I also did factory data reset and still no luck, says same thing. No choice but to wait now.
3a. Go to settings > apps > all > Google Services Frameworks
3b. Clear data and Force Stop Google Services Framework
3c. Go to settings > system update > Update ZTE software
3d. Retry steps 3a - 3c until you get the update
edit: actually, the best thing would be if you go back to stock, grab the update zip, and then let it update. I need the update zip and a new system dump and boot.img after the update.
Update: I was able to download update but get
assert failed: apply_patch_check("/system/app/SprintZone.apk",....
When I try to install it. I guess since I uninstalled the app and reinstalled it changed the last modified date. Sucks, i Actually backed up all these apps then deleted them using titanium backup thinking it would not change anything when I need to reinstall. I'm on stock and rooted. Any suggestions?
Update: I was able to download update but get
assert failed: apply_patch_check("/system/app/SprintZone.apk",....
When I try to install it. I guess since I uninstalled the app and reinstalled it changed the last modified date. Sucks, i Actually backed up all these apps then deleted them using titanium backup thinking it would not change anything when I need to reinstall. I'm on stock and rooted. Any suggestions?
Please upload the update zip file. The reason it failed is because you don't have SprintZone.apk or the file itself has changed somehow. The update checks the md5 sum of each file and if they do not match the originals the update will fail. It will also fail if you have cwm installed because it checks the partitions as well.
There is another problem. The stock roms are made from supreme, not vital. That means there will be files missing and the update won't work since they are patches to existing files. We are left with 2 options.
1) Someone that has not modified their vital /system directory can upload it and boot.img and i can make a vital unmodified stock rom which can be updated.
2) Someone that has not modified their vital /system directory can update and upload a new system.img and boot.img so i can make new stock roms.
Sadly, updates are where the supreme/vital are not compatible.
edit: just looked at the update and it is not a new android version, just updates some files and partitions
Ah man that sucks. Only one I know that has a Vital around here is Steve Stone. He may be our only hope...
As far as the update, you think it might me an update before the version update? I remember they did that for my tablet a while back. They sent an update to fix some things then sent out another update for the android version.
I flashed virgin system.img on my phone.. It act same like it was before.. nothing changed.. so provider data is in carrier partition.. i did rtn by mistakely so no wifi direct or hotspot option was available. so i thought of flashing virgin system.img but it was all same, like i am using same sprint vital.
@stevestone there is not a system.img in the vital link you posted above. In order for a vital to update successfully, we need a full stock vital system.img. The exact same files, every single one, or the updater will fail. This update is a pile of patches so if the files it tries to patch changed or do not exist it will fail.
I was semi-disappointed too when I saw that they were patches and not a new OS, but looking at the details in the link I provided in the OP, some of the patches actually may fix some annoying issues I've been having with my phone.
So, given the situation I described, what's my best course of action? Backup apps via Titanium Backup, do a factory data reset, download the patches from Mancow's link, apply them, reroot, and then restore the apps? Or is there an easier way?
I was semi-disappointed too when I saw that they were patches and not a new OS, but looking at the details in the link I provided in the OP, some of the patches actually may fix some annoying issues I've been having with my phone.
So, given the situation I described, what's my best course of action? Backup apps via Titanium Backup, do a factory data reset, download the patches from Mancow's link, apply them, reroot, and then restore the apps? Or is there an easier way?
Is your device deodexed? If not, post a list of every file you have in the /system/app directory. This is assuming you have not removed files from anywhere else. If you have, list all the files that you do have in those directories too. I can remove the asserts for the files you don't have and make a new update zip. It will take me some time to sort through it but it should work. Make sure you are running vital software and not supreme because even the files you have won't update otherwise.
edit: if you have changed your boot.img you will need to flash the stock one. The update patches it too so you are probably getting a new kernel. If it is not stock vital boot.img, the update will fail.
Semi-noob so I'm unaware of deodexing. But, looked it up, and since I have .odex files in my /system/app folder and didn't flash a new ROM or do anything explicitly to deodex, I think my answer is "no."
If not, post a list of every file you have in the /system/app directory.
I've only made two other modifications to my knowledge.
First, to stop the somewhat common problem of a ridiculously expanding .thumbnails file, I did a trick by deleting the files in /storage/sdcard0/DCIM/.thumbnails, replacing them with empty files of the same name as those that were just deleted using touch, and then changed permissions so that they couldn't be written upon, which solved the problem. Here's the list of the files in that directory, including permissions:
----r-xr-x system sdcard_rw 0 2014-02-16 03:23 .thumbdata3--1967290299
----r-xr-x system sdcard_rw 0 2014-02-16 03:11 .thumbdata3-1763508120
Finally, I added ".bak" to the boot sound in /system/etc to stop the annoying boot sound from happening. The contents of that folder is under the spoiler:
As far as I know, the bloatware I removed (e.g. Real Racing, the Virgin Mobile apps, and more) didn't come from anywhere else, but I'm afraid I can't recall how I removed them. I think I used Root Uninstaller once rooted, but I'm not 100% sure.
I can remove the asserts for the files you don't have and make a new update zip. It will take me some time to sort through it but it should work. Make sure you are running vital software and not supreme because even the files you have won't update otherwise.
How do I do that? I did purchase a Supreme from Virgin Mobile.
edit: if you have changed your boot.img you will need to flash the stock one. The update patches it too so you are probably getting a new kernel. If it is not stock vital boot.img, the update will fail.
Ok great. It sounds like we can make this work since you are running vital software, it's odexed, and you provided the list. I will sort through the updater-script in the update.zip and remove the parts you don't have. You will need to change the boot sound back to normal for the update because it is patched. The other mods you made should be fine...i think.
@CmplxAdSys The repacked update zip is uploading. Before I post it, I want to be sure you will share the new system.img and boot.img after the update to help others. This repack i made may not work for others as it is based on your missing files, not anyone elses. If you share the images i can make new roms so everyone can enjoy
Hey SuperR, so I have reverted back to stock with recovery by flashing the quantum stock B06 with recovery zip. I tried to update but now is says
assert failed: apply_patch_check("/system/app/DSS.apk",....
I have noticed that the modified dates on the apks are different than original. Before it was something like Jun 2013, maybe somebody can check and get the exact date and time, but now they say Aug 01, 2008 07:00:00 AM. Could this be the reason why it stops the update? Is there a way to change the modified dates to how they were before?
Or, is there a way to change the update so that it doesn't check with the patches completely?
Hey SuperR, so I have reverted back to stock with recovery by flashing the quantum stock B06 with recovery zip. I tried to update but now is says
assert failed: apply_patch_check("/system/app/DSS.apk",....
I have noticed that the modified dates on the apks are different than original. Before it was something like Jun 2013, maybe somebody can check and get the exact date and time, but now they say Aug 01, 2008 07:00:00 AM. Could this be the reason why it stops the update? Is there a way to change the modified dates to how they were before?
Or, is there a way to change the update so that it doesn't check with the patches completely?
I believe that is my fault lol. I probably zipaligned the "unmodified" stock rom which changes the files if they are not already zipaligned. With the help of CmplxAdSys, I am hoping to get the updated files and put together a new rom for you.
edit: maybe it's not my fault after all. The stock rom is for the supreme, not vital so the vital update will not work using the supreme stock rom.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
