Database Develop

Nexus 6 coming tomorrow

Guys I just have a question,
I will be receiving my nexus 6 tomorrow and I plan on unlocking the boot loader and rooting it, but what I am curious about from reading all the threads is a few things.
1) I plan on using adb to unlock boot loader and root
2) I plan on using flashify to install twrp so i can be able to get a backup of the stock recovery
My question is this. I plan on installing cm12 on my device and i like the idea of having my device descrpyted. I am told I have to flash the script I believe made by chainfire, but i also read u can flash another kernel. Which would i have to do? I read some say that u have to do the one made by chainfire first, and others said u just have to flash another kernel.
Also since the cm12 comes encrypted as default and lets say I "dont" want to descrypt do I have to before I flash cm12 even though its set as default encrpyted just like stock?

the_rooter said:
1) I plan on using adb to unlock boot loader and root
2) I plan on using flashify to install twrp so i can be able to get a backup of the stock recovery
Click to expand...
Click to collapse
1) You'll need to use fastboot to unlock the bootloader. YOu'll then need to use fastboot to flash the recovery. If you're going to flash a rom, you may not need to then root as some roms are already rooted
2) flashify needs root to flash the recovery and you need the recovery to flash root.

What chain fire thing? Chain fire doesn't have anything in relation to encryption from what I know. Go to Android development and find the unencrypt thread and from there you'll find out how to unencrypt.
Do note that your data will be wiped. You'll have to flash a custom kernel before your phone starts up otherwise your phone will be encrypted again.
Most custom kernels have encryption patches to accelerate the encryption i/o speeds. You're better off just leaving it enabled if you want to keep things simple.
Sent from my Nexus 6 using Tapatalk

rootSU said:
1) You'll need to use fastboot to unlock the bootloader. YOu'll then need to use fastboot to flash the recovery. If you're going to flash a rom, you may not need to then root as some roms are already rooted
2) flashify needs root to flash the recovery and you need the recovery to flash root.
Click to expand...
Click to collapse
If i remember from previous devices doesnt flashify allow backup of the stock recovery? and also it flashes twrp within the app as long as root is done.
Edit:
Also I wasnt sure who made the descrypt file to flash, and yes i know it does a FDR, but wouldnt it be better just to flash a custom kernel? Most kernels are already descrypted. Sorry if i repeated anything.

the_rooter said:
If i remember from previous devices doesnt flashify allow backup of the stock recovery? and also it flashes twrp within the app as long as root is done.
Click to expand...
Click to collapse
Yes, but you wont have root at that point so, no...

rootSU said:
Yes, but you wont have root at that point so, no...
Click to expand...
Click to collapse
i am honestly not trying to pick a fight and i thank you for taking your time to help me out but if i follow this thread:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
That gives me root via fastboot up to the end of obtaining root and not doing custom recovery.
Within flashify i know u can back up the stock recovery, and then flash twrp. After i flash twrp i will be making a back up of my system just in case something goes wrong.
That sound correct? I prolly will give a few days and wait till my usb otg sd adapter to get here before i actually flash a rom. Sorry should have mentioned that.

the_rooter said:
i am honestly not trying to pick a fight and i thank you for taking your time to help me out but if i follow this thread:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
That gives me root via fastboot up to the end of obtaining root and not doing custom recovery.
Within flashify i know u can back up the stock recovery, and then flash twrp. After i flash twrp i will be making a back up of my system just in case something goes wrong.
That sound correct? I prolly will give a few days and wait till my usb otg sd adapter to get here before i actually flash a rom. Sorry should have mentioned that.
Click to expand...
Click to collapse
That uses a script to flash root... But lets break down your steps...
fastboot unlock
run script
boot into android
install flashify
flash recovery
Download rom
reboot recovery
flash rom
vs my steps...
fastboot unlock
fastboot flash recovery
put rom on sdcard
flash rom
It doesnt matter if you backup your stock recovery, because its all available on the google site anyway as this is a nexus device.

rootSU said:
That uses a script to flash root... But lets break down your steps...
fastboot unlock
run script
boot into android
install flashify
flash recovery
Download rom
reboot recovery
flash rom
vs my steps...
fastboot unlock
fastboot flash recovery
put rom on sdcard
flash rom
It doesnt matter if you backup your stock recovery, because its all available on the google site anyway as this is a nexus device.
Click to expand...
Click to collapse
thanks man that helps alot. Now still on the confusing about the encrypt and decrypt. Whats the advantages to disadvantages? because from what i here people say it should be decrpyted, and that i have to follow the step set up in that thread to do so, but wouldnt like i said before just be as easier to just flash a decrpyted kernel and be done with it?
Edit: Sorry with all the questions this is my first nexus device since i am on verizon.

