yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] ImmortalsReign:
Please ignore this. I have recovered my phone and now I'm running 5.1. Thanks for this tool Wugg.
[Nexus 6 Android Development] WugFresh:
Cool. I may script root support for that device without TWRP since it doesn't seem anyone is making it.
[Nexus 6 Android Development] cory_dre:
So I have factory wiped and fastboot wiped and still show 23GB with my 32GB model, any other thoughts?
[Nexus 6 Android Development] DebianDog:
Congrats? http://xdaforums.com/nexus-6/help/23gb-total-space-32gb-nexus-6-box-t2948463

Sent from my Google N6 on VZ
[Nexus 6 Android Development] kornklown69:
that would be appreciated actually, the 5.1 image was just added cpl days ago as well if you want to add that to the images for that device.
[Nexus 6 Android Development] HipKat:
You know, in the NRT, it tells you when you get the errant storage reading to do a factory reset. I know people are doing fastboot commands, cool, but have ya's tried a factory reset? Seems to work every time on mine. Just sayin'....

Now, odd thing, I flashed E last night, d/l'd it, flashed it and when it was done, I was on D still. Did it again, same thing. Even though the version tried to change itself to E in the Program. I had to go into Win Explorer to the Wug's folder and delete the img folders for D & E, then start over, which worked.

---------- Post added at 06:00 AM ---------- Previous post was at 05:58 AM ----------

You should tell us how you fixed it, incase it happens to someone else
[Nexus 6 Android Development] cory_dre:
Yeah well I tried a normal factory reset and it didn't fix it lol. I guess I'll try and reflash with a wipe then see if its fixed and go through settings and factory reset
[Nexus 6 Android Development] phyba:
Should be getting my nexus today or tomorrow. Been testing as much as I can. Just wondering, if I disable encryption, is it recommended to do it before or after u flash a custom ROM? Does it wipe data?
[Nexus 6 Android Development] old_fart:
Go to the decrypt thread if you have not read that one yet . . .

http://xdaforums.com/showpost.php?p=56896020&postcount=1

delete, the format is . . . [ Think of decryption as a "first step" in a process flow.]

You "must" choose to format the data partition ( not wipe it ).

So, in the data partition, the format clobbers the encrypted ( factory installed ) stuff that "was" there . . . makes its ready for a do-over . .

And then also, you "must" have a non-enforcing kernel in place to replace the normal, stock kernel which will want to encrypt you as you come up.

hth.
[Nexus 6 Android Development] phyba:
So you're saying I should do decryption first right?
[Nexus 6 Android Development] WugFresh:
If the ROM you are flashing has the no-force encryption mod integrated into its boot.img then there is no need to decrypt first. Just flash the ROM and wipe data and you will be decrypted. If the ROM doesn't have no-force encrypt disabled then you can decrypt afterwards with the toolkit or flash a custom kernel that has that mod.
[Nexus 6 Android Development] DebianDog:
Wow this tool has command line for when I feel like going old school! NICE!

Sent from my Google N6 on VZ
[Nexus 6 Android Development] smclaughlin3:
Is the lmy47M build in the toolkit yet? Thanks
[Nexus 6 Android Development] toknitup420:
deleted. foolish mistake.

edit: i have now unlocked, rooted with twrp, flashed no enforce kernel. however in developer options oem unlock is unchecked. bootloader says unlocked though. is this normal..

verizon n6

5.1

47E outta the box
[Nexus 6 Android Development] Newblood:
Used NRT to root, flash TWRP, decrypt and flash 5.0.1 originally. At some point I lost root and TWRP.

It wasn't to big a deal because by the time I noticed I was ready to flash 5.1.

Prior to flashing 5.1 I used NRT to reroot. I then flashed 5.1 with decrypt and it "updated my TWRP" in the process.

However I have now noticed that i have lost root again and either can't access TWRP or it is no longer there.

Anyone have an idea why my phone keeps unrooting and appearing to lose TWRP?
[Nexus 6 Android Development] travisjshepherd:
Just got my Nexus 6 yesterday, already had NRT running waiting to get it home. I plug it in, do everything the toolkit said to do and I kept getting a fastboot device not found error. I tried over an hour to get this thing to work, eventually my power went out due to the electric company testing lines. when it came back up BOOM! worked in one go, all it needed was a computer reboot. lol I'm an idiot!
[Nexus 6 Android Development] DebianDog:
If you do a full flash its going to flash recovery and system. root lives in system and TWRP is an alternate recovery. if you do a flash to another version you can retain user but you will have to re root and reflash TWRP. You could also use the tool and just flash 1 image if you have it.

