yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] noolis:
ok,booted with r181 eng download the app and it's rooted!!

Also restore my apps through titanium.

But now i see that there is 182

there is something new?

Nexus 5x,android N clean install,recovery twrp 3(but nothing works there because of encryption)
[Android Software/Hacking General [Developers Only]] phhusson:
Oh ****. You're right/I was right before.

nocrypt does noverity, not noverity doesn't do nocrypt.

Sorry for the confusion.

r181 => r182 is unrelated. It adds new angler M build.
[Android Software/Hacking General [Developers Only]] cjkacz:
Are you able to install busybox? It will not install to system on the no encrypt version
[Android Software/Hacking General [Developers Only]] Tung_meister:
My tablet is just restoring. I'll try shortly.

Edit: No busybox won't install.
[Android Software/Hacking General [Developers Only]] elreydenj:
Thank you. Does the user version also support noencrypt and noverity?
[Android Software/Hacking General [Developers Only]] Droidphilev:
Now i'm lost too. :(

before i tried on an unencrypted system boot-shamu-NPC56P-su-noverity-r181.img and became encrypted. Started all over (decrypted again) and tried again using boot-shamu-NPC56P-su-noverity-r182.img and stayed unencrypted.

So to be sure, if i want:

-stay unencrypted

and

-r/w to system

i need to use boot-shamu-NPC56P-su-nocrypt-r182.img?

Thanks for all this!!! Very nice to play with really!
[Android Software/Hacking General [Developers Only]] jfpbookworm:
Android N on Nexus 6 with boot-shamu-NPC56P-su-noverity-r182.img. Root works but noverity doesn't seem to be working (i.e., I can't modify the system partition).
[Android Software/Hacking General [Developers Only]] Droidphilev:
Trying boot-shamu-NPC56P-su-nocrypt-r183.img now. whatever i do: it hangs at bootanimation. Of course on a clean system. Flashed system.img and afterwards the kernel both using fastboot.
[Android Software/Hacking General [Developers Only]] Franzie3:
Thanks [MENTION=1915408]phhusson[/MENTION] All set up and rooted on the N-preview for my N6P. No issues so far. Was hoping to get systemless root working but that would only be for AndroidPay but that isnt even supported on the N-build as of now. oddly enough they included it, but they mention it isnt ready for N-preview yet when trying to open it.
[Android Software/Hacking General [Developers Only]] phhusson:
This root has always been system-less. Though I won't help people circumvent SafetyNet.
[Android Software/Hacking General [Developers Only]] Lrs121:
[MENTION=1915408]phhusson[/MENTION] nVidia has finally posted the latest stock android 6.0 images for the Shield Tablet (version 4.0.1) and Shield Tablet K1 (version 1.1.1)
[Android Software/Hacking General [Developers Only]] rant:
Good to see some success with the N6P. What boot img file did you use? I continue running into the "Decrypt Data" prompt in TWRP using both nocrypt and noverity versions. Wiping data will resolve, but it reappears once I boot into the system, so something is overwriting or reverting, but I'm likely missing a step.
[Android Software/Hacking General [Developers Only]] elreydenj:
Same here. Cant decrypt data for the life of me. using the nodecrypt version and i format data afterwards.....
[Android Software/Hacking General [Developers Only]] bgboii:
I think the problem is that the link in OP for nexus devices just takes you to a different nexus device and not where the list of all them are at so that you can choose the correct build number that matches to your device. I did that yesterday and couldn't get this to work because I was using a different build number for another device.
[Android Software/Hacking General [Developers Only]] Droidphilev:
ok... don't kill me for this as this way of rooting is new to me.

Since my nexus 6 fails to boot i started to read everything again.

If i was decrypted before there is no need to format userdata after flashing the noencrypt version, correct? or is a format always needed regardless if the device was decrypted or not before trying this?
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
https://plus.google.com/u/0/+shofiqulanwar/posts/gqAMQ3yZW1o

