Develop Bugs

I think I messed up my root...

I'm currently running on yakju 4.1.1 and I think I've accidently messed up my root privileges. I think I somehow messed up my su by clicking the root button in Nexus Root Toolkit 1.5.
Cause:
I've always used Voodoo OTA Rootkeeper to keep my root. I update the SuperUser app via the market and found out that my su binary was out of date. I've tried various ways to update the su binary but gaining root access always resulted in a failure within the SuperUser app so finally I decided to try out the root toolkit. By clicking the root button in the app I think I've only made my situation worse....
Now I'm seeing that my su backup in the Rootkeeper app is messed up and I can't seem to delete it. The RootKeeper app seems to think that I'm still rooted and I can't successfully do the "temp-unroot" as well. Other apps such as Titanium Backup can't detect my root status now....
Can anyone offer any suggestions without re-flashing my image?

ayang02 said:
I'm currently running on yakju 4.1.1 and I think I've accidently messed up my root privileges. I think I somehow messed up my su by clicking the root button in Nexus Root Toolkit 1.5.
Cause:
I've always used Voodoo OTA Rootkeeper to keep my root. I update the SuperUser app via the market and found out that my su binary was out of date. I've tried various ways to update the su binary but gaining root access always resulted in a failure within the SuperUser app so finally I decided to try out the root toolkit. By clicking the root button in the app I think I've only made my situation worse....
Now I'm seeing that my su backup in the Rootkeeper app is messed up and I can't seem to delete it. The RootKeeper app seems to think that I'm still rooted and I can't successfully do the "temp-unroot" as well. Other apps such as Titanium Backup can't detect my root status now....
Can anyone offer any suggestions without re-flashing my image?
Click to expand...
Click to collapse
As of Nexus Root Toolkit 1.5.2, I do not see yakju 4.1.1 in the list of supported devices.

yakalid said:
As of Nexus Root Toolkit 1.5.2, I do not see yakju 4.1.1 in the list of supported devices.
Click to expand...
Click to collapse
I've figured out the solution to my problem: just re-push su & Superuser.apk to /system/su and /system/apps/Superuser.apk respectively.
Basically I referenced this thread: http://forum.xda-developers.com/showthread.php?t=1531865
Since I already have su and Superuser.apk in my /system (although I think I tainted both files), all I needed to do was grab clean versions of su and Superuser.apk and adb push em through and type "adb shell su" to make the # appear. I was even able to update su binary within Superuser, awesome :good:
Note: Once you do step 6, your prompt should change from $ to #. If not, it did not work.
7) Mount the system partition as rw: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
8) Copy su to /system: cat /data/local/tmp/su > /system/bin/su
9) Change permissions on su: chmod 06755 /system/bin/su
10) Copy Superuser.apk: cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
11) Change permissions on Superuser.apk: chmod 0644 /system/app/Superuser.apk
12) Mount the system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
13) Rescind root: exit
14) Exit the ADB shell: exit
Click to expand...
Click to collapse
Hope this helps with people who are having troubles with Superuser/su not gaining root access.

If you have an unlocked bootloader and the SU binary is still on the phone, this should fix the issue:
http://forum.xda-developers.com/showthread.php?t=1765754
As for the superuser APK, it does NOT need to be moved to the system folder, it just needs to be downloaded from the marketplace and will function if the su binary is present with proper permissions.

Matridom said:
If you have an unlocked bootloader and the SU binary is still on the phone, this should fix the issue:
http://forum.xda-developers.com/showthread.php?t=1765754
As for the superuser APK, it does NOT need to be moved to the system folder, it just needs to be downloaded from the marketplace and will function if the su binary is present with proper permissions.
Click to expand...
Click to collapse
I guess it makes sense, the only real issue was my su permissions.
I did this with a locked bootloader btw.

Problems with GBTweaked and R800x

Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.

Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app

otonieru said:
Maybe the button assigned to enter cwm has changed?
Last time i use kernel that assign back button for cwm, but since i have cwm on my system that use volume button to enter recovery mode, so the back button function is nullified automatically
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
Well, I don't even get the blue light on boot to indicate it is waiting for me to push the button...
Additionally, I keep finding a lot of chmod/rm/ls permission denies whenever I tried to reinstall superuser, or use the PC installer for CWM and Titanium keeps FC whenever I try to start it.