As much as I like this tool I actually prefer loading things with a zip from recovery that way the only thing that changes is system. Just be sure you use a zip that is pre-rooted. That and I'm just more comfortable letting things from TWRP.

Sent from my Google N6 on VZ
[Nexus 6 Android Development] TonikJDK:
Normal.....that dev option resets on boot with 5.1. So be warned....relocking can and does go horribly wrong. Dont relock unless you have to and learn the details if you do. And dont downgrade the bootloader.
[Nexus 6 Android Development] toknitup420:
No intention of relocking EVER lol. Just got worried when I saw that it was unchecked. Do I need to select it again before flashing Roms or am I good to leave it alone.
[Nexus 6 Android Development] tommydeaks:
Hi guys

Does the NRT work okay with Android 5.1 and the whole allow OEM unlock thing turning itself off?

I want to flash euphoria, but I bricked my last device. Luckily I got RMA.

Thanks
[Nexus 6 Android Development] smclaughlin3:
Will the lmy47m be on the toolkit im on T-Mobile and Google has not posted it yet... Why!
[Nexus 6 Android Development] Newblood:
I did flash to a newer version with NRT and used "No-Wipe", and afterwards I am fairly sure I was still rooted and still had TWRP. However I tried to access Titanium Backup yesterday and it said I didn't have root privileges (or whatever exactly it says). On top of that I noticed that my SuperSU was no longer installed.

Obviously I was easily able to re-root again using NRT. I still can't access TWRP, whenever I try to go into recovery I just get the dead android symbol. Which probably means I am back to stock recovery.

Just trying to figure out what keeps causing my phone to lose root and TWRP.

Thanks,
[Nexus 6 Android Development] WugFresh:
Yes, whenever google release it.. I can't do it beforehand.
[Nexus 6 Android Development] WugFresh:
If you flash stock, regardless of "no wipe" - you will lose root and recovery. Just root again with custom recovery checked.
[Nexus 6 Android Development] DebianDog:
Why! Can you not get the DeLorean up to 88 miles an hour? What the hell do we pay you for? oh wait...

Sent from my Google N6 on VZ
[Nexus 6 Android Development] toknitup420:
Lol.
[Nexus 6 Android Development] Newblood:
Ok thanks. Rooting again with custom recovery checked will wipe my phone correct?
[Nexus 6 Android Development] toknitup420:
Since OEM unlock doesn't stay checked on 5.1, is it a good idea to check it before flashing another ROM. Or should I be OK since the bootloader is unlocked status 3.
[Nexus 6 Android Development] jrbxx7:
Once your unlocked u should be fine. I have went from 5.0 to 5.1 d then e and flashed several custom ROMs with no issue. The only problem would be if u relocked and then tried unlocking without checking that option.

TaPpEd FrOm My N-sIx
[Nexus 6 Android Development] toknitup420:
OK cool. That's what I figured. Thank you.
[Nexus 6 Android Development] ronaldheld:
No problems with using this toolkit. Short of waiting in the unlocking phase, things went smoothly. I did not opt to load the custom recovery. Suggestions as to the preferred method without rerooting?
[Nexus 6 Android Development] russlowe73:
Only 2 ways, either root and use flashify, or fastboot flash the recovery image.
[Nexus 6 Android Development] ronaldheld:
I did root, but forgot to mention it. I am unfamiliar with flashily.
[Nexus 6 Android Development] smclaughlin3:
Is it safe to downgrade from 5.1 lmy47d to 5.0.1 lrx22c im trying to catch tmobiles 5.1 lmy47m ota btw has anyone tried the method i just described? If not why not? Thanks
[Nexus 6 Android Development] jhernand1102:
From what I've read you will not be able to flash the 5.01 bootloader so you will not be able to get the OTA update. You will have to flash the LMY47E factory images and then catch the OTA for that version that T-Mobile said was going to be released.
[Nexus 6 Android Development] mlin:
Hey, man. Welcome to the Nexus 6!
[Nexus 6 Android Development] joshjunior:
Used this to recover from a soft brick today lol. Was editing build.prop to enable tethering and I must have put the text in the wrong spot and it was hanging on the Google screen when booting. Thanks for putting a quality easy to use toolkit out there
[Nexus 6 Android Development] yankeesfan714:
So right now on 47M we can unlock root and flash custom recovery, we cannot flash stock and unroot. Is that correct?
[Nexus 6 Android Development] russlowe73:
Flashify is an app in the play store that allows you to flash boot images, kernels, etc. But if you are already rooted, you could just use wug toolkit to flash recovery.
[Nexus 6 Android Development] WugFresh:
For those who were curious about the "Enable OEM Unlock" security setting, I asked around and found an answer.

