yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] mwebb34:
I flashed 2 things the radio and bootloader and my device wouldn't reboot, so there is something I'm not doing right....I'm on 5.1.1 and I wanna update to 6.0.1. Would I be better off using wugs toolkit to unroot and flash stock then just take the OTA?

---------- Post added at 05:00 PM ---------- Previous post was at 04:30 PM ----------

Well iv tried and failed of course... This crap is very tedious and its starting to give me a head ache. In order for me to get this going I'm gonna need step by step or maybe a video guide. 1 person says to flash just the bootloader and radio then flash a custom rom and then reboot and all is done. Didn't work for me unless I done it wrong. Anyways all I wanna do is be on 6.0.1 w/root I'm currently on 5.1.1 w/root.
[Nexus 6 Android Development] force70:
Given the difficulty you have had thus far on this device and amount of posts over numerous threads requesting help to fix things i would say yes probably a good idea.

Being sincere here not trying to be an ass it just seems you have had alot of trouble with the thing and Id like to see you have an easier time getting it updated and running well. Its never fun when you spend more time fixing issues on your device than using it!

Sent from my Nexus 6P, Note 5, Note 4 or Nexus 6
[Nexus 6 Android Development] Nergal di Cuthah:
I agree, also (since you state you have been given multiple different advices) I would again, for the second time, beg you to open a thread in your device's board, and keep your entire experience to that one thread and not to multiple threads and helpers; at least 2 of my subscribed threads have been FLOODED by your issue(s). This does not allow you to get proper aid and definitely detracts from the subject of those threads. Neither are general "I'm going to ask every question about rooting" threads. One is a How-to thread and the other specifically deals with bugs in Wug's (hee hee rhyme); you don't have a Wug Issue you have a something went wrong somewhere in the steps you "followed" issue.
[Nexus 6 Android Development] TonikJDK:
I agree, this is not the place for this. Time to fire up your own thread and keep it all there. You will probably get more helpers that way also.
[Nexus 6 Android Development] mwebb34:
OK guys chill out I'm done, don't worry about me ever posting here. Im sorry for pissing you off so bad I feel absolutely humiliated. Thanks again for the help.
[Nexus 6 Android Development] HipKat:
You mean the 10 pages of people helping you and repeating themselves over and over?
[Nexus 6 Android Development] gee2012:
Learn the essentials needed for flashing/fastboot/adb/etc/etc, read the stickies thread in the General forum http://xdaforums.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066 . Its hard to help somebody without even the basic knowledge/skills and experience.
[Nexus 6 Android Development] mwebb34:
Why are you keeping this going, I clearly said IM DONE there is no point in saying anything else,period. So if you don't mind keep you're opinion to yourself.
[Nexus 6 Android Development] srothkin:
Working fine for me so far. Using stock 6.0.1 rooted, I tested with a my Sennheiser MM550 headphones (both music and phone call) and my 2008 Prius (phone call only). All worked as expected/no problems.

Even the different Tasker profiles that launch on connection of each of these devices worked properly.
[Nexus 6 Android Development] Philip:
I've also got stock 6.0.1 rooted and also have no Bluetooth problems. Using a Bluedio TS2 headset to make calls.
[Nexus 6 Android Development] MahoVader:
Thanks guys. I'm sure I just need a fresh install to fix my Bluetooth issue. Will have to wait for the weekend!
[Nexus 6 Android Development] baikal2:
Unlocked and rooted and installed TWRP. The TWRP did not stick for whatever reason. Had to go into NRT advanced and flash recovery again. The second time around the TWRP stuck.

Also got an backup. A little tip to an future beginners coming down this way. When you go into TWRP and about to create a backup , do not select the system image for backup. Even if you do, do not select that on the restore . The TWRP will abort midway of the restore . Lost a few hours because of that.
[Nexus 6 Android Development] rajat339:
After rooting and instaling TWRP, my device is not booting, it is giving error "your device is corrupt.It cant be trusted and may not work properly"

Please help
[Nexus 6 Android Development] fkfmfz:
I always have to flash root 2x for it to stick.

---------- Post added at 08:00 AM ---------- Previous post was at 07:36 AM ----------

I try to restore lastnite but got a quickboot mismatch and keeps failing. I try to check for updates also reinstalled the toolkit same result. Still got it to root by manually rebooting.
[Nexus 6 Android Development] HipKat:
Flash a custom kernel, like Franco or elemental in recovery.
[Nexus 6 Android Development] grgana:
Got to admit, after unlocking & rooting my previous N4/N5...

