yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] lords8n:
I apologize if this question was asked previously, I RTFF but I couldn't find an answer. Is it possible to change the folder location where the toolkit looks for images? I can't find an option in the toolkit and I don't remember seeing on option during install either. My system drive is an SSD and I'd rather store the images elsewhere instead of using my system space.

---------- Post added at 09:08 AM ---------- Previous post was at 09:05 AM ----------

I had the same issue. Using 'force flash' option was successful.
[Nexus 6 Android Development] GPS3:
No-wipe mode from 5.0.1 stock; encrypted; leankernel 1.17; unlocked; rooted to 5.1.0 worked flawlessly.

I had to re-root, but that was simple with the tookit. Also, leankernel was flashed over with stock 5.1.0 kernel. (obvious and expected).

I love this toolkit.
[Nexus 6 Android Development] darren.wlsn1:
i know i saw a fix but cant find it now, i show 32g mem and im using a 64g device?
[Nexus 6 Android Development] jiv101:
Need to go into twrp and factory wipe
[Nexus 6 Android Development] darren.wlsn1:
thankyou, will this happen often or is it from unlocking bootloader?
[Nexus 6 Android Development] jiv101:
Just the first time in my experience but after dirty flashing roms it will stay correct
[Nexus 6 Android Development] darren.wlsn1:
still showing 32g, says total space 23.03g with 14.43g available

i hope im adding wrong and box shows i own a 64g device
[Nexus 6 Android Development] norwoodesteel:
factory reset from phone settings
[Nexus 6 Android Development] h11g:
successfully rooted and installed twrp using this awesome toolkit, thanks ts.
[Nexus 6 Android Development] Lw00d:
did you get this fix?? i have the same issue
[Nexus 6 Android Development] darren.wlsn1:
nope, just backed up gonna stock factory reset and let ya know.

trying this first: http://xdaforums.com/showpost.php?p=58201783&postcount=106
[Nexus 6 Android Development] rubber guard:
finally got impatient and upgraded from 5.0.1 to 5.1 via this method, thus losing my data. skipped no wipe mode and forced flash.
[Nexus 6 Android Development] mikeytusa:
I was running 5.0.1, rooted and decrypted. Followed WUG's instructions for flashing 5.1 and once it installed I seem to be stuck in the "Optimizing app..." part. Once it finishes optimizing my apps, it reboots and does it all over again. What should I do?
[Nexus 6 Android Development] Pecata:
That happen to me last night, the only way to get out of it is to use Flash Stock+Unroot and use the Force Flash option using the 5.1 factory image. I was able to fix it this way. I hope you have backed up all your data...
[Nexus 6 Android Development] baudi11:
Same thing happened to me. Here's what I did.

1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.

2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"

3. Click "Flash stock plus unroot"

4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.

5. Follow the toolkit instructions from there.

This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
[Nexus 6 Android Development] ronaldheld:
I am looking forward to trying your toolkit out on Thursday when the Verizon version hits the stores. AFAIR it has 5.1 to start with.
[Nexus 6 Android Development] halon17:
I had to do this. Thanks. I'm currently waiting for it to format cache.
[Nexus 6 Android Development] jpierce:
That's exactly what happened to me. After it did it 3 times in a row I just hooked back up to computer and ran the steps again through NRT and it worked. All good since. Had to root and install recovery again after for some reason but all is well now.
[Nexus 6 Android Development] halon17:
Well this is annoying. It is bootlooping again.

If I'm in a bootloop does the device have 5.1 or is it still at the build I had when I started?
[Nexus 6 Android Development] SemperFratres:
Nexus 6 Stock Recovery

I am attempting to flash Stock recovery. It didn't flash when I un-rooted. I am getting to the following point and it just sits and waits for device. Got a message that waiting timed out.

Connectivity Status: Fastboot Device Connected

Information: Temporarily Booting modified boot.img to enable running privileged commands...

fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Modified_Boot\modified_boot_shamu_5.0.1_LRX22C.img"

Information: Waiting for your device...

Information: Waiting for your device...

Is this option not working?
[Nexus 6 Android Development] halon17:
I had to do it a third time and finally worked.
[Nexus 6 Android Development] darren.wlsn1:
5.1, same issue i had
[Nexus 6 Android Development] Chad_Petree:
My bootloader is unlocked and I flashed the stock 5.1 image, if I download this toolkit and try to root my device, will it work or do I have to wait for Wugfresh to update the toolkit? :confused:

