yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] kavey:
Once the tablet has passed the erase cycle you need to fastboot boot the image again to continue full boot with root.

The problem I am having is I can get the tablet rooted/booting fine, but for some reason entering security settings (to all installation of apks from unknown sources) causes a force close and clearing settings data causes a soft reboot.

Hence despite being rooted, I can't install FDroid or apps from Amazon etc. Has anyone else come across this?
[Pixel C Android Development] dkryder:
there does not seem to be a point after the erase cycle that will allow another boot boot.img.

when the erase cycle completes the device goes to booting in 30 sec screen and it is unable to connect to allow fastboot commands before it boots to clean install.

but thanks for the reply i would certainly appreciate being able to boot to a rooted system to test it.
[Pixel C Android Development] kavey:
When you get the 30 sec warning screen, don't let it boot, just force restart the device by holding volumedown+power and then enter fastboot from the bootloader, then fastboot boot the image again. If you don't interrupt it, it will do as you are experiencing and do a full clean boot without the modified boot.img
[Pixel C Android Development] dkryder:
ok. thanks for the reply. i want to get on the "same page" as much as possible, so

what boot image are you using? [there are 8 different choices] are you using one of the "142" or one of the "144" builds and which specific flavor [eng/nocrypt/noverity/user]?

did you flash one of the modified vendor images?
[Pixel C Android Development] kavey:
I used the boot image linked in post 50 and no I didn't flash any vendor image. This has given me root as I say, though with the annoying force close on Security settings meaning I can't install apps from unknown sources

I haven't tested all of them yet (no rush, just tinkering with it until a proper root solution) so there may be a better image from the test set that doesn't have the settings force close
[Pixel C Android Development] brando56894:
Yep same security crash for me. I just had an odd problem: I had the no-force-encrypt boot image flashed and booted it with the rooted boot image, and then left it to charge overnight. When I woke up in the morning it was beeping at me and stuck in the "reboot to recovery" bootloop. :eek: Flashing the no-force-encrypt boot image didn't allow it to boot but booting using the rooted boot image worked fine.
[Pixel C Android Development] dkryder:
ok. yeah, forgot about that one. so, 11 boot images. the tmp boot is no longer reachable for me. i can get the new-boot.img to boot using your technique, thank you for that. and i also get the force close [stopped running] on the security setting. my issue currently is that this instance is not properly set up. if i use the app "root checker" it is reported that superuser app is installed but the binary files are not properly configured. i tried phh.superuser, it will install but will not update/configure. chainfire supersu is basically the same, will install, will not update.

system/bin/su, system/xbin/su does not exist

so how did you manage to get a supersu or superuser configured properly?

edit: i flashed vendor from superchilpil and that eliminated the security setting crash. still need to find way to configure a super user.
[Pixel C Android Development] kavey:
Sounds like you just need to install a set of busybox root tools - there are still several on the play store - search for busybox
[Pixel C Android Development] dkryder:
busybox claims it is not rooted properly, i tend to agree. can not open shell with root access. my guess is this image is not rooted properly.

edit: my last run through of the process appears to have established a rooted session. thanks to all for the help. i'm gonna check out a few of the apps i use that require root

and see how they respond to what i have here. i used a "boot new-boot.img" and i also flashed superchilpil's vendor to get rid of the security setting problem, followed up by

install of superuser by phhusson through the play store.
[Pixel C Android Development] phhusson:
That problem is caused by the "uncrypt" variant. This part of Settings app has a bug, if encryption is disabled it crashes.

All the other variants (I suggest eng or noverity), does have encryption enabled, but due to a bug in hardware encryption on ryu, it must be forced to software, else Android won't boot.

So to fix your problem, you must use eng image, AND you need to flash the customized vendor partition.
[Pixel C Android Development] dkryder:
phhusson,

