Database Develop

[Q] Cons and Pros of rooting my Nexus 6 XT1103?

Should I root my Nexus 6? Why or why not?
Would I be able to go back to 100% stock everything to have my warranty back? Or will people know I unlocked/rooted it?
Would I be able to un-brick my device? (Soft and hard?)
Would I be able to install OTA updates, or would I have to use custom roms?
I have been thinking of using the Nexus toolkit by Wugfresh, what order should I do everything in? I want to decrypt my phone as well.
Should i use the root toolkit or manually unlock and root using Command prompt?
Thank you all

You should post this in the Q & A section
Unlocking and rooting means custom rom, i think you have your answer

Use the toolkit by wugfresh. Simple and good.

C00lBeanz said:
Should I root my Nexus 6? Why or why not?
Would I be able to go back to 100% stock everything to have my warranty back? Or will people know I unlocked/rooted it?
Would I be able to un-brick my device? (Soft and hard?)
Would I be able to install OTA updates, or would I have to use custom roms?
I have been thinking of using the Nexus toolkit by Wugfresh, what order should I do everything in? I want to decrypt my phone as well.
Should i use the root toolkit or manually unlock and root using Command prompt?
Thank you all
Click to expand...
Click to collapse
I am of the opinion that if you own a Nexus, you should root it.. it's too easy and development is awesome.
You could go back to 100% stock, yes. No on would ever be able to tell. You can do that in Wug's Toolkit.
You can undo a soft brick, hard bricks are hard to do on a Nexus.. don't do things you don't understand in Fastboot and you shouldn't hard brick. I dunno about undoing one of those, though.
You can't install OTA, but you can use Wug's toolkit or Fastboot to flash stock updates if you wish to go stock. If not, custom ROMs are updated to match whatever base (OTA) Google is currently using, so you would never be unable to update like on a locked phone like a Samsung because of root.
If you use the Kit, you should unlock your device, decrypt if you want to, if not no need, and install custom recovery with root, simple. It's very easy to do in Fastboot, though, and I would encourage you to learn.

wrongway213 said:
I am of the opinion that if you own a Nexus, you should root it.. it's too easy and development is awesome.
You could go back to 100% stock, yes. No on would ever be able to tell. You can do that in Wug's Toolkit.
You can undo a soft brick, hard bricks are hard to do on a Nexus.. don't do things you don't understand in Fastboot and you shouldn't hard brick. I dunno about undoing one of those, though.
You can't install OTA, but you can use Wug's toolkit or Fastboot to flash stock updates if you wish to go stock. If not, custom ROMs are updated to match whatever base (OTA) Google is currently using, so you would never be unable to update like on a locked phone like a Samsung because of root.
If you use the Kit, you should unlock your device, decrypt if you want to, if not no need, and install custom recovery with root, simple. It's very easy to do in Fastboot, though, and I would encourage you to learn.
Click to expand...
Click to collapse
Thank you for answering all of my questions
But I read somewhere that you should decrypt the phone after everything is done like the recovery, ROM, or does it not matter when you decrypt it? Would it stay decrypted?

C00lBeanz said:
Thank you for answering all of my questions
But I read somewhere that you should decrypt the phone after everything is done like the recovery, ROM, or does it not matter when you decrypt it? Would it stay decrypted?
Click to expand...
Click to collapse
No, it wouldn't even be possible to do it that way. You read exactly wrong, it's basically the opposite. You want to decrypt as soon as you unlock. Decrypting your phone formats your userdata, internal sd card at all, meaning it erases EVERYTHING on your phone. If you wish to decrypt, you want to do it after unlocking and before rooting and you always want to make sure to check if a ROM forces encryption before flashing it.. if you flash a ROM that forces encryption when you're decrypted it'll encrypt all your data. If you want to flash a ROM that forces encryption, make sure to flash it with a kernel that does not force encryption to remain unencrypted, Personally I just remain encrypted, easier and no performance difference Ive noticed, just read/write speeds and that has zero effect on use.

