I am running the latest Madhi ROM along with AK Kernel and SuperSU 2.16. I am having an issue where the root prompt is not being shown. I have uninstalled and reinstalled SuperSU and initially the grant root privileges prompt is shown for some apps that require root. However, if I reboot or wait a period of time and then check for root, the prompt is not being displayed. If I uninstall/reinstall SuperSU the same process holds true - prompt initially shown, then after a little while the prompt will not be shown (for new apps requiring root and/or root checker).
If I go into SuperSU and change the settings to "Grant" rather than "Prompt" all the apps are granted Root Privileges. Almost like something is blocking the prompts from being displayed.
Thanks.
Related
My device is rooted with SuperSU and my Application when device bootup will start immediately. But after bootup my Application can not run su command, I saw my Application process running before SuperSu process run. If I close Application and start again it will run as well. Anyone can help me find solution for that?
Hi, first of all this is my first contribution to the forum. I've been using the resources until now but i wanted to contribute with something. This is not my development, and only gathered the information and put it here, so thanks to all the guys who help me in the first place.
I bought the Homesync waiting more from the device, and i now the device has so much potential but has been wasted for samgsung, they havent give a real update to the device and they left it at Android 4.2.2, with little support to apps in the store, with no suppor for multiwindow, and other things they could make for this device to success. Well, what we can do i to root it so we can gain access to other apps, and apps from independent markets or developers.
Requeriments:
1) Set your devide to a MJ3 ROM, either updating it or downgrading it from a stock ROM. You can get it from sammobile here http://www.sammobile.com/firmwares/3/?download=24442. I had to use Odin to downgrade to Stock Rom MJ3. If you dont know how to use Odin, in the same link you can read how to do it. Why MJ3? Because that ROM is working with root process im doing here.
2) After with the MJ3 ROM up and running. From your PC, do the following: download the superuser folder from the attachment below.
3) This part is thanks to the user K1MU, you can see his work here http://forum.xda-developers.com/showthread.php?t=2565758 ,before you try using this rooting program, you'll need to have the USB drivers installed for the homesync. Download here if you cant see your homesync when connected to the microUSB port.
http://developer.samsung.com/android/tools-sdks/Samsung-Android-USB-Driver-for-Windows;jsessionid=1cG8Jw2NLJgzwXpG3RhBjQ5tQLGMQTVw2xwJxQld0yyKlG6psQ1W!-2096422745
4) The next thing you must do is to enable USB debugging on your phone. Go to "Settings", "More...", then "Developer Options".
If "Developer Options" doesn't appear, then you'll need to enable it - go to "Settings", "More", "About Phone". Scroll down so the "Build Number" is visible, then tap on that several times until developer mode is enabled. In Developer Options, make sure "USB Debugging" is checkmarked.
5) Make sure that your computer is allowed to use USB debugging on your homesync. To do this, unplug your phone and unlock it. Then, plug in the USB cable. If you see an "Alllow USB debugging?" window pop up, tap on the "Always allow from this computer" to check it, then tap OK. If you don't see that popup, it's OK, you should be OK to proceed. This is going to appear in the Homesync.
6) Then you need to unpack the attached ZIP file somewhere onto your PC. You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
7) Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
The first thing that the install script will ask you is whether or not to install Busybox. Busybox is a program that provides a fairly extensive set of Linux shell utilities that a Unix user would expect to see. If you're not going to be using the shell (terminal emulator or adb shell) then you may not want to install Busybox. You may, however, find that some root-required utilities assume that Busybox is installed. If SuperSU asks you to update the su binary, choose the "Normal" method. If SuperSU asks you about disabling Knox, allow it. This exploit will NOT set the Knox Warranty Void flag. It will set the "Custom" flag, but that's nothing to worry about. While you're running this, you'll need to keep the phone awake and watch both the computer running the rooting script and your phone. You shouldn't unplug the phone unless you're prompted by the rooting script. Leave it connected until it's done.
8) In this point you will be rooted and ready to boom your Homesync.
I think i will be expanding this post, but for now this is it. Everything works fine with the phone using the homesync app.
Root Samsung Homesync gt-b9150
Hi everybody, Samsung homesync is root with Kingroot, that´s all, thanks/Hola a todos, el Samsung Homesync se rootea con Kingroot, es todo, gracias.
So after trying multiple times to root this device with Poot.debug SuperSU would not function properly and root checker would not verify I had root.... I recently came across a new root program when rooting my chinese tablet and figured I would give it a final shot and guess what it finally worked! It's very simple all that it requires is a Windows PC, The devices drivers, and the program: "Kingo Root," Just search it on google.
Make sure the device has USB Debugging enabled and connect it to your PC after opening KingoRoot... It'll take a minute or two for the program to connect to the device but once it recognizes the device just click "root" wait a minute while it gathers the scripts and installs the SU Binary onto the device.. Wallah after root is successfully completed disconnect the device, reboot it, and there should be "Kingo Root's" own version of SuperUser installed.... Everything has been working since then and I've managed to install SuperUser from ChainsDD over Kingo's Superuser so I could update the SU binary to a more stable release and a better GUI interface.... Have Fun!!!
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://www.youtube.com/watch?v=_bt8BVaDCf0
http://slaycode.WordPress.com
Bump
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
When I open the app it opens but it doesn't work when I enter the commands and moreover the app when I try to start the adb it says unsupported device
Am using infinix hot 4 pro running NOUGAT xos 2.2
LordFME said:
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://slaycode.WordPress.com
Click to expand...
Click to collapse
Are you familiar with an APK that utilizes mtk_bypass to directly flash firmware to device.
I'm looking for an APK that basically does what sp flash tool does because I don't have a computer.
How to remove SuperSU on unrooted phone? - "there is no SU binary installed..."
Hi,
I lost some SMS data. I tired to use data recovery software. One of the programs was Fonepaw. Apparently fonepaw tried to root my device and failed; or did something else. Yet, somehow fonepaw installed SuperSU as a system application. This is causing problems with the device, a Galaxy S5 (SM-G900V) running Android 6.0.1.
When I run the SuperSU application it reports:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
My only option is to select 'OK'. Which closes the app.
SuperSU won't uninstall via application manager due to being a system application.
The "adb backup" command no longer works since my attempts at using Fonepaw and a few other applications.
ADB see's my device via "adb devices". I can explore directories. If I enter "adb shell su" I get "[email protected]:/ #".
But when I try to run "adb backup" the phone doesn't go into the prompt where you say 'okay' and set a password. Adb backup has worked just fine in the past. It's been useful, and I need to use it again as part of changing to a new phone.
Android also is showing in notification a "Security notice" stating "Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes."
Restarting does nothing. Even booting to safe mode doesn't stop the security notice. SuperSU being a system app runs in safe mode.
Root Checker app comfirms the phone isn't rooted.
I have never attempted to root the phone and have been the only owner/operator.
I would like to uninstall the SuperSU application and any data it stored on the phone without losing any data on the phone. Since the phone is not rooted and no SuperSU binary was installed, I'm hoping this is possible.
My search for information has provided limited insight.
I'm hoping someone on XDA might know what to do.
Edit: Additional info.
https://android.stackexchange.com/questions/103611/remove-su-after-unroot
I do the following:
"[email protected]:/ # cd system/xbin"
"[email protected]:/systems/xbin # ls"
output:
"Dexdump
dexdump
jack_connect
jack_disconnect
jack_lsp
jack_showtime
jack_simple_client
jack_transport
jackc
su"
The commenter at stack exchange would suggest the phone I have has root, but root check says otherwise.
Another edit:
I'm not sure, but it looks like a Custom Recovery was installed on the phone. Unsure if that's what came with phone or not, vol down+home+power brings me to a screen without the "Android" icon/statute/person thingy. Same for booting into vol up+home+power. However, in the recovery I get 'reboot to bootloader' and when I select that I go to stock android download mode/odin mode. And when I boot the system, boot/splash screen "Samsung Galaxy S5" on top, a lock icon that is unlocked with "Custom" in the middle, and "powered by Android" at the bottom.
command "adb root" returns "adbd is already running as root".
So, I'm not sure what's going on here. Found a post stating you can have adb root without root in androids system. So...I'm a noob at all this. *CONFUSED*. Hoping for someone to help.
Fonepaw support has not been helpful at all.