There's a test version of TWRP in the comments there that *might* help.
[Android Software/Hacking General [Developers Only]] elreydenj:
Your nocrypt version of angler for Android N does not decrypt your phone even after formatting userdata. Is there another version of your root zips that will decrypt, run permissive, and disable verity for the N6P? There is a no encrypt boot img in the general N6P thread that does in fact disable force encryption as I have tried it. However I am interested in gaining root through your methods and remaining decrypted. Any guidance is greatly appreciated.
[Android Software/Hacking General [Developers Only]] phhusson:
Ok I worked on volantis and I assumed it would be the same everywhere. I've checked fstab, and indeed there is a problem.

I'll fix it soon.
[Android Software/Hacking General [Developers Only]] elreydenj:
Thank you sir for the quick response! Looking forward to it.
[Android Software/Hacking General [Developers Only]] Droidphilev:
I think this counts for shamu too. I tried again and waited much longer. It indeed booted but was encrypted again (using the noencrypt kernel) that's why bootanimation was shown a lot longer.
[Android Software/Hacking General [Developers Only]] phhusson:
Should be fixed. I checked shamu and angler's fstab, they seem ok.

Added, thanks.
[Android Software/Hacking General [Developers Only]] hungmung:
Ok the noverity for angler on N allows root but I can't apply adaway so I'm assuming it isn't letting writes to system
[Android Software/Hacking General [Developers Only]] MrBrady:
Flashed the 3/10 nocrypt boot image on my Nexus 6 (Shamu) and am unable to get LTE on Verizon. Rebooting and toggling Airplane Mode don't help the situation.

Android N preview on Shamu.
[Android Software/Hacking General [Developers Only]] Droidphilev:
This time it booted and didnt get encrypted using boot-shamu-NPC56P-su-nocrypt-r185.img. Thanks!

Still if i understood correctly this version of the kernel should allow system r/w but that seems not to be working. Just FYI :)
[Android Software/Hacking General [Developers Only]] phhusson:
I have no Nexus with me ATM, and fstab looks good...

Can you get paste me the content of /proc/mounts ?

And what does the shell say when you try to run mount -o remount,rw /system ?
[Android Software/Hacking General [Developers Only]] Droidphilev:
Please keep in mind this is "i don't know what i'm doing"

i found a file in my fileman in /proc called "mounts -> /proc/self/mounts". Opened it and all that is there is: rootfs / ro

If i type that command in terminal i get output: permission denied

Hope this helps
[Android Software/Hacking General [Developers Only]] buffal0b1ll:
Same here on Shamu. I used the noencypt version and had no booting issues and stayed decrypted. Root works for most apps but system file rename, delete, edit is a problem.

I'm scratching my head and remembering, with my limited understanding, the difference between Systemless SuperSU 2.61 and 2.62. 2.61 was the "pure" systemless that allowed Android Pay and 2.62 had the poor man's overlay that allowed lots of non functioning root apps to work. Forgive me if this is common understood already, just trying to offer ideas;)

From http://xdaforums.com/showpost.php?p=64161125&postcount=3

"A poor man's overlay is used on /system/xbin. We are creating a copy of /system/xbin in /su/xbin_bind, adding a symlink to /su/bin/su there, then mounting the entire thing on top of the original /system/xbin. This is likely to fix some compatibility issues with some apps, without actually modifying /system. Removing /su/xbin_bind and rebooting will disable this feature, or "echo BINDSYSTEMXBIN=false>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash.

If you have one of those devices that refuse to remount system r/w in Android such as the Nexus 6P, but you do want to do this, "echo FSTABSYSTEMRW=true>>/data/.supersu" in recovery root shell before a SuperSU ZIP flash will patch the boot image in such a way that remounting will work. This feature itself breaks OTA compatibility, regardless of if you end up writing to /system or not."

BTW I got around the Adaway problem in particular by copying a hosts file from another device and pasting/644 it using TWRP. Ads are gone!
[Android Software/Hacking General [Developers Only]] mangomonkey00:
there is no boot.img for volantisg
[Android Software/Hacking General [Developers Only]] buffal0b1ll:
Thank you so much. I'm also on Nexus 6 with nocrypt R181 version experiencing rw system problems.

Attached are a few screenshots with the mount attempt in Terminal Emulator and the proc/mounts

proc/mounts looks to be a 0b file that symlinks to a file with these contents:

rootfs / rootfs ro,seclabel,relatime 0 0

tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1505060k,nr_inodes=171679,mode=755 0 0

devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

none /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0

adb /dev/usb-ffs/adb functionfs rw,relatime 0 0

proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0

sysfs /sys sysfs rw,seclabel,relatime 0 0

selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0

debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0

pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

tmpfs /mnt tmpfs rw,seclabel,relatime,size=1505060k,nr_inodes=171679,mode=755,gid=1000 0 0

/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0

/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0

/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0

/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0

/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0

/dev/block/platform/msm_sdcc.1/by-name/oem /oem ext4 ro,context=u:object_r:oemfs:s0,nosuid,nodev,relatime,data=ordered 0 0

/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0

tmpfs /storage tmpfs rw,seclabel,relatime,size=1505060k,nr_inodes=171679,mode=755,gid=1000 0 0

/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

tmpfs /storage/self tmpfs rw,seclabel,relatime,size=1505060k,nr_inodes=171679,mode=755,gid=1000 0 0
[Android Software/Hacking General [Developers Only]] phhusson:
The system/xbin trick is mostly never needed, only some old crappy apps need it. It is useful only if the ROM already has another system/xbin/su.

I have partial system/xbin trick: I only override system/xbin/su if it exists, I don't create it if it doesn't exist.

Can you test with: http://phhusson.free.fr/temp/boot-shamu-NPC56P-su-nocrypt-r185.img
[Android Software/Hacking General [Developers Only]] buffal0b1ll:
185 allowed me to rename etc/hosts.bak to etc/hosts1.bak ! YAY.

Disabling and Applying hosts file in Adaway working too.
[Android Software/Hacking General [Developers Only]] phhusson:
Thanks
[Android Software/Hacking General [Developers Only]] buffal0b1ll:
THANK YOU!

---------- Post added at 04:57 PM ---------- Previous post was at 04:44 PM ----------

