Related
Hey all,
couple of quick questions, would very much appreciate an answer.
I'm using MB525, green lens, CyanogenMod-7.1.0-jordan-Quarx, 2.6.32.9-gbc356f0 kernel and would very much like to update to 7.2.0, since it's almost been a year since I flashed the 7.1 and the defy is starting to lag a bit. The question is, do I just flash the zip from recovery and wipe it clean? I don't need to keep anything, except my contacts and I'm planning to use Titanium Backup for that (right?). Will I be able to roll back to the stock ROM? Because I've still got 1 year of warranty left on the device. Other than that, did any of you experience any serious failings of the 7.2.0? Thanks a million.
Install the froyo kernel builds for green lens. cm72 is very fast and stable, no major issues at all.
Download the zip and install through cwm, before that do full wipe. factory reset and wipe dalvik cache. For Contracts why don't you sync them with Google account and is pretty easy, otherwise you can just use export function to sdcard from settings of contacts application, and later you can import back.
Titanium backup is for application backup, not for contacts.
You can always come back to stick froyo for warranty purposes by fishing full sbf of your region. Never ever flash full sbf of higher revisions,2.3+ versions, so you keep downgradability.
Enjoy fishing!
Sent from my MB526 using XDA App
Awesome, thanks! I figured I'll go with euroskanks ROM, "update-cm-7.2.0-RC1-jordan-KANG-signed.03222012-0221.zip", since it might have several fixes that the original RC does not (amirite?). Gonna head out for couple of hours and then go on with the whole ordeal, and report back in case any other noobs come wandering in. Thanks again.
Delete cache install rom and install kernel
Sent from my MB525 using xda app
junesoung said:
Delete cache install rom and install kernel
Sent from my MB525 using xda app
Click to expand...
Click to collapse
woah, what a help you are! rrrrrrrr
HOLY **** it's flying. Didn't even have a chance to overclock it yet (1Gz as before), still at 800hz, however, it's so so snappy I could not be happier. I am not a very reliable source, though, since I only kept my contacts from the previous install, but that is just because I like it fresh, meaning, I didn't have a heart to uninstall the application I haven't been using for a while and now they're gone. Aaaaand got drunk in the meantime, which is how it's supposed to go down, I think! thanks all y'all, hugs n kisses
Hello! I have an unrooted N7 that is stuck with 4.1.1. I regularly get a notification advising me of an update & I run it through the process only to be discouraged to find I'm still stuck with 4.1.1.
Can anyone help? I don't want to root & do a bunch of crazy stuff to get the update. Is there a good fix without rooting?
FYI, I found a "fix" that required turning off WiFi, clearing the some of the systems cache, turning the WiFi back on & searching for an update. No dice...
Sent from my Nexus 7 using xda app-developers app
If you have nothing to lose your best and easiest fix would most likely be to perform a factory reset.
Cheers
Sent from my Nexus 7 using XDA Premium HD app
My N7 stuck at stock 4.1.2(JZo54K), I force clean Google Service Framework and checked update. N7 found 4.2 and downloaded 80.6mb file then restart and install. After install N7 still show 4.1.2. pleas help me.
clintjames77 said:
Hello! I have an unrooted N7 that is stuck with 4.1.1. I regularly get a notification advising me of an update & I run it through the process only to be discouraged to find I'm still stuck with 4.1.1.
Can anyone help? I don't want to root & do a bunch of crazy stuff to get the update. Is there a good fix without rooting?
FYI, I found a "fix" that required turning off WiFi, clearing the some of the systems cache, turning the WiFi back on & searching for an update. No dice...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Try applying the update. When your tablet reboots and you see the Android on your screen, hold down the power button then, while holding it down, press volume up. That'll put the stock recovery in verbose mode. When it errors out, post what the text says here.
Similar thing here.
Brand new 32gb Nexus 7, finds the 4.2 update but half way through I get a Android with a red triangle/exclamation mark which then reboots back to 4.1.2
Be happy your stuck on jelly bean 4.1.x!
Sent from my NOOK using xda app-developers app
SimonCraddock said:
Similar thing here.
Brand new 32gb Nexus 7, finds the 4.2 update but half way through I get a Android with a red triangle/exclamation mark which then reboots back to 4.1.2
Click to expand...
Click to collapse
Tried half a dozen times then did a manual forced update using this guide, easy to follow and worked first time.
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
3dwarehouse said:
Be happy your stuck on jelly bean 4.1.x!
Sent from my NOOK using xda app-developers app
Click to expand...
Click to collapse
Yes, I wanted to say this. stay on 4.1.1 or 4.1.2,.... 4.2.x is a piece of crap. Much slower, not the same device at all.
Thanks for advice, then I tried not to update to 4.2 and be happy at stucked 4.1.2
finger crossed and wait for next stable version instead.
dopodMyanmar said:
Thanks for advice, then I tried not to update to 4.2 and be happy at stucked 4.1.2
finger crossed and wait for next stable version instead.
Click to expand...
Click to collapse
4.2.1 is pretty stable, stability is not the problem, but initially it broke a lot of apps compatibility (ok, this will be solved in time), but no matter what I do I have feeling it is slower, and it stutters. I never had this with 4.1.1 or 4.1.2. And I was so happy with my Nexus until 4.2 Anyways, I had 4.2 on my original Nexus, then it died and I sent for repairs, now I have new motherboard (so it counts as different device) and factory-installed 4.2 and it is the same. Even sometimes when playing a game it just stops for a split second... Trust me, new notifications and multi user (if you're not using it) is not worth the smoothness of 4.1.1
Cheers,
D.
dalanik said:
4.2.1 is pretty stable, stability is not the problem, but initially it broke a lot of apps compatibility (ok, this will be solved in time), but no matter what I do I have feeling it is slower, and it stutters. I never had this with 4.1.1 or 4.1.2. And I was so happy with my Nexus until 4.2 Anyways, I had 4.2 on my original Nexus, then it died and I sent for repairs, now I have new motherboard (so it counts as different device) and factory-installed 4.2 and it is the same. Even sometimes when playing a game it just stops for a split second... Trust me, new notifications and multi user (if you're not using it) is not worth the smoothness of 4.1.1
Cheers,
D.
Click to expand...
Click to collapse
Thanks for reply, I'm curious to know as why my N7 stuck at 4.1.2, there may be reason as I tried several times update (reboot and installed, stuck at 4.1.2) no matter how I tried) but I'm peace in mind as 4.1.2 stability.
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
Same.
Same.
:crying:
Same.
Edit. I tried flashing the ROM by itself then booting the device. Then reboot into recovery and flash the gapps. It worked for me and I have seen others say it is hit or miss. It is worth a try though.
ernieb4768 said:
Same.
Edit. I tried flashing the ROM by itself then booting the device. Then reboot into recovery and flash the gapps. It worked for me and I have seen others say it is hit or miss. It is worth a try though.
Click to expand...
Click to collapse
This doesn't work for me... anyone got a solution? That's annoying..
Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
Did you try a clean install?
-wipe data/factory reset
-flash ROM
-flash gapps
-restart
no "restore"
If you say you had an "Older" version, does this mean you were on PAC23 (with android version 4.2.2)?
If you are on a pre-android 4.3 version of PAC, you need to do a full wipe. If you are already on a 4.3 version of PAC and you have "blame tyler" issues, try factory reset, if the problem persists, try a different nightly
Just a little curious...is the Blame Tyler error a specific error or set of errors, or does Tyler get blamed for everything?
Also, can we get Tyler's xda username, so he can get the blame he deserves :laugh:
Ninjaipod said:
I had the older version of pacman and now trying to flash the new one. I downloaded pac_jfltetmo-nightly-20131018.zip and gapps-jb-20130813-signed.zip. I reboot to recover, restore my phone, flash the ROM then Gapps. I reboot my phone and when i get to the welcome page to setup my phone i click one start and instantly a message pops up saying, "Unfortunately, Setup Wizard has stopped. Blame Tyler." I tried a dozen times and the same thing. Can anyone help please.
Click to expand...
Click to collapse
try redownloading the rom zip! and check its md5 code before flashing!!
also do a clean flash! all wipes!
if it doesnt work then even try fix permissions option !
Sent from my C6603 using Tapatalk 4
'Blame Tyler' error is just a generic message displayed when some component crashes/throws an unhandled exception, etc. It's not related to a bad ROM d/l or MD5 code. Telling people to do a full wipe b/c of an undiagnosed error condition doesn't help much. There are far too many little brokens with this ROM that need to be addressed and given more developer support, if this ROM is get more adoption.
Since RC1, nightlies have been dropping for 2 months now - no log of what's fixed or added, unless you are a dev who can wade thru the build change logs and understand what that means. It's ridiculous that we've gone this long since RC1 with a new stable release and documented fixes. Maybe this info is buried somewhere, but it's not in the Spring GS4 forum and the Pac-Man website forum is dead.
These errors are not specific to any one nightly and have been going on for months.
the tyler message is just a replacement of the force close messages. It is meant as a joke as he is one of our devs and we all take turns being blamed for breaking stuff.
If your coming from the old stable and flashing the newest nightile...comming from 4.2.2. to 4.3.1 then a full wipe is required due to the different databases and newer code that isnt compatable with the old version. This should fix your issues.
Also please dont post tylers username as its not nice to go and troll him...
I flashed the rom successfully after a full wipe this weekend. Amazeballs. I blame Tyler for making all my friends jealous of my phone.
I want to keep up with nightlies. The only thing not working for me is the wifi tether. If I have the US snapdragon quad-core variant do I want the pac-jfltetmo.zip?
Sent from my SGH-M919 using xda app-developers app
experienced the same problem and would be greatful for help
vedhed21 said:
I flashed the rom successfully after a full wipe this weekend. Amazeballs. I blame Tyler for making all my friends jealous of my phone.
I want to keep up with nightlies. The only thing not working for me is the wifi tether. If I have the US snapdragon quad-core variant do I want the pac-jfltetmo.zip?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yes, if you have the T-Mobile variant of the S4.
keyboard not working.....
Papa Smurf151 said:
the tyler message is just a replacement of the force close messages. It is meant as a joke as he is one of our devs and we all take turns being blamed for breaking stuff.
If your coming from the old stable and flashing the newest nightile...comming from 4.2.2. to 4.3.1 then a full wipe is required due to the different databases and newer code that isnt compatable with the old version. This should fix your issues.
Also please dont post tylers username as its not nice to go and troll him...
Click to expand...
Click to collapse
i have flashed your pac man rom to my galaxy sl everything went right but its keyborad was not working then i manually flashed another JB keyboard in recovery mode... then it worked ... and i flashed blackgapps(JB 4.2.2) from ENHDROIX developers and it is working quite well...
the only problem i had was keyboard stuff..
so devs should fix that issue...
GUYS THIS IS VERY STRANGE.. The nav bar at the bottom overlaps half of the dock of next launcher which makes the dock completely unusable and ugly.. the same problem persist in 50% of the other apps notably go sms, quick pic, go launchers and many others.. I have tried the milestone releases and a few latest nightlies but its still not fixed..
Its hard to believe there are many discussions of issues about pac rom going on but I didn't find this preety obvious and significant one anywhere..
I have waited like 3 months since I started with pac, updated about 5 nightlies along the way hoping it will be fixed but no luck everytime..
This one is serious.. It has forced me not to use some of my fav apps and use pie navigation at times..
No problem with all the minor bugs but this one is frustrating..
ANY IDEA GUYS??
PS. pac ver 4.3.1 on sg tab p3100 and sg3
Sent from my GT-P3100 using XDA Premium 4 mobile app
Do you know how to enable navigation bar? I saw all the settings in PAC settings>navigation bar but found no option to enable it.
Sent from my GT-P3100 using XDA Premium 4 mobile app
If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
If I flash stock kitkat my Samsung keyboard won't work (force closes over and over).. I've no problems with any custom roms, on sweetrom now with no problem.. It's not a massive issue but it's annoying me! Does anyone have any suggestions as to how to fix it?
P. S- installing SwiftKey etc isn't fixing it..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
You may need to do a full wipe when you flash stock, it's possible something has corrupted somewhere along the line.
Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
Yeah I've tried all the usual tricks, re - downloaded stock from several places with no luck.. It's baffling me..
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
..
Format all your data in system via CWM - then reinstall your ROM from scratch, it'll fix any coruption issues. ->>> Important >>> Make sure you make/get a PIT file for your device before you change anything in case you need to sort your partitions out for a reflash
I'll give it a try thank_you...
Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app
hypnodaz said:
Nope still got the same problem.. Must be some weird conflict with my phone that I can't pin down.. Like I say I'm on a custom rom anyway but it irritates me because I know it's still there...
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
How bizarre , I'd stick with the custom ROM for now just in case something else gets crazy corrupted - This Kitkat stuff atm is causing havoc all around.
Yeah I think you're right, maybe different batches of phones and buggy kitkat are causing problems for a few of us? It'll all get ironed out in the end hopefully..
Sent from my SM-N9005 using xda app-developers app
I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?
Colide said:
I got the same problem. KitKat update failed in the end and had to CF_Root in order to boot up.
Action Memo (with pen) are not working for me as well. It is all linked with Handwiting somehow.
Is your Action Memo broken also ?
The only thing that I didn't do is Wipe Data/Factory Reset in Recovery mode.
Did you try that ?
Click to expand...
Click to collapse
got the same problem as yours, no idea why though, after the update samsung keyboard and action memo stopped working.
I think I will wipe it tomorrow but it seems it's not working either
I'm checking around and they say that problem probably lies in the application S Pen Keep, there is no data on this one ... I guess as you said it's linked to the handwriting recognition. tried to do that using Snote transform into text as well and it immediately stopped working as well..
For time being I'm using different keyboard and I like it better than stock one. I really don't want to wipe a phone. Takes so much time to install everything back.
Sent from my SM-N9005 using Tapatalk
Did u guys intentionally or unintentionally uninstalled Samsung apps? From what I've understand, certain Samsung apps needs to be either freeze thru TB or disable it...
Haven't touched it. I've upgraded to KitKat without updating a bootloader and it happened.
Sent from my SM-N9005 using Tapatalk
same here, got the OTA update, after that it simply stopped working.. I don't need the keyboard .. I need the action memo more
Mine still isn't working, I'm on omega rom now so it doesn't affect me, but it still does it if I flash stock... Strange..
try to download another stock rom? maybe that will fix it.. if it did .. let us know... try to download the newest one that came up in Poland..
mine got fixed by formatting and wiping, re-download another stock rom I guess yours has some form of data missing ..
@Colide , just go back to factory settings , will resolve the issue, do it from the recovery of course.
I kinda hate it to wipe data. Lot of apps to reinstall. Thanks for a tip. ?
Sent from my SM-N9005 using Tapatalk
I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
barry123 said:
I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
Click to expand...
Click to collapse
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
deleted cache, dalvik, wiped entire phone, yes
LeftHandedWave said:
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
Click to expand...
Click to collapse
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
I've done that too in my initial flashing
flashback7 said:
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I've done that too in my initial flashing
Click to expand...
Click to collapse
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
flashback7 said:
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nope, I did a fresh install of all my apps
one7dchevy said:
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
did a hashcheck [md5] of all files as I usually do. Now I'm even having problems flashing new ROMs since in the last hour or so. I've made a backup of Pure Nexus ROM, so I know I'm able to use it, but might have to do other things here in the next couple of days to get rid of it
LeftHandedWave said:
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
flashback7 said:
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
Click to expand...
Click to collapse
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Using TWRP 2.8.7.2 wiped everything u mentioned above but unable to attach log files, no attachment box is available to me here
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
did everything u mentioned above. I've flashed my old Nexus 4 many times over the past couple of years
Use pastebin and include a link to your logs.
dodgerslim said:
Use pastebin and include a link to your logs.
Click to expand...
Click to collapse
<script src="//pastebin.com/embed_js/NHEvqKc9"></script>
BTW I've installed CM 13 and minimalistic text works flawlessly on it, no hiccups no crashes, weird!!
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
PKFR4Life said:
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
Click to expand...
Click to collapse
LOL! I've done that a few times reverting to stock and going from there. I'v had to do that in the past to get out of trouble. But seeing how I've done this countless of times over the past few years and the last phone was also a Nexus [albeit quite a change from Lollypop to Marshmallow], the rules are the same for flashing. One thing I was concerned with initially was that the vendor.img file for Pure Nexus was MMB29P but I'm on MMB29T. I don't know if that's an issue. I'm using 6.0.1 Android.
I may try it again in a few days mind you and re-flash. Will def post something if it's a positive change!!