Android Alliance

Hi. Just after 'nmake connect' I must type in the same window the command id? If that it was you mean, I have next one log:

Hidden Content: [SHOW]

C:\ndk\build>nmake connect

Microsoft (R) Program Maintenance Utility Version 14.11.25507.1
Copyright (C) Microsoft Corporation. Tous droits réservés.

"there is no prompt, type ls to test connection!!"
nc localhost 4040
NMAKE : fatal error U1077: '.\nc.EXE' : code retour '0x1'
Stop.

C:\ndk\build>id
'id' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

C:\ndk\build>

And there is log of adb shell:

Hidden Content: [SHOW]

C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
shell@graceqltebmc:/ $ 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
shell@graceqltebmc:/ $ echo u:r:init:s0 > /proc/self/attr/current
1|shell@graceqltebmc:/ $ echo u:r:init:s0 > /proc/self/attr/exec
1|shell@graceqltebmc:/ $ /data/local/tmp/super-chris/root.sh
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Operation not permitted
mount: Operation not permitted
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Permission denied
mount: Operation not permitted
mount: Operation not permitted
chmod: chmod '/data' to 40777: Operation not permitted
dd: /data/su.img: Permission denied
dd: /cache/su.img: Permission denied
e2fsck: Permission denied while trying to open /cache/su.img
You must have r/w access to the filesystem or be root
resize2fs 1.42.9 (28-Dec-2013)
open: Permission denied while opening /cache/su.img
e2fsck: No such file or directory while trying to open /data/su.img
Possibly non-existent device?
resize2fs 1.42.9 (28-Dec-2013)
open: No such file or directory while opening /data/su.img
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
127|shell@graceqltebmc:/ $
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
shell@graceqltebmc:/ $ 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
shell@graceqltebmc:/ $

anyone found a noob guide for this please?

How to change 60^ charging to 100%

GhostGH wrote: Fri Sep 29, 2017 5:38 pm Hi. Just after 'nmake connect' I must type in the same window the command id? If that it was you mean, I have next one log:

Hidden Content: [SHOW]

C:\ndk\build>nmake connect

Microsoft (R) Program Maintenance Utility Version 14.11.25507.1
Copyright (C) Microsoft Corporation. Tous droits réservés.

"there is no prompt, type ls to test connection!!"
nc localhost 4040
NMAKE : fatal error U1077: '.\nc.EXE' : code retour '0x1'
Stop.

C:\ndk\build>id
'id' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

C:\ndk\build>

And there is log of adb shell:

Hidden Content: [SHOW]

C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
shell@graceqltebmc:/ $ 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
shell@graceqltebmc:/ $ echo u:r:init:s0 > /proc/self/attr/current
1|shell@graceqltebmc:/ $ echo u:r:init:s0 > /proc/self/attr/exec
1|shell@graceqltebmc:/ $ /data/local/tmp/super-chris/root.sh
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Operation not permitted
mount: Operation not permitted
mount: Permission denied
mount: Permission denied
mount: Permission denied
mount: Operation not permitted
mount: Operation not permitted
mount: Operation not permitted
mount: Permission denied
mount: Operation not permitted
mount: Operation not permitted
chmod: chmod '/data' to 40777: Operation not permitted
dd: /data/su.img: Permission denied
dd: /cache/su.img: Permission denied
e2fsck: Permission denied while trying to open /cache/su.img
You must have r/w access to the filesystem or be root
resize2fs 1.42.9 (28-Dec-2013)
open: Permission denied while opening /cache/su.img
e2fsck: No such file or directory while trying to open /data/su.img
Possibly non-existent device?
resize2fs 1.42.9 (28-Dec-2013)
open: No such file or directory while opening /data/su.img
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
127|shell@graceqltebmc:/ $
C:\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
shell@graceqltebmc:/ $ 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
shell@graceqltebmc:/ $

Yes after typing nmake connect just type 'id' in the exact same terminal window to see that you are root. The terminal will look like it's hanging, shell@graceltebmc:/ $ should not be showing at all, the command line will be completely blank but ready to receive commands as root.

Sorry but the command nmake connect was finished with an error :

Hidden Content: [SHOW]

C:\ndk\build>nmake connect

Microsoft (R) Program Maintenance Utility Version 14.11.25507.1
Copyright (C) Microsoft Corporation. Tous droits réservés.

"there is no prompt, type ls to test connection!!"
nc localhost 4040
NMAKE : fatal error U1077: '.\nc.EXE' : code retour '0x1'
Stop.

C:\ndk\build>

And if I type id just in command line I have an error

Hidden Content: [SHOW]

C:\ndk\build>id
'id' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

C:\ndk\build>

What does nc.EXE do? Why the command nmake connect return an error of it? It seems that I have installed wrong the components of Visual studio... maybe.... Any idea?

P.S. OK, finally I have executed the command nmake connect and see what I have:

Hidden Content: [SHOW]

C:\ndk\build>nmake connect

Microsoft (R) Program Maintenance Utility Version 14.11.25507.1
Copyright (C) Microsoft Corporation. Tous droits réservés.

"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: can't execute: Permission denied

OK, I changed the permissions for root.sh and made it executable. And now I have this:

Hidden Content: [SHOW]

/data/local/tmp/super-chris/root.sh
Usage: mount [-r] [-w] [-o options] [-t type] device directory
196608+0 records in
196608+0 records out
100663296 bytes transferred in 2.034 secs (49490312 bytes/sec)
196608+0 records in
196608+0 records out
100663296 bytes transferred in 1.999 secs (50356826 bytes/sec)
/cache/su.img: recovering journal
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/cache/su.img: 369/6144 files (0.3% non-contiguous), 1943/24576 blocks
ext2fs_close2 : normal operation, return 0
resize2fs 1.42.9 (28-Dec-2013)
The filesystem is already 24576 blocks long. Nothing to do!

