Hi,
I tried this procedure to get root access on a Samsung Galaxy S3 I9300 :
http://forum.xda-developers.com/gal...3-07-2012-cf-root-6-4-supersu-cwm5-5-t1695238
The installation worked fine, but I'm not sure whether I need to run SuperSU afterwards to get the "su" root access.
SuperSU comes in version 0.93 and tell it requires being updated.
I'm trying to get root access from the adb shell.
The device is detected and "adb shell" works, but not the "su" command afterwards.
Also, "adb root" tells "adbd cannot run as root in production builds".
I chose the above procedure to root as I don't want to overwrite the kernel, nor data.
Can anyone help ?
Configuration details :
Android 4.3
I9300XUGMK6
Kernel 3.0.31-2429075
[email protected]
JSS15J.I9300XXUGNA5
kaglows controlling
Well, it seems that the new security of Android 4.3 is the cause of the difficulty in rooting with CF-Root 6.4.
Furthermore, CF-Root is no more maintained and was replaced by CF-Autoroot.
But I fear destroying the "/data" folder and "mmssms.db" by installing CF-Autoroot, as this means a new kernel.
I wonder if it would be possible to upgrade SuperSU instead.
So the two options :
a) installing CF-Autoroot
b) upgrading SuperSU
Who tested one of them on the Galaxy S3 I9300, and which were the consequences on the MMS and SMS database ?
Thanks
Related
can anybody teach me?
When mine P-500 on Android 2.2,I can root & using custom recovery
Now I using Android 2.2.2,I using GingerBreak v1.2 to root and I already root.
But when I want to operate custom recovery steps.
Then 1st.-restart my phone =>finish ok
2nd.-connect to PC & open Debug mode =>finish ok
3rd.-open windows DOS Command mode and type "adb shell" =>finish ok
4th.-In "$" prompt to input "su"(own superuser)
=show"Permission denied" why??
Hope someone talk to me how to
Thanks a lot
When you type su on your pc, you will usually get a prompt from the superuser app on your phone where you will have to allow it for the procedure to proceed on the pc. Have you done this?
And, If I understand correctly, gingerbreak need not always install busybox and superuser correctly on your phone. check first whether you have the superuser app on your phone and that it works. If not, install these 2 apps from the market.
Then try the procedure once more.
If you are trying to install a custom recovery on your phone, you don't need adb. You can install a custom recovery using a tool like terminal emulator on your phone. The procedure to do so is mentioned in the following thread -
HOWTO] Rooting, Installing -Android SDK, Custom Recovery, Custom ROM's
Hi,
I hope this is right right place.
I used INTERNATIONAL GSM [GT-I9300] and 06. Android 4.1.2 [Build JZO54K ELLA] as that seemed to match my phone model the closest - JZO54K.i9300xxemc2
I had a stock Samsung Galaxy S3 and tried to ROOT it using the Samsung S3 Toolkit so that I can install the Android Revolution ROM v31 but it appears it may have partially rooted, i think.
I didn't want to root it just yet as i wanted backups of the phone but using the backup options i ended up doing "Flash Insecure Boot Image and Root Phone" and then had to manually install Busybox using option 13. "Install BusyBox on Device".
When running most of the backup commands from the Samsung S3 Unified Toolkit, I get [email protected]:/ # su /system/bin/sh: su: not found
I don't know what to do now or know if the phone fully rooted and backed up.
Option 21 shows the below.
DEVICE INFORMATION FOR Samsung Galaxy S3
------------------------------------------------------------------------------------
Device Product Model: GT-I9300
Firmware Build : 4.1.2
Firmware Build ID : JZO54K
Firmware Build PDA : I9300XXEMC2
Firmware Region Code: BTU
------------------------------------------------------------------------------------
Boot Image Status : Insecure [based on ro.secure value]
Note: This is only an indictation if the boot image has been modified
------------------------------------------------------------------------------------
Use another root method like Philz .
jje
I downloaded Root Checker and Titanium Backup and both say the phone is not rooted but it appears may busybox is installed as some backup's seem to be working.
Not sure how could have happened other than I may have selected the incorrect phone model for JZO54K.I9300XXEMC2.
Since the phone seems to be in an inconsistent state, i'm now worried about bricking it.
bbasra said:
Hi,
I hope this is right right place.
I used INTERNATIONAL GSM [GT-I9300] and 06. Android 4.1.2 [Build JZO54K ELLA] as that seemed to match my phone model the closest - JZO54K.i9300xxemc2
I had a stock Samsung Galaxy S3 and tried to ROOT it using the Samsung S3 Toolkit so that I can install the Android Revolution ROM v31 but it appears it may have partially rooted, i think.
I didn't want to root it just yet as i wanted backups of the phone but using the backup options i ended up doing "Flash Insecure Boot Image and Root Phone" and then had to manually install Busybox using option 13. "Install BusyBox on Device".
When running most of the backup commands from the Samsung S3 Unified Toolkit, I get [email protected]:/ # su /system/bin/sh: su: not found
I don't know what to do now or know if the phone fully rooted and backed up.
Option 21 shows the below.
DEVICE INFORMATION FOR Samsung Galaxy S3
------------------------------------------------------------------------------------
Device Product Model: GT-I9300
Firmware Build : 4.1.2
Firmware Build ID : JZO54K
Firmware Build PDA : I9300XXEMC2
Firmware Region Code: BTU
------------------------------------------------------------------------------------
Boot Image Status : Insecure [based on ro.secure value]
Note: This is only an indictation if the boot image has been modified
------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Use Framaroot to root and then install Busybox via BusyBox from PlayStore...
Gesendet von meinem GT-I9300 mit Tapatalk 2
I ended up re-running through recommended rooting options using the Unified Tool kit and it worked.
Now time to put on a custom rom.
Hi,guys.
Does anyone make android 4.0.4 devices rooted by superuser?
I open my superuser:
downloading manifest okay
parsing manifest okay
latest version 3.1.1
checked install version 3.1.1
fixing database okay
unpacking sutools okay
check current install path= /system/xbin/su
Downloading new binary okay
gaining root access fail
anyone knows what to do ?
I have my device rooted by means of UnlockRoot, at first I think the version of superuser is low.
So I download Superuser-3.1.3-arm-signed.zip , exact it and replace the old version superuser and su .
I click the root on the software and it seems that everything work.
But the fact is that I can't find superuser in my android devices and manually install superuser by myself.
And then the phenomenon above appears.
I don't know what to do now, guys. It seems that I have rooted the devices and I can't get root access.
It is more dangerous than I don't root the devices.:crying:
makeperfect said:
Hi,guys.
Does anyone make android 4.0.4 devices rooted by superuser?
I open my superuser:
downloading manifest okay
parsing manifest okay
latest version 3.1.1
checked install version 3.1.1
fixing database okay
unpacking sutools okay
check current install path= /system/xbin/su
Downloading new binary okay
gaining root access fail
anyone knows what to do ?
I have my device rooted by means of UnlockRoot, at first I think the version of superuser is low.
So I download Superuser-3.1.3-arm-signed.zip , exact it and replace the old version superuser and su .
I click the root on the software and it seems that everything work.
But the fact is that I can't find superuser in my android devices and manually install superuser by myself.
And then the phenomenon above appears.
I don't know what to do now, guys. It seems that I have rooted the devices and I can't get root access.
It is more dangerous than I don't root the devices.:crying:
Click to expand...
Click to collapse
Put your device into download mode and restore to stock using Odin. Then try to root again. If the same thing happens, go back to stock and find another way to root. Cheers.
I have a Sony Xperia Z2 Tablet (SGP561; Build: 17.1.D.0.417) which appears to be rooted. (Settings > About Tablet > Status > Rooting Status: Rooted) however neither SuperSU or Super User appears to work. (and without Super User privileges the Root Checker apps always say I don't have root access even when I otherwise would) No matter what I try, it always says a variation of "There is no SU binary installed." (SuperSU) or "The Superuser binary (su) must be updated." (Superuser, and no logs created when it fails)
Is there any method of installing those binaries? Maybe through a USB cable and USB Debugging?
Elliander said:
I have a Sony Xperia Z2 Tablet (SGP561; Build: 17.1.D.0.417) which appears to be rooted. (Settings > About Tablet > Status > Rooting Status: Rooted) however neither SuperSU or Super User appears to work. (and without Super User privileges the Root Checker apps always say I don't have root access even when I otherwise would) No matter what I try, it always says a variation of "There is no SU binary installed." (SuperSU) or "The Superuser binary (su) must be updated." (Superuser, and no logs created when it fails)
Is there any method of installing those binaries? Maybe through a USB cable and USB Debugging?
Click to expand...
Click to collapse
You can try to download supersu from here http://www.appsapk.com/supersu/ and install if via adb.
Of you could also root it using easy root tool: http://forum.xda-developers.com/showthread.php?t=2784900
I rooted my device using the second method and everything went fine.
Let us know what happen
Syol said:
You can try to download supersu from here http://www.appsapk.com/supersu/ and install if via adb.
Of you could also root it using easy root tool: http://forum.xda-developers.com/showthread.php?t=2784900
I rooted my device using the second method and everything went fine.
Let us know what happen
Click to expand...
Click to collapse
As I mentioned in another thread, Easy Root ended up being the solution. It gave me errors like it failed, but after rebooting the device everything started to work fine and I was able to successfully install SuperSU without error.
Ive veen trying to root my sm-t380 to the point of even creating my own modded boot.img with security set to 0. When i felt like everything had been done correctly, magisk flashed successfully, and there were no bootloops, I go to magisk manager and see that only the ramdisk was modified. Sar and a/b were both no and the root status showed up as na. No app could detect the root.
What went wrong?
P.S SuperSU systemless dident work either
P.P.S SuperSU system puts me in a bootloop that lasts for around 15 minutes per bootloop
Bump
/\
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
jwoegerbauer said:
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
Click to expand...
Click to collapse
i know how to check, my problem is my device is **** and cant be rooted. Ive heard multiple places that say the sm-t380 is a sort of "touchy" device. It dosent like rooting AT ALL
Any updates with this? I'm trying to root with the latest OS this tablet has but is not picking magisk like it patch the BOOT.img perfectly but when I flash it with odin is not detecting anything.
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
flya258 said:
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
Click to expand...
Click to collapse
Hi I am reading through the xda treads have the same thing after patching the boot except my device in root checker says successfully rooted. What I did was switch from supersu to magisk( switch superuser app). I noticed the superuser binaries have to be installed or it will not work.
In my situation I just went inside supersu app and selected switch superuser app, then supersu uninstalls itself then reboot phone and open magisk app. root checker says successfully rooted.
I don't know if I am doing it right but my phone still says successfully rooted??