EDIT: WIFI ONLY - Not the LTE Version!
Title says it all. Hope this saves someone hours of searching for it like I did before giving up and pulling it from the stock JSS15R image. I know we should all make backups but life happens. This is for all of you [like myself] who found you could not upgrade to Stock 4.4 because of changes to your build.prop file.
In my case I forgot to uninstall a custom framework I had installed on a stock 4.3 image [root but stock recovery] and the 4.4 OTA failed. I never got another prompt to try again from Google so after removing the framework I downloaded the image manually and tried to install it through ADB. Again it failed this time telling me the file build.prop had the wrong checksum. The framework had restored the build.prop but the file checksum was off. The one below was pulled from the original stock image using ext4_unpack. I copied it to my system folder over the "original" and ran the update again. Worked like a charm.
If you run into the same issues try the stock file above. We really should just start a repository for these stock build.prop files.
Related
Here's the deal...I downloaded youtube v2.4.4 from here. I opened it in 7zip and extracted the res folder so I could re-theme it. I made my changes then put the res folder back into the original apk. Now this is where the problem occurs. I can't for the life of me figure out how to re-sign the .apk! I have tried every single apk-signer out there to no avail. I have put it in apkManager then decompiled it optimized PNGs recompiled then signed then zipaligned but EVERY time I install it on my phone I get either "Application not installed." or "There is a problem parsing the package." I have uninstalled all versions already on my phone through Titanium Backup prior to installing my themed one. I have manually put it in /System/app and changed permissions and rebooted. NOTHING I do works. I have adb and java installed and in the PATH. I have tried every possible solution I have found on the internet and none work. Any help would be appreciated. Thank You!
P.S. I have an HTC Thunderbolt running the latest build (3/17/12) of ThunderStick Full Blown Sense 3.0 (Thread for this ROM here)
Here is the edited res folder - Maybe someone can look at or use it for troubleshooting.
Thanks again for any input on this problem.
go to market and search and download zipsigner2. open it and navigate to the app and then chose and output and save it as an .apk file and it should install like normal
Does anyone have the original APK for GMS_Maps.apk? I think I might have overwritten mine at some point because the Jellybean update keeps failing the sha1 hash at GMS_Maps.apk. I tried rolling back, but it appears past me was too stupid to back up those files.
i can probably grab it for you in an hour or 2......
one question, how do you know where it is failing? is there a log file somewhere?
i am failing the install as well and i think i have everything back to stock but no dice.
i do have a custom boot animation.....would that cause it to fail?
Yeah, in /cache/recovery there is a file called last_log that details your last attempt at loading firmware.
I actually managed to make it past the GMS_Maps apk and get Jelly Bean installed. Thanks for your offer of help anyways
I don't believe a custom boot animation could cause the install to fail. I don't see in the update where it checks the boot animation SHA1, so unless your boot animation replaces more than just the /system/media/bootanimation.zip, then you should be fine.
aiziks251 said:
Yeah, in /cache/recovery there is a file called last_log that details your last attempt at loading firmware.
I actually managed to make it past the GMS_Maps apk and get Jelly Bean installed. Thanks for your offer of help anyways
I don't believe a custom boot animation could cause the install to fail. I don't see in the update where it checks the boot animation SHA1, so unless your boot animation replaces more than just the /system/media/bootanimation.zip, then you should be fine.
Click to expand...
Click to collapse
ok i see the file...then there are things under that and there is nothing displayed when i tap on any of those....what exactly do i do with this last_log file/
text viewer
sqlite databse viewer
linux script handler
apk handler
text editor
zip viewer
tar viewer
rar viewer
Just open it up in the text viewer or editor. Or if you're using the terminal just dump it out, the last few lines are all you want anyways because they will identify where the installation failed.
aiziks251 said:
Just open it up in the text viewer or editor. Or if you're using the terminal just dump it out, the last few lines are all you want anyways because they will identify where the installation failed.
Click to expand...
Click to collapse
i figured it out. for whatever reason root explorer wasn't seeing the text...ES worked fine and pointed out that it was my build.prop...even though i could have sworn that i returned to my original build.prop that i made a backup of.
I have a ZTE990 avail.
Currently I'm rooted with no other roms installed, simply stock, and odexed.
I've tried to manually de-odex using baksmali, Xultimate, etc. All were a pain, all wouldn't work properly.
I found someone and downloaded someone who just simply uploaded a Stock_Deodex.zip rom. Sounded perfect.
So I boot into CWM, try to update and...
assert failed: write_raw_image("/tmp/boot.img","boot" android
Click to expand...
Click to collapse
Since I have stock.. and am just trying to De-Odex.
Can I just unzip the Stock_Deodex.zip, delete the current (apparently faulty) boot.img, and replace it with one of the ones created with the cwm recovery, re-zip and attempt to update as usual?
Or since (if my understanding is correct), the only thing necessary for a system to become deodex is the files in /system/app and /system/restore.
Obviously when I un-zip stock_deodex.zip I have access to them. Could I possibly just replace the two folders (somehow?) and be properly de-odexed?
Any other options that I could use that'd be best?
Much appreciated to anyone who helps, thanks!
Before the eye rolling starts, please note i've Googled and searched for a solution on XDA extensively, with very little help concerning creating a flashable Zip file for Lollipop. Most of the guides and results dealt with KK and lower...
I'm attempting to create a flashable zip for the modified version of the Lollipop AOSP MMS app (located here: https://www.androidfilehost.com/?fid=95832962473398790). I've done this in the past with Jellybean and KitKat, but this time the app, for whatever reason just simply won't flash. No errors come up in recovery, but upon reboot, the app won't be installed.
I've concluded that the reason the app won't flash is the way I have my flashable zip structured.... Or the Updater Script is written wrong.. I've had this problem in the past and rectified it by placing the corresponding META-INF file into the apk itself before placing it in a flashable zip, but this hasn't fixed the issue this time around. The apk in the link above installs itself into the following directory when installed using a file explorer:
Code:
/data/app/com.android.mms-1
If I place the modified apk into the same exact directory in a flashable zip (along with the META-INF folder). An example of what I've done can be downloaded Here, for those interested in dissecting the zip. The only difference is the apk loaded in that zip is the original apk that I know works, not my modified one, as it isn't complete yet.
For reference, I took a look at the CM12 Gallery flashable zip which installs itself in this directory:
Code:
/system/app/Gallery2
Please note that the apk decompiles and recompiles with no issue, so unless APKtool (newest version) screws something up without throwing an error, I doubt that's the issue.
Really need some guidance on this one. I'm excited to see what I can do with this MMS app as I have done in the past with the KK AOSP MMS application. Any help would be greatly appreciated.
Resolution:
I've constructed a perfectly functioning flashable zip (not the ones above) after a few more trial runs. The problem actually seems to be with Apktool not compiling or decompiling the apks correctly. Basically the problem is APKtool.
Can someone please upload the stock build.prop file .
I'm not sure which version i need, whether 10A or 10D.
I have NEVER updated my phone (i got it in like april/may) and i am rooted.
In setting > Software version shows: Unknown
(Part of the reason i need a stock build.prop)
Edit: i found the 10D build prop here for anyone looking:
http://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-10d-rom-flashable-zips-imgs-t3406505
An interesting observation is that some buildprop apps load the file while others cant (that all request rot permission).
Can someone explain why perhaps? Is this due to a permission on the file or something?
UPDATE: The phone will not boot bc i accidentally deleted the build.prom file entirely by restoring a seemingly blank version.
I really need a build.prop file now. #fail
Final update:
I was able to find a backup of my original build.prop
For anyone that may need it in the future, here is an upload of the Stock H830 10A build.prop:
http://www46.zippyshare.com/v/xpQFOfnG/file.html
Thanks in advance.