i assume the new-boot.img is an "eng" image. i say this since it seems to be running well. i can report that tittanium backup so far has run well. another app i use on several devices is 3c toolbox. there seems to be much discussion in your other thread around this app so not sure if you want discussion here or there but the time i have used it has presented no big issues. 3c needs to install a helper app in /system to provide certain statistics, battery mostly. and during this process needs to reboot. i notice/use that a few others that need to do this, i have not got around to installing those yet. interesting thing is this time i did a "hot" boot to see if this would statisfy the need and after the "hot" boot the stats were being reported. i just wanted to avoid having to boot to bootloader and then boot boot.img again. in your opinion would it be best to fully reload the image if an app asks for a reboot? is it possible to create a script in android that would be similar to a windows batch file so that i could select it from the home screen and this script would boot to bootloader and then do a "boot new-boot.img" ? essentially booting the image by script file on home screen?

1/4/16 1:30 am [mountain..u.s.a.] edit: a few observations since obtaining root a while back.

1.] for me, a good boot process, the period of time between entering command "fastboot boot new-boot.img" and display of home screen is 34 seconds. anything longer indicated to me a problem with the boot which shows as a loop of the boot animation.

2.] seems to go without saying, but for me, any modification of the /system partition during a session would result in a boot animation loop during next boot attempt which would require getting to fastboot mode [boot to bootloader] and then flashing the system partition and once again "fastboot boot new-boot.img" which would restore again the system ,less any modifications that had been made prior. this is why i mentioned a "hot" boot seemingly being successful as a reboot should any app require one. doing a full reboot will most likely cause a boot animation loop and thus a restore of the /system partition.

i'm open to ideas or suggestions if i'm getting it wrong here.

all in all i'm happy with what has been given here as long as it is managed ok it is certainly better than no root.
[Pixel C Android Development] superchilpil:
So Phhusson,

Could you send me the two libs you removed from the vendor? I cant seem to extract them and i might need them for a little experiment im doing.
[Pixel C Android Development] kavey:
Thanks for the great explanation. I flashed the vendor image and everything is working now. Have restored apps using titanium backup and helium both using root mode without problems

Many thanks
[Pixel C Android Development] phhusson:
Uh? You can just adb pull /vendor/lib64/hw/keystore.xxx.so
[Pixel C Android Development] doumer:
Thanks a lot for your work, phhusson! Can't wait to boot up my new Pixel C!

