Database Users

Can't get ADB Root Access in certain ROMs?

I've noticed with a lot of CM10-based ROM's (possibly even others), I am unable to get root ADB access.
On the ROM's that have it, I set the Root access to Apps and ADB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can reboot, fix permissions, clear caches, but no matter what, Android Commander is never able to get Root access
This isn't the case on some ROM's I've tried though. Android Commander is able to get Root access just fine without me needing to do anything.
To name some ROM's that I can't get Root access with:
CyanogenMod 10 Nightly (9/4)
AndroidME CM10 N7 1.0.0
As for what ROM's had working Root access, I can't exactly recall correctly :/ But I think these had it working:
Codename Android 3.4.1
Team EOS 3 *JELLYBEAN* Nightlies (confirmed working ADB root)
Is there something else I should possibly be doing to get Root access on CM10-based ROM's?

Boot a unsigned kernel then ./adb remount
PS: it is effective until you reboot
Sent from my Nexus 7 using Tapatalk 2

"The Root access : No" because you'r using the rom which have a "secured adb" (even when you'r rooted)
Download the "adbd insecure" in this thread and "Enable insecure adbd", you can get "Root access: OK" in any rom
http://forum.xda-developers.com/show....php?t=1687590

adb root
The real reason behind adb root or insecure adb is the adb daemon in the device running at root permissions. In pre-Android 4.1 versions, this is usually decided by some initialisation script(like init.rc) at boot time. The script checks for value in default.prop,local.propand other environment variables.
If it finds build.prop,default.prop or local.prop property file with ro.secure=0 adbd is allowed to run as root. You'll get adb root and hence will be able to do commands like adb remount,adb root and adb shell's prompt'll be # by default. The user may be displayed as [email protected] or [email protected] adb GUIs like Android Commander and QtADB will get to work in Root mode.
But,if it's ro.secure=1, adb daemon is made to work in secure mode, and adb won't change to root mode on issuing adb root command. However, if su binary is present in $PATH, u can still call su command from adb shell. But, it's not enough for Android Commander to get Root Access. It is possible to attain adb root through any one of the following methods:
1.For CyanoGenMod based ROMs there is an option in Settings->Developer Settings->Root access to control root access. Choose ADB only or Apps and ADB in options to get adb root.
2.Else use adbd Insecure app by chainfire if you have a rooted device. This is useful, especially for Android 4.1+ devices.
3.Or, you may manually edit default.prop to set it's value to 0, but original default.prop will be restored from boot partition everytime you reboot(this is the reason why adb Insecure cannot permanently do adb root, though there is an option to repeat the rooting procedure everytime the device boots). This method is called temporary adb root. On pre-Android 4.0 ROMs default.prop file was located in / directory. I read that from Android 4.x this file is in ramdisk and so more difficult to edit. But Android 4.0 has local.prop which is easier to modify than default.prop( See method 5)
4.For permanent adb root, you'll have to extract boot.img, change default.prop, repack and then flash it back to device.
5. In Android 4.0 there's local.prop file in /data partition. Setting ro.secure=0 in this file will do adb root permanently. Else you can set another property ro.kernel.qemu=1 in the same file. But, this value makes the system think that it is running in an android emulator. Many exploits and root methods set this property temporarily to gain root. But, it may cause side effects if used permanently. Setting ro.secure=0 is recommended. Do this command in terminal app or adb shell:
echo ro.secure=0 >/data/local.prop
or you can manually copy a local.prop file with ro.secure=0 as it's content to /data.
6.Note that method 3,4 and 5 won't work in Android 4.0 Jelly Bean onwards. According to Dan Rosenburg(drjbliss in XDA),the researcher who discovered adb root emulator exploit and many other exploits, Jelly Bean doesn't parse any property files to set the ownership of adb daemon. The stock adbd will have to be replaced with an insecure one to gain adb root. But still,as adbd is located in /sbin whose contents are reloaded everytime on reboot from boot.img, it won't be permanent.
7. For permanent adb root, you may flash an insecure boot.img(one that contains and insecure adbd)
8. If you're really desperate and can't get adb root to work with any of the above methods use an exploit. Most of the adb based rooting methods utilise some exploit to make the adb daemon run as root. By studying the exploit and implementing it you could gain adb root atleast temporarily.I'm not recommending this method but as a last resort you could try them.
Acknowledgements: Thanks to Dan Rosenberg for explaining the reasons behind adb root, especially the one in Jelly Bean.

