Database Users

nv_data.bin Permission [TUTORIAL] needed

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.

How change permissions dir APP by ADB shell?

Hi i have problem with Kindle Fire,
i changed permissions folder system/app with app Root explorer and then I restart Kindle Fire and now dont want start. I think this is problem permissons for this directory.
Pleas can you send me setting permissions folder APP and how i can change it by ADB SHELL?
I have tried:
adb shell
su
chmod 644 app
Unable to chmod app: Read-only file system
THX very much .-(
Sory my english is very bad.

adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
or look here:
http://forum.xda-developers.com/showthread.php?t=1356257
guys please use the search function !

I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate

pitrsonek said:
I have tried it but:
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ chmod 755 /system/app
chmod 755 /system/app
Unable to chmod /system/app: Read-only file system
THX I'm a little desperate
Click to expand...
Click to collapse
you need root before you can do any of those (i.e. su)

But i think i have root because I install Google market and other app. Or how i can check if i have root?
THX!
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
4D1A002600000001 device
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls
ls
config
dropbox
cache
sdcard
acct
mnt
vendor
d
etc
ueventd.rc
ueventd.omap4430.rc
ueventd.goldfish.rc
system
sys
sbin
proc
init.rc
init.omap4430.rc
init.goldfish.rc
init
default.prop
data
root
dev
$

at the $ prompt type
su
should turn to # instead of $
Then you are Root.

krelvinaz said:
at the $ prompt type
su
should turn to # instead of $
Then you are Root.
Click to expand...
Click to collapse
Yes, what he said...you're confusing having root on the command line for "I installed su and superuser to their correct locations"

adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go

pitrsonek said:
adb shell
$ su
su
[1] + Stopped (signal) su
$ su
su
[2] + Stopped (signal) su
[1] Segmentation fault su
$
I have try install root by this manual: http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
I see device when i write: adb devices
I have executed runme.bat
but SU dont go
Click to expand...
Click to collapse
Something is wrong with your device then.

as a first step look if you have superuser.apk in \system\app\

Ho i dont have Superuser.apk in /system/app/

b63 said:
as a first step look if you have superuser.apk in \system\app\
Click to expand...
Click to collapse
Doesn't really matter if su is not working. Superuser.apk is just a wrapper for su and he's trying to do things on the command line so su is what he's calling to, not SuperUser.apk.
He either didnt root correctly to begin with or he did something after that messed things up. Temp rooting with zergRush and redoing things is most likely what he needs to do.

Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
Ther is content dir app:
c:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ ls /system/app
ls /system/app
-------------------------------------------------------------------------
ATVAndroidClient.apk
AccountAndSyncSettings.apk
AmazonVenezia.apk
ApplicationsProvider.apk
AudibleAndroidApplication-venezia.apk
CSApp-unsigned.apk
CalendarProvider.apk
CertInstaller.apk
Cloud9-unsigned.apk
Cloud9SystemBrowserProvider-unsigned.apk
Contacts.apk
ContactsProvider.apk
DefaultContainerService.apk
DownloadProvider.apk
DownloadProviderUi.apk
DrmProvider.apk
Email.apk
Facebook.apk
Gallery3D.apk
HTMLViewer.apk
IMDb-2.3.apk
KindleForOtter.apk
LatinIME.apk
Launcher.apk
LiveWallpapers.apk
LiveWallpapersPicker.apk
MagicSmokeWallpapers.apk
MarketIntentProxy.apk
MediaProvider.apk
MyAccount-unsigned.apk
OOBE-unsigned.apk
OTASilentInstall.apk
OtterAppManager.apk
OtterTutorial.apk
PackageInstaller.apk
PicoTts.apk
Provision.apk
Pulse-amazon.apk
QuickSearchBox.apk
QuickSettings.apk
Quickoffice_AMAZON_4.1.408_VC.apk
Settings.apk
SettingsProvider.apk
SystemUI.apk
TtsService.apk
UserDictionaryProvider.apk
VisualizationWallpapers.apk
VpnServices.apk
Windowshop.apk
air_runtime.apk
amazonmp3-unsigned.apk
com.amazon.dcp.apk
oem_install_flash_player_signed.apk
Superuser.apk
Vending.apk
$

agree - but it's an indication that his device is not rooted
i would suggest to install superoneclick to the computer and root again
all you need is here : http://forum.xda-developers.com/showpost.php?p=19789892&postcount=35

pitrsonek said:
Is ther somebody who can help me online on gtalk? I will pay you by PayPal. If anybody has freetime send me PM. THX
$
Click to expand...
Click to collapse
Maybe on Thursday I can. Busy until then.

I just run SuperOneClick and there is log http://jsfiddle.net/tVnDv/ from this program.

Kindle Fire is Back
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...

glad to help ...

pitrsonek said:
Jupiiie Kindle Fire is back.
So first i try SuperOneClikck install root, but this code doesnt go:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Then i tried unroot and this code go?
How my Kindle Fire start ,-) Its crazy but true.
Thank you very much guys...
Click to expand...
Click to collapse
I'm having the same issue, but when I go to change the mount permissions I get permission denied. Anyone care to give me some insight on how to fix it?