wrongway213 said:
No, it wouldn't even be possible to do it that way. You read exactly wrong, it's basically the opposite. You want to decrypt as soon as you unlock. Decrypting your phone formats your userdata, internal sd card at all, meaning it erases EVERYTHING on your phone. If you wish to decrypt, you want to do it after unlocking and before rooting and you always want to make sure to check if a ROM forces encryption before flashing it.. if you flash a ROM that forces encryption when you're decrypted it'll encrypt all your data. If you want to flash a ROM that forces encryption, make sure to flash it with a kernel that does not force encryption to remain unencrypted, Personally I just remain encrypted, easier and no performance difference Ive noticed, just read/write speeds and that has zero effect on use.
Click to expand...
Click to collapse
Is CyanogenMod decrypted?

No, Cm forces encryption. If you want to remain decrypted on official CM nightlies you'll need to make sure you're flashing them with a custom kernel that does not force encryption. I recommend Franco personally but many kernels will work for that purpose.

wrongway213 said:
No, Cm forces encryption. If you want to remain decrypted on official CM nightlies you'll need to make sure you're flashing them with a custom kernel that does not force encryption. I recommend Franco personally but many kernels will work for that purpose.
Click to expand...
Click to collapse
What is your recommended rom and kernel?

C00lBeanz said:
What is your recommended rom and kernel?
Click to expand...
Click to collapse
Lots of good ROMs and kernels but feel free to look in my sig lol

wrongway213 said:
Lots of good ROMs and kernels but feel free to look in my sig lol
Click to expand...
Click to collapse
Does dirty unicorns have forced decryption off? Or do I have to flash the kernel too?

C00lBeanz said:
Does dirty unicorns have forced decryption off? Or do I have to flash the kernel too?
Click to expand...
Click to collapse
I am running Dirty Unicorn as my Daily with Sensei Kernel, great battery and smooth. It does not force encryption with the Kernel that comes with it.
If you go to any Roms post it will 99% of the time tell you if it is forced or not.

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.

A ROM question

Not gonna ask the best ROM, as everyone gets a bit uptight about those, and feel the need to defend "their team" and all that...
My question is more generic, in that I am wondering if there is even a ROM out there that will meet MY needs... so if I list those things that I would need in a ROM, maybe someone can simply answer yes or no and point me in the right direction?
Here is what I would be looking for in a ROM:
1) Stability, has to be as stable as stock, no screens of dead or random reboots
2) Speed, zero lag, fast and fluid
3) Everything has to work. If it works on stock, be it apps like VZW Visual VM or whatever, it needs to work on the ROM
4) More polish and eye candy, nice animations, make the device beautiful to use without being buggy or laggy
5) Battery life at least as good as stock
If there is a ROM that gives you all that, has a bit more customization but not so much that it takes half a day to set it up, what would it be? Or would I be better served just using a different launcher?
I have not installed a ROM in a couple years... I was a flashaholic for awhile, but a few phones that I had in a row worked really well in stock form, and some had locked bootloaders that never got cracked, so I kinda gave up on them for while and so my knowledge is a bit rusty...
What I don't want to do is go to the trouble of installing a new ROM and having it not work, or be buggy, etc... This has to be daily driver quality and I want to USE it, no spend too much time fiddling with it.
Ideas?

SquireSCA said:
Not gonna ask the best ROM, as everyone gets a bit uptight about those, and feel the need to defend "their team" and all that...
My question is more generic, in that I am wondering if there is even a ROM out there that will meet MY needs... so if I list those things that I would need in a ROM, maybe someone can simply answer yes or no and point me in the right direction?
Here is what I would be looking for in a ROM:
1) Stability, has to be as stable as stock, no screens of dead or random reboots
2) Speed, zero lag, fast and fluid
3) Everything has to work. If it works on stock, be it apps like VZW Visual VM or whatever, it needs to work on the ROM
4) More polish and eye candy, nice animations, make the device beautiful to use without being buggy or laggy
5) Battery life at least as good as stock
If there is a ROM that gives you all that, has a bit more customization but not so much that it takes half a day to set it up, what would it be? Or would I be better served just using a different launcher?
I have not installed a ROM in a couple years... I was a flashaholic for awhile, but a few phones that I had in a row worked really well in stock form, and some had locked bootloaders that never got cracked, so I kinda gave up on them for while and so my knowledge is a bit rusty...
What I don't want to do is go to the trouble of installing a new ROM and having it not work, or be buggy, etc... This has to be daily driver quality and I want to USE it, no spend too much time fiddling with it.
Ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214