get root access with root commander
Question to that fantastic answer above.http://forum.xda-developers.com/images/smilies/good.gif
How do I push back my modified build.prop?
I have HDC S3 Ex v2 hung in bootloop, after changing vm heapsize to 60 from 64.(Tried 128 but it didn´t stick, so tried this and it unfortunately worked)
I have managed to start in recovery mode even though it´s chinese there, don´t understand, I can communicate through Android commander to pull the files but cannot push them back due to no "root access".
I installed the "insecure ADB" via Commander but it does no good when I can´t load android.
I have no backup. It is rooted Android 4.1.2 by Fastcardtech. has busybox installed

Use su in adb shell
Use adb shell and elevate to root access by using su
Code:
su
.
Now, if you get # prompt instead of $ sign you have root on adb shell. But, still you don't have adb root. So, don't try to push the files or use Android Commander. Instead we use shell commands to do the same.
First Remount /system partition as writeable.
i.To do this first type
Code:
mount
and find out system's device name and file system from the list. In case of my device (and many Stock ICS devices) this device name would be /dev/block/mtdblock?. ? varies for each device. I had /system as mtdblock8 with ext3 file system.
ii. Now type the following command
Code:
mount -o remount,rw -t <filesys> /dev/block/mtdblock? /system
use the number you have for '?' and the filesystem for <filesys>.
Now Copy the modified file to some readable location on the device, say /sdcard or /data/local/tmp. Then copy the build.prop to /system using cat command
Code:
cat /sdcard/build.prop > /system/build.prop
Hope it works!

Closer...
HEXcube said:
Use adb shell and elevate to root access by using su
Code:
su
.
Now, if you get # prompt instead of $ sign you have root on adb shell. But, still you don't have adb root. So, don't try to push the files or use Android Commander.
Copy the modified file to some readable location on the device, say /sdcard or /data/local/tmp. Then copy the build.prop to /system using cat command
Code:
cat /sdcard/build.prop > /system/build.prop
Hope it works!
Click to expand...
Click to collapse
Thank you! But...
After more than one hour installing android-sdk, I got the # ( I thought the shell through android-commander was the same first)
but it says Read only file system
Another thread suggested "remount rw" before pushing but thats not something adb shell recognices "not found".
Am I only missing the adress of my device when trying remount?
Any suggestions?

Renount /system as rw
Oh, i forgot! You've to remount /system as Read Write. I've edited the above post to include that.
You need not have installed the whole Android SDK(unless you develop for Android). It's the same adb that Android Commander or QtADB uses. You can even use adb as a standalone tool along with the required libraries(dlls on windows). Now that you have installed the Android SDK, it doesn't matter.

Yes! Yes! Yes!
HEXcube said:
Oh, i forgot! You've to remount /system as Read Write. I've edited the above post to include that.
Click to expand...
Click to collapse
:good::good::good::victory::victory::victory:
It worked! Thank you so much! A new phone useless was really disappointing, but happy again
Set heap size back to 64. Maybe I´ll dare set it to 128 another day... The phone has horrible ram performance, hoping that would cure it.
Uninstallation of an app of 6-7 mb takes at least 45 sec. My old Blade with cyanogen does that in less than 10.
Hard part was understanding my system name /dev/block/mmcblk1p1 cause it wrote /storage/sdcard vfat after it.
I saw ext4 in other part and asssumed it was that system cause it had "ro" after it.
Thank you again. You now introduced me into some new territory. Not just flashing modded roms in recovery mode.
But I will search out one modded rom so I can overclock some.

[ROOT] Disable Automatic Update (OTA) New Kindles