the_rooter said:
thanks man that helps alot. Now still on the confusing about the encrypt and decrypt. Whats the advantages to disadvantages? because from what i here people say it should be decrpyted, and that i have to follow the step set up in that thread to do so, but wouldnt like i said before just be as easier to just flash a decrpyted kernel and be done with it?
Edit: Sorry with all the questions this is my first nexus device since i am on verizon.
Click to expand...
Click to collapse
Do some reading off XDA on what encryption is and its advantages/disadvantages.
To be simplistic,
Encryption pro: more protection with your data
Encryption disadvantage: slower I/O speed
(Most custom kernels include patches that accelerate the speed of I/O with encryption on, Google's stock kernel does not include this)
Decryption pro: faster I/O speeds, possible increase in battery life as your phone is not using clock cycles to perform encryption (not by much, if any)
Decrypton disadvantage: less protection with your data, but if you're not carrying sensitive data, then who cares.
My suggestion to you is to leave it encrypted and if you don't notice anything slowing down then leave it. Keep it simple.

zephiK said:
Do some reading off XDA on what encryption is and its advantages/disadvantages.
To be simplistic,
Encryption pro: more protection with your data
Encryption disadvantage: slower I/O speed
(Most custom kernels include patches that accelerate the speed of I/O with encryption on, Google's stock kernel does not include this)
Decryption pro: faster I/O speeds, possible increase in battery life as your phone is not using clock cycles to perform encryption (not by much, if any)
Decrypton disadvantage: less protection with your data, but if you're not carrying sensitive data, then who cares.
My suggestion to you is to leave it encrypted and if you don't notice anything slowing down then leave it. Keep it simple.
Click to expand...
Click to collapse
Thanks for you help guys. With this being my first nexus phone i think i understand now.

the_rooter said:
Thanks for you help guys. With this being my first nexus phone i think i understand now.
Click to expand...
Click to collapse
Once a Nexus you won't go back Nexus devices are the devices to be on XDA, traffic is a lot higher here than the other phones.

zephiK said:
Once a Nexus you won't go back Nexus devices are the devices to be on XDA, traffic is a lot higher here than the other phones.
Click to expand...
Click to collapse
well yeah but like i said i am on big red and this is the first nexus device they are allowing since the gnex days

Trouble Decrypting Nexus 6

I recently received my nexus 6 a couple days ago and I LOVE it. The problem I am having at the moment is that I can't seem to get it to go decrypt. I downloaded the tool kit and my devices build isn't present. As a result, the tool kit it won't allow me to run the decrypt option on the fastboot window.
It's anyone running into this. My build is a LNX***.

First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?

Didgeridoohan said:
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Click to expand...
Click to collapse
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.

KappaAce2010 said:
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
You just need a custom kernel and a wipe.

another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce

Circaflex said:
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Click to expand...
Click to collapse
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.

KappaAce2010 said:
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.

+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).

Didgeridoohan said:
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Click to expand...
Click to collapse
I already plan on doing this anyway. Just time is conflicting with me at the moment.
rootSU said:
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
Click to expand...
Click to collapse
Well it happened, it's not going anywhere. Either way thanks guys for the advice. I should figure out everything tonight.
Nexus 6....man I missed being rooted.

Everything is a go. Fully decrypted and loving it. Thanks again.

Nexus 6 forced encryption questions.

Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!

H4X0R46 said:
Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
Click to expand...
Click to collapse
1. Yes
2. You can't update with any modifications to the system. Meaning you must have stock recovery, no root, etc.
3. Yes (They don't FORCE encryption meaning if your unencrypted already you will stay unencrypted.)
4. Yes
Sent from my Nexus 6 using Tapatalk

Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!

H4X0R46 said:
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
Click to expand...
Click to collapse
To be unencrypted, you must format data. Do not use toolkits unless you know how to use ADB/fastboot. Yes this phone is hard to brick as long as the bootloader is unlocked.

H4X0R46 said:
Hello! So I just have some questions about the forced encryption on the Nexus 6. I will be getting a Nexus 6 very soon here, and I like custom ROMs and custom software. Questions are:
1) Can I install a custom ROM without even messing with the forced encryption? In other words, can I ignore that it's there and just unlock bootloader, install custm recovery, and flash a ROM and gapps? Will it just run with the encryption on?
2) If I do disable the encryption, can I use the normal software update? (with no custom ROM of course in this case) Or will I have to reflash the encrypted kernel to system update?
3) Do some custom ROMs just disable the encryption by default?
And
4) If it get stuck in a boot loop because of a kernel issue, is this easy fixable? Or is it a hard brick that can't be recovered?
Thanks in advance everyone!
Click to expand...
Click to collapse
3. its the kernel, not rom, that makes you be abke to decrypt, not rom. it might be added to a rom as well, but it would be in its kernel. also, ot doesnt decrypt, it gives you the option to decrypt. but you have to do it, decrypt.
4 easily fixable. you have to learn the very basics of it though. rrally. but its extremely easy to fix.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
H4X0R46 said:
Thanks for the quick response! Much appreciated. On my fourth question, did you mean that's easily fixable? Or like, yes that's a hard brick? And also, (question 3) you say that a custom ROM won't force it, but if you're still encrypted when you flash the ROM, does that mean you can just turn it off in your settings with a ROM? Or do you stay encrypted? Or how does that work?
EDIT: (question 2) if I used a toolkit to reflash a stock image, that's clean enough for a normal system update right? After that and relocking the bootloader?
Sorry for all the questions, I just wanna know these things before I go fork out $600 for a device that I intend to mod!
Click to expand...
Click to collapse
learn to do it right the first time. it sounds hard and complicated, but its extremely easy after you do it all manually the first time. after that, feel free to use a toolkit. it wont save you time btw, doing it right takes just 3-5 minutes after the first time

