Ok so i followed the instructions to root my D3 twice and i have gotten the proper results, after the second reboot when i adb to my device i am given the root prompt.
That is about it though. I have installed superuser, tried to install jrummy16 busybox installer so i could get titanium working, but neither of the apps can find superuser or get root access.
Any ideas. Sorry for not putting this in the OG Thread but figured that would get real big real quick, thought it might be easier to start a separate thread for issues with the exploit.
need to find and push the su binary to the phone first. Superuser won't work without it.
Alright i got it working.
Anyone know of a good resource for how to kill all of the bloatware?
Is it safe to use titianium to remove the VZ apps, as in uninstall not just freeze
Titanium backup
Sent from my DROID3 using Tapatalk
at this point, i've just been freezing things. I'm waiting till we get a better list of what we can safely remove without breaking things.
Feels good man!
{
"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"
}
lordgodgeneral said:
need to find and push the su binary to the phone first. Superuser won't work without it.
Click to expand...
Click to collapse
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android. (edit: and planning on getting a droid 3 soon)
Also how to delete bloatware and install/use ADB
DoubleYouPee said:
Can anyone add this stuff to the guide? I know most of the stuff is logical for some of you, but I've never rooted a device or used android.
Also how to delete stuff and install/use ADB
Click to expand...
Click to collapse
Here's exactly how I did it... all steps stolen from the thread in the developers forum:
1) Make sure you've installed the android-sdk from Google on your computer. (http://developer.android.com/sdk/index.html)
2) Connect phone to computer. In terminal or a dos prompt, navigate to the directory where you installed the sdk and where adb is located.
(example location)
and type the following:
Code:
adb shell
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
3) Power off and power back on your Droid 3.
4) Drop back to shell/prompt and back to adb location. Type the following commands:
Code:
adb shell
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
5) Restart the phone again. You now have root.
6) Get a copy of su (http://www.megaupload.com/?d=82FH3AGI) and extract it to the same directory as adb on your computer. Type the following:
Code:
adb remount
adb push su /system/bin
adb shell chmod 6755 /system/bin/su
7) Install superuser from the android market.
Done!
Thanks! And then you delete apps with superuser?
I'm having trouble with:
Code:
adb push su /system/bin
It keeps returning:
Code:
cannot stat 'su' : No such file or directory
I have su (from the above link) in the same directory as adb...
*EDIT*
I have root within adb. So I definitely did everything before this right.
Did you extract su from the zip and put in the same directory as adb?
Yep.
10char
similar problem here. adb shell recognizes me as [email protected]_solana so im assuming its rooted..but when i try "adb remount" and press enter it says adb not found. i extracted the su file to my adb directory. Any ideas?
If you get an error like I did (top of 2nd page), try this:
Code:
C:\AndroidSDK\platform-tools\adb push C:\AndroidSDK\platform-tools\su \system\bin\su
That worked for me.
I hope this is helpful to any one that is having a hard time.
I found a one touch root video like 5 mins ago on youtube.
This is not my viedo all credits go to thedriodpeople the ones that made the video.
http://www.youtube.com/watch?v=RpGcuhoUp0k
k finally got the remount to succeed...now its say "chmod 6755: not found" after i enter "adb shell chmod 6755 /system/bin/su"
nevermind, simply retyped the same command and seemed to work on the third try mysteriously. working now
Hosed up my contacts after root and un-install --Help please--
---Solved---
So, I pulled a noob move and uninstalled a number of apps using titanium backup without understanding the repercussions of each. After uninstalling a few at a time, I would reboot my device and everything seemed fine. Little did I know, after uninstalling most, if not all, of the bloat I am unable to click a contact's picture to bring up the submenu and select call or text or whatever.
I didn't write down a list of items that I uninstalled and I should have frozen the apps prior to uninstall. I'm not a complete idiot and stayed away from obvious apps that shouldn't be uninstalled and what I thought was ALL motroblur stuff.
Long story short, I get a "com.motorola.contacts" stopped unexpectedly error(force close prompt) after trying to view a contact. I can look through all of the dialer menus showing contacts and recent calls and whatnot but I can't view a specific contact in detail. The searching I've done seems like there are a number of apps that use com.motorola.contacts and I believe I still have all of them installed but apparently not since there isn't a ton of detail on the latest motoblur that the D3 runs.
Does anyone have an idea of what apps use this process on the D3?
Thanks.
EDIT Javier78 ended up providing a solution to this issue.
http://forum.xda-developers.com/showpost.php?p=16998796&postcount=5
Quick fix and I was on my way again.
I dont think we know what all uses that process.
Sounds like your are going to have to do a factory restore, give it sometime eventually we will have a list of what is safe to remove and what isnt
Related
NOTE: Root is required
When an application fails to install - even side loads - an error message is logged.
First thing to check is the logcat -> it will point to a secure file issue.
for error -18 it is
smdl2tmp1.asec
this file, and all other *.asec files are in the /mnt/secure/ directory.
If this file cannot be removed by the installing application a failure message results.
to manually remove this file you need a terminal application
android terminal emulator works just fine.
{
"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"
}
Step 1.
launch the terminal application of choice
Step 2.
SU
Step 3.
At the # command prompt type
cd /mnt/secure/asec/
Step 4.
type
ls
This will locate the file causing the issue.
Step 5.
type
rm smdl2tmp1.asec
Step 6.
close the terminal application
Step 7.
enjoy the fruits of your labor by installing the application that initially failed.
Thanks, manikin13!
Do you know any other error codes?
joe75 said:
Thanks, manikin13!
Do you know any other error codes?
Click to expand...
Click to collapse
I believe this fix works on most install error codes.
Interesting. Been getting the Error code 18 when attempting to install VitalPlayer. (Vegan Beta1) Folowed your steps to the letter (miss DOS at times) but that folder appears empty. Actually there is no asec folder on either sdcard or sdcard2. Did I miss something? thanks
skeeterpro said:
Interesting. Been getting the Error code 18 when attempting to install VitalPlayer. (Vegan Beta1) Folowed your steps to the letter (miss DOS at times) but that folder appears empty. Actually there is no asec folder on either sdcard or sdcard2. Did I miss something? thanks
Click to expand...
Click to collapse
Are you using a terminal app on the tablet?
this folder does not show up without using a terminal app on the tablet.
once in the terminal app
cd to /mnt/secure/ to see the files. There is no asec folder. The file extension is asec as in *.asec
You bet. Android terminal emulator from the market. At /mnt (via FileManager) there are folders named secure and asec. Both are empty. Notice that when I cd to even mnt/secure I get same message "not found" Verrrrrrrry interesting!
skeeterpro said:
You bet. Android terminal emulator from the market. At /mnt (via FileManager) there are folders named secure and asec. Both are empty. Notice that when I cd to even mnt/secure I get same message "not found" Verrrrrrrry interesting!
Click to expand...
Click to collapse
I saw the samething that nothing shows up in any file manager. only in the terminal ls do the files show up.
you should definitely get a not found for mnt/secure as the actual path is
/mnt/secure/asec/
the initial / is the root of the OS. (linux or unix)
so you are looking for a dir under root called mnt -> /mnt
so if you are having difficulty finding the full path break it down into each step, and do a ls to find the next step
ie
cd /
ls
cd mnt
ls
cd secure
ls
cd asec
ls
etc
hope that helps
Permission denied in Terminal
How do I get terminal permissions?
JackedNY said:
How do I get terminal permissions?
Click to expand...
Click to collapse
Typically typing su at the $ prompt should bring up the superuser prompt (allow / deny) as seen on screen 3. If not you should be able to go into the superuser app, and specifically add terminal.
once you allow the su request the prompt should change to the
# symbol
That did it. Only difference this time was I added the ls step you suggested (ls same as dir in DOS?) Got to where I needed to be and deleted the *.asec. Thanks.
skeeterpro said:
That did it. Only difference this time was I added the ls step you suggested (ls same as dir in DOS?) Got to where I needed to be and deleted the *.asec. Thanks.
Click to expand...
Click to collapse
Exactly
Dos = Dir
Linux, Unix, OsX, Android = ls (small letters)
Awesome little tut
Was having the same issue - but not receiving an error when attempting to install - walked straight through - had to stop in the dir and see the filename to rm but worked like a champ - thanks!
Thanks for this great walk through. I followed it and was able to correct the problem I was having with some installs. I knew intellectually that Android was similar to Linux, but I did not realize how close it is. It is good to see that my Linux knowledge, I know enough to get me into and sometimes out of trouble (Linux Abuser) , can be applied somewhere else.
Thanks again!
linesma said:
Thanks for this great walk through. I followed it and was able to correct the problem I was having with some installs. I knew intellectually that Android was similar to Linux, but I did not realize how close it is. It is good to see that my Linux knowledge, I know enough to get me into and sometimes out of trouble (Linux Abuser) , can be applied somewhere else.
Thanks again!
Click to expand...
Click to collapse
Android is actually very close to OsX in the respect that it is gui first, with the BSD base doing the heavy lifting.
Android is linux in the background with a gui first to allow the ordinary user some familiarity. The reason linux on the phone is not popular and linux on the desktop is not mainstream is because the command line gets equal or higher billing.
Google was smart with Android (basically a linux port with java framework) by promoting it as a gui just like iOS even though to truely see all the potential you need to get to the command line.
Hello my friends,
I can not edit the hosts file.
I think i have to mount the partition but i do not know how to do it.
Could somebody help me please?
Thanks,
Zuka.
Hello,
Ya, you have to mount the partition.
An easy way to do this is to download es Explorer here https://play.google.com/store/apps/details?id=com.estrongs.android.pop
Then open the app, go to the left sidebar, tools, and click root Explorer. Select mount and mount /system.
In images
{
"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"
}
Don't forget to set system in RO back when finished.
When I click on the Root Explorer I get an error:
"Sorry,test failed.This feature can not run on your device"
Is your phone rooted?
Yes it is,i got SuperSU installed and the Root Checker says that my phone is rooted.
Strange... Did you allow root rights to es Explorer?
Yes,I gave ES file Explorer the permission, I got a screenshot:
Sent from my C6903 using XDA Free mobile app
I do not understand why Es Explorer doesn't work with your phone whereas it's rooted as well. But don't let's focusing on this, it's not the main subject. Try ROOT Explorer here https://play.google.com/store/apps/details?id=com.speedsoftware.explorer to get system mounted. If it doesn't work too, we will have to use command line through adb shell.
It's not working either,when I tap mount r/w nothing happens. I can't delete or edit the file.
Sent from my C6903 using XDA Free mobile app
quadrazid said:
It's not working either,when I tap mount r/w nothing happens. I can't delete or edit the file.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
Disable mount space separation on SuperSU, reboot
If still doesn't work, try uninstall ES File Explorer and install it again
Make sure you granted all R/W permission for Es File Explorer
EDIT: if steps above still doesn't work, you need disable Sony RIC first
Yenkazu said:
Disable mount space separation on SuperSU, reboot
If still doesn't work, try uninstall ES File Explorer and install it again
Make sure you granted all R/W permission for Es File Explorer
EDIT: if steps above still doesn't work, you need disable Sony RIC first
Click to expand...
Click to collapse
What is Sony RIC and where can I disable it ?
Did you root woth kinguser and replace it with supersu? If so, you need to disable ric as @Yenkazu say.
Try to install busybox too
odie70 said:
Did you root woth kinguser and replace it with supersu? If so, you need to disable ric as @Yenkazu say.
Try to install busybox too
Click to expand...
Click to collapse
Yes i rooted my phone with KingRoot then I replaced KingUser with SuperSU with the Terminal Emulator.
So yeah,how to disable SonyRIC ?
Edit: I installed BusyBox after I installed SuperSU
Try to connect to flashtool, with usb debugging enabled
frankee207 said:
I do not understand why Es Explorer doesn't work with your phone whereas it's rooted as well. But don't let's focusing on this, it's not the main subject. Try ROOT Explorer here https://play.google.com/store/apps/details?id=com.speedsoftware.explorer to get system mounted. If it doesn't work too, we will have to use command line through adb shell.
Click to expand...
Click to collapse
How to use the command line with the adb shell ?
First, no need to have adb installed on your computer. Type adb devices to make sure your device is recognized by adb. Make sure debugging is enabled.
Type adb shell. When you're at Android shell then type su to become root user. (the command prompt becomes # instead of $)
Chen you're root, type
busybox mount -o remount, rw /[email protected]/system
System file is now RW. When finished type the same command replacing rw by ro.
It should work
frankee207 said:
First, no need to have adb installed on your computer. Type adb devices to make sure your device is recognized by adb. Make sure debugging is enabled.
Type adb shell. When you're at Android shell then type su to become root user. (the command prompt becomes # instead of $)
Chen you're root, type
busybox mount -o remount, rw /[email protected]/system
System file is now RW. When finished type the same command replacing rw by ro.
It should work
Click to expand...
Click to collapse
Where do I type that? In the cmd or in the terminal emulator ?
You can type this in Windows cmd or Linux shell (Linux : make sur adb is installed, to install it, sudo apt-get install adb-android-tools)
If you type it in shell emulator like the very known Android emulator, then skip the command adb devices and adb shell.
(type directly su and busybox mount etc... )
PS: busybox must to be installed to perform this action!
frankee207 said:
You can type this in Windows cmd or Linux shell (Linux : make sur adb is installed, to install it, sudo apt-get install adb-android-tools)
If you type it in shell emulator like the very known Android emulator, then skip the command adb devices and adb shell.
(type directly su and busybox mount etc... )
PS: busybox must to be installed to perform this action!
Click to expand...
Click to collapse
I do not understand what to do.Where to put these commands ?
OK. Let's make easy
Go to play store and download Android Terminal Emulator : https://play.google.com/store/apps/details?id=jackpal.androidterm
Open the app.
type
Code:
su
The command prompt becomes # instead of $ after you have accepted root rights in the popup window.
Then type
Code:
busybox mount -o remount, rw /[email protected]/system
When your modifications in/system are finished, reopen the terminal, become root (type su) and then
Code:
busybox mount -o remount, ro /[email protected]/system
If busybox not installed, intall it first here: https://play.google.com/store/apps/details?id=stericson.busybox
Hoping you'll success
Hi, I've got a problem. Some time ago I installed GPE ROM on ma M7. Then everyting was working properly except ADB. I wasn't able to debugg any app on my phone, cause it was still showing that device is offline. So, I decided to try to factory reset my phone. After that I can't see any folder in SDCARD folder. I used several file managers including "Root Browser" and "ES Eksplorator". Both shows that SDCARD folder is empty. Additionaly, when I plug my phone to PC i see only 4 folders, every of them are empty and I can't copy anything to my phone.
{
"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"
}
What is more interesting, in TWRPs File Manager I can see all my folders and files:
http://i.imgur.com/Y9TSzDN.png
http://i.imgur.com/PrVoPoO.png
http://i.imgur.com/hZBhcN3.png
Do you have any ideas where the problem is? I've factory reseted my phone 2 times and still the same.
Unfortunately I didn't had any idea so I restored to my stock ROM and it solved my problem. Unfortunately, becuse I fallen in love with vanilla Android GPE ROM.
Mefa2 said:
Hi, I've got a problem. Some time ago I installed GPE ROM on ma M7. Then everyting was working properly except ADB. I wasn't able to debugg any app on my phone, cause it was still showing that device is offline. So, I decided to try to factory reset my phone. After that I can't see any folder in SDCARD folder. I used several file managers including "Root Browser" and "ES Eksplorator". Both shows that SDCARD folder is empty. Additionaly, when I plug my phone to PC i see only 4 folders, every of them are empty and I can't copy anything to my phone.
What is more interesting, in TWRPs File Manager I can see all my folders and files:
http://i.imgur.com/Y9TSzDN.png
http://i.imgur.com/PrVoPoO.png
http://i.imgur.com/hZBhcN3.png
Do you have any ideas where the problem is? I've factory reseted my phone 2 times and still the same.
Click to expand...
Click to collapse
When having problem to see your files on /sdcard when on lollipop roms, you can fix this problem normally by using these commands from a rooted rom with usb debug enabled:
Code:
adb shell
su
restorecon -FR /data/media/0
exit
Then reboot the phone.
btw /data/media/0 = /sdcard
http://www.linuxcommand.org/man_pages/restorecon8.html
Are you using TWRP ?
Enviado de meu Moto G usando Tapatalk
@xxmarsubxx
Yes, as I said before, I'm using TWRP. I posted images from TWRP File Manager
@alray
Thanks for the reply. Unfortunately, I was facing another problem with adb and I wasn't able to use adb shell command, because adb shows me that phone is offline. I described my problem here:
http://stackoverflow.com/questions/33002856/cant-connect-to-android-device
Mefa2 said:
@xxmarsubxx
Yes, as I said before, I'm using TWRP. I posted images from TWRP File Manager
@alray
Thanks for the reply. Unfortunately, I was facing another problem with adb and I wasn't able to use adb shell command, because adb shows me that phone is offline. I described my problem here:
http://stackoverflow.com/questions/33002856/cant-connect-to-android-device
Click to expand...
Click to collapse
As for your adb offline issues, looks like you already tried everything I could think of. IS your screen unlocked when you try to use adb commands? Anyway you could use adb from twrp terminal so you can at least fix (maybe) your sdcard issue.
alray said:
As for your adb offline issues, looks like you already tried everything I could think of. IS your screen unlocked when you try to use adb commands? Anyway you could use adb from twrp terminal so you can at least fix (maybe) your sdcard issue.
Click to expand...
Click to collapse
Thanks, for the replay
I will try to fix SDCARD issue then, cause for now I need fully working phone.
BTW, it's interesting that I easly get 2.5-3h SOT on GPE ROM, while on stock ROM it's hard for me to get 2h with Energy Saving Mode On.
Ok, I still have problem with my SDCARD. Now, I even can't take a picture, because I get that communicat:
"Unable to save file to SD card due to insufficient file permissions."
I tried to run "restorecon" command on my phone via adb, but I get this error:
Code:
>adb shell
[email protected]:/ $ su
[email protected]:/ # restorecon -FR /data/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat /data/media/0: Permission denied.
When I'm trying to run this command via TWRP, I get error, that there is no -F parametr (or something like this).
I'd like to add, that I was trying to root my phone and when I connect it to my PC, in "WinDroid Universal Android Toolkit v2.5" app I can see that my phone is already rooted, but when I run SuperSU app on my phone, then there is mentioned that my phone isn't rooted and I have to update "SU binary". Then I agree and after that I get info that it wasn't able to update "SU binary".
Does anyone faced problem like this?
EDIT:
Ok, I manually installed SU binaries (I sideloaded the file via TWRP adb) and now I have root access, but I still can't take any pictures. After restorecon command, now I get this:
Code:
[email protected]:/ # restorecon -FR /sdcard/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat /sdcard/media/0: No such file or directory.
Mefa2 said:
Ok, I still have problem with my SDCARD. Now, I even can't take a picture, because I get that communicat:
"Unable to save file to SD card due to insufficient file permissions."
I tried to run "restorecon" command on my phone via adb, but I get this error:
Code:
>adb shell
[email protected]:/ $ su
[email protected]:/ # restorecon -FR /data/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat /data/media/0: Permission denied.
When I'm trying to run this command via TWRP, I get error, that there is no -F parametr (or something like this).
I'd like to add, that I was trying to root my phone and when I connect it to my PC, in "WinDroid Universal Android Toolkit v2.5" app I can see that my phone is already rooted, but when I run SuperSU app on my phone, then there is mentioned that my phone isn't rooted and I have to update "SU binary". Then I agree and after that I get info that it wasn't able to update "SU binary".
Does anyone faced problem like this?
EDIT:
Ok, I manually installed SU binaries (I sideloaded the file via TWRP adb) and now I have root access, but I still can't take any pictures. After restorecon command, now I get this:
Code:
[email protected]:/ # restorecon -FR /[COLOR="Red"]sdcard[/COLOR]/media/0
SELinux: Loaded file_contexts from /file_contexts
SELinux: Could not stat [COLOR="Red"][B]/sdcard/media/0[/B][/COLOR]: No such file or directory.
Click to expand...
Click to collapse
Its not /sdcard/media/0 its /data/media/0
@alray
Thank you so much for restorecon tip and for notice my mistake! What a shame for me that I did such a mistake... Thank you again, it of course helped me, now I can take pictures and also save files in my memory.
Again, thank you and shame on me.
EDIT 09/23/16
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
(this is optional, you wont have any launcher after doing this! backup your old APK!!)
Code:
adb install -r -d com.amazon.firelauncher.apk
... as you can now see this will -r reinstall and -d downgrade the launcher, causing it to crash and never open.
Thanks for your support guys, I love android!
EDIT:
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
I'm new to the whole Android scene, and recently I had acquired an Amazon Fire HD 8. The only complaint about this tablet is the lack of Google Play and the horrible firelauncher. There is currently no root options available for the Fire HD modles 8 & 10, so I have spent the time to develop a temporary workaround.
Please take a quick look at the developmental thread I previously created so we can collaborate to make a more efficient version of this:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
Disclaimer:
If you plan on installing new applications/packages while this script is running you may have a hard time. Installing packages may take 2-10 minutes, or maybe not at all!
If you experience any problems you can undo everything by running the undo script attatched (unix), or by typing "adb shell ps | grep /system/bin/sh", you will see anywhere from 2-10 processes listed. For each type "adb shell kill -9 <pid>", pid would be the process ID, should be the first number you see on each line.
There is a small chance when you press the home button that it will load the regular firelauncher, do not fret, try again and it will go to whichever launcher you previously selected.
Performance may be slightly altered, if it becomes too bad to use try adjusting the script and change the interval at which it loops (set to 20 by default).
This is an alpha experiment, and I am a noob with Android so please bare with me
This is a noobish approach to disabling the firelauncher (com.amazon.firelauncher.apk), please do not judge it, this is also my first time releasing something for Android.
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Automatic Tool (easy, linux, mac only)
Step One:
Download the two script attachments:
remove_default_launcher.sh - disables amazon's firelauncher
re-endable_firelauncher(undo).sh - reverts the process, if you have any issues
Step Two:
Run the following commands to make the scripts executable:
Code:
chmod +x remove_default_launcher.sh
chmod +x re-endable_firelauncher(undo).sh
Run the tool to remove amazon's nasty launcher!
Code:
./remove_default_launcher.sh
Step Three:
The script should automatically do everything, when it's done, check your Fire. Keep pressing the home button and switching between applications until you get the "Change default launcher" dialogue, make sure you have an alternative launcher installed beforehand or else you won't have a launcher! When it's all working how it should be go to step four!
Step Four:
Simply exit out of your terminal window, do not type anything, just exit ADB. The script will continue running!
This is what a successful window looks like, whenever you have confirmed it is working, close out of the ADB window and end that process.
{
"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"
}
Manually (harder, windows)
Step One:
Open up a new ADB shell window and type
Code:
adb shell
Step Two:
Once you are in the shell window, simply copy and paste this line of code and press return. It is just a simple bash script that loops the command "install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"" which will reinstall the firelauncher repeatedly, which temporary uninstalls it.
Code:
#!/system/bin/sh
nohup
while :
do
kill $!
sleep 1 & pm install -r -d "/system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk" & sleep 20; kill $!
kill $!
done &
exit
#press enter now
After pressing enter, you can watch it go to work, or you can close out of the adb window and unplug your device, it will continue to run until you kill the shell processes or reboot the device. Make sure you have an alternative launcher already installed so it can easily be set as default. EDIT: Reboot may not reset it, which is cool but could be annoying. To turn off this wonderful feature open up adb shell and use "ls | grep shell" and kill using "kill <pid>" all releated processes to /bin/shell or whatever. It may take up to a minute to reset.
If you have any issues at all please comment and I will send you a private message with detailed instructions catered to your specific issue!
If you are a dev, take a look at my unix auto-install script, it may help you figure it out yourself as well. I need someone who understands batch to help me write a windows version .
I literally spent about 45 minutes working on this noobish approach, so if you find bugs or want to modify the script, simply post in the comments your version and why you think it is more efficient. If you want to help make a dedicated and more efficient approach to this, check out the development thread here (there are alternative methods here too):
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
This appears to be a very stable system actually, I recommend everyone does this to the Fire HD tablets!
I hope this helps someone, if this helps you please give me a thanks so I know it
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Pond-life said:
Confused as to why you'd post this here after using the correct forum section for the HD8 and 10 already.
Click to expand...
Click to collapse
I was not sure whether it was the correct forum actually, it is stable enough to use for all versions of Fire now, so I posted for users who do not want to root their device, but hate the launcher. If you think it is in the wrong place I will remove it promptly. I actually did post this in the wrong spot.. It is in development instead... At least there will not be any flaming here
I have also noticed 6x more downloads in 1/5 of the time this thread has been posted compared to the other.
I have updated with a new method that is much better, the only negative to this new method is when you hit the home button, for a brief moment you see the firelauncher. Performance, speed, and bugs are perfect.
Just paste this code in adb shell, I'm working on setting up nohup to work with it, when you close adb it will stop working.. Going to bed for now though.
Code:
#!/bin/bash
am monitor | while read -r line; do
if [[ $line == *"firelauncher"* ]]
then
am start [B]com.newlauncher.launcher[/B]
fi
done
Good job on this!
glitch3yf0x said:
Good job on this!
Click to expand...
Click to collapse
No problem, hopefully I will find some more time to work on this in the future .
I am glad you like it.
nyln said:
If you are using a unix operating system (like Linux or Mac), I have compiled a script that does the work for you! Windows users will have to wait and do it manually since I am unfamilar with batch (would someone like to help with this?)
Click to expand...
Click to collapse
If you're still in need, I'd be happy to help port it to windows!
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
This is one of the best thread for Fire OS world! Can't wait for you to perfect this.
P.S: Plz, someone here port it to Windows.
Does it work on Fire 5.3.1 ?
Please message me if you want me to keep working on this. After the root I stopped.
working great. And how to restore in the laucher back?
I am in Win10
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
ttcontributor said:
update: After reboot, it turns back to original FireOS launcher. Is there a way to make it auto applied?
Click to expand...
Click to collapse
I will do some work on it. I am not an android developer, so maybe i will write a python application.
nyln said:
I will do some work on it. I am not an android developer, so maybe i will write a python application.
Click to expand...
Click to collapse
It's great to hear you still have your hands on this
nerakkaren said:
as for me,on windows, worked simply:
adb shell
pm hide com.amazon.firelauncher
to enable the fire launcher again,
adb shell
pm unhide com.amazon.firelauncher
Click to expand...
Click to collapse
If I am not mistaken, this will only bennefit those who have a rooted device. Fire 7 and HD 8 got updated via OTA removing my root. I am now working on a better way right now .
Please PM or Thank me if you're interested in this, it'll come out faster if I know people are waiting
I finally found a permanent solution to how to change fire launcher on the Amazon Fire without root. It works on any version (FireOS 5.3.1) on any tablet variant (7, HD 8, HD 10 etc...).
You can read the detailed tutorial at http://forum.xda-developers.com/ama...-remove-default-launcher-amazon-fire-t3288310 but basically you run one command, must be done after reboot currently via adb shell:
Noval Launcher on Amazon Fire no-root:
Code:
nohup logcat -c; logcat | grep --line-buffered 'flg=0x10200000 cmp=com.amazon.firelauncher/.Launcher' | while read line; do am start com.teslacoilsw.launcher/.NovaLauncher; done &
That's it. Once you paste that into your adb shell you're done; you now have a default launcher programmatically set via ADB.
Optionally, you can install the modded firelauncher.apk so you can finally delete it without root .
Thanks for your support guys, I love android!
Here is a teaser of my application:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
ahac85 said:
[email protected]:/ $ adb install -r -d com.amazon.firelauncher.apk
/system/bin/sh: adb: not found
im getting this error, so i still c the default launcher for a couple of seconds before it goes to nova launcher
Click to expand...
Click to collapse
You are already inside adb shell, type exit then type it again silly
How can i copy TitaniumBackup folder to PC?
With my others Galaxy phones i always could copy through MTP but with my G998B/DS i can't.
I've used all the methods i found on the internet, such as:
Copy through MTP;
Compress TitaniumBackup's folder into a .zip file;
And through the ADB command
Code:
adb pull "/sdcard/TitaniumBackup" "D:\BACKUP"
Through MTP and compressing the folder i only get the .PROPERTIES files and through ADB i get this error message:
adb: error: failed to copy '/sdcard/TitaniumBackup/com.google.android.apps.photos-20210403-172138.tar.gz' to 'D:\BACKUP\TitaniumBackup\com.google.android.apps.photos-20210403-172138.tar.gz': remote open failed: Permission denied
If anyone can help me I would appreciate it.
SOLUTION: I entered in TWRP and i've been able to copy the folder.
anyone know how to resolve this? i don't have TWRP so i can't use that work around.
fizmixa said:
anyone know how to resolve this? i don't have TWRP so i can't use that work around.
Click to expand...
Click to collapse
Do you get the same error as below?
MasterHack10 said:
adb: error: failed to copy '/sdcard/TitaniumBackup/com.google.android.apps.photos-20210403-172138.tar.gz' to 'D:\BACKUP\TitaniumBackup\com.google.android.apps.photos-20210403-172138.tar.gz': remote open failed: Permission denied
Click to expand...
Click to collapse
Maybe the "Permission denied" error is triggered by windows itself since you try to copy into the root of drive D. Maybe running your terminal (e.g. PowerShell) as admin will resolve your issue.
Else, @fizmixa , you could still manually boot (but not flash) twrp using fastboot, if your device isn't a Samsung device (I don't know if you can achieve this with Samsung).
Same here...Still couldn't find a solution.
I had the same problem. Looks like it's permission related. I fixed the problem by booting into TWRP -> Advanced -> File Manager, navigating to /sdcard/TitaniumBackup, clicking the blue folder with the tick and then selecting the chmod755 option.
@fizmixa, try and download Terminal Emulator for Android from the Play store and run:
Code:
chmod 755 /sdcard/TitaniumBackup/
It is about owner permission. Tar.gz files has a different owner from .properties. I don't have TWRP recovery because I use Android Emulator. How can I solve this problem?
Same issue here. Is this an Android 11 issue?
I'm struggling with the same issue .. No TWRP with me yet. So any clue how to get these files out of the device ?
JazonX said:
I'm struggling with the same issue .. No TWRP with me yet. So any clue how to get these files out of the device ?
Click to expand...
Click to collapse
They're protected due to security changes in newer versions of Android. I had the same issue on my last device, unable to pull /sdcard/android or /sdcard/TitaniumBackup using ADB for example.
You can try the SmartSwitch Windows app to take a backup of your phone?
Just a word of warning, I used SmartSwitch yesterday and although the backup was successful the call log backup zip was corrupt and couldn't be restored.
skymera said:
They're protected due to security changes in newer versions of Android. I had the same issue on my last device, unable to pull /sdcard/android or /sdcard/TitaniumBackup using ADB for example.
You can try the SmartSwitch Windows app to take a backup of your phone?
Just a word of warning, I used SmartSwitch yesterday and although the backup was successful the call log backup zip was corrupt and couldn't be restored.
Click to expand...
Click to collapse
Hey, I just managed to sort it out.
Go to Titanium Backup, Preferences, Backup location - and click the below selected option;
Select the external backup storage option, and allow access to it.
It was weird how this caused the PC copying / internal copying to fail .. This sorted the problem for good.
{
"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"
}
JazonX said:
Hey, I just managed to sort it out.
Go to Titanium Backup, Preferences, Backup location - and click the below selected option;
Select the external backup storage option, and allow access to it.
It was weird how this caused the PC copying / internal copying to fail .. This sorted the problem for good.
Click to expand...
Click to collapse
I'm not rooting my S21U but this is good to know for the future, tks.
I'm also having this problem with Android 11 on Pixel 5a, adb: error: failed to copy ...: remote open failed: Permission denied
There isn't a TWRP for this device yet so I can't try that solution. I tried JazonX's idea but it hasn't helped. The problem seems to be that the tar.gz files are owned by media_rw user instead of u0_a252 like the other files. I tried using 'adb shell', "su -" and then "chmod 755 /sdcard/TitaniumBackup/" but it doesn't actually change any of the permissions. Also tried commands such as "chown u0_a252 *.tar.gz" but it doesn't actually change anything. I tried to write to TB support too but no response yet. Any other ideas?
Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!
scarlion said:
Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!
Click to expand...
Click to collapse
Wow! It worked for me! Thanks very much
scarlion said:
Aha! I found a solution! use "adb shell" then "su -" then navigate to "cd /data/media/0/TitaniumBackup". Now commands like "chown u0_a252 *" actually work and I was able to get full backup of /sdcard/TitaniumBackup with "adb pull". Crazy Android file system!
Click to expand...
Click to collapse
Did you do this via windows command prompt or within a terminal program on the android device?
As I can't seem to get it to work on Windows CMD
Code:
C:\platform-tools>adb shell
redfin:/ $ su -
redfin:/ # cd /storage/emulated/0/TitaniumBackup
1|redfin:/storage/emulated/0/TitaniumBackup # chown u0_a252 *
redfin:/storage/emulated/0/TitaniumBackup # adb pull "/storage/emulated/0/TitaniumBackup" "D:\Temp"
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup # adb pull /storage/emulated/0/TitaniumBackup
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup #
pennywaltz said:
Code:
redfin:/storage/emulated/0/TitaniumBackup # adb pull "/storage/emulated/0/TitaniumBackup" "D:\Temp"
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup # adb pull /storage/emulated/0/TitaniumBackup
: adb: inaccessible or not found
127|redfin:/storage/emulated/0/TitaniumBackup #
Click to expand...
Click to collapse
I think you have to exit the "adb shell" for further adb commands to work, as "adb" is in your C:\platform-tools directory
scarlion said:
I think you have to exit the "adb shell" for further adb commands to work, as "adb" is in your C:\platform-tools directory
Click to expand...
Click to collapse
I'm having the same problem on my Pixel 5 ("redfin"). It has nothing to do with adb. Without adb running at all, I can go to a terminal emulator on the device and run the following commands ...
Code:
redfin:/ $ su -
redfin:/ # cd /sdcard/TitaniumBackup
redfin:/sdcard/TitaniumBackup # chown u0_a362 *
No error is reported. However, after doing this, all the files previously owned by rw_media are still owned by rw_media. In other words, for those files, the chown command is effectively a no-op, even after an su to root.
Google strikes again with its "We think we're much smarter than you, and we're going to 'protect' you from yourself, whether you like it or not!" attitude.
HippoMan said:
Google strikes again with its "We think we're much smarter than you, and we're going to 'protect' you from yourself, whether you like it or not!" attitude.
Click to expand...
Click to collapse
I know right, it's pretty annoying... but even with root, I think you have to specifically modify the data from the /data/media/0 directory instead, i.e.:
redfin:/ $ su -
redfin:/ # cd /data/media/0/TitaniumBackup
redfin:/data/media/0/TitaniumBackup # chown u0_a362 *
Does that work?
scarlion said:
I know right, it's pretty annoying... but even with root, I think you have to specifically modify the data from the /data/media/0 directory instead, i.e.:
redfin:/ $ su -
redfin:/ # cd /data/media/0/TitaniumBackup
redfin:/data/media/0/TitaniumBackup # chown u0_a362 *
Does that work?
Click to expand...
Click to collapse
Yep, that worked for me! Thanks! It seems they have put some stupid userland file system which mirrors files from /data:
/dev/fuse on /storage/emulated type fuse (rw,lazytime,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other)