Q&A for [GT-P31xx] CF-Auto-Root
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 [GT-P31xx] CF-Auto-Root. 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!
Hi,
I 've tried root my GT-P3100 with auto-root but with no success.
I've stock 4.2.2, first wiped all data and did factory reset, then start rooting. After reboot an icon of supersu appears but after run it says "there is no SU binary installed" . I notice that this version is 2.13 with date 2014/10/10. I download it from link in the third post which is described as containing 1.30 version of superSu inside.
I try to reflashing auto-root many times but binary is still missing.
Maybe superSu misversion is a problem? How can i resolve an issue with missing binary?
Thanks for help, &Y
First post : Need personalized root info for GT-P3113
My first post and not sure what I'm doing or if its the right place, please have patience?
I have a 2012 Galaxy Tab 2 P3113 wifi only model. It auto updated from the stock Andy 4.0 to Andy 4.2.2. Im unhappy with this and Samsung tells me its irreversible. That makes me even more unhappy as, better or worse, its not the same 'user experience' for which I chose the device. Therefore I'm interested in 'rooting' it. My objective is to tweak the interface, disable some of the auto updating and some of the autostarting Samsung software and services (also some phone apps and services) which I will never use and manage autostarting of user installed apps. I would also like the ability to make complete 'single click' backups which include screen/'desktop' arrangements and app settings (such as one would make with a Windows system). I am NOT interested in loading custom ROMs or other modified system ware.
1 Is 'rooting' my solution?
2 Is it reversible?
3 Will it do anything more than unlock the existing system - what modifications will the rooting process make?
4 Will 'unrooting' reverse my settings alterations or can I disable the Samsung ware, and relock the system for safety/security? Will changes such as power or mem settings made by 'root only' apps remain in place after unrooting?
5 Is a 'temporary root' a better solution for me?
6 Has the aforementioned Samsung update made the root process any more difficult or hazardous?
7 Will just rooting leave a permanent detectable trace?
8 Can someone give me the simplest step by step procedure and reversal procedure? I realize this is covered in many places throughout these forums, but this will be my first attempt at raiding a Android device and I would be more confident with a personalized procedure that I can ask questions about and get direct device specific answers to.
I've been having trouble finding straight info about performing a ROOT ONLY. To reiterate I only want enhanced control over the EXISTING system, primarily to prevent autostarts, to positively terminate running apps and to make full image backups - I do NOT want to install modded systems or irreversibly or significantly alter the existing system.
I appreciate any clear info or advice I can get. Thank you.
Rooting Help
Hi I have a Samsung Galaxy Tab 2 7.0 GT-P3113 Jellybean 4.2.2. I have tried the CF Auto Root Method 6 times and it doesn't work. Odin says that it passes and that it worked but when the tab reboots, I try to open SuperSU but it says "There is no SU binary installed! and SuperSU cannot install it. This is a Problem!" Help me please! I know I am doing it right aren't I?
Help. Samsung Galaxy tab
i don't have much experience on rooting, i have only rooted 2 phones and worked. plus this tablet.
so i have a Samsung galaxy tab 2 7.0 GT-P3113 (IR blaster/wifi) at 4.2.2 JB
i tried rooting it with the ChainFire auto root tar.md5 file which is for GT-P3113 on Odin3.07 and odin detected my tablet, but showed it as blue
but seeing it different from Odin1.87 it worked and PASSED! by odin so i flashed it in download mode, on PDA, everything was looking normal,
after the loading on the download mode it went to where the Red pirate guy was shown and after that it rebooted.
i had the SuperSu application when i opened my tab which i didn't have before rooting so i downloaded a couple of root checkers from play store,
here comes the problem,
when i click SuperSU it says "There is no SU binary installed and SUperSU cannot install it. This is a problem!"
and when i check it with a root checker it says no Root Access so i think somehow i failed rooting.
but when i check the Build info via root checkers:
Device: espressowifi
Hardware: espresso
Product: expressowifiue
and it says on SU (info i saw on root checkers):
su found
[/system/xbin/]
i want to try to flash the tar.md5 auto-root file again with odin can i do it again? will it somehow stack the root or i don't know, be a risk for my tablet? or is there a fix to this?
Thank you.
Related
Ok, i watched your sign-up video, i read the READ BEFORE POSTING posts, i searched the search, and there is NOT ONE STRAIGHT answer to the most obvious and common issue: su binary update.
There is no official thread titled "su binary" which would be NICE if somebody post a link to the latest version of su binary, tells people which version of Superuser app it is compatible with (i know there's at least 3, CWM, ChainSDD, and Chainfire) I cant even google this binary. I cant even tell if somebody is developing on this binary.
I just don't understand how nobody brought up this issue in any manner. Nobody asked whether the binary code is available in the market, needs to be downloaded from the web and flashed on the phone, etc. In worst case scenario, if su binary is discontinued, then just say "It is no longer supported. Forget about rooting from now on."
I have T-Mobile GS4 (SGH-M919) running Android 4.2 baseband UVUAMDL, i rooted the phone using MotoChopper that gave me Superuser app by CWM.
If you can be ANY help, please reply with some kind of answer that somebody can actually understand. If you have no clue about a single word i just posted, there you go. There is no answer to this "su binary" issue, so forget about rooting and what not. Save your soul from googling 5 hours a day here and web, looking for answers that no one ever asked.
You're very welcome.
Superuser update
Cowls192,
There are a couple of ways to update SU ... I can share at least two ways.
1) If you have experience using Terminal and can get a hold of the updated SU binary, then you can simply copy it to
the appropriate place. I forget whether the location of the original SU binary is under the /sys or /system folder.
2) I'm quoting from DroidXForums here so take it for what it's worth ..
"The new superuser : su v2.3-ef can also be downloaded from the Google market."
I hope that this small bit of information shows you that the answer CAN be found with patience.
Lacking patience ... this IS a great place to find help!
If you found this to be of help, please condiser clicking the THANKS button.
Solidified
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
cowls192 said:
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
Click to expand...
Click to collapse
Hi. Im a noob and I am trying to update the su binary. I have a galaxy tab s. I just recently did the super su root but I cant. It installed correctly but the binary won't update. I've searched the Web but no clear answers. I've checked if the root is installed correctly and its not. I don't know where to look for any help is greatly appreciated.
Hello.
Same situation here...
Can't update bynary in SM-T700 - 5.0.2 LP...
me too...
me three.....I can,t update....
I used kingroot app, then superSU-ME, and superSU told me to update the su binary.(Another superuser app told me that my binary still remained "kinguser_su(348)")
Same here, from a nexus 6p
I have a Nexus 6p which I thought was already rooted, but when I used the root checker, it says my phone isn't properly rooted. Also, when I try running Super User it keeps saying that I'm missing the su binary or that it needs to be updated. I have no idea what the next step is now. Can someone help me figure out what I need to do?
Dg60069 said:
Hi. Im a noob and I am trying to update the su binary. I have a galaxy tab s. I just recently did the super su root but I cant. It installed correctly but the binary won't update. I've searched the Web but no clear answers. I've checked if the root is installed correctly and its not. I don't know where to look for any help is greatly appreciated.
Click to expand...
Click to collapse
idioleat said:
me three.....I can,t update....
I used kingroot app, then superSU-ME, and superSU told me to update the su binary.(Another superuser app told me that my binary still remained "kinguser_su(348)")
Click to expand...
Click to collapse
Those still having trouble ensure your device is rooted and also if su still can't install binary try another version some versions have trouble installing binary.
cowls192 said:
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
Click to expand...
Click to collapse
POST FOR EVERYONE WHO HAS TROUBLE FINDING/UPDATING THE BINARIES:
1. The SuperSU app version number corresponds to the su binary version. To check the version of the su binary go to Settings --> Apps --> SuperSU and look at the version number.
2. SuperSU app will push a notification if the binary needs to be updated.
3. You will also see a popup window once you open the SuperSU app in case there is a new version
4. To be sure you have the latest version you can follow one of the links below which will have the download for the latest recovery-installable zip that will root and install the SU app along with the latest binaries:
Stable (recommended): http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
5. There is a thread dedicated to binary update problems. You will have more luck there: http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365
6. Also remember to visit the official post for any future updates and extra info: http://forum.xda-developers.com/showthread.php?t=1538053
NOTE: In most cases you have to update the SU app to get the latest binary version.
janekmuric said:
POST FOR EVERYONE WHO HAS TROUBLE FINDING/UPDATING THE BINARIES:
...
will have the download for the latest recovery-installable zip that will root and install the SU app along with the latest binaries:
Stable (recommended): http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
It is exactly how I'm doing and every time get: "binary update unsuccessful"
Sent from my E2303 using Tapatalk
pawwaap said:
It is exactly how I'm doing and every time get: "binary update unsuccessful"
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
Then you didn't root properly. Try different root methods or re-root your phone.
So.. After a whole week trying to find a succesful way to root this f***ng phone, no success has been found.
I couldn't find this phone's section on XDA so I'm posting this on the general section...
If anyone could give me the link to the section, it would be very appreciated.
This is the phone:
Samsung Galaxy Trend 3 - SM-G3502C
Android Version: 4.3
Build Number: JLS36C.G3502CZCUAOD1
I have tried a number of on android apps, windows software, and even tried rooting manually by adb and linux. But couldn't have a single successful attempt or any signs of progress made...
Can anyone help me out with this phone, the reason I need root is because this is a chinese phone and doesnt have Play Store installed, and I need root access to install Play Store on /system/apps/ and give R+W permission...
Apps tried:
Saferoot
Kingo App Root
iRoot (vRoot/Root Master)
OneClickRoot
TowelRoot
A bunch of .bat rooting scripts
Baidu in-app Rooter
Rooting through ADB (everything was going fine until I had to access Ubuntu's Nautilus, to move the files to /system/ but the device wouldn't mount by MTP on download mode, and I couldn't access the files) link to the guide followed: http://forum.xda-developers.com/show....php?t=2684210
Any help would be truly appreciated, and If there is a way to install play store without the need of root access, or even a good replacement for play store would be really good.
Also, I have 0 experience on custom recovery, so, If any developer out there could create a custom recovery for this phone, I could give them the recovery.img from this phone and modify it to work on this phone. If that's the way it works, idk XD.
P.D. I already opened a thread on XDA-Assist but sorry, I had to move it, I saw that every post on that section had little views and replies and I was worried that this would happened to me on that section to me too. I'm ok if I need to erase it from there but I would like to leave it there for some time if there is any replies.
Link to the thread: http://forum.xda-developers.com/general/xda-assist/samsung-galaxy-trend-3-sm-g3502-rooting-t3106250
Hi, still you right~ looks like your are really can't to wait to root your device. Just try KingRoot, we just release new version which can root device from Android 2.x to 5.0. I can't give you promise, but just have a try~ good luck
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)
Ota - lmy47v1218_2217
For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.
I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.
Uninstall Xposed (moar hacks)
/system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
/system/etc/permissions/platform.xml (sd card "fix")
If trying to address the issues manually does not work, follow the procedure below.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update
General Notes - Lolipop
Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
SD cards bigger than 32Gb still do not work correctly on stock firmware
Known Working Customizations
To be determined
KitKat Notes
All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)
Sources / Mirror(s)
The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/
Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45
Do you trust Kingo?
I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
kemonine96 said:
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.
Click to expand...
Click to collapse
tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Components to clean up?
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
kemonine96 said:
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse
tomzweifel said:
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.
New OTA Update
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
tomzweifel said:
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.
kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.
Will post back with more info after I've had some time to poke at the OTA some.
Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.
Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.
In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.
Happy hacking and OTAing everyone.
kemonine96 said:
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device
Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?
Okay so I've had this phone for little over 10 months now and within that time I've managed to achieve root (unreliable but it works at the very least) in that time as well as learned a fair amount about Linux and android alike (Not a whole lot but I know some stuff) though I've now come to the point of I actually want to give my phone a proper root instead of this faulty solution I have currently. I (barely) managed to get my phone rooted using Kingoroot and I've played plenty with my phones' innards in that time, removed system apps, added my own selection to the system but some apps in my phone that use root don't work even with root permission granted which is why I'm wanting to replace Kingoroot with ChainFires' SuperSU binaries, could anybody help me with simple instructions for someone who doesn't actually know very much regarding how root and SU bins work inside of android? My phone's using 4.4.2 kitkat.
Just a few disclaimers first to get misconceptions out the way:
1. I do not have a custom recovery nor is one available for my phone (Samsung galaxy young 2 (SM-S130H) for those who want to know)
2. I'm currently unable to use the internet on my phone as I lack Wi-Fi to do so (router is dead) so I'm manually installing app packages through ADB, so if something needs an internet connection on my phone it's not going to work for me, for now..PC still has net access.
3. I have access to ADB shells' SU but not ADB root so I hope you don't need that from me.
4. This phone does not have a fastboot mode. (That I can find anyway..) Only a download mode from what I've found.
Can anybody help me out with telling me what I'll need to be doing in regards to getting this done?
Hi Mc Fow1er
Thank you for using XDA Assist
As we do not have an specific forum dedicated for your device yet, our experts at the below forum should be able to help you. Please be welcome to post over in there.
Android Q&A, Help & Troubleshooting
Nice regards and good luck.
.
Mc Fow1er said:
Okay so I've had this phone for little over 10 months now and within that time I've managed to achieve root (unreliable but it works at the very least) in that time as well as learned a fair amount about Linux and android alike (Not a whole lot but I know some stuff) though I've now come to the point of I actually want to give my phone a proper root instead of this faulty solution I have currently. I (barely) managed to get my phone rooted using Kingoroot and I've played plenty with my phones' innards in that time, removed system apps, added my own selection to the system but some apps in my phone that use root don't work even with root permission granted which is why I'm wanting to replace Kingoroot with ChainFires' SuperSU binaries, could anybody help me with simple instructions for someone who doesn't actually know very much regarding how root and SU bins work inside of android? My phone's using 4.4.2 kitkat.
Just a few disclaimers first to get misconceptions out the way:
1. I do not have a custom recovery nor is one available for my phone (Samsung galaxy young 2 (SM-S130H) for those who want to know)
2. I'm currently unable to use the internet on my phone as I lack Wi-Fi to do so (router is dead) so I'm manually installing app packages through ADB, so if something needs an internet connection on my phone it's not going to work for me, for now..PC still has net access.
3. I have access to ADB shells' SU but not ADB root so I hope you don't need that from me.
4. This phone does not have a fastboot mode. (That I can find anyway..) Only a download mode from what I've found.
Can anybody help me out with telling me what I'll need to be doing in regards to getting this done?
Click to expand...
Click to collapse
1. I have a Samsung galaxy s7 SMG930F with the chainfire root method. When I want to update to android 7, can i then still use the same root method for the phone, but which was written for android 6?
2. When I just take the stock firmware , which was not written for any specific phone, can i then use my real home button from Samsung and so on?
3. My phone has very strong security, so that xmodgames and cydia substrate can not work on my phone. Is there anyway to make the security of the phone more weak?
4. Is there any method to hide root without cydia? (because hide my root and rootcloak both use cydia)
Pls don't say thats the basic stuff and everyone knows it. Pls just answer, because I don't know much about root!
for my galaxy s7 SM-G930FD
i followed the following trails and got root
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
https://www.youtube.com/watch?v=nlj76YvxGYo
http://www.stechguide.com/install-twrp-recovery-and-root-galaxy-s7-edge/
Pls real answers to my questions, not just how to root the phone, because i have already rooted it!
i'd think it wouldn't be easy to tell if a future update (e..g. version 7) would be able to work with the current version of root apps. / method i.e. there is not enough info (perhaps a true version 7 rom does not even exist). i'd guess what would be likely though is that when version 7 is released, different version of root apps (and even method) etc may be necessary.
i went with the TWRP approach as TWRP is based on 'recovery', i.e. install su and super su through the recovery via a zip file.
this procedure provides more 'control' over how root is obtained and i'd guess it may allow one to troubleshoot the steps say in a situation a new rom or update is provided. a side benefit is that u could update the super su via TWRP recovery with and updated zip version rather than to await a next cfautoroot package for instance