Disclaimer: rooting your phone entails risk. You may brick it, cause it to catch fire, cause it to form the first node in the Skynet network, or otherwise render it inoperable. Please read the directions carefully to ensure that nothing unexpected happens. This rooting tool is as safe as I can make it, but there's never any guarantees.
After a very helpful suggestion from Surge1223, I managed to take an existing root exploit for the Xperia and modify it to work on 4.3 with SELinux enforcing. This installs su, SuperSU, and the necessary support files to enable the root.
This rooting process should work with a wide range of Android devices, particularly those running Linux Kernel before 3.5.5 (which most Android 4.3 ROMs use.) It 's known to work for may GS4 variants and is harmless if it fails to work (no "Warranty Void" flags get set.)
Again, using this WILL NOT set the "Knox Warranty Void" flag.
For a video showing the steps to root, see Tomsgt's awesome work here.
There's another video from owenbeals here.
A hint to people having problems using this:
If you use XDA to e-mail me a question, SET YOUR XDA ACCOUNT UP TO ACCEPT MAIL.
If you are set up to refuse mail, then your question will be ignored. Actually, you shouldn't e-mail me. PM or post here.
Step 1 - setting up the USB drivers
Before you try using this rooting program, you'll need to have the USB drivers installed for your phone.
The easiest way to do this is to install Samsung Kies. If Kies sees your phone, you're OK for the drivers.
If you don't have the drivers working, the root installer will hang at "waiting for device..."
Step 2 - Enable USB Debugging
The second thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled.
In Developer Options, make sure "USB Debugging" is checkmarked.
Step 3 - Enable USB ADB Access
Make sure that your computer is allowed to use USB debugging on your phone. To do this, unplug your phone and unlock it. Then, plug in the USB cable.
If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK.
If you don't see that popup, it's OK, you should be OK to proceed.
That's it for the phone.
Step 4 - Unzip the saferoot.zip
Then you need to unpack the attached ZIP file somewhere onto your PC.
You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
Step 5 - Root your phone
Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed.
If SuperSU asks you to update the su binary, choose the "Normal" method.
If SuperSU asks you about disabling Knox, allow it.
This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about.
While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone.
You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
Rooting on Linux and MacOS
The saferoot script has a copy of adb for MacOS and for Linux included.
To run this root, download and unzip the zip file. Open a shell window, use "cd" to change to the directory where you unpacked the zip, and type "sh ./install.sh". The OS will be detected automatically and the root should run basically as described above.
If the embedded adb fails, you'll need to have the Android Debugging Bridge (adb) installed and configured and on your path. You can test that it's ready by opening a shell (Terminal) window and typing "adb shell". If you get a shell prompt on the phone, type "exit" and you're ready to go.
Notes
Don't try to download this onto your phone and run it from there. That won't work, at least for the i545 (i.e. running it from the Terminal Emulator app will fail.)
Having troubles getting adb connected? There are several possible causes and solutions.
There are cases where people can't get the connection working unless they toggle the USB connection type from Camera to Media and back. Perhaps that may help getting it to work. Toggling the "Enable USB Debugging" apparently helps in some cases as well.
Others report that using these Samsung USB drivers resolve connectivity issues. Of course, these drivers are for Samsung phones. Install the right stuff for your phone.
Important - please read
If you fail to read this, you will be taunted.
1. You can't install custom recovery and custom ROMs on a phone with a locked bootloader. This rooting program does not unlock your bootloader and won't allow you to flash custom on a locked device. However, NOTHING allows flashing a custom recovery on a bootloader locked phone at the moment. See Safestrap for a way to install some custom ROMs.
2. Resetting the "Custom" and open padlock indication during boot can be worked around using the Xposed Framwork and Wanam Xposed. Get those two from the Play Store. In Wanam, tick "Security Hacks", "Fake System Status".
3. If Saferoot fails with the messages
"Your kernel is patched!
This device is not supported."
That means that your device's Linux kernel has been updated to keep Saferoot from working. Unless you can downgrade to an older kernel, you can't use Saferoot.
Reported Successes
Here's a list of phones and reported builds where this has been verified to work.
AT&T Galaxy Note 2 (SGH-I317), Android 4.3
AT&T Galaxy S3 (SGH-i747), MJB
AT&T Galaxy S4 (SGH-i337) MK2,MK6
AT&T Galaxy S4 zoom
Bell Mobility i337,MK6
Canadian Galaxy S4 SGH-I337M
Digicel (Jamaica) i9500, MK1
d2vzw s3 with the 4.3 update
Galaxy NX Camera, JDQ39
Galaxy Legend SCH-I200,MK2
Galaxy Note 2 GT-N7100, MK9
Galaxy Note 2 N7105 4.3
GT-I9192, MK4 (ML2 does not work)
Google Glass, (XRT73B), XR14
i605
International Galaxy S4, I9505: MH6, MH8, MJ5, MKE, MKF
I9500: MJ8, MK1
Kindle Fire HD
LG Optimus F3 - T-Mobile
LG Escape -P870 - ATT
MK4 Build Date 13.11.2013
Razr HD 9.30.1 OTA
Razr M 98.18.94,98.30.1
Samsung Exhilarate SGH-I577, Android 4.0.4, Build LH3
Samsung GT-I9192, UBUBMK4
Samsung Galaxy Tab 2 GT-P5513
Samsung Galaxy S4 Mini LTE (GT-I9195), MJ7
Samsung i547, Android 4.1.2
Sprint Galaxy S3 (SPH-L710), MK5
Sprint Galaxy S4 Mini SPH-L520
Sprint Galaxy S4 SPH-L720,MK2 (NA2 does NOT work)
Sprint Galaxy S4 (SPH-L720T), MK5
T-Mobile Galaxy S4 SGH-M919 JFLTETMO, MK2
T-Mobile Galaxy Note 2 SGH-T889, MK7
Telcel (Mexico) SGH-i337M, MK6
Telus Note 2 SGH-I317M
Verizon Galaxy Note 2 Android 4.3
Verizon Galaxy S3 I9300 - LF2
Verizon Galaxy S3 SCH-I535
Verizon Galaxy S3 Mini, SM-G730V, MI9
Verizon Galaxy S4 (SCH-i545) ME7,MJ7,MK2
Verizon Galaxy S4 (SCH-i545L) MG6, MK4
Verizon Galaxy S4 Mini SCH-I435, MK5
Verizon Galaxy S4 Developer Edition, I1545OYUAMDK
Verizon HTC One
Verizon SCH-I200PP, MK2
xt907, xt925/6 & mb866
Edits:
12/12/13: This version of the zip file includes the adb.exe so you don't need to install ADB just for this.
I've also changed it so you shouldn't have to unzip to any special place.
12/13/13: I've swapped out Superuser for SuperSU. This version also installs busybox for you once the phone finishes rebooting.
12/14/13: Fixed install of busybox. Install SuperSU as Chainfire wants it: called Superuser.apk, installed into /system/app.
12/14/13: Move "Look at your phone and give permission" message to the top of the script.
12/15/13: Update source distribution to correspond to updates.
12/16/13: Rename to saferoot as it's not just for MJ7.
12/17/13: Update to fix "text file busy" errors
12/18/13: Correct the "text file busy" fix. Force su binary to be setuid root so root checkers will work.
12/18/13: Add more help in the "install.bat" for people having troubles getting adb working
12/18/13: Ensure the folder setup is right when starting install.bat
12/18/13: Give users time to allow su permissions
12/21/13: Disable SEAndroid before rooting
12/22/13: Install selinuxoff to set SELinux to Permissive mode at boot
12/23/13: Fix permission on selinuxoff binary, update SuperSU install and clean up rooting program
12/30/13: Remove selinuxoff program - it doesn't do anything. Updates to the install scripts.
1/6/14: Hard code kernel addresses for ATT Galaxy S4 so it takes less time to root.
1/6/14: Try to work around Knox deleting the su binary
1/10/14: Clear immutable bit on existing programs to allow them to be updated
1/12/14: Update to current SuperSU binary
1/13/14: Updates suggested by @bgmg
1/16/14: Correct typo in Linux/OSX installer
1/21/14: Really correct the typo. Add OS detection to install.sh so it can run on OSX or Linux without installing adb.
1/21/14: Update to current SuperSU
2/4/14: Detect when the phone is not rooted and don't continue the rest of the operations.
3/29/14: Install 'unroot' script and add unroot.bat/unroot.sh to allow simple removal of Saferoot changes.
4/4/14: Fix problem with unroot not running
4/30/14: Clearer error messages on root fail, allow user to choose installation of busybox
5/14/14: Fix typo in Unix install script, more text on why it failed.
5/24/14: Fix install.sh portability issue with double equals on test.
Source code, Unrooting, and the Custom Flag
The source code for the exploit tool used for this rooting method is attached.
In addition, two common questions:
1. How do I unroot?
OK, so why are you so anxious to unroot just after rooting?
If you have used the current version of Saferoot to root your phone, then there's an unroot script installed to make this easy.
If you still have Saferoot unzipped, plug in your phone and use "unroot.bat" (Windows) or "unroot.sh" (Unix) to remove the changes that Saferoot made. Then, open SuperSU and instruct it to perform a "full unroot". After that, all changes that Saferoot have made to your device have been removed.
If you don't have the unroot.sh, then you can unroot manually as below.
There's two things you need to do to undo what this installer does. First, remove busybox. This will require adb shell or the use of Terminal Emulator to get a shell prompt. Execute the commands below at a shell prompt.
The "$" and "#" characters at the start of those lines are the system prompt. You don't type those.
Spacing, case, etc. matter. The letter after "type" in the "find" command is a lowercase L.
$ su
# mount -o remount,rw /system
# rm -f /system/etc/install-recovery-2.sh*
# rm -f /system/xbin/selinuxoff*
# find /system/xbin -type l | xargs rm
# rm /system/xbin/busybox
# mount -o remount,ro /system
# exit
$ exit
The easiest way to do this is to install the "Terminal Emulator" app from the Play Store. Or use "adb shell" to get a shell prompt.
You can cut and paste the following to make it easier.
su
mount -o remount,rw /system
rm -f /system/etc/install-recovery-2.sh*
rm -f /system/xbin/selinuxoff*
find /system/xbin -type l | xargs rm
rm /system/xbin/busybox
mount -o remount,ro /system
exit
exit
Click to expand...
Click to collapse
It's very likely that the "/system/xbin/selinuxoff" and "/system/etc/install-recovery-2.sh" files won't be there.
Now, open SuperSU and use "Settings", "Full unroot". When that's done, everything that this installer has done has been reverted.
If you've installed xposed framework or wanam, you should remove those and reboot BEFORE doing the SuperSU unroot. Also, if you've installed Safestrap you'll need to boot into SS recovery, delete the custom ROM slots, then uninstall Safestrap recovery. Or, uninstall the Safestrap application. If you forget to do these before doing the SuperSU unroot, you'll need to re-root to do those.
If you need adb to access your phone, there's a copy in the "files" directory included with the installer. You'll need to open a command prompt and use cd to change to the files directory before trying to use that adb.
2. How do I get rid of the "Custom" padlock open screen at boot?
You get that because you're running custom software. Samsung has an application that runs at boot to look for modified system files; this app detects that the phone has been modified and sets that flag.
If you really need to get rid of that, you can do the unroot in #1 above, then reboot. Wait about 10 minutes or so, then reboot again. If you haven't changed any other system files, the custom flag should have been reset.
If that doesn't fix it, flash the stock no-wipe ROMs from this forum. Those will undo whatever you've changed and allow the phone to reset the custom flag.
If you want to keep root while getting rid of that "Custom" flag, then you can fake it. Install xposed framework (google for it), enable it, then reboot.
Then install Wanam Xposed, and enable that module in xposed.
In Wanam, choose "Security Hacks", "Fake system status".
That will keep the "Custom" flag from appearing. This is a cosmetic fix, but it does get rid of the "Custom" screen.
Other devices?
There is really nothing specific to the I545 or MJ7 in this root tool. There's a good chance it'll work on anything currently running 4.3.
If you have success with other devices, please reply to let us know.
Im glad I could help and good work! Im sure this will work with MK2 too.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Im glad I could help and good work! Im sure this will work with MK2 too.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup. I'd say that it's almost certain.
Script did not work for me. I think there is a problem with the script or the zip.
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Oozura said:
Script did not work for me. I think there is a problem with the script or the zip.
Click to expand...
Click to collapse
Which of the two scripts? What error did you get?
I'll be happy to fix if you'll provide some details!
I can confirm this works on ME7 just in case anyone is wondering, Im pretty sure it can easily work on any build we have so far. Might require minor modification but for the most part, this is solid.
sharkie405 said:
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Click to expand...
Click to collapse
As far as lingering malware on the phone, the only thing you could do would be to flash a full-wipe factory image then root it when done.
I don't know if it's worth the hassle or no. If it was me, I'd be wiping, but I put the effort in to make this happen since I couldn't accept the closed-source risk with vroot.
sharkie405 said:
Suppose there is something actually malware-ish about vroot or kingoroot, would that be something that could be "undone" so to speak by unrooting? As in, I've already rooted via both of those other methods at different times. Should I unroot to stop whatever they "may" be doing and then try and root via your method? Or is there really no point now that I'm already rooted?
Click to expand...
Click to collapse
Sharkie, I'm new to S4, but I've been reading for decades & decades & saw a reference to a youtube video by Sgt tom (not sure of the name, but…) you can search for titles there relating to rooting S4, & it shows how you can install kingo root to obtain the exploit, do some stuff (don't recall, it may just be deleting that)… & installing Super SU in it's place or over that.
So do a little searching on root & s4 in youtube & invest some time… sorry, not sure if that was all meant for a diff version of the firmware; but it is worth looking into to use the kingo's exploit & then immediately replace it.
Don't know about the issue w/kingo is malware, or 'just' that it harvests your meid &/or other personal info, but there is a way to use it & replace it if you are OK with that approach…
Sorry I don't have specific references, but I just got into this since 'Grey Thursday' sale @ Staples, early start on Black Friday sales… hth,
oldwolf
First off... THANK YOU SO MUCH!
I did this method by putting it on my sd card... and it went through and told me to reboot. but upon reboot i have no custom splash screen and no su. i will try again tho.
I think I'm doing it wrong? Can someone help my dumb ass. Lol or I can just to adb. Either way haha.
Sent from my SCH-I545 using xda app-developers app
Craleb said:
I think I'm doing it wrong? Can someone help my dumb ass. Lol or I can just to adb. Either way haha.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Try the adb method first then if you get a failure message try the install.sh method from terminal again. After the script is done type "su". See if that works
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Try the adb method first then if you get a failure message try the install.sh method from terminal again. After the script is done type "su". See if that works
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same results as the poster before you. I tried using adb method, and the prompt said adb couldn't be found.
Anybody want to confirm this works? I just updated to MK2 right now and want to try but would like another confirmation first.
Ugh I have adb setup and everything... but my freaking phone will not go into debug mode. Even after restart. I have debugging checked in dev options. It just "connected as an installer" then MTP
Sent from my SCH-I545 using xda app-developers app
Thanks for working on this. Copy of errors running script run in terminal emulator attached.
on MK2 and got the same output as Jiggity
Sent from my SCH-I545 using XDA Premium 4 mobile app
Related
hi. i can't believe i'm the first person to ask this but i've searched as best i can through these forums, and on google, and cannot find a definitive answer. there are lots of pages giving high level descriptions of rooting a phone like "gives admin access", "allows access to the root filesystem", etc. but, when you root a phone, what actually happens ? does it simply make the "su" binary available so that apps can call it to access the root user ? eg. i've got a samsung galaxy s2, if i install an insecure kernel, then add su to /system/xbin, and then reinstall a stock kernel, is that technically a rooted phone ? this is actually what i did on my phone, although i installed superuser and busybox from the market after adding su. i am aware that there are various threads in the sgs2 forums on how to root, i'm just using my phone as an example, i'm just trying to understand generically what is meant when someone says a phone has been rooted. cheers.
Full control over your system
Ability to alter system files. You can replace many parts of the "Android Core" with this including:
Themes
Core apps (maps, calendar, clock etc)
Recovery image
Bootloader
Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
Boot images
Add linux binaries
Run special apps that need more control over the system
SuperUser (lets you approve or deny the use of root access to any program)
Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
<there are more but I cannot think of any right now>
Backup your system
You can make a folder on your sdcard and backup all of your .apk files to your sdcard (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
Relocate your (browser/maps/market) cache to your /sdcard
Relocate your installed applications to your /sdcard
Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Copied and pasted from google... it is your friend.
thanks for the response however, i'm trying to understand what actually changes on the phone when you root it, rather than simply the benefits of rooting a phone.
Carrot Cruncher said:
thanks for the response however, i'm trying to understand what actually changes on the phone when you root it, rather than simply the benefits of rooting a phone.
Click to expand...
Click to collapse
Unrooted phone is like logging on as user in a computer. By rooting you have "administrative" rights, just like using sudo command in Ubuntu. Some binaries which are important in gaining administrative rights are installed in the phone.
sent from my nokia 3210
If you come from Windows, you're familiar with the Administrator account. A user that can do everything on the system, as opposed to other users than only have limited privileges. In Linux, that account is called "root". That's all there is to it. It's a user that can do everything on the system.
@Panos_dm: Actually, it's *not* like using sudo. Sudo gives elevated privileges to your existing user account, whereas "root" is a whole separate account.
Nope, sudo actually switches users
i'm a linux user and have been a linux admin in the past so understand the difference between su and sudo. sorry to sound pedantic but i'm still not clear on exactly what happens when you root a phone, i.e. what exactly happens during the rooting process ?
It opens your phone to a whole new array of possibilities.
Sent from my HTC Sensation 4G using xda premium
Carrot Cruncher said:
but i'm still not clear on exactly what happens when you root a phone, i.e. what exactly happens during the rooting process ?
Click to expand...
Click to collapse
In a gist? The "su" binary and the Superuser.apk app get installed. Sometimes doing so requires exploiting a vulnerability via a trigger. Rageagainstthecage is a common trigger. I once had a link that explained what exactly rageagainstthecage does, but I don't have it anymore.
If you really want to know all the details, here's the script I used to root my Defy: http://pastebin.com/G3m9v4FQ
Hmm, I see the script contains a link to the explanation of what rageagainstthecage does. Cool.
many thanks for confirming my understanding of the process.
Hello Archos community,
I have bought the new Archos 50c Neon in early July, because of its nice price-performance ratio and the fact that it runs Android 4.4.2.
I have been able to successfully root it using Chinese "KingRoot", but am looking for an alternative SuperUser app. I already own a license of SuperSU Pro (which I am using for my tablet), but it turns out that the current versions of SuperSU (both 2.46 and 2.49) currently cause a crash when calling "su" from adb - seemingly because the Dalvik VM is unable to instantiate class "android.os.Environment" from SuperSU code when SuperSU wants to display its UI dialog that asks for permission. For the detailed issue description, please see here:
My thread in XDA SuperSU forum: Crash when trying to run su
Unfortunately, Chainfire (the author of SuperSU) from his signature is "away for most of the summer", and I will wait until he's back and then point him to this issue one more time.
In the meantime, I have created a script to successfully remove all remains/remnants of KingRoot (after successful rooting with it) and replace it by Koushik Dutta's OpenSource Superuser package:
https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
http://www.koushikdutta.com/post/superuser
I have attached a ZIP file to this post that includes everything needed to do so - here are the instructions:
Please note that I do not take any responsibilities in case you brick your device, and also note that you void your warranty for the phone when rooting (these should be clear anyway)!
Reset your Neon 50c to factory settings (optional, might be needed in case you run into issues otherwise when removing KingRoot)
Unzip the attached ZIP and copy its contents to the root of the internal SD storage on your 50c Neon (directory /sdcard)
Use the included kingroot_4.0.0.apk to root your phone (allowing to install apks from untrusted sources)
Then, from your PC, open an "adb shell" to your device (you need to activate developer mode and USB debugging in order to do so)
From this adb shell, execute "su" and allow this root access through the KingRoot dialog on your phone. You now have a root shell on your phone.
Open a second adb root shell in the same way to not become stuck in case something goes wrong with the first one
In the first adb root shell, cd to /sdcard and execute my script in the following way:
Code:
cd /sdcard
sh -x ./kingroot_2_koush_su.sh ./busybox ./superuser.zip
and while it is running, press enter three times when "ps | grep king" and "ps | grep k_" show whether there are still processes running on your device that are related to KingRoot. General rule here is: When there are processes still running for the first ("ps | grep king"), something went wrong and KingRoot uninstall will most probably fail, while the fact that only processes matching the second ("ps | grep k_") are found, is normal and will NOT stop the script from working successfully.
When the script has finished, your phone will do a "soft reboot" (from killing zygote). You should do another explicit "hard" reboot afterwards anyway before trying to use the newly installed Superuser package.
I have run this script myself on my device, and am pretty confident that after the script has run successfully, there are no remains/remnants of KingRoot left on my device. The Open Source Superuser app by Koushik Dutta runs without any issues.
Hope this helps - and am still looking for some help with why SuperSU crashes on the 50c Neon although it seemingly has been installed properly...
Best regards,
awl
Great work, thank you very much for sharing this. :good:
I have just successfully followed your instructions and they worked for my new Archos 50c Neon as well.
Just one remark concerning the Kingroot (as the app was confusing me with Chinese that I could not read): Make sure to turn your wifi on before you start Kingroot, otherwise the app won't do anything.
And now my questions:
Do you by any chance know if there is a custom recovery available for the Archos 50c Neon? I haven't found any.
Have you written a debloater script which uninstalls all uninstallable apps?
do you have a custom recovery for this phone as I cannot get the su to up date without it restarting into recovery for the clockwork mod superuser. I have got root but only if i set supersu to grant rather than prompt but this isn't a very secure way as you said the su binary is there but the system isn't allowing the prompt.
Da5t3rati0n said:
do you have a custom recovery for this phone as I cannot get the su to up date without it restarting into recovery for the clockwork mod superuser.
Click to expand...
Click to collapse
AFAIK there is no custom recovery for this phone. I don't own it any more, it had too many weak points, such as most promintently speech quality/microphone and frequent hangups or no sound for one party during 3G telephony.
Sorry & best regards,
awl
awl14 said:
AFAIK there is no custom recovery for this phone. I don't own it any more, it had too many weak points, such as most promintently speech quality/microphone and frequent hangups or no sound for one party during 3G telephony.
Sorry & best regards,
awl
Click to expand...
Click to collapse
Yes first thing I noticed about this phone was the call quality haven't had any dropped calls though also the touch screen is awful only 2 touch. Reasonable hardware though CPU is a spreadtrum 1.2ghz a7 quad core so runs cooler and more energy effient than the a9 with a mali400 mp2 twin core GPU runs Asphalt8 on decent settings and good frame. But sadly let by the touch screen as for SuperSU it roots the phone and if set to grant, root programs run so the problem is with the prompt not being allowed to show. I'm thinking this is more Google security than anything.
Sent from my Bush 5" Android using XDA-Developers mobile app
If you was one of those who root their devices by using KingRoot App and would like to remove kinguser and related files, you can replace it with the well known SuperSU.
Here's a small script to remove Chinese kingruser, all related files and folders, and install SuperSU.
This script will do all the work for you without using PC, just by terminal, first of all, thanks to chainfire for his SuperSU files.
Before starting :
Download and install Terminal emulator appTerminal emulator app
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Download and unzip "Replace_Kingroot_With_SuperSU.zip
http://tiny.cc/fo78zx
Steps :
Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
Open Terminal emulator and type :
"Su" (without "")
Allow root permission
Type :
" sh /sdcard/mrw/root.sh" (without "" , notice there's space between sh /sdcard.)
It might display some error, but wait for 30-40 seconds and at the end it will launch supersu or open supersu manually.
Update su binary normal, then reboot.
Done !
I ran the script and it went thru to installing Super Su but I lost root and couldn't update binaries. I redownloaded King Root and opened it and I instantly had root back. Are there other files that King Root has installed that don't allow this script to work. If you have any insight it wouldbe appreciated. I know I am on a different phone but script seems to work up to a point. ZTE Z820 Android 5.1 Thanks
I can confirm this method works on Lenovo Vibe X2 running Android 5.0. New Kingroot 4.5, the one with crown icon, successfully replaced by SuperSU while root status remain intact. A process crashed upon Kingroot removal, however restart seemed to get rid of the problem.
Peacekeeper888 said:
I can confirm this method works on Lenovo Vibe X2 running Android 5.0. New Kingroot 4.5, the one with crown icon, successfully replaced by SuperSU while root status remain intact. A process crashed upon Kingroot removal, however restart seemed to get rid of the problem.
Click to expand...
Click to collapse
May I ask did you have busybox already downloaded and installed? I see that the zip contains busybox as one of the actions of the script. Maybe that's why it didn't work for me?? Also I have Kingroot 4.9.2 and I'm thinking that is the main reason the script fails for me.
Jsmor1313 said:
May I ask did you have busybox already downloaded and installed? I see that the zip contains busybox as one of the actions of the script. Maybe that's why it didn't work for me?? Also I have Kingroot 4.9.2 and I'm thinking that is the main reason the script fails for me.
Click to expand...
Click to collapse
I had KingRoot v.4.85, on a KitKat 4.4.
The script didn't work, so I plug the phone and connected to the computer, opened a console, executed the adb shell command and start to give each of the script commands manually one by one.
The failure was at pm uninstall com.kingroot.kinguser (com.kingroot.RushRoot wasn't installed anyway).
The packet manager wasn't able to uninstall Kingroot. I had to uninstall manually using the phone
Code:
H:\Development\adt-bundle-windows-x86-20140702\sdk\platform-tools>adb shell
[email protected]_z10:/ $ su
[email protected]_z10:/ # mount -o rw,remount /system
[email protected]_z10:/ # am kill com.kingroot.RushRoot
[email protected]_z10:/ # pm uninstall com.kingroot.RushRoot
Failure
[email protected]_z10:/ # am kill com.kingroot.kinguser
[email protected]_z10:/ # pm uninstall com.kingroot.kinguser
Failure
In the end the replacement was successful
details of manual uninstall
halnovemila said:
I had KingRoot v.4.85, on a KitKat 4.4.
The script didn't work, so I plug the phone and connected to the computer, opened a console, executed the adb shell command and start to give each of the script commands manually one by one.
The failure was at pm uninstall com.kingroot.kinguser (com.kingroot.RushRoot wasn't installed anyway).
The packet manager wasn't able to uninstall Kingroot. I had to uninstall manually using the phone
Code:
H:\Development\adt-bundle-windows-x86-20140702\sdk\platform-tools>adb shell
[email protected]_z10:/ $ su
[email protected]_z10:/ # mount -o rw,remount /system
[email protected]_z10:/ # am kill com.kingroot.RushRoot
[email protected]_z10:/ # pm uninstall com.kingroot.RushRoot
Failure
[email protected]_z10:/ # am kill com.kingroot.kinguser
[email protected]_z10:/ # pm uninstall com.kingroot.kinguser
Failure
In the end the replacement was successful
Click to expand...
Click to collapse
I have rooted my phone (Android 5.1) with kingroot 4.8.0, I also want to remove KingRoot and replace it with supersu.
I plan to execute the script line by line via an ssh session as root on my phone.
finally how have you uninstalled Kingroot manually ?
fabp said:
I have rooted my phone (Android 5.1) with kingroot 4.8.0, I also want to remove KingRoot and replace it with supersu.
I plan to execute the script line by line via an ssh session as root on my phone.
finally how have you uninstalled Kingroot manually ?
Click to expand...
Click to collapse
I modified the script in this way:
After
Code:
pm uninstall com.kingroot.kinguser
I've added
Code:
am start -a android.intent.action.MAIN -n com.buak.Link2SD/.Link2SD
echo "Press any key to continue"
read typedkeys
The first of the three added rows launches Link2SD app (that I've installed on my phone since I rooted it); the last line pause the script execution.
I used Link2SD to uninstall Kingroot.
Anyway I have to say that, even though the installation of SuperSU seems completed without errors, the apps that asks for root permissions didn't receive the answer from SuperSU and they aren't granted root permission, so... it still doesn't work.
it did not work, superSU can not update binary and can not uninstall the other root app (kingroot)
guys,I am telling you a working method which worked for me..
but you are going to need some version specific apps for first time..
things you need...
1. clean MICROMAX a311
2. kingoroot KingRootSetup_v3.2.0.1129 (i can upload it if you want)
3. Supersume.apk {MUST BE VERSION 6.4} (application used to change from kingroot to supersu)
note -- Pay attention to versions,messing with them will not allow you to achieve target.
steps..
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
[email protected]_Rocker said:
guys,I am telling you a working method which worked for me..
but you are going to need some version specific apps for first time..
things you need...
1. clean MICROMAX a311
2. kingoroot KingRootSetup_v3.2.0.1129 (i can upload it if you want)
3. Supersume.apk {MUST BE VERSION 6.4} (application used to change from kingroot to supersu)
note -- Pay attention to versions,messing with them will not allow you to achieve target.
steps..
1. install kingrootsetup on pc(must have internet connection to work)
2. connect ur phone with ADB enabled from developers option
3. root ur phone by following on screen instructions...
4. after rooting,install supersume on phone
5.open the app,click on big blue button and wait...
done,replaced kingroot with supersu..
Click to expand...
Click to collapse
Hello can someone give me a link to supersume 6.4apk please
Thanks
2010radams said:
Hello can someone give me a link to supersume 6.4apk please
Thanks
Click to expand...
Click to collapse
sure....it will be my pleasure.
ok !
download from attachment and install,then get rid of kinguser...:good:
[email protected]_Rocker said:
sure....it will be my pleasure..BTW it can be used on ANY phone to replace kinguser with supersu..
ok !
download from attachment and install,then get rid of kinguser...:good:
Click to expand...
Click to collapse
Just used this solution on a Vodafone Tab speed 6 (VF-1397).
Seemed to work fine but after updating superSU and rebooting the Tablet, screen went black when boot reached unlock screen and couldn't see or do anything except using the power button options.
After some reboots (lost count, ~5/6, and failed atemps to enter recovery), (and the removal of the sim card) the tablet finaly started to optimize all my apps as if the dalvik cache had been wiped.
Afterwards screen went black again and couldn't do anything again.
After some time was finaly able to enter recovery and i'am now trying to format everything.
Subray said:
Just used this solution on a Vodafone Tab speed 6 (VF-1397).
Seemed to work fine but after updating superSU and rebooting the Tablet, screen went black when boot reached unlock screen and couldn't see or do anything except using the power button options.
After some reboots (lost count, ~5/6, and failed atemps to enter recovery), (and the removal of the sim card) the tablet finaly started to optimize all my apps as if the dalvik cache had been wiped.
Afterwards screen went black again and couldn't do anything again.
After some time was finaly able to enter recovery and i'am now trying to format everything.
Click to expand...
Click to collapse
Sorry to hear that...
can you tell how you were UPDATING supersu ??
i also updated from 2.4.5 to 2.6.5 without any problems...
were you using genuine zip of supersu meant for your device ??
or just regular zip ??
don't you have backup of your tab....you were rooted..
1st thing you were to do was to make a full backup...why didn't you did that ??
Script didn't work for me, tons of errors because the path wasn't right. Fixed it to have exactly the same but still plenty of errors and SU binary would not update.
That supersume.apk thing though... MAGIC!!
Thanks heaps!!!
Device reboots
Any idea why the device reboots when I press enter at the last command? I did everything correctly, step by step like you describe it but instead of replacing the KingRoot with SuperSu the device reboots and the KingRoot is still there.
The device is Sony Xperia SP (C5303)
Any help would be great cause I used the exact same method some time ago in my tablet (Lenovo A8) and it worked perfectly. But not in the Xperia and I don't know if I should fully unroot it and try a different method or what.
Sahilsinghlodhi said:
If you was one of those who root their devices by using KingRoot App and would like to remove kinguser and related files, you can replace it with the well known SuperSU.
Click to expand...
Click to collapse
All is done how you describe, everything was just fine and now I have a Lenovo S850 with android 4.4.2 rooted with SuperSU Free 2.78
Thanks a lot.
Does it also work with Kingsroot 5?
Lemmi1 said:
Does it also work with Kingsroot 5?
Click to expand...
Click to collapse
I tried on kingroot 5, no success then unistall kingroot and try kingroot 4.9, again same errors.
It worked for me for kingroot 5.0 on lyf flame 8 through emulator method.
Sent from my SM-G900H using Tapatalk
I tried on kingroot 5 oppo f1s anf failed. Then tried kingroot 4.9 failed. Then tried kingroot 4.81 and super sume pro.. Works like a charm.
How should I go about factory resetting my rooted, HD 7" that's running a different launcher? So that it can go back to as clean as possible and be updatable and used normally without bricking/dying. I heard it's dangerous to just use the native factory reset as it can end up with bricks.
Its running on some older firmware that was rootable not long after it became possible and is running Vire Launcher instead of the typical amazon launcher. I'd like to go back to Stock somehow.
Sorry for the double post but seriously no-one knows how to go back to fully default?
Shadowshinra said:
Sorry for the double post but seriously no-one knows how to go back to fully default?
Click to expand...
Click to collapse
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
DoLooper said:
For stock with no root:
Run these commands to unblock OTA:
Code:
adb shell pm unblock com.amazon.dcp and
adb shell pm unblock com.amazon.otaverifier
Also, look for /system/priv-app/deviceSoftwareOTA.apk and make sure the extension is (plain) "apk"
Put OS 5.1.2 onto /sdcard (not inside a folder) and press Update now in Device settings.
For latest stock with root, follow this root guide: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 without installing Gapps/xposed/makespace. If you're running OS 4.5.3 now you can use 5.2.0_stock_recovery_uboot.zip at step 10.
Click to expand...
Click to collapse
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Shadowshinra said:
Seems simple enough, the adb commands seemingly worked but I can't seem to rename the APK_ back into APK using ES file explorer, it just says renaming progress and the bar doesn't fill up.. so I haven't done the last step yet.
Click to expand...
Click to collapse
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Try rebooting and see if it got renamed. Are you sure you're rooted and have root explorer on in es file explorer? Maybe you used JMZ's Fire Tool to block OTA? See if you have it and try that for unblocking. Or, if rooted this command might work:
Code:
adb -d shell "su -c 'mount -o remount,rw /system; cd /system/priv-app/; mv DeviceSoftwareOTA.apk_ DeviceSoftwareOTA.apk'"
If you can't get it renamed, try doing the update. Don't think it'll work, but worth a shot. If it doesn't work, you'll need to boot twrp and install 5.1.1 or 5.1.2 from there: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Click to expand...
Click to collapse
Definitely rooted, heck you yourself helped me do it a long time ago, even Root checker says i'm still rooted, I do have JMZ tool, the OTA section is gray though, reboot didn't help, will try the adb command
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Shadowshinra said:
Edit, upon entering the command CMD appeared to hang/stall/do nothing. Not letting any other commands to be typed afterwards.
Click to expand...
Click to collapse
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
DoLooper said:
CTRL-C to get out. EDIT @Shadowshinra: Do you get # prompt with "adb shell" "su"?
Click to expand...
Click to collapse
You mean the popup on the kindle? Now you mention it, It hasn't been popping up since I've been attempting this, so somehow I/it semi-unrooted itself despite the rootchecker saying it's fine? Or were the changed we did responsible?
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Shadowshinra said:
Edit: Oh wait I know what you mean now, the # sign isn't there either, it's a $ so yeah It's unrooted itself somehow or I did something unknowingly, which is odd seeing as the Vire Launcher, root checker and all my apps are still working..
Edit2: Ran supersu, turned it off and on, appears to have fixed it? I was able to rename it aftar that.. it can't have been that simple lol..
Click to expand...
Click to collapse
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
DoLooper said:
Yes, there's a twilight-zone state in which root apps partially work but you can't get full superuser access until you update binaries by running superSU app. No idea how you lost su. Anyway, I trust you can update to unrooted stock 5.1.2 now.
Click to expand...
Click to collapse
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Shadowshinra said:
When I tried to use that update it just says Validating update file, and seemingly loading forever, i'll edit if it ever completes, but if I turn on wifi it will try to download an update from there can that not be used instead or does that cause the bricks I've heard about?
Click to expand...
Click to collapse
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
DoLooper said:
The OTA update should be fine. I actually thought the manual method would be faster, but . . .
Click to expand...
Click to collapse
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Shadowshinra said:
Ah I see, however another issue has arisen, upon hitting update and it attempting to do so after a reboot, the team win recovery menu shows up instead, If I click reboot from there I'm just taken back to the dashboard on the original rooted firmware, I guess the TWRP is interfering in some manner? Also do I have to reenable the Fire Launcher and uninstall Virelauncher before all of this or will the updating process just do all of that.
Click to expand...
Click to collapse
@bibikalka, I totally forgot @Shadowshinra would have TWRP, coming from rooted OS4. Any problem with him following your steps here to restore stock? http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267 Thanks!
Hello ive not done any guides before but since i had to search all over to try find out what i was looking for and stumbled across a lot of good information and thought id share it. None of this was my findings but there isn't anything clear on how to actually accomplish this on a Fire stick.
Im going to attempt to share how i have managed.
This guide assumes you already know how to transfer files to your stick.
First off, current Fire stick os is 5.2.1.0 and is rootable with Kingoroot.
https://root-apk.kingoapp.com
1. Download Kingoroot and ADB to your Fire stick, do this whichever way you normally get apk/files onto your Fire stick.
2. Download Kingoroot superuser and ADB to your Fire stick.
3. Run the Kingoroot tool and let it finish, when you have root, install Kingo roots Superuser. (If you install this before rooting it wont make any difference).
Now you should have a rooted Fire stick on 5.2.1.0 with Kingoroots SuperUser.
Now its time to downgrade your Fire stick. This file was provided by AFTVnews over at another thread and cuki3r3k83bln accomplished downgrade on the thread also so please leave thanks for them as before he posted the file and information i had no idea it was possible. Im suggesting to download the 5.0.5 file as i did because this was when firestarter worked with home button detection.
Download Fire Stick os 5.0.5
http://amzdigitaldownloads.edgesuit...te-kindle-montoya-54.5.3.7_user_537174420.bin
Once you have it downloaded rename the downloaded file to update.bin.
Im going to explain how i did it, i know there is many other variations on how to accomplish this and im not too familiar with adb commands but the way i will show is the way it worked for me.
We need to transfer the downloaded and renamed update.bin to the Fire stick so if you would like to transfer it with apps to fire or through command or any other variation thats fine but ill show commands used from windows laptop using adbLink.
Please note, if your using a different method to transfer you will have to slightly modify step 5 on where your update.bin is stored so cd /sdcard/download. if your update.bin is stored in download folder.
Another note is to make sure your file name is correct, mine was named update.bin.bin rather than update.bin this was fine just make sure to name it correctly or you will have to modify step 6 and step 8.
1. Open up adbLink and connect your device.
2. Push the update.bin to the sdcard. (this takes quite alot of time as your pushing 311mb file so be patient)
3. Once pushed you need to open up ADB Shell.
4. Run the command: su
5. Run the command: cd /sdcard
6. Run the command: mv ./update.bin /cache/
If you get an error about no space on device do the following:
Run the command rm -f /cache/*.bin
Run the command rm -f /cache/*.zip
Run the command exit
Run the command exit then reopen ADB Shell in adbLink repeat step 6.
7. Run the command cd /cache/recovery
8. Run the command echo --update_package=/cache/update.bin > command
9. Run the command reboot recovery
Your Fire stick should automatically start the downgrade and take 10 minutes or so.
As soon as its finished go back to your Kingoroot app and re-root your Fire stick. Then block updates (method 1) using AFTVnews guide at:
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/
You should now be on 5.0.5 rooted and have updates blocked
All your apps should be still intact. Make sure you uninstall appstarter/firestopper and reinstall firestarter 3.2.3 (if you use it)
Then follow AFTVnews guide on how to re-enable it here:
http://www.aftvnews.com/how-to-cont...v-and-fire-tv-stick-software-version-5-0-5-1/
Please give the credit deserved to @AFTVnews.com and @cuki3r3k83bln
Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.
Please do not use any type of Su modifying tool/script/apk eg: SuperSume as these do not work and you will end up with a small brick.
Also its been pointed out to me by @deanr1977 that if your going to use this guide and decide to update Fire Stick os in the future, it maybe safer to unroot it first.
With that out of the way please excuse the bad layout of the guide as im no expert and would like to just share my experience.
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
FireTho1 said:
Would I be able to go back to 5.2.1.0 once custom recovery and rom is released?
Click to expand...
Click to collapse
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Bierfreund said:
Are there any reasons for downgrading to 5.0.5? Does it have any advantages?
Click to expand...
Click to collapse
As far as im aware upto now, it seems that Firestarter home button detection works as it should, and firmware after this Firestarter will not work with home button detection.
Which is a big thing for me personally as i only use Firestick for netflix and kodi and its much easier to launch from within Firestarter.
Its good to know that the process of upgrading/downgrading is applicable to Fire stick as you never know what Amazon will try to take from you.
You sir are my hero. Kudos for the tutorial!
sconnyuk said:
i cant see any reason why not, either grab the 5.2.1.0 .bin file and follow the guide using that or let it automatically update after re-enabling updates.
Click to expand...
Click to collapse
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
deanr1977 said:
Its not recommended to let it auto update from root, unroot first then re-enable the update progress.
Also please can you note in your guide that its not recommended to try to swap the Su for Chainfires Su with the Super Sume or Super Sumepro app because so many people on this forum have bricked with this method & if any new users try your way & after want to unroot/swap method after the first boot they could have a non working device.
Ive not tried this guide myself (i dont need too) but if its working fine this info would be good to have here.
Click to expand...
Click to collapse
Fair point about pointing out about the brickable and dangerous su swapping methods with supersu me etc.
I will add a mention about it after the line that reads:
'Its suggested all over to hold off before doing anything that could brick the device until rbox releases a recovery.'
As for not recommended to auto update while rooted, ive had 2 sticks and a Fire Tv 2 auto update from 5.0.5 to 5.0.5.1 and then to 5.2.1.0 when my router was reset, (im sure im not the only one from what ive read either).
But since im a helping type of guy ill add this also.
Ok mate, just going by what's been said from the AFTVNews & Amazon Firestick forums. Glad you are including this thanks, Its just some only skim through the threads & read only the parts they want to so if this is included it may cut down on the "I've bricked my Amazon device please help threads" which clog up the forum.
Sent from my SM-G900F using Tapatalk
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
sins07 said:
i'm trying to downgrade to the point where display mirroring worked on windows devices, this is before 5.0.5, can i use this method to downgrade to another bin before 5.0.5?
Click to expand...
Click to collapse
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
@vulcan4d recovery & prerooted rom is being worked on at the moment by rbox in this forum
Sent from my SM-G900F using Tapatalk
vulcan4d said:
Amazing! I can't believe this was hard to find as all the news out there say you can only root the stick using a hardware mod.
I downgraded and rooted both my Sticks. Installed Firestarter 3.2.3, installed Seeder, removed unneeded processes from running and these things are super quick now. You still have to load the crappy slow Amazon launcher to keep the settings but oh well. Nicely done, now I hope a recovery option comes out and I can mess around further . Heatsink and overclocking anyone? lol
Click to expand...
Click to collapse
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
sconnyuk said:
Can I ask what processes you removed/stopped and how you accomplished this?
Id like to do the same on 2 of my sticks.
Click to expand...
Click to collapse
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
vulcan4d said:
I would like to give credit to this post for removing unneeded services:
http://forum.xda-developers.com/fire-tv/help/root-disabling-apps-services-bloat-t3325333
I only found a few from the list but that list was meant for a Fire TV so I'm sure there is more running. Just launch ADB Shell in ADBFire/Link and type pm disable <service_name>
Click to expand...
Click to collapse
Thanks ive disabled them as per the guide you linked to. Can I further ask what the program seeder does and whether to have it set to aggressive or not?
Thanks for the info.
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
nicefile said:
@sconnyuk i've downgraded successfully kingo root'ed stick 5.2.1->5.0.5 . But funny thing was under root shell command "wipe data " .It wiped device clean but root still stays on . Got OTA disabled and my other king root 5.0.5 stick will have similar treatment .
Click to expand...
Click to collapse
You will need to unroot it for root to go.
Kingoroot has the option to do this if its what you want.
You need mouse toggle for fire tv to navigate to the 'in app' menu icon if not plug fire stick into pc and run Windows version of Kingoroot to unroot.
Interesting, I just bought a 3rd Amazon stick to root. After running KingRoot, I've noticed I did not need to install KingUser at all. If you launch KingRoot again it allows you to launch KingoUser which is the same thing. I'm assuming that KingUser is just an updated version of what KingRoot already installs.
Sconnyuk, I checked all the boxes and chose Moderate. This was also mentioned in the XDA forums however sadly I cannot find the post anymore. Seeder is an application that has been around for a while which improves the response time on Android devices. There is a lot of technical details into how it works, but the point is the Amazon stick is not the fastest thing in the world and anything helps. Give it a try and see for yourself.
sconnyuk said:
Id take a stab and say if your stick originally came with a firmware below 5.0.5 but I honestly do not know as ive not tried but I cant see why it wouldnt work. You can go from 5.2.1.0 to 5.0.5.1 or to 5.0.5 so id imagine so.
What features have been removed by 5.0.5? Im interested myself and may try this myself if there is features I could use.
Click to expand...
Click to collapse
Miracast display mirroring became non-compliant with windows systems, it still works fine with android.