Let's say I wait for the toolkit to be updated, will I have to reset my device later on in order to root it ( like I said I already have unlocked the bootloader) ? :)
[Nexus 6 Android Development] DebianDog:
He already updated the software a few days ago you should be able to root it now.

Sent from my Nexus 6
[Nexus 6 Android Development] Chad_Petree:
Awesome! I was just confused because the thread's titel still says "Wug's Nexus Root Toolkit v2.0.4 [Updated 02/04/15]"
[Nexus 6 Android Development] DebianDog:
That is the Windows program itself. It looks for the latest drivers, images, and whatnot when it launches.
[Nexus 6 Android Development] Didgeridoohan:
About the boot loop with "Optimising apps...". I experienced the same thing and I think there's a bug...

I'm unencrypted and flashed 5.1 with the "No wipe" and "unencrypted" options under "Flash stock + unroot". The bug, I believe is that the tool didn't download the modified boot image for the unencrypted option and this since I already had that option active since my last flash. After unchecking "Force flash", trying again without success (because of the error with missing system.img), trying a third time with the "unencrypt" option once again the tool finally realised I was missing the modified boot image and prompted me to download it. This time everything worked perfectly...
[Nexus 6 Android Development] chopt51:
I've was planning on using this to decrypt my phone today. Currently on 5.0.2 custom ROM. The only thing that I'm concerned with is in the next few weeks upgrading to a 5.1 custom ROM. How is that going to affect encryption? I don't want to have to wipe all data twice.

Also I was going to take this time to f2fs my device also. I was wanting to do everything now. Is it OK?
[Nexus 6 Android Development] Amos91:
That happened to me. Seems the toolkit uses the boot.img for the android version you are currently running rather than downloaded.
[Nexus 6 Android Development] lioryte:
Yes. There is a new device protection feature built into 5.1. http://ow.ly/2VKX0D.

I thought that the new device protection kicks in during boot, but after trying it out, I can confirm that I thought wrong. If the phone was 1.on 5.1, 2. lock screen enabled (pin/pattern) 3. loged via a google account

bootloader factory reset via adb/ your tool, will generate a complete, full boot. but after choosing the initial language, one must put the main last default google login info in order to continue, no skipping is optional, android won't continue without the last default google account login Cool feature, but as far as [MENTION=3110798]WugFresh[/MENTION] and this tool are concerned, alles gut
[Nexus 6 Android Development] WugFresh:
Thank you for the clarification. That sounds horrible in general. For someone like me who uses lastpass for everything.. I don't know my 80+ random character passwords. That's a pain.
[Nexus 6 Android Development] bonbon363:
5.1 Stock image

I cant flash 5.1 stock image, it is always failed at flashing bootloader.img.

I've tried force flash too. I have no problems flashing 5.0.1. stock .

Can i just flash a 5.1 ROM over this 5.0.1 such as Sinless ROM? or do i need to flash the 5.1 bootloader, radio combo first?

Thanks
[Nexus 6 Android Development] Lesser Version:
Currently unlocked, rooted, unencrypted, and running a custom ROM. After reading 15 pages of problems, is there a definitive way to update with the 5.1 image file without having all of the problems mentioned in this and other threads? I have the toolkit and computer setup and ready, but am concerned with all the problems. Love this toolkit and have been using since Galaxy Nexus..
[Nexus 6 Android Development] darren.wlsn1:
dont relock and your fine, im new to fastboot ect and it went fine if you follow directions. i had a issue but i created it.
[Nexus 6 Android Development] rahsaanabdul:
Delete

Sent from my Nexus 6
[Nexus 6 Android Development] keltai:
hi, seem there a mixed bag of problem using NRT "flash stock+unroot" to upgrade from 5.01 to 5.1... currently, im rooted, stock rom and using TWRP recovery, unlock, unencrypt... to those who succeed, wat the step, advised and precaution i shd take before i flash stock+unroot to upgrade 5.1? any advice here? thanks and appreciate........
[Nexus 6 Android Development] Chad_Petree:
Just to be 100% clear, if you're 100% stock you should first unlock the bootloader and don't relock it , then flash 5.1, then root it and then unencrypt it?

Let's say google releases 5.1.1 in 2 weeks in order to get the OTA I have to unroot and unencrypt it and by doing so I have to delete everything on my device? What about if I only root do I still have to reflash stock in order to get the OTA? :confused:
[Nexus 6 Android Development] DebianDog:
Yes if you insist on getting OTA you cannot have a rooted phone. in my opinion the best thing to do is "get over it" and wait a day for someone to create a zip file you can load via TWRP or wait for WugFresh you update (which I believe he did in less than 24 hours)