I just ran rootchecker and got this:
Congratulations! You have root access!
Superuser Application Status:
Superuser application - version 3.0.7 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/bin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: exec: ls: permission denied
Analysis: Setuid attribute NOT present and root user ownership is NOT present. Root access is NOT correctly configured for this file!
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
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 R800x device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Any thoughts?

edwinen said:
Hi,
Last night I installed the latest CDMA version of GBTweaked for my locked R800x. I am running into the standard no wifi issue, however, when I tried to install the wifi modules, I found myself unable to access CWM.... I tried to reinstall CWM with no luck. Flashtool isn't helping much with restoring to a previod nandroid backup either. Help would be greatly appreciated.
Click to expand...
Click to collapse
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.

chery2k said:
I am assuming you have root access. Download an app called x-parts from the googleplay store that will install the CWM for you. I don't remember how to get into recovery by using the app but I think it is pressing the volume d-rocker down or up. Play with your xperia play buttons a little and you will be able to get into recovery.
Click to expand...
Click to collapse
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.

edwinen said:
I do have root, or at least it still seems like I do, with the exception of the errors root checker is giving me. X-parts never worked for me before I changed roms, and it isn't working now. The only way I could get into recovery was by using CWM v. 5.
Whenever I try to install now however, it says it installed, and to reboot, however, when it is rebooting, I never get the blue light like I used to, and when it loads all the way into the system and go back into CWM/x-parts it tells me recovery isn't installed, and that my phone is supported.
Click to expand...
Click to collapse
Do not use an auto-installing app for CWM.
If you are on windows, use RecoveryX.
Sent from my Kindle Fire

Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.

lightningdude said:
Sounds like you need to download the su binaries. In the superuser app, go to your settings menu and look for the option to update your su binaries.
Click to expand...
Click to collapse
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)

edwinen said:
Hmm.. any way of doing this without an internet connection? Right now I have no wireless functionality, additionally my reception is very minimal here (no 3G atm)
Click to expand...
Click to collapse
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.

lightningdude said:
yeah, it involves pushing to the su folder via adb, but I don't remember the steps involved. Searching for a manual way to root any phone should turn that bit up.
Click to expand...
Click to collapse
Yeah... well, whenever I try to do anything with adb shell, i get permission denied, I can't even ls!!!

how about re-flashing kernel? doom kernel should bring along CWM as well...

otonieru said:
how about re-flashing kernel? doom kernel should bring along CWM as well...
Click to expand...
Click to collapse
Hmm.. well looks like my only option is to wait for my bootloader unlock... but I have not heard back from them in about 5 days.

They r quite slow in replying email, contact them via gTalk directly.. or just pay 1st (like what i did), when they receive the money they will feel more responsible to finish the service, LoL
Sent from my R800x using xda app-developers app
---------- Post added at 11:28 PM ---------- Previous post was at 11:27 PM ----------
For now i will suggest to falshback to original stock via flashtool..
Sent from my R800x using xda app-developers app

Well.. ended up unlocking the phone, and been messing with various options. Nothing seems to be working quite well, although it is because I am trying to use CM10 and CM9 which dont seem TOO stable.. but eh... Thanks for all the help everyone!

[Q] Superuser after OTA

Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks

So you can't use boot unlocker so on play store?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Maybe you need to fix permissions.
Did you have ROM Manager by any chance with root access granted? If so you could flash CWM from there, and then apply the latest SuperSU zip from CWM.

skyes113 said:
Hi Everyone,
So I have updated to Jellybean (4.1.1) via the OTA update and my bootloader become locked again due to the update.
I have Voodoo OTA Rootkeeper installed so fortunately I was able to restore root and Superuser is working fine (so I thought)
Until yesterday, I install an application that would require root access and it appear to me that Superuser was not granting this access.
However previous application that has the access granted by Superuser is still intact.
I tried updating SuperUser binary and encounter the error "Gaining root access..... Failed"
It appears to me that new request for root access was not allowed anymore but previous granted access still works fine.
I do not want to unlock my bootloader again as this means everything will be wipe out.
Therefore Flash via CWM recovery mode is not an option for me.
As I still have root access on ES File Explorer, it there any possibility that I can manually update Superuser (or switch to SuperSU) using the ES File Explorer? Like copying the new apk over to the /system/app ?
Any help is appreciated. Thanks
Click to expand...
Click to collapse
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.

