WARNING: For 20b and up (it means V20d also! ) DOWNLOAD this and make steps from 2. and optionally from 2. to 6
check this site for updates of root-making app
------------------------
1. Download and put it on your phone: https://drive.google.com/file/d/0BwDGitcriVSbcVR3X0UtY1Y3WGs/view?usp=sharing
2. Run the app - click START ROOT (you must have internet connection). AND WAIT.
this steps are optional
3. Download and extract MRW folder to your phone memory. https://drive.google.com/file/d/0BwDGitcriVSbMjQ0N3NlcGYwTXM/view?usp=sharing
4. Download from Google Play Terminal Emulator
5. Disconnect the phone from the USB port - IMPORTANT. Without it changes will not succeed !!!
6. Open Terminal Emulator app and enter this lines:
Code:
Su (enter)
sh /sdcard/mrw/root.sh
This will start a script that will remove Kingroot and replace to SuperSu, then automatically direct you to update the binary files. After this procedure, restart your phone and enjoy the ROOT, SuperSU on L
------------------------
Thanks for tutorial: original thread
------------------------
#
It works, thank you very much
WYPIERDAALAAC said:
1. Download and put it on your phone: https://drive.google.com/file/d/0BwDGitcriVSbcVR3X0UtY1Y3WGs/view?usp=sharing
2. Run the app - click START ROOT (you must have internet connection).
3. Now you have to install SuperUser from Google Play and download binaries.
4. Turn on your phone.
5. Download and extract MRW folder to your phone memory. https://drive.google.com/file/d/0BwDGitcriVSbMjQ0N3NlcGYwTXM/view?usp=sharing
6. Download from Google Play Terminal Emulator
7. Disconnect the phone from the USB port - IMPORTANT. Without it changes will not succeed !!!
8. Open Terminal Emulator app and enter this lines:
Code:
Su (enter)
sh /sdcard/mrw/root.sh
This will start a script that will remove Kingroot and replace to SuperSu, then automatically direct you to update the binary files. After this procedure, restart your phone and enjoy the ROOT, SuperSU on L
BIG THANKS FOR THIS TUTORIAL
Click to expand...
Click to collapse
I will never test it. I don't trust a root app which need internet connection. For what does it need internet? Sending something to someone? I do not trust it. If you say it works, post some screenshots of working titanium backup, betterbatterystats or other apps
I tried another method for other LG Lollipop firmwares, but not working (but at least it works via ADB and download mode, with no internet connection needed -.-)
I just installed the Kingroot app and clicked "START ROOT" and it worked perfectly, i don't even did the rest of the tutorial...
I attached a screenshot of greenify with auto hibernation active (you need root for that, sorry for the Portuguese language)!
Big thanks!
Andrewbons said:
I will never test it. I don't trust a root app which need internet connection. For what does it need internet? Sending something to someone? I do not trust it. If you say it works, post some screenshots of working titanium backup, betterbatterystats or other apps
I tried another method for other LG Lollipop firmwares, but not working (but at least it works via ADB and download mode, with no internet connection needed -.-)
Click to expand...
Click to collapse
But it works maybe this update their binaries by the web, i honestly dont care do a "risk" or leave it
WYPIERDAALAAC said:
But it works maybe this update their binaries by the web, i honestly dont care do a "risk" or leave it
Click to expand...
Click to collapse
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Andrewbons said:
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Click to expand...
Click to collapse
I meant 'Risk it or leave it'. You are so grouchy today (or always?). You will use this app only once so just do it.
Andrewbons said:
"Do a risk or leave it", wise words. I gave it a try because of XDA translated it into english (but it's still a suspicious app -.-). Now, any idea on how to use SuperSU instead of KingUser? I want remove everything without installing anything else from shell
Click to expand...
Click to collapse
If you're so damn wise just inspect scripts that are used from mrw folder and see if it has something suspicious.
binary update faild
using d618
any other method to root with supersu ?
didar2 said:
binary update faild
using d618
any other method to root with supersu ?
Click to expand...
Click to collapse
same here using d620
I do it like this:
1. Use KingRoot to root.
2. Install SuperSU and Terminal.
3. Open Terminal and type: su then sh /sdcard/mrw/root.sh
4. SuperSU will open automatically and will ask for binary, accept it and you are done
sheraz777 said:
same here using d620
Click to expand...
Click to collapse
use last version of supersu (v2.49 - BETA) it has improved Kingroot removal :good:
Just to make clear to everybody, you don't need to install supersu from Play Store you already have it in mrw folder, and when you start root.sh script it will automaticaly install it from folder. I did it a couple of times in the last few days with no problem.
good to know. now just use KingRoot and type command in terminal.
maybe now nobody will have problems with it
didar2 said:
use last version of supersu (v2.49 - BETA) it has improved Kingroot removal :good:
Click to expand...
Click to collapse
thank you so much... it worked like a charm...
now waiting for twrp for lollipop..
sheraz777 said:
thank you so much... it worked like a charm...
now waiting for twrp for lollipop..
Click to expand...
Click to collapse
Twrp and patched aboot is already out...
Sent from my LG-D620 using XDA Free mobile app
steffenbakke said:
Twrp and patched aboot is already out...
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
thanks man,,,, patched and flash twrp from flashify
i rooted version d620r poland but when i removed some apps of bloatware like g+ hangouts etc then my apps were crashing and lag the phone....
i flashed then the portugal version for d620r but root fails on it
peplosfc said:
i rooted version d620r poland but when i removed some apps of bloatware like g+ hangouts etc then my apps were crashing and lag the phone....
i flashed then the portugal version for d620r but root fails on it
Click to expand...
Click to collapse
that's weird, bcoz i uninstalled bloatware and no problems at all. probably you deleted not that folder
i got rom from D620 (without LTE) and phone D620R (with LTE) and i don't really care for LTE for now so i got no problems, everything works fine.
SuperSU says update binary failed. Its some another root method or somebody knows where can be a problem?
I have d620r.
Related
Q&A for [ROOT][5.x.x] Root for G2 Mini / Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][5.x.x] Root for G2 Mini / Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
D620r rooting issue
So I've followed the steps but it doesn't seem to budge.
Here is what I do exactly, and tell me if I do something wrong.
1. I install the kingroot thingie, and root with it. It instals KingUser and something written in Chinese/Japanese/Korean (can't differentiate between those).
2. I install the SuperSu from playstore (did try with the one in MRW folder as well, didn't do anything different).
3. I attempt to install binaries but it fails (tried rebooting, still the same)
4. Using ES File Explorer I copy the MRW folder to the internal storage.
5. I am installing the Terminal Emulator on play store.
6. Then I'm opening the terminal emulator, type in "Su" (without the ") and hit enter and as a response I get "/system/bin/sh: Su: not found
7. Then for the sake of it I try inputting "sh /sdcard/mrw/root.sh
8. As a response I get "mount: operation not permitted java.lang.SecurityException: Permission Denial: killBackgroundProcesses() from pid=10412, uid=10117 requires android.permission.KILL_BACKGROUND PROCESSES" and it follows by several lines of code and that is that.
After that KingRoot, KingUser and the Chinese/Japanese/Korean thingie are still there, SuperSu still can't install binaries and root support is crappy at best. Some things work but most don't since the permissions are managed by KingUser which is really crappy.
Any idea why the thingie won't work?
I have a LG G2 Mini, with Lollipop 5.0.2 bought from T-Mobile, updated it to Lollipop myself.
When I had it on KitKat I had proper root managed by SuperSu.
petrovskyz said:
So I've followed the steps but it doesn't seem to budge.
Here is what I do exactly, and tell me if I do something wrong.
1. I install the kingroot thingie, and root with it. It instals KingUser and something written in Chinese/Japanese/Korean (can't differentiate between those).
2. I install the SuperSu from playstore (did try with the one in MRW folder as well, didn't do anything different).
3. I attempt to install binaries but it fails (tried rebooting, still the same)
4. Using ES File Explorer I copy the MRW folder to the internal storage.
5. I am installing the Terminal Emulator on play store.
6. Then I'm opening the terminal emulator, type in "Su" (without the ") and hit enter and as a response I get "/system/bin/sh: Su: not found
7. Then for the sake of it I try inputting "sh /sdcard/mrw/root.sh
8. As a response I get "mount: operation not permitted java.lang.SecurityException: Permission Denial: killBackgroundProcesses() from pid=10412, uid=10117 requires android.permission.KILL_BACKGROUND PROCESSES" and it follows by several lines of code and that is that.
After that KingRoot, KingUser and the Chinese/Japanese/Korean thingie are still there, SuperSu still can't install binaries and root support is crappy at best. Some things work but most don't since the permissions are managed by KingUser which is really crappy.
Any idea why the thingie won't work?
I have a LG G2 Mini, with Lollipop 5.0.2 bought from T-Mobile, updated it to Lollipop myself.
When I had it on KitKat I had proper root managed by SuperSu.
Click to expand...
Click to collapse
Try everything from the begining, install Kingroot and without installing SuperSU from market execute root.sh from terminal (with 'su' previously).
Yai!
nlooooo said:
Try everything from the begining, install Kingroot and without installing SuperSU from market execute root.sh from terminal (with 'su' previously).
Click to expand...
Click to collapse
okay using "su" instead of "Su" did change everything, now SuperSu binaries are installed, KingUser is gone. Thank you! I've been busting my head over typo. -.-
Finally I can start customizing my device now
Cheers!
Thanks, it worked ^^
LG G2 mini D618. firmware v20b
View attachment 3368494
its works...............,finally i've got rooted lg d 618 L5.0.2
Hi, thank's work fine for me.
lg g2 mini lg-d620fr
In this thread is a modded version of Towelroot if someone is eager to try. I would do that but my phone is already rooted.
http://forum.xda-developers.com/showthread.php?t=3139160
d620r for not working
I've tried all the ways to root my g2mini d618 but none of them works. even kingroot. when it gets to 70%, it shows me an error saying root failed. i have tried one click root and Root Script v1.2 and any other ways in the net but no luck. can anyone help me plz?
attari16 said:
I've tried all the ways to root my g2mini d618 but none of them works. even kingroot. when it gets to 70%, it shows me an error saying root failed. i have tried one click root and Root Script v1.2 and any other ways in the net but no luck. can anyone help me plz?
Click to expand...
Click to collapse
Kingroot needs active internet connection, maybe you switched it off.
nlooooo said:
Kingroot needs active internet connection, maybe you switched it off.
Click to expand...
Click to collapse
no without internet connection its not even start rooting. for me it stops at 70% of rooting. i tried kingroot so many times but every time i get the same error
gesher said:
Thanks, it worked ^^
LG G2 mini D618. firmware v20b
Click to expand...
Click to collapse
what is the region of your firmware? i firmware v20b too but kingroot is not working for me
Maybe Help
I tried this method mor than three times with no results... I tried one more but first installed the superuser.apk inside the MRW folder, not from PlayStore, then runned the root.sh an for my surprise its Working Perfectly!
Afther that moved from inside the app to system and it's totally rooted!
(Sorry my english je)
Hi, works for me thank's
lg g2 mini d620fr
attari16 said:
what is the region of your firmware? i firmware v20b too but kingroot is not working for me
Click to expand...
Click to collapse
COL originally V10a but use CIS to update v20b
unroot 5.x.x
If I want desrootear lollipop I do not trace if I have to take the SAT or update ??
Thank you very much ....
Help
Why do this comes up when I type in terminal ?
#su
#sh /sdcard/root.sh :directory not found
But I have mrw file in sdcard
hi i rooted using kingroot!
it worked! but while i was removing google uselless apps (music,games,g+ etc) i probably missclicked kingroot and removed...
Now i cant gain access to root apps or unroot...
what can i do?
thanks
Root failed in d618 20d firmware (cis). It worked in 20b (cis too). Need back to 20b?
Why doesn't work?? :'(
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.
Here simple tool for busybox installation. This is specially designed for stock ROM and kernel users. Without busybox many root app may not work correctly so made a simple one Click Tool for same. Also it have one more function to enable Broeser secret mode with password/fingerprint.
This application requires root.
1.Intall attached Busybox MM apk
2.open app - grant su
3.read status of busybox. And select to install if it is not installed.
4.once busybox installed, restarting app should show new status.
5.Also added small Tool to enable browser secret tab (with password / fingerprint) but that require to have busybox. So first install busybox before activating it.
Really I couldn't test this so recommend to make nandroid (at least before some report comes)
Cant install busybox, every time i install it and reboot it's gone.
Tamir_Hazut said:
Cant install busybox, every time i install it and reboot it's gone.
Click to expand...
Click to collapse
I have the same issue with Norma rom (Note 7 port). After restart I need to reinstall again.
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.
Hi,
I need to root a Zebra TC56 to install some other apps that require rooted Android. There is very little information in the way of rooting the Zebra TC56. I 'm pretty set on using Chainfire's superSU, but I cannot find any information on whether it will work on this hardware. Does anyone know if the superSU works on this device with Android 6? If not, is there another Root Tool that will work.
Any advice appreciated.
THANK YOU!
VK
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
jwoegerbauer said:
1. Install BusyBox applet-suite what contains the SU-binary
2. Install latest SuperSU APK
Click to expand...
Click to collapse
BusyBox installed fine.
SuperSU will not install all the way. When I select to root, it says root not detected and then, "How to Root", which launches my browser to a site that no longer exists.
Now what?
Thank You!
edit: Still stuck at this point. I read about TWRP, KingoRoot and some other random apps. I cannot brick this touch computer; it is $1600; that would be a very expensive brick. :crying:
So, I have no idea if I am right, but maybe I need to open the terminal emulator and "su" install the SuperSU apk. But I have no idea and I don't want to experiment. Hopefully, someone can help me.
@vidarr_kerr
Don't confuse things:
SU is the super user who unrestrictedly can perform any operation on Android OS. As soon as SU got installed Android is rooted! Again: BusyBox you successfully installed contains the su applet.
SuperSU is merely a root-manager app: it maintains a database where is stored what app can act as super user. SuperSU app doesn't grant super user rights.
BTW:
TWRP has nothing to do with rooting device's Android, as this is also true with Magisk.
The device is still not rooted after the "BusyBox Installer (No Root)", from your link, was installed.
I installed BusyBox, I followed the directions to then copy a command, then open a terminal, paste the command in and hit enter, then nothing happened. SuperSU was not installed with it.
So, as you told me, I then installed the latest SuperSU APK from your link. It says it installed, but when I run it, it says root not detected and then has a link named, "How to Root", which launches my browser to a site that no longer exists.
I followed what you said. Where did I go wrong?
Thank You!
You didn't get it. Sorry to say this.
jwoegerbauer said:
You didn't get it. Sorry to say this.
Click to expand...
Click to collapse
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
(That should have tipped me off right away you had no clue, but I thought maybe you knew something.
So, you gave me the links for both of those files and it doesn't work.
I don't think you have any idea what you are doing; and shouldn't be explaining things you do not understand.
The "no root" BusyBox, does not include SuperSU.
If it did, why did you give me the link for the separate SuperSU file?
All the "no root" BB did was install a terminal emulator (with no su abilities).
The SuperSU didn't install, because the Android is NOT rooted.
If the Android WAS rooted, SuperSU would run and allow me to grant su privilges to the apps that require it to work.
You basically just wasted my time.
I would have just said "thank you" and moved on, but you are rude.
You don't know what you are talking about either.
Hopefully, this will help others, to not do what you say to do.
vidarr_kerr said:
Didn't get what?
I installed the BusyBox you gave me the link to.
I semi-installed the SuperSU you gave me the link to.
SuperSU did not fully install, because the Android is NOT rooted..
BusyBox had no SuperSU as part of it --the file you said to use even says "BusyBox Installer (No Root)".
Click to expand...
Click to collapse
You're right: BusyBox (No Root) doesn't come with SU-binary. Wasn't aware of this. I misinterpreted APK's title. Pitty.
ERRARE HUMANUM EST ( To err is human ).
Installing BusyBox containing SU-binary requires your device's bootloader got unlocked before, because Android's /system partition gets modified. Hence manage to unlock device's bootloader as 1st thing of all things. Good luck.
DL BusyBox latest: https://github.com/meefik/busybox/releases/download/1.31.1/busybox-1.31.1-46.apk
My last 2 cents here: SuperSU and SU binary are totally different things.