Sent from my Nexus 6
[Nexus 6 Android Development] sun2sunny:
Best toolkit ever
[Nexus 6 Android Development] teddy sheringam:
Just flashes 5.1... Everyting's OK...? just have one question... Can someone tell me how do we enable device protection? Thanks...
[Nexus 6 Android Development] Chad_Petree:
I just wanted to be sure, I think I remember back in the galaxy nexus days, that you were able to get OTAs with a rooted phone, you would just lose root and had to reroot, am I dreaming? :confused:
[Nexus 6 Android Development] HipKat:
I was going to wait until the AOSP ROMs were working well with 5.1 but decided to take the OTA and run stock for awhile only because of the way it uses quad core now. I figure if I was OK running stock the first month after the N6 was released, I can do it again.
[Nexus 6 Android Development] DebianDog:
Well that's true but I have that same configuration running with the Franco kernel on 5.0.1. I found it funny Google came to the same conclusion he did.

I hear there are issues with Apex (my launcher) so I will probably wait for those to get resolved before moving to the next release.

Sent from my Nexus 6

---------- Post added at 08:32 AM ---------- Previous post was at 08:30 AM ----------

I think you're correct it used to be you would lose root if you took the OTA. Now I think there must be some type of check. Actually you used to have to change a flag so that the OTA didn't sneak up on you[emoji50]

Sent from my Nexus 6
[Nexus 6 Android Development] HipKat:
I could only ever get that to correct itself by doing factory reset form Settings. Beware, it takes forEVER to do it
[Nexus 6 Android Development] Chad_Petree:
I see a couple of people having this issue but they talk about encrypting the device , when I set the toolkit to force flash mode I get the option to "No force encrypt" which is not the default option, so when I flash with the toolkit the default option is to deactivate the encrypt option?
[Nexus 6 Android Development] MrStig91:
Just wanted to pop in and say thanks for the toolkit! Wish I had seen this sooner, makes everything so easy. Flashed stock 5.1, rooted and flashed twrp in a matter of minutes.
[Nexus 6 Android Development] rahsaanabdul:
It was great being able to go back to 5.0.1/2 after installing 5.1. There are features I can't get on stock that are a deal breaker for me. I will wait patiently for 5.1 to be incorporated into the AOSP ROMs. NRT is a great asset whichever direction you choose to go.

Sent from my Nexus 6
[Nexus 6 Android Development] Crosserson:
Thanks OP for this awesome toolkit.

Donation incoming.
[Nexus 6 Android Development] Citadel69:
Quick question

I'm currently running rooted stock 5.0.1. I want to flash 5.1. Should I do that first then root, then unencrypt? Just want to do it in the right order. Also I'm wipe everything by unencrypting right? Thanks for any help.

---------- Post added at 06:41 PM ---------- Previous post was at 06:04 PM ----------

I have one more question. Can I actually upgrade to 5.1 using the NRT
[Nexus 6 Android Development] jrbxx7:
Yes u can. I selected force flash and no wipe and it upgraded fine. Yes upgrade to 5.1 then install twrp and root. then unecrypt if u want. And yes that will wipe all data.

Edit.... Also make sure ur bootloader is unlocked. Don't relock it.

Sent from my Nexus 6 using Xparent Red Tapatalk 2
[Nexus 6 Android Development] Citadel69:
Thank you so much, really appreciate the help
[Nexus 6 Android Development] WugFresh:
Sorry for the confusing semantics. You have it understood incorrectly.

By default, the toolkit flashes the Stock factory image which *forces encryption*. The optional checkbox to swap in the "no force encrypt" will allow the user to deactivate encryption.

So to further clarify, you have it backwards. Hope that helps clear it up.
[Nexus 6 Android Development] HipKat:
The only difference is I backed up my storage and I;m letting it wipe. It;s going to when I decrypt and will make the Factory Reset that much faster
[Nexus 6 Android Development] Citadel69:
Ok so I'm not seeing a force flash option. I need to download the 5.1 update to my computer first right? Then open up the NRT, but I'm unsure what to do after that. Thank you for any help
[Nexus 6 Android Development] WugFresh:
Flash Stock + Unroot button. All options and methods are there and should be self explanatory.
[Nexus 6 Android Development] Citadel69:
Thank you
[Nexus 6 Android Development] wooddale:
So 5.1 is good to go?
[Nexus 6 Android Development] WugFresh:
Yeah.. I added it the same day it was released. You even could have flashed it with NRT before I added it using the other/browse option in flash stock.
[Nexus 6 Android Development] wooddale:
Thanks Im gonna get right on it
[Nexus 6 Android Development] HipKat:
All good. Flashed Stock + Unroot, d/l'd the 5.1 update, flashed it (With Force flash which I've had enabled since the first time I used the kit in December) no problem. Rooted, no problem.