you have the $ prompt !!!
type su - the prompt has to change to #
then do the commands ...

Rooted and permissioned correctly but getting a permissions denied on su

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!

Permission Denied writing to some folders

Hi, I just upgraded to OxygenOS 3, I did a full wipe (including Internal Storage), and then moved back, via adb push, some folders from my apps to the /sdcard. Now there are some folders that I just can't write to them at all, not even as root. see below:
Code:
[email protected]:/storage/self/primary/tmpFolder # pwd
/storage/self/primary/tmpFolder
[email protected]:/storage/self/primary/tmpFolder # ls -l
drwxrwx--x root sdcard_rw 2016-04-09 22:24 MyFolder
[email protected]:/storage/self/primary/tmpFolder # ls -l MyFolder/ |grep 201615
drwxrwx--x root sdcard_rw 2016-04-08 21:11 201615
[email protected]:/storage/self/primary/tmpFolder # touch test
[email protected]:/storage/self/primary/tmpFolder # touch MyFolder/test
[email protected]:/storage/self/primary/tmpFolder # touch MyFolder/201615/test
touch: 'MyFolder/201615/test': Permission denied
1|[email protected]:/storage/self/primary/tmpFolder #
Notice that I have tmpFolder and then MyFolder, to which I can write without any problems, but I have a tmpFolder/MyFolder/201615/ tthat I cannot write at all. Also notice the permissions, I have the same permissions for all folders, `drwxrwx--x root sdcard_rw`.

Bump! Anyone?

Root method for all original note 7's

This is the Root method for any and all original Explode 7's.
This works for all note 7 phones running on any and all firmware,(death updated firmwares as well) the only note 7 this method will not work for is the Note7FE. ENJOY!!
https://www.alliancex.org/viewtopic.php?p=16685#p16685

Anyone tried this yet?

rc0310 said:
Anyone tried this yet?
Click to expand...
Click to collapse
it works 100%, doesnt trip knox and no chance of bricking whatsoever

Work on Note 7 with FE Firmware?

Anybody has a copy of the N930W8VLU3APL1 firmware? Just the system.img would work too

DakiX said:
Work on Note 7 with FE Firmware?
Click to expand...
Click to collapse
does not work on the FE because the FE is not dirtycow vulnerable.

akiraO1 said:
This is the Root method for any and all original Explode 7's.
This works for all note 7 phones running on any and all firmware,(death updated firmwares as well) the only note 7 this method will not work for is the Note7FE. ENJOY!!
https://www.alliancex.org/viewtopic.php?p=16685#p16685
Click to expand...
Click to collapse
Hi, what features will stop working after root?
I assume android pay. What about s health, secure folder?
Sent from my SM-N930W8 using Tapatalk

You're in luck.
ARNOB said:
Anybody has a copy of the N930W8VLU3APL1 firmware? Just the system.img would work too
Click to expand...
Click to collapse
Yes i do have it and yes you definitely know by now it's nowhere to be found...100 bucks and ita yours.

