After so many tutorials on Forum for nv_data.bin permission denied, none of them worked for me. Is there any 100% working tutorial.
regards
karabey said:
After so many tutorials on Forum for nv_data.bin permission denied, none of them worked for me. Is there any 100% working tutorial.
regards
Click to expand...
Click to collapse
There's an app called mount system on the market. Install it & ask it mount always as r/w access at boot.
PS : You need to have root access.
Thanks but not worked.. Cant still read the nv_data.bin
Ok have saved now the bml3.bak but there is no Code saved if i try to extract by sgux2.exe
HEX
53534E56A6A7FA1A0709542A1E85E257F98A6F14E2E19CA932EBEC93945930F6D0D9713DF61AB70CA4D57F7F9BCEDD924B888C6AAE9074B9D49D8FEEC8C021A97D4882BEFF922E8B004646464646464646000000000000000000000000000000000000000000000000323332303523
323332303523 = 23205
Any help?
My friend who use the Phone could read the Codes and made an Froyo Update. But after the Update Code were not able to enter. It gave the Error that is wrong.
ProductCode: GT-i9000HKDONE
You can get permission by adb shell or terminal emulator by typing:
su
busybox chown 1001:1001 /efs/nv_data.bin
(reboot)
I tried your method, but I still get permission denied. Here is what I did and the list of the file under /efs:
C:\SDK\tools>adb shell
$ su
su
# busybox chown 1001:1001 /efs/nv_data.bin
busybox chown 1001:1001 /efs/nv_data.bin
# reboot
reboot
C:\SDK\tools>adb shell
$ su
su
# ls -l /efs
ls -l /efs
-rwx------ radio radio 2097152 2010-10-30 04:57 nv_data.bin
drwxrwxrwx radio radio 2010-07-17 09:31 imei
-rwx------ radio radio 32 2010-10-30 04:57 nv_data.bin.md5
#
iScream^ said:
You can get permission by adb shell or terminal emulator by typing:
su
busybox chown 1001:1001 /efs/nv_data.bin
(reboot)
Click to expand...
Click to collapse
lan_baba said:
I tried your method, but I still get permission denied. Here is what I did and the list of the file under /efs:
C:\SDK\tools>adb shell
$ su
su
# busybox chown 1001:1001 /efs/nv_data.bin
busybox chown 1001:1001 /efs/nv_data.bin
# reboot
reboot
C:\SDK\tools>adb shell
$ su
su
# ls -l /efs
ls -l /efs
-rwx------ radio radio 2097152 2010-10-30 04:57 nv_data.bin
drwxrwxrwx radio radio 2010-07-17 09:31 imei
-rwx------ radio radio 32 2010-10-30 04:57 nv_data.bin.md5
#
Click to expand...
Click to collapse
not workinggg.......
Why do you want to read the file?
Have you lost your imei? If so, was the phone sold to you?
Don't bother with the codes. Use the hex edit method to change the lock status to 0:
http://forum.xda-developers.com/showthread.php?t=761045
p.s. you should delete the file you posted... that's some bad security there.
Here's the problem from a logcat after trying to run titanium backup:
E/su ( 6867): Getting exe path failed with 13: Permission denied
I AM rooted. I remounted /system as read/write. Permissions are perfect:
from /system/bin:
# pwd
/system/bin
#ls -l su
-rwxr-xr-x root shell 22240 2008-02-29 20:33 su
#
Just to prove that I have root permissions:
# chmod 666 su
# ls -l su
-rw-rw-rw- root shell 22240 2008-02-29 20:33 su
#
Just for the heck of it I tried a 777 - same problem.
This is duhRIVing me nuts!
Could exposed framework be the issue? Before I installed it, I didn't have any problems? But I also at the same time installed several torrents. Could my problem be viral? Below is the script from root checker and two errors regarding root. Any insight would great. And I will extend my gratitude to everyone who contributes to this great forum, for your tireless work and selfless support.
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.55 - 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 104800 2014-01-10 00:02 su
Analysis: Setuid attribute is present and root user ownership is 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:
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 LG-D800 device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market - http://goo.gl/NcnHn
Sent from a PollutedG2 using the xda premo app
Your supersu is like ancient
Sent from my LG-G2 using Tapatalk
You are right, I got the latest su and now functions as it ought to.
Sent from a PollutedG2 using the xda premo app
Hi.
The following report was generated by Root Checker Pro.
Can someone please tell me what it means???
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-01-26 07:43 su
Analysis: Setuid attribute is not present BUT root user ownership is 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:
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 SM-N9005 - Android 4.4.2 device by Root Checker Pro version 1.3.7 from joeykrim in the Android Market -
alessandro77889900 said:
Hi.
The following report was generated by Root Checker Pro.
Can someone please tell me what it means???
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-01-26 07:43 su
Analysis: Setuid attribute is not present BUT root user ownership is 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:
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 SM-N9005 - Android 4.4.2 device by Root Checker Pro version 1.3.7 from joeykrim in the Android Market -
Click to expand...
Click to collapse
Means you have rooted phone which is installed in xbin folder
meawww said:
Means you have rooted phone which is installed in xbin folder
Click to expand...
Click to collapse
Thank you.
I just was not certain about the " Executing this file can grant root access."
I have a Docomo Galaxy S5, SC-04F, G900D, running Android 6.0.1 Marshmallow.
After the recent update to 6.0.1, my phone runs hot, the battery drains fast, and it turns out this is because of some process called AtFwdService, which does some screencasting function I don't need. It's part of the Android system, though, so it can't just be uninstalled. I thought I'd root my phone and forcibly delete it. Soft disabling apps like Package Diabler Pro don't seem to sufficiently suppress it.
So, I used Odin, I downloaded the proper CF-auto root for my model (double and triple checking, because I know how important it is to have the right packages for the right models). The flash process from Odin went okay. I had to disable auto-reboot, so, following advice on this forum, after Odin reported success, I manually powered off and on, and booted into recovery manually. There I saw the red android and it reported successful rooting. Everything about the root process went according to how all online instructions indicated it should look.
When I first booted, I saw the Supersu icon in my application tray, but, when I click on it, it says: "All apps associated with this action have been turned off, blocked, or not installed". Hmm... I installed Root Checker, and it failed to verify that I'm rooted.
Root checker generated a report that I've attached below.
In any case, how do I make my efforts at rooting my device actually have the result of my device being rooted?
Thank you for any help.
Here is the report Root Checker gave me:
Code:
Overall Status: Root access is not properly installed on this device
Feedback Mode: Install Root
Issue: Not installed su binary and unable to access root user account
Stage 1 - Superuser App: Installed
Installed: SuperSU Pro by Chainfire - version 2.78
Installed: SuperSU by Chainfire - version 2.74
Stage 2 - Superuser Binary Files: Not Installed
Standard Location
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
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
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative System Environment Location
Command: ls -l /su/bin/su
Result: /su/bin/su: No such file or directory
Analysis: File /su/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Error
Error: java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: True
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Hi!
I can tell you how I rooted my phone:
* flash a custom recovery - TWRP- by ODIN
* flash SuperSU by TWRP
Reyse said:
Hi!
I can tell you how I rooted my phone:
* flash a custom recovery - TWRP- by ODIN
* flash SuperSU by TWRP
Click to expand...
Click to collapse
Thanks for responding!
Just so I understand you... you're saying you just used the custom stock ROM, but changed the recovery, and then installed (flashed) SuperSU from inside TWRP recovery?
Any chance you could link to the TWRP recovery you used?
martin_tokyo said:
Thanks for responding!
Just so I understand you... you're saying you just used the custom stock ROM, but changed the recovery, and then installed (flashed) SuperSU from inside TWRP recovery?
Any chance you could link to the TWRP recovery you used?
Click to expand...
Click to collapse
I have G900T model (codename klte) , but TWRP is available for your model also.
Your model is kltekdi
This is the Smsung S5 TWRP official page https://twrp.me/devices/samsunggalaxys5qualcomm.html
and, fortunately, your phone has support (Japan (SCL23, SC-04F):
Choose that link and choose twrp-3.0.2-1-kltekdi.img.tar
Follow the install instructions:
Odin Install Method (No Root Required): ....
Bootloader must be unlocked but if you were able to flash CF-auto root, your phone must be already unlocked
Reyse said:
I have G900T model (codename klte) , but TWRP is available for your model also.
Click to expand...
Click to collapse
Thanks for your help! I got my phone rooted and working perfectly...
... almost.
It turns out that if the phone is rooted, I simply can't use the functions that let me use the phone's RFID chip for electronic money. I searched hard on the web, but, my research indicates that rooted phones and electronic money are completely incompatible.
I need the electronic money feature, so I had to go back to non-rooted. And after all that effort!
Anyway, thanks for helping root my phone.
CF-auto root for Samsung S5 Docomo SC-04F Android 6.0.1
Where did you find the proper CF-auto root for my model? (Samsung S5 Docomo SC-04F Android 6.0.1)
I can only find CF-auto root for Android 5.0
Thanks!
martin_tokyo said:
I have a Docomo Galaxy S5, SC-04F, G900D, running Android 6.0.1 Marshmallow.
After the recent update to 6.0.1, my phone runs hot, the battery drains fast, and it turns out this is because of some process called AtFwdService, which does some screencasting function I don't need. It's part of the Android system, though, so it can't just be uninstalled. I thought I'd root my phone and forcibly delete it. Soft disabling apps like Package Diabler Pro don't seem to sufficiently suppress it.
So, I used Odin, I downloaded the proper CF-auto root for my model (double and triple checking, because I know how important it is to have the right packages for the right models). The flash process from Odin went okay. I had to disable auto-reboot, so, following advice on this forum, after Odin reported success, I manually powered off and on, and booted into recovery manually. There I saw the red android and it reported successful rooting. Everything about the root process went according to how all online instructions indicated it should look.
When I first booted, I saw the Supersu icon in my application tray, but, when I click on it, it says: "All apps associated with this action have been turned off, blocked, or not installed". Hmm... I installed Root Checker, and it failed to verify that I'm rooted.
Root checker generated a report that I've attached below.
In any case, how do I make my efforts at rooting my device actually have the result of my device being rooted?
Thank you for any help.
Here is the report Root Checker gave me:
Code:
Overall Status: Root access is not properly installed on this device
Feedback Mode: Install Root
Issue: Not installed su binary and unable to access root user account
Stage 1 - Superuser App: Installed
Installed: SuperSU Pro by Chainfire - version 2.78
Installed: SuperSU by Chainfire - version 2.74
Stage 2 - Superuser Binary Files: Not Installed
Standard Location
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
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
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative System Environment Location
Command: ls -l /su/bin/su
Result: /su/bin/su: No such file or directory
Analysis: File /su/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Error
Error: java.io.IOException: Error running exec(). Command: [su] Working Directory: null Environment: null
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: True
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Click to expand...
Click to collapse
My model g900f (docomo sc04f unlocked) how to install marshmallow??