Decrypted, not only no problem but even had correct storage afterward.

Noi boot loops. no nothing but love!
[Nexus 6 Android Development] Recon0212:
Anyone else getting a failure when doing stock + unroot? Mine keeps failing at system when flashing 5.1...
[Nexus 6 Android Development] jrbxx7:
Have u tried checking the force flash option. That worked for me when the normal didnt

TaPpEd FrOm My N6
[Nexus 6 Android Development] Recon0212:
Tried it and worked. Thanks!
[Nexus 6 Android Development] Chad_Petree:
Thank you for the explanation :laugh:
[Nexus 6 Android Development] JMacD:
Had to re-Root after Stock Flash 5.01 to 5.1 & OEM unlocking defaults to off

Wug, thanks again for your work. I used the NRT to unlock, root, and decrypt my Shamu right out of the box. I also used it to flash stock 5.0.1. (I donated gladly :) - pure awesomeness. )

I just wanted to share my experience using the NRT to flash 5.1 onto my device, which is/was 32gb, running 5.01 stock, Franco Kernel r19, unlocked, rooted, and unencrypted, with BusyBox Pro, SU# Pro, etc.

The first time I tried flashing 5.1 stock with NRT last night, I went with the no wipe, force flash, no force encrypt and I ended up in a repeating "Android Upgrading, Optimizing apps...21 of 158" loop. After about 4 of these cycles I booted into bootloader mode and powered off for the night. I did try to boot into recovery mode from the bootloader, but all I got was a droid on his back with a red warning sign over the open chest area, and had to do a hard reset from there. I think this was due to the missing modified img for the no-force encrypt option, which the NRT downloaded this morning when I was back at it.

I did another "Flash Stock + Unroot" about an hour ago, which brought my Shamu back to life, however I no longer had root privileges. The phone was still un-locked (according to the Bootloader mode info) and not encrypted. The flash files were all still in the !ReadyToFlash directory, but when I opened SU# it said in had no binaries and that I could download them using the app - I had to root the device first.

So I used the NRT to Root and flash the custom recovery and SU binaries. I then flashed the latest Franco Kernel r20 using the FKupdater paid app and all seems back to normal, or an "upgraded" normal I guess. :good:

One thing that sticks out to me is the OEM unlocking: "Allow the bootloader to be unlocked", in Developer Options - it is off by default, but my phone is Unlocked (as far as I can tell). I assume this is the new 5.1 device protection that I saw mentioned in a couple recent threads? Does this setting actually affect the status of an unlocked bootloader? It didn't seem to stop the NRT from re-rooting and flashing the custom recovery (this option was off by default after flashing 5.1 and during the Root).

Thanks again.
[Nexus 6 Android Development] RandoTheKing:
How do I flash 5.1 without losing my stuff? I used NRT to decrypt, running 5.0.1 and stock recovery
[Nexus 6 Android Development] jrbxx7:
No once ur unlocked that doesn't have any affect on the unlocked status. If u relock then that must be selected or it will brick the phone when u try to unlock.

Sent from my Nexus 6 using Xparent Red Tapatalk 2

---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------

U can select the force flash and no wipe option and your SD card will not be wiped however if you flash the modified (unencrypted) boot image it will most likely wipe the device so back everything via titanium or something and transfer to a PC to save it. Then restore after updating.

Sent from my Nexus 6 using Xparent Red Tapatalk 2
[Nexus 6 Android Development] RandoTheKing:
So if I go encrypted I shouldn't need TB. Has anyone noticed a huge improvement on read/write speeds using encryption on 5.1? I had read that Google improved it
[Nexus 6 Android Development] Amos91:
I hope that [MENTION=3110798]WugFresh[/MENTION] can look into this as I am sure that when no-encypt is enabled it is using the 5.0.1 boot image and not 5.1. This is what causes the bootloop.

