Poll: *** Google Nexus 6 ***

Which colour & memory size are you going to get?

  • White - 32GB

    Votes: 33 15.6%
  • Blue - 32GB

    Votes: 77 36.3%
  • White - 64GB

    Votes: 36 17.0%
  • Blue - 64GB

    Votes: 66 31.1%

  • Total voters
    212
Just attempted to root my N6 (previously rooted a few N5s) and got a error saying the device is not trusted and i couldnt get past it without flashing stock image, not sure wether to try again or not as im finding the colors warm and want to change them using a kernel.

EDIT: got franco kernel on now, anyone else using it and changed the colour settings? ive got the phone on charge next to me now and the colours look a lot better from the side the whites actually look white and not yellow. Any recommendations for the settings?

I personally use francos own profile, it makes the colours pop more but I like it that way.
 
Using FK I went ahead and lowered the saturation and raised the white point.

LvS3YOL.png
4nzAoze.png



EDIT:

I also went ahead and ordered this

:D:D

973Q8WI.jpg
 
Last edited:
Gravitybox is out for xposed too.

Now I finally have removed the alarm icon, added a centre clock & got a decent circle battery percentage indicator.
 
Cheers for the color adjustment settings kona just applied them and its a lot better now.

Anytime.


Quick question guys. My spare Nexus 6 is on a stock rom and the bootloader is unlocked. Now, if I root it, will rooting wipe the phone?

I'm thinking no, but just want to be sure.
 
Cheers guys. Rooted last night and all good.

The new TWRP has an option I've not seen before when backing up, it's called 'system image'. Anyone know what that is?

Answer?

The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.

Also when rooting I didn't flash a modified boot.img from here

http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

as the link didn't have one for MRA58N. What implications does this have?

My root process was

1. Flash TWRP 2.8.7.1 via ADB
2. Flash Elemental kernel 3.06 + SuperSU 2.52 via TWRP.
 
Last edited:
I quick Google makes me think 'system image' is a stock backup of your ROM... rather than the 'system' backup which will have your changes is in. But I could very likely be wrong. Or that could be the wrong way around.

**EDIT** From XDA -

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
 
So it's do do with Official OTA's.

That's fine as I won't be doing those anymore. Cheers.



Amos91 - I have a feeling you'd know the answer to this:

Also when rooting I didn't flash a modified boot.img from here

http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

as the link didn't have one for MRA58N. What implications does this have?

My root process was

1. Flash TWRP 2.8.7.1 via ADB
2. Flash Elemental kernel 3.06 + SuperSU 2.52 via TWRP.
 
Hey,

Has anyone on stock 6.0 not received the November security update yet? I keep hammering the "check for updates" button, but no joy.

I guess I can sideload but, effort...

Cheers,

Su
 
So it's do do with Official OTA's.

That's fine as I won't be doing those anymore. Cheers.



Amos91 - I have a feeling you'd know the answer to this:

It's just Chainfires boot image (kernel) that allows root to work. All the boot images are the same across all N6 marshmallow builds so you don't necessarily have to flash a specific version for your build.

Franco already has these elements built into his kernel.
 
Ok thanks.

Question is do I need that boot.img? It seems to be working fine without.

Also I'm on the elemental kernel at the moment. If I wanted Franco's, do I just flashing over the top?
 
Hey,

Has anyone on stock 6.0 not received the November security update yet? I keep hammering the "check for updates" button, but no joy.

I guess I can sideload but, effort...

Cheers,

Su

Yes I got it about a week ago. I was on mobile data for a while and got nothing. As soon as I switched to wifi the update came through.
 
Ok thanks.

Question is do I need that boot.img? It seems to be working fine without.

Also I'm on the elemental kernel at the moment. If I wanted Franco's, do I just flashing over the top?

Don't need it, the custom kernels all incorporate it. It's just for people that want a true stock experience just with working root.

I normally just flash over the top, however some people say you should flash a standard version & system inage first due to ramdisk changes.

I often, go into fastboot, flash the Chainfires image above, then immediately flash the Franco image. Never had an issue.

http://elementalx.org/ten-rules-for-flashaholics/
 
Last edited:
Back
Top Bottom