The auto-resetting to disabled is an intentional "security" feature by Google, and it happens after a certain number of reboots.

Significance? Nothing you need to worry about, or constantly keep trying to re-enable once you are unlocked already. It's fine if its disabled when you are unlocked already. Just make note of this setting and behavior if you intend on relocking your bootloader (which should only be done if you are reselling/returning etc). If you plan on relocking, you should first flash stock, and make sure everything is running smoothly, so if you need to re-enable this setting to unlock again, you can do so easily.

Please note, a locked bootloader is NOT required to receive/take an OTA update; you just need to be running pure stock.

Main point: don't bother relocking your bootloader unless you absolutely need to, and are sure your device is healthy before doing so.

I will be adding a little notice about this in the relock info message in the kit.

Cheers,

{{ WugFresh }}
[Nexus 6 Android Development] efrant:
The explanation is here: https://support.google.com/nexus/answer/6172890?hl=en
[Nexus 6 Android Development] BossJ:
Question - I am on 5.0.1 STOCK - I just flashed it via Wug's NRT. I am on T-Mobile.

Where do I go from here?

I want to end up on Android 5.1 build LMY47M ...UN - ENCRYPTED...

Thanks for your help!
[Nexus 6 Android Development] lioryte:
Wait until the factory image is live

https://developers.google.com/android/nexus/images
[Nexus 6 Android Development] BossJ:
http://www.androidheadlines.com/201...a-update-now-available-download-included.html

is this not it? Or is the OTA update different than the Factory Image?

Also will it be added to Wug's NRT when it is live?
[Nexus 6 Android Development] lioryte:
No it is not the same.
[Nexus 6 Android Development] BossJ:
Thank you sir :D You've been much help. As a T-Mobile customer, do I need to wait for the T-Mobile factory image? - Is there a difference in bootloaders / radios or is it just the ROM it's self?
[Nexus 6 Android Development] lioryte:
Not really, you should be all set, the changes between builds should be minor, maybe a difference in radio, maybe M build is WiFi calling ready but currently D/E are running just fine on magenta. If you feel you can't wait, fire up adb and get 'er done.
[Nexus 6 Android Development] BossJ:
Thank you! I'll stop hijacking the thread :D
[Nexus 6 Android Development] beachbum40:
I have side loaded the m build I'm on T-Mobile . why are you saying the factory image of m build is different?
[Nexus 6 Android Development] lioryte:
http://xdaforums.com/nexus-6/general/nexus-6-android-5-1-versions-discussion-t3059114
[Nexus 6 Android Development] Nickchapstick:
I have read that thread and it just sounds like a bunch of guessing and then some facts about difference between those versions not anything about "factory images" vs "OTA" update.
[Nexus 6 Android Development] ok2nvnexus:
Yes...I did! Twice and was successful
[Nexus 6 Android Development] smclaughlin3:
I did it too just last night but

people on the chroma thread insist its impossible!
[Nexus 6 Android Development] wtherrell:
They are talking about the bootloader. NOT the Android build numbers. Lots of confusion on that point. You will not see the boot loader version in the "About Phone" section of settings (Unless the rom has put an added section in.)

For example, the old boot loader is 0x7105.

I don't know that number for the latest one.
[Nexus 6 Android Development] smclaughlin3:
Well i made it clear that i went from lmy47d 5.1 to lrx22c 5.0.1 to sideload the lmy47m 5.1 tmobile ota build i mean i went from 5.1 to 5.0.1 back to 5.1 ( theres a few out there d,e,m,i). I dont think 5.0.1 is gonna have same bootloader as 5.1?
[Nexus 6 Android Development] wtherrell:
Yes, it can.
[Nexus 6 Android Development] smclaughlin3:
Ok they were saying i didnt do what i described cause if they did the argument would have stopped
[Nexus 6 Android Development] the_rooter:
I read the part where u claimed this and its incorrect. U can't downgrade the bootloader. Once u upgrade it ur at that one. If u try to downgrade it will fail and may brick. Stop trying to get people to think your right. U are wrong. U didn't downgrade the bootloader. You were telling everyone u did.
[Nexus 6 Android Development] smclaughlin3:
I described exactly what i did pal.... fight ur own battles and look it up i didnt even mention the word bootloader
[Nexus 6 Android Development] the_rooter:
Lmao of course u did I am looking at it right now. Your what this community calls a noob and a nuisance. Covering up ur lies now ic.

---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------