/data/su.img: recovering journal
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: 369/6144 files (0.3% non-contiguous), 1943/24576 blocks
ext2fs_close2 : normal operation, return 0
resize2fs 1.42.9 (28-Dec-2013)
The filesystem is already 24576 blocks long. Nothing to do!

203+1 records in
203+1 records out
104384 bytes transferred in 0.003 secs (34794666 bytes/sec)
203+1 records in
203+1 records out
104384 bytes transferred in 0.007 secs (14912000 bytes/sec)
99+1 records in
99+1 records out
50720 bytes transferred in 0.004 secs (12680000 bytes/sec)
565+1 records in
565+1 records out
289432 bytes transferred in 0.006 secs (48238666 bytes/sec)
99+1 records in
99+1 records out
50904 bytes transferred in 0.007 secs (7272000 bytes/sec)
43+1 records in
43+1 records out
22456 bytes transferred in 0.001 secs (22456000 bytes/sec)
653+1 records in
653+1 records out
334744 bytes transferred in 0.004 secs (83686000 bytes/sec)
209+1 records in
209+1 records out
107317 bytes transferred in 0.002 secs (53658500 bytes/sec)
15+1 records in
15+1 records out
7900 bytes transferred in 0.001 secs (7900000 bytes/sec)
mkdir: created directory '/su'
203+1 records in
203+1 records out
104384 bytes transferred in 0.002 secs (52192000 bytes/sec)
203+1 records in
203+1 records out
104384 bytes transferred in 0.001 secs (104384000 bytes/sec)
99+1 records in
99+1 records out
50720 bytes transferred in 0.001 secs (50720000 bytes/sec)
565+1 records in
565+1 records out
289432 bytes transferred in 0.003 secs (96477333 bytes/sec)
99+1 records in
99+1 records out
50904 bytes transferred in 0.001 secs (50904000 bytes/sec)
43+1 records in
43+1 records out
22456 bytes transferred in 0.001 secs (22456000 bytes/sec)
653+1 records in
653+1 records out
334744 bytes transferred in 0.003 secs (111581333 bytes/sec)
209+1 records in
209+1 records out
107317 bytes transferred in 0.001 secs (107317000 bytes/sec)
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: set fc_digest(/su/app_process)
SELinux: set fc_digest(/su/daemonsu)
SELinux: set fc_digest(/su/libsupol.so)
SELinux: set fc_digest(/su/su)
SELinux: set fc_digest(/su/sukernel)
SELinux: set fc_digest(/su/supolicy)
SELinux: set fc_digest(/su/sush)
() start
usage: setprop NAME VALUE

Sets an Android system property.

setprop: Need 2 arguments
() /su not mounted yet
() copying boot image backups from /cache to /data
() /data/su.img found
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: 369/6144 files (0.3% non-contiguous), 1943/24576 blocks
ext2fs_close2 : normal operation, return 0
() /data/su.img: 100663296 bytes
() /cache/su.img found
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/cache/su.img: 369/6144 files (0.3% non-contiguous), 1943/24576 blocks
ext2fs_close2 : normal operation, return 0
() /data/su.img found
() attempting merge
() loopsetup(/data/su.img): /dev/block/loop0
() /dev/block/loop0 /data/su.img
() loopsetup(/cache/su.img): /dev/block/loop1
() /dev/block/loop1 /cache/su.img
() merge complete
losetup: /dev/block/loop0: No such device or address
losetup: /dev/block/loop1: No such device or address
() loopsetup(/data/su.img): /dev/block/loop0
() exec daemonsu

It seems working! Sad that after a reboot root disappear. Thank you for your great work!

One question: why when I try to save build.prop that I have just modified, the phone reboot suddenly and after reboot the modifications does not saved?

So am I the only idiot here who see's absolutely no instructions anywhere at all?
I keep seeing people say, I did step "X" and blah blah blah...
I see all sorts of info and the links but one would think that in a thread about how to go about rooting your note 7, the instructions would be front and center?

Anyone?

The first post

** Nvm, I got it to work. Thank you!
Wondering if theres any updates on permanent root?

UPDATE ON PERMANENT ROOT
So I know how to root the note 7 permanently, in theory. For me to test my theory i need someone to take the stock system.img.ext4 out of my firmware package, unpack it, place a since binary in the /system/xbin folder and repack it. If you can make it, i can flash it.

I can to try it if you give me exactly what I need to do

OnThe7thDayBOOM wrote: Thu Oct 19, 2017 1:29 pm UPDATE ON PERMANENT ROOT
So I know how to root the note 7 permanently, in theory. For me to test my theory i need someone to take the stock system.img.ext4 out of my firmware package, unpack it, place a since binary in the /system/xbin folder and repack it. If you can make it, i can flash it.

I could help too, dm me

Thanks for this. I was able to follow everything and received temp root. Only part that didn't work for me was "sh /data/local/tmp/su/no_updates.sh" I didn't see that file in the folder.

Any update on a permanent root? I have the n930w8 which still charges to 100 percent. Will help any way possible

yusuflulat wrote: Fri Nov 17, 2017 1:20 am Any update on a permanent root? I have the n930w8 which still charges to 100 percent. Will help any way possible

Very close, there has been some breakthroughs, which are now being tested. We will let everyone know once it is ready