Develop Bugs

[Q] Update on yakjuzs build

So I just got my Galaxy Nexus yesterday. I was doing a bit of looking around and found that the latest OTA update for the yakjuzs build was actually 4.0.2 and I'm stuck on 4.0.1. I tried several times to update, taking the sim out for wifi only each time. I'm in the US on AT&T and this is an Asian build on the unlocked GSM version but if it's through wifi I wouldn't think that would make a difference.
I don't want to flash my phone as I really got tired of that with my Galaxy S and I never learned ADB but if it's needed to get updates legitimately I wouldn't mind learning. So that said, is it necessary to flash via ADB and fastboot to the yakju build or is this update just going to mysteriously pop up unexpected-like?

I had the same problem. and turned it into yakju. and immediately received with 4.0.2

I would suggest flashing to yakju build and flash the Google 4.0.2 image. It does not take long.
Sent from my Galaxy Nexus using xda premium

It doesn't matter who updates your phone.
Not everyone gets the update at the same time. Someone can flash yakju and get the update immediately, and someone else can flash yakju and not get the update for another month. It's all luck. Updates are rolled out in batches. My friend on stock yakju just got the volume bug fix a week ago.

I'm not too concerned about having to wait so much as not knowing whether the update will even be pushed at all to my phone. It's an unlocked, gsm version with an asian build on AT&T. Besides that, from what I've read there's more to it besides just using odin with the phone in download mode. Has anyone seen a good tutorial that really details the process step by step? I looked but didn't seem to find much as most assume a working knowledge of adb which i lack.

Exinferios said:
I'm not too concerned about having to wait so much as not knowing whether the update will even be pushed at all to my phone. It's an unlocked, gsm version with an asian build on AT&T. Besides that, from what I've read there's more to it besides just using odin with the phone in download mode. Has anyone seen a good tutorial that really details the process step by step? I looked but didn't seem to find much as most assume a working knowledge of adb which i lack.
Click to expand...
Click to collapse
What? Where did you get that you won't be pushed the update? Every build will get updates.
Sent from my Galaxy Nexus using xda premium

Exinferios said:
I'm not too concerned about having to wait so much as not knowing whether the update will even be pushed at all to my phone. It's an unlocked, gsm version with an asian build on AT&T. Besides that, from what I've read there's more to it besides just using odin with the phone in download mode. Has anyone seen a good tutorial that really details the process step by step? I looked but didn't seem to find much as most assume a working knowledge of adb which i lack.
Click to expand...
Click to collapse
Like josh said, you will get the update. However, if you want a step-by-step, look at the how-to links in my signature.
Sent from my Galaxy Nexus using Tapatalk

joshnichols189 said:
What? Where did you get that you won't be pushed the update? Every build will get updates.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I had mostly chalked it up to my experience with the galaxy s which not once received an update and the one time it did was because i hacked the registry. Then the phone boot looped and i had to flash with odin.
efrant said:
Like josh said, you will get the update. However, if you want a step-by-step, look at the how-to links in my signature.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I hope you're right on that. I'll check out the tutorial you have if only for information sake for now.
Thanks everyone.

[Q] May have bricked my N7 (deb)

So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated

jahames said:
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
Click to expand...
Click to collapse
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart

StuMcBill said:
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
Click to expand...
Click to collapse
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader

jahames said:
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
Click to expand...
Click to collapse
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?

StuMcBill said:
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
Click to expand...
Click to collapse
Was working with the 4.4.2 image. Going to give the 4.4 a shot now

Same thing with 4.4...still stuck with the flo bootloader

Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?

jahames said:
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
Click to expand...
Click to collapse
You flashed a recovery for flo. Flash one for deb.
Edit:
http://techerrata.com/browse/twrp2/deb

Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!

if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.

Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app

same issue
Richieboy67 said:
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks

skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
It is here
http://www.wugfresh.com/
It is a toolkit that makes these things very easy. I have used this many times and have never had any issues with it.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
LinearEquation said:
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..

Richieboy67 said:
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Click to expand...
Click to collapse
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:

LinearEquation said:
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
Click to expand...
Click to collapse
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.

Richieboy67 said:
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Click to expand...
Click to collapse
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.