Thanks guys! Much appreciated! If things were to go horribly wrong with the kernel if I did decrypt it and it bricked because of a kernel issue, would flashing a stock image still be a fix for a kernel problem? (with the bootloader unlocked of course). I'm not new to Android modding, I have a phone running a CM nightly right now, but this encryption thing and messing with a phones kernel scares me a bit haha

H4X0R46 said:
Thanks guys! Much appreciated! If things were to go horribly wrong with the kernel if I did decrypt it and it bricked because of a kernel issue, would flashing a stock image still be a fix for a kernel problem? (with the bootloader unlocked of course). I'm not new to Android modding, I have a phone running a CM nightly right now, but this encryption thing and messing with a phones kernel scares me a bit haha
Click to expand...
Click to collapse
Flashing any rom also flashes a kernel, so you've already done it before. Its no different here

danarama said:
Flashing any rom also flashes a kernel, so you've already done it before. Its no different here
Click to expand...
Click to collapse
Alright, custom ROMs contain kernels. I've heard that before but wasn't sure haha Thanks everyone!

H4X0R46 said:
Alright, custom ROMs contain kernels. I've heard that before but wasn't sure haha Thanks everyone!
Click to expand...
Click to collapse
every rom haa a kernel in it. a rom can not run without a kernel. a kernel is like what will connect the cpu and hardware with the os.

H4X0R46 said:
If things were to go horribly wrong with the kernel if I did decrypt . . .
Click to expand...
Click to collapse
The first question you need to answer is:
'Why decrypting?'
When the answer contains words like 'speed' or 'performance' than you may consider to leave your N6 encrypted.

NLBeev said:
The first question you need to answer is:
'Why decrypting?'
When the answer contains words like 'speed' or 'performance' than you may consider to leave your N6 encrypted.
Click to expand...
Click to collapse
right :good:

chavonbravo said:
Try Ultimate Theft Alert v3.5 and W.I.M.P. Both have ability to track via GPS when your phone gets stolen as well.
Click to expand...
Click to collapse
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?

H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
Click to expand...
Click to collapse
I wouldn't say it triples battery, just increases the NAND read/write speed performance. Battery could take a hit as opening apps takes longer when encrypted.

Choristav said:
I wouldn't say it triples battery, just increases the NAND read/write speed performance. Battery could take a hit as opening apps takes longer when encrypted.
Click to expand...
Click to collapse
Apps aren't encrypted. If they were we couldn't pull them from phone to decompile and mod them. Only your data is and it is only a few KBs per app. Only notice encryption on large personal files and downloads.