Should I flash 186? I see it's up now.
[Android Software/Hacking General [Developers Only]] phhusson:
It's just that I pushed the change in temporary gave you to all devices. It shouldn't change anything for you.
[Android Software/Hacking General [Developers Only]] Tung_meister:
186 isn't booting on my volantis.
[Android Software/Hacking General [Developers Only]] phhusson:
Sniff :(

Which variant?
[Android Software/Hacking General [Developers Only]] Tung_meister:
nocrypt.
[Android Software/Hacking General [Developers Only]] hungmung:
Ok i tried both the 186 nocrypt and the noverity on the angler on N. The nocrypt just sits at the boot screen and loops. The noverity will boot but doesnt allow system r/w
[Android Software/Hacking General [Developers Only]] bgboii:
I keep getting an error when flashing SuperSU.zip
[Android Software/Hacking General [Developers Only]] nicholseric:
I clean flashed my Shamu with NPC56P, even formatted userdata. The first thing I did was lowered the Font size and Display size. That wasnt enough for me (I have 20/10 vision) so I tried the setprop persist.sys.lcd_density 360 from terminal emulator. That failed to do anything. Have I mentioned that I really like the tablet layout for Chrome and Gmail? Then I tried cat'ing it to /data/property and had no wrire access. So again from an adb shell. Still no write access. So on to rooting this damn thing. Why cant google please me?

Before I could find this post, I tried the superuser.zip. Not surprising, it failed to flash from TWRP. Then I tried boot-shamu-NPC56P-su-usr-r186.img. I was stock encrypted and I only got as far as boot loob back to twrp 3.0.1. Then I flashed boot-shamu-NPC56P-su-eng-r186.img and flashed the original recovery. This got me booted with and su.

So I created /data/property/persist.sys.lcd_density:360 and that did not noticeably increase my dpi. Same layout in Gmail and Chrome. I went all the way down to 280. Nothing.

I also downloaded this hosts and put it in /data/data/hosts then su --bind /data/data/hosts:/system/etc/hosts . This was gone after a reboot. I was expecting it to persist. Even while it was live, I dont think it was preventing adds.

Any tips?
[Android Software/Hacking General [Developers Only]] gizmosears:
On nexus 6 here. All boot images work except nocrypt, will not boot. Can not install binaries. Great work so far for such an early release. Thank you for your work
[Android Software/Hacking General [Developers Only]] Droidphilev:
Hi

boot-shamu-NPC56P-su-nocrypt-r186.img is working now. no encryption and r/w to system is possible. Thanks [MENTION=1915408]phhusson[/MENTION]!
[Android Software/Hacking General [Developers Only]] phhusson:
There are securities on su --bind: the owner of the file must be the caller of su --bind, and must NOT be root

As adb shell, put the file to /data/local/tmp/ and still as adb shell user, do the su --bind

Also, noverity indeed didn't have the "rw" flag in fstab, only nocrypt had it. I'm currently rebuilding with this change so noverity can also write to /system.
[Android Software/Hacking General [Developers Only]] beren:
flashed boot-angler-NPC56P-su-nocrypt-r187.img but my 6p doesn't boot, it stays loading android forever...

N preview + twrp 3.0.0.1 + unencrypted

tried wiping caches but didn't help, solved reflashing previous unencrypted-boot.

any idea?
[Android Software/Hacking General [Developers Only]] ridobe:
I'm with you. I can't get noencrypt to boot. I tried Tigerstown image and it boots right up but I can't apply su binaries.
[Android Software/Hacking General [Developers Only]] adrman:
[MENTION=1915408]phhusson[/MENTION] Just tried to update to the latest boot-angler-MHC19I-su-noverity-r187.img and it doesn't boot. The device never makes it to the point of asking for my decryption pin. All is well after rolling back to r182.
[Android Software/Hacking General [Developers Only]] hungmung:
Same here on angler, the 187 noverity may hangs on boot.
[Android Software/Hacking General [Developers Only]] nicholseric:
Great, appears to be working. Now if that hosts list were more accurate.

Ive been poking here and there and dont see where google is storing the Display:Small Font:Small settings. Im hoping there is a Tiny setting.

As always, to you, doitright and the rest of the team, thanks for the help and such a great contribution to the android ecosystem!
[Android Software/Hacking General [Developers Only]] MrBrady:
Settings / Accessibility
[Android Software/Hacking General [Developers Only]] phhusson:
It is in android.provider.Settings:

https://developer.android.com/reference/android/provider/Settings.System.html#FONT_SCALE

So you should be able to call:

settings put system font_scale 0.5
[Android Software/Hacking General [Developers Only]] yanleites:
Nexus 5X Android N - root works great !!!

I got root, but not to system, Greenify and AdAway don't work...

Any ideas ?
[Android Software/Hacking General [Developers Only]] Lrs121:
Look back a little ways and you'll see you need the noverity version to have system access.
[Android Software/Hacking General [Developers Only]] yanleites:
I know, but everyone got bootloop with this version...

Tried now - really bootloop :)
[Android Software/Hacking General [Developers Only]] phhusson:
Right, there seems to be something in 5X/6P that actually prevents from mounting /system rw, even if it is declared so in fstab.

I'll revert that change then. But I don't know how to have /system read-write.
[Android Software/Hacking General [Developers Only]] yanleites:
May be it's because we are "encrypted" ?
[Android Software/Hacking General [Developers Only]] gammaxgoblin:
ended up int his forum via a link.....so ive briefly scanned this post but.....can you say if root access is working on Shamu, N preview....is it working to the point of using layers manager? thanks!
[Android Software/Hacking General [Developers Only]] adrman:
Latest boot-angler-MHC19I-su-noverity-r189.img is working properly. No hang on boot and I'm able to mount system r/w from FX File Manager. Also, even on r182, I was having a problem with any app that attempted to call a reboot, even terminal. Superuser access was granted, but the reboot didn't occur. I wasn't sure if this was due to the updated Superuser or MHC19I. However, this problem has now been eliminated as well. Thanks for your work phhusson. :good:
[Android Software/Hacking General [Developers Only]] hungmung:
Tried the 189 noverity on angler n build still no luck can't apply adaway and can't write to system
[Android Software/Hacking General [Developers Only]] abnormalreply:
Can't flash the binaries with any of the shamu boot images on the N preview. It just fails with "ERROR: 1"

