yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] ultyrunner:
Thanks. It's getting late here so I better not start doing anything to the phone now. One last question as you keep teasing me with new info. First, it looks like some devs have a deodexed, rooted (SuperSU 2.52) stock ROM with no verity/forced encryption at http://xdaforums.com/nexus-6p/development/n6p-angler-mdb08m-deodexed-rooted-v1-0-t3245907 (recently updated to 6.01). Provided it stays updated and could be dirty flashed, that would appear to be what you're talking about.

However, if I went back to stock image with your toolkit then unlocked bootloader, and flashed TWRP and ElementalX kernel without rooting (says it can be installed without root, yet doesn't force encryption), would I be able to do that and still remain 'stock' ... ? I expect it wouldn't work, but I'm just putting 2 + 2 together from the various forums.
[Nexus 6P Original Android Development] Lexmazter:
For 6.0.1 Android Version people stopped using the system root method because you need to manually patch the kernel, and the SeLinux binary that was initially patched by Chainfire is not working on 6.0.1, it can be patched again, but there is no reason to do it since the newest system-less root methods do that for you.

Also, if you look carefully in the thread that you linked, apparently they have some mismatch information provided, they initially say 2.52 but I guess that is old information since you can clearly see on the lower part of the screen this

If you want to stay stock and rooted, you should try to flash the stock package without userdata and recovery via my tool, if that works, then you only need to flash from TWRP the 2.62 SuperUser and you're done.
[Nexus 6P Original Android Development] ultyrunner:
When I was reading that, it 'appears' that the deodexed and 'slightly' debloated ROM with the modified kernel used 2.52, or the traditional root I'm guessing. The absolute stock rooted ROM was using the systemless, V2.61 ...
[Nexus 6P Original Android Development] ultyrunner:
Looking at the systemless instructions from chainfire, it would appear that having already flashed SU2.52, I'd need to flash the stock system image first, anyway. As many North Americans who upgrade to stock or custom 6.01 are having major LTE issues, I was thinking I'd just use your tool to get back to stock 6.0, while not flashing the userdata or recovery images, then flashing the systemless SU2.62. That should work and preserve root. Waiting for the LTE bug to be fixed and ROMs to be updated seems to make the most sense.

I just have one question as a Mac user AND a guy who hasn't typically used the toolkits much. How do I extract/where should I put the individual img files from the zip within the full stock ROM, so I can easily flash them via fastboot? I don't see an obvious place to put them.

Also, one rather odd thing I've noticed. If I have my device plugged into my MacBook but fully booted, I can access the ADB functionalities. However, if I have it in recovery I can't. Seems it should be the other way around. I had to flash SuperSU yesterday via TWRP and not your toolkit.

Cheers.
[Nexus 6P Original Android Development] Lexmazter:
In the first post you can see in the FAQ section how you need to proceed to flash the stock package, bascially you need to extract the contents in the the tools folder Data/StockPackages, there is even a screenshot related to that.

All of the ADB feature besides sideload are created to work while the phone is booted. Have you entered the sideload mode in the recovery and clicking refresh in the tool after that?
[Nexus 6P Original Android Development] ultyrunner:
Thanks for the response.

Yes, I know how to flash the stock package, but since I haven't actually flashed a stock ROM yet, there's a disconnect in the instructions. When you start flashing the stock ROM will your toolkit allow me to select/skip specific images? Without anything that says so, it 'appears' to be a full stock flash.

I think I tried refreshing the toolkit when I was in recovery last night. I'll try again later.
[Nexus 6P Original Android Development] john7760:
In the update he's working on you should be able to select specific items, but not currently. It's all or nothing.
[Nexus 6P Original Android Development] ultyrunner:
Thanks [MENTION=2564500]john7760[/MENTION] ... that will be ideal when the next version comes out. In a previous response, [MENTION=4206980]Lexmazter[/MENTION] seemed to be suggesting I could pick and choose images from the package to install now, so that's why I was curious. I'm sort of on the fence right now. Still at stock 6.0 but rooted with TWRP. I don't want to experience the 6.01 LTE issues many seem to be having, BUT if I'm going to stay on TWRP, I'd really like advanced reboot and to be able to use my current Titanium backup to restore user apps and data. Decisions, decisions ...
[Nexus 6P Original Android Development] john7760:
In that case I'd flash one of the several custom rom's that are 6.0.1 that will give you all you need.
[Nexus 6P Original Android Development] ultyrunner:
But, it seems North American users are experiencing major LTE issues on all 6.01 ROMs, or am I just misreading that? Seems OTA and custom ROMs are all affected http://xdaforums.com/nexus-6p/help/lte-issues-6-0-1-radio-canadian-carriers-t3267270

Aside from not wanting that, the other main reason I'm considering going back to stock and re-rooting is so I can do it systemless, and I'd have to flash the stock system partition anyway.
[Nexus 6P Original Android Development] john7760:
I am on Beanstalk 6.0.1 Rom in PA on VZW and I am not currently having any LTE issues. You need to make sure you update to the latest vendor image though. I did have to flash it twice but no issues myself. If that helps
[Nexus 6P Original Android Development] ultyrunner:
I can confirm that, after starting sideload mode when in recovery, whether I refresh the tool or even restart, it doesn't recognize the device at all. No way to sideload from my Mac. Everything else seems to work perfectly for me. In recovery, I can usually mount my device via Android File Transfer and move SuperSU that way for a normal zip flash if needed.

---------- Post added at 03:23 PM ---------- Previous post was at 03:19 PM ----------

Thanks. I was actually looking at http://xdaforums.com/nexus-6p/development/stock-goodies-multi-window-dynamic-t3244784 as a good compromise of being close to stock with a few nice enhancements. No one who has flashed that has mentioned data issues and they don't seem to have needed to update vendor or the bootloader first.

Again, before I decide on a direction I'm going to give it a little thought. Aside from not being able to use OTAs now, everything is running really well on 6.0 so there's no need to rush and end up flashing a few times over to get happy again. I can wait, but I suspect I'll end up going with custom ROMs when I can confirm I won't have to take a bunch of extra steps to avoid data issues.

Thanks for the feedback.
[Nexus 6P Original Android Development] ultyrunner:
After using the Return to Stock feature, one piece of feedback in my case. It worked fine, but once I chose the stock package and started the flash procedure, the Stock screen remained with everything greyed out. The only thing I could do was open the folder. The phone was rebooting and re-setting up fine, but I had to force close the toolkit with Activity Monitor. So, aside from that bug, it would also be good to have some kind of messaging telling the user what's happening. I suspect you'll need that when we can select partitions, but for now it's a little buggy and unintuitive when doing that.
[Nexus 6P Original Android Development] hapticxchaos:
Hello,

I was wondering how I would open this in linux. I've extracted the zip, but all I see is an executible. Should I be using wine? I noticed no other toolkits could send adb through wine.

Regards,
[Nexus 6P Original Android Development] Lexmazter:
I already fixed that bug for the next version and added an animation, the problem is that the radio ia not flashed unless you reboot to fastboot again while the tool is stuck. Anyways, it should be ok in the next version.

No wine, the toolkit is native for all OS'es, make sure you downloaded the linux version , in the first post you will find that you need to install a couple of libs before you can run it. Other than that it should work by double-clicking the executable.
[Nexus 6P Original Android Development] ryman222:
Sure I'd be happy to help.

Ok I checked that version out and it runs now however there still seems to be a few issues with it. Not sure if this is because there is not a phone hooked up or not but otherwise here's what I found.

Option 1: line 26: bootloader: command not found

'q' Command doesn't work either. Says command does not exist.

Most other options gave errors as saying fastboot-mac and adb-mac does not exist. I'm just assuming that's because I have no device plugged in. Let me know if you want those specifics as well.
[Nexus 6P Original Android Development] Lexmazter:
Okay, checked everything in more detail, apparently there were lots of mistakes around the Linux and MAC scripts (due to not testing...).

Here is the new version -> 6PMultiTool.v0.2.2
[Nexus 6P Original Android Development] os2baba:
Yes, you should be able to lock the bootloader after installing a custom recovery. The only times I have done it though is if I needed to send the device back to the manufacturer for service. And for that, I had to go to stock recovery as well. However, locking the bootloader is safer if you 1. have stock recovery and 2. have disabled USB debugging. And perhaps even that is not safe. The idea is that if someone wants to install a custom recovery or ROM, they will have to wipe the phone since unlocking the bootloader forces that. However, you have apps like BootUnlocker (https://play.google.com/store/apps/details?id=net.segv11.bootunlocker) which get around that as well if you are rooted. And I really can't see myself without USB Debugging, unrooted and not having TWRP. So I just try to practice safe downloads, pay attention to permissions and have Cerberus on my phone to lock/wipe after theft.
[Nexus 6P Original Android Development] chevycam94:
What song is it trying to mention? Not sure how someone is supposed to play it.....now it has me curious.... :P
[Nexus 6P Original Android Development] locolbd:
Is QFUSE really something on the nexus 6p and does this trip it
[Nexus 6P Original Android Development] Lexmazter:
Well, according to this article, QFUSE is something that you could expect to be implemented in a Qualcomm SOC, and if you read more, you will see that in order to blow them you need to do some hardware related steps...
[Nexus 6P Original Android Development] sonofevil77:
Now mine just needs to hurry up and get here!

Sent from my Nexus 6
[Nexus 6P Original Android Development] Planters76:
backup and restore don't work, I keep getting adb: unable to open file
[Nexus 6P Original Android Development] Planters76:
disregard, this maybe on my end
[Nexus 6P Original Android Development] Bartkevin:
I'm going to wait with rooting until there is some more information from google regarding the whole Qfuse situation. From what i've read it disables your fingerprint scanner and some other key features regarding google pay.
[Nexus 6P Original Android Development] wy1d:
The real question everyone wants to know is that will unlocking your bootloader on the 6P cause Android Pay to stop working.
[Nexus 6P Original Android Development] WhiteAsIce:
This is a safety feature. Unlocking any device disables Android Pay. A small sacrifice to make for unlocking your device.
[Nexus 6P Original Android Development] Tung_meister:
[MENTION=4206980]Lexmazter[/MENTION] Just a heads up, you need to update the unlock command to "fastboot flashing unlock" as this is the new command for the M devices - oem unlock no longer works.
[Nexus 6P Original Android Development] r0cafella:
This command doesn't work for me.
[Nexus 6P Original Android Development] Tung_meister:
It should do, just to confirm you'e enabled unlocking in developer settings haven't you?
[Nexus 6P Original Android Development] r0cafella:
I have indeed adb just gives me a list of recognized commands
[Nexus 6P Original Android Development] Tung_meister:
You shouldn't be using ADB - it's a fastboot command ADB isn't involved.
[Nexus 6P Original Android Development] r0cafella:
Let me update the sdk and try again

---------- Post added at 05:22 PM ---------- Previous post was at 04:53 PM ----------

Apologies, updating the SDK fixed it.
[Nexus 6P Original Android Development] Tung_meister:
No problem, glad you got it sorted :good:
[Nexus 6P Original Android Development] d1ez3:
Is this standalone? Do I need android SDK or any other software on my computer?
[Nexus 6P Original Android Development] ultyrunner:
I didn't reboot to fastboot while it was stuck, just allowed the phone to reboot to the OS and finish setting up. So I assume I didn't get the updated radio when I went back to stock (which would have been the same since I was actually still on B08L, just rooted with TWRP), but I imagine I did when I did the OTA update to 6.01? Maybe until that bug is fixed, it would be a good idea to document it somewhere so people know they have to reboot to fastboot before killing the tool manually?

Related, I don't know if you've seen this ADB/Fastboot cmd line toolbox ... http://xdaforums.com/nexus-6p/development/tool-nexus-tools-2-8-featured-xda-t3226767

I probably won't be flashing until there's a next Android January security or point release, but hopefully your toolkit will be updated by then and I can compare ;)
[Nexus 6P Original Android Development] Lexmazter:
The toolbox you mentioned is only installing ADB/Fastboot to your PC, my toolbox has it's own ADB/Fastboot included, so yeah.

I will add a new section to the first post with known bugs so I can document the limitations/bugs I know of.
[Nexus 6P Original Android Development] ultyrunner:
Good call on the bugs section. I'm not saying I'd necessarily stick with a command line interface over a GUI, but as I have never really used the command line being a long-time Mac user, I'm going to play with it. Certainly in breaking apart factory stock ROM and only flashing specific partitions to update, it might be worth testing it for the next release.
[Nexus 6P Original Android Development] Lexmazter:
Since you mentioned, I will add a button in the tool that will open the terminal/cmd so you can manually type your commands using the tool's ADB and FASTBOOT. Sounds like a nice feature to have :)
[Nexus 6P Original Android Development] ultyrunner:
That would be a nice addition. I think where a toolkit with GUI is still nice is that, it can be harder to keep track of files for flashing on OSX than in Windows. Since everything is done via the command line and they are installed via the other toolkit as system wide, I suspect you could put your img files anywhere to flash. Your toolkit makes keeping track of flashables a little easier.
[Nexus 6P Original Android Development] Sarchie1982:
Hello,

I want to make sure if I return to stock to get the new OTA update using this tool, I will be able to use this tool again to unlock the boot loader and root again on 6.0.1?
[Nexus 6P Original Android Development] Lexmazter:
You can still get OTA updates while you have all the stock stuff flashed and you can have an unlocked bootloader.

Since 6.0.1 you should use the systemless root methods, there should be links in the first posts, I will try to keep the first post FAQ section as updated as possible, but due to the fact that the phone and Android 6 are relatively new around the block, things are pretty dynamic and are prone to change rather fast.

So make sure and keep an eye out for updates and such.
[Nexus 6P Original Android Development] Rogoshin:
I tried to use this kit, but got into trouble. It has been a long time since i rooted last, so i was a bit rusty. I unlocked the bootloader, installed new recovery and kernel. But then i forgot to put a rom into the phone so i had nothing to flash. I tried to reboot the phone, but now i have to enter somekind of password. If anybody can help i would be greatly appriciated.
[Nexus 6P Original Android Development] Lexmazter:
Did you put any password for your phone, or pattern? If yes then that might be what you need to unlock it.
[Nexus 6P Original Android Development] Rogoshin:
I managed to get into the phone and download a rom. I then installed the rom and everything seems fine.

I dont like the Rom though, it is called purenexus. If anybody cam revommemd me a rom it would be great.

Sendt fra min Nexus 6P med Tapatalk
[Nexus 6P Original Android Development] adrman:
There are plenty of options out there. Check the op on each rom thread and find the one that suits your needs.
[Nexus 6P Original Android Development] Lexmazter:
Personally I run the 6.0.1 full stock and I wait for MIUI to be released on Android 6 and if time permits will get it to Nexus 6P.
[Nexus 6P Original Android Development] Rogoshin:
Oh i luve miui, cant Wait. Thanks

Sendt fra min HTC One A9 med Tapatalk
[Nexus 6P Original Android Development] slimc84:
What are you looking for in a ROM (Layers, CMTE, specific features)?
[Nexus 6P Original Android Development] Rogoshin:
I like close to stock with few options. I like a audio optimization. But I think I already found one. Now I use Chroma.
[Nexus 6P Original Android Development] wayne8821212:
What exactly CMTE? A quick Google search proved unsuccessful. Thanks!
[Nexus 6P Original Android Development] Lexmazter:
CMTE => CyanogenMod Theme Engine

Layers => RRO (Runtime Resource Overlay)
[Nexus 6P Original Android Development] slimc84:
Thanks. Ya beat me to it!
[Nexus 6P Original Android Development] Lexmazter:
Hello there - Version 1.2.0 is up and running, the changelog has been updated in the first post and is also visible in the github release page. But to sum it up, stock flashing has been fixed and the feature to flash any partition has been added - USE WITH CAUTION.
[Nexus 6P Original Android Development] wayne8821212:
I'm splitting time between Chroma and Beanstalk. .....So many great Roms to choose from!
[Nexus 6P Original Android Development] lynseyw:
I want to flash the new radio only. Where do I put that img file to flash. I put it in stock and it did not work.
[Nexus 6P Original Android Development] Lexmazter:
There is a new menu called flashing, you can enter there and then click open folder, in that folder you copy your radio, then, back in the tool right click on the big white area -> refresh -> now the radio.img should appear, you select the image, make sure the radio partition is selected and click Flash.

This should do it.

Edit: Also, it is recommended to flash the Bootloader before the Radio/Baseband, according to the "base" flashing in the stock images of Google.
[Nexus 6P Original Android Development] lynseyw:
Thanks. I flashed the bootloader using Windows and parallels on my Mac. It's just a big pain in the butt. I wasn't sure about the radio as I heard initial problems with it. I didn't see a flashing folder. I'll look again.
[Nexus 6P Original Android Development] Lexmazter:
Well, you don't need Windows to use my tool, as it has native support for MAC. The folder is called Flashable and it is inside the Data folder in the tool.
[Nexus 6P Original Android Development] lynseyw:
Yes I know!!! That is why I was waiting. I used your tool day one to root etc. I love it. Thanks for helping out us Mac peeps.

When I download the new version.. It's still the old one. No flash folder and says there is an update.
[Nexus 6P Original Android Development] Lexmazter:
So in the v120 zip file you get the 110 version of the tool?

Edit: I just checked by downloading to my vmware MAC the exact zip file from AndroidFileHost and it is the good 1.2.0 version. Make sure that you downloaded that one :)

