-------THIS GUIDE IS NO LONGER NEEDED------
If your on a rootable version follow the guide and instructions to install a pre rooted Firmware, with Rbox's custom recovery.
This I supposed was good to use to have SuperSU before we had any type of recovery.
-----UPDATED V3-----NEW DOWNLOAD LINKS-----
*PLEASE READ THROUGH THE FULL GUIDE BEFORE STARTING.*
FIRE STICK Replace King/o Root with SuperSU v3.
Thanks @joojoobee666 for his suggestions on layout of the guide to try make it more understandable to folk and also to incorporate a step into the script to make it a little easier still.
First off i am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
REMEMBER GUYS, the process for this to work is root with KINGOROOT - reboot-root with KINGROOT - reboot - run the commands - uninstall KINGOROOT. Failing to follow the order of the steps could soft brick you.
Prerequisites
Fire Stick
Fire OS 5.0.5 (if your on anything other than 5.0.5 use my other guide to downgrade to 5.0.5 here:
http://forum.xda-developers.com/fire-tv/development/fire-tv-stick-downgrade-firestarter-3-2-t3399298 ) dont forget to block updates again.
An understanding that 2 separate root programs are used in this guide KINGO ROOT and KING ROOT.
Installation Procedure :
You must follow these steps exactly as they are here, any deviation from this could cause you to brick (which is undo able so dont worry too much)
If you are not already rooted you need to root with KINGO ROOT. Once rooted reboot your Fire Stick. download it from here :
https://root-apk.kingoapp.com/kingoroot-download.htm
Your now able to follow the guide after you Root with KINGO ROOT.
Procedure
1.) Download the rar file containing the scripts and APKS:
http://www.filedropper.com/firestickroot_2
http://s000.tinyupload.com/?file_id=73723140467469181970
http://www.megafileupload.com/7nfv/firestickroot.rar
2.) Extract the file pack in the rar to /sdcard on your Fire Stick, PLEASE DOUBLE CHECK THIS. YOU NEED TO HAVE THE FOLDER STRUCTURE CORRECT OR IT COULD CAUSE PROBLEMS. YOU SHOULD HAVE /SDCARD/FIRESTICKROOT/CONTENTS . Inside the firestickroot folder you will see KING ROOT, install this and open it. Grant any permissions to it and let it take over root. When its finished, reboot your Fire Stick.
3.) Open an ADB Shell connection to the device. You should now see a prompt like this:
[email protected]:/ $
4.) Run the "su" command and choose "Allow" when prompted by KINGROOT on the screen. If successful, you should now see the following in the terminal:
[email protected]:/ $ su
[email protected]:/ #
5.) Run the following command:
sh /sdcard/firestickroot/root.sh
if successful you should see something similar to this
[email protected]:/ # sh /sdcard/firestickroot/root.sh
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
rm: /system/app/Kinguser.apk: No such file or directory
/system/bin/am[8]: app_process: not found
/system/bin/pm[6]: app_process: not found
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
cp: /system/xbin/su: Text file busy
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Success
-----------Your Welcome--------------
6.) Run the SuperSU application, go to settings and un-check Enable Superuser then re-check it.
7.) Reboot the device (either hold play and select or run "reboot" from the ADB Shell prompt)
8.) Open ADB Shell once again and run "su". This time you should see the SuperSU prompt asking to allow the ADB Shell process to run as root.
9.) Uninstall KINGOROOT
10.) If you have any reminents of KING ROOT installed uninstall them, if it wont let you uninstall, re-install KING ROOT but DONT OPEN IT! then you can uninstall it.
IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again.
Thumbs up if ive helped
If anyone can make use of another app from chainfire, Flashfire, as it now will work with chainfires Su binaries installed. The app allows for backup/flash all partitions/install zips etc. Im not sure if its fully working or maybe an older version might?
Anyway ill leave that for anyone who might want to test that app out.
*IMPORTANT*
If you still cant seem to manage this, delete he associated KINGOROOTS SUPERUSER manually, then right after you have installed KINGROOT and rebooted navigate to /system/xbin and delete the file daemonsu. When the script finishes run it a second time, if you dont get chainfires SuperSU installed manually install it. This is included in the script to carry out this task but seems it wont work for everyone.
sconnyuk said:
be back soon with re-written guide v2 that is much simpler.
Click to expand...
Click to collapse
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
asafegous said:
:good: i went out and bought the device for this process. was going to pull the trigger on the long complicated route. can you throw together a twrp image for us as well?
Click to expand...
Click to collapse
Ive re done the guide made it much simpler, spent 2 days on it trying all ways to brick my device in the process and could not brick it no matter how hard i screwed up.
This newer guide should work 1st time if followed correctly, and you will be shot of Kingo/o Root.
Im real sorry but to make a custom recovery is a little beyond me.
sconnyuk said:
*Update*
I am not responsible for your device, if you want to wait for a custom recovery (if one is even being made) that is your choice. Ive spent 2 days trying all possible ways to accomplish this and made it as easy as i could for you.
The guide has been re done again by myself as it was far too long and although there was zero chance of bricking (with the use of Kingo Roots windows tool) ive put v2 together which is much simpler and all in a single script you will have no chance of any brick, with success the first attempt
This guide is for Fire Stick 5.0.5, you need root access with KingRoot, so if your rooted with Kingo Root please update your root app with the KingRoot apk in this pack, it will take over your Kingo Root and use King User.
Please note, you must root originally with Kingo Root, restart then Re-root with KingRoot then restart again, if not you will find that after a restart you will get unrooted.
Also be aware, if you have followed this through and still after a restart you are unrooted navigate to /root/system/xbin and delete the file daemonsu, then try again.
Download the pack here : http://s000.tinyupload.com/?file_id=02940258229221060594
Extract it in your Fire Sticks /sdcard directory.
You should have a folder in your Fire Sticks /sdcard directory called firestickroot.
Ive noticed myself that if im at the standard fire tv stick launcher sometimes king/o root fails to grant permissions so for the next step be aware and maybe have firestarter/app starter launcher loaded up.
Connect your Pc/Laptop/terminal to your fire stick and type the following commands. (grant permissions to all)
su
sh /sdcard/firestickroot/root.sh
Thats it, the script will remove KING ROOT and all associated files and install su binary and SuperSU apk.
Once you restart make sure you are using ChainFires SuperSu and uninstall Kingo Roots stuff.
Thumbs up if ive helped
Click to expand...
Click to collapse
II
@sconnyuk, could you pls add another d/l mirror? Thx
dave157 said:
@sconnyuk, could you pls add another d/l mirror? Thx
Click to expand...
Click to collapse
I certainly will when I get home later.
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
joojoobee666 said:
This is not working for me here. Here's the log:
Code:
-----------------------------------------
-----------------------------------------
---FireStick SuperSU Tool by Sconnyuk----
Thanks to Mr.W0lf for the original script
------Thanks @Chainfire for SuperSU -----
--------Swap KingRoot for SuperSU--------
-----------------------------------------
-----------------------------------------
Success
Success
rm: /system/app/Kinguser.apk: is a directory
rm: /system/app/Kinguser: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
/sdcard/firestickroot/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.kinguser: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
----------------INSTALLING SU BINARIES--------------------
mkdir failed for /system/bin/.ext, File exists
ln: /system/bin/install-recovery.sh: File exists
cp: /system/bin/mksh: No such file or directory
pkg: /sdcard/firestickroot/superuser.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=android.permission.ACCESS_SUPERUSER pkg=com.kingouser.com]
-----------Your Welcome--------------
I removed the com.kingouser.com package manually and was able to install the Superuser APK but when I run Superuser, it says the SU binaries are not installed. I've reinstalled KingRoot for now but this script is NOT bullet proof. I'm not sure exactly what state this is leaving me in but root seems to be working again after reinstalling KingRoot. Should I be completely removing KingoRoot BEFORE running this script? If so, the instuctions hould mention it. As of now, I'm afraid to do so for fear of bricking this thing. Any thoughts?
Click to expand...
Click to collapse
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
sconnyuk said:
As the guide says if you have problems navigate to /system/xbin and delete daemonsu
First make sure you are rooted with KINGO ROOT - reboot
Second install the KING ROOT apk in the pack you downloaded and placed in /sdcard. let it take over root and should install its own King User apk. - reboot
Third step :
su
sh /sdcard/firestickroot/root.sh
The script is no way bulletproof but it works, if anyone would like to moddify it to better suit Fire Stick that would be great. As for bricking, i understand that nothing is 100 percent fail proof as in root etc but the way this script is set out ive tested it for 2 days uninstalling root re installing king/go in different combinations and could not brick my stick, i got a few restarts but that was all. The v1 guide i did had higher chance of bricking (trust me i tested the crap out of it) and everytime my stick failed to boot i plugged it into my laptop and ran either kingo or king root windows versions and it re rooted and got me back up and running, everytime.
I tried all different combinations to try brick and not be able to bring it back but always did.
The v2 guide here what your using i couldnt get my stick to brick once.
Click to expand...
Click to collapse
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
joojoobee666 said:
I initially WAS rooted with Kingo, re-rooted with King and rebooted, then ran script. But it FAILED to complete so I didn't try the removal of deamonsu since it never completed. Is that going to fix the error I received when installed Superuser.apk? That error seems to be unrelated to the leftover daemonsu as it's in regards to a conflict with packages installed from KingoRoot. Review of the scripts shows that they in NO WAY remove that application (com.kingouser.com) so I imagine I will end up in the same spot....If I get there. I'm currently stuck on "fireTVstick" logo after trying to Re-Root with Kingo as you suggested. I don't think this looks very good...
Click to expand...
Click to collapse
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Nowhere in the guide says you must install SuperSU apk, the script does this for you. All you should be left with when it completes is KingoRoot and a newly installed SuperSU apk v2.01
sconnyuk said:
OK, run the windows version of KingoRoot on your pc/laptop. if it fails first time unplug usb then plug it back in and it should root you and get you back up and running.
Its failing to complete because the daemonsu file is there. Delete it and the script will finish and uninstall KingRoot.
Click to expand...
Click to collapse
Thanks. Will give all that a go here and let you know.:good:
joojoobee666 said:
Thanks. Will give all that a go here and let you know.:good:
Click to expand...
Click to collapse
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
sconnyuk said:
Definitely want to know if everyone is having success, i did not make the scripts used here, i just slightly modified them and merged more instructions.
Everytime i run the script it works and if it wasnt for the fail safe of Windows Kingo Root i would not of put the guide up.
Click to expand...
Click to collapse
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
joojoobee666 said:
Hmm...I'm not having any luck with the KingoRoot windows app. It's not even getting to the point where it can fail. "Connecting...Please enable USB Debugging mode" is where it's getting stuck. If I remove the fire stick and plug it back in, nothing happens in the program. It still just sits at that screen. I can adb into it but I do not get root (of course). Should I maybe relflash the 5.0.5 update.bin I have sitting on the SD card (if possible)?
Click to expand...
Click to collapse
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
If not, run kingroot windows tool if that works then ok, if not dont close it open kingoroot up and then try, you will get it detected it happened to me a few times when i did v1 guide
sconnyuk said:
Just restart the KingoRoot app and plug unplug firetick and plug it back in, it will eventually detect it.
Click to expand...
Click to collapse
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
joojoobee666 said:
I think I've done all that over 10 times, same thing keeps happening. The one thing I have gotten twice is a window titles "Notification" that explains that I will need to allow debugging on the device for the app. Obviously, I cannot do that. It eventually goes away on its own then hangs at the aforementioned screen again. Any other suggestions?
Click to expand...
Click to collapse
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
sconnyuk said:
restart your pc/laptop try another usb port ? did you try KINGROOT windows app then if that goes ok fine, if not dont close it open KINGO ROOT windows app and try it then, like i said i had this a few times when i did the v1 guide but everytime i got it back up again.
Click to expand...
Click to collapse
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now? (side note, there is not daemonsu in /system/bin currently)
joojoobee666 said:
I was just in the middle of installing the KingRoot app. I ran it and it said it was successful. Should I just reboot now?
Click to expand...
Click to collapse
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
sconnyuk said:
If it wont start up in a few minutes yes just unplug and plug it back in.
Like i said, i would not of put guide up if there wasnt the failsafe methods of KING/O for windows in place.
Click to expand...
Click to collapse
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
joojoobee666 said:
That was the only reason I decided to go for it. However, It's still stuck on the fireTV Stick logo...after multiple reboots
Click to expand...
Click to collapse
Let it sit there a while, will probably go to optimising screen.
If it wont re root it with Kingo/king on pc and dont restart after, just let it sit and it should go to optimising screen.
Related
Im experienced rooting phones and i already read the faqs, but this seems to be the hardest phone ive ever come across with rooting. superoneclick freezes before i get a chance to use it,i tried using odin which gets stuck halfway through, ive closed all kies process also, ive tried using "DooMLoRD's Easy Rooting Toolkit" and it gives me this error "rm: can't remove '/system/app/Maps.apk': Read-only file system
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!""
i feel like i exhausted every idea to root it, i feel like i either brought a broken phone or im just dumb lol,but can anybody please help me.
Last I tried I did with SuperOneClick and ZergRush exploit.
Make sure you have dev mode enabled on phone, and I had to run the app in compatibility mode (running Win7 x64) AND as admin (right-click).
The SuperOneClick tool, DooMLoRD's Easy Rooting Toolkit and the zergrush exploit do not work on UCKK6 (2.3.6) Gingerbread, only on UCKH7 (2.3.4).
You can follow the guide which is the first link in my signature. You will need to flash the stock plus root package using Odin, paragraph 2C. You said you had trouble with Odin before, but you didn't say with what firmware package. This is your best path to root, and the only one that does not increment the flash counter.
With odin ive tried both packages in [Heimdall][Odin][Stock][Root]UCKH7/KK6 Return/Unbrick to Stock (or Root), ive also tried the "odin3 one-click" from that thread, it wouldn't recognize my phone all the odins ive tried would recognize it. i will try the stock root package from that thread.
Could be user error. Have you ever used Odin successfully before?
Or it could be a driver problem.
I would suggest that you make sure it's not user error first. Use the following guide. Follow it step by step in order
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
i can't even use odin now my phone is labeled as unknown device, its a shame i don't know what else to do. ill either just keep using it on 2.3.6 or sell it since i don't think its possible to root it now. Before it was being recognized by both computers now its not.
is there anyway to root it from the phone?
Sounds like a driver problem. I had the same issues. Google this it helped me. Samsung USB Driver for Mobile Phones v 1.4.8.0 and Delete Kies. After I deleted Kies everything worked. So maybe this will help you. Then you can start over using Creepys post.
im uninstalling kies right now and downloading the usb drivers, my phone was already recognized by windows i don't understand why that changed
chillywillyhoe said:
im uninstalling kies right now and downloading the usb drivers, my phone was already recognized by windows i don't understand why that changed
Click to expand...
Click to collapse
Just to be sure, uninstall kies and if you have Samsung USB Drivers for Mobile Phones listed under program manager also uninstall that, then reboot, download the USB drivers, install, reboot again. Usually driver problems happen because people are too lazy to reboot their computers between uninstalls and reinstalls, and again afterwards.
i uninstalled kies and the usb drivers, rebooted, installed the usb drivers, rebooted, and my device still shows up under "unknown device", i have no idea what to do now
Basically it says its not installed, but it says its installed.
I'm not sure this is related, but perhaps you can try toggling usb debugging mode (settings->developer options) or enable usb mass storage mode before connecting your phone?
Also, extract the contents of the drivers install using a program like 7zip, tell Windows to update the drivers and point to that directory and see if it finds anything updated.
Yeah I'm hoping he knows he has to have usb debugging disabled at least one time when plugging in so it detects it properly.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
seanpr123 said:
Also, extract the contents of the drivers install using a program like 7zip, tell Windows to update the drivers and point to that directory and see if it finds anything updated.
Click to expand...
Click to collapse
i extracted it but there's a bunch of folders, what folder is the right one to choose? how do i enable usb mass storage?
seanpr123 said:
Also, extract the contents of the drivers install using a program like 7zip, tell Windows to update the drivers and point to that directory and see if it finds anything updated.
Click to expand...
Click to collapse
Phalanx7621 said:
Yeah I'm hoping he knows he has to have usb debugging disabled at least one time when plugging in so it detects it properly.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
usb debugging is off, its still not seeing it
chillywillyhoe said:
i extracted it but there's a bunch of folders, what folder is the right one to choose? how do i enable usb mass storage?
Click to expand...
Click to collapse
I believe last I tried I was able to point to the general directory and tell it to traverse through sub-directories and it worked after that.
Also, does your dir look like this:
Or this:
seanpr123 said:
I believe last I tried I was able to point to the general directory and tell it to traverse through sub-directories and it worked after that.
Also, does your dir look like this:
Or this:
Click to expand...
Click to collapse
I'm using XP by the way if that helps and mine looks like the second one, which folder do I choose because its not letting me choose the whole USB drivers folder just one folder.
FINALLY!, thank you all for your help, i serious have no idea what happened, as soon as i seen it recognized it i just went for it, i assume im rooted now, so i got to figure out a way to put cwr on it.
chillywillyhoe said:
FINALLY!, thank you all for your help, i serious have no idea what happened, as soon as i seen it recognized it i just went for it, i assume im rooted now, so i got to figure out a way to put cwr on it.
Click to expand...
Click to collapse
Before you go off, a couple friendly warnings: CWM is built into the custom kernels for our phone, it is not separate, so DO NOT attempt to install it/update it separately from the kernel you choose. Also, NEVER, EVER use ROM Manager.
As for how to install a custom kernel which will include CWM, just follow creepy's guide from 3a.
I succesfully updated my Samsung Galaxy S3 from Android 4.2.2. to 4.3 after rooting my Phone.
However, SuperSU doesn't work anymore, giving the message "If you upgraded to Android 4.3 you need to manually re-root".
I cannot find an answer in the forums here on XDA developmers.
Can anyone help me?
Thanks in advance,
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Rooted 4.3 and installed SuperSU
morwit99 said:
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Click to expand...
Click to collapse
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Same problem here
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
otto68 said:
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
Click to expand...
Click to collapse
if you have supersu or super user already than just download update-supersu from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and flash it through the recovery mode( custom recovery preferred).
xprivacy / reboot to recovery
In my case I was getting false alerts as xprivacy has blocked system access. (eg was with AdAway) Cleared those apps in XPrivacy and all worked find then.
Also you can try to go into recovery and the try to reboot. You may get message to reinstate/fix SU.
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
You rock, I had re-rooted my updated Android 4.3 but my SuperSU was not usable anymore. Redownloaded it, allowed it to update SU Binary, disabling Knox, and viola! Root galore
suyash1629 said:
if you have supersu or super user already than just download update-supersu from ...LINK REDACTED.. and flash it through the recovery mode( custom recovery preferred).
Click to expand...
Click to collapse
that fixed it for me..thanks :good:
Tried all these steps on the new 4.3 MK6 ROM. Does not work for me. I cant find the Root access option itself in developer options. I already tried flashing CF-Autoroot multiple times after factory reset, using odin. I CWM still says binaries outdated and SuperSU doesn't work work even after updating from play store. Later i tried flashing supersu via the recovery mode. Still no success. Any suggestions?
Edit:
Another factory reset and flash did it. I don't know how. But it is fixed now.
By following your step, my superuser icon is gone...
Stuck in ODIN
Everytime I try to root S3 LTE via ODIN with CF auto root, it gets stuck there, need some help please, have had to use kies's recovery tool 3 times today because of that
i dont have this function
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
Hi, I dont have this function in my phone, nowhere, please help me?
fragiepacino said:
Hi, I dont have this function in my phone, nowhere, please help me?
Click to expand...
Click to collapse
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
no
tallman43 said:
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
Click to expand...
Click to collapse
the root function in the developers section, nowhere i can tick it
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Sorry I thought you wanted to know how to get into developer settings....This thread is from 2013 i don't have S3 anymore if your trying to get root to work just follow some of the other suggestions posted.:good:
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Here you don't have the "root access" setting ?
Sent from my GT-I9300 using XDA Free mobile app
s3 i9305 supersu binary problem
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix.
PS. If this post is i wrong place please advise where itshould be.
Thanks
S :good:
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
I can't find my phone as one of the packages. I have an Alcatel phone.
root my mobile but didn't get access
rooted my phone micromax a116, all proccess done wel as shown in tutorials. But root checker says that "root access is not properly installed on this device". Please tell me what to do?
DISCLAIMER : You attempt the following at your own risk !
I'm not responsible if your phone blows up, bricks, you travel back in time or go bald or something!
Background :
I have the MT2-L05 Mate 2 from China.
When I received my Mate 2 last Thursday, the phone was on 4.2.2
After much hunting and downloading and flashing of ROMS, I managed to finally update to 4.4.2 KitKat.
Great ! I was happy. But I didn't have root access.
After trying and failing to use the various bootloader unlock tools on these forums, I Emailed Huawei, and politely asked them if I could have the 16 digit code for my Mate 2. An hour later an Email arrived with my bootloader unlock code, so I fastbooted, used the code and unlocked the Bootloader.....Cool ! Thanks Huawei, great customer service.
I then went to root my phone, and here the problems started. I tried at least 20 different Root tools, both via phone and over the pc, but no joy.
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine and all was good with the world. I tried wakelock detector first ( Yeah, I know, I REALLY need more battery life from the Mate 2 ! ), and Supersu asked for permission and it worked no problem.
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
Root Genius 2.0.1.3 :
http://www.shuame.com/root/
The Problem :
The 4.4.2 update adds a file to your System folder called :
set_immutable.list
this file contains :
Code:
/system/bin
/system/build.prop
/system/etc
/system/fonts
/system/framework
/system/isp.bin
/system/lib
/system/ons.bin
/system/usr
/system/vendor
/system/xbin
/system/app/HwLauncher6.apk
/system/app/HwLauncher6.odex
/system/app/systemUI.apk
/system/app/systemUI.odex
Any location listed above is IMPOSSIBE to mount as rw. Every file explorer or emulator you try will tell you it is rw, but it's not.
It's locked down completely...................and it's REALLY annoying.
This is why I could never edit my build.prop or Install Adaway etc..................
But I found a solution...... ( I think ! )..........
The Solution :
I spent the afternoon at work using google translate to find a fix for my problem and found a post from a guy called :
**** wire His Royal Highness Prince czx ( I cannot post the first 4 letters as it will probably be banned....It must be a Google translate error but it made me laugh ! )
His guide never worked for me until I made a few edits and added STEP 4. Then I got it to work.
The Solution :
1, First Root your Phone ( I suggest trying Root Genius 2.0.1.3 from my first post )
2, install busybox (I suggest BusyBox ( Stericson ) as I couldn't get this to work with the Jrummy BusyBox installer )
3, Install Rom Toolbox Pro ( I know it's payware and I tried other programs, but this is the only one that worked for me. I had already purchased ages ago. The free version may contain the following tools too, but I genuinely don't know )
4, open Scripter from Rom Toolbox pro and click " Mount System R/W "
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
6, Leave Terminal Emulator open, Hit your Home Button
7, then delete the file :system / set_immutable.list with Root Explorer. Other File managers with root access may work, I haven't tried
If you can not delete it, the above steps haven't worked, I can only suggest you try from step 4 after rebooting your phone.
If you are successful and manage to delete the set_immutable.list file then reboot your phone.
Job Done !
You now have full Root Access.
This has been tested by myself on my MT2-L05, it should work on ALL China Variants and presumably on the US MT2-L03 if this file is included in a 4.4.2 update, but I obviously cannot guarantee this.
I'm also curious as to whether anyone thinks this has left my phone open to exploits by the deleting this file....? Remember, if I have done something stupid by doing this, then so will you if you follow the above!
All I know is Xposed has installed perfectly after finally being able to edit my build.prop file and Adaway is running like a charm.
Feedback very welcome.
4L0M said:
The Solution :
Snip
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
Snip
Click to expand...
Click to collapse
I followed your guide, the part I bolded didn't seem to work for me, but after a few attempts I just kept going with the rest of the guide and I was still able to delete the file at the end of the day Thank you so much! I always felt like the root I had with 4.2 was kind of a pseudo root since I was limited by my root access, this is exactly what I needed!
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
4L0M said:
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
Click to expand...
Click to collapse
Thanks dude. Btw does your device support Google search by swiping up from home?
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Same issue for me
janrck said:
Same issue for me
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
Cool xposed apps for 2.5.1 :
wanam kit : adds circle battery, expanded notifications, 4-way reboot menu etc etc
Android L Navbar : adds Android L navbar and Android L shapes Navbar
Both work flawlessly for me and have NEVER crashed once.
Hi, I followed your steps but in the step 5, when i type this : mount -o rw, remount / system it doesnt work.
4L0M said:
DISCLAIMER : You attempt the following at your own risk !
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
Click to expand...
Click to collapse
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
magicpromise said:
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
Click to expand...
Click to collapse
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
4L0M said:
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
Click to expand...
Click to collapse
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
magicpromise said:
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
Click to expand...
Click to collapse
Can you please upload the script you made?
You'll make things easy for me, 'cause commands in terminal don't seem to work in my case.
Thank's !
After searching a guide about this on internet for weeks (without any result), i decided to post my own guide about Permanently Rooting a L9 II mounting KitKat (it also include two little scripts made by me, to simplify the process to newbies) :good:
Code:
[COLOR="DarkRed"]DISCLAIMER: I DONT TAKE ANY RESPONSABILITY FOR ANY DAMAGE DONE TO YOUR PHONE[/COLOR]
P.S: You need ADB to be installed on your Computer.
1)Install TowelRoot (go to TowelRoot website with the L9 II and press the red Lamba, it will start the tr.apk download)
2)Open the "TowelRoot" application and press "make it Ra1n"
3)Install "Super User" and "Total Commander" from PlayStore
4)Enable "USB DEBUG" in "Developement" setting's
7)Download "init.engdo.post_boot1.sh" and place it in C:
6)Download and open Permanent_D605_KK_Root_Part1.bat
7)Open "Total Commander" , go into /system/etc/ , delete the original "init.engdo.post_boot.sh" and rename "init.engdo.post_boot1.sh" to "init.engdo.post_boot.sh"
8)Download and open Permanent_D605_KK_Root_Part2.bat
9)Enjoy
If anybody will ask for it, i'll upload a standalone .exe to do all this
P.S: I'm kinda new to XDA and English is not my motherlanguage, sorry about any mistake i could've made
Erorr
CursedCake said:
After searching a guide about this on internet for weeks (without any result), i decided to post my own guide about Permanently Rooting a L9 II mounting KitKat (it also include two little scripts made by me, to simplify the process to newbies) :good:
Code:
[COLOR="DarkRed"]DISCLAIMER: I DONT TAKE ANY RESPONSABILITY FOR ANY DAMAGE DONE TO YOUR PHONE[/COLOR]
P.S: You need ADB to be installed on your Computer.
1)Install TowelRoot (go to TowelRoot website with the L9 II and press the red Lamba, it will start the tr.apk download)
2)Open the "TowelRoot" application and press "make it Ra1n"
3)Install "Super User" and "Total Commander" from PlayStore
4)Enable "USB DEBUG" in "Developement" setting's
7)Download "init.engdo.post_boot1.sh" and place it in C:
6)Download and open Permanent_D605_KK_Root_Part1.bat
7)Open "Total Commander" , go into /system/etc/ , delete the original "init.engdo.post_boot.sh" and rename "init.engdo.post_boot1.sh" to "init.engdo.post_boot.sh"
8)Download and open Permanent_D605_KK_Root_Part2.bat
9)Enjoy
If anybody will ask for it, i'll upload a standalone .exe to do all this
P.S: I'm kinda new to XDA and English is not my motherlanguage, sorry about any mistake i could've made
Click to expand...
Click to collapse
When i try to push file init.engdo.post_boot1.sh with root_part1.bat CMD says: remount failed: Permission denied or failed to copy C:/init.engdo.post.boot1.sh to /system/etc//init.engdo.post_boot1.sh : read-only file system
Much easier instruction.
Most of the instruction in the first post is unnecessary.
1) you do NOT need any computer at all
2) no USB debug needed (because you do not need a computer)
3) two .bat files are also unnecessary to download
All you have to do is to replace init.engdo.post_boot.sh file, which resides in /system/etc
You DO need:
1) towelroot installed
2) a file manager with root capability (I used Root Explorer for example)
Instruction:
1) download the init.engdo.post_boot1.sh, using the link in the first post- download it to your phone SD
2) open the file manager with root permissions enabled, /system/etc must be accsessible for read/write
3) copy init.engdo.post_boot1.sh to /system/etc (using the file manager running on your phone)
4) delete init.engdo.post_boot.sh in /system/etc
5) rename init.engdo.post_boot1.sh that you copied to /system/etc to init.engdo.post_boot.sh
6) reboot
All this is great! But, you forgot one important thing:
TOWELROOT does not work on version 20D (which is increasingly represented)
But here you have an explanation for v20D so who wants to try:
http://forum.xda-developers.com/opt...4-4-2-v20a-t2964723/post57308650#post57308650
forgetting...
I did not know the 20D issue so I also could not have forgotten it.
Thanks for info. I just checked, indeed, I have 20A. Towelroot and the permanent root trick work in my case.
Thanks for the feedbacks
I know it can be done more easily using a file manager on the phone, but i tried to make the process easier for newbies (I'm still a newbie too, i did it for myself because i was lazy, but i decided to post it , hoping to help someone )
All this is great! But, you forgot one important thing:
TOWELROOT does not work on version 20D (which is increasingly represented)
But here you have an explanation for v20D so who wants to try:
http://forum.xda-developers.com/opti...0#post57308650
Click to expand...
Click to collapse
Thanks koxyman88, i didn't know about that
When i try to push file init.engdo.post_boot1.sh with root_part1.bat CMD says: remount failed: Permission denied or failed to copy C:/init.engdo.post.boot1.sh to /system/etc//init.engdo.post_boot1.sh : read-only file system
Click to expand...
Click to collapse
Mmmm strange, are you sure you have SuperSU installed, and TowelRoot started before restarting? (TowelRoot's Root disappear after reboot, and so SuperSu binaries)
the question is ... WHY?
I want to point out that I did permanently root my D605 with KitKat. Took a bit of effort but actually it was wasted time.
I did finally go back to 4.1.2 software, rooted it, installed TWRP and then Varcain's modified Cyanogen 11. It is so much nicer than rooted stock 4.4.2. All the efforts of rooting Kitkat and keeping the root were unnecessary exercise.
Because the Varcain's image does not have any bloatware I could even switch from Dalvik to ART and still have enough free space on phone.
I rooted my strange tablet using Kingo and apparently it was succesful:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-20_zpsurdgzj8p.png
But I have been trying for days to erase a file in /system and I have not been able to do it, I think I have read every relevant thread about this problem but no luck, I tried using ES and changed /system to r/w in the root options but when trying to delete the file all I get is operation failed, the same happens with all the other root explorers and tools. I even tried the solution on this thread: http://forum.xda-developers.com/ascend-p7/help/edit-replace-write-files-set-immutable-t2884172
but still can't delete it.
Also the app root toolkit for android gives me this weird error too:
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-06_zps4nrxqiev.png
http://i1312.photobucket.com/albums/t539/talos910/Screenshot_2015-09-11-17-08-02_zpsa1ycwdwl.png
Do you have an app like root explorer that specifically asks for root permissions? It doesn't matter if you have root if the explorer can't use it
Sent from my Nexus 5 using Tapatalk
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Try installing root explorer and then attempt to delete the file, then it should instantly open a window asking for root. The of course grant the permission. That should always work, but if it doesn't just restart the tablet, if it still doesn't work it must mean you are deleting a file that is in use by the system. Otherwise i have no idea whats wrong
Sent from my Nexus 5 using Tapatalk
Talos91 said:
Yes all the file manager apps I used always ask for root permission, that is the problem they have root permission but still can't delete the file, which is weird because I can use apps that definitely need root like scr screen recorder and greenify just fine.
Click to expand...
Click to collapse
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
JMink said:
What recovery did you install...twrp, cwm, philz?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Rooted my device using kingo root, I didn't intall other recovery.
Bad idea to try and remove system files without a custom recovery and a nandroid backup made and stored in a safe spot. What are you trying to remove?
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Talos91 said:
I am trying to delete /system/sbin/su because I read in another thread this was the solution to fixing the issue of the app supersu not updating binaries when rooting your device using Kingo.
Click to expand...
Click to collapse
That is the binary. If you remove it, you wouldn't be rooted. Can you link the thread you are looking at? There's an app made specifically for replacing that su binary with SuperSU and it's binary called Super-SUme, though I believe it is a paid app.
I know it is the binary but according to this guy:
http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365/page23
(post 223)
""It appears kango wrote to /system/sbin/su whereas supersu wrote /system/xbin/su and subsequently supersu would keep wanting to update 'su' then fail.
The long and the short of it is once I manually removed /system/sbin/su supersu stopped telling me 'su' was outdated. I don't know android but I do know linux.
$PATH on my tablet has /system/sbin/ prior to /system/xbin/ so it would appear supersu is issuing 'su -V' as opposed to '/system/xbin/su -V' when it checks the version. The kingo 'su' was older than the supersu 'su'.
Dunno what the solution is 'cos the older 'su' is going to get called first & I figure there's nothing but trouble to be gained from changing $PATH globally. Nevertheless it might be enough to check $PATH for unwanted 'su' and flag them, possibly offer to remove them? In my case I renamed it "/system/sbin/su.ORIGINAL" so that it's still runnable in an emergency"""
If you rename it, it won't be able to run, and won't require removal.
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Talos91 said:
That's the thing I can't rename the file either for some reason. Using es and other root explorers doesn’t work.
Click to expand...
Click to collapse
Seems like the SU binary that Kingroot included is pretty finicky and only works for some things. I've rooted 100s of devices and have never had issues like that. Have seen complaints about other various oddities with Kingroot too. It's nice that it's easy and works on a variety of devices, but if you have only limited control then that kind of defeats part of the purpose of rooting it...
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
With Root Explorer, does it let you set the system to R/W? There's a little button at the top of the app that will say R/O or R/W for Read Only or Read Write. If you don't have R/W to the system, then you are unable to make changes to it.
I just renamed file su and then it became able to be deleted.
Talos91 said:
Tried using SuperSUme but the app says I am not rooted with Kingo? wtf? Do you guys know of any other reason why i can't erase the system file sbin/su?
Click to expand...
Click to collapse
Connect your android tablet device to your windows computer. Then enable usb debugging on your android tablet. Then open the windows program called cmd. Then do these commands.
Code:
adb root
Code:
adb remount
Code:
adb shell rm /system/sbin/su