yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
This month they are quite early ...

August 2016 -> MXC89L

system-vendor ...

Update.ZIP_PixelC_Ryu_MXC89L-system-vendor.zip

The new stock kernel ...

Update.ZIP_PixelC_Ryu_MXC89L-kernel_dragon.zip

Installation:

1. Reboot into TWRP

2. Install Update.ZIP_PixelC_Ryu_MXC89L-system-vendor.zip

3. Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89L_v160802_followmsi.zip or Update.ZIP_PixelC_Ryu_MXC89L-kernel_dragon.zip

4. Install UPDATE-SuperSU-v2.76-20160630161323.zip

5. Reboot into system

And a fresh stabilize-smaug-7897.B-chromeos-3.18 kernel !

Here are the latest changes from google ..

162fdfc Revert "HACK: memory: tegra: Do not go to 40.8 MHz EMC" by Danny Huang · 8 days ago stabilize-smaug-7897.B-chromeos-3.18

1b05ae7 CHROMIUM: clk: tegra: set sbus rate to minimum when no user enabled by Danny Huang · 8 days ago

1ede68c CHROMIUM: clk: tegra: keep sbus clock always on by Danny Huang · 8 days ago

eef3447 CHROMIUM: clk: tegra: set SCLK source to PLL_P by Danny Huang · 8 days ago

For both Android versions ..

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD90G_v160802_followmsi.zip

kernel-chromeos-3.18_v160802_NPD90G_boot.img

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_MXC89L_v160802_followmsi.zip

kernel-chromeos-3.18_v160802_MXC89L_boot.img

Kernel Installation:

1. Reboot into TWRP

2. Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NPD90G_v160802_followmsi.zip

3. Install UPDATE-SuperSU-v2.76-20160630161323.zip

4. Reboot into system

Due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy !
[Pixel C Android Development] nigelhealy:
On today's version all looking good!
[Pixel C Android Development] followmsi:
Android N Final has been released .. NRD90M !

As they are still no official factory images available I have used the sideload package from here: https://android.googleapis.com/pack.../2b0d80e539b415ed50f59d5aadc509a995f777d1.zip

EDIT: The factory image has been released as well .. https://dl.google.com/dl/android/aosp/ryu-nrd90m-factory-6aec2222.tgz

system-vendor:

Update.ZIP_PixelC_Ryu_NRD90M-system-vendor.zip

stock kernel:

Update.ZIP_PixelC_Ryu_NRD90M-kernel-dragon.zip

Pls find the new bootloader inside the download folder .. bootloader_NRD90M.img

Of course we have a new stabilize-smaug-7897.B-chromeos-3.18 kernel as well :)

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NRD90M_v160823_followmsi.zip

kernel-chromeos-3.18_v160823_NRD90M_boot.img

Installation:

1. Flash bootloader via fastboot (fastboot flash bootloader bootloader_NRD90M.img)

2. Reboot into TWRP

3. Install Update.ZIP_PixelC_Ryu_NRD90M-system-vendor.zip

4. Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NRD90M_v160823_followmsi.zip

5. Install UPDATE-SuperSU-v2.76-20160630161323.zip

6. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy the final version of Android N ..
[Pixel C Android Development] followmsi:
The new sources have been arrived as well .. https://android.googlesource.com/device/google/dragon/+/android-7.0.0_r1

Time for some testing ..

You should have a clean build tree before you start to change to Android N ..

repo init -u https://android.googlesource.com/platform/manifest -b android-7.0.0_r1
repo sync -n -j 4 && repo sync -l -j 12

You need to install openjdk-8 and there is one very annoying issue .. but I found the fix here:

https://stackoverflow.com/questions...ror-try-increasing-heap-size-with-java-option

export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4g"
./prebuilts/sdk/tools/jack-admin kill-server
./prebuilts/sdk/tools/jack-admin start-server

Having a clean build-tree and using the "Xmx4g" flag - it´s working.