C:\Users\User>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $ u:r:dnsmasq:s0
/system/bin/sh: u:r:dnsmasq:s0: not found
127|[email protected]:/ $ cd /data/local/tmp/super-chris/
[email protected]:/data/local/tmp/super-chris $ touch file
[email protected]:/data/local/tmp/super-chris $ echo FFFFFFFF >> root.sh
[email protected]:/data/local/tmp/super-chris $ chmod 777 *
cho u:r:init:s0 > /proc/self/attr/current <
cho u:r:init:s0 > /proc/self/attr/exec <
data/local/tmp/super-chris/root.sh <
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
chmod: chmod '/data' to 40777: Permission denied
dd: /data/su.img: Permission denied
dd: /cache/su.img: Permission denied
/data/local/tmp/super-chris/root.sh[36]: e2fsck: can't execute: Permission denied
/data/local/tmp/super-chris/root.sh[37]: resize2fs: can't execute: Permission denied
/data/local/tmp/super-chris/root.sh[38]: e2fsck: can't execute: Permission denied
/data/local/tmp/super-chris/root.sh[39]: resize2fs: can't execute: Permission denied
dd: /sbin/su: Permission denied
dd: /sbin/daemonsu: Permission denied
dd: /sbin/sukernel: Permission denied
dd: /sbin/sush: Permission denied
dd: /sbin/supolicy: Permission denied
dd: /sbin/app_process: Permission denied
dd: /sbin/libsupol.so: Permission denied
dd: /file_contexts: Read-only file system
dd: /sbin/launch_daemonsu.sh: Permission denied
mkdir: '/su': Read-only file system
dd: /su/su: No such file or directory
dd: /su/daemonsu: No such file or directory
dd: /su/sukernel: No such file or directory
dd: /su/sush: No such file or directory
dd: /su/supolicy: No such file or directory
dd: /su/app_process: No such file or directory
dd: /su/libsupol.so: No such file or directory
dd: /file_contexts: Read-only file system
chmod: chmod '/sbin' to 40777: Read-only file system
chmod: No /sbin: Permission denied
chmod: /su: No such file or directory
Function: selinux_compare_spd_ram, index[3], priority [2], priority version is VE=SEPF_SECMOBILE_6.0.1_0013
SELinux: Loaded file_contexts contexts from /file_contexts.
SELinux: Could not get canonical path /su/* restorecon: No such file or directory.
restorecon: restorecon failed: /su/*: No such file or directory
sh: /sbin/launch_daemonsu.sh: Permission denied
/data/local/tmp/super-chris/root.sh[65]: FFFFFFFF: not found
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
heres my log
i chmod 777 the file before I run it root.sh did the nmake commands first then the uid stuff
any help I have to return device today steps in the right direction appreciated thanks

christiansfreeman said:
C:\Users\User>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]:/ $ u:r:dnsmasq:s0
/system/bin/sh: u:r:dnsmasq:s0: not found
127|[email protected]:/ $ cd /data/local/tmp/super-chris/
[email protected]:/data/local/tmp/super-chris $ touch file
[email protected]:/data/local/tmp/super-chris $ echo FFFFFFFF >> root.sh
[email protected]:/data/local/tmp/super-chris $ chmod 777 *
cho u:r:init:s0 > /proc/self/attr/current <
cho u:r:init:s0 > /proc/self/attr/exec <
data/local/tmp/super-chris/root.sh <
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
chmod: chmod '/data' to 40777: Permission denied
dd: /data/su.img: Permission denied
dd: /cache/su.img: Permission denied
/data/local/tmp/super-chris/root.sh[36]: e2fsck: can't execute: Permission denied
/data/local/tmp/super-chris/root.sh[37]: resize2fs: can't execute: Permission denied
/data/local/tmp/super-chris/root.sh[38]: e2fsck: can't execute: Permission denied
/data/local/tmp/super-chris/root.sh[39]: resize2fs: can't execute: Permission denied
dd: /sbin/su: Permission denied
dd: /sbin/daemonsu: Permission denied
dd: /sbin/sukernel: Permission denied
dd: /sbin/sush: Permission denied
dd: /sbin/supolicy: Permission denied
dd: /sbin/app_process: Permission denied
dd: /sbin/libsupol.so: Permission denied
dd: /file_contexts: Read-only file system
dd: /sbin/launch_daemonsu.sh: Permission denied
mkdir: '/su': Read-only file system
dd: /su/su: No such file or directory
dd: /su/daemonsu: No such file or directory
dd: /su/sukernel: No such file or directory
dd: /su/sush: No such file or directory
dd: /su/supolicy: No such file or directory
dd: /su/app_process: No such file or directory
dd: /su/libsupol.so: No such file or directory
dd: /file_contexts: Read-only file system
chmod: chmod '/sbin' to 40777: Read-only file system
chmod: No /sbin: Permission denied
chmod: /su: No such file or directory
Function: selinux_compare_spd_ram, index[3], priority [2], priority version is VE=SEPF_SECMOBILE_6.0.1_0013
SELinux: Loaded file_contexts contexts from /file_contexts.
SELinux: Could not get canonical path /su/* restorecon: No such file or directory.
restorecon: restorecon failed: /su/*: No such file or directory
sh: /sbin/launch_daemonsu.sh: Permission denied
/data/local/tmp/super-chris/root.sh[65]: FFFFFFFF: not found
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
heres my log
i chmod 777 the file before I run it root.sh did the nmake commands first then the uid stuff
any help I have to return device today steps in the right direction appreciated thanks
Click to expand...
Click to collapse
looking at your logs you literally didnt follow the instuctions at all.
right after you type nmake run you have to turn on your mobile hotspot on the device and wait until it loads, then rur off mobile hot spot. right after u type nmake reverse you have to turn on your mobile hotspot on the device again and wait for it to finish loading and then turn off mobile hotspot. Then when you type nmake connect it should look like its hanging, there should not be your devices name followed by a $ or #, its just blank. at this point type in id and youll see that you are root. the type in : echo u:r:init:s0 > /proc/self/attr/current and then type in : echo u:r:init:s0 > /proc/self/attr/exec.
and lastly type in : sh /data/local/tmp/super-chris/root.sh
Now you are full SuperSu root, you csn type in adb shell and then su and youll see a # but know this, it isnt permanent yet so when you reboot, the root disappears and you have to do it over again, im still working on trying to mount the system to make it permanent.

Tried this step by step and doesn't work on my T-Mobile Note 7...
When on Step 12, I run the "/data/local/tmp/super-chris/root.sh" command and receive the following: (And, YES I am able to "adb push the files" and can see them using Root Browser)
C:\ndk\build>nmake connect
Microsoft (R) Program Maintenance Utility Version 14.11.25547.0
Copyright (C) Microsoft Corporation. All rights reserved.
"there is no prompt, type ls to test connection!!"
nc localhost 4040
id
uid=0(root) gid=0(root) groups=0(root) context=u:r:dnsmasq:s0
echo u:r:init:s0 > /proc/self/attr/current
echo u:r:init:s0 > /proc/self/attr/exec
/data/local/tmp/super-chris/root.sh
/system/bin/sh: <stdin>[4]: /data/local/tmp/super-chris/root.sh: not found
Here's the ADB push results:
C:\ADB\platform-tools>adb push C:\ADB\platform-tools\super-chris\ /data/local/tmp
C:\ADB\platform-tools\super-chris\: 14... 1.5 MB/s (103302641 bytes in 64.683s)

cplabaunza said:
Tried this step by step and doesn't work on my T-Mobile Note 7...
When on Step 12, I run the "/data/local/tmp/super-chris/root.sh" command and receive the following: (And, YES I am able to "adb push the files" and can see them using Root Browser)
C:\ndk\build>nmake connect
Microsoft (R) Program Maintenance Utility Version 14.11.25547.0
Copyright (C) Microsoft Corporation. All rights reserved.
"there is no prompt, type ls to test connection!!"
nc localhost 4040
id
uid=0(root) gid=0(root) groups=0(root) context=u:r:dnsmasq:s0
echo u:r:init:s0 > /proc/self/attr/current
echo u:r:init:s0 > /proc/self/attr/exec
/data/local/tmp/super-chris/root.sh
/system/bin/sh: <stdin>[4]: /data/local/tmp/super-chris/root.sh: not found
Here's the ADB push results:
C:\ADB\platform-tools>adb push C:\ADB\platform-tools\super-chris\ /data/local/tmp
C:\ADB\platform-tools\super-chris\: 14... 1.5 MB/s (103302641 bytes in 64.683s)
Click to expand...
Click to collapse
After pushing the folder to /data/local/tmp you have to type adb shell chmod -R 0777 /data/local/tmp
Also type ls /data/local/tmp/super-chris to see what's in the folder, it might be root1.sh but I'm pretty sure it's root.sh

akiraO1 said:
After pushing the folder to /data/local/tmp you have to type adb shell chmod -R 0777 /data/local/tmp
Also type ls /data/local/tmp/super-chris to see what's in the folder, it might be root1.sh but I'm pretty sure it's root.sh
Click to expand...
Click to collapse
Thank you for the suggestions...I will give them a try and report back. :good:

Ok...I can confirm the Temp Root instructions work with changing the file/folder permissions step. Unfortunately when performing certain Root functions, such as allowing Ad Block to update the Host file, the phone reboots...I tried this about 5 times all with the same result and just gave up and installed Blokada instead.