I AM DUMB..... not dumb bot lost in all this stuff. I need step by step guide to root my desire x. The hasoons all in one toolkit does not work for me. I tried a lot.
This is what root checker says:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
SuperSU application - version 0.96 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Ok, since you managed to unlock bootloader that means that you have ADB installed and have sufficient knowledge to root phone manually do this:
If you already have clockworkmod recovery installed (I explained you how to check it in the other thread where you posted your question skip to step 3.
1. go here:
http://forum.xda-developers.com/showthread.php?t=1952224
and download clockworkmod recovery, rename to recovery.img and put it on your pc on root of c: partition.
2. Reboot phone to fastboot, connect to PC and execute commands
fastboot flash recovery c:\recovery.img
fastboot reboot bootloader
fastboot erase cache
3. Boot phone to bootloader (not fastboot!!!) and choose option recovery
4. Go here:
http://androidsu.com/superuser/
download superuser form ARM devices as a flashable zip and put it on your sd (option in clockwork to mount sd as USB device)
5. Flash downloaded superuser .zip from recovery as a flashable zip.
6. Reboot, go to app drawer and you should see Superuser app. Open it.
Hasoon's tool is awesome but I prefer manual method.
I dont know how to "execute commands"
should i open command prompt and enter "fastboot flash recovery........." ? it does not work. I am not programmer, dont know how to use it but thank you for your reply. I am gonna try and try
nlooooo said:
Ok, since you managed to unlock bootloader that means that you have ADB installed and have sufficient knowledge to root phone manually do this:
If you already have clockworkmod recovery installed (I explained you how to check it in the other thread where you posted your question skip to step 3.
1. go here:
http://forum.xda-developers.com/showthread.php?t=1952224
and download clockworkmod recovery, rename to recovery.img and put it on your pc on root of c: partition.
2. Reboot phone to fastboot, connect to PC and execute commands
fastboot flash recovery c:\recovery.img
fastboot reboot bootloader
fastboot erase cache
3. Boot phone to bootloader (not fastboot!!!) and choose option recovery
4. Go here:
http://androidsu.com/superuser/
download superuser form ARM devices as a flashable zip and put it on your sd (option in clockwork to mount sd as USB device)
5. Flash downloaded superuser .zip from recovery as a flashable zip.
6. Reboot, go to app drawer and you should see Superuser app. Open it.
Hasoon's tool is awesome but I prefer manual method.
Click to expand...
Click to collapse
Execute command in the same way you did when you flashed unlock_code to unlock bootloder. You have to guide prompt to the folder with platform-tools that you installed installing ADB. The part c:\recovery.img is a path where you stored recovery.img (I told you to put it on root of c: partition) and it needs ta be named 'recovery.img'.
No no no no no please. I cant believe it.
ROOT CHECKER is now saying CONGRATULATIONS!!!! you have root access.
MAN THANK YOU!
but why is my phone not wiped? everything like before, just rooted. is this normal? every site is telling that root will factory reset your device.
THANK YOU AGAIN!
nlooooo said:
Execute command in the same way you did when you flashed unlock_code to unlock bootloder. You have to guide prompt to the folder with platform-tools that you installed installing ADB. The part c:\recovery.img is a path where you stored recovery.img (I told you to put it on root of c: partition) and it needs ta be named 'recovery.img'.
Click to expand...
Click to collapse
janickonajkrajsi said:
No no no no no please. I cant believe it.
ROOT CHECKER is now saying CONGRATULATIONS!!!! you have root access.
MAN THANK YOU!
but why is my phone not wiped? everything like before, just rooted. is this normal? every site is telling that root will factory reset your device.
THANK YOU AGAIN!
Click to expand...
Click to collapse
ROOTING WILL NOT WIPE YOUR DEVICE!!!
Bootloader unlocking resets phone, flashing superuser zip will only install superuser.apk to system/app folder and su binary file to system/bin (or system/xbin for SuperSU), which will allow you to have root privileges to phone system partition.
Related
I finally got my NookColor to sideload apps via ADB. The first thing I did was install Root Explorer and I rebooted the NC.
However, using Root Explorer, I do not have access to the cache or data directories. The response that I get is "Mounted as r/o" and "Your phone doesn't appear to be rooted. ..."
Did I miss something in the process and I'm not really rooted?
Also, I've noticed that the command adb remount gives back an error message as well.
Any thoughts?
Thanks!
See http://forum.xda-developers.com/showthread.php?t=857636
Assuming that you've already install the SuperUser apk
You need to push the su file into /data/local
use the following ADB commands:
Code:
adb push su /data/local/
Then
Code:
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
Use the su file from the attachment in the thread below
http://forum.xda-developers.com/showthread.php?t=665974
Thank you, Sapienta.
I noticed the Superuser comes down as a zip and the instructions say to boot into recovery mode and flash ... does that translate to renaming the zip to apk and installing via adb (as I've done with other apps)? Or do I need to figure out how to do the recovery boot/flash?
Ya sorry about that. I should've been more clear. Ignore everything from that page just download the attachment. You need to push the "su" file into /data/local and then chmod it to 6755 per the instructions from the first link I post and you're good to go.
EDIT NVM, I got it
Well, actually, you were quite clear the first time, I had just forgotten about the first link. But now, when I try to install the file (after renaming the zip to apk) via ADB I get an error message that says file does not contain AndroidManifest.xml. But I know the file is there ... I can see it when I view it with 7Zip. So, I guess I'm being dense today, but what am I missing?
indeana said:
Well, actually, you were quite clear the first time, I had just forgotten about the first link. But now, when I try to install the file (after renaming the zip to apk) via ADB I get an error message that says file does not contain AndroidManifest.xml. But I know the file is there ... I can see it when I view it with 7Zip. So, I guess I'm being dense today, but what am I missing?
Click to expand...
Click to collapse
Inside of the zip file there should be two files, a file called "su" without an extension and the Superuser.apk.
You'll want to push the su (the file is actually a raw binary) to your NC using the steps provided. You'll also want to install the Superuser.apk after pushing the su binary.
Thank you, antoniouslj. Yesterday I installed SU first and then pushed su but Root Explorer kept erroring out. So just to be sure I'm clear, the steps would be done in this order:
1. Push su -->
adb push su /data/local/
2. Change permissions -->
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
3. Install Superuser
Then do I adb Root Explorer or should Root Explorer be installed before I do the steps above?
indeana said:
Thank you, antoniouslj. Yesterday I installed SU first and then pushed su but Root Explorer kept erroring out. So just to be sure I'm clear, the steps would be done in this order:
1. Push su -->
adb push su /data/local/
2. Change permissions -->
adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
3. Install Superuser
Then do I adb Root Explorer or should Root Explorer be installed before I do the steps above?
Click to expand...
Click to collapse
That's exactly what I did and it worked great for me. I also had Root Explorer installed prior to installing SU.
Still Struggling!
So ... I still can't get this to work. Do I need to install an alternative launcher (like ADW) first and then do this process?
indeana said:
So ... I still can't get this to work. Do I need to install an alternative launcher (like ADW) first and then do this process?
Click to expand...
Click to collapse
No... what part of the process are you getting stuck on?
I do the three steps like we talked about earlier (and exactly in that order--except I exit out of the shell before I issue the adb install superuser.apk command) and I reboot the Nook. Turn the Nook back on and open Root Explorer, but then RE tells me that there are issues with Superuser and to close RE and restart the RE app. So I do. But it repeats the same process. (I've removed everything so I don't remember the exact language. When I open SU there is no way for me to add an app (that I know of anyway) including looking at the settings. So that's where I'm stuck. And if I can't get root access, then apps like SetCPU and Quickboot won't run successfully.
indeana said:
I do the three steps like we talked about earlier (and exactly in that order--except I exit out of the shell before I issue the adb install superuser.apk command) and I reboot the Nook. Turn the Nook back on and open Root Explorer, but then RE tells me that there are issues with Superuser and to close RE and restart the RE app. So I do. But it repeats the same process. (I've removed everything so I don't remember the exact language. When I open SU there is no way for me to add an app (that I know of anyway) including looking at the settings. So that's where I'm stuck. And if I can't get root access, then apps like SetCPU and Quickboot won't run successfully.
Click to expand...
Click to collapse
Grab another version of RE. I'm finding that version matters when trying to sideload apps.
EUREKA!!!
Thanks to everyone for your help! I finally figured it out. Just as I was about to take the last suggestion of finding and downloading another version of RE, I found and downloaded another version of Superuser (version 4). The new SU version extracts from the zip differently but I was finally able to push and modify per the earlier instructions, installed the new SU version, rebooted, started RE, added it to the SU Whitelist and BAM Root Explorer is working just as I expected it to. SetCPU and Quickboot also seems to be working.
Once again, thank you! You were all GREAT!!!
indeana said:
Thanks to everyone for your help! I finally figured it out. Just as I was about to take the last suggestion of finding and downloading another version of RE, I found and downloaded another version of Superuser (version 4). The new SU version extracts from the zip differently but I was finally able to push and modify per the earlier instructions, installed the new SU version, rebooted, started RE, added it to the SU Whitelist and BAM Root Explorer is working just as I expected it to. SetCPU and Quickboot also seems to be working.
Once again, thank you! You were all GREAT!!!
Click to expand...
Click to collapse
Nevermind...I got mine going, too.
Hi guys, need some help here.
I followed all the steps to unlock the bootloader and root the rezound last night but the root didnt work. The bootloadrer is unlocked, i have been able to confirm that at the very least by going back into the fastboot screen.
I was using the guide at the unlocker as it really went over step by step in great detail.
No idea what i did and am really hoping someone can provide me some guidance here.
See below for the errors i am getting from root checker app.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-09-18 06:41 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22228 2012-09-18 06:41 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your ADR6425LVW device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market -
Thanks so much, i have always done a ton of reading on this site and love it...figured it was about time to reach out for some help.
Thanks again and please let me know if i can provide any other info that would help you all figure out where i went wrong.
Amon Ra 3.15?
swilbert80 said:
Amon Ra 3.15?
Click to expand...
Click to collapse
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
jesternsb said:
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
Click to expand...
Click to collapse
When you pull battery and then power + volume down start into hboot (make sure no PH98IMG.zip on root of ext sd card), you should be able to get into recovery. You will see very quickly if Amon Ra is there. It is a dark screen with blue text. If you don't have it, you can get it at:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
I assume you are using adb fast boot for this. If I am telling you stuff you already know, let me know.
jesternsb said:
Not 100% sure......i will have to double check tonight but i used the Amon Ra linked to the unlocker site in the walkthrough.
I did do some reading on this a bit last night after unsucessfully attempting to root the rezound and read a few things about Amon Ra not working with ICS....but the walkthrough on unlocker was updated just a few weeks ago so i would have assumed they would use the newest one.
Thanks Swilbert80.......apprecaite the response here.
Thoughts?
Click to expand...
Click to collapse
If you are not sure on Amon Ra, I think you missed a step. The unlocker only puts the SuperSU program on your phone. You then need to go into recovery (Amon Ra) and flash the file. When I did this to my friends phone a few days ago, the file was on the internal SD card.
If you are still having issues, please refer to this thread - http://forum.xda-developers.com/showthread.php?t=1872651
Download the latest version of SuperSU zip file and install it with Amon RA recovery.
http://download.chainfire.eu/204/SuperSU/
swilbert80 said:
When you pull battery and then power + volume down start into hboot (make sure no PH98IMG.zip on root of ext sd card), you should be able to get into recovery. You will see very quickly if Amon Ra is there. It is a dark screen with blue text. If you don't have it, you can get it at:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
I assume you are using adb fast boot for this. If I am telling you stuff you already know, let me know.
Click to expand...
Click to collapse
Thanks for the info.....I went back into the hboot menu and did see a zip file titled PH98IMG.zip when it flashed the check on that hboot screen....i also was able to go into recovery and see a black backround with options to install the su.......and yes i am using adb for this.
Hey thanks for the reply here HowardZ......i am assuming i place that file in the same location as i do the recovery image? Trying to figure this out tonight....never a dull moment. lol
Thanks again
Correction.....no ph98im.zip was located....was just searching for it.
UPDATE i tried to go back through ADB and re work the steps and now the superuser is not on the phone anymore....argh.
UPDATE...i dl'ed the superuser through google play.....but still no root access.
I think if i can get some guidance on flashing Amon Ra and getting the supersu on the phone i might be ok, not 100% on that though.
Updated root checker report below.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22228 2012-09-18 19:22 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2012-09-18 19:22 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your ADR6425LVW device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market
Flash amon ra in boot loader and then download the super user.zip, the link is a few posts above mine
Sent from my cm_tenderloin
You can try updating the binary for SU from:
http://androidsu.com/superuser/
First, reinstall SU in recovery, and then flash the new binary followed by reboot. Should fix so SU remains (in app drawer) and root success.
MD5 checksum provided below DL link to check.
chaos254 said:
Flash amon ra in boot loader and then download the super user.zip, the link is a few posts above mine
Sent from my cm_tenderloin
Click to expand...
Click to collapse
Hey Chaos thanks for the reply here.....and please excuse my Noob-ness, god i hate the sound of that. I just want to make sure i fully understand and follow your instructions here.
Once i flash the amon ra recovery in the bootloader where do i save the super user zip file to and how do i flash that? That is where i seem to be getting hung up on.....not exactly sure where to save that file to and where to access/flash it from.......
I just want to make sure i follow you so that i dont scew it up.
thanks again
jesternsb said:
Hey Chaos thanks for the reply here.....and please excuse my Noob-ness, god i hate the sound of that. I just want to make sure i fully understand and follow your instructions here.
Once i flash the amon ra recovery in the bootloader where do i save the super user zip file to and how do i flash that? That is where i seem to be getting hung up on.....not exactly sure where to save that file to and where to access/flash it from.......
I just want to make sure i follow you so that i dont scew it up.
thanks again
Click to expand...
Click to collapse
Superuser.zip should be on your SD card. Once in amon ra>flash zip menu>sdcard>superuser.zip
Sent from my ADR6425LVW using Tapatalk 2
Awesome....victory is mine....thanks again......XDA is the shiznit!!!!!
OK, so I have a rooted I9300 and for some reason for the last few weeks I cant update the subinary and titanium wont get root access.
I did many google searches, tried a few thing eg (http://forum.xda-developers.com/showthread.php?t=1900217) , tried rooting again (even though I know Im rooted but nothing works.
So the next thing I want to try is to unroot my phone and root again.
My question is, because I cant access titanium to back everything up,
is there a way to unroot WITHOUT losing all apps and data?
Thanks a lot in advance.
Make nandroid backup and restore apps using titanium when your phone are rooted again.
Use MybackupPro to backup messages/contacts/bookmark/system setting/bookmarks.
Sent from my GT-I9300 using xda app-developers app
Uninstall super su via Google Play and reinstall .
jje
Cant use nandroid. It needs busybox which requests root access.
JJEgan said:
Uninstall super su via Google Play and reinstall .
jje
Click to expand...
Click to collapse
Tried it- it wont uninstall but go back to an earlier version.
Reinstalled the latest version and Im getting the same message.
Root checker app says "This device does not have proper root access".
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
qwerty12 said:
...just re-root it? Assuming you used CF-Root and will be flashing it again, when CWM runs again and installs the SuperSU ZIP, /system/xbin/su will get overwritten (and get set with the correct permissions).
Else, if whatever reason you don't want to do that, if you have CWM recovery installed, just mount /system, and using ADB delete /system/xbin/su, /system/app/Superuser.apk, /system/bin/.ext and install CWM-SuperSU-v0.96.zip again.
If you don't have CWM, you can use a kernel with an insecure adbd (Perseus kernel has this for Jellybean ROMs, and earlier Siyah and GalaxSih kernels have this for ICS) and delete /system/xbin/su and /system/app/Superuser.apk. You'll have to manually install SuperSU from the ZIP.
Click to expand...
Click to collapse
I tried rooting again- didn't change anything.
I do have CWM.
Tried using ADB, but it requests root access and fails to get it...
tomerstern said:
I do have CWM.
Click to expand...
Click to collapse
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
If you don't already have ADB setup and the correct drivers installed (if you already have Kies installed then you have the drivers installed). do the following. You can check, if you wish, by seeing when you connect your phone in recovery - you should have a SAMSUNG Android ADB Device under SAMSUNG Android Phone or an Android Debugger Bridge device in Device Manager. If not:
Download http://dl.google.com/android/repository/platform-tools_r14-windows.zip and extract the three files adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to a place of your choosing
install the drivers: http://www.mediafire.com/?2243ouw1701zp8l (Extracted from Kies_2.5.0.12094_27_11.exe)
disconnect and reconnect your phone
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
That should unroot your phone.
Go to "Install ZIP from sdcard" and choose to install a zip from the internal sdcard.
Exit out of the root shell (Ctrl+C or, alternatively, "exit" and you'll be sent back to the command prompt) on your computer and download the SuperSU ZIP.
Go back to the command prompt and type this "adb push " (including the space) and drag the CWM-SuperSU-v0.96.zip onto the command prompt window, add a space and type "/data/media". You should have something like "adb push <path to CWM-SuperSU-v0.96.zip> /data/media"
This should put the SuperSU ZIP onto the root of your internal memory card. Choose go back on your phone and select to install a ZIP from the internal memory card again. You should see CWM-SuperSU-v0.96.zip. Install it, reboot, update SuperSU from the Play Store and run SuperSU from the app drawer. You should get a prompt asking you to update the su binary. Do so.
Grab Android Terminal Emulator on the Market, and run "su". If all went well, SuperSU should ask you for permission. Grant it and if the $ turned into a # and the command "id" says uid=0 (root) then you're rooted!
OK, Im really sorry and embarrassed to say that I got confused with my tab 10.1.
I Do not have CWM installed.
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
What can I do now?
Thanks again and sorry for the confusion..
tomerstern said:
Tried installing it now and could not. I stay on odin mode and I dont get the CWM menu...
I guess at this stage when my root is screwed I cant install CWM anymore.
Click to expand...
Click to collapse
Flashing CF-Root should always get you CWM as it's done through ODIN, which does not care if your phone is rooted or not. When you're flashing CF-Root, make sure the auto reboot option remains ticked. If your phone doesn't boot into CWM after ODIN reboots it, then take note of the following:
Chainfire said:
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
Click to expand...
Click to collapse
qwerty12 said:
Go to the folder where you have adb installed in the Command Prompt, and run "adb shell". Run the following commands:
Code:
rm /system/app/Superuser.apk
chattr -i /system/xbin/su [in case Survival Mode is turned on in SuperSU]
rm /system/xbin/su
rm /system/bin/su [ignore this one if it throws an error]
rm -r /system/bin/.ext
Click to expand...
Click to collapse
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
tomerstern said:
OK, Im now in the mounts and storage folder insider CWM.
ADB interface is installed on device manager.
II dont understand what to press and where to run these commands.
Click to expand...
Click to collapse
Under the mounts and storage option, select mount /system. It will change to "unmount /system" if selected correctly.
The commands are run from an "adb shell" session, which you can get to by doing this:
Extract those three ADB files from that platform-tools ZIP to a folder somewhere (I chose C:\adb out of randomness). Open that folder and while holding down the shift key, right-click a blank, white area in the folder and select "Open command window here". You can then type "adb shell", which will allow you to run those commands.
qwerty12 said:
Good, ADB will be running as root in CWM by default. Boot into recovery mode, go to mounts and storage, and select Mount /system.
Click to expand...
Click to collapse
There isnt mount system there. I see unmount system.
I see mount data, preload etc.
OK, that's fine, you may move on to running those commands.
Two problems:
1. running "chattr -i /system/xbin/su"
resulted in a "chatter not found" message.
2. Trying to push the su zip resulted in this message: "error: device not found".
tomerstern said:
"chattr -i /system/xbin/su"
Click to expand...
Click to collapse
If rm worked on /system/xbin/su, then ignore it as you don't need it anyway.
2. Trying to push the su zip resulted in this message: "error: device not found".
Click to expand...
Click to collapse
Reconnect the phone and try again?
not working after numerous attempts.
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
tomerstern said:
Can I Start the phone and move the zip file manually with a micro sd cable? If not, what else?
Click to expand...
Click to collapse
That should be fine
moved it to internal memory and after shutdown, power+home+volume up wont take me to cwm anymore but to android system recovery.
Why? How do I get back to cwm? Install it again with Odin?
BY THE WAY, I can still see supersu is installed on my device. Does it mean what we did did not work?
OK, I can confirm this method works
I just installed the zip of the supersu and now Ive got full root privileges.
The reason I couldnt get into cwm was that for some reason I get a short android upgrade each time I boot up. This upgrade deletes cwm. Thats why I found out that I need to install CWM and then immidiately press power-volume up-home, before i let the device power up.
I want to give a big thanks to qwerty12 for the help and much needed patience.
Hey Guys -
After being an iPhone fanboy for years, I recently went to Android to try something new. For two months, I've been running Revolution HD (4.3) on my HTC One - but - yesterday decided to give Venom ViperOne a try. I downloaded the latest version, booted to recovery (TWRP) wipred cache, and applied new ROM.
Everything seemed to work great, but after getting many things set up, I found out that I didn't have full root access. When laucnhing SuperSU, it said something like the binaries were not installed, but I finally got that to go away. Re-installing the binary via Recovery didn't fix everything, though.
I installed Root Checker Pro and here is what it said about my phone:
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.69 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 104556 2013-11-17 20:25 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
I have tried many suggestions and now have 3 different zip files for SuperSU that I've tried. I'm still researching, but any suggestions would be fantastic... Thanks!
Click build number at setting 7 times until it appear developer option, change root access to app and adb, see if that can solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
Thanks for your reply. Fortunately, I finally fixed it by doing the following:
1. Uninstalled SuperSU via Play Store
2. Downloaded the 1.69 SuperSU update file and installed it through Recovery.
3. Re-installed SuperSU via Play Store
Once I did this, it verified working 100% again in apps as well as passed verification.
Thanks again for your help!
No sweat, Glad you've solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
THANKS!
bzowk said:
Thanks for your reply. Fortunately, I finally fixed it by doing the following:
1. Uninstalled SuperSU via Play Store
2. Downloaded the "" and installed it through Recovery.
3. Re-installed SuperSU via Play Store
Once I did this, it verified working 100% again in apps as well as passed verification.
Thanks again for your help!
Click to expand...
Click to collapse
Thanks man I was stuck with no root access for the longest. This worked!
Su not found
Thanks again for your help![/QUOTE]
Error in tmp/sideload/package.zip (Status 255)
McNaireP said:
Thanks again for your help!
Error in tmp/sideload/package.zip (Status 255)
Click to expand...
Click to collapse
why are you sideloading superSU ?
just copy it to your phone storage and flash it with TWRP /CWM
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
clsA said:
why are you sideloading superSU ?
just copy it to your phone storage and flash it with TWRP /CWM
"1.93"
Click to expand...
Click to collapse
Using CWM to do just that, flash 1.93 update to fix the fact that 'su' disappeared after KDZ update to ICS, trying go back to GB KDZ Stock has me stuck at LG logo. tried re-flashing a number of times...just going around in circles...
pls delete - wrong thread SRY!
azliazmi said:
Click build number at setting 7 times until it appear developer option, change root access to app and adb, see if that can solved your problem
Sent from my Yuga powered by Asyluminator CM10.2 by chasmodo.
Click to expand...
Click to collapse
You saved my skin. Thanks so much!
Sudo password
Hello there,
First-off, i would like to thank the Chainfire for the SuperSU files and the Kingroot for making the rooting process easier.
As far as i am aware, it is pretty hard to root this device. It runs on a Spreadtrum chipset sc7731. However, recently i figured out how to root this device.
->> REQUIREMENTS:
1. Minimal adb and fastboot tool.
2. Kingroot app.
3. As usual, a working brain.
->> METHOD:
It seems like that the device's default.prop file comes with a configuration :
Code:
ro.secure=1
which makes it impossible to root this device with absolutely any rooting software out there including the one-click apps.
To be able to root this device, the only efficient way is to replace the stock recovery with a custom one, deleting the default su binary file inside the /system/xbin folder as well as in the /system/bin folder, installing the SuperSU.zip file and finally by installing the Kingroot apk which will ultimately root the device.
I personally prefer the TWRP but there is no official release out there for this device. So, i ported a custom recovery for it in my spare time ( It may appear somewhat ridiculous but i had nothing more interesting to do so i changed the layout :silly
I have attached the recovery file below as well as the SuperSU.zip files below.
After you have downloaded the recovery as well as the SuperSU.zip, here are the steps to root it:-
Download the minimal adb fastboot for windows. You may google it, its available easily. (It turns out it may be the only tool that may work effectively in case your device is not getting recognized by any other adb.)
Rename the recovery as twrp and place it inside the Minimal adb and fastboot folder.
Connect the device via a USB cable and make sure adb debugging is on inside the developer options.
Now open the Minimal adb and fastboot tool and type the following commands inside the prompt:-
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot
Type the commands in the exact sequence. Your device will boot normally. Now, time to checkout the recovery. Type the following command inside the prompt
.
Code:
adb reboot recovery
In a few seconds, you will have the custom twrp booted in front of you. Now, open the Mount tab inside the recovery and check the system option within it.
Head back to the recovery homescreen and open the Advanced tab which is followed by opening the File Manager tab.
Inside the file manager, follow the path to the pre-existing su binary file, i.e /system/xbin and delete it. Do the same with the su file present on /system/bin.
Now, head back to the recovery home ,open Install tab and select the SuperSU.zip wherever you placed it and swipe to confirm the installation.
Reboot system. (It will probably boot without the logo so don't worry if it does.)
Now Google the Kingroot.apk, download it and install it. Give it a run, it will probably fail.
So get rid of the other superuser app i.e, SuperSU app via the option present inside it, i.e "Cleanup to install other superuser app" or something like that.
After a few seconds, it will disappear from the device and probably the same might happen with the Kingroot app.
Reboot the device.
Re-install the Kingroot app and run it again.
Congrats! You just rooted your device. Go ahead and check the root via an app like Rootchecker.
The custom recovery file has been attached and happens to be in the .zip format so kindly extract the recovery from it.
If you have any query regarding this, do let me know. :v
(I would be glad if you or anyone who finds this post useful would thank me) Cheers!