yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] kipperfish:
I have worked around this by installing TWRP and then using it's rooting solution.
[Nexus 6  General] SscoootzZ:
Clarify please... and excuse my n00bity...

So just to be clear, this method would work on Verizon retail versions of the Nexus 6? I apologize if the build #'s you referred to reveal that answer, it's just that I'm not experienced enough to pick out that detail.

Thanks in advance and thanks for your reply,

Scott :confused:
[Nexus 6  General] JavaTiggy:
Your build number is indicated within the About Phone section in Settings. The "retail" version that Verizon sells is no different from the one you can get from google except for the fact that the SIM card was pre-installed for you.

Edit: This method works on 5.0 LRX21O, 5.0.1 LRX22C and all 3 revisions of 5.1 that I mentioned LMY47D, LMY47E and LMY47I.

Just a word of advice...read, read and read some more. If this stuff is already getting you worried I highly recommend that rooting or flashing is probably not for you. And if you insist, the search tools of this forum and google are your friend. It is how I learned and I'm sure how most of the guys or gals on here have as well.

Just my $.02, take it or leave it. By no means am I trying to be mean, just honest.

The Tig using Tapatalk
[Nexus 6  General] SscoootzZ:
Thanks Tig ^_^

:good:

Thanks for taking the time to reply. Your insight is useful and appreciated, and nothing you shared felt mean, IMHO. I am getting used to reading a lot, since I'm not prone to successful troubleshooting on my own. When it comes to being certain about root, I will definitely heed your advice. The root community is, I've found, generally very supportive and the members provide solid advice and guidance. The Moto DroidX was the first device I successfully followed rooting instructions with. I held on to root on the DX through trying out many ROM and encountering many soft-bricks in the process. My Note3 was a tad less worrisome, though I've chosen to sort of "set-it-and-forget-it" once I gained root.

I really enjoy the Note3 but I'm fiscally bound to retail versions (vs dev editions), and Note4 root for the retail edition may not manifest. Also, I'm not currently willing to step out of VZW due to how coverage considerations affect my job. Therefore I'm looking at other devices, and am interested in the Nexus 6. On the Note4 forums, the threads are very specific about retail vs dev edition in regards to rooting. Best I understand, this is because the dev edition bootloader is not locked down on VZW. I'm guessing that, based on your info, the Nexus 6 threads are not separated because the bootloader isn't locked down on VZW. If that's accurate, then I'm relieved and I think I've chosen my new device. However, if I do an early trade, I'll have to turn over my Note3. Ugh...decisions, decisions.

So, again, thank you very much for your time and insight. You've given me something to think about as well as some hope. Have a great day.

:victory: Scott
[Nexus 6  General] indianajonze:
i take it this still doesn't work on M yet, correct?
[Nexus 6  General] ilanad:
will this work on LYZ28E (TMobile 5.1.1)????
[Nexus 6  General] teinwhite:
Yes. It works for T-Mo 5.1.1
[Nexus 6  General] u4atharva:
It says on chainfires website that it's for 5.0.

What about 5.1?

I'm currently on 5.0.1. I wanna upgrade to 5.1.

How do I go about it??
[Nexus 6  General] stupidchicken03:
Im on Google Fi and got prompted today for an update to 5.1.1

Ive already ran the CF-auto-root when I got the phone. So im currently unlocked and rooted. With previous phones on Verizon, whenever they pushed out an update, I needed to protect my root with an app (rootkeeper or something similar), update and then re-enable root.

Question I have, do I still need to do that? Or would I be fine just installing the update?

Thanks
[Nexus 6  General] :
Since the implementation of lollipop, absolutely NO system, recovery, or kernel changes can be present to install an OTA. Flashing a system and boot image from a factory image is the ONLY way to successfully remove altered files.

That being said, if you're unlocked, just download the factory image for the OTA you want, unzip twice and extract the bootloader, radio, system, boot, recovery, cache, and userdata images. Flash everything but userdata individually with fastboot and you'll be updated without data loss.

Or, there's a thread in Android development section, titled FXZ, in the OP, there are recovery flashable zips that will get you updated as well. :)
[Nexus 6  General] stupidchicken03:
Good to know and a bit of a PITA lol.