efrant said:
Use ES File Explorer and change the permissions on /system/bin/su (or /system/xbin/su) to 6755 and you will be all set.
Click to expand...
Click to collapse
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.

skyes113 said:
I see that the Permission of the SU from ES File Explorer is rwx r-x r-x . I believe this is already the correct permission?
I'm thinking if it's possible for me the get the latest binary for Superuser and replace the SU file using the file explorer. Will this work?
Unfortunately I don't have rom manager as well.
Click to expand...
Click to collapse
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Those are not the correct permissions. The setuid bit needs to be set as well. What you posted is 0755, not 06755.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.

skyes113 said:
ES File explorer doesn't seems to be able to allow me to set the setuid bit.
I guess I just have to figure out how to use adb to do that.
Click to expand...
Click to collapse
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
I just checked and you're right. (i only ever use root explorer.)
In a terminal window:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
chmod 06755 /system/xbin/su
I would also symlink it to bin:
ln -s /system/bin/su /system/xbin/su
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?

skyes113 said:
I managed to do the above. However still no luck with updating SuperUser binary and still encounter the error "Gaining root access..... Failed"
I believe after doing the above I should get permissions (-rwsr-xr-x) but i'm seeing the permission as -rwsr-sr-x
seem like something is wrong?
Click to expand...
Click to collapse
Strange. I have no idea what the problem would be then.
What I would do is boot up CWM, and re-flash an su package.
The permissions are fine: -rwsr-xr-x = 04755 and -rwsr-sr-x = 06755. Both will do the same thing.

Also I see nothing in the OTA package that would relock your bootloader. You're sure that's exactly what happened? If it did, maybe someone here could pinpoint the component of the OTA package responsible for this?
Sent from my Galaxy Nexus using Tapatalk 2

Looks to be a problem on su.
I download the latest binary and replace it using adb + busybox and now it works fine.
Thanks!

[Q] SU Binary error upon Execution: No root access

Info: For those of you who need more info on my SU Binary (/system/bin/su), it's NOT out of date. Its the newest version for galaxy s4 m919.
My problem: /system/bin/su (SU binary files) will not execute.
Why?...: Because, access to execute binary files on system is denied (I don't have root access/permission). EEEK.
here's the Logs from root checker Pro: (In no particular order)-
SuperSU application - is NOT installed.
SuperUser - Installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 380532 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!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2013-10-11 02:57 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.
Alternative Location
Check Command: ls -l /system/xbin
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

more details
Extra info that I didn't include: I originally WAS rooted, running stock Samsung ROM (factory ROM) and I rooted using ODIN. So after rooting, I installed CyanogenMod 10.1.3.1, which does not come with root installed by default.
*SIGH* So... I want to know how to root CyanogenMod... So supposedly following the instructions by Root checker pro Logs,
I need to execute /system/bin/su. (Which won't work, unless a magical "S-Off" appears so I can execute it. But, then executing would be pointless because I would be already rooted with S-Off.
Help please, anyone? Could I root cyanogenmod from the computer terminal? Is there a way to override system permissions and execute su binary?

As per all your other post. Have you enable Root in Developer Options? CM ROM now has root disable by default.

Root options...
Root options in CyanogenMod Developer Options are not displayed in my settings...
What exactly does the toggle panel say for it? I can take a screenie of my settings..?
sorry for my ignorance with CyanogenMod... The last time I flashed CyanogenMod
was with CyanogenMod version 5, lol. And that was 3 years ago (I had an HTC Inspire 4G)

System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]

In reply...
dynospectrum said:
System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]
Click to expand...
Click to collapse
Well then. That was not so loving and friendly. Lol. And I have done so, btw.. My developer options are enabled, but the root access panel is not
In there. infact, there was a new section called "SuperUser", and I had set the root access panel to "Allow ADB and Apps" like you said.
But in return, no cigar. No root rights, even still. :/