im scared to do it with new N6 it's completely stock,

ota updated from ,lollipop 5.0 to MRA58K with 6.0.1 ota ready on device to installed,

The last few pages freaked me out + that red warning "corrupted device"

I regret a little to not stopped on lollipop to unlock & root, from what i understand it was easier.

But i know my self and not gonna be able to discipline my self from custom roms much longer. :banghead:

I read much..but still if any good suggestion how to avoid bootlops and corrupted device are more than welcom..

should i go for 6.0.1 and then unlock and root or better stay on 6.0.0? :what:
[Nexus 6 Android Development] Alxoom33:
Yes, just read up first. It's easy!
[Nexus 6 Android Development] Philip:
It's just a warning message, which you can choose to ignore without it having any effect whatsoever, so there's absolutely no reason to be "freaked out" about it.

Only you can answer that - why do you want to root your device? What features of 6.0.1 do you want over 6? Are the risks worth the benefits to you?
[Nexus 6 Android Development] grgana:
From what i understood, you cant boot device if you get corrupted message with "this device can't be trusted" maybe i got it wrong?

I want features that usually custom roms are packing, DU or Aicp..like material dark background((CMTE)and more customization options, and decryption for better perfomance...

Sorry for bad English, but question was more like is it easier to root 6.0 over 6.0.1 or no diffrence at all..(i suppose there is no but still)..
[Nexus 6 Android Development] Alxoom33:
Flashing most custom roms and kernels get rid of that message from Google.
[Nexus 6 Android Development] srothkin:
If you're on Marshmallow, you need to follow chainfire's systemless root (see earlier notes on this thread) and DO NOT allow TWRP to install root on exit (doing so will prevent boot).

The "your device is corrupt" is going to happen on any marshmallow device that has been rooted or has a custom recovery. But with the systemless root it should not prevent proper operation.

---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------

The warning starts with 6.0.0. It's a new Android "feature" and its to be expected when you root and/or install a custom recovery.

To avoid bootloops, follow the instructions for systemless root following chainfire's method.
[Nexus 6 Android Development] Long Island NOOBIE:
MMB29S

Factory image update available for Nexus 6: 6.0.1 (MMB29S). Can be flashed with NRT.

https://developers.google.com/androi...s/images?hl=en
[Nexus 6 Android Development] Stryder52:
Two options, I believe.

1) Wait for the toolkit to be updated

2) Download and flash stock + unroot using NRT, just select "Other/Browse" Screenshot below.
[Nexus 6 Android Development] Long Island NOOBIE:
Correct on both options, except under 'CHOICE' in screenshot click on:

"I downloaded a factory image myself that I would like to use instead".

That's only if you are willing to try out update before WugFresh updates NRT.
[Nexus 6 Android Development] stupidchicken03:
Ive browsed the last 3 or so pages.

I havnt used the NRT since 5.1.1 was still fresh. So im still running 5.1.1 with root.

From what im gathering, root is not working thru the NRT on 6.0.1?
[Nexus 6 Android Development] Alxoom33:
No, Root has been working perfectly since 6.0!!!
[Nexus 6 Android Development] TonikJDK:
It worked, just a tad more work

That said, I noticed yesterday NRT updated with the new systemless root. I didnt look further yet....waiting for it to update with yesterdays google update....but if it is using systemless now it will work. I suspect there is an advance option to use systemless now

But this is the way to be sure for now:

Flash with the toolkit. No wipe and force checked.

Use toolkit to flash twrp.

Manually copy sytemless root 2.66 to !readytoflash folder on the phone.

Reboot into twrp and select install. Install the 2.66 zip. NOTHING else.

When you exit twrp it will offer to root. Say NO.

Thats it. Been doing it that way for some time now.
[Nexus 6 Android Development] stupidchicken03:
Im guessing the path is

!readytoflash - Root_Files - .zip file

in that current location I have - UPDATE-SuperSU-v2.46.zip. Should I delete that zip, or doesnt matter as long as I dont select it?

I would REALLY prefer to not have to wipe all the data from my phone (pics/txt/settings/ect), I know from going to 5.0 to 5.1.1 I did a "dirty flash" or whatever the name is to update. Can I do the same going to 6.0.1?
[Nexus 6 Android Development] TonikJDK:
I would delete anything in there just to avoid a mistake.

The no wipe option will save your data. BUT going to 6 most of us hit a bootloop and had to boot into recovery and wipe data.