I did not realize (when I first got the Nexus) that it was a bit backwards from other Androids ive had previously where you need to unlock first then root (for me it had always been root then unlock) and it wipes everything out. So I had my phone all set up with my launcher/apps/settings ect and then cleared everything to unlock/root.

Now a week later Ill have to do it again lol
[Nexus 6  General] knives of ice:
how do you install TWRP after successfully rooting then?
[Nexus 6  General] JavaTiggy:
I believe you still can you just have to flash the stock recovery back on for updates.

The Tig using Tapatalk
[Nexus 6  General] saman0suke1:
Does it work for LMY48I? Thanks!
[Nexus 6  General] JavaTiggy:
It sure does!

The Tig using Tapatalk
[Nexus 6  General] JulesJam:
Is this the only way to root the Nexus 6 running 5.1.1?
[Nexus 6  General] mSergiy:
unroot cf-root ?

Is there an easy way to unroot cf-root (without flashing the factory image)? I was thinking about flashing boot and system... Will it help?

Thanks!
[Nexus 6  General] Jiggs82:
Hey i have a nexus 6 running 5.1.1 and the dwnload for 5.0 doesnt work is there a 5.1.1 cf auto root version or am i doing something wrong? thanks
[Nexus 6  General] JavaTiggy:
No there are some toolkits like wugs that do the trick as well.

Not that I am aware of, I'm not sure if anyone else can chime in. As for manually you could just do the normal flash steps for keeping user data it is just a bit long winded.

What actual version of 5.1.1 are you on? It has worked every time for me, maybe you just got a corrupt download of it.

The Tig using Tapatalk
[Nexus 6  General] Jiggs82:
Disregard that I ended up using NRT root toolkit but thanks :)
[Nexus 6  General] JavaTiggy:
So i am just curious if anyone has had the opportunity to try this on marshmallow yet?
[Nexus 6  General] 92slammer:
Try it and let us know
[Nexus 6  General] JavaTiggy:
I will most likely give this a go this week when I have some time and I will report back
[Nexus 6  General] billygoat32:
From my understanding the process is different due to substantial changes in the architecture - not sure if it will work, but I'd be interested in your results.
[Nexus 6  General] TheSlipperMan:
It doesn't work on Marshmallow, it wouldn't boot. It shows the red triangle and says your device maybe corrupt, then the screen goes black, I left it for 5 mins or so but nothing.
[Nexus 6  General] 92slammer:
follow this guide to root! http://androiding.how/how-to-root-marshmallow-on-nexus-5-6/ i did it through nexus root toolbox. now have twrp, root ..no issues
[Nexus 6  General] Jayracer7474:
what did u do to get it to boot, I think my wug toolkit did something stupid and I have the same triangle u got
[Nexus 6  General] DutchDogg54:
You'll need a kernel that allows permissive to root at this point. There's only one option, at least until you're rooted - Hells Kernel. They've just released a version built from M sources so it's not a bad idea to continue running it after it's served it's rooting purposes. You can get the Nexus 6 one here: http://renderserver.net/?dl=6cfdf96aff584924592e73b51f0f7629

Once you have that file downloaded, flash it in TWRP and then flash SuperSU, which you can get here https://download.chainfire.eu/696/SuperSU to root. Enjoy.
[Nexus 6  General] mtran13:
Worked for me. Thanks.
[Nexus 6  General] oscillik:
so, if I'm understanding correctly, once I've used Hells Kernel to boot and install SuperSU, I can then flash back to the stock kernel? Or do we have to stick with Hells Kernel to stay rooted?
[Nexus 6  General] gerard_f:
I made a kernel with root for marshmallow updated with the new sources.

http://xdaforums.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958
[Nexus 6  General] p-slim:
this is basically stock then?
[Nexus 6  General] jeffhoe:
it appears that way. I'll be installing tonight.
[Nexus 6  General] collegencmc:
Will chainfire come out with an updated auto root for 6.0? Also to comment on oscillik question. Can I used the modified kernel to root, and then go back to a stock kernel if I want without losing root? Anyway to get rid of the message that comes up when first boot up after trying to root?
[Nexus 6  General] pcrussell50:
Far from Chainfire's or any other developers level, I'm pretty much just a script kiddie, (well I do do my own flashing, longhand not with a toolkit)... I think I understand that since M has a different architecture, it will need a different rooting script. As far as that goes, does that rely on a developer having to find an exploit, where Google is trying to thwart rooters? Or is it a simpler matter of one of the devs learning the architecture, to isolate the steps required to obtain root?