Evolution_Tech said:
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
Hmmm... that might be what I am looking for...
Does the latest version have the stagefright fix built in?

SquireSCA said:
Hmmm... that might be what I am looking for...
Does the latest version have the stagefright fix built in?
Click to expand...
Click to collapse
Yes.

Evolution_Tech said:
Yes.
Click to expand...
Click to collapse
Cool. And I am sorry if this is a dumb question, but like I said, it has been a couple years since I installed a ROM...
I can use Wug's Nexus toolkit to install a custom recovery, and then take the downloaded ROM and recommended GAPPS files, go into Recovery, install ROM, install Gapps, then factory reset and I am good to go?

SquireSCA said:
Cool. And I am sorry if this is a dumb question, but like I said, it has been a couple years since I installed a ROM...
I can use Wug's Nexus toolkit to install a custom recovery, and then take the downloaded ROM and recommended GAPPS files, go into Recovery, install ROM, install Gapps, then factory reset and I am good to go?
Click to expand...
Click to collapse
I don't personally recommend toolkits unless you have ADB/fastboot knowledge and experience but otherwise yes. You don't need to factory reset after ROM installation, just do the required wipes, generally listed in the OP of the ROM you choose, in TWRP, prior to flashing.

Evolution_Tech said:
I don't personally recommend toolkits unless you have ADB/fastboot knowledge and experience but otherwise yes. You don't need to factory reset after ROM installation, just do the required wipes, generally listed in the OP of the ROM you choose, in TWRP, prior to flashing.
Click to expand...
Click to collapse
Which is the better/easier Recovery to use?

SquireSCA said:
Which is the better/easier Recovery to use?
Click to expand...
Click to collapse
TWRP recovery is THE recovery for shamu.

Evolution_Tech said:
TWRP recovery is THE recovery for shamu.
Click to expand...
Click to collapse
Got it, just installed it. Put the ROM and Gapps in a folder and I will first make a Nandroid of my current setup... Then I will try it out.
The OP for that ROM doesn't have any instructions, but you said that in TWRP that I need to wipe cache and stuff PRIOR to installing the ROM? I always thought you did that last? Am I remembering it wrong or did something change?

SquireSCA said:
Got it, just installed it. Put the ROM and Gapps in a folder and I will first make a Nandroid of my current setup... Then I will try it out.
The OP for that ROM doesn't have any instructions, but you said that in TWRP that I need to wipe cache and stuff PRIOR to installing the ROM? I always thought you did that last? Am I remembering it wrong or did something change?
Click to expand...
Click to collapse
For your first installation, wipe, used advanced wipe, then select dalvik, cache, data, and system. Then flash your ROM. Updates to the same ROM can usually be "dirty flashed" by simply wiping cache and dalvik prior to installation.

Tried it out, but found that it was slower in Antutu by 3,000 points and it was a bit laggy at times... Weird.

I wouldn't hold a ton of value or base anything off Antutu.
Sorry if I didn't pay attention to time stamps between your posting. I did look at your stats and see you have plenty of experience here. May just need to give a bit of time for ROM to settle.
I have tried several ROMs here and consider there to be a BIG 3, or the most popular. I won't say the names due to the fact that I don't want to place any one above the other. However, I would recommend a ROM with Layers.
When you go to wipe prior, wipe all but internal storage. I wipe twice, just because I am OCD. Flash all necessaries and sometimes an alternate kernal will help, but give baked in kernal a chance. At least a cylcle or two. Wipe the Davlik and Cache after flash, as TWRP suggests.
There are a few to choose from which are close to stock without overdoing it. Most things folks want to do to customize can be done with apps in Play Store without over loading file size of ROM.
OK, I'll say it, but I don't want you to think I am partial. Try Chroma
Sent from my Nexus 6 using XDA Free mobile app