[100% 47792/47792] host Executable: net_test_osi_32 (out/host/linux-x86/obj32/EXECUTABLES/net_test_osi_intermediates/net_test_osi32)

#### make completed successfully (01:20:42 (hh:mm:ss)) ####

The first Nougat AOSP version for Pixcel C :)

Update.ZIP_PixelC_Ryu_AOSP_7.0.0_r1_system.img_v160824.zip

It´s a system.img only - to be flashed via TWRP.

Another reason for testing .. to have a look into TWRP compilation on Nougat sources.

Building TWRP using Android 6 TWRP branch on Android 7 AOSP sources ;)

Made some quick tests only .. but the compilation fails.

Anyway .. currently there is no rush to get TWRP running on Android 7 sources.

At least from my experience it´s working fine with DP3, DP4, DP5 and the final N version now.

Happy compiling ...
[Pixel C Android Development] nigelhealy:
I did a TWRP full backup, then flashed in TWRP the system vendor kernel and was on Android N, I found 2 functions I need not working so tried to go back via TWRP restore but the Pixel C just didn't get past the Google logo. So be cautious about upgrading, you may have to do a clean install. Or have say the earlier vendor system kernel zip files. I had TWRP say no OS after a restore.

So what I did was install N again and then download the earlier zips to install.
[Pixel C Android Development] followmsi:
You updated to the final N version ?

After this you restored back to Android N DP5 ?

Did you restore all partitions or just data ?

Pls post recovery.log to have a better unterstanding of your problem.

Thx

EDIT: sorry, just saw you pic, you went back Android M ?

Did you flash your "old" bootloader as well?

You have used twrp version 3.0.2-21 ?

Recovery.log would help too.
[Pixel C Android Development] nigelhealy:
Yes on your TWRP 3.02.-21.

What I did to do the upgrade: download and install the vendor system kernel zips. That worked. So that's good an easy no-PC upgrade to N.

To roll back, what failed: TWRP backup of all partitions (before I did the upgrade), TWRP restore of all partitions, it would not boot past Google logo.

To roll back, what worked: install the prior vendor system kernel zips, TWRP restore just the data partition, then apply supersu, xposed, adaway.

I'm on the latest M version, waiting for better N support (xposed, and EDS which needs selinux permissive).
[Pixel C Android Development] followmsi:
You got the "no OS" message inside TWRP, after your full restore and before booting.

If you get this message you most likely will hang on bootlogo, like you did ;)

The recovery.log of your full restore process would be interessting.

Did you made a full restore without problems before ?

Anyway .. we need to test and reproduce your issue - this takes time.

There are some new TWRP commits on github, and I was planing to upgrade the underlying AOSP from r43 to r63 .. and using a new kernel too.

When the next TWRP version will be ready I will get in contact with you .. for full restore testing ;)

Cheers
[Pixel C Android Development] greco2003:
Quick question prolly not the right place for it but will ask if I install android N will I have to reinstall twrp and will the root method for Mm work? I want to upgrade but am holding off till there's a solid path for root. Thank you for all your support gotta love our devs for this device.
[Pixel C Android Development] xnaquada:
How to Root the Google Pixel C on Android N 7.0

Made a post here outlining how to root Android N for the PixelC as I wasnt sure if it was entirely in place in this thread.
[Pixel C Android Development] nigelhealy:
So I have been dirty flashing the MM builds for a while and your TWRP worked fine, so now I did a clean flash of N, and it all worked. Then I went to bootloader, fastboot flashed your TWRP I got the recovery bootloop problem. Typing the fastboot reboot doesn't make it work, it bootloops back to recovery. So then I tried going to stock recovery and then get into a "no command" problem.

I'm about to right back to a clean erase fastboot process and probably not fastboot flash your recovery but just fastboot boot your recovery so it isn't installed but is used to get supersu.zip installed.