H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true? Because it would be a waste if the phones battery is abysmal for such a great device! From anyone's experience here, should I not worry about it and just leave the device encrypted?
Click to expand...
Click to collapse
im encrypted, and my n6 sees between 5.5-7 hours sot. thats more than most unencrypted phones see!
---------- Post added at 08:28 PM ---------- Previous post was at 08:26 PM ----------
battery life is all about how you personally use the device, how you set it up, which apps you use, and your phone/data signal quality. everything else plays a minor role for battery.

Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.

H4X0R46 said:
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
Click to expand...
Click to collapse
Only problems you will notice is all the CM bugs.

H4X0R46 said:
Alright! So if I just ignore the encryption and install a ROM, it won't pose a problem at all? I can say, leave it encrypted and install a cm ROM without issue? And because of the encryption, do operations like installing a zip and formatting the device take a lot longer? I'm using a Galaxy Note 2 right now and the ROM installations take mere seconds to install, so a Nexus 6 might be something different.
Click to expand...
Click to collapse
formatting is how you decrypt. besides decrypting, theres no need to ever format your device. installing a zip it depends on the zip, generally its fast. flashing a zip is fast. what will be slowed down is tranafering a large file to your computer to or from a pc.
oh, and cm does get many bugs, often.

Oh yea! Bugs for sure! I'm running a cm nightly right now on my Note 2 and it's buggy as hell haha I just like messing with ROMs really, I will probably leave it stock and rooted for the most part Just like to see new ROMs and tweaks and stuff. Thanks guys! You all helped a ton! I will probably buy a Nexus 6!

H4X0R46 said:
Well, I've heard from many sources that the encryption in the phone just KILLS battery life, and if you turn off the encryption, it nearly triples the battery life. Is this true?
Click to expand...
Click to collapse
.
I have tried decryption with the Chroma and CM Roms. I did not notice more performance in daily use.
Then 5.1.1 arrives with some confusion because Google presented several factory images for the N6. I went back to stock and waited for the OTA.
After flashing the OTA and Franco's kernel my battery life was about the same.
Of course it depends on the daily use, but for me it was clear that not decrypting causes better battery life but the kernel.

Easy to follow Root Steps for Stock Android 6.0?

Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!

TPADroid said:
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
Click to expand...
Click to collapse
First this does not belong in the Development sections, moved here. Secondly please read the Forum Rules on posting...thanks.

Thank you for moving to the appropriate location.

as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.

Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481

simms22 said:
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Click to expand...
Click to collapse
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!

TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
The boot.img files that your referring to are probably to un-encrypt your phone. I personally don't but other always have. Supposed to make it faster although i haven't been bothered by it being slow.
To unlock the bootloader all you have to do is used fastboot oem unlock via fastboot while your phone is in the bootloader mode.

You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[

mbiscuits said:
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
Click to expand...
Click to collapse
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
thats a kernel thatll let you unencrypt, if you want.

simms22 said:
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
Click to expand...
Click to collapse
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/

mbiscuits said:
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
Click to expand...
Click to collapse
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.

simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.

mbiscuits said:
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
Click to expand...
Click to collapse
which is why i always recommend that someone new root their phone the proper way the first time, to learn how to do it, and to learn a general way to fix your phone in case you mess up. after the first time, use toolkits all you want. but the learning how to do it properly is a very important.

TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
That modified img allows for root because you cant just flash SU on the stock one (not yet anyway). Unlocking the bootloader is something different.

simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
Anybody knows where is the correct toolkit?

cpugeeker said:
Anybody knows where is the correct toolkit?
Click to expand...
Click to collapse
in my opening, there is no 'correct" toolkit.

Jnewell05 said:
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.

jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
If you haven't rooted for over a year why do it now? There are sure to be updates to how to root on the Nexus 6 and since I don't use my nexus 6 very much I hate to steer you in the wrong direction, as to backup information. I recently got the android 7.0 update and I haven't really had a chance to check it out yet. But I bet there are dozens of ways to backup if you would search Google.
Sent from my SAMSUNG-SM-G935A using Tapatalk

jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.

istperson said:
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
Click to expand...
Click to collapse
Thank you very much!!!!

Boot-loader Flashing vs. using Flashfire

(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)

RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.

I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use

ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.

ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.

RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery

simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone

Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.

scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).

And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app

RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.

31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx

simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?

Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app

31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?

RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.

simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.

RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me

Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.