LinearEquation said:
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
Click to expand...
Click to collapse
While not disastrous, I kind of know what you mean, I started with Wug's (and it is a great toolkit), but once I flashed my own kernel (I used francos app to autoflash so did not have to use recovery or fastboot), I did not realize that by using Wug's a week later that it would flash over that kernel to run those commands and NOT replace francos (I found I was back on stock), lucky by then I had learned enough to recover and no damage was done, but it does point out that my reliance had caused me more work and a bit of worry in the long run.
Still Wug's NRT is a great toolkit...but it should be used as a tool, not a replacement for knowing what to do without it.

KK XML/FXZ is now Live! Thx to stras1234! Notice, 2 different ota's

XML.
https://drive.google.com/file/d/0Byyu7DY1fJ31cVFzSGdsb1RrOXM/edit?usp=sharing
Thanks @stras1234
From
http://forum.xda-developers.com/showthread.php?p=52747840
If you be on 98.18.94 do the OTA of the same name!
....98.30.1 do the OTA likewise.
More:
http://forum.xda-developers.com/showpost.php?p=52716429&postcount=25

I was on 98.18.94 and updated to KK 182. I froze system apps and it refused to boot. Then i RSD'd to 98.30.1 and that gave me the KK 183. update. NOTHING on the phone changed. Bootloader still unlocked and everything. I believe they're pretty much identical and it doesnt matter which update you take.

I was kind in the same situation, I was on 98.18.94, but was rooted and couldn't take the OTA. Used House of Moto to go to 98.30.1 and then was able to take OTA. I still have the original KitKat OTA Blur_Version.98.18.94.XT907.Verizon.en.US.zip that I pulled before going to 98.30.1. Are you saying I should be using that version 182.46.10.xt907 instead of 183.46.10.xt907 since I originally had the 98.18.94? Any idea what the difference is between the 2 versions?

Murph28 said:
I was kind in the same situation, I was on 98.18.94, but was rooted and couldn't take the OTA. Used House of Moto to go to 98.30.1 and then was able to take OTA. I still have the original KitKat OTA Blur_Version.98.18.94.XT907.Verizon.en.US.zip that I pulled before going to 98.30.1. Are you saying I should be using that version 182.46.10.xt907 instead of 183.46.10.xt907 since I originally had the 98.18.94? Any idea what the difference is between the 2 versions?
Click to expand...
Click to collapse
I no longer have a M. I did check the recoveries & they have different md5's.
There have been just too many borks associated with this neglect of name/build subtlety to ignore it.

Since I have the original OTA could I either down grade and apply the correct OTA or since I have an unlocked bootloader would I be able to reinstall the original without the down grade step?

Murph28 said:
Since I have the original OTA could I either down grade and apply the correct OTA or since I have an unlocked bootloader would I be able to reinstall the original without the down grade step?
Click to expand...
Click to collapse
Consult @SamuriHL
But just a do over seems best.

If you're unlocked, just downgrade using the UNIVERSAL RSD script back to 9.30.1, then install the OTA zip for 9.30.1. See here:
http://www.droidrzr.com/index.php/topic/45495-how-to-xt907-upgrade-to-kitkat-ota/

stras1234 posted the full XML for the KK update in this thread this morning.
http://forum.xda-developers.com/showthread.php?t=2751212&goto=newpost
The file is good. Folks should go and thank him.
This makes life easier and gives us a safety net...Yay!

cellzealot said:
stras1234 posted the full XML for the KK update in this thread this morning.
http://forum.xda-developers.com/showthread.php?t=2751212&goto=newpost
The file is good. Folks should go and thank him.
This makes life easier and gives us a safety net...Yay!
Click to expand...
Click to collapse
I can update my thread on droidrzr now. Thanks for checking that. No sign of the RAZR HD FXZ yet huh?

Nope, and I was told by someone who would absolutely know that they hadn't been pushed to the servers yet...
This guy popped up out of the clear blue sky and said he had the file almost as soon as the OTA started going live.
That is all I can tell you...manna from heaven...I wouldn't *****!

Click-able XML link in op.