-Peter
[Nexus 6  General] 06sharpshot:
Based on my limited understanding, the issue is that on the stock kernel you have to bypass the SELinux restrictions and it's best to do this without disabling SELinux completely as it provides a layer of security. I know Chainfire has sold SuperSU but I'm not sure if he's going to continue work on his other projects such as CF-Auto-root. What we're waiting for now is Chainfire or some other developer to discover how to bypass SELinux on Marshmallow.

Edit: A beta of SuperSu was posted today by Chainfire so he definitely appears to be continuing development on some of his projects.
[Nexus 6  General] djkinetic:
Still requires a modified boot.img to have root on m that part hasn't changed.
[Nexus 6  General] pcrussell50:
Well damn. It seems that Chainfire IS Android rooting, and without him, we're kind of screwed. I would have thought there would be a ton of other developers doing that kind of work. :(

-Peter
[Nexus 6  General] djkinetic:
He is stepping away from SuperSU in the next two years, chainfire already gave control of the project to another team all that's left is to transition over the dev work to that team. Hopefully they care as much about the project as he has.
[Nexus 6  General] 06sharpshot:
I've also seen work being done on a fork of Superuser so in the future there may be an open source competitor to SuperSU once again. I strongly believe that if Chainfire steps away and the company he handed control over to does something community member disagree with, they will take it upon themselves to create an alternative. Especially with the Nexus program, there are always a ton of developers looking for ways to contribute and make a name for themselves. Hopefully Chainfire continues work on some of his other projects as he's made a ton of useful and necessary stuff.
[Nexus 6  General] beachbum40:
http://xdaforums.com/showthread.php?t=3219344
[Nexus 6  General] marc.ientilucci:
to be sure. i should be able to flash marshmallow, the boot.img from the post & SU 2.5+ and i will have a working rooted 6.0 with no "corrupt device" message AND i'll be able to modify build.prop?

thnx in advance!
[Nexus 6  General] dekciw:
I actually get a boot loop from doing that so I think I'm going back to using hellscore kernel and rooting

Just to be clear I tried flashing the boot.img with hc-b7-m and then flashing stock and retrying the process without the hc kernel
[Nexus 6  General] JavaTiggy:
Just in case you guys haven't seen this thread yet. Here is Chainfire's current way to root 6.0 without the need for a modified kernel (As the thread states, this is not going to be supported and future methods found may require a clean system):

http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
[Nexus 6  General] collegencmc:
Has anyone tried it? If so was it with a wiped or not wiped phone?

Another question what does this mean: "disabled forceencrypt" does that mean we can't encrypt the phone?
[Nexus 6  General] JimSmith94:
That's the method I used, along with SuperSU 2.51 beta.My phone was not wiped and everything works fine. Android Pay still doesn't work though.
[Nexus 6  General] dekciw:
I flashed the second version of chainfires boot.img with hellscore b8-t2-M and supersu 2.52 and it didn't wipe my phone or give me a bootloop, also it removed the corrupted screen at boot. The only issue I'm having is snapchat crashes a lot but not sure if that's anything I've done or just snapchat not being 100% compatible with 6.0 yet

Edit: I installed snapchat beta and the crashing went away
[Nexus 6  General] chinly43:
I just tried this (and it worked) with a phone that was already on 6.0 and already encrypted, and everything I see indicates it still is encrypted.
[Nexus 6  General] stslimited84:
can someone help me? just got a nexus 6 and went to do the cf auto root. the program installed supersu but when it boots it just brings up the red triangle and says the phone is corrputed?

how do i get past this? Need to get up and running asap. currently without a phone :\

my goal is to root, install twrp and then cynanogenmod.
[Nexus 6  General] jasonftfw:
If you're going to be installing cm you just need custom recovery so that you can flash cm, no need to establish root on stock rom. Can you boot into recovery?
[Nexus 6  General] stslimited84:
thank you for the fast reply. yes i can get to recovery.

currently downloading android studio. already have the twrp file. what now?
[Nexus 6  General] jasonftfw:
Then wipe and install cm if that is your end goal
[Nexus 6  General] stslimited84:
I'm brand new to the neuxus 6 platform. my initial approach was to root the stock rom and install twrp using its play store app.

