Database Users

Problem with Jeffs Kitchen... Permission Denied.

Here are the errors that I am getting when I try to build a rom based on the 4.00.16 TMobile Rom...
echo Warning: OS type not detected, you may need to set tounicode variable manually
./mkrom.sh: line 89: ./tounicode: Permission deniedwrite xip block starting at 81740000, with 4 fileswrite xip block starting at 81cc0000, with 62 files
Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.
Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.
Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.
!!! your rom is not known to me:
md5: 8ac9fd0d069f71b6113785cf724315ac
this bootloader seems to be V5.22 2003-05-15 17:46:55
This looks like something that Jeff would have to fix...
Anyone have any suggestions otherwise?
J

[Q] Security policy blocking native software

I am trying to make a rather complicated script work, but with all the shells I've tried so far I'm gettimg permission issues. Tried the sh of two differemt busyboxes, the default mksh and Bash 4.0
Also tried to use different interpreters but nothing changed.
Example of the errors I get:
Code:
/system/bin/threaddl: line 3: /system/bin/basename: Permission denied
/system/bin/threaddl: line 26: /data/local/bin/egrep: Permission denied
/system/bin/threaddl: line 26: /system/xbin/sed: Permission denied
/system/bin/threaddl: line 27: /data/local/bin/egrep: Permission denied
/system/bin/threaddl: line 26: /system/xbin/sed: Permission denied
/system/bin/threaddl: line 26: /data/local/bin/egrep: Permission denied
/system/bin/threaddl: line 27: /data/local/bin/egrep: Permission denied
These executables exist with 755 permission and have the root:root owner property

ntfs-3g-mount: mount failed: Permission denied

Hi!
I am trying to mount NTFS with ntfs-3g
I have root terminal open.
I write:
ntfs-3g /dev/block/sde1 /sdcard/ntfs
The path /sdcard/ntfs exists
I get error:
ntfs-3g-mount: mount failed: Permission denied.
What should I do?

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.

Help downloading the new kernel

The old instructions from Nvidia (new ones aren't available yet) say to set up the git directory with "repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-24-uda-r1.4-partner -m tlk/t210.xml". Do I use the same branch for the Oreo sources, or do I switch to the new "rel-29-r3-partner" branch? Thanks

Well, I tried compiling the current branch and it gave me a Nougat kernel, so I'm guessing Oreo is on rel29. However, it seems to be incomplete. "Repo sync" gave me the following error:
Code:
..
Fetching projects: 95% (534/562) Fetching project android/platform/external/seccomp-tests
Fetching project android/platform/prebuilts/build-tools
Fetching project tegra/prebuilts-licensed-binary-tlk-t210
fatal: Couldn't find remote ref refs/heads/stage-main-partner
fatal: Couldn't find remote ref refs/heads/stage-main-partner
error: Cannot fetch tegra/prebuilts-licensed-binary-tlk-t210
error: Exited sync due to fetch errors

I found I could bypass the error by editing .repo/manifests/tlk/t210.xml and commenting out the line for the prebuilt binaries, then downloading them from https://nv-tegra.nvidia.com/gitweb/?p=tegra/prebuilts-licensed-binary-tlk-t210.git;a=shortlog;h=refs/heads/rel-29-r3-partner. But I ran into another problem.
Code:
$ lunch foster_e-userdebug
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
/bin/bash: build/tools/normalize_path.py: Permission denied
build/core/product_config.mk:247: *** device/nvidia/platform/loki/t210/foster_e.mk: PRODUCT_NAME must be a valid C identifier, not "foster_e @inherit:". Stop.
I checked that all the files are readable and owned by me. No idea what to do here. Maybe the O sources just aren't complete yet.

@Mogster2K
i have the same problem with the sources:
Code:
error: Cannot fetch tegra/prebuilts-licensed-binary-tlk-t210
[...]
error: Exited sync due to fetch errors
Code:
/bin/bash: build/tools/normalize_path.py: Permission denied
Is the file executable? Does the following help?
Code:
chmod +x build/tools/normalize_path.py

It's already marked executable. I'm guessing that some stuff just hasn't been pushed to the repo yet.

Mogster2K said:
It's already marked executable. I'm guessing that some stuff just hasn't been pushed to the repo yet.
Click to expand...
Click to collapse
no the binaries are in the sh as a TGZ wacky way of doing but here is the extracted contents
https://www.androidfilehost.com/?w=files&flid=274922
I don't have a build environ for shield so you will need to handle that your self if you wanna build this into a usable blob

Legitsu said:
I don't have a build environ for shield so you will need to handle that your self if you wanna build this into a usable blob
Click to expand...
Click to collapse
I'm not sure how to search for info on how to build a usable blob, but if you can point me in the right direction I'm sure I can learn. Could you help with that?