cellzealot said:
Nope, and I was told by someone who would absolutely know that they hadn't been pushed to the servers yet...
This guy popped up out of the clear blue sky and said he had the file almost as soon as the OTA started going live.
That is all I can tell you...manna from heaven...I wouldn't *****!
Click to expand...
Click to collapse
Yes, I talked to our mutual friend about it a few days ago and was told the same thing. How stras1234 managed to acquire the FXZ so quickly is beyond me but truly amazing. We were highly skeptical when he posted that he had it on droidrzr. I guess we should have looked into it a bit further. LOL. But that's what prompted me to ask our mutual friend about it and when he said it wasn't out, my skepticism grew. Ah well. Most impressive!

SamuriHL said:
Yes, I talked to our mutual friend about it a few days ago and was told the same thing. How stras1234 managed to acquire the FXZ so quickly is beyond me but truly amazing. We were highly skeptical when he posted that he had it on droidrzr. I guess we should have looked into it a bit further. LOL. But that's what prompted me to ask our mutual friend about it and when he said it wasn't out, my skepticism grew. Ah well. Most impressive!
Click to expand...
Click to collapse
Well...it gets thickerer and thickerer...but ya, I was also rather skeptical and spoke to another friend about it and our buddy stras1234 is a resourceful fellow indeed!
I am always grateful for new sources of valuable files.

cellzealot said:
Well...it gets thickerer and thickerer...but ya, I was also rather skeptical and spoke to another friend about it and our buddy stras1234 is a resourceful fellow indeed!
I am always grateful for new sources of valuable files.
Click to expand...
Click to collapse
Hell yea! Completely appreciated. This update has been a nightmare given the multiple OTA updates depending on previous version. The FXZ makes all that go away.

SamuriHL said:
If you're unlocked, just downgrade using the UNIVERSAL RSD script back to 9.30.1, then install the OTA zip for 9.30.1. See here:
http://www.droidrzr.com/index.php/topic/45495-how-to-xt907-upgrade-to-kitkat-ota/
Click to expand...
Click to collapse
I was originally on 98.18.94 and rooted. I ended up using House of Moto to install the 98.30.1 because OTA failed. I was then able to get the OTA. The OP is saying I should be using 182.46.10.xt907 version and not 183.46.10.xt907. So if I go back to 98.30.1 can I then install the correct OTA, or is there a place to get the file to downgrade to my original version? I went to http://sbf.droid-developers.org/ and it did not have my version to download.

Murph28 said:
I was originally on 98.18.94 and rooted. I ended up using House of Moto to install the 98.30.1 because OTA failed. I was then able to get the OTA. The OP is saying I should be using 182.46.10.xt907 version and not 183.46.10.xt907. So if I go back to 98.30.1 can I then install the correct OTA, or is there a place to get the file to downgrade to my original version? I went to http://sbf.droid-developers.org/ and it did not have my version to download.
Click to expand...
Click to collapse
Since the FXZ for KK was posted, I've updated my thread with instructions on how to use it. I'd just flash that and call it good. The whole 182 vs 183 nonsense is a red herring. There's no difference between the builds except the build number and signing keys. Personally if I still had a Moto phone I'd be sticking with the FXZ path regardless of what anyone says.

im currently running KK, get kitkat from ota update and my KK version is 183.46.10. can i reflash to this FXZ??it is save? my phone is unlocked bootloader.. need your help. thank you

You CAN but the question is what do you hope to gain?
Sent from my SM-P600 using Tapatalk

SamuriHL said:
You CAN but the question is what do you hope to gain?
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I dont now why..but i found bug with version 183..sometimes i got my phone cant turn on from lockscreen..and can only fix it using hard reboot (press vol up+vol down+power in the same time)..i hope with version 182 can be solved..and another question is after ota update my model number is XT905 NOT XT907 OR Razr M..dunno why
Sent from my XT907 using XDA Free mobile app

That's odd about XT905 (since neither the Electrify M, nor the Aussie Razr M got KitKat yet - they're both can be XT905 for some reason), but yes, you could try to flash again via RSD Lite for a cleaner system. It doesn't matter if it's 182 or 183 though, as it's the same version.
OT: But for the Electrify M which is XT901 an update is announced at Moto's site now.

has the lollipop update been canceled?

I bought a Nexus 7 today went though all the updates got to 4.4 then checked for updates it told me I was up to date, I know I can just unlock the bootloader and update that way.
thought id ask since it must have a reason to being cancelled

So many threads regarding this issue.