So copy off the important stuff first.
[Nexus 6 Android Development] Philip:
There is nothing magical about the path or the file - you can place the ZIP in any directory on your device and navigate within TWRP to flash it. And there is no issue with having old versions of the SuperSU ZIP file around - other than the (small) amount of disk space that it takes up, and the risk that you might accidentally flash an older version rather than the latest one.
[Nexus 6 Android Development] Long Island NOOBIE:
TonikJDK's instructions were on the money!

{ Flash with the toolkit.

No wipe and force checked.

Use toolkit to flash TWRP.

Manually copy sytemless root 2.66 to !Readytoflash! folder on the phone.

Reboot into TWRP and select install.

Install the 2.66 zip.

NOTHING else.

When you exit TWRP it will offer to root.

Say NO. }

I downloaded Busy-Box Pro from the Google Play Store plus the rest of my rooted apps and was back in business. Thank you very kindly.
[Nexus 6 Android Development] Stryder52:
Did you flash perm-recovery-signed.zip when flashing TWRP? I'm guess not, but wanted to ask.

Thanks!
[Nexus 6 Android Development] Long Island NOOBIE:
Just the SuperSu 2.66 zip out of the iReadytoflash! folder. Hope I clarified my answer for your benefit.
[Nexus 6 Android Development] TonikJDK:
No. JUST 2.66, the other stuff is for the old root system.
[Nexus 6 Android Development] mwebb34:
Just wondering something. Should I relock my bootloader? If I do relock will I still be able to flash custom ROMs I won't be able to flash kernels correct? Am I more vulnerable to outside threats, or does being unlocked really matter? Thanks
[Nexus 6 Android Development] Prack:
No it is not recommended to re-lock your bootloader unless you are selling/returning the device. You are not any less secure by having your bootloader unlocked. Think of it as a developer option being enabled. Just leave it the way it is.
[Nexus 6 Android Development] cybertec69:
I am unlocked and rooted, Nexus 6, also loaded the last update by Google using NRT.
[Nexus 6 Android Development] TonikJDK:
Do not relock. If it freaks out and you are locked you are screwed, you probably wont be able to reflash. And no, if it is locked you cant flash roms until it is unlocked.

There is a very minor loss of security being unlocked. But only if you physically lose your phone. And if you lose your phone and they really want in, they will get in. So dont worry about it.
[Nexus 6 Android Development] HipKat:
Unlocked bootloader will not open you up to outside threats and really, what outside threats are there?? I've never used anything to secure my phones from these outside threats and have never had any issues
[Nexus 6 Android Development] Long Island NOOBIE:
Two interesting threads pertaining to your question:

http://xdaforums.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497

http://xdaforums.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
[Nexus 6 Android Development] stupidchicken03:
So yesterday I was able to do exactly what was said to do. Used the su2.66 for root in TWRP.

Im now on 6.0.1 and it says im rooted via Root Checker Basic app.

But Im having an issue. I have tried via ES File Explorer and Solid Explorer to move a file from one folder (storage - portal - FileX) to another (root - system - fonts - Move here) and I cant do it.

Then with the AdAway app, I open it, it asks for root permission then I grant it. It pops up with an error "Either the su binary could not be found or you did not allow root permission".

Any thoughts or other way to verify root?
[Nexus 6 Android Development] lngwca:
Forgive me if you've already done this. But in the file explorer app you have to give it the permissions in the menu left side all the way down at the bottom there should be a root explorer button
[Nexus 6 Android Development] TonikJDK:
Or you dont have space on your system partition. You have to delete a couple off apps, like google apps so there is space. You can add them back in from the store and the will go to user.

Reboot into twrp. And mount system in read and delete them with twrp file explorer.
[Nexus 6 Android Development] stupidchicken03:
I looked in both ES File Explorer and Solid Explorer. Didn't see anything obvious for extra permission.

This screenshot is from ES scrolled all the way to the bottom.
[Nexus 6 Android Development] lngwca:
Yes where it says " root explorer". When you click this it should ask for root permissions. Like a superSU pop up. Did it pop up and you grant the root permission?
[Nexus 6 Android Development] stupidchicken03:
I think I might have to do this.

See the second screenshot

Yes it had.

So I just removed permission from ES, and closed it. Reopened and it asked for root permission as shown.

Now I'm getting this pop up saying full.. So looks like I have to clear some space in the system folder.

How big is that partition? I know I have something like 9GB free, at least as storage is concerned.
[Nexus 6 Android Development] NOSTALGIA:
this is how it looks on my end
[Nexus 6 Android Development] Nergal di Cuthah:
Which brings up the question I was going to poise.

