Related
Update/SOLVED: the guide for Gapps by zedomax wasn't working for me, but by going through and re-reading the Complete Video Guide (here) I found the video specifically for installing the android market (here) and was able to follow it successfully. There were several steps that noobs like me wouldn't have known to do just from the other guide.
Click to expand...
Click to collapse
Hi, I've been trying for a few days to install the google apps (gapps) package on my kindle fire, which during that time has been rooted via kindlewater on version 6.2.2 and now has been flashed with the rooted 6.3 rom.
I am able to verify that I am rooted, can adb into the device and can sideload apps over usb. I have root explorer, es file manager, file expert, etc but am never able to get past the first install of the gapps package, where i'm supposed to navigate to the GoogleServicesFramework.apk and install it. Every time I try to install it i get an error "application not installed" and it doesn't seem to matter that I'm rooted and that the app (e.g. file expert) has its settings set to "root" level permissions.
I also note that I am unable to move vending.apk from its location to the system/app folder, no idea how I am to achieve a read/write setting on that folder. I am able to "see" that i have rwxr or something like it but that doesnt let me move the file into that folder so not sure what to do.
Is there some critical step I am missing?
Thanks!
summary: kindle fire rooted on 6.3 via the secured rom found on this forum, mac is running osx 10.6.8.
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Thanks for this. Will try now.
Worked great. Had to copy the apk and odex file.
Good job! It's great to see the steps for Windows users!
Just a heads up that I simply extracted the files I needed from and on my N7 using Root Explorer, without using my PC at all.
Great guide! Method worked perfectly on my Nexus 7 going from 4.1.2 to 4.2, thanks
Please... is there some other way to update the files w/o installing Java on my Windoze PeeCee? I accidentally messed up my YouTube.apk with Titanium Backup... now I can't update from 4.1.2 --> 4.2 JB.
EDIT: JavaPortable FTW... updating (fingers crossed)
EDIT: SUCCESS TY OP!
For anyone who flashed the 4.2 clock/keyboard already
Hey, for anyone who flashed the 4.2 clock and keyboard on their Nexus 7 already and need to roll back to do the 4.2 update, I used OP's method to make a flashable zip that puts the 4.1.2 clock and keyboard back.
Worked perfectly for my Nexus 7 to get me up and running. Hope it helps anyone!
cantthinkofa.com/files/RestoreClockKeyboard.zip
galaxy nexus
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Nice Guide
perfect, the guide works just fine. Now finally running 4.2.
Awesome guide... Thanks... Happily running 4.2 now aften beeing stuck at libutils.so...
Sent from my Nexus 7 using xda premium
damagno said:
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Click to expand...
Click to collapse
I don't have a Galazy Nexus, but I think the steps should be the same. Here is a link to the factory images: https://developers.google.com/android/nexus/images#takju . It looks like they now have links for older versions, rather than just the newest images (which is how it was when I made my guide). So that's pretty sweet.
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1.
Click to expand...
Click to collapse
I was wondering if you could tell me how you did it? I'm searching a way to install 4.2.1 with no avail as of yet :crying:
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
Click to expand...
Click to collapse
Yes. I am having the same issue. I cannot update mine from 4.2 to 4.2.1. I wonder to know which original stock image you have used. Can you list a detail procedure?
Thank you very much.
Ric
dev/block/param
legom said:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Click to expand...
Click to collapse
my error 7 was generated by emmc: dev/block/mmdblk0p7 (the file is "param" any suggestions?
Thanks. After searching for a lot of time, this post helped me updating my SGS3.:victory: I previously tried to integrate youtube update into rom using titanium backup.
GallStones said:
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual)
Click to expand...
Click to collapse
Yes, that's what I mean. The reason I didn't want to do this on my device is because I had modified some other system files that I wanted to keep the modifications for.
Wow, thanks a lot OP! Your guide helped me fixing an error during the update to 4.2.2 on my Nexus 4.
please include a video ,im getting lost in the details
solved.
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
deusfaux said:
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
Click to expand...
Click to collapse
I think TIBU needs a big update....I have same issue but my biggest problem is I can´t uninstall any system apps (there a some I don´t need) when I tap the uninstall button always same thing...."Cannot find the .apk file .....no problem whith my personally apk´s..?
Somebody same issue?
I ran into the same issue and solved (?) it by rebooting into recovery and doing an adb pull from there. It doesn't work from within Android like you said but once you're in the recovery partition things are different.
I think this not a problem with TiBu (or maybe it just needs an update like shivasrage said), because I can't copy my Nandroids to my PC either. I had to do a adb pull from recovery as well in that case. In fact, now that I remember, yesterday I tried to copy some backups I did in ES Explorer and some of them failed.
Android 4.3 is secure but that's messing with our old habits and making things more difficult.
Yeah but I had this problem before updating to 4.3
deusfaux said:
Yeah but I had this problem before updating to 4.3
Click to expand...
Click to collapse
Oh, that's weird. I never had this problem before 4.3.
I just went through this exact same problem with my TWRP backup files yesterday (Except in that case it was an issue with the latest 2.6 version of TWRP, not the Android OS). For Titanium Backup, I am going to have to go back today and count the files that I copied over to my PC using Windows Explorer and compare it to an adb pull under Recovery. There are so many files as part of the backup that I would never have noticed a couple of missing ones like I did on TWRP.
EDIT: Just checked and 427 files were copied over doing it each way with a full Titanium Backup (Windows Explorer or an adb pull), so it works fine for me. I am on Android version 4.2.2.
I solved the problem by installing BusyBox from Play Store (Normal install). Then, opened a command window (you can also do it using Terminal Emulator) from within my platform-tools folder in C and typed:
adb shell
su (grant permission in the phone)
busybox chown -R 1023.1023 /data/media/*
Click to expand...
Click to collapse
Now I can safely copy all files by drag-n-drop or adb pull from within android.
Cheers
Can someone walk me through solving this? I'm wanting to do a factory reset immediately, but I can't before copying over these Titanium Backup'd apps.
Why is this even happening?
ABD, ES File Explorer, everything is giving me a permission error. The latter said EACCES (Permission denied) Refused by system.
edit: nevermind. I narrowed down the offending files, and forced new backups by deleting the old ones and re-doing them. Something about the way TiBu wrote a handful of the backups was not allowing anything to copy the files.
Edit: Sorry for not maintaining this thread for a long time (rl stuff) but after all I really recommend you switching to LineageOS. It's very straightforward, you have full Play Store and Amazon access and a smooth, nice, customizable and clean android. Also you don't have to worry about your device getting incompatible to the Play Store^^ or bricking your device by accidental updates.
Srsly, don't do anything below here. It's old and not supported anymore. Also before doing anything to your tablet: Unlock the Bootloader here
So you finally rooted your Kindle Fire HDX 7/8.9 on 4.5.2
and you want to start using it but remembered that amazons updates kill everything, searched for a method to bypass it and fortunately found this thread.(You Sir are very lucky)
So lets start:
1. How to disable OTA updates
Step 1:
Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
Step 2:
Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
Step 3:
Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
Step 4:
Profit! You can now access the internet freely without the fear of evil amazon updates
But you want to install apps on your Kindle so
2. How to install Google Play Apps
Step 1:
Aquire the GApps for KitKat. Preferably here
Step 2:
Extract it to your Kindle and copy everything except for PrebuiltGMSCore.apk, META-INF and addon.d in the similar system folder (apps in system/app folder go to system/app folder (the real one))
Step 3:
Install PrebuiltGMSCore.apk manually like you would install any normal apk
Step 4:
Reboot (eventually it takes a bit longer)
Step 5:
PROFIT!!!! You have a fully working Play Store!
Obviously i don't take any responsibility if anything goes wrong (even though this procedure should be pretty safe)
Just rename DeviceSoftwareOTA.apk to whatever you like
Click to expand...
Click to collapse
You need specify that need to change the extension exactly
Potato_of_Doom said:
Step 5:
PROFIT!!!! You have a fully working Play Store!
Click to expand...
Click to collapse
Worked great but for some reason on my kindle hdx 7" running 4.5.2 when I booted up the SetupWizard came up to select my language and then when I clicked the big arrow it dumped me into the wireless settings screen and I was stuck. I had to eventually remove /system/priv-app/SetupWizard.apk. You might want to recommend users not including this as well on the off chance it causes the same problem I had. After I fixed this I just clicked on the play store and it prompted me to login.
Potato_of_Doom said:
So you finally rooted your Kindle Fire HDX 7/8.9 on 4.5.2
and you want to start using it but remembered that amazons updates kill everything, searched for a method to bypass it and fortunately found this thread.(You Sir are very lucky)
So lets start:
1. How to disable OTA updates
Step 1:
Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
Step 2:
Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
Step 3:
Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
Step 4:
Profit! You can now access the internet freely without the fear of evil amazon updates
But you want to install apps on your Kindle so
2. How to install Google Play Apps
Step 1:
Aquire the GApps for KitKat. Preferably here
Step 2:
Extract it to your Kindle and copy everything except for PrebuiltGMSCore.apk, META-INF and addon.d in the similar system folder (apps in system/app folder go to system/app folder (the real one))
Step 3:
Install PrebuiltGMSCore.apk manually like you would install any normal apk
Step 4:
Reboot (eventually it takes a bit longer)
Step 5:
PROFIT!!!! You have a fully working Play Store!
Obviously i don't take any responsibility if anything goes wrong (even though this procedure should be pretty safe)
Click to expand...
Click to collapse
do i put <app etc framework lib priv-app> in /system dir
candiflan said:
do i put <app etc framework lib priv-app> in /system dir
Click to expand...
Click to collapse
Yes you can copy everything, just look out for /priv-app/PrebuiltGMSCore.apk (If you try to copy it you'll get a memory error)
@awinston
Thats strange. On my kindle it worked without any issues
Potato_of_Doom said:
Yes you can copy everything, just look out for /priv-app/PrebuiltGMSCore.apk (If you try to copy it you'll get a memory error)
@awinston
Thats strange. On my kindle it worked without any issues
Click to expand...
Click to collapse
Got it thanks
awinston said:
Worked great but for some reason on my kindle hdx 7" running 4.5.2 when I booted up the SetupWizard came up to select my language and then when I clicked the big arrow it dumped me into the wireless settings screen and I was stuck. I had to eventually remove /system/priv-app/SetupWizard.apk. You might want to recommend users not including this as well on the off chance it causes the same problem I had. After I fixed this I just clicked on the play store and it prompted me to login.
Click to expand...
Click to collapse
How did you remove /system/priv-app/SetupWizard.apk
After doing this to get gapps, I am receiving license error when attempting to play amazon instant videos. Any ideas?
Edit: obviously did something to drm as I can't access kindle books either.
Anyone know a way to fix? Thanks
candiflan said:
How did you remove /system/priv-app/SetupWizard.apk
Click to expand...
Click to collapse
Never mind I rename SetupWizard.apk to SetupWizard.apk.old this is what I did
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'mv /system/priv-app/SetupWizard.apk /system/priv-app/SetupWizard.apk.old'"
adb shell "su -c 'mount -o ro,remount /system'"
Is there a recommendation on installing the gapps via this method, versus the HDXposed method?
It sounds like this is easier and slightly less risky.
Sent from my KFTHWI using Tapatalk
Potato_of_Doom said:
So you finally rooted your Kindle Fire HDX 7/8.9 on 4.5.2
and you want to start using it but remembered that amazons updates kill everything, searched for a method to bypass it and fortunately found this thread.(You Sir are very lucky)
So lets start:
1. How to disable OTA updates
Step 1:
Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
Step 2:
Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
Step 3:
Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
Step 4:
Profit! You can now access the internet freely without the fear of evil amazon updates
But you want to install apps on your Kindle so
2. How to install Google Play Apps
Step 1:
Aquire the GApps for KitKat. Preferably here
Step 2:
Extract it to your Kindle and copy everything except for PrebuiltGMSCore.apk, META-INF and addon.d in the similar system folder (apps in system/app folder go to system/app folder (the real one))
Step 3:
Install PrebuiltGMSCore.apk manually like you would install any normal apk
Step 4:
Reboot (eventually it takes a bit longer)
Step 5:
PROFIT!!!! You have a fully working Play Store!
Obviously i don't take any responsibility if anything goes wrong (even though this procedure should be pretty safe)
Click to expand...
Click to collapse
Doesnt work on my Apollo. I downloaded GAPPS 036 (320DPI) and follow your steps. But it doesn't work and I cannot copy phonesky.apk, i have to manually install it. I copied system folder using ES Explorer. Do I have to set permit for files??
Thanks
tuanda82 said:
Doesnt work on my Apollo. I downloaded GAPPS 036 (320DPI) and follow your steps. But it doesn't work and I cannot copy phonesky.apk, i have to manually install it. I copied system folder using ES Explorer. Do I have to set permit for files??
Thanks
Click to expand...
Click to collapse
I had issues when I tried ES Explorer. I used Root Explorer with no issues. Also, make sure to set perms to RW R R to match other files in all the directories.
tuanda82 said:
Doesnt work on my Apollo. I downloaded GAPPS 036 (320DPI) and follow your steps. But it doesn't work and I cannot copy phonesky.apk, i have to manually install it. I copied system folder using ES Explorer. Do I have to set permit for files??
Thanks
Click to expand...
Click to collapse
Did you get an error message?
Notifications not working
Anyone else having problems not receiving notifications? I am not receiving notifications about updates from google play and I am not receiving notifications from apps where they have been enabled. I took a quick look at some test apps on the store and I never receive the notifications through those apps either. Below is a log cat from a test notifications app. I did some reading and it seems to suggest maybe the individual apps are not configured correctly but I will need to keep digging. Will keep digging, just not very familiar with c2dm so wanted to ask.
03-03 11:17:24.787 2024-4230/? I/GCM﹕ GCM message com.firstrowria.pushnotificationtester 0:1425403044280977%c5da679ff9fd7ecd
03-03 11:17:24.797 2024-2024/? W/GCM-DMM﹕ broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=com.firstrowria.pushnotificationtester (has extras) }
03-03 11:17:24.797 937-966/? W/BroadcastQueue﹕ Permission Denial: broadcasting Intent { act=com.google.android.c2dm.intent.RECEIVE flg=0x10 pkg=com.firstrowria.pushnotificationtester (has extras) } from com.google.android.gsf (pid=2024, uid=10003) requires com.google.android.c2dm.permission.SEND due to receiver com.firstrowria.pushnotificationtester/.broadcast.GCMReceiver
Potato_of_Doom said:
Did you get an error message?
Click to expand...
Click to collapse
@riggsandroid: I tried root explorer and set permissions, same results.
@Potato_of_Doom: It closed without message. On the first boot, I can log in my account but after the home screen loading, PlayStore closed without warning. next time playstore close without warning (very fast). It is seem another Google service still working except playstore. I can log in to my play games account and load Clash of clans data without problems.
tuanda82 said:
@riggsandroid: I tried root explorer and set permissions, same results.
Click to expand...
Click to collapse
@tuanda82 I had similar issues when I didn't remember to install the GMS Core apk after moving all files over. Just a thought.
awinston said:
Anyone else having problems not receiving notifications?
Click to expand...
Click to collapse
Discovered a fix. I had to install Xposed and HDXposed. This leads me to wonder whether the technique used to install gapps with HDXposed might not be the better and safer solution if notifications only work with HDXposed. Anyone else have notifications working without HDXposed installed? After looking through the HDXposed code it looks like this is probably the only solution but maybe I am missing something.
candiflan said:
do i put <app etc framework lib priv-app> in /system dir
Click to expand...
Click to collapse
I don't want to confuse anyone, but you really don't want to overwrite the folders, just add files to their corresponding location within their like-named partition directories.
If you are comfortable with adb shell commands, I find it easiest to actually move all the folders from the zip into the data or a newly created system folder & then use batch scripts that take advantage of the * wildcard call, such as *.apk, to change ownership & permission setting to 644 for all files at one time. I don't have time to list it all out all the steps right now, but if you have been playing with adb for a while, you probably already know what I am talking about. You can also do the same thing, live in the system folder, but I personally like to segregate the new files so I can check several & then move them all over at once, after I am confident all the changes were made via the shell commands.
Potato_of_Doom said:
So you finally rooted your Kindle Fire HDX 7/8.9 on 4.5.2
and you want to start using it but remembered that amazons updates kill everything, searched for a method to bypass it and fortunately found this thread.(You Sir are very lucky)
So lets start:
1. How to disable OTA updates
Step 1:
Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
Step 2:
Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
Step 3:
Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
Step 4:
Profit! You can now access the internet freely without the fear of evil amazon updates
But you want to install apps on your Kindle so
2. How to install Google Play Apps
Step 1:
Aquire the GApps for KitKat. Preferably here
Step 2:
Extract it to your Kindle and copy everything except for PrebuiltGMSCore.apk, META-INF and addon.d in the similar system folder (apps in system/app folder go to system/app folder (the real one))
Step 3:
Install PrebuiltGMSCore.apk manually like you would install any normal apk
Step 4:
Reboot (eventually it takes a bit longer)
Step 5:
PROFIT!!!! You have a fully working Play Store!
Obviously i don't take any responsibility if anything goes wrong (even though this procedure should be pretty safe)
Click to expand...
Click to collapse
There's another way to get working playstore:
You need enough system store to flash gapps by recovery. To get this, change some system apps to user apps (for example by titanium backup). Don't do this with 'really' system apps, but there are many Amazon apps, you can change (for example kindle reader, music, audible). You can still use these apps after change. Then you can flash with twrp a small gapps package.
Hi,
I have two old modded NST's with kindle and a bunch of other apps loaded on it.
I want kindle to sync on both, but it won't due to the cacerts.blk file needing updating. So on one of them with ES File Explorer already loaded, I have swapped the cacerts.blk file and sync works fine.
I followed instructions here: https://forum.xda-developers.com/showpost.php?p=65503037&postcount=24 to get it working - no issues.
The other NST has the same apps loaded, but unfortunately not ES File Explorer.
So I can't copy the files to the /system directory.
So I downloaded two old versions of the ES File Explorer apk and uploaded to the SD card via the USB cable (with ADB Konnect already on the device).
I can't find any way to get the .apk to install. I have tried this with two old versions (1.6.2.3 & 3.0.5.5) loaded to the sdcard/download folder.
Its ages since I did this - so probably forgot how to do this.
When I go to this directory via the base file manager in the modded env I see the .apk, but when I select them it gives me a Parse error.
Can anyone please tell me either how to load the ES File Explorer apk, or another way to get the damn cacerts.blk into /System/etc/Security.
Thanks
meggiedude said:
Hi,
I have two old modded NST's with kindle and a bunch of other apps loaded on it.
I want kindle to sync on both, but it won't due to the cacerts.blk file needing updating. So on one of them with ES File Explorer already loaded, I have swapped the cacerts.blk file and sync works fine.
I followed instructions here: https://forum.xda-developers.com/showpost.php?p=65503037&postcount=24 to get it working - no issues.
The other NST has the same apps loaded, but unfortunately not ES File Explorer.
So I can't copy the files to the /system directory.
So I downloaded two old versions of the ES File Explorer apk and uploaded to the SD card via the USB cable (with ADB Konnect already on the device).
I can't find any way to get the .apk to install. I have tried this with two old versions (1.6.2.3 & 3.0.5.5) loaded to the sdcard/download folder.
Its ages since I did this - so probably forgot how to do this.
When I go to this directory via the base file manager in the modded env I see the .apk, but when I select them it gives me a Parse error.
Can anyone please tell me either how to load the ES File Explorer apk, or another way to get the damn cacerts.blk into /System/etc/Security.
Thanks
Click to expand...
Click to collapse
Use the 1.6.2.3 version.
Since you have ADB working you can install the app that way.
Code:
ADB install yourappfilename.apk
The only stipulation is that the app you are trying to install should be in the same directory as ADB. Oh, and no spaces in the file name.
nmyshkin said:
Use the 1.6.2.3 version.
Since you have ADB working you can install the app that way.
Code:
ADB install yourappfilename.apk
The only stipulation is that the app you are trying to install should be in the same directory as ADB. Oh, and no spaces in the file name.
Click to expand...
Click to collapse
Thanks,
Tried that, but I get an install error. Does this suggest that the ADB on the NST is older than my Win10 PC is using?
E:\Simon\Downloads\platform-tools_r28.0.1-windows\platform-tools>adb install es-file-explorer-1-6-2-3-es-en-br-fr-de-it-cn-jp-ru-nl-pl-kr-se-android.apk
adb server version (31) doesn't match this client (40); killing...
* daemon started successfully
es-file-explorer-1-6-2-3-es-en-br-fr-d.... 1.4 MB/s (22531795 bytes in 14.894s)
pkg: /data/local/tmp/es-file-explorer-1-6-2-3-es-en-br-fr-de-it-cn-jp-ru-nl-pl-kr-se-android.apk
Failure [INSTALL_FAILED_OLDER_SDK]
rm failed for -f, Read-only file system
E:\Simon\Downloads\platform-tools_r28.0.1-windows\platform-tools>
Click to expand...
Click to collapse
Cheers
meggiedude said:
Thanks,
Tried that, but I get an install error. Does this suggest that the ADB on the NST is older than my Win10 PC is using?
Cheers
Click to expand...
Click to collapse
Hmm...
First, just for the future, you can rename apk files so you don't have to type so much (and make mistakes like I always do). So just ESFileExplorer.apk would work OK. Renaming the file does not change anything internally and the internals are what ADB (or a package manager) looks at.
I see two possibilities. One is that you may be right, but I don't know enough about ADB to answer definitely. I've always used this tool: https://forum.xda-developers.com/showthread.php?t=2317790, although my version is older than what is currently posted. Looks like my adb.exe goes back to February 2013. Anyway, I've never seen that error.
To me, the error message also suggests that the flag for installing from unknown sources might not be set. Why that would be I can't say. Since NookManager is non-destructive and can be run repeatedly, you may want to just try that. You can use the package as is or take some of my update suggestions (one of which will install ES File Explorer during the process). This would insure that the flag is set correctly AND also put the app on the device. There's even an update option to install the cacerts.bks file (second post down).