Here's your exact post.

http://xdaforums.com/showthread.php?p=59683473

#9176 u claimed that u can downgrade bootloader
[Nexus 6 Android Development] smclaughlin3:
Not really i may have mentioned the word bootloader but i never argued bootloader specifics there may have been some loss in translation as far as downgrading in the sense that i downgraded to 5.0.1 from 5.1 then sideloaded the tmobile 5.1 update haha thats what you get for dipping your nose in stuff thats not you business lmao

Plus if there were any experts what i was saying was perfectly understood as i clearly explained what i did i didnt harp on bootloader specifics brah
[Nexus 6 Android Development] yankeesfan714:
Jesus, can a moderator please stop the madness?
[Nexus 6 Android Development] kornklown69:
new factory image out for nexus 6 already lol lmy47i is ready to download and be installed
[Nexus 6 Android Development] WugFresh:
Shaboom - http://www.wugfresh.com/new-lmy47i-builds-for-n5-and-n6-added/

{{ WugFresh }}
[Nexus 6 Android Development] teddy sheringam:
Do you think that who´s on lmy47d, should upgrade to lmy47i? Or it's a version to a specific region? It's getting weird releasing builds every week...:)
[Nexus 6 Android Development] toknitup420:
I think that release is for some Australian carrier. I don't think there's any notable difference.
[Nexus 6 Android Development] yankeesfan714:
[MENTION=3110798]WugFresh[/MENTION] all these different versions of 5.1 are supported by NRT except 47M?
[Nexus 6 Android Development] DebianDog:
Yes if Google has a factory image this tool supports it.

Sent from my Google N6 on VZ
[Nexus 6 Android Development] yankeesfan714:
I guess my question is. I don't see my build in the drop down on NRT. Can I do a flash stock and unroot using the tool if my build isn't in the list? Mine shows as "any build"
[Nexus 6 Android Development] WugFresh:
Yes, the "current build" is actually irrelevant to the flash stock operation. As long as you have selected the correct device, "Any Build" is fine.

Also, if you try to perform a task with "Any Build" that is in fact build specific - the toolkit will give you a message and not continue.
[Nexus 6 Android Development] yankeesfan714:
So if I were to do this right now on build 47M would it succeed at flashing stock 47M or would it fail? Sorry to keep bugging. I'm just not understanding.

---------- Post added at 10:26 AM ---------- Previous post was at 10:22 AM ----------

All these different build numbers have my head spinning.
[Nexus 6 Android Development] DebianDog:
I'll make it simple for you

If you can select it than it will happen or it will tell you it can't do it

Sent from my Google N6 on VZ
[Nexus 6 Android Development] yankeesfan714:
I'm new to nexus, do we know why google has made public The D, E, and I available but not the M? Is this standard?
[Nexus 6 Android Development] WugFresh:
In an ideal world, google would release the OTA's and factory packs simultaneously - however, I don't think this has ever happened. Sometimes they release the OTA first, sometime they release the factory pack first, and the delay in-between these releases seems to always vary.

In the past they have even released a factory image - only to take it down moments later, and re-post a new one with the same build (without a public notice and without updating their sites md5sum for hours). ::facepalm::

So yes. Weird timing with releases can be considered "standard". lol.

Usually the hold up's have to do with proprietary binaries, such as carrier-specific radio/basebands.

The rapid releases of 5.1.0 builds recently basically indicates that noteworthy-bugs were discovered in production/too-late, and they are scrambling to get things fixed as soon as possible. The dust will eventually settle, and there will probably be factory packs for everything.