tonyt3rry said:
I bought a Nexus 7 today went though all the updates got to 4.4 then checked for updates it told me I was up to date, I know I can just unlock the bootloader and update that way.
thought id ask since it must have a reason to being cancelled
Click to expand...
Click to collapse
There are a lot of bugs in Lollipop & that the reason why Google might have cancelled the OTA Update. If use Nexus 7 (2013), the good news is that there is a new update 5.0.2 couple of days ago. So you might be receiving the update soon

Thanks I didn't realise that there was so many threads
Sent from my Nexus 5

If you really want the Lollipop update you can use WugFresh's toolkit, you just need to click some buttons and it does everything for you.

JaimerPT said:
If you really want the Lollipop update you can use WugFresh's toolkit, you just need to click some buttons and it does everything for you.
Click to expand...
Click to collapse
Or don't use any toolkit and learn how to use fastboot and adb because they'll help you more than any toolkit.

nhizzat said:
Or don't use any toolkit and learn how to use fastboot and adb because they'll help you more than any toolkit.
Click to expand...
Click to collapse
But for someone that's new to the ecossystem of roms, its a good tool because it does everything for you.

Wugfresh Toolkit is Like Graduation at Primary School. It is necessary for everyone who steps into the world of Rooting, Roms & much more. After sometime, getting the experience, the choice is ours to do

Also, note that the Wugfresh toolkit actually logs every ADB/fastboot command it sends, so you can actually learn a lot by running it and watching it work.

Android Marshmallow G4 Root

When android Marshmallow releases will we still be able to root our devices with the low effort root available now?

cmetzger93 said:
When android Marshmallow releases will we still be able to root our devices with the low effort root available now?
Click to expand...
Click to collapse
Sure will! But I hear it'll interfere with holographic display mode. That is, assuming President Trump doesn't veto the "Holographic Display Act."
.....oops, I've said too much!

joshw0000 said:
Sure will! But I hear it'll interfere with holographic display mode. That is, assuming President Trump doesn't veto the "Holographic Display Act."
.....oops, I've said too much!
Click to expand...
Click to collapse
So much sarcasm! I assume that is a no then? Lol

cmetzger93 said:
So much sarcasm! I assume that is a no then? Lol
Click to expand...
Click to collapse
Oops, my crystal ball was acting up. Sorry I couldn't be of more help.
Sent from my VS986 using Tapatalk

I'll be the serious guy...
Theoretically (meaning I take no responsibility for what might/might not happen, and of course have not seen confirmation of this working except over Lollipop)...yes you could root with the low effort root if you're on M.
All you're doing is flashing a rooted Lollipop image over the stock one, so yeah you'd be going back to Lollipop but yeah you'd also be rooted. It's a downgrade but I suppose it would do for the time being if you really wanted root and for some reason took the M upgrade without wanting to.

Cwey55 said:
I'll be the serious guy...
Theoretically (meaning I take no responsibility for what might/might not happen, and of course have not seen confirmation of this working except over Lollipop)...yes you could root with the low effort root if you're on M.
All you're doing is flashing a rooted Lollipop image over the stock one, so yeah you'd be going back to Lollipop but yeah you'd also be rooted. It's a downgrade but I suppose it would do for the time being if you really wanted root and for some reason took the M upgrade without wanting to.
Click to expand...
Click to collapse
I appreciate the serious answer very much. It was very insightful

Cwey55 said:
I'll be the serious guy...
Theoretically (meaning I take no responsibility for what might/might not happen, and of course have not seen confirmation of this working except over Lollipop)...yes you could root with the low effort root if you're on M.
All you're doing is flashing a rooted Lollipop image over the stock one, so yeah you'd be going back to Lollipop but yeah you'd also be rooted. It's a downgrade but I suppose it would do for the time being if you really wanted root and for some reason took the M upgrade without wanting to.
Click to expand...
Click to collapse
I don't think the Lollipop image would work. Root would need to be injected into a M image.
Sent from my VS986 using Tapatalk

The reason he was being sarcastic is because there is no way to know if we can root M until it actually comes out. It's like asking if the LG G5 will be rootable, no way to know until it's out.

hollywoodS14 said:
I don't think the Lollipop image would work. Root would need to be injected into a M image.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
I tend to agree, I was just saying in theory it would work...
People used to downgrade from LP to KK with pre-rooted images.
But yeah the 100% surefire answer at this point is who freakin knows. I'm sure a root will come along eventually, just gotta give the developers some time.