I used odin a few times before but that doesn't apply here obviously so I need some guidance on proceeding. :\

not sure how to install twrp from this point
[Nexus 6  General] jasonftfw:
Google/search on this forum and you'll find the answers
[Nexus 6  General] stslimited84:
edited. there was an issue with the file name. i was able to correct it. thanks :D

any idea why cf auto root failed in the first place?
[Nexus 6  General] scryan:
You need a custom kernel that supports it too.

No, it means you won't be forced to encrypt the phone.
[Nexus 6  General] shabydog:
Oh no! Used CF and it didnt complet the process!!!!! PLEAS

I just had some alert...which was quicly disappeared.

Device did not booted up.

It show's so message:

[IMG="Error message"]https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300[/IMG]

What should i do???

When i boot into Bootloader I can see that:

"Device is UNLOCED Status code: 3"

Thank you!

P.S:

OP!

Would you please UPDATE that CF autoroot does not work for Marshmallow???

Otherwise people are going to brick their phones!!!!!
[Nexus 6  General] Yasharkhan:
cf does work for 6.0.1 now, check mmb29k

https://download.chainfire.eu/628/CF-Root/CF-Auto-Root/CF-Auto-Root-shamu-shamu-nexus6.zip
[Nexus 6  General] Marc_Goeing:
Status 3 is correct for unlocked bootloader
[Nexus 6  General] Spectre007:
So now with the updated cf root we can use the original guide? Unlock the bootloader, flash cf root, flash recovery?
[Nexus 6  General] JW09I4:
Yes, provided you downloaded the newest version from chainfire's link a few posts up.​

Prior to Marshmallow, couldn't you re-lock the bootloader after rooting and still retain root, or am I mis-remembering?

Also, anyone else notice it's not possible to edit any file on the system partition or copy a file to the system partition? Remounting r/w from cli is impossible, although it is possible from within recovery, however, even if mounted r/w, the partition is listed as 100% full, regardless of how much free space there is. If you are successful at saving a file to /system, it's 0'd out and contains no data. see this post

It also appears at least one third party file recovery software [EaseUS MobiSaver] is unable to detect the device is rooted, claiming the device still needs to be rooted.
[Nexus 6  General] jtrentha:
Having an issue completing the process - I'm getting the following message:

downloading 'boot.img'...

FAILED (command write failed (Unknown error))

finished. total time: 5.008s

CF auto root successfully unlocked the bootloader but cannot seem to send the boot img. adb and fastboot are confirmed working, not sure where I've missed it... I'm on MMB29K build so I should be good.

Can I just flash the modified boot img with fastboot, flash twrp and then superSU instead of persisting with auto root?

Thanks in advance for any help!
[Nexus 6  General] JW09I4:
fastboot boot cf.img

Don't allow twrp to install SuperSU

Ensure you press "Do Not Install" and do not use the slider when rebooting from TWRP Recovery
[Nexus 5 Q&A, Help & Troubleshooting] kc_shrestha:
I guess everyone got notification for downloading update for android 5.0 lollipop on nexus 5. When the download is complete and the phone is restarted, it takes me to TWRP screen and I could not figure out what to do next. How could I update now ?
[Nexus 5 Q&A, Help & Troubleshooting] dicecuber:
Are you stock?
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
You must be on the stock recovery, not twrp
[Nexus 5 Q&A, Help & Troubleshooting] kc_shrestha:
Can't I do the same thing from TWRP ?
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
No, it had to be the stock recovery!

---------- Post added at 07:46 PM ---------- Previous post was at 07:46 PM ----------
[Nexus 5 Q&A, Help & Troubleshooting] syrob:
same issue

you have the same issue as I do. if you press the wee squiggly lines at the botton and you will see the log that the install failed.

looks like the root job left something with a KVT49L signature and lollipop wont update now. I posted on how to get by this by no replies as of yet.

I suppose stock android has to be reinstalled wiping out the phone then the ota would work......but I am not sure how to reinstall stock kitkat
[Nexus 5 Q&A, Help & Troubleshooting] Citizen_Snips:
You'd flash the factory images from the Google developer website...
[Nexus 5 Q&A, Help & Troubleshooting] syrob:
unzip a tgz