Same here I'm using beanstalk 4.3 and most of the root apps work but some don't for example gamekiller, the few times I installed it it denied it before the prompt window popped out then after a few tries it finally granted it but before I pressed grant it said WARNING GAMEKILLER HAS A COMMAND (not sure about that part) android.permission.ACCESS_SUPERUSER not declared so I went into super user settings and I checked that option so I tried searching a value number and as soon as I press search it doesn't do anything then I press help and it tells me it needs root access which has been give
Sent from my SGH-M919 using XDA Premium 4 mobile app

Download and flash in recovery: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

Yay.
I've flashed that in CM10 ROM several times, and no root. But no worries, I'm running an awesome, fast, great battery life AOSP Based ROM (Completely AOSP, actually) and it comes rooted
The ROM is actually solely based off of googles open source code from android 4.3, with a few of the major components hand-picked from other Dev sources. The ROM is called-
Google Edition s4
For all who wish to download this as well as I did, here's the link to this epic ROM:
http://forum.xda-developers.com/showthread.php?t=2341026

Thanks
Thank you, this method worked for me. So much misinformation out there, I tried like 20 other bogus remedies before this. I could hug you.

same problem
I rooted my phone before,then I unroot it. But now when I am trying to root it again I'm facing same problem with superuser, it's saying that su binary is outdated and its not updating also, and I don't have root permission so that I can fix it with several methods which I found by google it.

Just Rooted My S3 But SU Is Missing A Binary

I just rooted my ATT S3 4.3. I did everything the tutorial said to do except when it got the part wherr odin reboots ur phone, i had to reboot it myself yo makr it go in cwm recovery. So once I was done rooting my phone and turned it on for the 1st time I instantly was greeted with superuser has stopped and security violations. So I tried random fixes from google and it keepa teling me there is no binary code. I can't figure out how to fix this, can anyone help me?

Which tutorial did you follow?

audit13 said:
Which tutorial did you follow?
Click to expand...
Click to collapse
I can't find it anymore. It was on this forum and it said it was for att S3 phones. Is there an area where all the ways to root are?
This is what root checker pro gave me as the results.
Super User Application Status:
SuperSU application - version 1.93 - 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 113036 1970-08-25 22:58 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:
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

Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

laughingT said:
Try Chainfire's CF autoroot with SuperSU, including google play SSU update to App? It sounds like you failed to reboot into recovery first before doing a normal boot. After flashing via odin, the root is temporary and will be wiped during a normal boot, unless you first reboot into recovery. So, you have to uncheck the reboot after flash option in odin. After successful flash, pull usb cable and boot into recovery using three button method.
Did you use CF autoroot? Try it again.
http://forum.xda-developers.com/showthread.php?t=1963790
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did reboot into recovery. I remeber the files I downloaded were named clockword mod and another was called superboot with cwm. Don't k ow if that helps.
I'm having a big issue though, I had tried fixing it by flashing dif ways, now whe I try tk flash it. When it loads up in download mode, my phone turns off or of ot doesn't do that, after I flash my phone and it reboots, it shows a red screen.
EDIT:
I just tried that root method you suggested and I still have the same issues. I don't know what to do!
EDIT 2:
I fixed it by using this site http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html. Specifically, these instructions:
Download and install the latest APK for SuperSU like MrW0lf suggested.
I was having the same exact problem (unfortunately, SuperSU has stopped), so I downloaded the latest UPDATE-SuperSU file and extract it to have supersu APK, put it on my SD card in my phone and installed it from there.
It was strange because the version that was already on my phone was the same 1.89 version that I downloaded, but regardless, when I clicked on the APK, it saw it as an update, it asked to disabled knox, and worked like a charm.
- See more at: http://www.w0lfdroid.com/2013/12/Fi...y-S3-S4-Note2-Note3.html#sthash.0nlj3XHO.dpuf
PS: this is the root method I had 1st followed, http://forum.xda-developers.com/showthread.php?t=1726960