In all seriousness it most likely will not work. Android M will almost certainly come with upgraded boot.img, etc and most new phones with locked bootloaders are preventing downgrading and/or preventing of unsigned images so its quite likely we will not be able to downgrade. This is my first locked LG device so I could be wrong about the G4.
Sent from my VS986 using Tapatalk

Yea no one really knows. Lollipop really made rooting complicated. Phones like the G2 and G3 were able to use older partition firmwares that were still rootable but required KitKat parts. With the G4 having stock lollipop, it was more complicated.
I suspect that we will always be able to root similarly how we did already. The USB>COM>flash a custom rooted system image should still be an option. This method is how the LG updater tool works. If they block access to that, then everything will break.
I have faith that we will be ok but like everyone said above, we won't know until it is released.

joshw0000 said:
In all seriousness it most likely will not work. Android M will almost certainly come with upgraded boot.img, etc and most new phones with locked bootloaders are preventing downgrading and/or preventing of unsigned images so its quite likely we will not be able to downgrade. This is my first locked LG device so I could be wrong about the G4.
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Does anybody know if we can install the update while already rooted on the T-Mobile variant?

Toast67 said:
Does anybody know if we can install the update while already rooted on the T-Mobile variant?
Click to expand...
Click to collapse
If that bootloader is unlocked and the good ol' legendary Chain man has a nice, sweet, hot binary in SuperSU to shove up that there thang. Then, I don't see why not. You can root through TWRP or whatever custom recovery you choose to use to overwrite the partition when you're boot scootin' boogied.

Google is really trying to lock their OS down. They make it harder to root, and now Android Pay won't work on rooted phones and they have an API for developers now to restrict or prevent use if the OS is modified.

This is a stupid question that's why it was answered sarcatically. Its a new version, so when root is out it would be posted or if someone tries the old root and it worked they would post it. Otherwise you would ask if anyone is working on the root. You basically asked if a new phone coming out if it will be rootable.
Also why are people asking tmobile questions in a verizon thread.

No root possible on verizon MM. They plugged the hole so we are no longer able to pull and push the rooted system images like we were.
The V10 is facing a similar issue and they've been at it longer. So until then, I just disabled the System Update app in settings.

ARGGGHHH
Well, We will need to Find a way to Roll Back or Root M, Guess I'm Stuck For now. (Wife decided We both needed the OTA (Last Time I sleep later than her -EVER-))

Exerp said:
Well, We will need to Find a way to Roll Back or Root M, Guess I'm Stuck For now. (Wife decided We both needed the OTA (Last Time I sleep later than her -EVER-))
Click to expand...
Click to collapse
Someone in the general thread "6.0 marshmallow is out!!!" thread mentioned that he had success downgrading.
tulio25 said:
I just successfully downgraded from 24C to 13b with LGUP (version 1.14) tool.Used 'refurbished' mode on LGUP.So,now we know:This MM upgrade is downgradable to 13B Lollipop! By the way,what a relief,didn't like MM,but that's my feeling,anyway
Click to expand...
Click to collapse

Too good to be true ?
I wonder if this works:
How to root the LG G4 VS986 Marshmallow 6.0.1
https://www.search4roots.com/how-to-easily-root-lg-g4-vs986-marshmallow-6-0-1/
Seems too good to be true if I have not read about in on XDA VS986 forum yet
The VS986 does not show up on their rootable list: https://www.oneclickroot.com/rootable/ , so I guess that page is just a teasing advertisement .....
Gosh, talk about shameless advertising .... a YouTube video showing the VS986 MM 6.0.1 too

divineBliss said:
I wonder if this works:
How to root the LG G4 VS986 Marshmallow 6.0.1
https://www.search4roots.com/how-to-easily-root-lg-g4-vs986-marshmallow-6-0-1/
Seems too good to be true if I have not read about in on XDA VS986 forum yet
The VS986 does not show up on their rootable list: https://www.oneclickroot.com/rootable/ , so I guess that page is just a teasing advertisement .....
Gosh, talk about shameless advertising .... a YouTube video showing the VS986 MM 6.0.1 too
Click to expand...
Click to collapse
its fake, if it was real you know about it. good thing you did not do it or you end up with a paper weight