Ok done that... downloaded the tgz file to a windows directory. What's the best way to unzip this file on windows.
[Nexus 5 Q&A, Help & Troubleshooting] Citizen_Snips:
I use 7zip, personally.
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
+1 for windows.
[One (M7) Q&A, Help & Troubleshooting] RoyalChalksHere:
Hey guys, this is my first thread in XDA have quite some experience with samsung android but pretty new with HTC.

So, I dropped my HTC one day and it got stuck in a bootloop after few days. I havent change anything, stock, unrooted, never flashed any ROM into it, etc. I tried flashing RUU into it using fastboot command but it ddnt work since its still S-on.

Im working on mac as a platform and i dont think this is a major issue?

I am able to access recovery mode and fastboot mode, but wasnt able to push any file into it since debugging mode is off before the bootloop. ./adb devices command wont detect the phone. I also have HTC Sync installed on my mac but again, it wont detect the phone.

I also printed the getvar all result here:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4T.27.3218.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 5.11.631.8

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT36xxxxxxx7

(bootloader) imei: 3544xxxxxx23453

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: ROGER001

(bootloader) battery-status: good

(bootloader) battery-voltage: 3876mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-e47fb74b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

also attached is screenshot of bootloader mode.

please help. my phone have been like this for 2-3 weeks now :(:(
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
First of all is there any warranty left on the device. If there is it would be a good idea to take advantage of that before tampering with it. Especially as this happened after you dropped the phone. So there's a good chance it's a hardware problem.

I assume you've tried to factory reset from stock recovery?

If there's no warranty your best option is to unlock the bootloader. This will allow you to flash a Custom recovery. Then you can push a Rom to the phone, as adb will work in a custom recovery weather debugging is enabled or not.

I recommend TWRP 2.6.3.3 recovery it's not the latest twrp but is the most stable.
[One (M7) Q&A, Help & Troubleshooting] RoyalChalksHere:
yes ive tried factory reset too. I bought it in september 2013 from someone else and i think i lost the receipt, so i dont think I can take advantage of the warrant. i will keep looking though. is there any good link to unlock the bootloader?
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
www.htcdev.com to unlock the bootloader. You'll need to register an account. Then go to the Unlock my Bootloader section. Follow the instructions to get the Unlock code ;)
[One (M7) Q&A, Help & Troubleshooting] @CallMe_Y_C:
I tried resetting rooted device... it rebooted in trwp... so i wiped it from there

when i reboot it doesn't move from the htc logo screen

when i try to power off, the soft keys blink and thats it.. nothing more.. i don't know what else to
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
When you say you wiped it in twrp, did you Factory Reset or did you Format Data?

If you used Format Data then you wiped your entire device including the installed Rom. You should be able to force the device to power of by holding the power button for 60secs.

Then power on while holding volume down to get to the bootloader. Then you can boot to recovery and push a Rom with adb. :good:
[One (M7) Q&A, Help & Troubleshooting] RoyalChalksHere:
awesome, thanks [MENTION=5116541]Danny201281[/MENTION] i got TWRP to work on my HTC one. now on to custom rom. Which one is the best for HTC One? Any suggestion anyone? =)
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Hehe I will always recommend Android Revolution HD because it's my favorite :D

But honestly is depends what you want from a Rom. ARHD is close to stock. It's very stable with no real bugs. It also has xposed support so you can make your own modifications. For me this gives a more personal experience.

MaximusHD is also a very popular close to stock Rom.

Or then you have the likes of Viper Rom or insertcoin which are more heavily modified.

But either way you look at it ARHD is a good place to start. It should be flashed with TWRP 2.6.3.3 TO avoid problems installing as most newer versions of TWRP don't seem to agree with the Aroma installer the Rom is packaged with :good:
[One (M7) Q&A, Help & Troubleshooting] RoyalChalksHere:
hey. ok so i downloaded AICP and installed them through TWRP and everything works fine. BUT, when i got to my homepage and use the phone for a couple of minutes, it restarted on its own. Any idea on why this is happening?
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Go to Setting>About>Phone Identity

Is your IMEI displayed properly there?

Also check Setting>About>Software Information>More

Is your Baseband displayed correctly here?
[One (M7) Q&A, Help & Troubleshooting] RoyalChalksHere:
oh they are both unknown. what should I do?