Related
Market on stock Gtablet Rom
After alot of research i got this to work.
Try at your own risk!!!
First root with Z4 root. This is totally reversable.
Next find and download gtab_tnt_lite_v2.00 and unzip to your computer. Go to update, system, app and copy the files below to your gtablet. Go to ES file explorer and install the apps listed below manually in the order they are numbered. Then reboot . Pick setup wizard after reboot and follow instructions for google.
1. GoogleServicesFramework.apk
2. OneTimeInitializer.apk
3. SetupWizard.apk
4. Talk.apk
5. Vending.apk
6. Gmail.apk
7. Maps.apk
Next
- Get a copy of Titanium Backup and sideload it (free version is fine).
- Make sure the Market is working with your Google ID, of course.
- Go into Settings -- Applications -- Manage Applications and Force Stop both the Market and Google Services Frameworks apps.
- In Titanium Backup, go into "Backup/Restore", look for "Google Services Framework 2.2", click on it and then choose "Wipe Data". Then go back to the home screen.
- Run the Market app. You should get an error (that's a good thing, as that's what we want. If you don't get an error, re-try the steps above until you do).
- Reboot, and wait at least a minute after the OS is up to let things stabilize.
- Run the Market again. You should see an immediate difference.
Enjoy
http://forum.xda-developers.com/showthread.php?t=842590
Post #1
duplicate post
Well this is just for the folks that dont want to have to mess with having to flash through recovery.
frankie_pr1 said:
Well this is just for the folks that dont want to have to mess with having to flash through recovery.
Click to expand...
Click to collapse
You get the most up to date gapps from the link provided. You can extract the same files from that zip.
You are less likely to have problems using the current gapps and installing through recovery than manually copying and pasting files.
There are several existing threads that cover this process already.
http://forum.xda-developers.com/showthread.php?t=889659
Closed, as there are already multiple threads that cover this subject.
THIS METHOD IS NO LONGER WORKS as of update version 2.0.5 and higher.
Please visit this thread instead for the current rooting method.
Posting in this thread will get you nowhere, let it RIP.
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Let me start by saying that I didn't come up with the working root method. The original root instruction came from verygreen in this thread. And I am not a developer, I merely have a few linux background and even less so in the Android. I worked on this on my spare time by myself.
I merely take what was working, but unusable to make it usable. I found something that he is missed. This may actually be working on Nook HD (non-plus) also, but since I don't own one I can't say that it will.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
When I found out the root doesn't actually work past a reboot, I start looking what actually cause the Nook to be pissed and factory reset itself. Well, it seem that the /system and anything in there is basically coming from a /dev/block/mmcblk0p8 And if something got change, Nook get pissed and do a FULL FACTORY RESET(I'll explain in a moment). Well, at least I start investigated under that idea.
What I found:
What I found, or at least what I think I found is that, probably just adding file, or increase in the size(maybe there is a threshold for this), will cause it to do a full factory reset. What I also found is that there is a $PATH for /system/sbin but not pointing to anywhere. So I come up with the idea of making another ext4 file system in a file and loop mount it to /system/sbin I guess that work(very well). What I also found is that, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system
What is included:
basically a zip file, inside that zip file are 6 files.
boot_complete_hook.sh.bak this is basically a modified version of verygreen's
busybox & su are basically from his thread
superuser.apk well I found this one floating around and seem like a good idea to stick it in there (not even sure if it gonna work w/ Nook)
makeroot.bat this is basically what do most of the work. It's base on verygreen original rooting instruction.
sbin_mount This is basically an ext4 file system which have su and another version of busybox all setup nice and tidy for you all. This version of busybox is 1.20.2r2 which I grabbed from here.
Prerequisite:
ADB, it's your responsibility to have adb up and running, meaning not just have it install, but it can see your nook also.
leapinlar wrote a post to help you getting ADB to work here.
Now to get root:
all you have to do is unzip it and run makeroot.bat (obviously you run this in windows command prompt). Yub that's all. The batch file will do the rest, including reboot the nook and wait for it to reboot and stuff. Won't make a coffee for you though.
The manual and hard way:
well, I will only explain this in a summarize way. Basically this start with verygreen rooting method. It basically take advantage of the exploit and run /data/boot_complete_hook.sh which you adb push yourself(with correct permission) with root privilege. What you can run in there is basically up to your creativity. So obviously in this case, you mount the sbin_mount as an ext4 filesystem in the /system/sbin You can make this file yourself if you want to, in linux using dd and mkfs command. Basically using dd to create a file volume to the size you want and mkfs to format it to ext4. Mount it and start uploading stuff you want in there. You will have to correct all the file permission as well. Since all of this will be mounted to /system/sbin you should be aware what you gonna put in there. I guess I could make this thing 100MB, but for this specific purpose 10MB is enough. I my case, just the su and busybox and the symbolic links for the busybox. I'm doing this for the long term. I'm too lazy to point to busybox everytime I wanna do something.
What to do afterward:
Now that you have root, you can Enable Unknown Source to allow you to install app from within the device and install GAPPS. Follow the two guides below if you interested.
Enable Unknown Source: Again, I make an easy little tool for you here.
GAPPS: here.
Did I missed something:
Well, as I said I'm no coder so if I didn't do a clean job, you can refine it. If I didn't document or give proper credit, then I guess I missed that. Sorry about that, again I'm no coder and never done this. And finally:
If this thing work for you, feel free to hit that "THANKS" button. I spent many hours trying to come up with this solution.
FAQ:
Q: My so and so application when attempting to have root access get freeze up, or superuser doesn't work?
A: Well, I'm not sure if this is dued to how the Nook side-loading work or not, but it seem for some reason superuser won't start by itself. So you have to start it manually the first time.
Q: I type in "adb root" and I can't get in as root, it doesn't work?
A: yes it does, it's just not working with adb root. You can get in via "adb shell" once you get in, type in "su" and you can see that you now should have root access.
Thank you so much! This works perfectly. Survives reboot.
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
This sounds like a good idea initially.
It is true that the B&N does not just check for /system/xbin/su directly like they did in the past.
This time they check for something else and I just had no time to look into it more deeply to find out what is it they are actually checking for. I plan to figure this out on Friday when I am back home.
Also wanted to tell you that having Linux background is a great thing when tinkering with Android (at a low level, anyway). I don't have much Android background to speak of as well.
This works really well, and thanks to Someone (and mad props too) for getting persistent root working on this.
I may be being very naive, but my suspicion on the reboot is around the manifest file that's present at root.
It seems to be generated by the boot process and it might provide a quick and dirty list of what's permitted on the device to check. With persistent root, lots of investigation becomes a lot less painful. I expect that by end of day we'll have install unsigned running.
Early in my experimenting with the HD+, I noted:
- some versions of the Google Services Framework can be installed via adb
- when I launched the native calendar app after installing gsf, it wanted to sync to a google account, and was able to add the google account
- one version of the Play store installed and launched as far as throwing the 'you must accept the terms of service' before crashing
What BN most likely does is calculating the hash value (or digest, if you prefer) of certain system files that they think shouldn't be tampered with, then during reboot, the values of these files must match, or they will do a factory reset.
The key point is to find out where they do these checks and fool the check.
This sound simple but it depends on how they implement it. If they use binary decisions (like if the hash_value == calculated), then it is easy to get around. If not (e.g. using white box algorithm to hide keys), then it get more complicated.
excellent and very elegant solution. Kudos!
I'm heading out to work, and if you think your theory is right, try poking around with it. Now that your have root, you can try to dd those bootloading partitions out to user area and upload them out to PC and inspect them.
looking at the vold.fstab
Code:
xloader -> /dev/block/mmcblk0p1
bootloader -> /dev/block/mmcblk0p2
recovery -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p4
rom -> /dev/block/mmcblk0p5
bootdata -> /dev/block/mmcblk0p6
factory -> /dev/block/mmcblk0p7
system -> /dev/block/mmcblk0p8
cache -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p10
Be extra careful when touching those partition if you not sure, don't touch them. But making a block copy of them and taking them out should be relatively easy and safe. Obviously you gonna need a Linux box to do this. I setup a VM on one of my PC last night because I need to get a ext4 partition and put all the goodies in there.
krylon360 said:
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
Click to expand...
Click to collapse
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
someone0 said:
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
Click to expand...
Click to collapse
works just fine.
I chmod a+x'd the script before putting it into the zip.
heh, yeah, it works. Forgot I had my touchpad pluged in and it rebooted it....
whoops.
thanks for posting the location of the /recovery partition. I want to put a copy of htat on ice to prevent BN from undoing any of my work in a future update - I may want some of the fixes they have, but I want to be able to roll them back if needed.
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder and was able to see it in my sideloaded launcher, was able to uncheck/check install non market apps which sets the setting for US to be able to install .apk files from the nook itself, ONLY ISSUE is since I put that file in the system/app folder and the nook didnt like it I got stuck in a bootloop and get to start this process all over again! (nook resetted to ground zero)
maybe we temporary can leave it there get us the permission to install non market apps then remove the file and we will be ok or maybe stuck in another bootloop.
---------- Post added at 09:20 PM ---------- Previous post was at 08:52 PM ----------
GOT IT WORKING NOW:
1. Once rooted, get a file manager with root support and enable read/write permission to /system
2. temporary copy nook tools ver .02 .apk to the system/app folder
3. have a sideloaded launcher and check the app drawer youll see nook tools, run it, first screen uncheck and check the install non market apps box couple of times make sure its checked afterwards
4. have a test .apk to run the BN installer on and see you can now install .apks from the NOOK HD and HD+
5. remove the nook tools.apk file from the system/app folder and quit your file explorer which should reset everything for the system folder back to the way it orginally is!
6. reboot, if you reboot successfully with no boot loop 8 times, your GOLDEN FOR NOW! once again load up a file manager go select an .apk file and see you can now install it! Next step is trying to get amazon market working! then google somehow, but for google you need files in system/app folder permanently!
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
someone0 said:
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
Click to expand...
Click to collapse
when you sidelaod it OR install or have it installed to another folder or ran from another folder it cant modify the setting to allow non market apps to install!!
has to be in the /system/app folder THEN RAN from app drawer then you can set the setting uncheck and check box quit program and for now YOU HAVE to remove the .apk from the system/app folder and then you can reboot and the setting sticks! I GOT AMAZON MARKET INSTALLED right now installing apps! NOW WE GOT A KINDLE ladys and gentleman!
Amazon apk installs in internal memory. Apps downloaded from Amazon get installed in internal memory. You can then move them to SD card or leave them in internal memory. System apps are provided in the ROMs by the developers or vendors. ALWAYS back up before making system changes.. Now rooted - use Titanium Backup. System/app should be static throughout ROM lifecycle unless modified by user.
skyhawk21 said:
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Click to expand...
Click to collapse
This is why I put the /system back to ro, at least that is what I think I did.
Amazon Store working on ROOTED Nook HD
Proof of Concept:
http://youtu.be/wCyd730L74Y
skyhawk21 said:
Proof of Concept:
http://youtu.be/wCyd730L74Y
Click to expand...
Click to collapse
LOL, your internet is slow. Could have cut the video time by 1/2 if not 2/3 if you switch to faster ISP.
skyhawk21 said:
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder
Click to expand...
Click to collapse
What exactly did you install? I cannot find "nook color tools" in Google Play or on APKTOP. Thanks for your hard work!
NEVERMIND! I found the thread that has the link for the app: http://forum.xda-developers.com/showthread.php?t=868366 Thanks again.
does this root method work on Nook HD+2.0.2?
if not how I can downgrade to 2.0.0?
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.
[Guide] Reload Facer & Watchmaker On-The-Fly (without PC) after Factory Reset (rev.1)
Hi Guys,
Since my watch has developed a problem (http://forum.xda-developers.com/huaw...-pair-t3337462) I have figured out an on-the-fly return mechanism with the help of TWRP.
* This requires TWRP flashed.
** Your Facer and Watchmaker collection should be existed there (/sdcard/Facer & /sdcard/BeautifulWatches directories) already.
Since factory reset won't delete your directories in /sdcard/ ; they will stay, survive.
0- Create a new directory "app" in /sdcard/ directory. (It will be: /sdcard/app/)
1- Copy of facer & watchmaker wearable APKs and any other micro APKs you wish (SWApp, etc.) into /sdcard/app.
2- Once you have completed your factory reset & paired your phone.
3-
3.A) Press and hold power button until reset, Huawei logo pops and you will feel a long vibration.
3.B) Upon feeling the vibration, release the power button then a short press (Press/Release) quickly.
3.C) It will take you to the bootloader, go to Recovery (TWRP must be installed)
4- Once you are in TWRP, head to Advanced -> File Manager
5- Go to /sdcard/app directory, and click on "Select" button below. It will show you options (what you want to do with /sdcard/app directory) and Copy It under /data/ folder. It will overwrite your /data/app/ folder.
6- Reboot to System. You will see all apps you have kept are installed.
Now you will find Facer & Watchmaker among your watchfaces.
I also keep Swapp wearable app there as backup, and copying it either along with many other watch faces.
So you don't need to install apps one by one, /sdcard/app directory contains all apps you want to install, just copy & overwrite /data/app/ folder, all apps installed .
Your watch is ready, from Factory Reset confirmation to this stage takes about 5-6 mins. Really on-the-fly.
I wish it will help.
Thanks for reading
Credits/Thanks:
1) @richboy324 : For manual bootloader method (http://forum.xda-developers.com/huaw...flash-t3307137)
2) @_that & @LunarEclipse120 : For teaching me /data/app manual .apk loading method.
Edit: I have originally posted this thread on Huawei Watch forum, but I think it is valid for all Android Wear. Also revised some parts of text (after experiencing it several times). Transferred the thread here.
Thanks for the mention. No Problem
I have had the Oneplus 5 for many years. After each update of OxygenOS I uninstalled some system apps (Chrome Google Photos, Gmail, Google Movies etc) in Solid Explorer (with root access).
But, since the update to OxygenOS 10.0.0 with Android 10 this does not work anymore. Solid Explorer says that the app has been deleted, but after a reboot it is still there.
When I try to uninstall one of the apps with Titanium Backup, the message "Cannot remove system app. Failed to locate the apk file."
Does anyone have an idea how to permanently uninstall and delete system apps?
Thanks!
Berta Paneslowski said:
I have had the Oneplus 5 for many years. After each update of OxygenOS I uninstalled some system apps (Chrome Google Photos, Gmail, Google Movies etc) in Solid Explorer (with root access).
But, since the update to OxygenOS 10.0.0 with Android 10 this does not work anymore. Solid Explorer says that the app has been deleted, but after a reboot it is still there.
When I try to uninstall one of the apps with Titanium Backup, the message "Cannot remove system app. Failed to locate the apk file."
Does anyone have an idea how to permanently uninstall and delete system apps?
Thanks!
Click to expand...
Click to collapse
On Android 10 it's not possible anymore to delete system apps directly from OS, even with root access. You must use Titanium for show the path of apps you want deleted, system apps are located on :
system/system/app
system/system/priv-app
Go in recovery TWRP
> mount Cache, System, Vendor, Persist, Data, Firmware partitions
> Advanced > File Manager > system/system/priv-app/Gmail > "Folder" button on right bottom > Delete
Do the same thing for all apps that you want deleted.
Actually,it does get deleted from a root explorer, however, few apps have symlinks as well, or few apps have stubs as well. Hence those may invoke reinstallation automatically. Those are the ones which need to be deleted permanently from recovery (especially).
As you have discovered, several apk files are system linked and so every reboot will bring them back. To counter this I use the xXx debloat script. The module is flashed in Magisk and allows one to select which apps and services you want removed. Here is a link to the module on xda: https://forum.xda-developers.com/showpost.php?p=82391573&postcount=2.
You can flash the module with stock settings or make a custom profile as I did.
I have a question or two...
1) Is it ok to convert Chrome and Google Maps from system to user apps in android 10?
2) Will first deleting the app using TWRP, then install it from Playstore convert the app from a system to a user app?