Any ideas why I have these issues? workaround?
[Pixel C Android Development] followmsi:
Maybe a new TWRP version - based on Android 7 sources - will solve your issues on N.

Pls wait a few days for the TWRP N version.
[Pixel C Android Development] followmsi:
I did upgrade my current Installation to Android N, but still the same "old" and UNencrypted Data partition.

No problems using SuperSu on final Android N version.

2.78 was the first version coming thru playstore to my device, but no problems either.

Binary Update and reboot - fine now.

The way I did my Upgrades are described in this thread.
[Pixel C Android Development] nigelhealy:
That is probably the best idea, in general to wait for N support.

So I have tried a few combinations.

A clean N stock install, then your TWRP, it can't read encrypted data, and boot loops. So that needs to wait for a N version of twrp.

A clean install of M stock, then your TWRP works.

A dirty flash upgrade then to N works. So there is something different between a clean M then upgrade to N compared with a clean N.

So this thread is correct "in context" that those who had a working M, then your TWRP, works, and then using your upgrade ZIPs to N works.

Where the problems arise is in a different context, a clean N install.

Do you think separate threads would help others or you think overkill given the small community? This thread for M and M to N and a new thread for clean N?

I repeat a past point also, your TWRP fails to do a N back to M restore, the successful way is to TWRP backup data, go to N, to revert back just do data restore and flash the prior system vendor kernel zips, I.e. don't TWRP restore from backup the vendor system kernel.

I am now back on M as N doesn't do still some important things for me, despite daily improvements on updates and workarounds. e.g. BBC iPlayer doesn't download on N.

---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------

I found even you did M encryption then TWRP then upgrade to N then TWRP can decrypt, but a clean N the TWRP can't decrypt. That infers the encryption with N is different than with M.

I know because this worked: full wipe of everything, install stock M, it is encrypted, then fastboot flash this TWRP, it can decrypt data. Then a TWRP install of N kernel system vendor, and TWRP still can decrypt data and all works.

But this fails: full wipe, then instal stock N. If you try to fastboot flash this TWRP recovery then boot loops, if instead of fastboot flash you fastboot boot recovery then it can't decrypt data.

So 3 valid approaches: 1) begin with M then dirty flash to N. 2) clean N and just temporary TWRP via fastboot boot to then sideload to avoid needing /data. 3) wait for a new TWRP version.
[Pixel C Android Development] followmsi:
Thanks for your feedback.

Yes, as it looks like and as you describe, the clean install of Android N will behave different as the upgrade install, like I did.

We will see how the new TWRP Android 7 version will work on Android 6 .. maybe the TWRP Team made it compatible for both versions. :)

Cheers
[Pixel C Android Development] followmsi:
In your case - go for option 3 ;)

The decryption stuff for Pixel C is "handmade" - at this time for Android 6.

I hope the underlying TWRP general changes for 7 are sufficient to solve the clean install issue.

Maybe some additional libs are required on 7. ;(

We will see ..
[Pixel C Android Development] followmsi:
Another month .. another release -> NRD90R

system-vendor:

Update.ZIP_PixelC_Ryu_NRD90R-system-vendor.zip

stock kernel:

Update.ZIP_PixelC_Ryu_NRD90R-kernel-dragon.zip

Seems to be the same bootloader as used for the final version .. bootloader-dragon-google_smaug.7900.27.0.img

Of course we have a new stabilize-smaug-7897.B-chromeos-3.18 kernel as well :)

Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NRD90R_v160906_followmsi.zip

kernel-chromeos-3.18_v160906_NRD90R_boot.img

Installation:

1. Reboot into TWRP -> TWRP_dragon_3.0.2-22.img

2. Install Update.ZIP_PixelC_Ryu_NRD90R-system-vendor.zip

4. Install Update.ZIP_PixelC_Ryu_chromeos-3.18_KERNEL_NRD90R_v160906_followmsi.zip

5. Install SuperSU-v2.78-201609011115.zip

6. Reboot into system