How much space in your system partition.

The system is small partition separate from the device's size as you are understanding it. It's probably full depending on your device. For instance the N6 is full after Marshmallow, and requires a user to move/delete/uninstall system apps; suggestions for this include keyboard languages you don't use or Google Apps, such as hangouts or youtube, which can be installed via Play Store.
[Nexus 6 Android Development] stupidchicken03:
That indeed was an issue! I had 4KB free lol... Cleaned out some non-used apps and now have 181.21 MB free.

Time to try again.
[Nexus 6 Android Development] stupidchicken03:
Something still isn't happy.

Before the error was not enough space, now it's this: permission denied.

ES has root access. Not sure why its throwing a fit.
[Nexus 6 Android Development] stupidchicken03:
Ok... well I think the full root partition was my whole issue from the get go. An app I used to switch to Samsung emojis, was not working after the 6.0.1 update... So I found a .ttf file I could manually swap in.

Downloaded file in storage and just needed to move it to the root - font folder.

Cant manually do it, for whatever reason, due to "permission denied" as seen in my last screen shot.

Well on my way home from dinner... it dawned on me.. maybe the emoji app didnt work because the system root was full... So I tried it again and it worked hahahha...

So my journey thru all that came to an end. Seriously thank you for those who chimed in and led me to the not so obvious answer! Gave you all some thanks ;)
[Nexus 6 Android Development] Long Island NOOBIE:
HEADS UP !

Wug's NRT updated to v2.1.1.
[Nexus 6 Android Development] Oniska:
When trying unlock. it just says "encrypted" ?
[Nexus 6 Android Development] grgana:
So its better to not update NRT ? for now im preparing fot unlocking & root
[Nexus 6 Android Development] armored:
Same here. Any ideas?
[Nexus 6 Android Development] Oniska:
Don't update. 2.1.1 has a lot of bugs.
[Nexus 6 Android Development] Prack:
I just used it to go to the latest version and had no issues whats so ever.
[Nexus 6 Android Development] grgana:
Did you flash new image or use OEM unlock..

I never ulocked bootloader on my N6 so im encrypted..and thats the error is what updated NRT is reporting while unlocking..
[Nexus 6 Android Development] Prack:
I was unencrypted, unlocked and on 6.0.1, I just did no wipe, no encrypt, force flash, and then after it was done re-rooted and installed recovery. Everything I did was working like it always does.
[Nexus 6 Android Development] grgana:
Glad for you but error appears to happennig when unlocking BL..other functions are maybe fine
[Nexus 6 Android Development] Oniska:
Agree. You need to use 2.1.0 to unlock and the rest use 2.1.1. Rooting is also easier now.
[Nexus 6 Android Development] Long Island NOOBIE:
v2.1.3

Wug's NRT updated again!

NRT v2.1.4 update: January 16th, 2016
[Nexus 6 Android Development] cybertec69:
I already installed the update, and loaded the recent Google build for my Nexus 6, manually downloaded it using NRT
[Nexus 6 Android Development] justibasa:
A little off topic, if your following the Ground Zero Roms community on g+, don't mention or recommend nrt as it is now a bannable offense. How do I know, cause I recommended it and am now banned. What a great bunch of people, right? Just thought I should give fair warning if you don't want to get banned from that community.
[Nexus 6 Android Development] Alxoom33:
Why is it a bannable offense to mention NRT?
[Nexus 6 Android Development] justibasa:
I guess cause they don't like people in their community using toolkits.
[Nexus 6 Android Development] Alxoom33:
Yes,obviously, but why?
[Nexus 6 Android Development] wtherrell:
Anal Retentive Luddites.
[Nexus 6 Android Development] grgana:
What about new update now i see there is 2.1.4 version of NRT available.. Anybody used it..?

(Is bug your "device is encrypted" gone?)
[Nexus 6 Android Development] disiz:
Thanks a lot for this ! I've just root my Nexus 6 with your tool 2.1.4., and all those helps between commands are very usefull :)

Now my Nexus 6 is rooted and is ready for ROMs :)

Thanks.
[Nexus 6 Android Development] Philip:
Why not read the Changelog?

http://www.wugfresh.com/nrt/changelog/
[Nexus 6 Android Development] grgana:
I did.. But still hasitating, since i have very limited amount of free time, in case somenthing goes wrong, to fix it up..