Just to be sure: If I want root with encryption enabled I have to flash the modified vendor partition you linked in your first post and then boot via fastboot (and don't flash) the boot img (noverity), corect? And at every reboot I need to boot via fastboot, right? What happens if the device got stuck and reboots on it's own?

And in case of a system update manually flashing all images (like Heisenberg described here at no 10: http://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) should work, right?

Thanks a lot for your help!

EDIT: just couldn't wait and tried it already. the linked vendor image can't be flashed (fastboot crashes) but the one from superchilpil works – after doing a factory reset (this won't be needed every time i have to boot via fastboot, right?) booting with the r144 noverity gives me root, wohoo!
[Pixel C Android Development] ]grimm[:
To follow up on this, it seems that if you can't pass dm-verity verification, you'll have to boot with the "noverity" variant. I made some changes to the system partition and when I booted with the "eng" boot image, it took me to a screen that indicated that the OS didn't pass a consistency check and it prompted me with a recovery-style menu that allowed me to reboot or wipe. This is after flashing the customized vendor partition. Perhaps this is the coreboot equivalent of the "yellow, orange, red" warnings on Nexus devices?
[Pixel C Android Development] doumer:
Two more questions:

1. on each reboot (with the noverity img) a popup says that there is a problem with my device – i guess because of the modified vendor image – is this normal?

2. what to do on a system update? on my nexus 6p I just would flash all images from the factory image, reflash twrp and supersu but since we need a modified vendor image on the pixel c, does this image also have to be modified for each system update and will be a factory reset needed on every update (this one from the screen where you have to enter 0000000)?

Thanks a lot !
[Pixel C Android Development] SDT:
Did anyone try CF's systemless root here? Or does it just not work because of completely different img / partition / whatever design?
[Pixel C Android Development] doumer:
how? there is no custom recovery available yet :(
[Pixel C Android Development] superchilpil:
It's the same concept as this method.
[Pixel C Android Development] brando56894:
We now have TWRP!! http://xdaforums.com/pixel-c/orig-development/unofficial-twrp-2-8-7-0-pixel-c-dragon-t3288243
[Pixel C Android Development] phhusson:
This confirms that just signing the boot.img workarounds bootloader's stupid bug

Thanks for info. I'll work on that.
[Pixel C Android Development] ]grimm[:
I tried booting with the r147 noverity image and while I'm able to boot successfully with a modified system partition, I did not have root and was prompted by the superuser application that the su binary was out of date and needed to be updated. I did not have su access from a shell when testing to verify.
[Pixel C Android Development] phhusson:
Can someone test http://phhusson.free.fr/boot-ryu-test.img ?

I mean fastboot flash, not fastboot boot
[Pixel C Android Development] streilu:
Tried boot-ryu-test.img, booted up fine but SuperSU said the binary is outdated and the update failed.

Edit: Sorry, reading the first post helped! Root access is working with your superuser app!
[Pixel C Android Development] phhusson:
Sorry, bad connection ate up my message.

You fastboot flash-ed it? What I want to test is fastboot flash
[Pixel C Android Development] streilu:
Yes I flashed it!

Gesendet von meinem SM-G925F mit Tapatalk
[Pixel C Android Development] doumer:
is this a noverity version to be used with a modified vendor img and encryption enabled?
[Pixel C Android Development] phhusson:
Good, thanks!

It is an eng noverity crypt

But it should work even with unmodified vendor.img now.

Please confirm.
[Pixel C Android Development] doumer:
great, gonna flash the default vendor.img and your new boot as soon as I'm back home.
[Pixel C Android Development] streilu:
Yes it works with unmodified vendor.

Gesendet von meinem SM-G925F mit Tapatalk
[Pixel C Android Development] phhusson:
Perfect, thanks!

I now have to do a real release.

Edit: release made
[Pixel C Android Development] dkryder:
is the 147-nocrypt version best to flash with system that has been from booting the new-boot.img. i think that was nocrypt also?
[Pixel C Android Development] phhusson:
If it was nocrypt, yes use 149-nocrypt.

To be sure, boot it one last time, go in Settings => Security. If it crashes it's nocrypt. Else it's noverity.

Please note that now standard boot-su-eng.img should work, and it won't disable encryption nor verity.

Also, can someone test http://superuser.phh.me/superuser.zip ?

By default its configuration is eng crypt verity, but you can edit config.txt in the zip to change, for instance to eng nocrypt noverity
[Pixel C Android Development] ]grimm[:
This should be tested after flashing the Google provided boot.img and vendor.img, correct?
[Pixel C Android Development] dkryder:
i flashed the boot-ryu-test image with standard vendor and for some reason when i boot to the twrp recovery the sdcard will not mount so i messed up something

edit: i checked on twrp thread and there is an issue with twrp not decrypting data, that was most likely what caused not being able to mount data.

i am currently using the boot-ryu-test image so i need to try the nocrypt one later. i tried it just now and just booted to recovery so i guess it will need a reset. will do that later.

edit 2: boot-ryu-test and standard vendor is best combo for me. can't figure why twrp has issue with encrypt data since all nexus are same on that. why is su in /sbin and not /system/bin or /system/xbin, /system/sbin?
[Pixel C Android Development] phhusson:
Yes
[Pixel C Android Development] ]grimm[:
I flashed the orig-boot.img, then loaded TWRP and sideloaded the latest superuser.zip after changing the config.txt file to

eng noverity crypt

and it rebooted into recovery instead of booting properly.
[Pixel C Android Development] phhusson:
Erf :/

Thanks
[Pixel C Android Development] Avalun:
i got the no command error after flashing boot-ryu-test.img I hope I can fix that.
[Pixel C Android Development] doumer:
hi quick update: after flashing the new boot-img and the default vendor image I ended in a bootloop but after erasing cache, flashing default cache, modified boot, default system and default vendor again it booted normaly.

Got an meesage after boot that my su binarys are outdated but your su works nonetheless :)
[Pixel C Android Development] Avalun:
Thanks to your manual I could repair my tablet, unfortunately I don't have a TWRP nor SU yet. As I have visitors today, I have to check that tomorrow in detail.

So additional I installed that superuser app on the first Page it worked!

Thanks very much :D
[Pixel C Android Development] phhusson:
Can someone here help http://xdaforums.com/showpost.php?p=64751112&postcount=48 ?
[Pixel C Android Development] ]grimm[:
I just updated my Pixel C to MXB48T and tried applying superuser-r170 via twrp and was sent immediately to recovery when I rebooted the device.

I tested the boot image generated by the build bot for MXB48T and that works well.
[Pixel C Android Development] doumer:
did you flash the one without encryption or the noverity version and the modified vendor.img?

[MENTION=1915408]phhusson[/MENTION]: can we flash the modified vendor img for the noverity boot img on newer builds?

[MENTION=1915408]phhusson[/MENTION] just tried the noverity img for MXB48T and it works fine, thank you so much for keeping me rooted since twrp still can't handle encryption!
[Pixel C Android Development] doumer:
quick update: your modified boot noverity is also working with MXC14G with encryption enabled
[Pixel C Android Development] Grims:
Any chance this will work on N? I haven't had any luck with any of the others methods for rooting N.
[Pixel C Android Development] phhusson:
Sorry for the long time to answer.

Yes it works on N, you can use https://superuser.phh.me/nexus/ryu/NPC56P/
[Pixel C Android Development] drewski_1:
What's the difference between these and the ones from mid-month?

And thanks for Root on N for Pixel C! :good:
[Pixel C Android Development] ]grimm[:
I'm not sure if this is still useful information, but I tried sideloading superuser-r197.zip in TWRP again after having flashed M5C14J but the zip still cannot apply on the device. I get the following output:

Updater process ended with ERROR: 1
Failed to mount '/data' (Invalid argument)

Am I perhaps doing something incorrectly when trying to sideload superuser.zip?

If the zip cannot be applied on the device itself, is there a script that users can run on a non-Android device on to produce a rooted kernel image like you are producing and uploading on your server?
[Pixel C Android Development] drewski_1:
NPC91K-su-nocrypt-r201 is not working, for some reason.

after flashing in Fastboot, it reboots twice, the second time going into Recovery.

i went back to NPC56P which is working fine.
[Pixel C Android Development] phhusson:
They broke fastboot boot...

I'll see what I can do
[Pixel C Android Development] phhusson:
New r203 works, though it seems only noverity variant works
[Pixel C Android Development] minieod:
has anyone tested for npc91k?

whoopsn, nevermind, you were talking about it above
[Pixel C Android Development] drewski_1:
NPC91K-su-nocrypt-r203 is working! :good:

edit: having some random reboots . . .
[Pixel C Android Development] Mortron_xda:
All versions of r203 - if something call su, reboot in safe mode. "User" version - nothing when su called.
[Pixel C Android Development] minieod:
what was your flashing order? nocrypt just gives me loading screen loops and never goes to the OS

ill try a full wipe and all

edit: full wipe seemed to work, at least im into the system now, but setting up now so havent experienced a reboot
[Pixel C Android Development] drewski_1:
i didn't do a full wipe. flashed full ota, the boot.img, rebooted.

after any root access, the tablet would reboot into safemode. reverting to my N-preview1 backup didn't work, so currently back on MM while licking my wounds . . . :crying:
[Pixel C Android Development] minieod:
yup, just experienced my first su-reboot

i can go without root for now, so hopefully just run it with 203 for now til updated. at least the device is decrypted and twrp works and ready for upgrades to boot and recovery
[Pixel C Android Development] phhusson:
I noticed the reboots as well.

I switched back to stock/locked system, it still reboots, so it is this N preview which is unstable...
[Pixel C Android Development] minieod:
i had/have zero issues running either locked or decrypted system without root.

i have your nocrypt 203 kernel running perfectly, and have not had one reboot ---- until you try and call something for SU. which then puts the tablet into safe mode, and then have to reformat from there

i redid nocrypt 203 and put it on, never installed superuser.apk or anything that would invoke SU - and the system runs just fine...

awaiting future fixes to kernel to restore it. but works great for now
[Pixel C Android Development] drewski_1:
I'm jealous. I tried 203 with Preview 2 & no root and still getting rebooting :crying:
[Pixel C Android Development] minieod:
Well doesn't do so much for now, I just have the system decrypted which is nice for later
[Pixel C Android Development] Mortron_xda:
N-preview 2 and r205 - su -> reboot =(
[Pixel C Android Development] a63548:
Just flashed the factory May build, and used your boot-ryu-MXC89F-su-nocrypt-r205.img image. Worked flawlessly. Have root, and runs great!

Thank you so much phhusson :)
[Pixel C Android Development] minieod:
going to release for build 3? :)

i dont even care about root now, just want unencrypted everything
[Pixel C Android Development] drewski_1:
SuperSU 2.72 removes forced encryption and roots n preview
[Pixel C Android Development] Mortron_xda:
what about su-reboots? UPD it's ok with supersu 2.72
[Pixel C Android Development] doumer:
any change to get a noverity-img for MXC89H? or could the boot-ryu-MXC89F-su-noverity-r210.img	still be used for newer builds?
[Pixel C Android Development] ]grimm[:
I'm able to still boot MXC89H using the older boot image from MXC89F so this seems to be a temporary fix until the build bot produces new images or superuser.zip is modified to work directly on the platform.
[Pixel C Android Development] doumer:
thank you! gonna try that right away – hopefully there will be a TWRP version with support for enabled encryption at some point
[Pixel C Android Development] ]grimm[:
Has anyone been able to get superuser.zip to apply properly on the Pixel C? I've tried with several releases up to the most recent using the unofficial TWRP builds from XDA and have never been able to patch the kernel successfully using the zip.
[Pixel C Android Development] doumer:
damit, noverity-images no longer working with the november release :(
[Galaxy Note5 Q&A, Help & Troubleshooting] arthvpatel:
hey all

I just woke up and the note 5 from telus has this update

N920w8vluza0k5 , did a quick search on Google and did not find any results
[Galaxy Note5 Q&A, Help & Troubleshooting] arthvpatel:
just updated and it is still 6.1.1 : (
[Galaxy Note5 Q&A, Help & Troubleshooting] u2u:
This update adds gear vr support basically. Today is the release date of gear vr in Canada. Optimizes few other things....
[Galaxy Note5 Q&A, Help & Troubleshooting] jtOttawa:
Including - importantly - battery optimisation. You can selectively optimise individual apps' battery use under Smart Manager. Appears to improve battery life of the phone particularly when phone is sleeping. Also provides security updates to November 2015. Very pleased to get this.

---------- Post added at 08:29 AM ---------- Previous post was at 08:26 AM ----------

I think you mean 5.1.1 - right? ;)
[Xperia Z1 General] kos25k:
Hello andromaniacs!

As maybe this is the most important issue that concerns almost everyone..Please post the best combination included ANY rom (custom,stock) ANY kernel,ANY mod (v4,chocolatetrain etc) that gives you the best photo quality!
[Xperia Z1 General] zhuoyang:
Wrong section
[Xperia Z1 General] kos25k:
Why?i emphasize in photos quality related to rom and mods. Not general thread about picture quality,as there are 2 of them also.If anyone can suggest something different feel free to correct me :)

Στάλθηκε από το C6903 μου χρησιμοποιώντας Tapatalk
[Xperia Z1 General] tomascus:
Questions belong in the Q&A (Questions and Answers section :p)

Here's more information: http://xdaforums.com/showthread.php?t=2440619
[Xperia Z1 General] kos25k:
guys give a try at huawei emui v2 or v2.3 camera port!it the fastest camera i have tryied and the ONLY camera that there is not blur overxposed in night shots when there is a lamp near the phone! the taken picture is as it really appears!

Στάλθηκε από το SM-T310 μου χρησιμοποιώντας Tapatalk
[Wear OS Q&A, Help & Troubleshooting] bok11:
Hi,

I own a LG smart watch and an nexus 5X, but i don't feel like they are working 100% together. For instance, i set the language on my phone to my native language (danish) , yet the watch only takes commands in English. Also, if i talk to the watch, and decide to look on my phone, i see the phone also registered the "ok google" sentence, and is trying to understand me in danish. So what i get whenever i say "ok google" is a watch that listens for commands in English, and a phone that simultaneously wants to take commands in danish.

Is there any way to make them work more together on this?