And again .. due to supersu installation it will boot twice - no panic, it´s normal !

Enjoy the September release !
[Pixel C Android Development] Alxoom33:
Thank you!

Backing up now..98℅?

---------- Post added at 09:20 PM ---------- Previous post was at 09:01 PM ----------

Thank you!

Backing up now..98℅?

Flashing, rebooting twice....and, reebooted I to TWRP v.22…I'm in the old TWRP loop. Time to fastboot out of here!

Reflashed System Vendor zip, old and new msi kernel s and SuSuperuser. Then fastboot flashed System reeboot... Success![emoji469]
[Pixel C Android Development] followmsi:
Thanks for testing.

Wer need to wait and observe the current situation on Android 7.

For me personally it's working fine, also twrp v21 works fine for me.

But as we move forward .. twrp will need to move forward as well.

v22 is the first version based on Android 7 sources - fresh AOSP + TWRP sources.

As I understood there is an Android 7 "clean install" way which is working fine, like described here.

http://xdaforums.com/showpost.php?p=68354151&postcount=211

The "dirty install" way, like we do in this thread, using system-vendor.zip is working fine as well.

But you keep your "old" Data partition.

Anyway .. still some Pixel C owners have boot-loop problems .. etc.

The problems are not nessecarly related to TWRP at all.

In general an Android system will boot via boot.img (kernel+ramdisk) into the System.img.

If there is a problem within this process it will fall back into recovery mode, booting stock recovery or custom recovery.

This could have several reasons, like verified boot issues .. etc.

SuperSu is changing the ramdisk inside boot.img - and removes a lot of security related stuff.

Also stuff related to verified boot.

SuperSu is changing default encryption behaviour as well.

If you boot just one time into system without modified ramdisk it will try to forceencrypt your device.

The order of the installation could be the trigger for different problems.

As said above .. we need to wait a bit longer and collect more information.
[Pixel C Android Development] NYCHitman1:
Nothing new in that tag unless you haven't pulled down changes in 2+ months, which is unlike you lol.
[Pixel C Android Development] followmsi:
The last commit is 5 weeks ago .. yes, not very fresh, but still "fresher" as stock kernel.

1e92432*FROMLIST: usb: xhci: Fix panic if disconnect*by Jim Lin*· 5 weeks ago*stabilize-smaug-7897.B-chromeos-3.18

162fdfc*Revert "HACK: memory: tegra: Do not go to 40.8 MHz EMC"*by Danny Huang*· 6 weeks ago

1b05ae7*CHROMIUM: clk: tegra: set sbus rate to minimum when no user enabled*by Danny Huang*· 6 weeks ago

1ede68c*CHROMIUM: clk: tegra: keep sbus clock always on*by Danny Huang*· 6 weeks ago

eef3447*CHROMIUM: clk: tegra: set SCLK source to PLL_P*by Danny Huang*· 6 weeks ago

But the main reason for the "new" boot.img is the new ramdisk from latest stock boot.img. (nrd90r)

Always use the current stock ramdisk to build "my" boot.img.

I know this is manual work ..
[Pixel C Android Development] NYCHitman1:
Yeah, but none of this includes any of the N kernel -- which Google is no longer uploading to Chromium source. It's on Google's git now.

https://android.googlesource.com/kernel/tegra/+/android-7.0.0_r0.16

Just an FYI.
[Pixel C Android Development] Alxoom33:
Thank you for your comments and tireless work.

Is there a substantive difference between the old and new Data partition. Can we game the system by a "clean install" and then restore data from a Nandroid?

Also, noticed that although I was able to install my custom SoftKeyZ Nav bar after installing Busybox to Su/Xbin and debloating the System Partition a little, by removing some non-English language keyboards, I was not able to install layers or substatum. Is it a matter of these apps just needing an update, or is there something in the System and Vendor partition that's stopping layers from loading?
[Pixel C Android Development] followmsi:
Thanks .. maybe time to switch the sources soon. ;)

