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!!!!!
Related
I used Oneclickroot and it says my device is rooted, but none of the apps like Titanium backup, say I have root. I also followed another way or rootiong my phone where you use the volume down button to select "reinstall packages" it says it was rooted successfully, yet none of the root-required apps are detecting root. I also have the superuser app installed now.
I dont want to flash a ROM or anything, i just want to delete the bloatware and make my battery last longer
Are you on android 2.2 or 2.1?
Sent from my SGH-T959 using xda premium
im on 2.2 with froyo.
I actually followed the directions that were posted on XDA about how to root, so im not sure why it didnt work. This is another that I followed when the XDA one didnt work... http://www.techwhizz.com/root-samsung-vibrant-android-22-froyo-2/
I also keep getting this when OnClickRoot asks to test when rooting is finished...
Running a SU test...
Test failed!
FAILED
any suggestions?
I have used the ODIN route with Eugene's Unofficial TMO 2.2 Froyo ODIN. You can find it here with the directions:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
If you are successful, you will be rooted and stock. Some of the bloat will already be removed. Good Luck.
The goal is not to wipe anything from my phone. This is why I have never bothered to root my phone. I knew something would go wrong, and it would be so easy like everyone says it is. I just want my battery to last longer. Im already using Juice Defender, but I still only get about 8 hours on my phone. I hardly use it and find it almost dead by 8pm
I have busybox and battery calibrator, but say im not rooted. Superuser shows no apps
To be clear, you were using nothing but stock 2.2 Froyo. You then used the OneClickRoot method for rooting, follow all instructions exactly as they're listed. After you rebooted, you attempted to download and use an app that requires root and it didn't work. Is that correct?
I've noticed that occasionally Titanium Backup won't properly recognize root until you've wiped the data for it through the Applications Manager.
kaintfm said:
To be clear, you were using nothing but stock 2.2 Froyo. You then used the OneClickRoot method for rooting, follow all instructions exactly as they're listed. After you rebooted, you attempted to download and use an app that requires root and it didn't work. Is that correct?
I've noticed that occasionally Titanium Backup won't properly recognize root until you've wiped the data for it through the Applications Manager.
Click to expand...
Click to collapse
thats correct. The only thing that does recognize root is now battery calibrator. Superuser still shows no apps
so far the only app that recognizes root is battery calibrator. Busybox, TB, and autokiller memory optimizer dont recognize root. super user shows no apps. Im wondering if my phone is even rooted, since after using battery calibrator, my phone has dropped 15% in the last 20 minutes. Nothing is even running on my phone. its just sitting there.
I did use Root Checker, heres the results...
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: No such file or directory
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your SGH-T959 device by Root Checker version 3.9 from joeykrim in the Android Market - http://goo.gl/GgWae
but I guess BusyBox was installed correctly...
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
BusyBox binary location: /system/xbin/busybox
BusyBox binary file information: -rwxrwxrwx root root 282624 2011-10-27 22:46 busybox
Installed BusyBox Version:
BusyBox is not sharing its version information
BusyBox supports the following applets:
BusyBox is not sharing its supported applets
Results provided on your SGH-T959 device by Root Checker version 3.9 from joeykrim in the Android Market - http://goo.gl/GgWae
Im sure that im putting the update.zip on the internal sdcard and that it isnt called update.zip.zip. Ive been at this for 3 days now...
Anything? Ive posted the results from Root Check... really didnt think rooting would be this much of an ordeal
How about if you unroot and start over.
Get a terminal (any terminal) from the market or if you have adb set up and run these commands.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
reboot
Then start over with the update.zip from the stickie that I show you yesterday.
I don't usually solicit thanks but this is going on two days now. How about a little something for the effort, eh? hahaha
I did try ot unroot last night with one click root and it says Im not rooted when I try that. I did use the update.zip from the sticky you gave me.
When i used the terminal I got:
rm failed for -r/system/bin/su, no such file/directory
reboot: operation not permitted
At this point, i would say Odin back to stock or try to re-root with the first method you tried. I agree though, it should not be this hard to do it. If you do end up going back to stock, just use the update.zip method to root it. It works so much easier.
Like I said yesterday, it took less than 3 mins to do it. It actually took me longer to download it than to do it and I never once hooked up to a PC. Did it all through phone with browser, xda app and root explorer.
itsLYNDZ said:
When I used the terminal I got:
rm failed for -r/system/bin/su, no such file/directory
reboot: operation not permitted
Click to expand...
Click to collapse
Did you type su and then enter first? Did ask for superuser permission? From what you posted last night and now this, I am almost positive that you are not rooted and Odin-ing back tostock is the way to go and start over.
I just deleted the update.zip file. im gonna start over, again. Should it remain zipped? Or do I need to extract it? Ive also read somewhere the update.zip needs to go in the j:/ or the root of the internal sdcard? I dont see that anywhere on the internal sdcard or anywhere in my files. Ill try the terminal again.
I'm in a pretty bad situation.. (I think..) In short: I rooted my HTC EVO 4G LTE, unlocked bootloader, installed viper rom, by mistake deleated a root file, (so now i have the su brainy app, and cant uninstall it.) But i have no root. Then i re-locked my bootloader (while trying to fix my root...)
*UPDATE* users are suggesting i fix it useing recovery: I DONT HAVE RECOVERY
This is what Root checker said:
Root Access is not properly configured or was not granted.
Superuser Application Status:
Superuser application - version 3.1.3 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwxr-xr-x root shell 91980 2008-08-01 08:00 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 91980 2008-08-01 08:00 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.
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 EVO device by Root Checker Pro version 1.2.7 from joeykrim in the Android Market
I dont understand this jibberish.. Im still a noob.
Please help me ether:
1) return it to stock
or
2)Re-root it.
Thanks in advance,
Messed up EVO owner.
do you still have TWRP installed as your recovery?
Just reflash the ROM.
Problem solved.
Rxpert said:
Just reflash the ROM.
Problem solved.
Click to expand...
Click to collapse
I wish i can but i no longer have root or recovery
bog3nator said:
do you still have TWRP installed as your recovery?
Click to expand...
Click to collapse
No. But i cant get it because im not rooted. (and cant root b/c i have viper rom and my pc wont recognize it as evo 4g lte)
does you phone turn on? if it does then run regaw mod and unlock bootloader and it will reflash everything for you...
bog3nator said:
does you phone turn on? if it does then run regaw mod and unlock bootloader and it will reflash everything for you...
Click to expand...
Click to collapse
Because i have viper lte rom regaw mod wont recognise me and says "this is not a htc evo 4g lte"
did you do the gameloft tweak? if you did thats why, that tweak edits the build prop. you can always ruu back to stock and re-run the rooter
bog3nator said:
did you do the gameloft tweak? if you did thats why, that tweak edits the build prop. you can always ruu back to stock and re-run the rooter
Click to expand...
Click to collapse
I did. Thank for your tip (and i will hit the like botton.) but if the build prop. is changed, will ruu recognize me?
i would think it would. but i havent tried to ruu before so i am not sure what the exact process is
edit: i will hit the thanks button for you so i can pop you thanks cherry
Stop. You don't need to ruu. First install twrp recovery. Then wipe and reflash your favorite Rom. Are you s-off?
he said he is not currently rooted and the bootloader is locked again. so goo manager wont be able to get root permissions and he cant fast boot if the bootloader is locked.
---------- Post added at 09:48 PM ---------- Previous post was at 09:29 PM ----------
Did you try installing supersu from the market and see if that works. I don't know if it would but couldnt hurt also.
Sent from my EVO using xda app-developers app
That doesn't mean he is s-on if he was s-off at some point. Boot into bootloader. Does the phone say s-on or s-off?
{ParanoiA} said:
That doesn't mean he is s-on if he was s-off at some point. Boot into bootloader. Does the phone say s-on or s-off?
Click to expand...
Click to collapse
Its S-ON
I have ruu ready to run.. Should i go ahead with it now, or is there something else to do?
Running ruu can't hurt.. u will just have to start over that's all ..and with one click root that's easy
firmbiz94 said:
Running ruu can't hurt.. u will just have to start over that's all ..and with one click root that's easy
Click to expand...
Click to collapse
ok thats good to know, thanks!
thats why i recommended it, if you dont mind starting over...how did it all go?
bog3nator said:
thats why i recommended it, if you dont mind starting over...how did it all go?
Click to expand...
Click to collapse
:laugh: Its like a new phone! Thank you!!!! Now im just gonna re-root it and im good to go!
I was wondering if someone could help. I have followed all the instructions of this post http://forum.xda-developers.com/showthread.php?t=1886460 It says it is successful, but still do not have root access. Could someone tell me if they see something wrong?
Here is the log from Root Checker.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.98 - 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: -rwsr-sr-x root root 91988 2012-11-20 09:39 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 /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:
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 C5155 device by Root Checker Pro version 1.3.0 from joeykrim in the Android Market - http://goo.gl/NcnHn
Fixed
Removed Super SU all is now ok.
I have been trying to root my Kyocera Rise I just got a week ago, and I am having this problem as well. However it seems that removing SuperSU isn't doing the trick. What was your method of going about this? I'm so lost without root access . I followed the tutorial to a T, multiple times, as other users have suggested, and I get nothing! Thanks for your time!
I had the same problem I went into stuff folder of binry and replaced supersu with su, re-ran it and root took 1st time
Sent from my Amazon Kindle Fire using Tapatalk 2
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Could not get v17 to work. I saw in the thread v3 was supposed to so I tried it and after a few attempts I got it.
Sent from my LG-VM670 using Tapatalk 2
any luck on 4.0.4?
the latest krise firmware version is 4.0.4.
In the thread the guy who reported rooting success didn't say his version num, so it could be outdated information.
I am on 4.0.4, was not aware of any other version for this phone
Sent from my Amazon Kindle Fire using Tapatalk 2
jimchee said:
Forgot this but make sure you open super su and in installing from within app and then uninstall in market before running with su apk.
Sent from my C5155 using Tapatalk 2
Click to expand...
Click to collapse
Could you please be more specific with your procedure?
sonic_knx said:
Could you please be more specific with your procedure?
Click to expand...
Click to collapse
Since you have a rooted copy now, could i borrow a backup or a copy of the system folder because I installed hp beats audio installer (do not do) and my audio drivers are messed up. It is really taking a long time to get a copy so I was hoping that you guys would have a good copy. I also have another guy with the same issue so please help us.
the actual problem and a slight fix...
The actual problem/glitch with supersu is when it tries to promt access for su it freezes the app. When I tried unistalling supersu and installing superuser. It did not work for me even with the proper uninstall procedure (going into super su settings and click uninstall and prepare for new su app. Then go to the play store search supersu, google still thinks installed so click uninstall from there then immediatly search and install superuser.) I even tried going into the root setup folder I downloaded and switched the su apk files to start the root fresh... and still nothing. I figured out its the problem with the app trying to promt you for su access (ether app) bcs when I went into the settings I changed it to automaticaly grant su (TO EVERY APP READ BOTTOM DISCLAIMER) instead of promting you to ask for su.
DISCLAIMER: I AM NOT RESPONSIBLE FOR A ROUGE APP TAKING ADVANTAGE OF YOUR PHONE WITH YOUR SU SET TO GRANT ACCESS TO ALL APPS INSTEAD OF PROMTING YOU FOR YOUR ACTION ON ACCESS.
root VM rise
I used this method to root my Rise it says hydro but works on rise too.
http://www.cricketusers.com/content/646-root-cricket-wireless-kyocera-hydro-tutorial.html
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.
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