This Method disable ota services.
steps:
-Decompress the attached file
-Execute the following commands:
<important>Please look the screen for superuser permission grant.
Code:
adb push disable_ota_for_kindle.sh /data/local/tmp/
adb shell "su -c 'chmod 777 /data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "su -c '/data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "rm /data/local/tmp/disable_ota_for_kindle.sh"
Tested in a Kindle Fire 2 (10.2.3_user_2313820

julionadal said:
This Method disable ota services.
steps:
-Decompress the attached file
-Execute the following commands:
<important>Please look the screen for superuser permission grant.
Code:
adb push disable_ota_for_kindle.sh /data/local/tmp/
adb shell "su -c 'chmod 777 /data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "su -c '/data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "rm /data/local/tmp/disable_ota_for_kindle.sh"
Tested in a Kindle Fire 2 (10.2.3_user_2313820
Click to expand...
Click to collapse
Guessing this can only be confirmed at the time of the next update for me. Currently running 7.2.2 on KFHD.
Will download and give it a go.
Thanks.

Droidwall is a good solution for this too. You can block all Apps for using the Internet connection to call "home"

This script looks to disable all OTA services. Would that not included whispersync, the personal documents service etc? it is possible that blocking all of these services may have undesired consequences to folks who value those services. That said, thanks for developing this script.

Can you provide more details on how to disable OTAs using Droidwall? I downloaded the application but I am not sure which applications I need to block or how to configure.
Sent from my KFTT using xda premium

Should I disable the system app in the center of the screenshot? Will it lock up the device if I do so?
Sent from my KFTT using xda premium

ameswilliam said:
Should I disable the system app in the center of the screenshot? Will it lock up the device if I do so?
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
I installed DroidWall and blacklist all amazon apps, but it still update to 7.2.2 version. I doubt DroidWall can off OTA update

Did you blacklist the 10000. System file seen in the attachment?
Sent from my SPH-L710 using xda premium

Ok, so I used the OP's .SH file, and then read a bit further on this thread and realized his code would disable whispersync too.
Is there any way to reverse his code? I tried to go into his code and change the word "disable" to "enable" but the file would not execute anymore. I have no idea why. I did not change the file name, but ADB keeps telling me "no such file or directory"
Can anyone please help? I'm using Fire HD 8.9 ver. 8.1.3
After i reverse the code, I will just use droidwall
Thanks for your help.

pullmyfinger123 said:
Ok, so I used the OP's .SH file, and then read a bit further on this thread and realized his code would disable whispersync too.
Is there any way to reverse his code? I tried to go into his code and change the word "disable" to "enable" but the file would not execute anymore. I have no idea why. I did not change the file name, but ADB keeps telling me "no such file or directory"
Can anyone please help? I'm using Fire HD 8.9 ver. 8.1.3
After i reverse the code, I will just use droidwall
Thanks for your help.
Click to expand...
Click to collapse
Try running each command with ADB.
I'm not familiar with the disable 'pm' command but know that services can be enabled/disabled via titanium backup. Dont know if this is the same function but you could install it and give it a go.

bryanchapman9999 said:
Try running each command with ADB.
I'm not familiar with the disable 'pm' command but know that services can be enabled/disabled via titanium backup. Dont know if this is the same function but you could install it and give it a go.
Click to expand...
Click to collapse
Yea I dont see any service that's already frozen using Titanium Backup. Can anyone else who knows what this guy's code did help me reverse it? Thanks.
This is his code:
#!/system/bin/sh
pm disable "com.amazon.dcp/.ota.OTAUpdateMessageHandler"
pm disable "com.amazon.dcp/.ota.InventoryUploadService"
pm disable "com.amazon.dcp/.ota.UpdatesLookupService"
pm disable "com.amazon.dcp/.ota.OTAService"
pm disable "com.amazon.dcp/.ota.AppStateMonitorService"
pm disable "com.amazon.dcp/.ota.CheckForOTAUpdatesService"
pm disable "com.amazon.dcp/.ota.ViewUpdateActivity"
pm disable "com.amazon.dcp/.ota.OTAStatusActivity"
pm disable "com.amazon.dcp/.ota.ResetOTAMessageHandler"
pm disable "com.amazon.dcp/.ota.InventoryUploadService$InventoryUploadReceiver"
pm disable "com.amazon.dcp/.ota.UpdatesLookupService$MountStatusChangedReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTAWakeupReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTADedupeReceiver"
pm disable "com.amazon.dcp/.ota.OTAService$OTAInstallNowReceiver"

Disable OTA Updates - Kindle Fire 7" HD
Very well thought out script.
On my Kindle Fire 7" HD all I did was moved /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
So far no updates, still on 7.2.2

Thanks!
thanks Bro for sharing.just wanted to feedback after doing these procedures.my kindle fire HD 7" is not updating anymore.i give it two thumbsup!now i still have the same build 7.2.2 for almost more than a month even if Amazon has the newest build 7.2.3 thanks alot.it really helps

Thanks for the script. Looks like it worked ok for me...Just wondering about the whisper sync deal? Does it still work"

Whisper Sync Disabled
ninjabeaver said:
Thanks for the script. Looks like it worked ok for me...Just wondering about the whisper sync deal? Does it still work"
Click to expand...
Click to collapse
ninjabeaver,
This script does disable Whisper Sync which is why we had our developers redesign a scipt to remove the OTA Services
only. Here is the less aggressive version:
http://forum.xda-developers.com/showthread.php?t=2086450
when we developed the attached script we were very careful to only effect OTA and no other services. We also wrote
an enable script for the people who need to send back there Kindles for repair.

Right on thanks..I hadn't seen that thread before.
Sent from my KFTT using Tapatalk HD

prokennexusa said:
Very well thought out script.
On my Kindle Fire 7" HD all I did was moved /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
So far no updates, still on 7.2.2
Click to expand...
Click to collapse
Hows it going, did you just move otacerts.zip and not block it tru droidwall?

prokennexusa said:
ninjabeaver,
This script does disable Whisper Sync which is why we had our developers redesign a scipt to remove the OTA Services
only. Here is the less aggressive version:
http://forum.xda-developers.com/showthread.php?t=2086450
when we developed the attached script we were very careful to only effect OTA and no other services. We also wrote
an enable script for the people who need to send back there Kindles for repair.
Click to expand...
Click to collapse
If I had used this script on my KF2 but now have installed TWRP and installed new ROM, would I need to run this again ?

Does this script prevent syncing with google play?
I rooted my kindle fire 2 and I ran this script. I uploaded songs onto google play music, but i'm unable to find songs I'd uploaded to the site.
Is it because of this script that google play is unable to sync with my kindle?
Thanks

julionadal said:
This Method disable ota services.
steps:
-Decompress the attached file
-Execute the following commands:
<important>Please look the screen for superuser permission grant.
Code:
adb push disable_ota_for_kindle.sh /data/local/tmp/
adb shell "su -c 'chmod 777 /data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "su -c '/data/local/tmp/disable_ota_for_kindle.sh'"
adb shell "rm /data/local/tmp/disable_ota_for_kindle.sh"
Tested in a Kindle Fire 2 (10.2.3_user_2313820
Click to expand...
Click to collapse
Good afternoon:
Is it possible to provide this service in an APK?
This would allow the user to simply install the APK and then select enable or disable OTA as required?
The User would not have to know anything about ADB and related commands.
If I knew how to create APK apps I would give it a try.
Regards

Fake 'su' using service started through adb shell

Many of the root tools/apps such as screencast, Helium... allow an option to start a background service through adb shell, and then connect to this service to execute commands with elevated permissions.
My idea is around generalizing this experience. There is only one app that starts a background service and acts as a proxy for all other apps (like the SuperSu app).
To make this interaction compatible with all root apps, I was thinking to writing a shell script "su" which redirects all the arguments to the above service.
This will give users with non-rooted devices access to many of the root apps.
But this will require the "su" script to be in the $PATH directory.
[Q] Is there a way to change the $PATH variable from adb shell (without root) so that it is retained system-wide? Any alternatives?

Fire Setup Script (FSS) - Transform your 5.0.1 Fire tablet

Here is a script I have been working on for a while, and have tested on multiple Fire 2015 models. *This is ONLY for the new 2015 Fire tablet, not any Kindle variant. This is for the 5.0.1 firmware. It will work on the 5.0.0 for all functions but the Google Plays Store, 5.0.0 is incompatible with the Google Play Store at this time.
Credits go to alot of the members of this forum for parts of it, including @sd_shadow, @K3Llogs, and @Rivethread to name a few. I'm just wrapping up all the knowledge in a nice package, and cleaning up the code.
DOWNLOAD> https://www.dropbox.com/s/jseeolrqfb1uvdy/FSS.zip?dl=0<DOWNLOAD
This script is meant to be run on the first boot of a Fire, after choosing your language, cancelling the initial setup, and turning on USB debugging. It is a requirement to have the ADB drivers working correctly on your PC before running the script as well. (ADB Drivers available here, require manual device manager loading - http://koush.com/post/universal-adb-driver)
What it does:
-Disable packages to block OTA updates.
-Disable packages to block lock screen adverts
-Remove all of the Amazon bloatware
-Install the FOSS App Store F-Droid
-Install the Google Play Store, and associated framework
The script keeps a log file of all its activities, and reboots your tablet when it is done. It can be run as many times as you want, if you believe a step failed or you made a mistake and need to run it again, go ahead.
When it is done, you will have the Amazon AppStore, Google Play Store, F-Droid App Market, and the Clock app. That's it, 4 things. You can then build it up the way you want to, using whichever store you wish, however you would like. Here are some recommendations to get started:
-Google Camera (The built in camera app tied to Amazon Cloud services, so you'll need a camera app)
-VLC (The built in music and video apps tie into Amazon services as well, so you need a media player app)
-ES File Explorer (The built in picture app is tied to Amazon services, so you need something to look at your pictures)
--I recommend installing OneDrive or DropBox to help manage and backup your pictures as well.
NOTES:
Currently in 5.0.1, you cannot redirect the home button to use a different launcher other than Amazon's Fire Launcher (without a lot of complicated 3rd party overlays). You will be using the Fire Launcher, but with such a blank base to start from, and it's folder ability, I find it quite clean and easy.
Widgets do not work. Even if you get a 3rd party launcher working, they cannot be applied because the core Android framework is not installed. This may not be able to be fixed until the device is rooted.
Performing the process to root your fire, and install a alternative launcher, works great along with this script. It shouldn't matter but I recommend doing this script first, and then the root/launcher fixes second.
ADDITIONAL FEATURES:
If you wish to have one of the Amazon service based apps back, you can simply modify my script and run it again. Go to the 4th section marked [Using Package Manger (pm) to hide Amazon bloatware]. In this section, find the app I chose to hide that you want back, and change the word hide to unhide. Example, if you want the Amazon cloud photos and the Fire camera apps back, find the lines for com.amazon.photos and com.amazon.camera, change hide to unhide, and run the script. Those apps will be back after the reboot.
It works the other way too if you want to hide more of the Amazon stuff you can add more lines to the 4th section. For example, to completely remove the Amazon AppStore and it's framework (gets rid of some of the tabs on home screen), and just use Google/FDroid, add these lines to section 4.
adb shell pm hide com.amazon.platform
adb shell pm hide com.amazon.venezia

Good job putting it all together into one package.

Nice work. I have a new Fire that I haven't opened yet. I am assuming it still comes with 5.0.0. Should I complete the setup and let it update to 5.0.1 before running this script?

natedawg187 said:
Nice work. I have a new Fire that I haven't opened yet. I am assuming it still comes with 5.0.0. Should I complete the setup and let it update to 5.0.1 before running this script?
Click to expand...
Click to collapse
You can do it either way. If you run it on 5.0, you wont get the Play Store but you can use a custom launcher. If you do it on 5.0.1, you will get the Play Store, but have to use Amazon Launcher. Personally, I don't find the Amazon launcher bad once all the bloatware is out of it, and I need the Play store, so I go to 5.0.1 first, then factory reset, then run this.

tufkal said:
You can do it either way. If you run it on 5.0, you wont get the Play Store but you can use a custom launcher. If you do it on 5.0.1, you will get the Play Store, but have to use Amazon Launcher. Personally, I don't find the Amazon launcher bad once all the bloatware is out of it, and I need the Play store, so I go to 5.0.1 first, then factory reset, then run this.
Click to expand...
Click to collapse
Yeah, I would want the Play Store, so I'll go this route. Thanks for the reply.

can you add what each service does here or maybe in the file ?
these are all i could find info on
from another post
k3ll0gs said:
com.amazon.camera. - Camera App
com.amazon.csapp - Help App
com.amazon.legalsettings - Legal Settings App
com.amazon.venezia - Amazon App Store
com.amazon.h2settingsfortablet - Profiles & Family Library App
com.amazon.weather - Weather App
com.goodreads.kindle - Goodreads App
com.android.calendar - Calendar App
com.amazon.kindle.kso - Special Offers setting
com.android.email - Email App
com.amazon.kindle.personal_video - Video App
com.amazon.avod - Video App
com.amazon.contacts - Contacts App
com.amazon.windowshop - Amazon Windowshop
com.amazon.cloud9 - Silk Browser App
com.amazon.ags.app - Amazon Game Circle App
com.amazon.kindle.otter.settings - Amazon Registration Service
Big thanks to Rivethead 23 for the below System OTA update processes
com.amazon.device.software.ota - OTA Updates
com.amazon.settings.systemupdates - OTA Updates
com.amazon.device.software.ota - OTA Updates
Click to expand...
Click to collapse

Mac version
just fyi - I quickly converted the script to run on a Mac. The 'adb' commands are all the same - just modified some echo/prompt commands that didn't work.
I ended up running it twice since 1 of the commands failed the first time:
>> adb shell pm uninstall com.android.vending
>> Failure [DELETE_FAILED_INTERNAL_ERROR]
I also removed the >>lot.txt stuff but you can run it like this to view and save the output:
"run.sh | tee log.txt"
Code:
echo "Starting the Android Debug Bridge (ADB)"
adb kill-server
adb start-server
echo "--------------------------------------------------------------------------------"
echo Communicating with your Fire Tablet from your PC requires 2 things:
echo -The ADB debugging option is enabled on the tablet
echo -The ADB drivers are installed on your machine
echo Make sure you have both of these requirements met before continuing!
echo ...if you need help, see the XDA forums.
echo "--------------------------------------------------------------------------------"
read n
adb wait-for-devices
echo "Using Package Manger (pm) to block OTA updates"
adb shell pm hide com.amazon.otaverifier
adb shell pm hide com.amazon.device.software.ota
adb shell pm hide com.amazon.settings.systemupdates
echo "--------------------------------------------------------------------------------"
echo "Using Package Manger (pm) to block adverts on lock screen"
adb shell pm hide com.amazon.kindle.kso
echo "--------------------------------------------------------------------------------"
echo "Using Package Manger (pm) to hide Amazon bloatware"
adb shell pm hide com.amazon.kindle.personal_music
adb shell pm hide com.amazon.kindle.personal_video
adb shell pm hide com.amazon.photos.importer
adb shell pm hide com.amazon.calculator
adb shell pm hide com.amazon.photos
adb shell pm hide com.amazon.mp3
adb shell pm hide com.amazon.windowshop
adb shell pm hide com.amazon.avod
adb shell pm hide com.amazon.cloud9
adb shell pm hide com.amazon.ags.app
adb shell pm hide com.amazon.csapp
adb shell pm hide com.amazon.weather
adb shell pm hide com.amazon.kindle.otter
adb shell pm hide com.amazon.kindle.otter.oobe
adb shell pm hide com.amazon.kindle
adb shell pm hide com.amazon.whisperlink.core.android
adb shell pm hide com.amazon.zico
adb shell pm hide com.amazon.client.metrics
adb shell pm hide com.amazon.device.backup
adb shell pm hide com.amazon.tahoe
adb shell pm hide com.amazon.webapp
adb shell pm hide com.amazon.camera
adb shell pm hide com.android.calendar
adb shell pm hide com.android.email
adb shell pm hide com.android.contacts
adb shell pm hide com.audible.application.store
adb shell pm hide com.audible.application.kindle
adb shell pm hide com.goodreads.kindle
adb shell pm hide com.nuance.edr.androidservice.service
echo "--------------------------------------------------------------------------------"
echo "Installing additional packages"
adb install FDroid.apk
echo "--------------------------------------------------------------------------------"
echo "Installing Google Play Framework"
adb install com.google.android.gms-6.6.03_\(1681564-036\)-6603036-minAPI9.apk
adb install GoogleLoginService.apk
adb install GoogleServicesFramework.apk
adb shell pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
adb shell pm uninstall com.android.vending
adb install com.android.vending-5.9.12-80391200-minAPI9.apk
echo "--------------------------------------------------------------------------------"
echo Done. Press any key to reboot device.
read n
adb reboot
adb kill-server

Can someone give me some advice on how to do this via Ubuntu?

edjca said:
Can someone give me some advice on how to do this via Ubuntu?
Click to expand...
Click to collapse
use adb to hide apps from system
http://forum.xda-developers.com/showthread.php?p=63216347
Adb Shell Pm Hide as much bloat and amazon as you can
and look at these
[SIZE=+1]Can ADB/Fastboot be used on Linux and Mac?[/SIZE] Yes see
The Easiest Way to Install Android's ADB and Fastboot Tools on Any OS
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) by AshtonTS
[Guide] How To Setup And Use Fastboot by demkantor
Sent from my KFFOWI using Tapatalk

Thank you for putting this all together.
With the 'Black Friday' deal on these (down to £35 in the UK), I'd predict this thread is going to get more interest
Just a quick question though; should it be required to send the Fire7 tablet back, does a factory reset revert all this good stuff?
Thank you

Ubuntu
edjca said:
Can someone give me some advice on how to do this via Ubuntu?
Click to expand...
Click to collapse
Yup, sd_shadow's reply is spot on
OK I didn't use the script.... instead I did it line by line, but got one this afternoon... within minutes of unboxing my fire is happily ticking along without bloat and with Playstore..... damn ,u just gotta love XDA :good:

edjca said:
Can someone give me some advice on how to do this via Ubuntu?
Click to expand...
Click to collapse
If the Fire tablet complains about requiring adb 1.0.32 or higher:
Check your adb version
Code:
adb version
It will likely say Android Debug Bridge version 1.0.31, that seems to be the newest one in the software repository.
You can grab adb 1.0.32 from google:
Code:
wget -O - https://skia.googlesource.com/skia/+archive/cd048d18e0b81338c1a04b9749a00444597df394/platform_tools/android/bin/linux.tar.gz | tar -zxvf - adb
This will place adb 1.0.32 in your home directory. To use it type: ./adb (dot slash adb). You can copy the new adb over old one in /usr/bin but I'd recommend just keeping it in your home directory & just add the ./ (dot slash) to any adb commands.
Code:
./adb version
Android Debug Bridge version 1.0.32

Weird issues here, it won't let me change my time zone because of 'parental controls', and I am unable to change the wallpaper, it just spins and then goes back to the settings screen. Don't know if I'm doing something wrong or if these are parts of the blocked system apps. Everything else seems to work fine.

Edit: I used the script in the link below to change the launcher and that fixed the issue for me.
http://forum.xda-developers.com/amazon-fire/general/alternative-launcher-one-click-script-t3239966
Thanks so much for this, it worked perfectly! I added the lines below to remove the extra tabs from the home screen, but does anyone know how to get rid of the books, audiobooks and newsstand tabs? I keep getting parental controls errors on them and I'd like to just remove them. Thanks!
adb shell pm hide com.amazon.platform
adb shell pm hide com.amazon.venezia

Can anyone give me a general idea of how long this process takes? I've factory reset my kindle to 5.0.1, I've got ADB debug setup on the kindle, got the adb file from the post installed, and I've run the .bat file and hit enter to continue. It's been quite a while now (15 min) and I haven't seen the Kindle reboot.

theusualuser said:
Can anyone give me a general idea of how long this process takes? I've factory reset my kindle to 5.0.1, I've got ADB debug setup on the kindle, got the adb file from the post installed, and I've run the .bat file and hit enter to continue. It's been quite a while now (15 min) and I haven't seen the Kindle reboot.
Click to expand...
Click to collapse
should only take about 2 mins, likely drivers are not correct
Sent from my KFFOWI using Tapatalk

sd_shadow said:
should only take about 2 mins, likely drivers are not correct
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
I'm on Windows 10. What drivers do I need. Don't I just need the universal adb one in the first post? If not, could you please point me in the right direction. Got this as a birthday gift for my daughter and I need to get the Playstore on it asap.

theusualuser said:
I'm on Windows 10. What drivers do I need. Don't I just need the universal adb one in the first post? If not, could you please point me in the right direction. Got this as a birthday gift for my daughter and I need to get the Playstore on it asap.
Click to expand...
Click to collapse
+90% of the time you need to manually select drivers in Device manager
After using the driver installer
Sent from my KFFOWI using Tapatalk
---------- Post added at 10:54 PM ---------- Previous post was at 10:46 PM ----------
manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Fire to pc
Enable USB debugging
(If Fire is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KFFOWI using Tapatalk

this was so easy to do, thankyou for all your hard work

For those looking to replace Amazon launcher:
Search on YouTube: How to Root the Amazon Fire 5th Gen 7in tablet and remove fire launcher (Rootjunky.com)
You need to root your device in order for this to work AND ANOTHER LAUNCHER ALREADY INSTALLED. Basically, you just delete the Fire launcher from /system/priv-apps/. When you reboot your Fire, it will automatically use the other launcher (or ask you to choose, if you have more than one installed).
See video for more info.

Amazon Blocks Users From Blocking Updates

Hello XDA users and Fire TV users, Amazon now blocked the adb shell pm disable-user command permanently. You can no longer block update packages 7.2.7.3/6.2.8.7 and higher. If you just updated your device without applying the system components updates, it should still work so avoid those incremental updates if you can while it lasts.
I'm currently running a Fire TV Stick Lite [TWRP Unlocked] (sheldon) on firmware 7.2.4.2 (PS7242/3515)
The pm disable-user is as follows from adb prompt:
pm disable-user com.amazon.device.software.ota
Security exception: cannot disable a protected package: com.amazon.device.software.ota

Yes mate, newer versions affect custom launchers being permanent too. https://www.aftvnews.com/amazon-blocks-custom-home-launchers-with-latest-fire-tv-software-update/

Skel40 said:
The pm disable-user is as follows from adb prompt:
pm disable-user com.amazon.device.software.ota
Security exception: cannot disable a protected package: com.amazon.device.software.ota
Click to expand...
Click to collapse
The command for unlocked/rooted devices is
pm disable com.amazon.device.software.ota
I guess you know that already, isn't it?
And this would be the command for the locked devices... which is blocked on the latest?
pm disable-user --user 0 com.amazon.device.software.ota

Sus_i said:
The command for unlocked/rooted devices is
pm disable com.amazon.device.software.ota
I guess you know that already, isn't it?
And this would be the command for the locked devices... which is blocked on the latest?
pm disable-user --user 0 com.amazon.device.software.ota
Click to expand...
Click to collapse
Yes which still works with root installed. The command is blocked on latest with system components installed for locked devices. It won't work. Maybe eventually it'll be rolled out as a system update so I wouldn't update if you use the custom launchers and want updates blocked. If they can permanently block launchers they can block update blocker tools from working anymore and it'll continue with newer methods. If anyone has a Fire TV Stick Lite and wants to unlock it. Now would be your best bet before it's patched.

I've enabled adb on rooted FTV2 sloane and launched adb shell (as administrator) but when I run pm disable com.amazon.device.software.ota I get an Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9891, uid=2000, package uid=32011
I was able to run pm clear com.amazon.device.software.ota with success
How do I overcome the permissions denial

hafren said:
I've enabled adb on rooted FTV2 sloane and launched adb shell (as administrator) but when I run pm disable com.amazon.device.software.ota I get an Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9891, uid=2000, package uid=32011
I was able to run pm clear com.amazon.device.software.ota with success
How do I overcome the permissions denial
Click to expand...
Click to collapse
You need to spawn a root shell before running the pm disable cmd. In order to do so, run 'su'.

Rortiz2 said:
run 'su'.
Click to expand...
Click to collapse
When I run su nothing happens, and I cant enter the pm disable command as it seems the adb shell is frozen
Code:
C:\adb>adb shell
[email protected]:/ $ su

Ok so I changed my usb a-a cable I retried su - this time I do get a flashing cursor so entered the commands but still received no feedback from device (its a ftv2 sloane rooted twrp via amonet)
Code:
C:\adb>adb devices -l
List of devices attached
G070GV146247023P device product:full_sloane model:AFTS device:sloane transport_id:1
C:\adb>adb shell
[email protected]:/ $ su
pm disable com.amazon.device.software.ota
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.tv.forcedotaupdater
pm disable com.amazon.tv.forcedotaupdater.v2
exit
exit
pm clear com.amazon.device.software.ota

[email protected]:/ $ su
Should result in
[email protected]:/ #
The '$' turning to a '#' indicates you now have root privileges. It looks like your device is hanging on the su command, with no confirmation the request was granted.

Finnzz said:
[email protected]:/ $ su
Should result in
[email protected]:/ #
The '$' turning to a '#' indicates you now have root privileges. It looks like your device is hanging on the su command, with no confirmation the request was granted.
Click to expand...
Click to collapse
Thanks that's really helpfull to learn. I think I have an issue with magisk so will reinstall from twrp.

OK solved it - magsik had not fully loaded to allow root selection. Now working- Really appreciate learning the '$' turning to a '#' indicates you now have root privileges

hafren said:
I've enabled adb on rooted FTV2 sloane and launched adb shell (as administrator) but when I run pm disable com.amazon.device.software.ota I get an Error: java.lang.SecurityException: Permission Denial: attempt to change component state from pid=9891, uid=2000, package uid=32011
I was able to run pm clear com.amazon.device.software.ota with success
How do I overcome the permissions denial
Click to expand...
Click to collapse
Extremely hard to currently override their malicious updates .
the problem is for most Amazon recent devices , the firmware updates have been slowly
Removing user control away from the device owner , and little by little giving more and more control to Amazon by them hitting your device with malicious updates that change how your device originally worked.

For anyone with a locked device , try an alternative method using no root firewall
or check out teckdoctoruk On YouTube and search his channel for vpn app to
block Amazon updates . either or works , firewall app like no root firewall or
a vpn app that blacklists updates.
Check his page out because he simplifies the process.
Just remember , mileage will vary depending on what malicious updates you already got
From Amazon that changed your device already.
Using a firewall or VPN app to block updates only prevents further Amazon updates from
hitting your box , so it can't remove updates that already changed thing's.