The latest versions are always on the bottom of the list.
[Nexus 6P Original Android Development] ultyrunner:
I like very close to stock, too. If you like stock with a few very nice customizations, Cataclysm mod is great.
[Nexus 6P Original Android Development] lynseyw:
For some reason when I updated to the new version via the app link it didn't work. I updated with the link in the OP and it worked great. Thanks so much. The link the app gives me is this: https://www.mediafire.com/folder/fvk6cuhsd7nsj/AndroidMultiTool That one doesn't work (at least the Mac version).
[Nexus 6P Original Android Development] Lexmazter:
I changed at some point the hosting and as of now the hoating is hardcoded in the tool, I will update it in a future release to include a more dynamic way to do it.
[Nexus 6P Original Android Development] Lexmazter:
Since a new official release is on the block 6.0.1 (MMB29P), here is a small tutorial how to update to the latest version using the tool without the need to reset all the stuff (as return to stock does).

In order to do this, you need to download the factory image, extract all the zips, even the image-angler-mmb29p.zip, after that, copy all the images except - userdata.img in the tool folder Data/Flashable.

You need to put your device in Fastboot and to enter the Flashing menu of the tool.

Remember to flash first:

1. Bootloader

2. Radio

For the rest of the images there is no order that needs to be kept.

If you want to keep custom recovery, don't flash the recovery :)

