TESTED AND WORKS ON THE NEW VRALHE AND VRALHD IN ADDITION TO ALL OF THE OTHERS
(EXCEPT THE NEW LEAK I535VRBLI5) I AM WORKING ON IT
BOTH DEODEXED AND ODEXED
â
This is a modified version of debugfs that installs SuperSU instead of SuperUser. The only other way I was aware of that would install SuperSU without having to install SuperUser first, was Chainfire's method using a CWM zip and flashing. You use this version of debugfs just as you would normally from here . There are a few changes, but if you have used debugfs before, you will have no trouble.
THIS MODIFIED DEBUGFS IS 100% STABLE/UPDATED SCRIPT 10/09/2012!!!
DOWNLOAD: SuperSu_GS3_Debugfs_r2b.7Z
MIRROR: here MIRROR2: here
MD5: FE4F03407F8CACF8575714CED91CC843
DOWNLOAD: SuperSu_GS3_Debugfs_r2b.MD5
MIRROR: here MIRROR2: here
MD5: 44F4BE5F7E1A41CCEA14822A3D5E8F54
MODIFIED Debugfs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Opening SuperSU for the FIRST time
-------
-------
Roots PERFECTLY
--
--
--
Phone Number, Device Status and IMEI are ALL GOOD
-------
ALL CREDITS GO TO:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* Chainfire, for the SU files/binaries and Supersu
* Noxious Ninja, for making Debugfs work w/the SGS3
I am a Flash-O-Holic and I love my rooted devices. I really like to use SuperUser for some devices, BUT for some devices I would rather use SuperSU. They are both great APPS.
But, if you are extremely anal like I am, you like things to be as clean as possible. And even if you root your device and install SuperUser so that you can install SuperSU afterwards, you still have to go back and uninstall SuperUser (if you want to). I am sure there is nothing left behind, but I like everything to be fresh.
-
I did not like having to install SuperUser and then afterward insstall SuperSU and then delete SuperUser, etc, etc. So, I came up with this method using the Debugfs script and Chainfire's SuperSU.
-
I give all credits to Noxious Ninja for getting this to work wth the Samsung Galaxy S III for Verizon.
I simply changed a little of the script and swapped out the binaries and APK.[/FONT]
-
-
DON'T FORGET TO HIT THE "THANKS" BUTTON IF YOU LIKED IT!
-
-
-
I was not the one who made this tool and I really can only accept about 25% of the credits for this tool. I just modified/scripted debugfs to use SuperSU instead of SuperUser.
Noxious Ninja was the one who modified it to work with the Samsung Galaxy S III.
I used/modified his script. I found out it was okay to modify this tool as long as the PROPER CREDITS were given.
I also used some of Chainfire's files obviously for SuperSU.
This is Noxious Ninja's credit list for the original creators.
Noxious Ninja said:
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser
Click to expand...
Click to collapse
If you get a chance to donate/thank them, I am sure they would appreciate it.
I made sure that there were links for absolutely EVERYONE that had a hand in debugfs. Inside of the "Donate Menu".
-
-
-
-
-
Reserved
..
Is there any need to wipe any data or other settings? Or is this just a plain simple way to have root access and it does nothing else (which is what I need/want)?
gmm6797 said:
Is there any need to wipe any data or other settings? Or is this just a plain simple way to have root access and it does nothing else (which is what I need/want)?
Click to expand...
Click to collapse
I' sorry, but could you elaborate? If you want to get root from your stock/unrooted ROM, then this is a tool you could use.
For some reason I cant download ....
:victory:
h3llsdr0id said:
I' sorry, but could you elaborate? If you want to get root from your stock/unrooted ROM, then this is a tool you could use.
Click to expand...
Click to collapse
In a lot of the root scripts, it requires the phone to be wiped and cache deleted or cleared.
I wanted to know if this was the case, so I can run multiple backups (since titan backup wont work until rooted)
Can anyone mirror the download to another site?? wont let me d/l from the OP site
they both downloaded fine for me
im getting something about javascript not being enabled on the download site
but its enable...
EDIT
This is what i get...
{"INFO":"failed posted hashcheck","SOLUTION":"please make sure you have javascript enabled for androidfilehost.com. Hit the back button, enable javascript and try again please. we promise we are probably not doing anything nefarious. maybe. no promises though."}
crazydad said:
im getting something about javascript not being enabled on the download site
but its enable...
EDIT
This is what i get...
{"INFO":"failed posted hashcheck","SOLUTION":"please make sure you have javascript enabled for androidfilehost.com. Hit the back button, enable javascript and try again please. we promise we are probably not doing anything nefarious. maybe. no promises though."}
Click to expand...
Click to collapse
Mirrors are up. Let me know if y'all have anymore problems.
THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!! BTW Awesome work!!
gmm6797 said:
In a lot of the root scripts, it requires the phone to be wiped and cache deleted or cleared.
I wanted to know if this was the case, so I can run multiple backups (since titan backup wont work until rooted)
Click to expand...
Click to collapse
:victory:
I just tested it on my other SGS3 which was running a stock ROM and had not been rooted. I have been installing apps and using it as my personal phone for about a week. I ran the modified debugfs and it rooted my phone perfectly. Just make sure you read the instructions when you run debugfs.
Make sure you have "Uknown Sources" checked off in Security Settings and that you also have enabled "USB Debugging" in Developer Options.
-
-
-
-
-
-
crazydad said:
THANKS!!!!!!!!!!!!!!!!!!!!!!!!!!!! BTW Awesome work!!
Click to expand...
Click to collapse
Thanks A LOT brother.
You can support me by hitting the THANKS BUTTON and everyone else listed in the OP (who created Debugfs and made this all possible) by doing the same.
Support Chainfire and purchase SuperSU Pro!
Thanks so much for this, its perfect !!
I'm just about to root my phone, was reading all the guides and thought how nice it'd be if the DebugFS method had the newer SuperSU instead, and you did all the work already
ECrispy said:
Thanks so much for this, its perfect !!
I'm just about to root my phone, was reading all the guides and thought how nice it'd be if the DebugFS method had the newer SuperSU instead, and you did all the work already
Click to expand...
Click to collapse
Thank you for trying it out. I did it mainly so that there was a way to use SuperSU without having to go through the process of installing and uninstalling or flashing a zip.
In regards to:
ECrispy said:
you did all the work already
Click to expand...
Click to collapse
I was not the one who made this tool and I really can only accept about 25% of the credits for this tool. I just modified/scripted debugfs to use SuperSU instead of SuperUser.
Noxious Ninja was the one who modified it to work with the Samsung Galaxy S III.
I used/modified his script. I found out it was okay to modify this tool as long as the PROPER CREDITS were given.
I also used some of Chainfire's files obviously for SuperSU.
This is Noxious Ninja's credit list that I also added to the OP for the original creators.
Noxious Ninja said:
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser
Click to expand...
Click to collapse
If you get a chance to donate/thank them, I am sure they would appreciate it.
I made sure that there were links for absolutely EVERYONE that had a hand in debugfs. Inside of the "Donate Menu".
will this work on the new ota
johnminator said:
will this work on the new ota
Click to expand...
Click to collapse
Okay. I just took the OTA update just so that I could test this. I sucessfully rooted my phone with SuperSU!!!
But, just in case:
I DO NOT TAKE ANY RESPONSIBILITY IF YOU MESS UP/BRICK YOUR PHONE WHILE TRYING TO ROOT YOUR PHONE WITH THIS MODDED DEBUGFS.
Yes. It just worked on MY phone, but you never know what could happen.
For some reason, my bootloader did not relock (many are saying that their bootloader gets re-locked).
I already have my phone rooted using the original method with SuperUser I would rather use SuperSu can I just use this or would it be easier and safer to just install SuperSu and delete SuperUser?
So this is still going to work on both phones with and without the OTA, right?
LakerStar25 said:
I already have my phone rooted using the original method with SuperUser I would rather use SuperSu can I just use this or would it be easier and safer to just install SuperSu and delete SuperUser?
Click to expand...
Click to collapse
Hey brother.
Both ways seem fine. If it was me (because I am a weird) I would start over from scratch and root with SuperSU.
Or, leave SuperUser on your system and run this tool. Then after it is done running, you won't have to give SuperSU permission through SuperUser to update it's binary, because it will have already installed it with DebugFS. Then you can uninstall SuperUser.
(I.E. You know how when you normally have SuperUser on root66/other ROMS/etc. and you have to install SuperSU and then give it permissions from SuperUser to update it's binary, and then uninstall SuperUser, etc, etc? If you just run this tool, you won't have to go through that whole process)
So are you on the OTA right now?
Please post back and tell us how everything turned out!!!
Related
Background:
Originally posted on XDA and Google Play in 2011 and frequently updated with over 10M users!
Disclaimer:
** This application will NOT provide root access **
** FREE on XDA - Want to help the rooting community! **
Brief Description:
This application will allow the user to confirm they have proper root (super user) access and proper busybox install.
Advanced Root Check mode will show, Superuser.apk installation and version, adb shell default user mode, standard su binary locations and permissions, along with root uid/gid. Advanced Busybox Check will show all applets the installed Busybox binary supports. Advanced Root Check and Busybox Check have an email feature allowing results to be easily shared/exported. Over 20+ different devices have links to their device specific rooting guides.
Description:
The goal of this application is to provide even the newest Android user with a simple method to check for root access on their phone. This is a very simple application to notify the user whether or not they have properly setup root access and whether or not they have properly installed busybox. For advanced users, this application will provide many more details giving the user greater control and knowledge of their root and busybox installation.
Gaining root access varies based on manufacturer, model, and carrier. Please refer to device specific posts and boards here on XDA or use http://www.google.com to search for the appropriate support areas for your specific rooting needs. Feel free to email me with root guides which have worked!
Download:
From the Android Market: Root Check Basic (Free) & Root Check Pro (Paid)
From my personal host: Root Check Pro (Free)
For those in China or other countries which block the Android Market, please use my personal hosting link above.
Feedback:
Please PM me with feedback, suggestions and comments. Thank you!
Screenshots:
Root Checker Basic - Successful Results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root Basics - Learn the essentials about Android root
Root Checker Pro - Success Results - Part 1
Root Checker Pro - Success Results - Part 2
Change Log:
Version 3.7
** Added System PATH variable output to advanced
** Added BusyBox binary location to advanced
** Added /system/xbin/sudo check to advanced
** Added root guide links for Motorola Photon & Samsung Prevail
** Hide empty results text field on App Load
** Updated title from Busybox to BusyBox
w00t! nice job, joeykrim!
I like!!!!!! 10 chAAAAAAAAAAAAAAAAAAAAAAAAARRRRRS
Released an update!
v1.5 - Jan 25th 2011
** Added Froyo App2sd native support
** Added Exit button to the menu
** Refined dialog box menu code
v1.4 - Jan 24th 2011
** Added options menu under the hardware menu key
** Added disclaimer and about menu sections
** Increased efficiency in a few functions
** Fixed screen rotation button/text color bug
** Removed old and unused code
** Prepared application for possible future translations
Pretty neat.
The Busybox checker doesn't work for me though. I launch Titanium Backup, click Problems, it downloads everything and then says Busybox installed. Then I launch Root Checker and it says it's not installed (for Root, it says yes).
Paul22000 said:
Pretty neat.
The Busybox checker doesn't work for me though. I launch Titanium Backup, click Problems, it downloads everything and then says Busybox installed. Then I launch Root Checker and it says it's not installed (for Root, it says yes).
Click to expand...
Click to collapse
Titanium Backup installs a local copy of busybox ONLY for Titanium backup to use. It does not install a systemwide busybox, which is the proper way to install it. It would be very hard to look for every specific application's locally installed version of busybox as they are hidden from other apps by default and root access must be obtained to even find them.
Thanks for the feedback. It is a good confirmation to what I had suspected regarding Titantium backup.
Glad to hear root check verifies root correctly!
Released new Version 1.6:
** Added Advanced mode for experienced users
** Added toggle for advanced mode under Options Menu
joeykrim said:
Titanium Backup installs a local copy of busybox ONLY for Titanium backup to use. It does not install a systemwide busybox, which is the proper way to install it. It would be very hard to look for every specific application's locally installed version of busybox as they are hidden from other apps by default and root access must be obtained to even find them.
Thanks for the feedback. It is a good confirmation to what I had suspected regarding Titantium backup.
Glad to hear root check verifies root correctly!
Released new Version 1.6:
** Added Advanced mode for experienced users
** Added toggle for advanced mode under Options Menu
Click to expand...
Click to collapse
Ahh, I didn't know that it got installed ONLY for Titanium Backup. That makes sense.
How do you install BusyBox for all applications? (I've never actually installed it for any reason other than from within Titanium Backup.)
Paul22000 said:
How do you install BusyBox for all applications? (I've never actually installed it for any reason other than from within Titanium Backup.)
Click to expand...
Click to collapse
Either use a custom rom, they all generally install busybox correctly, or search the market for BusyBox, an app by Stephen (Stericson), a senior moderator here on XDA, which should install it correctly.
Hope that helps and appreciate your support in using my app!
App
Handy, thanks!
Sweet app, works on my Stock german milestone 2.1u1
Sent from my Milestone using XDA App
Thanx man!
When I search either "joeykrim" or "Root Checker", it does not show up in the Market at all.
Why?
I tried typing the direct URL into Browser and that just did a google search of that URL... :\
Can not find it on market ?
austinm08 said:
When I search either "joeykrim" or "Root Checker", it does not show up in the Market at all.
Why?
I tried typing the direct URL into Browser and that just did a google search of that URL... :\
Click to expand...
Click to collapse
Go through APPBRAIN worked for me ....
austinm08 said:
When I search either "joeykrim" or "Root Checker", it does not show up in the Market at all.
Why?
I tried typing the direct URL into Browser and that just did a google search of that URL... :\
Click to expand...
Click to collapse
LIL-SIDDI said:
Can not find it on market ?
Click to expand...
Click to collapse
Sorry! I was just making a few updates to the app.
A new version has been released and is available in the market. Thanks everybody for your support! I look forward to all the feedback and suggestions!!
edit: ignore me. Somehow didn't set busybox executable. App now detects it in xbin fine
joeykrim said:
Disclaimer:
** This application will NOT provide root access **
Brief Description:
This application will allow the user to confirm they have proper root (super user) access.
Goal:
The goal of this application is to provide even the newest Android user with a simple method to check for root access on their phone. This application will also provide a simple notification whether or not Busybox has been installed properly.
Description:
This is a very simple application to notify the user whether or not they have properly setup root access and whether or not they have properly installed busybox.
Gaining root access varies based on manufacturer, model, and carrier. Please refer use http://www.google.com to find the appropriate support areas for your specific rooting needs.
Download:
From your Android Phone - Root Checker
From the market - search for Root Checker or joeykrim
Feedback:
Feel free to PM me with feedback, suggestions and comments. Thank you!
Click to expand...
Click to collapse
It works ... Optimus One P500 - void
joeykrim said:
Sorry! I was just making a few updates to the app.
A new version has been released and is available in the market. Thanks everybody for your support! I look forward to all the feedback and suggestions!!
Click to expand...
Click to collapse
I guess we happened upon this thread at just the wrong time. Downloaded it, nice app.
very useful
Nice one.cheers for usefull app m8
Sent from my HD2 Jaws-MIUI
GalaxyTab3_Toolkit v1.1
For use with the Samsung Galaxy Tab 3 8" WiFi - SM-T310 Model
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an all-in-one tool, used to assist with rooting/custom recovery/stock rom/custom rom/bricks
I've made this because, there isn't a tool specifically for the 8" sm-t310 available, and I figured everybody could benefit from it somehow.
- Instantly and directly download the following:
--- GalaTab3 Kernel v14.1.6 (thanks to @arshull )
--- CWM Recovery v6.x r#4 (thanks to @emwno )
--- TWRP Recovery v2.5.0.0 r#3 (thanks to @emwno )
--- TWRP Recovery 2.6.3.0 (thanks to @gr8nole )
--- Philz Advanced CWM v6.12.8 (thanks to @Phil3759 )
--- Odin v.3.09
- Flash recovery, stock firmware image
- Read system information
- Run Odin within this app to flash recovery/firmware
- View live logcat
- Supports JDQ39 firmware 4.2.2 (does not currently work with 4.3/4.4!!)
- Perfect for noobs and advanced users
Download
http://www.f0il.com/android/GalaxyTab3_Toolkit_v1.1.zip - v1.1
Special thanks to:
@arshull - for his GalaTab3 Kernel work
@emwno - for his CWM & TWRP Recovery work
@regaw_leinad - for his AndroidLib project
@autoprime - for being a cool ass dude
@gr8nole - for his work on CWM recovery and Cyanogenmod port
@Phil3759 - for his awesome advanced CWM port
Changelog -
02/02/2014 - v1.1
(*) Fixed Reboot Download issue requiring root, will now reboot regardless
(*) Reworked GUI to be quite a bit more friendly
(*) Fixed a few connection related bugs
(+) Added option to make program always on top of other forms on/off
(+) Added options to download more recoveries
01/22/2014 - v1.0
(*) Fixed bug in GalaTab3 Kernel Download
(*) Changed GUI slightly, added section for "links" instead of including them under "tools"
(+) Added link to this support thread
01/20/2014 - v0.1a
First initial release
@emwno I tried to contact you in your twrp thread, but never got a response. If you want me to remove cwm & twrp from this program, or my server, please let me know and I will do so!
Sent from my iPhone using Tapatalk
Fantastic! Downloading..
Ok DEV i may need a spoon-full. Fired up the tool and scanned, it worked perfect, tab information showed-up and all buttons lit-up. Didn't try any recovery options cause i'm already rooted but i had been meaning to install galatab3. Clicking on "Get GT3 Kernel" didn't do anything and neither did clicking on "Gala Tab 3" (tools section) took me to the discussion thread but nothing else. Neither option downloaded the file, so is it something I'm doing wrong?
Downloading odin worked like a charm, i didn't try TWRP or CWM since I'm already rooted.
Reboot recovery and reboot system work. i haven't had a need to try any other functions (yet). Oh, one thing i found inconvenient is the tool is always-on-top.
I do believe if you intend for it to a tool for noobs, you do a separate tool for rooting and recovery only, sort of like a one or two click rooting with only one or buttons to click. As it is right now, there are too many options. And also you can really get in that noob mode and it would dawn on you to put in the instruction how to make the developer options show up in the first place LOL Just IMO DEV.
Thank you for all of your feedback @treetop777
When you click "Get GT3 Kernel," it should download the GalaTab3 Kernel right into the same directory as the program itself.
Once it downloads, if you then click the "Copy GT3," it will then copy the Kernel over to /sdcard/ path of the device. From there, you can reboot into recovery and install the zip file of GalaTab3 from the sdcard.
Please try that and let me know how it works for you. I will try to categorize everything better and lay it out easier with your feedback. Thank you
Sent from my iPhone using Tapatalk
foil said:
Thank you for all of your feedback @treetop777
When you click "Get GT3 Kernel," it should download the GalaTab3 Kernel right into the same directory as the program itself.
Once it downloads, if you then click the "Copy GT3," it will then copy the Kernel over to /sdcard/ path of the device. From there, you can reboot into recovery and install the zip file of GalaTab3 from the sdcard.
Please try that and let me know how it works for you. I will try to categorize everything better and lay it out easier with your feedback. Thank you
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
NP DEV. Will you put out an update? Cause for sure the version i have DO NOT download the Kernel and also, i don't see the "Copy GT3" you mentioned.
You know, now that i think of it, when i hover over the "Get GT3 Kernel" i get a message about the SD card. Maybe you meant that button to read "COPY GT3 Kernel" ?? If that's the case, then it would have to be moved to the tools section.
But first DEV, it has to download the Kernel which it's not doing right now. Unless I'm doing something wrong.
I'm sorry about the issue that you're having.. I am going to look into it in just a few minutes. I will release an update tonight for you.
Sent from my iPhone using Tapatalk
treetop777 said:
NP DEV. Will you put out an update? Cause for sure the version i have DO NOT download the Kernel and also, i don't see the "Copy GT3" you mentioned.
You know, now that i think of it, when i hover over the "Get GT3 Kernel" i get a message about the SD card. Maybe you meant that button to read "COPY GT3 Kernel" ?? If that's the case, then it would have to be moved to the tools section.
But first DEV, it has to download the Kernel which it's not doing right now. Unless I'm doing something wrong.
Click to expand...
Click to collapse
I have uploaded version 1.0 now, and have fixed the bug in the Kernel download method that I was using.
Please try the new version, and let me know if that fixes your problem(s)!
Once you click "Get GT3 Kernel," it will download the kernel zip, and place it into the current directory of the GalaxyTab3_Toolkit, then the button will rename itself to "Copy Kernel." Click that, and it will ask you if you'd like to transfer the kernel zip over to /sdcard/ on the tablet. Click yes, then once it finishes, click Reboot Recovery, and you will be able to install the kernel zip file from there.
Worked EXACTLY as expected! Downloaded GT3 then pushed it to the internal storage then rebooted into TWRP. After flashing GT3, rebooted into system and the tab is running smooth. No glitches, no problems. What more can i say - flawless!
It's nice to have all these procedures all in one place.
Thanks!
treetop777 said:
Worked EXACTLY as expected! Downloaded GT3 then pushed it to the internal storage then rebooted into TWRP. After flashing GT3, rebooted into system and the tab is running smooth. No glitches, no problems. What more can i say - flawless!
It's nice to have all these procedures all in one place.
Thanks!
Click to expand...
Click to collapse
Great! I am going to work on making everything a bit easier for everyone to understand, thanks to your input!
I'm glad everything worked for you
Sent from my SM-T310 using Tapatalk
Looks awesome going to give it a shot, lets see if this meets my needs.
Using it now but why no philz recovery?
Update....
Worked great thanks.
One small issue was having to put the device into download mode manually. I was getting an exception error about no root when I chose the reboot download button.
Once philz was installed, I used his root option and then installed supersu and Staricson busybox using smart install. Device is now rooted and I can start modding.
Thanks !
Small recomendation.. allow for the app to use or not use system proxy. Also, app should have an option to not always be on top.
CodeJACK said:
Using it now but why no philz recovery?
Update....
Worked great thanks.
One small issue was having to put the device into download mode manually. I was getting an exception error about no root when I chose the reboot download button.
Once philz was installed, I used his root option and then installed supersu and Staricson busybox using smart install. Device is now rooted and I can start modding.
Thanks !
Small recomendation.. allow for the app to use or not use system proxy. Also, app should have an option to not always be on top.
Click to expand...
Click to collapse
Well, I haven't had the chance to test Philz recovery out just yet, I only included the tools that I have personally tested.
I am going to add an option for all of the updated recoveries that support CM10-CM11! Also, I will add an option to allow it to not always be on-top, too!
I will look into the root-required Download Mode reboot, but it would always fail to reboot into Download Mode for me if I didn't run it as SU.. I'll see what I can do to fix it, because I know that it doesn't require root through a regular shell.
Thank you for your feedback!!
Sent from my SM-T310 using Tapatalk
duh... i was working on a toolkit :cyclops::cyclops: but anyways this looks awesome :fingers-crossed:
Nice all in one root package. Thanks a lot...
Sent from my SM-T310 using XDA Premium 4 mobile app
Does this toolkit also works with T311 (Tab3 8.0 3G)?
Gesendet von meinem SM-T311 mit Tapatalk 2
OllerLoewe said:
Does this toolkit also works with T311 (Tab3 8.0 3G)?
Gesendet von meinem SM-T311 mit Tapatalk 2
Click to expand...
Click to collapse
I don't have a T311 to test with, but once I get everything implemented that I want for the T310, I will try to add functions for the T311 for you!
Any love for the t315 4g version?
I've updated to version 1.1 guys, please check the changelog in the original post for more information!
@gx3k - no, I'm sorry, no support for T311 or T315 yet! I think everything is now good with the T310, so I will start working on the other two now!
@Phil3759 & @gr8nole - I added your recoveries to my project, and have hosted them on my server as well for a direct-download method. If this is a problem at all, please let me know and I will remove them asap! Thank you guys for all of your work
Superb!
Echoing what others have said, nice to see everything in one place, had my Tab rooted within ten minutes, thanks for the tool!
Motorola Stock Kernel with f2fs patched and kcal added
Disclaimer: Your warranty is now void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Why this kernel exists:
As many of you know, there is a bug with the f2fs filesystem in the stock kernel which makes it nearly impossible to use systemless modifications (SuperSU, Magisk) on the Moto Z Play. The flaw and its solution are described here.
I started this project for myself to be able to use systemless modifications again, but I hope some of you will find it useful as well. The kernel for Android 6.0 is based on Motorolas source code release (MPN24.104-44) from here and includes security fixes up to december 2016. The Android 7.0 kernel is based on release MMI-NPN25.137-15 with patch date 2017-01. It has been developed and tested with the European model and ROM, but should work on other variants as well as all retail models share the same boot image.
As of patch level 2017-03, Motorola included the f2fs fix in the official kernel. However, I will continue to work on this kernel for those of you who need the verifiedbootstate patch and kcal.
Warning
This kernel is not meant for 7.1.1 and will break your camera and probably more! Once Motorola release the source code you will find an update here.
Features:
f2fs patched to allow systemless modifications to work
kcal color control
Thats all for now, let me know if you need something else ...
Instructions:
If you previously rooted your phone with the chinese TWRP in system mode I would advise to un-root the phone from the SuperSU app and restore a factory image. However, deleting userdata is not necessary except for the SuperSU app. It might not recognize the new systemless mode otherwise.
Optional, unroot via SuperSU app
Reboot to boatloader / fastboot mode
Flash modified TWRP image Flash @Alberto97 latest TWRP from here
Reboot directly into recovery
Optional, remove forced encryption (see below)
Check with TWRP file manager that /data/.supersu is not present, otherwise delete the file.
Flash kernel zip
Flash SuperSU
Reboot the device
Remove forced encryption (optional):
Download attached RemoveForceEnc.zip
Flash file from TWRP
Wipe userdata (in TWRP or use 'fastboot erase userdata' in fastboot mode)
Credits:
Thanks to @Alberto97 for his work on addison.
Thanks to @erfanoabdi and @ryzion for the RemoveForceEnc.zip found on the Moto Z forum (in this post).
@fortunz for testing kcal functionality
Download:
03/22/2017 - Android 7.0.0 Kernel v03: Mega
03/23/2017 - Android 6.0.1 Kernel v03: Mega
Archive:
Modified TWRP: androidfilehost No longer needed, flash latest TWRP from @Alberto97
02/18/2017 - Android 7.0.0 Kernel v02: androidfilehost, Mirror: Mega
02/02/2017 - Android 6.0.1 Kernel v02-test: androidfilehost
01/28/2017 - Android 6.0.1 Kernel v01: androidfilehost
Sources: Github
Changelog:
03/22/2017 | 6.0.1 / 7.0.0 | v3
Added kcal color control. Patch
02/18/2017 | 7.0.0 | v2
Remove verifiedbootstate flag to pass SafetyNet checks. Patch
02/17/2017 | 7.0.0 | v1
Initial release for 7.0
02/02/2017 | 6.0.1 | v2-test
Test build to pass safetynet checks. Removes verifiedbootstate flag. See this patch
01/28/2017 | 6.0.1 | v1
Initial release based in MPN24.104-44 and security bulletins up to december 2016
Is it just enough to flash the sprasechunks ? Is there any need to delete userdata?
Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.
tomparr said:
Yeah, system sparsechunks should be enough. Additionally, make sure the file '/data/.supersu' does not exist. There was one guide which required the file to force system mode for supersu.
Click to expand...
Click to collapse
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.
flashallthetime said:
Great job, it worked, I flashed the lastest SR3-supersu without any issues:good::good::good:
Ran into a bit of trouble, everything flashed without any issues but when I went into the SuperSU APK " no binary is installed" so it seems even though I did flash the sparsechunks , you may need to delete user data.
I was already rooted with the SuperSU that I extracted from the Chinese TWRP.
Click to expand...
Click to collapse
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?
Thanks a lot OP, I've been waiting for something like this. I'll give it a go.
tomparr said:
Thanks for testing. Have you tried to delete SuperSU and its app data and flash SR3 again?
Click to expand...
Click to collapse
No I didn't.
Edit: You need to also re-flash the kernel as well as the sparsechunks. It works and I'm rooted with SR3.
Sent from my XT1635-02 using XDA-Developers Legacy app
Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
regards
So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app
elgringoloco77 said:
So if a install this i finally will be able to install adaway? Cause with the root i have i just cant
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, running AdAway (and Titanium Backup) was the main reason I started building the kernel.
iron maiden said:
Hi I have stock reteu with this version twrp of alberto and root with super his SR3 2.79 is this for me? Thank you
regards
Click to expand...
Click to collapse
Depends, if you are ok with system mode root, you don't need this.
tomparr said:
Depends, if you are ok with system mode root, you don't need this.
Click to expand...
Click to collapse
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards
iron maiden said:
Hello and how can I know that I do not need this? What is the advantage of doing those steps? I do not know if you understand me, I feel my English, thank you.
regards
Click to expand...
Click to collapse
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Main advantage is that Magisk is supposed to work, and that f2fs is working properly.
Systemless root already does work fine using phh superuser without this kernel.
To have AdAway functionality - which systemless needs SuperSU or Magisk, both don't work without this kernel - you may use dns66 which does not modify hosts, but instead runs a local DNS server. It has very similar functionality and doesn't even need root.
I'd like to have f2fs working, but currently don't have the time to do backup, restore in twrp doesn't work maybe because of broken f2fs, do 4 times update etc. This kernel probably will help me and I thank you very much for publishing it. We'll see when I find the time to test it.
tomparr said:
Hi, the advantage of this method is that the /system partition is not modified. This makes OTA updates much easier.
Click to expand...
Click to collapse
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification
iron maiden said:
Hi and what flash of these? Does magisk work to hide root in some applications? Do I have to reinstall the firmware before doing this process?very thanks
Flash SuperSU / Magisk / Systemless modification
Click to expand...
Click to collapse
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?
iron maiden said:
hello what supersu, magisk and systemless I have to install
I have the house z I have reflated the stock now would be good time to install this system no?
Click to expand...
Click to collapse
You can use the regular SuperSU and Magisk versions from here and here.
tomparr said:
You can use the regular SuperSU and Magisk versions from here and here.
Click to expand...
Click to collapse
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
Unistalled Sr3 v279 and installer phhsupersu
regards
iron maiden said:
Hi, okay, this system is running smoothly. And that twrp? thank you very much @tomparr
Something has failed? Install magisk 10.2 and sr3-supersu-v2.79 thanks
regards
Click to expand...
Click to collapse
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.
tomparr said:
Root and Magisk look fine. The SafetyNet test is required for Android Pay and other "secure" apps. From what I read, it can fail on newer versions when the bootloader is
unlocked. I found a temporary patch for the kernel in the OnePlus forum which might solve it. I'll prepare a test version for you soon.
Click to expand...
Click to collapse
Hello ok very very thanks for job
regards
UnBloatMi - Xiaomi MIUI Bloatware Remover
I have been searching for a script to remove Bloatware from my Xiaomi Mi5s, and found a couple of different ones that do part of the job.
None were exactly what I was looking for, so I wrote a script of my own.
Although I tested the script on my MI5s only, it should be very usable for any Xiaomi device running MIUI 7 or 8.
In UnBloatMi I have combined multiple lists of MIUI 7 and 8 apps that should be safe to remove.
It also contains a couple that are less safe to remove, but the script will ask for confirmation before removing those.
Which is a big difference from other scripts; you get to choose what to remove and what to restore!
Backup location:
If you edit the script, you can change the backup location to use (by default "/sdcard/UnBloatMi")
You can of course also add more apps to remove to the list in the script. (instructions are in the comments)
It's not needed to remove files from the list, as it will not process files that are not on your device, and you can choose not to remove any app.
To Customize the Script:
Unzip the zip and edit the file under: META-INF\com\google\android\update-binary
This script is written in shell language (sh), so editing is somewhat different from "normal" EDIFY scripts that use the "updater-script" file.
I used part of the excellent template by osm0sis to create UnBloatMi
Install Custom Apps/Files:
You can also have the script install Custom files to /system folder. (So you can add another HomeLauncher, for example)
To have the script install Custom files, just add them to the Zip in "/system/app/" folder:
/system/app/YourCustomApp1/YourCustomApp1.apk
/system/app/YourCustomApp2/YourCustomApp2.apk
The script will automatically install them for you.
To use the Script:
You need to have TWRP Recovery installed.
BACKUP YOUR DEVICE BEFORE RUNNING THIS SCRIPT!!! (I recommend using TWRP Backup)
(even though the script allows you to restore your changes, something can always go wrong - press wrong button for example)
- Move the ZIP file to your SDCard, and install using TWRP Recovery
Basically, you can just follow the instructions on the screen, by pressing Volume buttons.
- The first run, you'll be asked what apps to remove. Backups are automatically made.
You can confirm each app, or choose to only confirm the more risky apps.
- If you run the script again (after testing your installation), it will detect the backups from the previous run.
You can then choose to restore the backup files, or delete them from your device.
- You can now also create a default UnBloat list, that can be used to UnBloat after flashing a (new) ROM.
It is created by checking for installed apps. If an app is not found on the device, it's added to the list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feel free to edit and change the script.
If you make any improvements, please let me know so I can add them to the script.
This includes reporting what apps caused problems when removed, or comments about apps.
You can find the script in: /META-INF/com/google/android/update-binary (or on GitHub by clicking the "Source Code" link below)
Instructions can be found in the comments of that file.
--UPDATE--
Added Step by Step Restore: You can now choose which apps to restore, so it is easier to troubleshoot your installation.
--UPDATE v0.2--
Added warning to SecurityCenter App (so it has to be confirmed). It caused bootloop on my device when removed.
--UPDATE v0.3--
Bugfixes, Added Apps, changed and added some app comments. Changed download link (GitHub download creates a folder too many)
--UPDATE v0.4--
Changed/Added menu's - Allows you to do more actions at once
Added apps and comments.
Added ability to save a default UnBloat list. This can be used to UnBloat after flashing a ROM.
Download
Source Code
Unfortunately I got an error (missing files) under TWRP 3.0.2
luxim said:
Unfortunately I got an error (missing files) under TWRP 3.0.2
Click to expand...
Click to collapse
I'm using TWRP 3.0.2 as well...
Did the install reach the menu at all?
Can you look at the log file to investigate? (TWRP --> Advanced --> Copy Log --> Open log file from your SDCard)
Zappo said:
I'm using TWRP 3.0.2 as well...
Did the install reach the menu at all?
Can you look at the log file to investigate? (TWRP --> Advanced --> Copy Log --> Open log file from your SDCard)
Click to expand...
Click to collapse
Here it is. My recovery is the ZCX one and I wasn't able to enter the menu. I'm running the latest xiaomi.eu developer.
luxim said:
Here it is. My recovery is the ZCX one and I wasn't able to enter the menu. I'm running the latest xiaomi.eu developer.
Click to expand...
Click to collapse
Thanks for your bug-report and logfile!
It says it couldn't find the script, and after investigating I found the download link to GitHub creates a folder too many inside the zip.
I was hoping to have the available download automatically give the latest version...
I guess I'll have to create a release after every update, and update the link accordingly...
I adjusted the download link in the original post.
this is great! i made my own debloater script, but your is so much more elegant! i hope things dont change much when we update to 8.2....
wurstel said:
this is great! i made my own debloater script, but your is so much more elegant! i hope things dont change much when we update to 8.2....
Click to expand...
Click to collapse
I have just released version 0.4, which allows us to create a default UnBloat list.
This can be used to UnBloat again after flashing a new ROM.
(I'm hoping to use this in combination with OTA updates. I'll write a howto if I manage to get this all to work)
Thanks, i try it...
EDIT: i have removed many apps on my rn3se (kate), wipe davilcache but i've a bootloop :?
Good restore option
Hey @Zappo, did you already get the update to 8.2? Will you be updating the script for the new miui?
wurstel said:
Hey @Zappo, did you already get the update to 8.2? Will you be updating the script for the new miui?
Click to expand...
Click to collapse
I'm running the MIUI Global ROM 8.0.3.0....
As far as I know, no updates yet...
If anyone knows of new or other Bloatware, I'll update the script accordingly.
samurri said:
Thanks, i try it...
EDIT: i have removed many apps on my rn3se (kate), wipe davilcache but i've a bootloop :?
Good restore option
Click to expand...
Click to collapse
If you have found the app causing your bootloop, please let me know. I'll add it to the risky apps list.
I use the "restore one by one" option, and try to find the problem-app that way...
Zappo said:
If you have found the app causing your bootloop, please let me know. I'll add it to the risky apps list.
I use the "restore one by one" option, and try to find the problem-app that way...
Click to expand...
Click to collapse
Hi.
Big thanks for your hard work. At this moment i have personalized your list but i think that velvet.apk is a possible problem
This "# The file number doesn't have to be in order, but should be unique." is no true otherwise the script does not work well (es.: items 0-1-3-4)
samurri said:
this "# The file number doesn't have to be in order, but should be unique." is no true otherwise the script does not work well (es.: items 0-1-3-4)
Click to expand...
Click to collapse
You are both correct and wrong; they don't have to be in order, but do have to be ascending without interruptions (can't have missing numbers)
Ex: items 0-1-3-5-4-2 is OK.
I didn't think it would be a problem, as items don't have to be removed...
I will review your list, and add a comment to velvet.apk when I have the time. (however it didn't cause any problem on my Mi5s)
Ok, thanks.
Do you know where can i find mi apps description?
samurri said:
Ok, thanks.
Do you know where can i find mi apps description?
Click to expand...
Click to collapse
I've been Googling for those quite a bit...
It's hard to find good descriptions for those.
Zappo said:
I've been Googling for those quite a bit...
It's hard to find good descriptions for those.
Click to expand...
Click to collapse
No sorry, velvet is ok but it's need a litlle of attention.
EDIT: install /system/custom1/custom1.apk is impossible
hey @Zappo is this debloat script working for china stable?
wurstel said:
hey @Zappo is this debloat script working for china stable?
Click to expand...
Click to collapse
Yes, it should work for all MIUI 7&8 devices.
If software in the script is not found on your device, it will be automatically skipped.
samurri said:
EDIT: install /system/custom1/custom1.apk is impossible
Click to expand...
Click to collapse
I agree this kind of got lost in the code...
New software is only installed when removing bloatware the first time (or when no backups are found).
It should be automatically installed when choosing "Remove/Restore bloatware" from the first menu.
However when a backup is present on the device (folder "UnBloatMi" by default), this is skipped...
I did this, presuming new software is installed after the first run, and if a backup is already created it doesn't have to be installed again.
Hey @Zappo , found this project for redmi note 2, and it's so heavily debloated, i haven't seen anything like it. Maybe you can look over it and add a few more things to debloat? I tried to recreate it but I don't know which qualcomm apps are essential to our phone, i had only bootloops... Anyway here's the link https://forum.xda-developers.com/redmi-note-2/development/best-sot-t3434915
Edit: i can provide you with a list of all the contents of the rom, i extracted the system partition.
KingoRoot is annoying. No landscape support and battery lock screen cause my device to freeze. Support took 6 months to reply. I finally found a way to manually replace Replace KingoRoot with SuperSU without a script.
Before you get started, make sure you backup everything. I'm not responsible for any damages in your device.
Tip: You can use root without Kingouser but your device will be in high risk as any apps can grant permissions without your permission. I'd strongly recommended you to follow these steps for SuperSU replacement... or just keep Kingouser
What you need?
- CPU-Z app
- X-plore file manager app or other root explorer apps
- SuperSU flashable zip
- SuperSU app from playstore
Let's get started
Step by step:
EASY WAY - AUTOMATIC SWITCHING:
There is an easy way to switch to SuperSU but the change is low. Please go to page 2 or 3 for more infomation.
1. Delete/Uninstall Kingouser, but keep Kingoroot. DON'T reboot your device
3. Install SuperSU apk from flashable zip v2.79
4. Launch it, press "continue" and "normal" wait until the update is successful.
5. Reboot and uninstall Kingoroot
Thanks MarshisnotMellow for this trick
If this automatic switching fails, try manual switching
COMPLICATED WAY - MANUAL SWITCHING:
This might sounds complicated but I prefer doing it manually than executing a script in Terminal.
1. This is very IMPORTANT: Check your Kernel Architecture of your device using CPU-Z app. I bricked my device by placing wrong binaries for armv6 on a armv7 device by a mistake
In my example, my Kernel Architecture is armv7 so i'm gonna extract armv7 folder later
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Download SuperSU V2.79: https://download.chainfire.eu/1016/SuperSU
Do NOT use v2.82 since it no longer have ability to reinstall binaries (SU binary occupied error), and it have "Android is starting" bug. See this post https://forum.xda-developers.com/showpost.php?p=77303017&postcount=84
In the zip, there are 9 folders. I will list the folder below
META-INF = Signature and script for custom recovery
common = required files for SuperSU/rooting. init scripts are not needed
arm = arm11 / armv6. Devices like HTC Wildfire, Wildfire S, Galaxy Y etc
arm64 = armv8 / armv8l / arm 64-bit. Sony Xperia M5 etc.
armv7 = armv7l. For all popular devices, you know, Samsung S3 mini, HTC, Sony, LG, etc
mips = Unknown. Don't know which device is using mips
mips64 = Unknown. Don't know which device is using mips64
x64 = Unknown. Don't know which device is using x64
x86 = Any Intel CPU. Asus Zenfone, Bluestacks, Android emulator etc.
3. Open X-plore, open confuguraion and enable root access as Superuser + mount writable
4. Extract <Your architecture> and common folder in your device
5. Navigate to extracted folder on left pane and navigate to /system on right pane
6. Now we gonna replace and delete some files in the ROM very carefully! Do the following:
Tip: Press and hold on the file and select permission to change the permission
Skip step 6.1 if you already have SuperSU app installed
6.1. Install SuperSU as system app
Android 4.4.x and below: Copy: /common/Superuser.apk => /system/app
Android 4.4.x and below: Change permission to 644 (-rw-r--r--)
Android 5.0.x and above: Create a folder named "Superuser" or whatever
Android 5.0.x and above: Change permission to 755 (drwxrwxr-x)
Android 5.0.x and above: Copy: /common/Superuser.apk => /system/app/Superuser
Android 5.0.x and above: Change permission to 644 (-rw-r--r--)
6.2. Replace: /common/install-recovery.sh => /system/etc
6.3. Delete: /system/etc/install_recovery.sh
6.4. Replace: /<Your architecture>/libsupol.so => /system/lib
6.5. Rename "su" to "daemonsu"
6.6. Replace: /<Your architecture>/daemonsu => /system/xbin
6.7. Replace: /<Your architecture>/supolicy => /system/xbin
6.8. Delete: /system/app/kingouser.apk and uninstall it from Settings -> App (if it was installed as user app)
After you replace any files, make sure the new file still has the same permissions as the old file. X-plore does this automatically, that's why X-plore is the best file manager. Root Browser doesn't, and you will lost root or get bootloop after reboot. But, you can re-root with KingoRoot and do it again.
There is no need to replace "su" binaries since they are write protected, but SuperSU can replace them once you update it in STEP 8
7. That's all. Reboot your device
8. SuperSU will appear on app drawer. Open it and it will ask you to update the binary. Press "continue" and "normal". The update should be successful.
9. Reboot your device one more time
Now you have a working SuperSU. Enjoy
Tested devices
https://www.dropbox.com/s/q6t8puao1q5746v/Kingoroot to SuperSU tested devices.xlsx?dl=0
Most ARMv7 devices are tested and working. If you have a device with ARM64/v8 or x86, i need you to tell me the system files that Kingoroot have modified so i can find out which files to replace. PM me for more info
Regarding "Android is starting" bug
This is SuperSU 2.82 bug. Upgrade to SuperSU 2.82 r5 or downgrade to SuperSU 2.79 + binaries and use re-signed APK to block update from Playstore
SuperSU 2.82 r5 beta:
- https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
- https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Credit:
Evildog1 (This tutorial)
Chainfire (SuperSU)
Thanks Op for this thread.
I personally use super su but some devices make it hard to so I have to use king root(cough-lenovo-cough)
This is a good idea to do what you have told over flashing the zip as sometimes that can be complicated.
Can't wait to get home and try it out.
Will surely get back to you with device names
Rahul98076 said:
Thanks Op for this thread.
I personally use super su but some devices make it hard to so I have to use king root(cough-lenovo-cough)
This is a good idea to do what you have told over flashing the zip as sometimes that can be complicated.
Can't wait to get home and try it out.
Will surely get back to you with device names
Click to expand...
Click to collapse
This thread is for Kingoroot with o, not Kingroot
Btw, replacing Kingroot with SuperSU failed. I have tried it.
evildog1 said:
This thread is for Kingoroot with o, not Kingroot
Btw, replacing Kingroot with SuperSU failed. I have tried it.
Click to expand...
Click to collapse
Typo?
working in galaxy ace s5830i
Armv6 arch
running cm11
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
OK here is a working list!
ROM:CyanogenMod11 Arch:Armv6
1.Samsung Galaxy Ace-i(S5830i) Code Name=Cooperve
2.Samsung Galaxy Ace(S5830i) Code Name=Cooper
3.Samsung Galaxy Y(S5360) Code Name=Totoro
4. 1.Samsung Galaxy Mini Code Name=Tassave
sohamsen said:
working in galaxy ace s5830i
Armv6 arch
running cm11
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
OK here is a working list!
ROM:CyanogenMod11 Arch:Armv6
1.Samsung Galaxy Ace-i(S5830i) Code Name=Cooperve
2.Samsung Galaxy Ace(S5830i) Code Name=Cooper
3.Samsung Galaxy Y(S5360) Code Name=Totoro
4. 1.Samsung Galaxy Mini Code Name=Tassave
Click to expand...
Click to collapse
Err... are you using CM11 with Kingoroot?
CM11 is already pre-rooted.
evildog1 said:
Err... are you using CM11 with Kingoroot?
CM11 is already pre-rooted.
Click to expand...
Click to collapse
i used kinguser for root management
tried this vulnerability
it works
sohamsen said:
i used kinguser for root management
tried this vulnerability
it works
Click to expand...
Click to collapse
Kingouser or Kinguser?
Work perfectly with my experia e4 dual.
Im just write cat /proc/cpuinfo in terminal for check my kernel architecture. ?
Sent from my E2115 using XDA Forums Pro.
My Kernel Architecture is armv8I. Which one should I select in zip file because there is no armv8I?
Won't this work instead?
Install SuperSU (I used SuperSU Pro) from the play store and grant it superuser access. When prompted, install updated su binary with the normal mode. Once installed successfully, uninstall Kingoroot and Superuser app. Reboot.
That's what I did on an android 6.0 headunit I have and seems to work. But maybe there is a benefit of avoiding kingoroot completely?
kenosis said:
My Kernel Architecture is armv8I. Which one should I select in zip file because there is no armv8I?
Click to expand...
Click to collapse
arm64
evildog1 said:
This thread is for Kingoroot with o, not Kingroot
Btw, replacing Kingroot with SuperSU failed. I have tried it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
here's a guide but needs terminal in order to work.
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
aarick said:
Won't this work instead?
Install SuperSU (I used SuperSU Pro) from the play store and grant it superuser access. When prompted, install updated su binary with the normal mode. Once installed successfully, uninstall Kingoroot and Superuser app. Reboot.
That's what I did on an android 6.0 headunit I have and seems to work. But maybe there is a benefit of avoiding kingoroot completely?
Click to expand...
Click to collapse
seems like a great alt. procedure to me,this should go to OP,if anyone else confirms this?
aarick said:
Won't this work instead?
Install SuperSU (I used SuperSU Pro) from the play store and grant it superuser access. When prompted, install updated su binary with the normal mode. Once installed successfully, uninstall Kingoroot and Superuser app. Reboot.
That's what I did on an android 6.0 headunit I have and seems to work. But maybe there is a benefit of avoiding kingoroot completely?
Click to expand...
Click to collapse
This did not work for me on 4.1.2-5.1.1. SuperSU always say Install failed no matter how many times i tried. That's why i made this guide.
evildog1 said:
This did not work for me on 4.1.2-5.1.1. SuperSU always say Install failed no matter how many times i tried. That's why i made this guide.
Click to expand...
Click to collapse
Strange. Worked for me. Guess I'm lucky.
aarick said:
Strange. Worked for me. Guess I'm lucky.
Click to expand...
Click to collapse
Didn'tâ work for thousands of us! Maybe you updated SuperSU binaries via custom recovery?
Big thanks @evildog1 for this guide!!!
Sent from my Samsung Galaxy S7 using XDA Labs
Phone needs to be rooted in order to replace, right?
Thanks for the detailed post. I once ran across this problem and this will definitely help me with other devices.
kenosis said:
Phone needs to be rooted in order to replace, right?
Click to expand...
Click to collapse
Yes
PalmCentro said:
Didn'tâ work for thousands of us! Maybe you updated SuperSU binaries via custom recovery?
Big thanks @evildog1 for this guide!!!
Click to expand...
Click to collapse
I wish, but I'm using an android mtcd px5 head unit and no one has a custom recovery for it..
I was really just suggesting as an option to try as it worked for me and less complicated.. But guess it's only this device that allowed it..