{{ WugFresh }}
[Nexus 6 Android Development] russlowe73:
From my understanding the M version is T-Mobile build. Why google has not released a factory image, I don't know. Maybe if someone not on T-Mobile. That has tried to ADB sideload the build can answer if it works, cause only thing I can think of is it doesn't work on all carriers like the rest of the builds.
[Nexus 6 Android Development] info[]box1:
Flawlessly updated to the newest " i " build from Google image site. Had to sideload it and worked like a charm.
[Nexus 6 Android Development] Pecata:
Great! I was going to do that after I get off work. Did you use the Flash Stock + Unroot with No wipe to do that or another method?
[Nexus 6 Android Development] yankeesfan714:
I'm gonna try it after work. I'm scared ;) worst case scenario can I flash another 5.1 build if something goes wrong? Again I'm on 47M
[Nexus 6 Android Development] ANTHONY81L:
hi guys i have a pretty bad problem and I've tried everything so i figured maybe the toolkit can solve my issues. I sold my Nexus 6 to someone on Swappa. i factory reset my phone before shipping it but when he got the phone and tried activating it its asking for my gmail and password because i guess i had it connected to the Android device manager. i called google and they said that factory resetting through the boot loader or with recovery wouldn't erase the phone needing my info and it needed to be reset in the phones settings. But now the guy that bought it can't get into the settings because it won't let him passed the initial setup.. it asks for country, then wifi setup and then the screen kicks in where it needs my info. so i temporarily changed my google password and gave him the the google email and temp password but its still locked out for some reason. Google said it could take up to 72 hours because i changed the password. Anyway would this toolkit be able to wipe the phone to where it wouldn't be connected with the android device manager anymore? ill have him unroot, whatever it takes. i went to the android device manager on my computer but it can't find the phone to actually fix the problem because it was factory reseted to twrp so location services aren't even turned on.
[Nexus 6 Android Development] HipKat:
Why is everyone jumping on the I Release when it's Australian?
[Nexus 6 Android Development] info[]box1:
Cause it's the latest and greatest! That's why we went out our way get a Nexus 6 aka Shamu aka Da Apex Predator!
[Nexus 6 Android Development] TonikJDK:
No, you have to wait the 72 hours. You should have given him the current password, set it up then changed it. Now this guy has your pw for the next 72 hours. Change it again, wait 72 hours before you give it to him....so he can set up and tou can change it again after he is done.
[Nexus 6 Android Development] info[]box1:
via: Flash stock + unroot + wipe all = so fresh so clean #yass

Then unlock bootloader + root + custom recovery = bam!
[Nexus 6 Android Development] Harleydroid:
[MENTION=3110798]WugFresh[/MENTION] I want to say thanks for this amazing tool. Its been since my Galaxy Nexus that I used your NRT.
[Nexus 6 Android Development] HipKat:
That's great, if you're in Australia............
[Nexus 6 Android Development] yankeesfan714:
I could be wrong but I believe people in the states are using that build with no issue
[Nexus 6 Android Development] lioryte:
No. Can't be undone with this tool. Is a new feature called device protection. , Anyone about to sell his n6 better disable the lock screen before factory resetting or unlock the initial screen after a factory reset

http://m.pocketnow.com/2015/03/23/android-5-1-anti-theft-device-protection
[Nexus 6 Android Development] tomzefi:
Yep no issues. As a matter a fact I will be staying stock rooted for a while. Faster and more stable then any rom out. SPRINT service here
[Nexus 6 Android Development] info[]box1:
Freaking A.. That's great! I've owed every nexus known to man, for that same reason.

Riding a kangaroo at full speed right now.

Correct. I'm one of them!

Thanks
[Nexus 6 Android Development] tomzefi:
Where did you see its Australian? Its a small bug fix to the way the sim handles radio. According to the change log. Google releases are shamu period. Its an update for all and if its specific to a country or whatever then it won't affect other services. So y not flash it. It won't hurt.

---------- Post added at 10:04 PM ---------- Previous post was at 09:59 PM ----------

Here I am talking to hipkat like I no more than him. Lol. If anyone knows its you.
[Nexus 6 Android Development] info[]box1:
Ah hip hippy hipkat... :cool:
[Nexus 6 Android Development] HipKat:
That can be readily seen. Hey, if it works, great! But I'd like to see a change log before I blindly flash something that isn't even made for phones in the country I live in. That's just me as of yesterday, I hadn't seen one yet

---------- Post added at 06:31 AM ---------- Previous post was at 06:28 AM ----------

I saw it right here, 2 daysago

Nexus 6

5.0 -> 5.1 (LMY47D - Global): shamu LMY47D from LRX21O

5.0.1 -> 5.1 (LMY47D - Global): shamu LMY47D from LRX22C

5.0.1 -> 5.1 (LMY47I - Australia): shamu LMY47I from LRX22C

5.0.1 -> 5.1 (LMY47M - T-Mobile USA): shamu LMY47M from LRX22C

https://lockerdome.com/androidpolice/7526607023776020
[Nexus 6 Android Development] slider112:
There are no carrier specific builds. This is a Nexus. Any build posted on the factory images page can be flashed by any Nexus device, anywhere, anytime. It just so happens the Aussies got the 47I build first, that's all.

There is a whole lot of misinformation out there, and I get it, because Google is horrible with posting any kind of information or clarity on anything. But the "facts" that are being reported various places are just pure speculation, just like everyone else is doing, with nothing at all official from Google to back it up. Flash away, it's a Nexus.

FWIW, I'm running 47I in the USA on AT&T with absolutely no issues at all. It's a great build.