captemo said:
I wouldn't hold a ton of value or base anything off Antutu.
Sorry if I didn't pay attention to time stamps between your posting. I did look at your stats and see you have plenty of experience here. May just need to give a bit of time for ROM to settle.
I have tried several ROMs here and consider there to be a BIG 3, or the most popular. I won't say the names due to the fact that I don't want to place any one above the other. However, I would recommend a ROM with Layers.
When you go to wipe prior, wipe all but internal storage. I wipe twice, just because I am OCD. Flash all necessaries and sometimes an alternate kernal will help, but give baked in kernal a chance. At least a cylcle or two. Wipe the Davlik and Cache after flash, as TWRP suggests.
There are a few to choose from which are close to stock without overdoing it. Most things folks want to do to customize can be done with apps in Play Store without over loading file size of ROM.
OK, I'll say it, but I don't want you to think I am partial. Try Chroma
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Oh trust me, I have no concerns with people being partial. Some people get bent out of shape in "best ROM" debates, but I don't. I WANT to know which ones are top tier, and why, from people that have used them.
I know that Antutu is not the end all be all... But when I saw it was laggy, I run that to see if it is just placebo, and sure enough, it was slower and there was a little stuttering and lower frame rates in the final 3D game test... I just use it as a reference point, that's all...
I played with Layers a little and didn't really get much out of it... It just seemed to change the color a bit on menus and things, so I didn't see a lot of benefit.... or am I missing something?
I will take a look at Chroma and see how that looks, thanks.

Question about kernels

Hey guys! Me again! Just wanted to know if you're supposed to wipe userdata for every custom kernel with this phone. I know it has the forced encryption and it complicates things a bit. I know if you flash an unencrypted kernel, it needs to be wiped because it can't read your old encrypted data, but as for a custom kernel change that maybe has encryption on, is a full wipe still needed? Thanks guys!
Sent from my Nexus 6

H4X0R46 said:
Hey guys! Me again! Just wanted to know if you're supposed to wipe userdata for every custom kernel with this phone. I know it has the forced encryption and it complicates things a bit. I know if you flash an unencrypted kernel, it needs to be wiped because it can't read your old encrypted data, but as for a custom kernel change that maybe has encryption on, is a full wipe still needed? Thanks guys!
Sent from my Nexus 6
Click to expand...
Click to collapse
short answer, no.
long answer.. you NEVER have to wipe when flashing a kernel. what does your data and installed apps have to do with kernels? its like wiping your butt specifically to eat a banana :silly:

Oh no way? I heard the unencrypted kernels need a full wipe! And the same when installing the stock kernel back! Is this wrong info?
As for what it has to do with kernels, I thought it did just because this device specifically complicates it with it's forced encryption.
Sent from my Nexus 6

@simms22 banana huh. Lol I agree guys, and why would the encryption matter. Correct me if I'm wrong Simms but that's like saying yes to permissive boot, no to enforcing. Just kernel commands. Still a kernel. Fastboot wouldn't, flashifly wouldn't.
Sent from my Nexus 6 using Tapatalk

Alright guys! So I was told false information hahahaha nice banana analogy. So flashing an unencrypted kernel means I can retain my data? The forced encryption doesn't cause any extra complications?

H4X0R46 said:
Alright guys! So I was told false information hahahaha nice banana analogy. So flashing an unencrypted kernel means I can retain my data? The forced encryption doesn't cause any extra complications?
Click to expand...
Click to collapse
It's always best practice to to wipe or format userdata and if you have one when going from one version of Android to another (such as Lollipop to Marshmallow) but I guess there's nothing wrong with trying a "dirty upgrade" (no format) and seeing if everything works okay. If it doesn't you can always go back and wipe or format userdata and restore from your backup.

713brianp27 said:
@simms22 banana huh. Lol I agree guys, and why would the encryption matter. Correct me if I'm wrong Simms but that's like saying yes to permissive boot, no to enforcing. Just kernel commands. Still a kernel. Fastboot wouldn't, flashifly wouldn't.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
its made into a kernel option nowadays, but it really can be implemented by anything. it use to be apps that people used, but google banned all those apps from the play store, like 6 months ago i think.

