Related
Update2: Updated and tested under Lollipop (Sept 2015 FireOS 5.0.1 version for Fire HD 7 2014 [5.2.2u2], and should work with Fire 7 2015)
Given that a Fire tablet with Amazon experience is a terrible thing to waste, these are scripts to switch from and to Amazon launcher both under FireOS 4.5.x and Lollipop. Along with the launcher this disables a lot of battery sucking Amazon apps (the enabling script revives all of this goodness back).
The key stuff in scripts is the launcher block/unblock. I block other apps too because some of them seem to wake up a lot ("Wakelock detector" tells me this), so why not make them less obnoxious when you are not running Amazon experience ...
Naturally, you do need ROOT (how to root FireOS is a subject of other guides).
I assume you have Nova Launcher or free Google Now Launcher (on Lollipop installed as a system app in order to have Widgets working). If your Amazon launcher apk file is renamed, rename it back (verify that you do have the proper /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk ). Do make sure that you have an alternative launcher (besides the stock Amazon one !!!). Also, make sure that your adb is authorized in order to enable you to unblock the Amazon launcher in case you get the permanent Fire logo.
Go ahead install Gscript ( https://bitbucket.org/Equidamoid/gscript/downloads ). Copy either fire_on_off.zip (for FireOS 4.5.x), or fire_on_off_511b.zip (for FireOS 5.x - Lollipop) to /sdcard/gscript, and unzip scripts right in there. In "Gscript", tap the 3 dots at the bottom right corner, tap "Add script", tap "Load File", tap root required, first choose the disabling script, then repeat for the enabling script. All set.
In Nova, long tap on an empty area, it'll offer to create Shortcut. Choose Gscript/"Kindle block". Repeat for "Kindle unblock".
Then in "Nova", tap "Kindle unblock". It'll get you into Kindle Launcher, at which point you have 100% Amazon experience. Once you do your thing, and want to go back, launch/switch to "Nova", and tap "Kindle block". At this point you are back to more stock like Android.
To give proper credit, this approach was proposed by DoLooper ( http://forum.xda-developers.com/showpost.php?p=61089153&postcount=29 , and some good suggestions in a reply to this post) .
bibikalka said:
So why not switch quickly to and away from stock Amazon UI ?
Click to expand...
Click to collapse
Thanks for the post and the scripts! The shortcut makes it so easy to switch between launchers, and blocking the other packages is a great idea.
In case it's not obvious to casual reader, this lets you run any adb shell command(s) from a homescreen shortcut (and scripts that do other things, too, of course). Here are a few related tips:
Launcher: This works with any launcher that allows shortcuts on the homescreen
Gscript: I suggest using this Gscript app instead of getting it from play store. Play store version is older and less stable, and I don't think it closes after running the shortcut.
Adding the scripts (alternate method): Create a folder named "gscript" in sdcard and put bibikalka's scripts in there. Then in Gscript app, tap (3-dot) menu button, "Add script," "Load file" and the scripts will be listed.
Edit scripts from Gscript: Long press on the script name and choose Edit.
People using Freetime should edit the scripts and delete lines for amazon.kindle.kso and Tahoe. Blocking these causes bootloop.
I'm on 4.5.3 root with Google play, does it Worth upgrading ?
This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.
DoLooper said:
This works with any Fire OS; don't need 4.5.4, just have to be rooted. If you use the Amazon launcher occasionally, try this.
Click to expand...
Click to collapse
Has anyone made a version of this for Lollipop ???
bibikalka said:
Has anyone made a version of this for Lollipop ???
Click to expand...
Click to collapse
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)
DoLooper said:
Not I. (Kinda puts the lie to that old post, eh?)
Commands for developers preview:
pm disable com.android.launcher
pm enable com.android.launcher
am start -n com.android.launcher/com.android.launcher2.Launcher
5.2.2u2 enable/disable = pm disable com.amazon.firelauncher
I can guess start is:
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
. . . but I can't test cuz I don't have a custom launcher right now. Maybe someone else can test this ??? If not, I'll figure it out in next few days. (You're still on 4.5.5?!)
Click to expand...
Click to collapse
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.
bibikalka said:
OK, thanks! I just got a 5th gen Fire 7 for a present, and will play with it to see how this blocking works on Lollipop.
Click to expand...
Click to collapse
It works "interestingly." Played with it today to update the block sys app post. Start command:
am start -n com.amazon.firelauncher/.Launcher
Couple interesting (to me) things:
Disable:
- If you only have one alternate launcher, disabling firelauncher immediately takes you to alternate. (But maybe it did this before. I've always had multi alt launchers.)
Enable:
- You stay on alt launcher, but tapping Home icon takes you to Fire launcher (even with multi alt launchers installed).
- Enable and switch = same as before: run enable and then run start
Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!
bibikalka said:
Updated and tested for Lollipop. Thanks to DoLooper for the suggestions!
Click to expand...
Click to collapse
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...
I enjoy the Nova Prime(paid app) no ads lots to customize
phfoneman said:
I want to give this a try on my Fire HD7 and have only been using the Amazon launcher to this point. What is the preferred Android launcher most of you use and do you go with the free launcher or purchase a particular one? I see a couple varieties of Nova at the Play Store and have to assume the purchased one does not have ads, so thought I would ask your preferences before giving it a try. Thanks in advance for any advice you provide...
Click to expand...
Click to collapse
What don't you try the free Google Now launcher ? Once you see how this works, perhaps you'll try Nova.
In case you overdo launcher switching and end up with no working launcher, just remember you can always save the day with these commands in adb (as long as keep the amazon launcher intact, and just block it via "pm disable" as the script above does it):
pm enable com.amazon.firelauncher
am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
No need to answer, easily fixed my problem by factory reset in recovery
Yevgen.A said:
Hi all, I have run kindle_block_5_1.sh and then reboot device. I am stack with "Fire" logo at the boot. I have access to ADB, but could not receive root access in adb shell. Can anyone advice me? How can I revert changes after that script back?
Thanks in advance
Click to expand...
Click to collapse
Yevgen.A said:
No need to answer, easily fixed my problem by factory reset in recovery
Click to expand...
Click to collapse
Rookie mistake No launcher present, no adb authorized ! But I've added some messages to the original post to mention this issue.
I can't get Nova to create a Gscript shortcut at all. I press the Gscript disable option and it dumps me back to the Amazon launcher.
Hello to everyone,
as promised in my old thread, here is a first version of the automatic script to replace the launcher.
For now, firelauncher will be replaced with cyanogenmod's trebuchet.
If you want to use a different launcher, just replace the apk in the folder. (Remember to rename your new file to trebuchet.apk.)
No root is required for this to work.
This will not work with regular updates to 5.1.1!
Only for those who kept the old bootloader.
I will update the script to work with 5.1.1 later today
Remember to enable usb-debugging before running the script and make sure your PC is authorized.
There are automatic delays in the script, but check the necessary points when asked to do so, because boot-time can be really long sometimes.
As no one complained about the original script, I do believe that the basic steps are working properly.
However: I'm not responsible if anything goes wrong, please keep that in mind.
Credits go to @csolanol for finding root, @Awesomeslayerg for summing up the manual steps (If you don't like scripts, just take a look at his thread, it's good too), and to all those other people that were involved in working on boot.img and root.
Trebuchet is a cyanogenmod app, please refer to their website and xda-posts for further information.
Changelog:
V1.1:
Added some automatic delays and reduced the "pause"-commands, runs with a little less user-interaction.
Let's sum it up as more one.click.
V1.0:
Initial release
Planned features:
Allow the user to choose between trebuchet and any other launcher he copies into a special folder.
Make it easier, more documentation, clean up
Thanks for the package could come in handy for me with my daughters fire I did mine the longer way
Sent from my HTC One_M8 using Tapatalk
Okay good, should work for you as you already know the steps
If anything goes wrong booting the boot-firelauncher.img again and copying firelauncher.apk back in place will fix it.
But that should only be needed if connection is lost or any other unusual thing happens.
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
cryophil said:
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
Click to expand...
Click to collapse
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Vlasp said:
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
cryophil said:
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
Click to expand...
Click to collapse
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Vlasp said:
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
No problem, and good luck!
Sent from my KFFOWI using Tapatalk
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
Just to clarify, for the launcher replacement, the boot.img is used just to make the system partition r/w so that the changes can be made to replace the launcher. So the r/w mounting of the system partition will only last for that one boot, but the replacement of the launcher will be "permanent," in that it will persist after reboot. The rooting procedure uses the same method to copy the necessary su binaries to the device and set permissions.
So if you follow this procedure for replacing the launcher, it will be permanent with no need to then also root the device in order to make it permanent. Of course, you can also then root the device if you want, but you don't need to in order to replace the launcher.
Will the home button work after running this? I had read in some other threads about replacing the home screen messing up the home button.
Yes, the home button will work after using this.
Even widgets should work.
Maybe I'm missing something, but I don't see the script anywhere.
Was due to updating, you can find the new version 1.1 in the first post.
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Enviado desde mi KFFOWI mediante Tapatalk
Darkside1984 said:
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Click to expand...
Click to collapse
So you want to replace the trebuchet.apk with google now launcher and use that as your default?
If you rename your apk file to trebuchet.apk that will work.
But google now launcher is reported to be rather unstable as default one somewhere else in this forum, so it might be a better idea to install trebuchet using the script and then google now launcher from play store.
That should allow you to choose between the two and set now launcher as default one, but with a fallback to trebuchet.
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
below seems to be "USER ERROR"
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
a1yet said:
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
Click to expand...
Click to collapse
I can confirm the first issue, but it also exists if you replace the launcher manually (as I did), will look at were it comes from tomorrow.
The second one appears like you ran pm hide on the default video player and should not be related to the script.
ChrBeck said:
you ran pm hide on the default video player
Click to expand...
Click to collapse
thank you
i installed VLC after hide should it not use it as my default video player ?
or do i have to unhide the default one ?
Download the latest tools from the AFH link near end of post. It includes the changes in the attached "jobs" zip. You only need "jobs" if you downloaded the tools before May 11
EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
UPDATE May 17: Install Other Launcher and Install Kingroot tools may not complete if Windows username has spaces. I'll fix in next update. Until then, if your username has spaces, use this fix.
Here are tools for the 2014 Fire HD 6 and 7. A little late, I know, but some of you who still troll the forums may find them handy. Download the tools from AFH link, extract and run RUNME.bat.
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
Tested working on OS 5.1.2.1 and below, except:
- Current Kingroot can't root 5.1.2.1. You need to downgrade. See "ROOT OS 5.1.2", below.
- OS 4: Only OTA blocking is implemented in the Block/Unblock jobs. [5/13/16 UPDATE: Also, Play Store isn't working on OS 4.
.. I probably won't fix it unless there's some demand. Try the video guide here. OS 4 users, also see post #11 for useful info about custom launchers.]
THE TOOLS
Install Play Store
Install Nova Launcher to /priv-app [root]
Install Other Launcher to /priv-app [root]
Uninstall priv-app Launchers [root]
Install Apps
Block/Unblock: OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH [root]
Root Checker
Device Info
Root Tools
Install Kingroot ~ Root ~ Block OTA
Replace Kingroot with SuperSU [root]
DESCRIPTIONS
Before running a job, look here for any tips and instructions. This info is also in the readme.txt in the zip
INSTALL PLAY STORE - Like it says. Works on both rooted and unrooted OS 5. Not for OS 4. EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
INSTALL NOVA LAUNCHER - Installs Nova to /system/priv-app so widgets work. If you just rooted, make this your first custom launcher. You can replace it or add a different one later.
INSTALL OTHER LAUNCHER Installs the launcher app in user_launcher folder to priv-app. Get the apk for the launcher you want (from apkmirror.com for example) and put it into the folder and run the job. EDIT 5/16/2016: Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.)
HOW TO INSTALL GOOGLE NOW (also in Readme.txt):
It's much easier to install Google Now if Amazon is blocked, and you need a custom launcher to do that.
1. If you don't have a custom launcher installed, use Install Nova tool (installs Nova and blocks Amazon)
If you have a custom launcher, block Amazon so your custom launcher is running.
2. Get Google Now (small) from apkmirror.com, e.g., put into user_launcher folder and run Install Other Launcher job.
You'll boot to your "other" launcher
3. Run Google Now in app drawer and:
If prompted to Update Google App (Get it from Google Play), do it.
If prompted that other launcher is default, tap link to go to Amazon Settings. In Apps & Games>Manage all Applications: Swipe to All, scroll to your other launcher, tap it and see if "Launch by Default" is on. If yes, Clear Defaults. If no, go to your launcher settings and see if you can turn off default there.
Some launchers don't give up their default easily. If pressing home key doesn't show "Select Home App" after doing the above, run Block/Unblock tool and switch to Amazon. Then block Amazon again. After restart, press home key and you'll get "Select Home App" and be able to choose Google Now.
UNINSTALL LAUNCHERS - Uninstalls and deletes everything associated with a launcher installed to /priv-app. If multiple, prompts you to choose the one to uninstall.
INSTALL APPS - Installs all the apps in the user_apps folder. Put the apks into the folder and run the job. Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.) Don't install a launcher with this; use one of the launcher tools.
BLOCK/UNBLOCK - OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH
Except for OTA, these work only on rooted OS 5. OTA does a soft block on unrooted OS 4, hard block on rooted.
OTA: Disables update packages and renames DeviceSoftwareOTA.apk for a "hard" block. Unblock reverses it.
ADS: Blocks/unblocks the lockscreen ads.
AMAZON LAUNCHER: Block disables the stock launcher (Amazon UI) and the Appstore, which forces the home key to use your custom launcher. Unblock switches you to Amazon. Checks for custom launcher before disabling Amazon. Black screen with multiple custom launchers: If you haven't set a default launcher, disabling Amazon will boot to black screen. (System doesn't know which launcher to use.) Press home key (circle at bottom) for launcher choices. TIP: To easily switch between your launcher and Amazon, use @bibikalka's guide here to set up "one-tap switching" from launcher home screen.
APPSTORE: Blocks the appstore so in-app links take you to the Play Store (instead of throwing that stupid Appstore prompt). Amazon complains bitterly if you run this from Amazon UI, so use it at your custom launcher or just use the Amazon launcher block.
AMAZON SEARCH: If you have Google Search installed, blocking Amazon Search makes your launcher search bar use Google instead of Amazon shopping.
DEVICE INFO - Just some specs that I find interesting. Lazy man's way to find out which tablet is plugged in, OS it's running, whether rooted . . .
INSTALL KINGROOT, ROOT, BLOCK OTA - Installs Kingroot, prompts you through rooting and blocks OTA updates.
- Installs kingroot v.4.8.5 by default.
- You can skip installation if Kingroot already installed
- You can install a later version if available: Check for new versions here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
ROOTING AND UPDATES: An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
Amazon says that updates install when the the device is not being used, but be aware that on OS 5 there's some risk. To minimize the risk, never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.) To eliminate all risk, you can downgrade and root OS 4.5.3. On OS 4 the tool blocks update installation before rooting. (There's no way to do this on OS 5.) From OS 4.5.3, you upgrade with root in TWRP per bibikalka's root Tut.
True story: Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the kingroot tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
REPLACE KINGROOT WITH SUPERSU - Installs W0lfDroid's sh script and prompts you through using it to replace Kingroot.
I reviewed and tested the script and it does (only) what it says: Removes all Kingroot (except Purify app, which tool uninstalls) and installs SuperSU. The tool uses SuperSU v. 2.4.6 for OS 5 (known working on OS 5.1.2) and SuperSU v. 2.4.9 for OS 4 (because 2.4.6 didn't seem to work).
FULL DISCLOSURE: I lost root one time after running this on OS 4. I think the problem was SuperSU 2.4.6 and that's why I changed it. I've tested many times and this only happened once, but you should know it happened. AFAIK W0lfDroid script is still the best free tool for the job.
ERRORS: Script was written to remove Kingroot from multiple android versions, so it tries to remove Kingroot files that don't exist on Lollipop. THIS PRODUCES LOTS OF ERRORS. THAT'S OK. I left in all commands so it will work on OS 4, too.
USE THIS SOON AFTER ROOTING. W0lfDroid's script should work fine even with root apps installed, but all I know for sure is it runs quick and easy on a "fresh" system.
ADB Sideload
There's an adb-sideload job in the jobs folder. I didn't put it on the menu because it uses commands that may not run on some systems. Also, if you know what you're doing, it's probably faster to manually sideload an update. If someone wants to try it, put the update bin file into adb_sideload folder and run sideload.bat.WINDOWS TESTING: Script was tested on English-language versions of Win 7 Pro and Home. Some testing on Win 10. (Thanks @SpaceBananas!) There's nothing that can hurt your tablet, but there may be kinks to work out based on Windows version. Hope a tester will work with me to help make the tools accessible to everyone. Thanks!
ADB DRIVERS REQUIRED: Try the guide in first link below. If problems, try the second.
Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
ROOT OS 5.1.2
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
ROOT GUIDE: Follow this guide to use Kingroot and the root tools to set up your tablet.
At this time, Kingroot can only root OS 5.1.2 (February 2016) and below.
You can downgrade OS 5.1.2.1 (March 2016) to 5.1.2 and root, as explained in Root Guide, but this is an exception!
In general, never downgrade in order to use Kingroot. It's the fastest way to a brick!
You may be able to safely downgrade a higher OS to OS 4.5.3, root, and then upgrade in TWRP per @bibikalka's root Tut. Before trying this on an OS later than 5.1.2.1, make sure the tutorial says it's safe.
DOWNLOAD THE TOOLS FROM AFH ➔ . FireHD_TOOLS v 1.2
Update as of 5/11/16
➔ If you got the tools before the update, just replace the jobs folder in FIREHD_TOOLS with the one in attached "jobs_v1.x.zip"
Change Log
5/11/2016 - v1.2: Updated sideload.bat. (Missed the Find/Findstr fixes.)
5/10/2016 - v1.1: Fixed "No such file or directory" and "Permission denied" errors for users with *nix Find command installed
.
Nice Work!
@DoLooper - Magnum Opus, no less !
Why version 0.1 ??? The first release - solid 1.0 !!!
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Updated again <sigh>. Sideload tool didn't get updated in v1.1. Apologies to those who downloaded the jobs zip.
DoLooper said:
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Click to expand...
Click to collapse
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Thanks again!
notorious.dds said:
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Click to expand...
Click to collapse
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
DoLooper said:
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
Click to expand...
Click to collapse
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
notorious.dds said:
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
Click to expand...
Click to collapse
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work? This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
BTW, how come you want to stay on OS 4?
DoLooper said:
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work?
Click to expand...
Click to collapse
Nope.
DoLooper said:
This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
Click to expand...
Click to collapse
I think I tried that to no avail, but I can't remember exactly which module I used.
DoLooper said:
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
Click to expand...
Click to collapse
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
DoLooper said:
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
Click to expand...
Click to collapse
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
DoLooper said:
BTW, how come you want to stay on OS 4?
Click to expand...
Click to collapse
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
notorious.dds said:
. . .
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Sorry to hear about the brick. Good thing Amazon is patient with us.
Yes, wallpaper works fine on OS 5. [For others who read this, on OS 4 the only way to get wallpaper is with Xposed (installed in TWRP) and the kindleBG module in the link I posted above. And BTW, although the tools don't block OS 4 Amazon launcher ATM, it can be done manually. Commands are here.]
Thanks for your input. Play store didn't work for me either this time, despite earlier success. Everything else except the launcher block (and other non-OTA blocks) does work, so for now I'm just going to edit post and see if there's any other interest in play store on OS 4. (I trust you'll get OS 5 on replacement or will want to update to it.)
As to TWRP: Once tablet is set up, booting TWRP isn't needed much except for upgrading. and bibikalka gives us lots of options for doing it.
Let us know if anything comes of UART port tests. You'd be the hero of the community!
Workaround for Windows username with spaces
The Install Other Launcher and Install Kingroot jobs may not complete if your Windows username has spaces in it. I'll fix this in next update. Meanwhile here's the workaround:
1. Right-click RUNME.bat and choose Edit. [file opens in Notepad]
2. Add a blank line under :: Set paths and run menu.
3. Type: SET "username=abc"
4. Make sure this section of RUNME looks like below and then save and close Notepad
Code:
:: Set paths and run menu.
SET "username=abc"
SET "main=%CD%\"
SET "jobsdir=%main%jobs\"
[remaining code]
This changes the username only for the tools. The rest of Windows continues to use the real username.
I'm getting ready to update. Please let me know if you found any problems.
Used the tool on my Fire HD 6 (4th Gen) running a Rooted OS 5.1.2.1 to install a new launcher and block OTA's, ads, fire launcher, appstore, and Amazon search. Everything worked without issue! Thanks for the awesome and simple to use tool! Tablet is now almost pure Android. Great work!!!
Sidenote: Used bibikalka's TUT (http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950) on my Fire HD 6 that was currently running Fire OS 4.5.3 with TWRP Recovery to obtain a Rooted Fire OS 5.1.2.1..
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
wallywallywally said:
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
Click to expand...
Click to collapse
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
sd_shadow said:
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
wallywallywally said:
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA Labs
Confirmed, this procedure worked for Fire (5th generation), however the amazon update file is different (see a few posts back)
I just got a fire HD 6 (4th Gen) with the 4.5.2 OS.
Everything I see talks about 4.5.3 and later. I have not turned on wifi, so basically in a holding pattern for now. I want to root/twrp and maybe a custom rom.
Can some give me advice on the best path to take? Should I upgrade then root? Or root then upgrade? Any advice is appreciated.
[SIZE=+3]TWRP scripts: Ad removal - Debloat - Block OTA[/SIZE]
[SIZE=+2]Amazon Prime Variant and OEM Variant[/SIZE]
Tested on Prime and OEM variants. Please report back if any issues
[SIZE=+1]This guide only require you to be able to boot TWRP. You can follow this TWRP install guide and perform the installation of these .zip files AFTER step 8) (You must backup your system in case anything goes wrong, you will also need this backup to perform any future OTA, such as the one activating band 12). You can either stop there after installation, or proceed to the following steps if you want to have root access.[/SIZE]
[SIZE=+1]All .zip have to be installed using the TWRP "Install" function. You will need to download them on your phone or copy them on a SD card. You do not need to install all these packages at once. These scripts do not install or remove anything on /system, they only rename some files. All scripts can be extracted and opening "update-binary" with your favorite text editor will allow you to see exactly what is done (always a good idea if you are concerned with your device security), and customize it if you wish.
This will only rename the stock apps in your /system. If an update was performed, or if you used the app previously, the app and it's files may still be present on your device /data even after running these scripts but you will be able to uninstall them as any other app. This also means that you can rerun these scripts after a future OTA and they will not erase any app you reinstalled yourself on /data.
A "reset all" script is also provided to restore all apps and unblock OTA.
You can individually restore any app by using a file manager with root access (or TWRP built-in one) and rename any "*.apk_" to "*.apk", app will show up again after the next reboot.
[/SIZE]
[SIZE=+1]Disable ads, block OTA and Amazon PARTIAL debloat "bluR1-AMZ-PARTIALdebloat-blockOTA"[/SIZE]This package will remove all the ads from your Prime phone and block future OTA. You DO NOT need to reset / wipe your phone after installation.
It will also remove all Amazon apps from your system except for the Amazon Underground app store (recommended).
This option allows automatic background updates from the amazon app store and do not need you allow the installation of packages from unknown sources.
[SIZE=+1]Disable ads, block OTA and Amazon FULL debloat "bluR1-AMZ-FULLdebloat-blockOTA"[/SIZE]This package will remove all the ads from your Prime phone and block future OTA. You DO NOT need to reset / wipe your phone after installation.
It will also remove all Amazon apps from your system including the Amazon Underground app store.
[SIZE=+1]Google PARTIAL debloat "bluR1-GOOGLE-debloat"[/SIZE]This package will remove SOME stock Google apps that can be easily downloaded from the google play store and are not required for the system.
This will only remove apps in the /system partition. This means that if you downloaded or reinstalled some of the apps they won't be removed by the script. It also means that if you previously used the phone and some apps were updated they will still be installed in your /data/app, but you will be able to uninstall them manually as any other app.
List of removed apps and their Google Play link for easy reinstall:
Google Search bar on home screen
https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox
Google Talkback
https://play.google.com/store/apps/details?id=com.google.android.marvin.talkback
Google GMail
https://play.google.com/store/apps/details?id=com.google.android.gm
Google Play Music
https://play.google.com/store/apps/details?id=com.google.android.music
Youtube
https://play.google.com/store/apps/details?id=com.google.android.youtube
Google Drive
https://play.google.com/store/apps/details?id=com.google.android.apps.docs
Google Maps
https://play.google.com/store/apps/details?id=com.google.android.apps.maps
Google Chrome
https://play.google.com/store/apps/details?id=com.android.chrome
Google Talk Services
https://play.google.com/store/apps/details?id=com.google.android.tts
Google Play Videos
https://play.google.com/store/apps/details?id=com.google.android.videos
Google Photos
https://play.google.com/store/apps/details?id=com.google.android.apps.photos
Google Agenda
https://play.google.com/store/apps/details?id=com.google.android.calendar
Google Hangouts
https://play.google.com/store/apps/details?id=com.google.android.talk
Google Calculator
https://play.google.com/store/apps/details?id=com.google.android.calculator
Google Clock
https://play.google.com/store/apps/details?id=com.google.android.deskclock
It will not disable Google Play store, Play services etc. Some of the apps can be removed by editing the script yourself. See the "update-binary" file. No additional help to do so will be provided, do it at your own risks.
[SIZE=+1]Mediatek and BLU PARTIAL debloat "bluR1-MTK_BLU-debloat"[/SIZE]This package will remove SOME stock Mediatek and BLU apps.
Remove useless BLU app and Opera preinstaller.
Remove the ugly File Manager app. Replace it by any other file explorer app is you like.
Amaze File Manager is a great and open source alternative https://play.google.com/store/apps/details?id=com.amaze.filemanager
[SIZE=+1]Restore all apps and OTA "bluR1-RestoreApps-OTA"[/SIZE]This package will restore all apps and unblock OTAs.
Changelog:
07/30/2016 - Topic creation. Amazon ad removal / debloat / OTA blocking scripts from the original post moved here for a better visibility. Initial release of Google and Mediatek debloat scripts.
08/17/2016 - MTK debloat script updated to fix FileManager removal bug
10/01/2016 - Scripts updated to v2. Now only rename files, restore script provided (V1 downloads: AMZ-PARTIAL 740, AMZ-FULL 828, GOOGLE 747, MTK 536)
05/31/2017 - Some scripts updated to v2 or v3, support V8.4 and V21 changes in folder and apk names. (V2 downloads: AMZ-PARTIAL 774, AMZ-FULL 1208, MTK 544, RESTORE 294)
07/13/2017 - MTK and OTA restore script updated to fix a typo in BLUHelp debloating. (V3 previous downloads: MTK 60, RESTORE 44)
thanks for this! very nice of you to make all the different options as well.
worked great for me on first try.
Now I'm tempted to buy the 50 version, would this leave your phone as stock?
rmartinezdl said:
would this leave your phone as stock?
Click to expand...
Click to collapse
I do not have access to a stock ROM or nandroid backup to compare everything so I can't be 100% sure but as far as I know pretty much yes.
Scripts worked perfect and didn't delete the Google apps I actually use! Thanks!
Problems after Factory Reset
after factory reset got a Error looping, “Unfortunately, Setup Wizard has stopped.”
Method to bypass problem,
1. Boot into TWRP Recovery
2. Mount System ( Mount → check System )
3. Advanced → File Manager
4. Browse to /system/priv-app/Setup-Wizard
5. Delete it
Also, home button and menu button doesn't work
(had to restore from backup)
Fibrizox said:
after factory reset got a Error looping, “Unfortunately, Setup Wizard has stopped.”
Method to bypass problem,
1. Boot into TWRP Recovery
2. Mount System ( Mount → check System )
3. Advanced → File Manager
4. Browse to /system/priv-app/Setup-Wizard
5. Delete it
Also, home button and menu button doesn't work
(had to restore from backup)
Click to expand...
Click to collapse
Or in between the pop up error messages you can go to Settings-> Apps->App Permissions and give Setup Wizard the necessary permissions.
So to clarify I can use the script to also disable ota for a prime that's been converted to OEM? excellent
I am a Prime-Member and would like to buy two NEW BLU R1 HD - 16 GB - Black - Prime Exclusive - with Lockscreen Offers & Ads:
https://www.amazon.com/dp/B01H2E0J5M/ref=twister_B01G7TG6SW?_encoding=UTF8&psc=1
However, since I am buying these two cellphones for my sons, and I don't want that they have access to my amazon account details...
So, I would like to know if these phones will come fully registered to my Amazon account, or if it is possible to block or unregister these phones to my Account ?
So, my Amazon Orders, List and Shopping Cart, can not be seen or used by my sons ?
At first and if not totally necessary, I not want to root or modify nothing on this Blue phone... I just would like to totally block in some simple way, my Amazon account that I will use to purchase these phones, possibly because both will come already registered to the same account.
ulises.rodriguez said:
I am a Prime-Member and would like to buy two NEW BLU R1 HD - 16 GB - Black - Prime Exclusive - with Lockscreen Offers & Ads:
https://www.amazon.com/dp/B01H2E0J5M/ref=twister_B01G7TG6SW?_encoding=UTF8&psc=1
However, since I am buying these two cellphones for my sons, and I don't want that they have access to my amazon account details...
So, I would like to know if these phones will come fully registered to my Amazon account, or if it is possible to block or unregister these phones to my Account ?
So, my Amazon Orders, List and Shopping Cart, can not be seen or used by my sons ?
At first and if not totally necessary, I not want to root or modify nothing on this Blue phone... I just would like to totally block in some simple way, my Amazon account that I will use to purchase these phones, possibly because both will come already registered to the same account.
Click to expand...
Click to collapse
They do not come registered to your account at all. Signing into an amazon account is an option during setup, but not required.
Thanks for letting me know that these BLUE phones, not come pre-registered to an amazon account...
That's just what I wanted to know before ordering my two phones.
The scripts worked perfectly except for the MTK one. The ugly file manager is still there.
oakami said:
The scripts worked perfectly except for the MTK one. The ugly file manager is still there.
Click to expand...
Click to collapse
This is strange. What phone version do you have? (Prime, normal, Prime converted to normal, etc)
Is the Gallery App gone? If yes try to uninstall the file explorer manually like any other app, else try to run the script again to be sure nothing went wrong.
emc2cube said:
This is strange. What phone version do you have? (Prime, normal, Prime converted to normal, etc)
Is the Gallery App gone? If yes try to uninstall the file explorer manually like any other app, else try to run the script again to be sure nothing went wrong.
Click to expand...
Click to collapse
I have the prime version. I flashed TWRP plus superSU and Xposed. The gallery app is gone. I tried installing the script again but the file manager is still there.
oakami said:
I have the prime version. I flashed TWRP plus superSU and Xposed. The gallery app is gone. I tried installing the script again but the file manager is still there.
Click to expand...
Click to collapse
Found the problem. Please redownload the script from the original post, I updated it and it should now remove properly the file manager.
Thank you for your bug report!
Thanks so much for this.
Also wanted to let people know that I removed Google Play Service and Google Play (store) without any issues so far.
I will update this post if I run into any problems.
Thanks again!
Any way to make the Camera app launch Google Photos? It now just gives me an error since I removed the Gallery app...
lostman1027 said:
Any way to make the Camera app launch Google Photos? It now just gives me an error since I removed the Gallery app...
Click to expand...
Click to collapse
No, use of the default gallery app is hardcoded in the camera app.
You can only launch Google Photos using the shortcut displayed after taking a new picture.
If you use an alternative camera app (I use Open Camera https://play.google.com/store/apps/details?id=net.sourceforge.opencamera ) these will correctly launch Google Photos or any other default gallery app.
For testing purpose (seems to work ok on my phone) here is an update of the scripts.
These ones will not delete the apps in /system but rename them from *.apk to *.apk_ effectively disabling and hiding them.
Two main advantages:
- Each app can easily be individually disabled/reactivated using TWRP builtin file explorer or any file explorer with root access by renaming them back to *.apk.
- Easily revert to an out of the box state to be able to apply an OTA update by simply using "bluR1-RestoreApps-OTA.zip" script. This will "rebloat" your system. If you installed root etc you still have to take care of this yourself.
If you are giving these scripts a try, please report success / failure so I can eventually update the original post.
Edit 09/10/2016: scripts updated to debloat non-prime phones, restore script released.
Edit 10/01/2016: scripts are now available on OP, beta is over. Thanks to the few testers that reported back!
Oops, wrong thread.
Hi. I recently change my phone ROM to a custom one, after one year using the phone just as it came.
I installed Pixel Experience+, which its great, but there's two stock apps that I miss: Mi Screen Recorder and Mi security app.
Stock screen record was awesome: Just one touch on status bar to start recording, a floating button to start/stop and it let you record system audio and mic audio, choose 1080/720, 30/60 fps, etc. The Pixel experience+ one its just start/stop and nothing else, I don't even know if it's HD.
Security app was great too: Good trash cleaner, and a App Lock option by pin/fingerprint that it works great.
Is there a way to install those apps in Pixel Experience rom ? I tried to install apkmirror apks but it didn't work. Maybe it's something that it needs to be flashed. Or something that it just can't be done, that's why im asking.
Thanks!
ps: I just intalled the ROM, I didn't root the phone.
Some of them.
Short answer is NO at the moment there isnt any zip file that you flash it and boom Mi apps installed. (like the gapps) What you can do is to track & find which Mi-apps you want to install (manually).
What i had done in the past was to find the Mi Home launcher apk and the gallery i thing if you search you may find more apks but keep in mind that you can replace every single one app, just search for an alternative.
user171 said:
Short answer is NO at the moment there isnt any zip file that you flash it and boom Mi apps installed. (like the gapps) What you can do is to track & find which Mi-apps you want to install (manually).
What i had done in the past was to find the Mi Home launcher apk and the gallery i thing if you search you may find more apks but keep in mind that you can replace every single one app, just search for an alternative.
Click to expand...
Click to collapse
Thanks for the answer. That's bad new, I really liked those apps.
Yeah, I tried to download Screen Recorder and Mi Security apks from akpmirror and install it, but I couldn't.
I guess I'll have to try a third part app lock and screen recorder. Any suggestion?
uum... try to avoid 3rd party app lock (your custom rom may include that option already) as for screen recorder nop i dont have any suggestion. :|
**UPDATE 02/10/2020**
Im going to share with you what i found after some research on the web even tho i havent test anything yet from the sources that im going to link below. I hope it helps
MOD EDIT: Link Removed