P.S. Be patient with the system partition flashing, it will take some time to flash and the first boot will take a while :D
[Nexus 6P Original Android Development] ultyrunner:
Across the board, I've seen various posts saying the bootloader and radio haven't changed, so theoretically if you are just flashing the individual images you should be able to skip those too, no? And, my understanding from some posts is that you may have to re-flash TWRP since flashing the new system image may overwrite the recovery.
[Nexus 6P Original Android Development] Lexmazter:
I can confirm that the bootloader and radio have not changed (between release mmb29m and mm29p) and it's true that you can skip flashing those.

Usually for any release you can skip the bootloader and the radio, they are pretty much stand-alone, the only really important thing is that it's recommended to have the radio match the bootloader version/release, but this is also not mandatory.

As for the recovery, I see no reason why the recovery should be overwritten by the system image. If the system image would overwrite the recovery it would negate the purpose of having a recovery partition.
[Nexus 6P Original Android Development] ultyrunner:
In [MENTION=4153349]Heisenberg[/MENTION]'s initial guide to returning to stock by flashing individual partitions (and even in my own experience in the past on Sammy devices), the recovery can get patched with stock even if you skip flashing it. I guess as long as you have TWRP ready for flashing you'd just have to test it. Since your tool has it included, shouldn't be much of an issue, regardless.
[Nexus 6P Original Android Development] Rogoshin:
I tried to return to stock, but I still get the orange warning when I boot. Is this because I haven't unlocked the bootloader?
[Nexus 6P Original Android Development] Lexmazter:
In the FAQ section there is an entry about this, the point is that the Return to Stock feature does not lock your bootloader. While you have an unlock bootloader you will always get the orange screen.

For example I run full stock but with the unlocked bootloader and I still get the orange screen.
[Nexus 6P Original Android Development] theDK10:
Hey so quick question. I have unlocked bootloader and flashed twrp but now it wants me to mount when i tried to boot up and is asking for a password? Also i can just cancel or select read only but i cant sideload or anything to flash systemless supersu? I was on 6.0.1
[Nexus 6P Original Android Development] Lexmazter:
The thing is that you have an encryoted device, in order to get all working in order you need to go in TWRP, under "Wipe" menu, there is a "Format Data" function, which will effectively remove the encryption from the device.