Oh yeah I deal with selinux in repos. I just add the cmdline, but I was just using that as an analogy referring to encryption on kernel. Not seeing why encryption status would matter. @simms22
Sent from my Nexus 7 using Tapatalk

H4X0R46 said:
Alright guys! So I was told false information hahahaha nice banana analogy. So flashing an unencrypted kernel means I can retain my data? The forced encryption doesn't cause any extra complications?
Click to expand...
Click to collapse
to unencrypt, you not only have to flash the kernel, but you have to format your storage as well. that completely delete everything. thats a one time deal though. those kernels actually give you an option, you can stay encrypted or you could decrypt. if you flash other custom kerneks, theyll give you the same option. from that point on, you could just flash. or flash your rom , and kernel. but you you flash a kernel that doesnt give you that option, itll encrypt you again.
---------- Post added at 11:29 PM ---------- Previous post was at 11:13 PM ----------
713brianp27 said:
Oh yeah I deal with selinux in repos. I just add the cmdline, but I was just using that as an analogy referring to encryption on kernel. Not seeing why encryption status would matter. @simms22
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
my bad
i thought you were asking about it :angel:

When you mentioned app, I was lost. Google's encrypting apps. Guess I should a role a fruit rectum combo. Its a fine line simms. You can flash unencrypted w/o wiping or anything. But you'll still be encrypted until you "fastboot format user data.img". I decrypted twice first on fastboot, then tried the twrp format and it worked.
Sent from my Nexus 6 using Tapatalk

Alright, so basically you have to wipe when you first install an unencrypted kernel, but you don't have to wipe again when installing the stock encrypted kernel? This post is going so many random ways, from butt wiping to getting your daily intake of vitamins hahahaha
Sent from my Nexus 6

H4X0R46 said:
Alright, so basically you have to wipe when you first install an unencrypted kernel, but you don't have to wipe again when installing the stock encrypted kernel? This post is going so many random ways, from butt wiping to getting your daily intake of vitamins hahahaha
Sent from my Nexus 6
Click to expand...
Click to collapse
Yeah , sorry we were going off topic in your thread. Lol
Once your unencrypted your good. No erasing data. I only did it twice because I needed to check a feature on cm as were cm based and they still had boot encryption. Should of known better. 1 time format data and install any kernel thats not force encryption

713brianp27 said:
Yeah , sorry we were going off topic in your thread. Lol
Once your unencrypted your good. No erasing data. I only did it twice because I needed to check a feature on cm as were cm based and they still had boot encryption. Should of known better. 1 time format data and install any kernel thats not force encryption
Click to expand...
Click to collapse
Nah you guys are all good haha a good laugh is needed sometimes xD Alright! Are most or all custom kernels unencrypted? And is a full wipe needed to go back to stock kernel? Thanks guys! You're a big help lol

H4X0R46 said:
Nah you guys are all good haha a good laugh is needed sometimes xD Alright! Are most or all custom kernels unencrypted? And is a full wipe needed to go back to stock kernel? Thanks guys! You're a big help lol
Click to expand...
Click to collapse
Yes most are. Saw 1 "Starship" not yet unencrypted. Yes you flash back to stock but upon reboot your data will get encrypted

hey, so, I am on hells-core kernel right now, and It still says that I am decrypted. Can someone help me out with this? I have not wiped anything since I unlocked the bootloader. Do I need to wipe everything to have it decrypted? please help because I have no idea why its not unencrypting it.

royredman said:
hey, so, I am on hells-core kernel right now, and It still says that I am decrypted. Can someone help me out with this? I have not wiped anything since I unlocked the bootloader. Do I need to wipe everything to have it decrypted? please help because I have no idea why its not unencrypting it.
Click to expand...
Click to collapse
you need to format your userdata to decrypt, after flashing a kernel that allows it. you can use fastboot to do it, fastboot format user data.img. or you can do it with twrp recovery. it will delete everything in your storage.

