I just used Odin3 v3.04 and CF-Root-SGS3-v6.4 to root my Samsung Galaxy S III. It seems root worked because CWM was installed and as i tried to execute it, i had to grant root rights to this app. But i can't execute adb root since its telling me "adbd cannot run as root in production builds". I can't access /data through ES Explorer on my phone either. Does anyone have a solution?
Djablos said:
I just used Odin3 v3.04 and CF-Root-SGS3-v6.4 to root my Samsung Galaxy S III. It seems root worked because CWM was installed and as i tried to execute it, i had to grant root rights to this app. But i can't execute adb root since its telling me "adbd cannot run as root in production builds". I can't access /data through ES Explorer on my phone. Does anyone have a solution?
Click to expand...
Click to collapse
Try by flashing this zip file from CWM: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
That may fix your issue..
EDIT: this wont flash any new app to your SGS3, it will flash updated su script.
suyash1629 said:
Try by flashing this zip file from CWM: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
That may fix your issue..
EDIT: this wont flash any new app to your SGS3, it will flash updated su script.
Click to expand...
Click to collapse
I get the following message when i start CWM:
After that i cant see any possibility to flash something (or i dont really know what else do you mean by "flash from cwm")
Djablos said:
I get the following message when i start CWM:
After that i cant see any possibility to flash something.
Click to expand...
Click to collapse
just press ok and then press reboot in recovery mode and flash it through there.. else press the combination of Volume up + Power + Home button to enter the recovery.. you nneed to flash it through there
suyash1629 said:
just press ok and then press reboot in recovery mode and flash it through there.. else press the combination of Volume up + Power + Home button to enter the recovery.. you nneed to flash it through there
Click to expand...
Click to collapse
Unfortunately It didn't fix my issue. It don't get any message for "adb root" and device is getting disconnected after that.
Code:
>adb devices
List of devices attached
4df1ec9f1b844f57 device
>adb root
>adb devices
List of devices attached
Still no luck for access to the folder from the phone.
Djablos said:
Unfortunately It didn't fix my issue. It don't get any message for "adb root" and device is getting disconnected after that.
Code:
>adb devices
List of devices attached
4df1ec9f1b844f57 device
>adb root
>adb devices
List of devices attached
Still no luck for access to the folder from the phone.
Click to expand...
Click to collapse
Go to developer options and enable root access to both apps and adb, this may fix that problem..
suyash1629 said:
Go to developer options and enable root access to both apps and adb, this may fix that problem..
Click to expand...
Click to collapse
Do you mean developer options of the phone? I can't find any options there regarding root access. I checked SuperSU app, but there is also only list of apps with root access and no possibilities to add apps.
Djablos said:
Do you mean developer options of the phone? I can't find any options there regarding root access. I checked SuperSU app, but there is also only list of apps with root access and no possibilities to add apps.
Click to expand...
Click to collapse
yes it should be in developer options of the phone, m not sure if its in stock firmware.. if there is no such option than first try adb shell and then su, than it will prompt to give root access to shell. have you tried doing that?
suyash1629 said:
yes it should be in developer options of the phone, m not sure if its in stock firmware.. if there is no such option than first try adb shell and then adb su, than it will prompt to give root access to shell. have you tried doing that?
Click to expand...
Click to collapse
Well now we're talking! I didn't know there is a possibility to gain root that way. Thank you for your help!
Djablos said:
Well now we're talking! I didn't know there is a possibility to gain root that way. Thank you for your help!
Click to expand...
Click to collapse
well thats nothing, but why do you want to do by using adb?
suyash1629 said:
well thats nothing, but what do you want to do by using adb?
Click to expand...
Click to collapse
I want to pull some apps to my PC to decompile them. I'm preparing myself for a seminar on my uni.
Djablos said:
I want to pull some apps to my PC to decompile them. I'm preparing myself for a seminar on my uni.
Click to expand...
Click to collapse
oh.. and as i said above to use adb shell and then adb su, that might too work but simply use su after adb shell, i dont know how i entered adb su.
suyash1629 said:
oh.. and as i said above to use adb shell and then adb su, that might too work but simply use su after adb shell, i dont know how i entered adb su.
Click to expand...
Click to collapse
Well, since i logged once with adb as root, the phone seems to give now permanently root access to adb. So i just used "adb pull /data/app/com...." with no problem.
Djablos said:
Well, since i logged once with adb as root, the phone seems to give now permanently root access to adb. So i just used "adb pull /data/app/com...." with no problem.
Click to expand...
Click to collapse
thats fine but next time you can also use su to be root user over adb.. maybe next time also adb root wont work and you have to use adb shell asnd su to be root user..
suyash1629 said:
thats fine but next time you can also use su to be root user over adb.. maybe next time also adb root wont work and you have to use adb shell asnd su to be root user..
Click to expand...
Click to collapse
Well to be precise, "adb root" still doesnt work, so i can gain root access only over shell->su. But it is completely sufficient for my purposes.
Djablos said:
Well to be precise, "adb root" still doesnt work, so i can gain root access only over shell->su. But it is completely sufficient for my purposes.
Click to expand...
Click to collapse
adb root is not working because root access to adb is not available from developers option, so thats only way to gain root access. And also best of luck for seminar..
suyash1629 said:
And also best of luck for seminar..
Click to expand...
Click to collapse
Thanks, I will definitely need some luck
Real Root
Real root is odin root!
Related
I've followed the following thread CF-root 4.1.
Everything went fine and the kernel is rooted.
I can use apps which require root, like TitaniumBackup.
I also can use su to gain root privileges and also adb shell and then su. To make this more clear. I first get $ (user priv) and then with "su" i get # (root priv).
For this reason i can't use the adb push method, because i'm not root directly.
adb root which is suggested in a couple of threads isn't helping me. I get the following output. "adbd cannot run as root in production builds".
How can i fix it, so i can have root privileges directly when connecting via the adb shell?
You need an "insecure kernel" for that.
There are several for download in a thread in the dev section.
Why do you need ADB to be running as root for pushing, if you don't mind asking?
bla
HellcatDroid said:
You need an "insecure kernel" for that.
There are several for download in a thread in the dev section.
Why do you need ADB to be running as root for pushing, if you don't mind asking?
Click to expand...
Click to collapse
Many thanks for illuminating people in this situation!
Cuz it's obviously more comfortable to do stuff using the computer's keyboard.
I tried to perform the Windows How To in page http://forum.xda-developers.com/showthread.php?t=1158400. How do I know I have super user access?
mcabrera1965 said:
I tried to perform the Windows How To in page http://forum.xda-developers.com/showthread.php?t=1158400. How do I know I have super user access?
Click to expand...
Click to collapse
open up an app that requires SU access and it will tell you it has been granted or that you dont have root access. also in adb after running the commands you can type "adb shell" and you should see a #
steal25 said:
open up an app that requires SU access and it will tell you it has been granted or that you dont have root access. also in adb after running the commands you can type "adb shell" and you should see a #
Click to expand...
Click to collapse
Yeah. What he said.
im trying to root my atrix, i have followed the steps in the post however each time i type in the flash preinstall preinstall.img the cmd says that it cant be read....im lost. is there a easier way too root instead of cmd. btw im on 2.3.4 i did nothing to my phone, im just trying to root it so i cant install roms
Make sure that you put all your root files, on your pc, on c:\root, and not in a subdirctory. Then, while you're trying to root, make sure you are in that directory when you're entering the commands.
the files inside the folder i download have to be in a folder or just in C:\
also when im in cmd the whole time it says that im C:\documents and settings\something>
also im running windows xp on a macbook if that matters let me know
make a folder in c:\
To get to root directory in command prompt: "cd c:\" (+ any other folder destination that you want to get to).
ok i flashed the preinstall and rebooted the phone, do i have do go back to fastboot? or just stay with the phone on (but the cmd says phone not found)
mac208x said:
ok i flashed the preinstall and rebooted the phone, do i have do go back to fastboot? or just stay with the phone on (but the cmd says phone not found)
Click to expand...
Click to collapse
after reboot you should be done... and rooted. Run titanium backup to check or download rootcheck from the market
Bender B. Rodgriguez said:
after reboot you should be done... and rooted. Run titanium backup to check or download rootcheck from the market
Click to expand...
Click to collapse
what about the other stuff? i just did the preinstall and thats it
ok so when i do adb shell and than preinstall/su it says access denied.....
mac208x said:
ok so when i do adb shell and than preinstall/su it says access denied.....
Click to expand...
Click to collapse
Sorry I misunderstood you at first. I didnt realized u had just done preinstall stuff... Is usb debugging enabled on the phone??
Bender B. Rodgriguez said:
Sorry I misunderstood you at first. I didnt realized u had just done preinstall stuff... Is usb debugging enabled on the phone??
Click to expand...
Click to collapse
yes, should i put the usb as mass storage?
mac208x said:
yes, should i put the usb as mass storage?
Click to expand...
Click to collapse
No, it needs to be on usb debugging to use adb.
If i remember correctly one of the steps does give you an error but you just ignore it and type the rest of the commands. Im not sure if that is the step you are on though.. Im just recalling from memory. Complete the rest of the steps in the tutorial you are using and see if it works
Bender B. Rodgriguez said:
No, it needs to be on usb debugging to use adb.
If i remember correctly one of the steps does give you an error but you just ignore it and type the rest of the commands. Im not sure if that is the step you are on though.. Im just recalling from memory. Complete the rest of the steps in the tutorial you are using and see if it works
Click to expand...
Click to collapse
i did in fact ignored it but nothing happened
mac208x said:
i did in fact ignored it but nothing happened
Click to expand...
Click to collapse
have you tried
Code:
adb shell
/preinstall/dosu
instead?
everything says access denied >.<
Bender B. Rodgriguez said:
have you tried
Code:
adb shell
/preinstall/dosu
instead?
Click to expand...
Click to collapse
i tried everything
mac208x said:
i tried everything
Click to expand...
Click to collapse
well I'm about out of suggestions here. My only other one is to run cmd "as administrator" or you can flash an image with root built in.
However, it should work. this is the method I used to root my atrix and countless others as well. Also you may want to make sure you have the right device drivers installed too.
whats the other method? coz i just keep getting this stupid premission denied the whole time, or how do i know if im on admin cmd?
Get rootchecker from the market and check to see if you have root privileges.
mac208x said:
whats the other method? coz i just keep getting this stupid premission denied the whole time, or how do i know if im on admin cmd?
Click to expand...
Click to collapse
To run as admin right click cmd and choose the "run as admin" option.. If you are admin the directory you start out in is C:\
windows/system32.
i think thats the problem coz im running as "owner" but i cant get into admin becouse there is a password required that i dont know, anyone know what would be the password?
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.
I have a Nexus 7 (2013/flo/razor) with Firefox OS installed. Is there a way to "Root" the device? and if so, what could it do?
Can u tell more about your problem ?
rakoczy12 said:
Can u tell more about your problem ?
Click to expand...
Click to collapse
I am asking if it is possible to root the device on FirefoxOS
Yoyodude1124 said:
I am asking if it is possible to root the device on FirefoxOS
Click to expand...
Click to collapse
Root to accomplish what?
If you use adb and the adb shell, you effectively have root access to the device and can muck about.
Saijin_Naib said:
Root to accomplish what?
If you use adb and the adb shell, you effectively have root access to the device and can muck about.
Click to expand...
Click to collapse
You could have adb and adb shell without being root. In that case, you would have restricted permissions in your device. For example, you couldn't edit manually the wpa_supplicant.conf.
You could get root If you set ro.secure to 1. The best way to do it in a non-root build (and If you don't want to flash a new build with the env variablle VARIANT=eng), is to flash the boot.img from a rooted build.
That way, for example, I was able to root an user build to do some test and fixes.