EDIT:

Just had some time and made a new kernel .. based on google sources now. :)

Update.ZIP_PixelC_Ryu_tegra-3.18_KERNEL_NRD90R_v160907_followmsi.zip

kernel-tegra-3.18_v160907_NRD90R_boot.img

Let´s test the "new" sources :)

Cheers
[Pixel C Android Development] followmsi:
If you restore full data partition you may back to "dirty install" anyway ;)

Sorry, still testing Android 7 myself .. No clue regarding layers.

Cheers
[Pixel C Android Development] nigelhealy:
What is the difference between these kernels? I see the tegra kernel added to the followmsi chromeos kernel. What is their diffference and pros/cons?
[Pixel C Android Development] Alxoom33:
Don't know until we try it. So... try it!
[Pixel C Android Development] NYCHitman1:
Kernel source originally was maintained on Chromium's git, but when N released -- Google moved it to their Android git. Same kernel, just different location.
[Pixel C Android Development] nigelhealy:
I love my Pixel C, it is so good on form factor and the keyboard that I can travel lighter rather than a Chromebook or worse.

The only problem is the Wifi and Bluetooth is unreliable, it drops out, Ive checked forums and seems RMA wont likely improve so Im looking for a software answer. Im sitting out from N as it doesnt support an app I use regularly, but when I move to N, which kernel will produce the best Wifi?

Is it just me trying each in turn?
[Pixel C Android Development] Alxoom33:
Flashed your new kernel. So far, so good...although only time will tell.

Thanks,

---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------

I've never had any bluetooth or wifi issues. Have been on N since first Beta with [MENTION=5480152]followmsi[/MENTION]'s kernels. I do think some Pixel C's have hardware issues, and some don't.
[Huawei P9 Questions & Answers] Milamber:
Can someone check to see if their Google Contacts is stuck after their first sync?

I've tried everything and cant fix it, first sync is fine then after that it I get "Sync is currently experiencing a problems, it will be back shortly"

FIXED: If you are using Signal, turn off the contact sync option under accounts as it will conflict with contacts! Only took me 2 days to find that!!
[Lava Pixel V1] aaryan45:
Flashable TWRP 3.0.0.0 & 3.0.2.0 By Aaryan Pednekar​

FLASH VIA RECOVERY​

IF U GO TO BACK TO TWRP 3.0.0.0 (FLASH TWRP_3.0.0.0.zip)​

DOWNLOAD​

https://drive.google.com/open?id=0B1WL8TCyFfmiLWNWMlN1d0Zna0U

CREDITS:-​

@srinu427 for Porting TWRP 3.0.0.0 Recovery

And

Me (Aaryan Pednekar) For Porting TWRP 3.0.2.0 Recovery​
[Lava Pixel V1] Girish1437:
Good devloper aryan.....

Tanx aryan... And good luck u r next develop
[Lava Pixel V1] aryan9:
I can not find TWRP for my lava z10 mobile
[Samsung Galaxy S5 Neo Questions & Answers] derL3r0y:
Hallo an alle,

ich möchte mir das Samsung Galaxy S5 Neo kaufen und habe da eine frage zu custom roms. Ich habe momentan das Samsung Galaxy Note 3 (hltexx) aber konnte es ohne Probleme mit der HLTE version (cyanogen, aicp etc.) flashen.

Kann ich das S5 Neo auch einfach mit der KLTE version flashen?

Über antworten/erfahrungen würde ich mich freuen und bedanke mich schonmal in vorraus.
[Samsung Galaxy S5 Neo Questions & Answers] *Detection*:
English only on XDA
[Samsung Galaxy S5 Neo Questions & Answers] spyrotsk:
Hi,

No, you can't use another custom Rom for another smartphone, because the modules into kernel, recovery and partitions are different from other smartphone.