Thanks everyone! You guys are awesome!
EDIT: This may be a stupid question, but you can't be too damn careful with kernels haha anyways, are custom kernels at all specific to a certain build? Or is it cool to flash a custom kernel without worrying about the build too much? And worst case scenario, you can just fastboot flash the stock if it just doesn't work?

H4X0R46 said:
Thanks everyone! You guys are awesome!
EDIT: This may be a stupid question, but you can't be too damn careful with kernels haha anyways, are custom kernels at all specific to a certain build? Or is it cool to flash a custom kernel without worrying about the build too much? And worst case scenario, you can just fastboot flash the stock if it just doesn't work?
Click to expand...
Click to collapse
Build meaning Roms correlated Android version. Yes they are specific. For ex an easy one is ElementalX , his site will list device- and version . kernel for 5.1.1 kernel for 6.0 and such. Visit his xda under original android development. You'll see how it works version wise.
Sent from my Nexus 6 using Tapatalk

H4X0R46 said:
Thanks everyone! You guys are awesome!
EDIT: This may be a stupid question, but you can't be too damn careful with kernels haha anyways, are custom kernels at all specific to a certain build? Or is it cool to flash a custom kernel without worrying about the build too much? And worst case scenario, you can just fastboot flash the stock if it just doesn't work?
Click to expand...
Click to collapse
It' s all about Android version. Generally, you should only use a 5.0 kernel on a 5.0 build, or a 5.1 kernel on 5.1, however, there aren't many kernel changes between 5.1.1 and 6.0, so you can actually use a 6.0 kernel without any issues on 5.11 - though you shouldn't go backwards and use a 5.1.1 kernel on 6.0

Per Android version yea, I figured. But they aren't specific as to like, only works with MRA48k or only works with LMY48I or something? And worst case scenario, can a kernel leave your device in a hard brick if it's at least for your device?
Sent from my Nexus 6

Strange issue.

Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.

H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
You flashed Npreview radio on a marshmallow build?

Dead-neM said:
You flashed Npreview radio on a marshmallow build?
Click to expand...
Click to collapse
Yes! Yes I did. Could this be an issue?

H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
H4X0R46 said:
Hey guys! So this is a very strange issue. When I power off my nexus, a lot of times I have to wait a good 30 seconds or so before I can power it back on or go into the bootloader. If I power it off, and try to turn it back on fast, it stays black screen almost as of it's frozen or just not responding. I noticed this issue begun when I flashed the radio from N preview 2, and didn't happen before that. My question here, is what could this be? Can the radio really cause odd things like this to happen? Or is there another cause? I am running the newest Android version MOB30I, and have multirom installed with about 4 or so secondaries.
Click to expand...
Click to collapse
im going to guess, try a different kernel. as its the kernel that will boot up the device?

H4X0R46 said:
Yes! Yes I did. Could this be an issue?
Click to expand...
Click to collapse
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)

Dead-neM said:
Yes it can. Why did you do that?
Make a backup (android or titatium backup)
Then reflash stock n6 firmware (erase data so put your backup and important files into pc)
Click to expand...
Click to collapse
the N radio, is the same exact radio that google released for the may security patch. so the N radio, is the latest official radio for the nexus 6. so no, that wont be the problem.

simms22 said:
no. as im using the n preview radio on marshmallow, which is the same radio that came out with the last security update.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
I wonder if it is. I'm using the newest Elite kernel for Marshmallow, it's always been my go to kernel. It's strange because after turning the device off, I can't turn it back on instantly, screen stays black as if it's not 100% shut down yet. I have to wait a bit before turning it back on, or entering the bootloader.

simms22 said:
im going to guess, try a different kernel. as its the kernel that will boot up the device?
Click to expand...
Click to collapse
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.

