Requirements:
TWRP recovery or equivalent
Root access
Android Debug Bridge (adb)
Know how to connect to device through adb (USB, network)
Ability to extract tar, lz and zip archives (7-Zip, Lzip)
Allowed apps from unknown sources through Fire OS
Ability to launch system apps (ES File Explorer, FireStarter)
USB or bluetooth mouse helps but is not required
Installation:
Install Xposed and the HDXPosed module
Download and install Open GApps ARM64, 5.1, pico using TWRP recovery
Download Google Play Store (Android TV) and rename APK to Phonesky.apk
Create a temporary folder on your Fire TV:
Code:
adb shell mkdir -p /sdcard/gtmp/lib/
Push Phonesky.apk to your Fire TV:
Code:
adb push Phonesky.apk /sdcard/gtmp/
Extract Core/gmscore-arm64.tar.lz and Core/gsflogin-all.tar.lz from the Open GApps archive obtained during step #2
Extract the contents of gmscore-arm64.tar.lz and gsflogin-all.tar.lz
Push these newly extracted files to your Fire TV:
Code:
adb push gsflogin-all/nodpi/priv-app/GoogleLoginService/GoogleLoginService.apk /sdcard/gtmp/
adb push gmscore-arm64/nodpi/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk /sdcard/gtmp/
adb push gmscore-arm64/common/priv-app/PrebuiltGmsCore/lib/arm64/* /sdcard/gtmp/lib/
Enter adb shell and run su for root
Mount the /system partition with rw access
Code:
mount -o remount,rw /system
Create missing directories that Open GApps failed to create:
Code:
mkdir /system/priv-app/Phonesky
mkdir /system/priv-app/GoogleLoginService
mkdir -p /system/priv-app/PrebuiltGmsCore/lib/arm64
Copy the missing APKs and libraries to their proper locations:
Code:
cp /sdcard/gtmp/Phonesky.apk /system/priv-app/Phonesky/
cp /sdcard/gtmp/GoogleLoginService.apk /system/priv-app/GoogleLoginService/
cp /sdcard/gtmp/PrebuiltGmsCore.apk /system/priv-app/PrebuiltGmsCore/
cp /sdcard/gtmp/lib/* /system/priv-app/PrebuiltGmsCore/lib/arm64/
Change the permissions for the newly created files and directories:
Code:
chmod 755 /system/priv-app/{GoogleLoginService/,Phonesky/,PrebuiltGmsCore/,PrebuiltGmsCore/lib/,PrebuiltGmsCore/lib/arm64/}
chmod 644 /system/priv-app/Phonesky/Phonesky.apk
chmod 644 /system/priv-app/GoogleLoginService/GoogleLoginService.apk
chmod 644 /system/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk
chmod 644 /system/priv-app/PrebuiltGmsCore/lib/arm64/*
Remove the temporary folder:
Code:
rm -r /sdcard/gtmp/
Exit adb shell
Download Google Play services (Android TV), variant 846 (8 for Android TV, 4 for arm64-v8a, 6 for 320 dpi) and rename APK to com.google.android.gms.apk
Download Google Account Manager 4.4.4 and rename APK to com.google.android.gsf.login_4.4.4.apk
Install Google Play services (Android TV) and Google Account Manager 4.4.4 using adb:
Code:
adb install 'com.google.android.gms.apk'
adb install -r -d 'com.google.android.gsf.login_4.4.4.apk'
Disconnect adb and reboot Fire TV
Connect to adb, enter adb shell and run su
Mount the /system partition as ro
Code:
mount -o remount,ro /system
Exit adb shell and disconnect adb
Play Store Setup:
Launch Google Play Store. Play Store is a system app and requires a program such as ES File Explorer or FireStarter to launch.
Login to your Google account. You should be able to fully navigate this version of Google Account Manager with the Fire remote, but a mouse can be helpful.
Play Store should have launched and you can now install Android TV apps and use apps that require Play Store or Google accounts.
Credits:
AFTVnews for their Play Store guide
guyHalestorm for his updated AFTVnews Play Store guide
I created this because guyHalestorm's guide was getting pretty outdated and wanted a better guide for the next time I have to install Play Store instead of referencing multiple guides, comments and updating commands.
Notes:
I omitted some very, very basic things from the guide such as how to use adb, extract archives, and launch system apps from specific apps due to the guide already being very long and most XDA users should be familiar with these or can be easily learned from Google.
Windows users may have to replace forward slashes (/) with back slashes (\) in paths depending on their shell.
I only tested this on my Fire TV 2 but I don't see why this wouldn't work on other Fire TV devices with root. I didn't personally test this 1:1 since I already installed Play Store, so let me know there's problems.
Oh wow, thanks for this. I will try this out when I get home tonight.
Proved on Fire OS [5.2.6.2_r1] and it's working fine.
Made a couple changes to the guide which are hopefully the last:
Fixed minor typos
Fixed Phonesky.apk source directory path in cp command (command would have failed)
Greatly simplified push and copy commands which should also improve future Open GApps compatibility
Corrected directory and file permissions (chmod) which may have worked before but were incorrect and possibly insecure. If you've followed the guide before, do step 9 & 10, 13 and then 21 & 22
ok solved done
Anyone tested this on Fire TV 3?
StDevious said:
Anyone tested this on Fire TV 3?
Click to expand...
Click to collapse
Doesn't work on Fire TV 3 bro. There's no root for us v3 users. :'(
First of all thank you @Bracket- for the guide :good:
I have done Everything exactly like the guide
but i can't open the playstore.
When i open it, it loads for few seconds and then it close.
Do you have or anybody else here have an idea why this happens?
My system: Fire TV 2, 5.2.6.2 rooted, xposed and hdxposed installed
chris-89 said:
First of all thank you @Bracket- for the guide :good:
I have done Everything exactly like the guide
but i can't open the playstore.
When i open it, it loads for few seconds and then it close.
Do you have or anybody else here have an idea why this happens?
My system: Fire TV 2, 5.2.6.2 rooted, xposed and hdxposed installed
Click to expand...
Click to collapse
If you already have root, this guide is much too complicated
Simply modify build.prop and then install the appropriate GApps and you have the complete Play Store & Services available.
Take a look around: here
You only need these steps:
2. Customize build.prop
4. Install Open Google apps for Android TV (the newest version works fine)
5. Allow Google registration (NoTouchAuthDelegate)
Prerequisites:
XposedInstaller-3.1.5.apk (install Xposed v89+)
HDXPosed-1.3.apk
BusyBox
rainman74 said:
If you already have root, this guide is much too complicated
Simply modify build.prop and then install the appropriate GApps and you have the complete Play Store & Services available.
Take a look around: here
You only need these steps:
2. Customize build.prop
4. Install Open Google apps for Android TV (the newest version works fine)
5. Allow Google registration (NoTouchAuthDelegate)
Prerequisites:
XposedInstaller-3.1.5.apk (install Xposed v89+)
HDXPosed-1.3.apk
BusyBox
Click to expand...
Click to collapse
Thanks for you help :good:
I will do this tomorrow.
Short question: do i need also the gapps-config.txt or not?
And when i need it, what did i need for using only the playstore and services?
chris-89 said:
Thanks for you help :good:
I will do this tomorrow.
Short question: do i need also the gapps-config.txt or not?
And when i need it, what did i need for using only the playstore and services?
Click to expand...
Click to collapse
yes, you need gapps-config.txt
Code:
forceclean
skipswypelibs
skipvendorlibs
GoogleAssistant
+extsharedstock
+keyboardstock
+provision
+packageinstallerstock
+webviewstock
+notouchauthdelegate
Include
gappspico
rainman74 said:
yes, you need gapps-config.txt
Click to expand...
Click to collapse
Thanks, playstore works now :victory:
Btw whats the different between the notouchauthdelegate.apk from the gapps package and your tv-notouchgsf.apk? and why we need yours and not the one from the package? I ask just for my understanding
chris-89 said:
Thanks, playstore works now :victory:
Btw whats the different between the notouchauthdelegate.apk from the gapps package and your tv-notouchgsf.apk? and why we need yours and not the one from the package? I ask just for my understanding
Click to expand...
Click to collapse
The package com.google.android.gsf.notouch of Open GApps (TV-Stock version) does not work on Fire TV so that the AndroidManifest.xml had to be modified.
I followed the guide as exactly as I could:
I did not install Xposed and the HDXPosed module, because it is nowhere stated what it is for.
Open Gapps arm64 releases of 5 September 2018 are the last containing Core/gsflogin-all.tar.lz. So I used:
open_gapps-arm64-5.1-pico-20180905.zip.
my /system ran out of memory, so I had to create a symlink:
Code:
ln -s /data/priv-app/PrebuiltGmsCore /system/priv-app/PrebuiltGmsCore
and continued without any error from there.
But when I run Google Play Store app and try to login, I get Error [RH-01].
Related
I can't speak for all GT 10.1s, but the one I received at Google I/O certainly does not have Google Books installed and it's not available in the Market. It comes with Kindle pre-installed, so I'm guessing Samsung has inked a deal with Amazon, but uhh... what about choice? I have several books from both Amazon and Google and use both applications on my Xoom, but now I'm curious why I can't use Google Books on my new tablet. Do I need to try to get the Google Books APK off my Xoom or what? Anyone else found a solution, besides reading their purchases online?
EDIT: The attached file is what finally worked for me. Thanks to smaskell for the link.
Books works fine on the 10.1. Just grab it off another device. My guess is that the market may not know the 10.1 yet as it is not really released now aside from IO.
Sent from my HTC Vision using XDA Premium App
I wasn't able to install the tablet version but I did manage to push it to /system/app/ and it works.
1. get root access
2. download busybox
3. adb push busybox /sdcard
4. adb push BooksTablet.apk /sdcard
5. adb shell
6. cd /sdcard
7. su
8. mount -o remount,rw /system
9. ./busybox cp busybox /system/bin - yes, I'm using busybox to copy itself
10. busybox cp /sdcard/BooksTablet/apk /system/app
and you're good to go!
I'm still struggling with this and I've tried installing (via adb, adb shell, and via Astro / app manager) both a BooksTablet.apk (with and without BooksTablet.odex) from a stock Xoom dump and with a copy from my Honeycomb 3.1 Xoom. Am I missing something? Installing always fails and simply putting the files in place does nothing as well (with a reboot). Anyone have any more ideas? I'm out at this point and it seems as if it should be so simple from what you guys are saying! Thanks for the help!
have you tried a deodexed version of the apk?
I have not and cannot seem to find these files anywhere and am not sure how to deodex the files I have. I tried the 1.2.7-dev version of baksmali with no luck. Any other thoughts or perhaps a link to the files you used that seemed to work? Thanks!
I used the one from this thread
http://forum.xda-developers.com/showthread.php?t=1071047
works like a charm
Case closed
Perfect! Thanks for the link, one of the two files in that thread worked like a charm! In case anyone else is looking for it, I've attached the file that worked for me.
Each time I try installing the BooksTablet.apk file provided above, it fails on the device. When I try installing it via "adb install BooksTablet.apk" it constantly fails with the error "INSTALL_PARSE_FAILED_NO_CERTIFICATES"
I took a look at the logcat output and it seems to be having an issue finding the "fallback_covers.png" file in the assets folder.
I tried renaming the apk to .zip and poking around and I was not able to find this file.
Anyone else having this issue when installing the Google Books app?
I searched around regarding the error message on installation and the solution is to uninstall the app and reinstall it. But because I don't have the app installed to begin with then this isn't an option.
Any help would be greatly appreciated. Thanks.
yeah, I had the same problem. The only way I got it to work was by pushing it to /system/app. see my earlier post for details.
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
nadewad said:
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
Click to expand...
Click to collapse
Did you try navigating to the apk and launching it?
nadewad said:
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
Click to expand...
Click to collapse
While I did have BusyBox installed, I can only vouch for the last thing I did that wound up working since I'd tried so many different things before getting the right APK. So once I had the file in the first post (and of course a rooted GT 10.1), I opened a shell, mounted the /system directory for read/write, chmod'd the app directory to 777, pushed the APK into the /system/app folder and then chmod'd the directory back to 644 (IIRC?). So the steps would have been:
1. adb shell
2. su
(if you get a permission denied error, make sure you leave your screen on and accept the prompt by Superuser Permissions, I forgot this on the freshly rooted tablet the first time)
3. mount -o rw,remount /system
4. chmod 777 /system/app
(now either exit the shell or open a new command prompt)
5. adb push BooksTablet.apk /system/app/BooksTablet.apk
(now back in your su'd adb shell)
6. chmod 644 /system/app
(you'll probably want to note what permissions were there previously as I'm going from memory)
There was no need to launch the APK or issue an install command (it fails anyway), the Books app appeared right away in my app drawer but got a FC after only a moment of it being opened the first time. After a reboot, everything has been working just like on the Xoom!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 02/03/2015
This guide I posted is well out of date, there are other methods to follow now days.
Please use http://www.aftvnews.com/tag/guide/ as it is up to date and current.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to AFTVNews.com for the OTA link and rbox for pointing me in the right direction I've successfully manually upgraded to the latest firmware, downgraded back to 51.1.0.2 and am now upgrading back to 51.1.1.0.
This is the process I followed. I take it for granted that you rooted, have SU and Busybox free installed.
Don't blame me if you **** your device up and you have a brick.
So lets get to it:
1. Download which ever firmware you wish to restore to:
Code:
51.1.0.1
http://amzdigitaldownloads.edgesuite.net/obfuscated/e6f65fefb36aaf7b94fd370f516b9c11/bueller-ota-51.1.0.1_user_510055620-signed.bin
51.1.0.2
http://amzdigitaldownloads.edgesuite.net/obfuscated/cec02756d1964c9cb1f71d52056cc81a/bueller-ota-51.1.0.2_user_510058520-signed.bin
51.1.1.0
http://amzdigitaldownloads.edgesuite.net/obfuscated/568eef32595f034b4304e19aa566befb/bueller-ota-51.1.1.0_user_511069920-signed.bin
51.1.1.0 Update 1
http://amzdigitaldownloads.edgesuite.net/obfuscated/4edaba705e98dee475680c33d3f41132/bueller-ota-51.1.1.0_user_511070220-signed.bin
2. Rename which ever one you wish to restore to update.zip
3. adb shell
4. su
5. chmod 777 cache
6. cd cache
7. chmod 777 recovery
8. cd recovery
9. echo --update_package=/cache/update.zip > command
10. ctrl + c
11. adb push update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever over wireless.---
An alternative is to copy update.zip to a USB Flash Drive, use StickMount to mount on the FireTV then copy it with the following command:
cp /sdcard/usbStorage/sda1/update.zip /cache
12. adb reboot recovery
Now it should reboot and start installing whatever update you downloaded and called update.zip :good:
If you get the out of space error:
roligov said:
No it's not because the updates are blocked, it's because you out of space in your cache partition. ADB shell to the box and run
ll /cache
If you have any bin files, delete them.
Click to expand...
Click to collapse
1. adb shell
2. su
3. rm /cache/*.bin
Nice
Nice work and great news! No reason not to update to the latest version since we can downgrade too.
Thanks. Should we delete the file after the update to save on the space or is it automatically deleted?
It automatically gets deleted. It's late this side so I'm going to bed.
Will do some testing tomorrow before I give the go ahead and tell everyone it's all working!
Wow!! I knew someone would figure it out, just did not think it would be this soon. Thank you for the work!!
One step closer to an unlocked bootloader...
Super guide, worked like a charm - thank you!
Good work! Thank-you.
zahir32 said:
Super guide, worked like a charm - thank you!
Click to expand...
Click to collapse
would there be a way to do this via shh
you should probably make a mirror of those firmware bundles. :good:
wavrunrx said:
you should probably make a mirror of those firmware bundles. :good:
Click to expand...
Click to collapse
Good point. I'll dl them tonight and leave them on my NAS. Eventually i"ll put them on dropbox or other filelocker for safekeeping
Getting It Done
bdscds said:
would there be a way to do this via shh
Click to expand...
Click to collapse
This method gets it done. I've tried others, but these instructions - and the fact that the OP has kindly prepared the "command" file for us - make it an easy ride. Just put the update zip in the same folder as your ADB setup, open your command window in that folder and adb will find it.
Thanks!
With this we can safely update to latest version!
Nice guide
Sent from my iPhone using Tapatalk
Can this be done over a local network or do I have to hook the Fire TV up to my PC using a USB (Male to Male) lead?
gazdaman. said:
Can this be done over a local network or do I have to hook the Fire TV up to my PC using a USB (Male to Male) lead?
Click to expand...
Click to collapse
http://www.firetvnews.com/how-to-sideload-apps-to-your-amazon-fire-tv-using-a-windows-pc/
network
shows you how to use adb, so you can do "adb shell"
be careful though, if you were to mess anything up in the process you could render your fire tv useless.
roligov said:
Thanks to FireTVNews.com for the OTA link and rbox for pointing me in the right direction I've successfully manually upgraded to the latest firmware, downgraded back to 51.1.0.2 and am now upgrading back to 51.1.1.0.
This is the process I followed. I take it for granted that you rooted, have SU and Busybox free installed.
Don't blame me if you **** your device up and you have a brick.
So lets get to it:
1. Download which ever firmware you wish to restore to:
Code:
51.1.0.1 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/e6f65fefb36aaf7b94fd370f516b9c11/bueller-ota-51.1.0.1_user_510055620-signed.bin
51.1.0.2 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/cec02756d1964c9cb1f71d52056cc81a/bueller-ota-51.1.0.2_user_510058520-signed.bin
51.1.1.0 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/568eef32595f034b4304e19aa566befb/bueller-ota-51.1.1.0_user_511069920-signed.bin
2. Rename which ever one you wish to restore to update.zip
3. adb shell
4. su
5. chmod 777 cache
6. cd cache
7. chmod 777 recovery
8. cd recovery
9. wget http://dl.dropboxusercontent.com/u/16913146/command
10. ctrl + c
11. adb push update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever.---
12. adb reboot recovery
Now it should reboot and start installing whatever update you downloaded and called update.zip :good:
Click to expand...
Click to collapse
Thanks for the info! I hear the new update offers nothing new and causes more problems than good by disrupting the alphametical order of sideloaded apps. Is it worth updating for or will there be no significant differences? It's funny because amazon.com don't mention a new update release.
Also does you update method require you to re-root the device or does root survive the update? Thanks very much!
Got it working with Windows 7
This is how I done it.
(Ensure you have ADB installed - If not google "ADB setup 1.3 windows")
Download the chosen firmware and rename it to update.zip
Download roligov's command file
remove the .txt extension that windows gives it when you download it. The filename should just be "command" with no extension otherwise you will get the failed message when you reboot to recovery.
Now run command prompt as Administrator
(I will use C:\ as the file location example)
adb kill-server
adb start-server
adb connect "Fire TV IP Address"
adb shell
su
chmod 777 cache
cd cache
chmod 777 recovery
ctrl + c
adb push C:\command /cache/recovery
adb push C:\update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever.--- (Took 2 minutes over LAN for me)
adb reboot recovery
Done
Many thanks to roligov for the initial find to set me on my way.
Yeah my FireTV is hooked up to my Wireless so it takes forever to push the update.
roligov said:
Yeah my FireTV is hooked up to my Wireless so it takes forever to push the update.
Click to expand...
Click to collapse
if one has a usb thumb drive and stick mount installed, copying the .bin to the /cache folder step might be faster?
User copies .bin file(s) and command file to a folder on thumb drive where a script file which lists .bins in thumbdrive folder and allows user to choose a numeral and then executes commands for update process would be cool for newbies. even having the script "autocreate" the command file.
DEODEXED APPS
Here is the stock app and framework files from new firmware I8200NXXUAOA1 for Samsung Galaxy VE (I8200N).It have all apps so and the bloatware.After install you can delete any bloatware you want.Maybe it is safe for all versions!!!
What is Odex and Deodex ROM
What is an ODEX file?
In Android file system, applications come in packages with the extension .apk.
These application packages, or APKs contain certain .odex files whose supposed function is to save space.
These ‘odex’ files are actually collections of parts of an application that are optimized before booting.
Doing so speeds up the boot process, as it preloads part of an application.
On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
What is an DEODEX file?
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files.
By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
So, Deodexed ROMs (or APKs) have all their application packages put back together in one place,
allowing for easy modification such as theming. Since no pieces of code are coming from any external location,
custom ROMs or APKs are always deodexed to ensure integrity.
all apps are full working and not yet any bugs
Code:
[COLOR="red"][B][U]* I can give ABSOLUTLEY no gurantee!!
All you do with your phone will be on your own.
I'm not responsible if your phone will brick or whatever...[/U][/B][/COLOR]
Code:
[B][COLOR="Red"]Rrequirements :[/COLOR][/B]
[B]Root [URL="http://forum.xda-developers.com/galaxy-s3-mini/general/s-iii-mini-ve-i8200-n-t2826565"]Hot To Root[/URL]
Adb [URL="http://forum.xda-developers.com/showthread.php?t=2588979"]How to Install[/URL]
Phone drivers[/B]
How To Install :
1. download the zip file
2. extract it
3. connect your phone
4. usb debugging on
3. paste the app and framework file into
GT-I8200N\Card folder which you find it on your computer
4 .install adb drivers
5. open cmd and type
Code:
adb shell
[COLOR="red"][I][SIZE="3"](if you are using adb shell in su for the first time,
keep phone screen on.
After entering "su" code, super user request prompt in phone.
Press allow )[/SIZE][/I][/COLOR]
su
stop
mount -o rw,remount /system/ /system/
cp /storage/extSdCard/app/* /system/app/ (wait...)
rm /system/app/*.odex (wait...)
cp /storage/extSdCard/framework/* /system/framework/ (wait...)
rm /system/framework/*.odex (wait...)
mount -o ro,remount /system/ /system/
reboot
How To check if you done
1. open cmd and type
Code:
adb shell
su
cd /system/app
or
cd /system/framework
ls
2. now you see all your system apps.if doesnt exist .odex file and you dont have any errors or bugs your ok
DOWNLOAD:
the file
credits:
@Snoop05 for adb installer
@j.posarekar70 for deodex guide
This work for the version i8200L?
Nice all ok
Test done
SAMSUNG
GALAXY S3 MINI
GT-I8200N
Willian182 said:
This work for the version i8200L?
Click to expand...
Click to collapse
try it i dont know.take a backup first.maybe you have error with nfc you can delete the apk .try it and tell me please
..................
Como lo descargo soy nuevo en esto.
Sent from my GT-I8200N using XDA Free mobile app
Thanks for this apps pack! It saves my phone. Best regards.
download link
download link is broken
Is it possible to unroot the deodexed stock rom?
I got some Apps which refuse to work if they detect a rooted phone...
[GUIDE][7.1.1] Making The System Half-Writable & Convert The Apps To Be System-Apps
Okay. This is my first guide. My English isnt that so good. I tried something for my phone. I thought maybe it will helps you too.
HERE IS MY EASY GUIDE FOR UNINSTALL SYSTEM-APPS ON NOUGAT 7.1.1 VERSION 34.3.A.0.244 (AND ALSO MAKE THE SYSTEM HALF-WRITABLE?)(I DONT KNOW MUCH THESE SUBJECTS SORRY)
-Requires
- Version 34.3.A.0.244
- Magisked
- TWRPed
Note: Here is my TWRP and Magisking Guide Here Here Here
Installation
1. First Install
a. Android Terminal
b. Busybox By Meefik
2. Open Busybox and Install.
3. Open The Terminal Emulator. Its just like this
Code:
F5121:/ $
and type "su" just like this (NOT "Su", just "su" with little S)
Code:
F5121:/ $ su
press okay (on your keyboard)
Now this dollar symbol changed the like this #
Code:
F5121:/ #
That was First Step of terminal. Now the second step, type this command carefully
Code:
busybox mount -o rw,remount,rw /system
rw,remount,rw
-These are not dots, These are virgules.(commas)
Type and enter. If it doesnt give any error message just like this "mount: '/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy" or something, congrats you did.
-Now you can delete your system-apps using Link2SD.
-But you cant still convert the u-apps to system-apps using Link2SD!
If you want convert user-apps to system-apps, use Root Explorer.
- User-apps located at root/data/app
- So cut the folder (wanted to convert system-app) from data/app
- Paste to root/system/app
- Restart The Phone
- I know this is manual guide for converting apps but it simple and easy.
(When some apps converted, maybe doesnt work. You have been warned.)
+thanks for the SoNyek for post
+commands from YasuHamed. Thanks. His guide is here
Hi there,
I'm using a Nvidia Shield TV Pro - unrooted due to the DRM stuff like Dolby Vision.
Now I want to reconfigure Kodi from Scratch. In my current installation there are a lot packages which aren't updatable anymore.
For that reason I was using Termux to copy the Kodi userdata. That worked until one year ago. With some updates of Android this isn't possible anymore. That's very sad, because Termux is fully configured with every tool I need.
Fortunately I can access /sdcard/Android/data/com.xbmc.kodi using adb. The disadvantage: adb shell doesn't even provide VI or any other simple editor. The proposed solution to install busybox fails in need of root permission. And just to copy the busybox binary to an accessable folder didn't work too. Android gives the binary 660 permissions (no execute).
My solution for editing some configuration files in Kodi now is:
adb shell: access /sdcard/Android/data/com.xorg.kodi/files/.kodi
adb shell: cp configfile to /sdcard
Termux: Edit configfile
adb shell: cp /sdcard/configfile back to com.xorg.kodi
That's not a very comfortable solution. Is there better way modify config files of installed applications?