See pic.
[Android Software/Hacking General [Developers Only]] jr313:
Layers manager is not working at all. It will ask for root access but after that it doesn't even load up. I have root and busybox but it's a no go
[Android Software/Hacking General [Developers Only]] adrman:
Thankfully, layers and busybox are working perfectly on the latest M. That's the reason I'm using the noverity image. I'm not sure if it will with with N, but if you look back on page 21 (I think) of this thread, there are instructions on setting up a bind mount for adaway from adb shell. Even though it doesn't matter for me at this point, I'm still running adaway in this fashion, as I had it set up that way from when I was running the eng image.
[Android Software/Hacking General [Developers Only]] Lrs121:
I've had no luck getting the bind to work with adaway on my Nexus 6 even before I jumped to the N preview
[Android Software/Hacking General [Developers Only]] adrman:
Try the instructions in this post.

I used the newest adaway available here on xda though.
[Android Software/Hacking General [Developers Only]] contesauce:
I'm using adaway from fdroid repo with 189 no verity on shamu N preview and have r/wr
[Android Software/Hacking General [Developers Only]] pacman photog:
how can i get adb to recognize device after flashing this N?

5x ota,
[Android Software/Hacking General [Developers Only]] phhusson:
My first investigation:

1. It's not su related: same as adb shell which has proper groups

2. ping works in both su and shell, pings resolves only in shell (I'll fix this part Edit: fixed)

3. It's not iptables related, I cleaned everything and it's still not working

4. The error is "connection refused" when opening the connection, looks like a firewall

5. ping uses a dnsproxyd_socket
[Android Software/Hacking General [Developers Only]] phhusson:
For the /system/etc/hosts usecase, I've done a --copy option to sepolicy-inject to copy a context into another, so that /system/etc/hosts can run in its own context without breaking everything.

But then I realized I can't change /system so I can't change the context of the files in it /o\

I guess I'll have to make a white list, and do a su --bind /src/ /dst/ command...
[Android Software/Hacking General [Developers Only]] phhusson:
I added an update.zip which should be able to root any ROM on supported devices.

It has been really lightly tested (HTC A9 and N5), use it with caution.
[Android Software/Hacking General [Developers Only]] nicholseric:
Just flashed it on Pure Nexus ROM 20151113. No more chainfire su, It worked! After installing your apk, terminal emulater was able to su and nslookup works.

Does the update.zip parse and insert init.rc or replace it? Never mind, I see it...

sed -i '/on init/a \ chmod 0755 /sbin' init.rc

echo -e 'service su /sbin/su --daemon\n\tclass main\n\tseclabel u:r:su_daemon:s0\n' >> init.rc

addFile init.rc
[Android Software/Hacking General [Developers Only]] Lennoard:
Cool bro thanks
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
[MENTION=1915408]phhusson[/MENTION]

Your superuser update zip also worked on my M8 Google Play Edition. So that's at least 2 of my Marshmallow devices confirmed working :).
[Android Software/Hacking General [Developers Only]] phhusson:
Thanks [MENTION=1162986]Captain_Throwback[/MENTION] for the feedback

Also succesfully tested on CM12.1 for GT-N7100
[Android Software/Hacking General [Developers Only]] toonlight:
Has anyone tried installing Xposed (v78) while rooted with phhusson's root?

Edit: I've installed it on my Nexus 5 running stock 6.0 (MRA58N) and it's working fine so far (only tried using XPrivacy so far).
[Android Software/Hacking General [Developers Only]] Captain_Throwback:
I just tried flashing the superuser zip on my 5.1 Google Play Edition M8, and got an error during the install. Link to recovery log is below. Any idea what went wrong?

https://www.dropbox.com/s/hulvjjuxyzz3du8/recovery.log?dl=0
[Android Software/Hacking General [Developers Only]] craigacgomez:
[MENTION=1915408]phhusson[/MENTION] I've started working on a updating the Superuser app UI to Material Design. It's still in the early stages (but looks better already [emoji14]) and there's a lot more that can be done, but here's what my first stab looks like (first 1 hour of work). I will be pushing all my changes to my GitHub (https://github.com/craigacgomez/Widgets & https://github.com/craigacgomez/Superuser) and sending you pull requests as and when things get updated to usable states.

I've sent you two pull requests which update the UI to basic Material design (screenshots below)