LOOKS LIKE THIS ONLY WORKS FOR 5.6.1.0 AND UP BUT YOU CAN ALWAYS TRY IF YOU WANT, THIS *SHOULD* NOT DAMAGE YOUR DEVICE
THIS DOES NOT WORK ON NEW 2018 MODELS.
You can use this method in any tools or scripts, but you must add a link to this thread in these threads, videos, etc.
Hi!
This is a guide on how to disable system apps on 7th Generation or older Fire tablets.
This guide *should* work in theory for every Fire tablet, in every version, but I only tried this is my HD 8, version 5.6.1.0.
(Also the "pm hide" command does not just hide the app, it is almost completely identical to "pm disable", only the system interprets it differently. So, yes, you will notice a good increase in performance after you do this!)
Please hit thanks if this helped, it is easier than commenting thanks...
--You'll require a PC with ADB installed.--
--------
MANUAL METHOD:
1.) I attached an APK for "Amazon Facebook Share" below,(edit: it is not displaying properly in this thread, see post #1) install it with ADB, or copy it into the device and install it manually.
2.) Reboot.
3.) Now open the command prompt, and type:
Code:
adb shell
run-as com.amazon.unifiedsharefacebook
id
4.) If the "id" command output *does not* start with "uid=2000" then you are good to go! Just run "pm hide" on every system app package you want to disable, you can find some lists in this forums. (If it does not, PM me your output or reply in this thread with the output)
5.) So, it looks like that this sheet works well.
SEMI-AUTOMATIC METHOD:
SORRY, CURRENTLY THE SEMI AUTO METHOD IS BROKEN, I'LL TRY TO FIX IT.
1.) Download the attached .ZIP and extract it, see post #30.
2.) Run the batch file, (it will reboot your device).
3.) Now continue the step #3 from above.
--------
If you try to access a disabled app, it will show an annoying warning, (like accessing "System Updates" in Device Options after disabling OTA)
Code:
The requested action is not permitted. Check Parental Controls settings and retry.
IMPORTANT- If you disable com.amazon.firelauncher, everything will work almost perfectly, but you will see the warning message I mentioned above every time you press home.
--------
Good Luck with disabling, and don't disable critical parts!
Here is the APK.
Sadly didnt work, have a Fire HD 8, 5.6.0.1
Installed it via adb install -r -d with the following error.
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Works !
works on 5.6.2.0
removed the apps from the bloatware spreadsheet
Not yet rebooted my fire hd8
Need help with my fire HD 8 running fire OS 5.6.2.0
Supersonic27543 said:
THIS IS STILL UNCONFIRMED, AND MAY OR MAY NOT WORK. BUT IT JUST WORKED FOR MY DEVICE.
Hi, I'll be unable to be in this forums for some time, maybe for a couple of months, (I will still check the forums when I can) so I'm going to leave a gift for everyone!
This guide *should* work in theory for every Fire tablet, in every version, but I only tried this is my HD 8, versions 5.6.0.1 & 5.6.1.0.
(Also the "pm hide" command does not just hide the app, it is almost completely identical to "pm disable", only the system interprets it differently. So, yes, you will notice a good increase in performance after you do this!)
-You'll require a PC with ADB installed.
1.) I attached an APK for "Amazon Facebook Share" below,(edit: it is not displaying properly in this thread, see post #1) install it with ADB, or copy it into the device and install it manually.
2.) Reboot.
3.) Now open the command prompt, and type:
Code:
adb shell
run-as com.amazon.unifiedsharefacebook
id
4.) If the "id" command output *does not* start with "uid=2000" then you are good to go! Just run "pm hide" on every system app package you want to disable, you can find some lists in this forums. (If it does not, PM me your output or reply in this thread with the output)
If you try to access a disabled app, it will show an annoying warning, (like accessing "System Updates" in Device Options after disabling OTA)
Code:
The requested action is not permitted. Check Parental Controls settings and retry.
IMPORTANT- If you disable com.amazon.firelauncher, everything will work almost perfectly, but you will see the warning message I mentioned above every time you press home.
Good Luck with disabling, and don't disable critical parts!
Click to expand...
Click to collapse
hey, I am trying to get rid of some apps on the fire HD 8 and what this post said was not working and I was hoping you could help me out...
1. when I put the apk in the storage and try to install it on my Fire it comes back and says "app not installed" but I tried to push it with ADB and still no luck...so I try my luck and try all the commands anyway and here is the script I got back:
C:\Tools\platform-tools_r28.0.0-windows\platform-tools>adb shell
[email protected]:/ $ run-as com.amazon.unifiedsharefacebook
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
1|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $
anything would help.
Thanks
Rangerclass said:
hey, I am trying to get rid of some apps on the fire HD 8 and what this post said was not working and I was hoping you could help me out...
1. when I put the apk in the storage and try to install it on my Fire it comes back and says "app not installed" but I tried to push it with ADB and still no luck...so I try my luck and try all the commands anyway and here is the script I got back:
C:\Tools\platform-tools_r28.0.0-windows\platform-tools>adb shell
[email protected]:/ $ run-as com.amazon.unifiedsharefacebook
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
1|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $
anything would help.
Thanks
Click to expand...
Click to collapse
i've copied the apk in /sdcard and then pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
t0x1cSH said:
i've copied the apk in /sdcard and then pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
Click to expand...
Click to collapse
I just got the tablet on Prime day and have not yet got the sdcard...
is there anyway i could do it without and what Tablet do you have?
mine is a Fire HD 8 7th gen running OS 5.6.2.0
thanks for the advice and hope we can figure something out.
Rangerclass said:
I just got the tablet on Prime day and have not yet got the sdcard...
is there anyway i could do it without and what Tablet do you have?
mine is a Fire HD 8 7th gen running OS 5.6.2.0
thanks for the advice and hope we can figure something out.
Click to expand...
Click to collapse
simply copy the apk on the device via usb cable in the root directory
open adb shell on your pc
run pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
then run run-as com.amazon.unifiedsharefacebook
and then check your id
t0x1cSH said:
simply copy the apk on the device via usb cable in the root directory
open adb shell on your pc
run pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
then run run-as com.amazon.unifiedsharefacebook
and then check your id
Click to expand...
Click to collapse
Thanks you so much.
I was doing /local not /sdcard because I thought that local would be it because I did not have a SD card yet.
the ID has now changed and I should be able to complete the first post.
Thank you so much for your time and help.
t0x1cSH said:
simply copy the apk on the device via usb cable in the root directory
open adb shell on your pc
run pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
then run run-as com.amazon.unifiedsharefacebook
and then check your id
Click to expand...
Click to collapse
I still get the [INSTALL_FAILED_MISSING_SHARED_LIBRARY] error
edt: not sure if I want to update if sooner or later an exploit might be found..? what do you guys think
Worked for HD7 (7th Edition) with OS 5.6.1.0
Now I can disable ("hide") further OTA updates.
Thank you very much.
Edit: I bought my HD7 last year, which came with O.S. 5.4.0.0. However, after "pm uninstall" Special Offer and a few Amazon Apps, I forgot to "pm uninstall" OTA. Consequently, it continued to get OTA updates till now.
Dan_firehd said:
Worked on HD7 (7th Edition) with OS 5.6.1.0
Now I can disable ("hide") further OTA updates.
Thank you very much.
Click to expand...
Click to collapse
It worked for HD 7? Nice :good:
vierlex said:
I still get the [INSTALL_FAILED_MISSING_SHARED_LIBRARY] error
edt: not sure if I want to update if sooner or later an exploit might be found..? what do you guys think
Click to expand...
Click to collapse
That error shows when the device does not support the APK. Is it a HD 8 2016? Also, do not update if you don't have to, 5.6.1.0 is considerably reinforced against exploits than previous versions. But if you really want to disable, it may be worth a try.
This is awesome! This worked on my 7th gen HD 8.
I followed the list of apps in this thread for what to hide (plus a little more): https://forum.xda-developers.com/hd8-hd10/general/debloat-fire-hd-2017-kindle-prime-music-t3729209
But I think I hid something important as I have a red line across the bottom of my screen now....
I know you said we need a PC with adb installed, but would this not also work with a terminal emulator?
Sent from my SAMSUNG-SM-G935A using Tapatalk
I get INSTALL_FAILED_INVALID_URI when trying to install on a Fire HD 8 2017 with 5.6.2 is it blocked in 5.6.2
I am so hoping this works for me! When I have the time to give it a try I will let you know.
getochkn said:
I get INSTALL_FAILED_INVALID_URI when trying to install on a Fire HD 8 2017 with 5.6.2 is it blocked in 5.6.2
Click to expand...
Click to collapse
I tried to link to the path /sdcard/Download/com.blabla.apk and it installed no problem.
I still cant properly hide the apps tho. All apps I try get hidden from the launcher but still exist and are active according to the settings/apps.
However, the apps cannot be run by any means...so this may work afterall.
Rollercoaster this one.
Edit: Vesion 5.6.2.0 install date: 11.07.2018
I'll post an update on the OTA check, if no automatic check is done!
You have to reinstall the apk every time you reboot, before you try the "run-as" command:
Code:
adb install -r -d .\com.amazon.unifiedsharefacebook.apk
I didn't have to rename the apk.
Yes, the apps still show up in the Settings and don't show as disabled in there, but the apps don't show in the launcher and can't be run, which is really what I'm looking for.
Badass post, Supersonic27543. You keep killin it!
Related
This root was rendered unusable at this time due to AT&T disabling the Ready2Go app installation feature. Working on a work around now.
Original content:
http://www.androidpolice.com/2012/0...the-att-htc-one-x-on-version-1-85-or-earlier/
Hope you get your One X soon dude!
Confirmation number: 8PH11891CA483914J
In! Thanks Justin!
Billy
Damn, thanks a lot!
jcase said:
Now comes the timing critical part, you have to use ATT Ready2Go to Download "AT&T Mark the Spot", and interrupt the install process right after the download has finished. Easiest way is to reboot the device, but we have found other ways to do it.
Click to expand...
Click to collapse
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
jcase said:
You need to reboot right after the download is done. I haven't had a chance to do this in person, I just found it in the firmware and asked others to test for confirmation. Hopefully someone can chime in and tell us what visual indicators show when to do the reboot.
Some testers got it first try, some took 3-4 tries.
Click to expand...
Click to collapse
Hah, well now I just feel dumb as I am on try 10 or so. I must not be able to hit the timing right at all. I'll keep at it, as I am constant as the northern star.
Don't feel dumb, it is very timing critical, with few real indicators of when to pull it off.
Maybe xfinrodx or designgears can chime in on this one
noobsquared said:
I'm with you on this one. I've been trying this for last hour but to no avail. The minute it says in status bar that it's installing, I tried command. I tried when I press finish on phone and LTE signals go up and down and even tried as soon as I was done with att site but can't get it to work. I've restarted 20 times and this startup sounds I think is now annoying other people in the office
Click to expand...
Click to collapse
Turn your ringer off, it will silence the startup sound. At least I can help with that!
id10terrordfw said:
Turn your ringer off, it will silence the startup sound. At least I can help with that!
Click to expand...
Click to collapse
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
I have been deleting the file from data/install
adb shell
cd data/install
rm com.att.android.markthespot.apk
exit
then repeat the process...i'm in double digits on attempts...going to have to walk away from it for a bit.
going on 10x for me and still nothing. Any suggestions?
id10terrordfw said:
OK, so when exactly do we reboot? There is no download status bar or whatnot, and I have rebooted right when it says install started to no avail. Do we have to do it before that point?
<---Not a noob, just crappy at timing.
Click to expand...
Click to collapse
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
noobsquared said:
Thanks, but everytime I do factory reset...it comes back on?
I might be doing something dumb.
After I get permission denied error, I try to start at the process of tryping:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
but when I do that after uninstalling AT&T Mark the spot, it gives me erorr:
link failed File exists
So I do a factory reset and then try again from scratch.
Is there an easier way to repeat the process?
Edit: I figured it out, just delete the file like this:
Code:
adb shell rm -r /data/install/com.att.android.markthespot.apk
Hope that's the right way of doing it.
Thank you.
Click to expand...
Click to collapse
Um, why are you doing a factory reset?
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
I will give that a shot, and I should have thought of that. Thanks!
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (It is 3801413 bytes as of today). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Good advice, was the first person to test it for me. I confirmed it with 4 users before posting, and all got it eventually.
id10terrordfw said:
I will give that a shot, and I should have thought of that. Thanks!
Click to expand...
Click to collapse
I was the first one I'm aware of who used this exploit a couple weeks ago. I won't claim that the process is clean, but it should work for you if you do it the way I intended the instructions to read... Good luck!
Thanks for all the help but I think this red bull is not working today.
Here is what I did:
First CMD:
Code:
adb shell
cd /data/install
ls -l <- it only gives me the file name..it doesn't tell me the size.
Also, I delete the file and run the first command in second CMD and right after that I see this in ls -l:
[email protected]:/data/install $ ls -l
ls -l
lrwxrwxrwx shell shell 2012-05-25 12:16 com.att.android.markthesp
ot.apk -> /data/local.prop
Second CMD:
Execute:
Code:
adb shell ln -s /data/local.prop /data/install/com.att.android.markthespot.apk
Wait to execute:
Code:
adb reboot
xfinrodx said:
No worries. Here's the way I did it back when I did it:
Open 2 cmd windows
adb devices on both (to make sure daemon is running)
In first shell type adb reboot but do not execute (obviously!)
In second window, cd /data/install
Enter ls -l
Now tell Ready2Go to install.
In that second window SPAM "up arrow - enter" to repeatedly execute ls -l. Observe the .apk file growing in size. When it stops growing it's probably done downloading (I think it was around 5MB but it's been a while). Go back to that first window IMMEDIATELY and hit enter on that adb reboot you typed in. It's a small apk so you need to be fast.
This was my method. Hopefully it works for you!
Click to expand...
Click to collapse
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $4}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
dharani1234 said:
Great Idea !!!.... If you could post the exact size of the file , we can probably try to script it...( I have an idea in mind as mentioned below , but not sure if it works the way I intended in android )
for Ex:
szie=`ls -l /data/install/com.att.android.markthespot.apk | awk '{print $5}'`
while [ "$szie" -lt <size-of-apk> ];do
echo "waiting......"
done
adb reboot
Click to expand...
Click to collapse
If you can get a working script, that was reliable I would love to post it in the OP. To get an idea of the size, you could install the app, and do adb shell ls -l /data/app/<filename>
Root for ZTE z990g aka ZTE Merit
by jcase - [email protected] - http://twitter.com/TeamAndIRC
June 16 2012 - Copyright 2012 CunningLogic
Do Not Distribute or republish without permission. (Sad that this is needed, but people/blogs like to profit off the work of others without credit)
Want to support my work? Donations are always appreciated, but never required:
Paypal: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=LZ62YFU3XCEK8
Amazon Giftcards: [email protected]
Required files:
http://dl.dropbox.com/u/8699733/chainsdd-su.zip
Unzip chaindsdd-su.zip and then get a shell with adb
Code:
adb shell
Set up the dirs, so shell owns them prior to logging. If shell does not own them then we can not control them. If the logs dir already exists, you may have to do a factory reset to remove them. They should not exist unless someone attempted this previously.
Code:
mkdir /data/local/logs
mkdir /data/local/logs/kernel
Open emode's logset activity. First button should be for enabling log set, enable it. Do not exit the activity, but if you do just repeat the below command.
Code:
am start -a android.intent.action.MAIN -n com.zte.emode/.logset
Confirm the log_kernel.txt file exists, if it does not wait a minute and check again.
Code:
ls -l /data/local/logs/kernel/log_kernel.txt
If it exists, delete it and immediately symlink it to /data/local.prop, logset may recreate it, if it does delete and try symlinking again.
Code:
rm /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt
Now we want to wait for /data/local.prop to be created, it may take a minute or two. Keep checking until it exists.
Code:
ls -l /data/local.prop
Now once /data/local.prop exists, go back to the logset activity and disable logset. If you don't disable it, it will slowly eat away at all the disk space, and possibly overwrite the local.prop before you get root. Now lets set qemu=1 then reboot.
Code:
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
Once you have rebooted, remount, install su.
Code:
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Clean up your mess!
Code:
adb shell rm /data/local.prop
adb shell rm -r /data/local/logs
Reboot, install the Superuser app from the market and enjoy
Code:
adb reboot
Might Not Work As Expected
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
bitshifter52 said:
I just tried this procedure from JCase at the RootzWiki dot com site with mixed results. The phone is a ZTE Merit Z990G from Straight Talk.
I went through all the steps and everything performed as expected. When I start start an app that requires superuser permissions, the app reports that the device has not been properly rooted. I have repeated the process as outlined four times, including downloading the SU file, and have the same results. Titanium Plus, Busy Box Pro and Root Check Basic report that the device is not rooted.
However, a couple of the Google apps - music, movies and reader seem to think the phone is rooted. Any ideas or suggestions will be very appreciated.
Click to expand...
Click to collapse
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
jcase said:
Sounds like band permissions on su, try
adb shell ls -l /system/xbin/su
if the permissions come out as "-rwsr-sr-x" then you are rooted, try updating su with the suepruser app, or finding a different copy of su.
If the permissions are different or it says it doesnt exist, then you need to repeat the instructions as you missed one or two
Click to expand...
Click to collapse
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
Click to expand...
Click to collapse
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
bitshifter52 said:
Thank you for the fast response. Here are the permissions for the SU file and based on what you are saying they look good:
C:\SDK>adb shell ls -l /system/xbin/su
-rwsr-sr-x root root 22364 2012-06-17 12:47 su
I have located and downloaded a couple of "su" files from XDA and similar sites and the files are identical. I will continue searching for a different "su" file and see if that makes a difference.
---------- Post added at 06:15 PM ---------- Previous post was at 05:43 PM ----------
I looked around and did not find any "su" files that were different than what I downloaded according to the root process. Just for grins I copied the "su" file from my Noot Tablet which is rooted and tried that file. Sadly, it did not make a difference.
Please let me know if there is any other information I can provide or if you would like me to try something else.
Click to expand...
Click to collapse
It Worked - But Don't Know Why...
jcase said:
What happens when you open the Superuser app (note this is not supersu) and go to settings/options and attempt to update su?
Click to expand...
Click to collapse
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
bitshifter52 said:
I re-installed Superuser and Superuser Elite and now the phone says it's rooted. I've been in IT for over 35 years and it makes me nervous when software "magically" fixes itself. But now that it's working I won't question it and proceed from here. I appreciate your help and your effort.
Cheers
Click to expand...
Click to collapse
Generally you have to run superuser once to get it to work I've found, at least recent builds (or maybe its recent android builds)
Problem.
Hello, i have followed this entirely but at parts it says "Access denied" when im on certain parts when i tryed to check if the Kernel log was there it said "access denied" same with some folders.
root or no root
followed steps, ended up with this...
$ ls -l /system/xbin/su
ls -l /system/xbin/su
-rw-rw-rw- root root 22364 2012-07-15 09:25 su
the superuser app shows all blank under apps and logs, when i try to update it, it says "checking" for a few secs and then nothing... also wondering how to do a factory reset cuz if i didn't screw the phone up yet, i will thx in advance
Has you can see I'm new here. I'm old and retired I would love to root my ZTE Merit 2.3.5 but this is over my head.
I was wondering if there's any accomplished phone rooters in the NC area that would be willing to walk me through this or do this for me
I'd be more than willing to make a donation to make this happen,
custom recovery
I was wondering if someone would make q custom recovery for this phone because the stock recovery is really bad
Not working
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Worked!
omg I've wanted to root my phone. Thank you thank you! I thought I would brick my phone at first.
SIM Carrier unlock a ZTE Merit Z990G Straight Talk
I'm currently a T mobile prepaid customer and received the Merit from a friend of mine for doing some painting. I have looked for a month now and had a few unlock websites fail at attempting to unlock the phone via the IMEI (which the phone does have ). I have attempted to put my tmobile sim in the Merit but there is NO place to enter an unlock code. I really DONT wanna change my service to straight talk and would be willing to pay a decent amount to anyone that is capable of unlocking this phone for use with tmobile. If you think you have what it takes PM me and i will give you the IMEI and we can work out a deal. I challenge ANYONE achieve the impossible and get me the unlock code and a way to input it into the phone.
Cannot get local.prop
I have waited 20 minutes after trying to create the local.prop file and it simply won't create it. Any suggestions?
Can't get SU to upload
Hey I'm new to rooting android. I get to the point of installing SU but windows keeps telling me file not found. Would really like some help in fixing this issue. I have installed SU file to C:\Android\android-sdk\SU. Up to this point everything works fine.
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Any help would be really appreciated.
Thnks
Help getting Started
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Not a Damn thing...
Rather sad....I have everything going as it should....all input correct...still no root after final reboot...I followed every step to a T several times -rw-rw-rw- grrr...ive rooted many devices none this big of a pain in tha butt!
Used updated su binary on root just for fun...same result
Help plz!
im a noob to this but have been messing around with ubuntu for some time now can someone show me step by step on how to root my zte merit plz? is there a video tut on how? i tried all the quick methods but they don't work, this one obviously does on this page, can someone help start me out plz, im learning still and love to learn more!
---------- Post added at 08:59 AM ---------- Previous post was at 08:45 AM ----------
Univarseman said:
I can't even get past step 2, I have the file installed and unzipped on both my computer and my smart phone. The only thing I can find to put in the codes is command prompt which says "error: device not found" when I type in adb shell. My ZTE Merit phone has very low internal memory due to all the retarded system apps that came on the phone, I would very much like some assistance removing them from my phone. I also downloaded superuser elite onto my phone and it doesn't show up with ANYTHING. The first page says
superuse v3.1.3(46)
tap to display changelog
elite installed
su binary not found
a check in the box "outdated binary notification
unchecked box, temp unroot (When tapped it does nothing)
unchecked box ota survival (Again when tapped it does nothing)
I scroll over to the apps section of the program and it says "No apps in list"
What am I doing wrong? This lack of space is quite irritating
Click to expand...
Click to collapse
help me, whats the first step then i can get the gearz in motion, i have not a clue on how to start this but if i do i can usually figure it out from them sometimes
Start menu
jjflappy said:
Hey Anyone and everyone that may be online, I have a real quick and probably REALLY EASY question for ya... I'm trying to get started Rooting my ZTE Merit and I need to find out how to get to or where to find the screen where I type in the commands. I already downloaded the chainsdd zip file. So now I'm supposed to get shell with adb. If someone would be so kind and put me in the right general direction, I sure would
be grateful.
Thanks in advance,
Jason
Click to expand...
Click to collapse
Start menu then type CMD hit enter
!!!UPDATE!!!!
Sorry I lost my root files. I still have the base code i used to make them. I am trying to work with @saurik to get vtab1008 working with the cydia impactor so that this process will be eaiser. sorry about not keeping up here.
The linux root is still working.
!!!!!!!!!!!!!!!!!!!!!!!!!!!
I was able to get the VTAB1008 HONEYCOMB ROOTED. This device is no longer doomed to a rootless existence.
ROOT AT YOUR OWN RISK! I AM IN NO WAY RESPONSIBLE IF THIS BREAKS SOMETHING.
----WINDOWS ROOT (This worked for me)----
!!Some people have had problems with 64 bit systems.!!
https://dl.dropboxusercontent.com/u/...nys Root.zip (restored by grnsl2)
Download the latest java sdk http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
(if it installs anywhere but C:\Program Files\Java\jdk1.7.0_45\bin\jdb change the path in the runme.bat)
Setup ADB
Follow instructions at http://www.google.com/url?sa=t&rct=...5IAx2Xg-VjGm5pQ&bvm=bv.57155469,d.cGU&cad=rja
for the inf file use the one in the skinnys root,zip
!!!THIS STEP IS VERY IMPORTANT ^ IF YOU ARE HAVING ISSUES YOU MAY HAVE NOT COMPLETED THIS STEP!!!
Run Exploit
open command prompt (windows 7 type cmd in start menu and press enter)
CD to location you extracted the zip
example: cd "C:\Users\skinny\Downloads\Skinnys Root"
type "runme.bat"
You will see a ton of data on the screen after a minute your tablet will show android.app.Activity
Paste the following into the shell (the prompt should have changed to look like >)
Code:
stop in android.os.MessageQueue.next()
Touch your tablets screen (the prompt should change to <1> main [1]
Paste the following into the shell
Code:
print java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh")
Wait until you see something like Java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh") = "Process[id=1265]"
Code:
exit
Press enter to reboot
----LINUX ROOT----
Get Linux on a live usb stick to run exploit (skip if you have a linux system)
Download 32bit kubuntu from http://www.kubuntu.org/getkubuntu/download
Get a thumbdrive at least 2 gig
Launch unetbootin
Select bubble next to diskimage
Choose ISO
Click on ...
Browse to the kubntu iso downloaded at A.
Set drive to your usb drive letter.
The next step will erase your thumb drive!!!!!
Click OK
Process will complete and ask you to reboot (reboot)
Select the thumbdrive at startup (i don't know what type of computer you are using but most systems you can press f8, f11, f12 or f2 tp get the boot prompt)
(For more information read this guide http://sourceforge.net/apps/trac/unetbootin/wiki/guide)
Select Default at the kubuntu boot prompt
Select Try Ubuntu
Get kubuntu linux setup for the exploit (skip if you already have android tools on linux)
Press alt+f2
Type "konsole" and press enter
Paste the following commands in.
Code:
sudo chown kubuntu:kubuntu /opt
mkdir /opt/exploit/
cd /opt/
wget http://dl.google.com/android/adt/adt-bundle-linux-x86-20131030.zip -O adt.zip
unzip adt.zip
mv adt-bundle-linux-x86-20131030/ adt/
echo 'export PATH=$PATH:/opt/adt/sdk/build-tools/android-4.4:/opt/adt/sdk/platform-tools' >> ~/.bashrc
source ~/.bashrc
sudo su -c "echo 'deb http://ppa.launchpad.net/webupd8team/java/ubuntu saucy main
deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu saucy main' > /etc/apt/sources.list.d/oracle-java.list"
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys EEA14886
sudo apt-get update
sudo apt-get -y install git
cd /opt/exploit/
sudo apt-get -y install oracle-java7-installer
Accept Java license agreement to install java 7
Run Exploit
Plug in your tablet
Enable debugging mode (Settings -> Applications -> Development -> USB debugging)
Paste the following commands in your linux console (if following steps use the konsole that you have been running commands in).
If you are not using /opt/adb/sdk for your android devlopemnt use your dir on the 3rd step
Code:
git clone [url]https://github.com/raymondhardy/mkbreak.git[/url]
wget 'http://goo.gl/Ox8qDx' -O Superuser-3.1.3-arm-signed.zip #thanks to @Munk0
unzip Superuser-3.1.3-arm-signed.zip
cp system/bin/su mkbreak/
cp system/app/Superuser.apk mkbreak/
cd mkbreak
./doit.sh /opt/adt/sdk
You will see a ton of data on the screen after a minute your tablet will show android.app.Activity
Paste the following into the shell (the prompt should have changed to look like >)
Code:
stop in android.os.MessageQueue.next()
Touch your tablets screen (the prompt should change to <1> main [1]
Paste the following into the shell
Code:
print java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh")
Wait until you see something like Java.lang.Runtime.getRuntime().exec("/system/bin/sh /data/local/tmp/rootme.sh") = "Process[id=1265]"
Code:
exit
Press enter to reboot
If you get stuck at any part of this process please post a reply with information about the problem you are having.
PROOF OF ROOT
Thanks and credit goes out to.
robertmillan
Jay Freeman (saurik)
PoC by Pau Oliva
Vinogans for leading me to masterkey exploit
NICE!!! Any instruction changes for windows?
gnoober said:
NICE!!! Any instruction changes for windows?
Click to expand...
Click to collapse
Not yet i suspect someone will make a better root later on as of now this is linux only. This exploit uses of linux commands for injecting code into a system application to gain root.
I will be updating the first post later on with steps and screenshots on how to do this on a ubuntu live instance (I may even throw in a shell script so you run it and then wait forever while it does the setup and starts the root. I will see what i can do.)
skinnyquiver said:
I will be updating the first post later on with steps and screenshots on how to do this on a ubuntu live instance (I may even throw in a shell script so you run it and then wait forever while it does the setup and starts the root. I will see what i can do.)
Click to expand...
Click to collapse
Awesome! Nicely done! Guess I'm gonna have to dig out the VTab and give this a shot. Thinking it's gonna need a charge!
Sent from my LG Optimus G using Tapatalk
I updated the steps and re-rooted my tablet with them several times to verify that they worked. Let me know if they work for you
dandrumheller said:
Awesome! Nicely done! Guess I'm gonna have to dig out the VTab and give this a shot. Thinking it's gonna need a charge!
Sent from my LG Optimus G using Tapatalk
Click to expand...
Click to collapse
gnoober said:
NICE!!! Any instruction changes for windows?
Click to expand...
Click to collapse
Got this working on windows (does not look very pretty but it works.
Hey skinnyquiver, that is awesome... my vtab has already gained like 5mm of pure dust. However, i gonna digg it out these days, install stock recovery to update it to honeycomb finally and then reroot this thing...
Btw, the paragraph above windows instructions still says linux only...
_________________________
tapatalked from GalaxyS3
FadeFx said:
Hey skinnyquiver, that is awesome... my vtab has already gained like 5mm of pure dust. However, i gonna digg it out these days, install stock recovery to update it to honeycomb finally and then reroot this thing...
Btw, the paragraph above windows instructions still says linux only...
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
try to root it with master key exploit I am talking about the the version .57 .. then before updating to honeycomb grab the update.zip the one that belong to honey comb ... try to do this
vinogans said:
try to root it with master key exploit I am talking about the the version .57 .. then before updating to honeycomb grab the update.zip the one that belong to honey comb ... try to do this
Click to expand...
Click to collapse
i am currently charging... my device is rooted with frozen updater, firmware is currently 1.9.56 so i am not sure what is the update path, will i get the honeycomb firmware immediately or do i have to update to .57 first?
_________________________
tapatalked from GalaxyS3
FadeFx said:
i am currently charging... my device is rooted with frozen updater, firmware is currently 1.9.56 so i am not sure what is the update path, will i get the honeycomb firmware immediately or do i have to update to .57 first?
_________________________
tapatalked from GalaxyS3
Click to expand...
Click to collapse
u will have to update to .57 then u will get honeycomb update ..
vinogans said:
u will have to update to .57 then u will get honeycomb update ..
Click to expand...
Click to collapse
Thats bad, but i will give that a try. However, i cant promise that i will succeede and it will take me some days as i am quite busy with my real life as well
_________________________
tapatalked from GalaxyS3
So it's certainly exciting to see root for this guy after owning it now for a couple of years.
I believe with root we'll be able to get rid of some bloat and stuff unneeded but I'm assuming we'll stay on Honeycomb.
I'd like to figure out what the real upside to this is.
Sent from my DROID RAZR HD using Tapatalk
grnsl2 said:
So it's certainly exciting to see root for this guy after owning it now for a couple of years.
I believe with root we'll be able to get rid of some bloat and stuff unneeded but I'm assuming we'll stay on Honeycomb.
I'd like to figure out what the real upside to this is.
Sent from my DROID RAZR HD using Tapatalk
Click to expand...
Click to collapse
You should be able to use this root with the 5.7 before going to honeycomb. This way you can have gingerbead rooted if your device came with the 5.7 update. I would like to get this running cm9 or cm10. The first problem with this is it will require a new kernal. I am going to be moving this weekend so it will be a while until I can get a build env to work on this. I plan on using this tablet to learn all about android rom making. Hope I don't brick it.
As Vizio has not released the kernel source I think we may want to look at using the xo-3 kernel.
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
unqualified said:
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
Click to expand...
Click to collapse
What os do u use? Check if adb is working
_________________________
tapatalked from GalaxyS3
unqualified said:
Everything seems like it works, everything says 'success', but root checker is showing no root. I had force closes on the System UI before rebooting it a second time.
I tried it straight from a factory reset, just to be sure, same issue.I'm on 3.2.1 on this Vtab.
Not sure what is missing? Anything I should check?
Click to expand...
Click to collapse
I had this problem also in the first time .. try to check if java is installed and working well .. try to check if ADB driver is identified on ur pc ..
I am thinking it is just a java problem .. did u type the commands in the shell " just wondering " this will not work if u didnt type the commands and follow the steps ..
vinogans said:
I had this problem also in the first time .. try to check if java is installed and working well .. try to check if ADB driver is identified on ur pc ..
I am thinking it is just a java problem .. did u type the commands in the shell " just wondering " this will not work if u didnt type the commands and follow the steps ..
Click to expand...
Click to collapse
Thanks for all the suggestions! I was surprised so many people responded on such a forgotten tablet.
I did enter the two commands in the shell (copied and pasted the exact commands) at the appropriate times, and they appeared to work.
I wasn't able to do the ADB setup exactly per the link on the OP, because my computer already recognizes the VTAB1008 under debugging mode, and runs ADB. If I try to uninstall and manually install the generic driver from the Skinny Root zip, it re-discovers and says the current driver is 'more current'. However, since 'adb devices' recognizes the vtab, and all the commands appear to be working, I should be good to go with ADB, right? Or is the generic driver from the Skinny Root zip file a critical component?
I also uninstalled Java SDK for x86 and re-installed for 64 just in case, but that didn't fix it.
Also tried disabling antivirus, no luck...
Is there a basic way to check whether java is working correctly? Or to read the java output as it is running the commands? Maybe something would show up there.
Thanks again
Do u see superuser app installed? If so, what does it output when you open it?
_________________________
tapatalked from GalaxyS3
FOR FIRE HD 10 (7th GEN, 2017) ON 5.6.0.0 ONLY
Seems like this is a tradition so I will put this on here.
Update 4: 2018/1/14, Offline rooting method by retyre (If no new method comes out, this will be the final update)
Update 3: 2018/1/1, Minor text fix
Update 2: 2017/12/31, New rooting method by bibikalka.
Update 1: 2017/12/28, Added more content
Code:
###Disclaimer###
I am not responsible for the potential damage that will be done to your tablet, such as boot looping and bricking.
Your warranty might be void by doing the following steps.
YOU are choosing to make these modification.
Looks like these methods doesn't work for Fire HD 8 (7th GEN, 2017)
Reason to start this thread
The topic was started by ztrund in this thread and we ended up with a pretty messy thread, which makes people really hard to locate the exact tutorial post. So I think it should be a good idea to start a new thread.
Note: This thread doesn't work for HD 10 (7th Gen) anymore because root access is temporary and it can't survive after a reboot. As a result, don't follow the exact steps on that thread.
Special thanks to strund, DragonFire1024, Blaiser47, mistermojorizin, UROMEGAX, retyre, bibikalka and countless people who helped, discussed and contributed in the original thread.
By the way, please correct me if there is any problem or mistake.
Some useful posts
1. The first detailed tutorial is located in #221 in the original thread. mistermojorizin provided the method and adb shell history.
2. #233 in the original thread. UROMEGAX provided a detailed guide of the method.
3. #304 in the original thread. I provided a more coherent step by step guide.
4. #248 in the original thread. retyre provided a different way to root the tablet. (Blaiser47 wrote that it's easier for him)
5. Easier Way to Root Fire HD 10 used a different approach by bibikalka. (Looks like new method is easier to do) (For legacy method go to post #2)
6. Offline Rooting Method by retyre
After getting root access
1. Xposed & FlashFire posted by retyre
2. tweaks/apps/modules/hacks/optimizations started by razers7t8
New method
Easier Way to Root Fire HD 10 by bibikalka.
Offline Rooting Method by retyre
Legacy way
You need the following things in order to proceed:
1) adb (Available Here)
2) Kingoroot PC version (Available Here)
3) Kingo.to.SuperSU.zip (can be found here in the attachment of the post)
Preparation work:
1. Turn on USB debug mode and "allow third party app to install" on fire HD 10
2. Update Kingoroot to the latest version
Note: There will be a small grey box on the update pop up page. It is up to you whether to uncheck that box or not. I don't think that will affect the following process.
3. Connect your fire HD 10 with your PC.
4. Unzip "Kingo.to.SuperSU.zip". Copy the folder to your internal storage on tablet.
Note: In root explorer the directory is /storage/emulated/0
Let's start:
1.- Install supersu (ver 2.82) on the fire and root file explorer.
2.- Use Kingoroot to root
3.- Open the adb shell and start to type "su" while Kingoroot is rooting (You can also wait until it's done, then type su to proceed)
Code:
[email protected]:/ $ su
Note: Do not type "adb shell su" because you won't be able to type any command once the # appear. The correct way is to type "adb shell" first then start typing "su"
4.- once the # appear i did # mount -w -o remount /system
5.-Uninstall the Kingo super user app normally (Do not choose to unroot in Kingo super user app)
6.- # cd /data/media/0/Kingo.to.SuperSU
7.- # cp ./su /system/xbin/daemonsu (no error was given in my situation)
8.-# chmod 0755 /system/xbin/daemonsu
9.-# daemonsu -d &
10.-# cp ./su /system/xbin/su
11.-# chmod 0755 /system/xbin/su
12.-# rm /system/xbin/supolicy
13.-# rm /system/bin/install-recovery.sh
14.-# rm -rf /system/usr/iku
15.-# rm -rf /sdcard/Kingroot
16.-Open Supersu (and get the Su occupied error)
17.-setting > reinstall (It is not rebooted)
18.-Install Supersu (ver 2.79) and open it
19.-Supersu ask the user to update binary (I tried to update the binary but failed, nothing happened, didn't reboot)
20.-setting > set supersu as a system app (Mine rebooted immediately after doing this step)
21.-Go to google play to launch Supersu (Don't know why the Supersu icon is not shown in the Fire Launcher so this is an alternative way to open Supersu)
22.-setting > set grant as default access
23.-Then (not sure if a reboot is required here) I received a notification from Supersu and it ask me to update binary
24.-Click the notification to update binary and it should work.
Not sure whether it will work or not if SuperSU (ver 2.79) is used in the beginning of the guide.
Personally the method posted here seems simpler and makes more sense to me.
https://forum.xda-developers.com/hd...re-hd-10-7th-generation-t3718629/post74940137
No need to mess with two versions of supersu. After you have root you can just update supersu and binaries to the latest.
I also do not think there is any need to start adb while kingoroot is rooting. It is fine, and maybe better to prevent errors, to just wait until it is done.
I would recommend one always go back to a clean system by sideloading the official Amazon 5.6.0.0 .bin and do not fully set up or connect to the internet until you have rooted. To skip Amazon set up, just select a wifi and enter the wrong password. Then hit back and it will let you skip. May need to do it a few times.
Make sure to say in the op to copy the kingo folder with the files to your SD card storage and clarify that this is the emulated SD. Implied but for newbies just saying you need to have it and not saying where could be confusing.
After you root, if you want the latest updates, at least as of a day or so ago you can still update officially via device options, system updates. But be careful as at some point doing this may remove root if Amazon pushes more updates. To this point I strongly encourage everyone who roots to keep a copy of the current 5.6.0.0 .bin in case you need to recover. If Amazon updates their website with a new updated os, this version may be gone.
Another note, if you are using the fire launcher (default) and new apps are not showing up, just go to manage apps and find the system app called Home Pages. Force stop it and see if that fixes it. If not, go back and force stop and clear data. That should make it work.
I'll add more as I think of things and as this thread evolves.
why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
C:\ADB>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
1|[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
Click to expand...
Click to collapse
{
"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"
}
bakshi said:
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
Click to expand...
Click to collapse
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------
davidinfoman said:
why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
Click to expand...
Click to collapse
Use adb and explore your devices directories. CD to get to a directory, ls to list things in the directory. It shouldn't matter how you get it onto your fire, but it needs to be unzipped. It also doesn't matter where you put it as long as you adjust the commands accordingly. Maybe try the downloads folder?
Thanks for your quick reply, I'll do this now!
UPDATE: Your advice worked! Thanks for clarifying that we should do this with a factory reset and should use Kingoroot on the PC.
Blaiser47 said:
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
Click to expand...
Click to collapse
Part of my problem was seeing written many times ... put files on SD card, and I thought we had to have an external SD card put in the tablet. ( I have been running with that "false IDEA" for a couple of days until an hour ago.
No! SD card just refers to location that is on Fire Tablet itself. The ls command helped me a lot. Others should be aware of this.
I thank Blaiser47 for pointing that out. I am getting much further so far, following the advice in this thread.
Thank you oscarcx for starting this thread. Hopefully you can watch over it, and help correct our errors and giving helpful pointers.
Thanks everybody. I feel better now because the roadblock I hit, has been overcome, now for the other steps in the process.
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
manaox2 said:
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse
manaox2
Thank You! Thank You! Thank You!
You are the man!
Only those of us that have been frustrated with this process can appreciate your KEEP IT SIMPLE approach to this!
Not sure why the other BIG thread on this couldn't do a step by step like you just did!
You listed the steps that were screwing around with me the last couple of days.
Finally it is ROOTED! Yeah!
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
Has anyone tried this method with HD 8 2017 ?
dusty23007 said:
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
Click to expand...
Click to collapse
1. You can get it from Google Play or get it from any liable third party app store.
2. If you get it from any liable third party app store, place it directly in the internal storage so you can install it in es file manager.
3. I remember seeing a post about how to save the bricked device in this forum. You can try to follow that post if your tablet got bricked.
YEAH!!!
rooted baby!!!! now can i get rid of the home tabs?
never mind... i disabled fire launcher
Silly question perhaps, Do I need to reset the device before attempting this?
Guys, how about HD8 2017 ?
wikke said:
Silly question perhaps, Do I need to reset the device before attempting this?
Click to expand...
Click to collapse
It is recommended but may not be required
hacker-on said:
Guys, how about HD8 2017 ?
Click to expand...
Click to collapse
As reported in the original long thread, it doesn't work on Fire 7 or Fire HD8.
my .02, i like these instruction by @retyre. Easy peasy when I had to re-root. mostly just posting here for my own reference, hope it's ok.
retyre said:
I have done this with success multiple times over the last day, so try this and report:
1. Start with a pristine /system (adb sideload update .bin if you can).
2. Root using KingoRoot as usual; confirm su usage in adb shell.
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps (incl. SuperUser) from the Apps page on your Fire's Settings.
5. Confirm su and daemonsu are in /system/xbin/:
Code:
cd /system/xbin
ls -al
If not, copy them to /system/xbin/ as in step 3.
6. Copy SuperSU 2.79 .apk (other versions might work, but this is the one I have tried) to your tablet and install.
7. Open SuperSU and update binary as Normal. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse
oscarcx said:
3. #304 in the original thread. I provided a more coherent step by step guide.[/SIZE]
Click to expand...
Click to collapse
When I use KingoRoot it gets stuck at 90%, nevertheless su binary exists and is working.
The folder /data/media/0/Kingo.to.SuperSU however does not exists.
So I skip steps 7-11.
The folders /system/usr/iku and /sdcard/Kingroot do not exists, so I skip 14 & 15 as well
SuperSU does not show "ocupied", but the update binary pop-up (as in step 19) which seems to be successfull (non-recovery install).
I move SuperSU to /system (SuperSU config) and reboot manually.
afterwards the boot is stuck at the "fire" Logo, a soft brick. I tried this two times using adb sideload to reset the system.
With the news that the Pixel 7 is now restricting applications to 64-bit only, I have created a shell script that can be ran on your old phone to check for any armeabi-v7a only applications that will not run on the Pixel 7.
Obviously this script does not make much sense to run on a Pixel 7, but this will help anyone prepare for switching over and give you a heads up if you won't be able to bring over any apps.
As far as I know almost all applications from the Play Store should already be arm64-v8a as Google has been enforcing this requirement on the Play Store for over 3 years now, but any ancient apps that have not been updated for years might still be 32-bit.
There's two methods to run the script, and two different scripts that can be ran.
Both methods will take some time so be patient if you have a lot of user installed applications.
ADB from computer (root not required)
Make sure you have ADB debugging enabled, platform-tools installed, and your old phone plugged in
Run adb shell
You should now be dropped into a shell on the device
If you aren't then you should try making sure ADB debugging is enabled on the phone, that your phone has authorized your computer, and that the adb server is running on your computer
Paste and run the following command:
for PACKAGE in $(pm list packages -3 | sed "s/^package://"); do if ! pm dump "$PACKAGE" | grep -E "^Dexopt state:" -A4 | grep -q "arm64:"; then echo "$PACKAGE is 32-bit ARM and will not function as of now on the Pixel 7 or later."; fi; done
Any applications that only have 32-bit binaries will be output.
Example:
Code:
raven:/ $ for PACKAGE in $(pm list packages -3 | sed "s/^package://"); do if ! pm dump "$PACKAGE" >
com.dotgears.flappybird is 32-bit ARM and will not function as of now on the Pixel 7 or Android 14.
raven:/ $
If nothing is output then you are fine and have no applications that are only 32-bit.
On DeviceThe following script will be ran, it will also be attached to this post if you want to download it. This is a bit more verbose.
Code:
#!/bin/sh
echo "Script will check for user installed packages that are 32-bit ARM."
echo "This may take a while."
for PACKAGE in $(pm list packages -3 | sed "s/^package://"); do
if ! pm dump "$PACKAGE" | grep -E "^Dexopt state:" -A4 | grep -q "arm64:"; then
echo "$PACKAGE is 32-bit ARM and will not function as of now on the Pixel 7 or later."
FOUND="1"
fi
done
if [ -z "$FOUND" ]; then
echo "No user installed 32-bit packages found."
fi
echo "Script done."
Either download the script or copy the above code and paste it into an empty file. Make sure you don't mangle it if you are pasting it and to name it arm32appchecker.sh.
Terminal Emulator (root required)
Use your favorite terminal emulator (I prefer TermOne Plus)
Make sure you have functional root, and that you navigate to where the script is or supply the path to it
Make sure the above script is on your phone somewhere accessible
Navigate to the directory where it is (most likely /sdcard/Download)
Run the following command
su -c sh arm32appchecker.sh
Over ADB (no root)
Make sure you have ADB debugging enabled, platform-tools installed, and your old phone plugged in
Make sure you get the script on to your device, either via adb push arm32appchecker.sh /sdcard/Download or download it.
Run the following command on your computer
adb shell sh /sdcard/Download/arm32appchecker.sh
Any applications that only have 32-bit binaries will show up. This script will also let you know if there aren't.
Example:
Code:
raven:/sdcard/Download $ su -c sh arm32appchecker.sh
Script will check for user installed packages that are 32-bit ARM.
This may take a while.
No user installed 32-bit packages found.
Script done.
raven:/sdcard/Download $
What Can I Do If I Have 32-bit Apps?If you have old APKs then I suggest trying to find some new ones. Check on APKMirror for the application to see if there are any newer ones or variants that are built for arm64-v8a. If the application is from a developer directly then try reaching out to them.
Beyond that, there is nothing else that can be done at the moment. It's theorized that the change is only in the Android zygote process, and that the phone still has a full compliment of 32-bit libraries. It is entirely possible for a custom ROM or Magisk module could patch zygote and you can then launch 32-bit apps.
What we do know is that the chipset (Tensor G2 - GS201) is still using ARMv8-A processors that support AArch32, so it's not a hardware limitation.
It is my intention to at some point also create a script that will use aapt to check any downloaded APKs you have. This script will be Linux only, but I will give the commands used so you could cobble together one for Windows. I used to actually have a script to do this several years ago, but have lost it since.
A couple more things to note.
Any applications that are wildly out of date, like built for Android 1-2 might not run at all on Android 13 if they are trying to get permissions that are blocked now. You're not going to get around that if the application isn't functioning because of permission changes.
There is evidence that Google might be forcing this change with phones launching with Android 14. This certainly sets a deadline for new devices going forward. They may also force this change with upgrades to Android 14, but it is currently speculation.
Oh I'm loving this, thank you!
But seems like I'm the only one who voted "yes" haha! (haven't used your script yet but I think I have older apps that are not updated anymore that are probably 32 bits)
Ghisy said:
Oh I'm loving this, thank you!
But seems like I'm the only one who voted "yes" haha! (haven't used your script yet but I think I have older apps that are not updated anymore that are probably 32 bits)
Click to expand...
Click to collapse
That's what I thought originally, I scrolled all the way to the bottom of my previously installed on the Play Store and found the oldest application that hasn't been updated. It was from 2014 so I was certain it was going to be 32-bit, however much to my surprise it was actually 64-bit.
I actually don't have a single application that is 32-bit only, I had to download Flappy Bird from APKMirror just to have a test case for the script.
Thank you, wise one! This confirms the problem I was having installing some of my favorite modded apps yesterday. It will be interesting to see if the apps get updated and/or there is a workaround at some point.
Alright, I have 12 apps that are 32-bit and not compatible with the P7P.
Most of these I can uninstall/replace but it seems like the Instagram mod I'm using is 32 bit-only. Surprisingly, the Amazon App Store is one of them too. Cr*p!
Ghisy said:
Alright, I have 12 apps that are 32-bit and not compatible with the P7P.
Most of these I can uninstall/replace but it seems like the Instagram mod I'm using is 32 bit-only. Surprisingly, the Amazon App Store is one of them too. Cr*p!
Click to expand...
Click to collapse
Same with the Instagram Moded apk. I guess we'll have to wait a bit.
Supermaxness said:
Same with the Instagram Moded apk. I guess we'll have to wait a bit.
Click to expand...
Click to collapse
I've emailed the dev of the one I'm using. I'll PM you if I get a reply (not too sure we're allowed to talk about this here).
For direct, quick and dirty checking an apk (either on your desktop or device) you can just do an unzip and a grep.
The details are dependent on how unzip and grep take flags and the listing format.
Code:
C:\>7zip l fennec-68.11.0.multi.android-arm.apk|grep lib
247300 169274 lib\armeabi-v7a\libfreebl3.so
26376 12943 lib\armeabi-v7a\liblgpllibs.so
132744 60551 lib\armeabi-v7a\libmozavcodec.so
144924 70955 lib\armeabi-v7a\libmozavutil.so
1213340 485264 lib\armeabi-v7a\libmozglue.so
1164536 764454 lib\armeabi-v7a\libnss3.so
352812 176726 lib\armeabi-v7a\libnssckbi.so
14196 7407 lib\armeabi-v7a\libplugin-container.so
141344 85415 lib\armeabi-v7a\libsoftokn3.so
58525688 31002207 lib\armeabi-v7a\libxul.so
Thanks for the script! Looks like I only have about 3 apps that won't work on my P7P when it arrives.
I ran it over wireless ADB.
The script isn't working on my phone, it's listing a bunch of apps that I know have 64-bit (or might be pure java/kotlin) such as Swift Backup.
When I break it down, the pm dump has output, but piping that to the grep -E does not
Is this how the script should work? If yes, does it mean that I have none 32-bit apps on my phone? Thank you
davidgro said:
The script isn't working on my phone, it's listing a bunch of apps that I know have 64-bit (or might be pure java/kotlin) such as Swift Backup.
When I break it down, the pm dump has output, but piping that to the grep -E does not
Click to expand...
Click to collapse
I have Swift Backup on my phone and it doesn't show up. Which method did you use? What phone do you have? What version of Android are you running?
flashbac76 said:
Is this how the script should work? If yes, does it mean that I have none 32-bit apps on my phone? Thank you
Click to expand...
Click to collapse
You're not doing it right, you're just pasting the script into the terminal emulator or letting it try to read and paste the file for you, download the script from the attachment in the post and follow the directions for a terminal emulator with root. If you still can't get it to function or don't have root then try the ADB method that is listed right after the terminal emulator method.
Ghisy said:
Alright, I have 12 apps that are 32-bit and not compatible with the P7P.
Most of these I can uninstall/replace but it seems like the Instagram mod I'm using is 32 bit-only. Surprisingly, the Amazon App Store is one of them too. Cr*p!
Click to expand...
Click to collapse
I just checked and it's absolutely hilarious that the Amazon App Store can't be installed, nearly 2023 and they still don't know how to make universal APKs.
Thank you very much! The script found 2 apps on my phone. One I should be able to easily replace with another, and the other is a game that I won't miss.
I have a game on my phone that hasn't been on the play store or updated for many many years, I'm surprised that didn't show up.
davidgro said:
The script isn't working on my phone, it's listing a bunch of apps that I know have 64-bit (or might be pure java/kotlin) such as Swift Backup.
When I break it down, the pm dump has output, but piping that to the grep -E does not
Click to expand...
Click to collapse
So I checked and it appears you're using a V20? It's possible that your device has old enough utilities that they don't support grep with extended regular expressions. The script might work without that one grep, but with how much junk pm dump includes about the system state I wanted to be able to anchor it to a point where I know the data I am looking for will be so I don't end up with false positives or negatives.
You can try this updated script to see if it works. I tested it on my phone and it still works, so if it works for you I guess it can be pushed to everyone else.
One App com.amazon.venezia = Amaton Appstor, wtf Amazon 32bit in 2022?
Ghisy said:
I've emailed the dev of the one I'm using. I'll PM you if I get a reply (not too sure we're allowed to talk about this here).
Click to expand...
Click to collapse
If you get any answer, please send me a PM too if you can. I was using Instander. I tried Aeroinsta, InstaPro and InstaXtreme, but all of them are 32 bits only...
narcisrm said:
If you get any answer, please send me a PM too if you can. I was using Instander. I tried Aeroinsta, InstaPro and InstaXtreme, but all of them are 32 bits only...
Click to expand...
Click to collapse
Yeah, they all seem to be 32 bits only. I believe the official Instagram app is 64 bits so why?
No reply yet but I'll PM everyone who is interested. Don't wanna flood this thread too much.
Namelesswonder said:
I just checked and it's absolutely hilarious that the Amazon App Store can't be installed, nearly 2023 and they still don't know how to make universal APKs.
Click to expand...
Click to collapse
You know what? I emailed the Amazon App Store support through the app for 64-bit support. No idea if I'll ever get a reply (it's mostly for sh*ts and giggles haha) but eh, worth a try.