Yoinx said:
No, it's the bootloader that boots the device.
If he's hitting the power button and unable to get to the "Google" splash screen or the bootloader, the kernel is very irrelevant.
I'd be more curious if he's trying to use the bootloader from the N-Preview 2 with MM. Even though I think it's supposed to be backwards compatible, the bootloader is the only thing that would cause that sort of issue.
*technically* I'm pretty sure that you could format /boot (where the kernel is stored) and still get to your bootloader for fastboot and such. So, the kernel is really irrelevant until after the bootloader does it's thing.
*edit*
also, there's a reason that these are known as "Developer Previews" not "End-User Previews"... If you don't know how to fix weird issues that pop up like that, you should probably avoid them.
Click to expand...
Click to collapse
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?

Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.

Yoinx said:
It can be. Normally, once you upgrade, you just stick with the new one as they're backwards compatible normally. But, the ones for the Previews aren't always 100%. The whole reason these previews come out is so that developers can start making their apps compatible prior to the official release. Ideally, this is supposed to be done in emulators not necessarily real devices.
If the 30 second delay in powering back on is *that* big of a deal (to him) to risk bricking the phone by downgrading the bootloader and having something go wrong... I say go for it.
Click to expand...
Click to collapse
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.

Dead-neM said:
Mmm yes after what said simms22 I've check the n preview and the bootloader is xxx.18 instead of last mm which is xxx.17 but a bootloader downgrade is risky right?
@H4X0R46 do you use the .sh file and update your bootloader and radio with n preview?
Click to expand...
Click to collapse
I flash each partition manually.

H4X0R46 said:
Is downgrading the bootloader really risky? I've done it before without issue and never knew this was risky! Are you supposed to just stay with the newest bootloader if you already flashed it? I always flash the bootloader for the image I'm flashing, even if I'm downgrading.
Click to expand...
Click to collapse
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.

Yoinx said:
It's always risky when you're messing with essentially the lowest level software on the device. For instance, lets say that something happens while you're flashing the bootloader and it corrupts. What do you use to reflash it? You can't get to fastboot anymore...
As long as you know what you're doing, don't have corrupt images, and don't lose power or have lightning strike your computer while you're doing it, you would be fine.
The issue is that many/most people on XDA these days have no idea how to recover from problems or even what problems the things that they're doing might cause. So I tend to approach every situation under the assumption that the other poster may not have a full understanding.
No offense intended of course.
Click to expand...
Click to collapse
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe

H4X0R46 said:
Alright so that's just to be safe then? My laptop sometimes freezes solid out of the blue, uncommon but does happen, and I always thought "what if I'm flashing stuff?" Scary thought. ESPECIALLY the bootloader! So the danger you're referring to is flashing a bootloader in general, not so much downgrading? Like I said, I always match the bootloader to the version I'm running. This is okay?
EDIT: I ALWAYS ALWAYS ALWAYS check the MD5 checksum for EVERYTHING before flashing. Can never be too safe
Click to expand...
Click to collapse
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).

Yoinx said:
In general, the bootloader needs to match the highest version of android you intend to run. They're typically always backward compatible. On some phones, you can't downgrade the bootloader (at least not easily). This phone you should be fine doing so. However, there's not usually any reason to (backwards compatible afterall).
Click to expand...
Click to collapse
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol

H4X0R46 said:
Cool! Thanks for your input on that! Much appreciated! Yea I'm always wary of the bootloader because like you said, it IS the lowest software on the device. Quick question, if that were to get corrupted, does the device just not boot resulting in permanent brick? Or does it boot just no fastboot access? Might be a noob question, but why not ask lol
Click to expand...
Click to collapse
Depends, I've never really looked into unbricking this phone. Never had to yet.
Depending on the phone you can use tools like QHUSB and similar which let you reflash partitions just through the USB connection.

I know it's late but it could also be just the rom setup. I know a while ago there were commits that shut the device screen and buttons off before it was done shutting down (to make it appear faster) this made devices seem bricked for a short period. I don't know what ever happen to those commits, so I can't say for sure that it is them. But your issue fits perfectly.

So have I been flashing the bootloader wrong all along? I flashed in twrp a couple times but I try to flash them individually and wipe after flashing.
Sent from my Nexus 6 using XDA-Developers mobile app

Anybody able to find out why? I'm surprised to see I'm not the only one having this issue, it's annoying really.