Edit: if you try to flash it with custom Rom for different smartphone, you can throw the phone.
[Samsung Galaxy S5 Neo Questions & Answers] GuestK0087:
Thread closed.

English only on XDA.
[AT&T Samsung Galaxy Note 4] kentangz:
I’m sorry if my English is not perfect since I’m from Malaysia and this is my first posting in XDA Forum. And I’m not sure if this is the right forum to post my questions to.

So recently I’ve bought a new Note 4, knowing that the international variant can be rooted easily. Having successfully rooted a few Samsung phones in recent years, I thought that the root method for Note 4 is more or less about the same (either through ODIN flashing, Kingroot, Towelroot etc). After some frustrating attempts, it seemed that I couldn’t get the phone rooted. I managed to get some sort of root using Kingoroot (verified by root checker, and Titanium Backup) but I couldn’t update the SU binaries.

Here are some phone details from the About Device info:

Model Number

SM-N910F

Android Version

5.0.1

Baseband Version

N910FXXU1BOC4

Kernel Version

3.10.40-4160876

Build Number

DONGCHAO.A916

However, from the Phone Info app, I got this detail:

Product Code:

SM-N910AZKECHN

CSC Country:

USA / US

Bootloader Version:

N910AUCU2COC6

PDA Version:

N910AUCU1COC4

CSC Version:

N910AATT1COC4

Baseband Version:

N910AUCU2COC6

Kernel Version

3.10.40-4160876

I’ve tried booting the phone in bootloader, and it says that the product name as SM-910A.

1.	Does this mean that the actual phone model is SM-N910A with a European firmware SM-N910F installed?

2.	If it is a yes, how is it possible that other firmware version can be installed on the AT&T variant? I was under the impression that any firmware must be signed by AT&T before it can be installed on the said model.

3.	I’m quite concerned with the build number DONGCHAO.A916. I’ve tried to get more info about it but none can be found. Anyone know for which market is this firmware meant for?

4.	Do I need to use only the firmware updates from AT&T in the future?

I have so many questions running in head right now but I’m afraid to tinker with the phone any further for fear of bricking it. I’ve never seen the AT&T stock firmware before so I don’t know how my phone might function with the stock rom in Malaysia.

Hope someone can shed a light on this. If it is indeed the SM-910A variant (which is weird since it is sold in the Asian market), I might be stuck with the locked bootloader with no rooting method as of now.
[AT&T Samsung Galaxy Note 4] Shanghai.Knight:
First thing you need is to know what you really have...

Download this and report back what you find

https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
[AT&T Samsung Galaxy Note 4] cnote74:
Bootloader will block any firmware attempt but at&t branded.
[AT&T Samsung Galaxy Note 4] kentangz:
That is exactly the app I used to check the phone info as posted above (the second part of the info, not the one from About Device).

I believe I cannot post the screenshot since my total post counts is less than 10. But please tell me what other info should I report here from the app
[AT&T Samsung Galaxy Note 4] kentangz:
Apparently I was mistaken about posting the image file. Please refer to the attached screenshot for the info of my phone, including the info from the rom's About Device
[AT&T Samsung Galaxy Note 4] Shanghai.Knight:
Looks to me like you have an ATT Phone... Perhaps someone rooted the phone and edited the information to make it look like you have the international variant?
[AT&T Samsung Galaxy Note 4] spexwood:
This shouldn't be possible since the only root obtained on the ATT variant was temp root. If the information was edited (build.prop), wouldn't it revert back to stock upon a reboot?

Also, speaking of reboot, shouldn't the phone not say that it's rooted since a reboot would unroot it?
[AT&T Samsung Galaxy Note 4] giga8547:
Im wondering if what you have is a clone and not genuine
[AT&T Samsung Galaxy Note 4] kentangz:
That's the thing. I've actually thought of that but with all the standard Samsung built quality on this phone, I can't even tell. And I bought it at legit retailer with the Samsung warranty. Aside from the physical inspection, is there any way to test it through an app or something?