Btw..I know its selfish to ask for confimation..sorry
[Nexus 6 Android Development] Brian706:
Just used 2.14 to upgrade to the latest factory image and root with the no force encrypt option checked. I didn't see any errors/bugs and my device remains unencrypted.
[Nexus 6 Android Development] grgana:
Error was present when trying to unlock bootloader , but thanks for info, it seems that its has been fixed by the last update
[Nexus 6 Android Development] Brian706:
Oh, okay. I wasn't familiar with that error as I normally just do everything manually but I can't keep track of which files I need these days as things are changing too much so I decided to use this, which was nice!

My bootloader was already unlocked so I can't comment on that portion of the toolkit. :)
[Nexus 6 Android Development] LupineDream:
Your torrent is being seeded, good sir! Thank you so much for this contribution, and for including my Motorola variant! I see that it is new in the recent update! :)
[Nexus 6 Android Development] tsalate:
A few devs are more traditional and always insist on knowing how to use fastboot and adb. Which I agree it is very important to know in case something goes awry with your toolkit set up. But I use wug many times. But every so every so often I flash everything manually just to stay sharp.
[Nexus 6 Android Development] darklordofthesith:
Can I just root and install custom recovery even if my phone is encrypted? Just using the NRT?
[Nexus 6 Android Development] TonikJDK:
Yes, that's all I do. Unlock the bootloader on the phone in developer options. Then unlock in the tool, flash twrp.

Then copy over chainfires systemless root 2.66 into the !readyto flash folder, boot into twrp and flash 2.66. Ignore the other files twrp put in there. And say NO when twrp offers to root your phone.
[Nexus 6 Android Development] Nergal di Cuthah:
not sure the last paragraph is needed,NRT now uses that version for root if you tell it to.
[Nexus 6 Android Development] TonikJDK:
Good to know, thanks. I have not had to reflash in awhile.
[Nexus 6 Android Development] darklordofthesith:
I'm not new to this stuff but new to an encrypted phone. Since my nexus 5 died, I moved to the 6. But wasn't sure if I needed a different kernel or anything.

---------- Post added at 02:21 PM ---------- Previous post was at 02:19 PM ----------

I was just going to go regular root since system less isn't fully perfected yef
[Nexus 6 Android Development] Pecata:
New Factory image for Nexus 6P is up https://developers.google.com/android/nexus/images?hl=en version MMB29Q includes the February security patches.
[Nexus 6 Android Development] hdtechk:
It's already up for N6 and flashed to my N6 thanks to NRT
[Nexus 6 Android Development] Philip:
Likewise.

Am I alone in thinking that it's only in Google's world where version MMB29

Q

can be a later version than MMB29

S

?!
[Nexus 6 Android Development] hdtechk:
I was thinking same
[Nexus 6 Android Development] Alxoom33:
Somethings wrong!
[Nexus 6 Android Development] cyberon:
While rooting the app is not detecting the device after entering twrp, i have to try again after twrp has fully started, and then it works. Anyone else having this issue?
[Nexus 6 Android Development] Nergal di Cuthah:
I kinda had an issue like this, but it was resolved by waiting for the teamwin splash screen to go away and then clicking the prompt from wug's that allows retry.

Perhaps it's the same issue. Seems wug's needs to wait a second or so longer than before in order for twrp to finish booting
[Nexus 6 Android Development] cyberon:
Yep, that's exactly what happened to me.
[Nexus 6 Android Development] NOSTALGIA:
just a question.. if you are to update to the newest firmware are you flashing only the img file will it keep your apps??
[Nexus 6 Android Development] TonikJDK:
When you flash with the toolkit you select the No Wipe option. Those options show up after you select Flash to stock button.
[Nexus 6 Android Development] smclaughlin3:
Is the unencrypted boot image up for the q build?
[Nexus 6 Android Development] klone96:
so no MMB29S ? Really hate not having a rooted phone
[Nexus 6 Android Development] NOSTALGIA:
already up. used the toolkit and im unencrypted
[Nexus 6 Android Development] cybertec69:
I just updated to the latest image security patch, device unlocked and rooted, never had an issue before modifying build.prop , I do this for the tethering option on my Nexus 6 , net.tethering.noprovisioning=true, when I choose yes to modify the build.prop, I get this message failed saving build.prop, then it erases the whole build.prop on the device. What gives. I then have to reinstall the whole image all over again.

Also HD calling no longer works, can not activate simultaneous data/calling feature, which worked before, what the heck is going on. I am on Verizon. Nexus is non Verizon. Those two features worked just fine with the previous image build from Google.