When you go to re-flash, it reads that you are running 5.1 android and downloads the updated 5.1 boot image. I confirmed this when I first bootlooped as the boot.img was an old one. When it realised I was running 5.1 it updated the boot dependencies before re-flashing to the new 5.1 no encypt version. (I did manually press update files before my first flash but it made no difference).
[Nexus 6 Android Development] twatts723:
[MENTION=3110798]WugFresh[/MENTION], just burned up as much thanks as I could find your name on this thread. I was having all kinds of problem trying to update my nexus 6 to 5.1, using all these different methods. Then, helloouueueer, nexus toolkit. Updated all the dependency files on the toolkit, click on unroot/upgrade, and follow simple instructions. Haven't had a problem since. Thanks for making everything so easy for us simpletons bro! :good:
[Nexus 6 Android Development] emanuele635:
Hi. I'm running 5.0.1, rooted and decrypted and I want flash 5.1. Before doing this I have to unroot and relock? Can I make it with a decrypted phone?

Thanks.
[Nexus 6 Android Development] kingofkings11:
This might be a stupid question but if I select the Flash Stock + Unroot option to upgrade to 5.1 will this process flash the newest bootloader and radio or do I have to do that separately?
[Nexus 6 Android Development] wooddale:
Yes
[Nexus 6 Android Development] maxamus007:
Yes as in flashing the image also updates the basehand and radio?
[Nexus 6 Android Development] jrbxx7:
Correct it will update bootloader, radio and system image

TaPpEd FrOm My N-sIx
[Nexus 6 Android Development] SmokeyMon:
[MENTION=3110798]WugFresh[/MENTION] ,

Just plugged up the phone watched your app update and do its thing and boy your app does its thing. A simply brilliant automation device. You make it too easy. It is professional grade sir. I can't say enough about a tool that does exactly what I expect every time I use it. Thanks for sharing.
[Nexus 6 Android Development] cory_dre:
So I managed to flash 5.1 one and got the system apps boot then suddenly my phone just shut off. Anyone guide me through this?

---> Nvm bros I managed to figure it out. I needed to breath lol
[Nexus 6 Android Development] buzzwyzr:
I have confused myself reading about the "don't relock" problems people are having.

I went back to stock to upgrade to 5.1 like lots of you did. But I relocked my boot loader afterwards because I wanted to run "full stock" for a few days. I know there's no difference in actually using the phone whether it's locked or unlocked but I locked it anyway.

So is the consensus that if you attempt to unlock the bootloader...even if you check the option under developer options...once on stock 5.1 will brick the device? Or does a brick occur ONLY if you don't check the option prior to unlocking?

Thanks for any clarification...like I said I've done confused myself lol.
[Nexus 6 Android Development] jrbxx7:
From everything I've read it will only brick if u fail to check the option before unlocking. I never relocked so I can't say 110% for sure. But read this thread.

http://xdaforums.com/showthread.php?t=3053497

TaPpEd FrOm My N-sIx
[Nexus 6 Android Development] HipKat:
I swear, in an effort to save time and take shortcuts, people make this so much harder than it has to be.

The only Solid, 100% way to do it is to do it right.

First, read the directions on every step. Don't skip over anything

Backup your Storage.

Use WUG's to d/l and flash 5.1 with Force Flash and do NOT check No wipe or unencrypt.

Let it wipe like it's meant to do.

When it's done, root. Don't sign in or anything, just skip it all and then root.

When that's done, in Advanced, flash Kernel, select Unencrypt, let it d/l the RIGHT img and flash it.

When it's done, check storage in Settings. If it's good, like mine was last night, restore your storage backup. If it;s not, do a factory reset from Settings, not TWRP.

When that's done, restore your backed up storage files. Done.

That's it. That's the way to make it work right, the FIRST time.
[Nexus 6 Android Development] jrbxx7:
I used the no wipe option and it worked flawlessly. ??

TaPpEd FrOm My N-sIx
[Nexus 6 Android Development] WugFresh:
You guys are right. I confirmed the behavior. It's not the modified boot that matters (not used during the flash stock procedure) but rather the no-force encrypt boot.img is in fact referencing the current device info. I will push 2.0.5 as soon as possible with the fix, plus the other things I have been working on.
[Nexus 6 Android Development] WugFresh:
Thank you. :) most appreciated.
[Nexus 6 Android Development] garenzy:
How would one upgrade to 5.1 using Wug's NRT if I already unencrypted and rooted back in 5.0.1? Apologies if this has been answered before.
[Nexus 6 Android Development] WugFresh:
1. Set your current device as 5.1.0 (even though you are actually on 5.0.1 - this won't be necessary in NRT v2.0.5)

2. Use "Flash Stock + Unroot", select the 5.1 build to flash and check: "force flash", "no wipe" and "no force encrypt"

That's it. Still finalizing some other feature changes in v2.0.5. Hopefully I can get it out today.
[Nexus 6 Android Development] Lancez:
Google just posted new LMY47E, might wanna update that as well. Thanks