• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
  • Like
Reactions: horsecharles
Upvote 0
So pretty much this is what's going on.

If you flash the kdz for tmobile and get that small patch all you have to do is wait a few weeks or days and you'll receive the Marshmallow update for your phone.

I just received the update last night but updated this morning. It's being released slowly.

I like how the phone response time is much faster and no lag anymore is a plus.
 
  • Like
Reactions: horsecharles
Upvote 0
if you have recieved the update, please drop the boot.img system.img and recovery.img into a file hosting site and post them here or pm me with them. i'm trying to make this a twrp flashable zip for everyone.
unfortunately, the update-script mounts /system and uses patch tool to patch the system files individually. using this method takes way too long and makes it harder for things to work right (because there is more activity in the script), such as matching the md5 sum of a metro system app vs a t-mobile system app(they are also signed differently).
this member uploaded a backup he made...can you get what you need from there?

http://androidforums.com/threads/guide-how-to-root-t-mobile-6-0-update.1008880/page-2#post-7246548
 
  • Like
Reactions: horsecharles
Upvote 0
Thanks Man & Every time I Reboot the LG Logo Still Shows Bootloader Unlocked lol

Yeah I put in the OP of the root guide that it will ahow this o. The splash screen everytime you reboot. But you should be able to make sure "Enable OEM unlock" is on in devwloper optioms and boot to fastboot mode and run "fastboot oem lock" to get rid of it. But I have not tried it yet.
 
Upvote 0
Yeah I put in the OP of the root guide that it will ahow this o. The splash screen everytime you reboot. But you should be able to make sure "Enable OEM unlock" is on in devwloper optioms and boot to fastboot mode and run "fastboot oem lock" to get rid of it. But I have not tried it yet.
Ok & I Notice When I Reboot My Phone in TWRP It Always Says I'm Not Rooted & To Install Superuser Even Tho I'm Rooted
 
Upvote 0
On a friend's Metro Stylo I flashed the T-Mobile J then took the L update ota. Then set time to 11:30 and waited waited and waited. Finally I cleared Google Services Framework and LG Update Services and the MM update popped right up. That might help someone else...

Yes thank you! Finally got it after days by doing that.
 
  • Like
Reactions: hgrunwell
Upvote 0
Screenshot_2016-03-15-22-19-30.png


This can't be accurate, lol
Screenshot_2016-03-15-22-19-47.png
 
Upvote 0
It seems like if you activated developer option (setting -> about phone -> tab build number 7 times -> developer option), OTA MM update get blocked.

I tested with two Stylo phones (mine & my wife's). She immediately got MM update after 10L patch because hers not rooted + carrier locked + developer mode locked. Mine had developer option unlocked, even after 5 days no MM update.

So I KDZed again, this time didn't touch anything immediately checked system update only. 10J, 10L -> MM boom.

Now I have MM on my stylo :)


TL DR - Do not unlock developer option, just straight go to system update and apply patches and updates.
 
Upvote 0
It seems like if you activated developer option (setting -> about phone -> tab build number 7 times -> developer option), OTA MM update get blocked.

I tested with two Stylo phones (mine & my wife's). She immediately got MM update after 10L patch because hers not rooted + carrier locked + developer mode locked. Mine had developer option unlocked, even after 5 days no MM update.

So I KDZed again, this time didn't touch anything immediately checked system update only. 10J, 10L -> MM boom.

Now I have MM on my stylo :)


TL DR - Do not unlock developer option, just straight go to system update and apply patches and updates.

Developer options has nothing to do with it. It was root that caused your issue. The very first night the update was released I had flashed my T-Mobile Styli baxk to stock unrooted but had enabled developer options so I could use ADB as I had already downloaded the update.zip that had been uploaded. I wanted to try and flash it in the stick recovery and I used adb reboot recovery to boot to recovery but stock recovery on the stylo has no interface that I could use or atleast make come on screen. So this did not work. But I still got the update via OTA that night and I did have developer options enabled.
 
Upvote 0
Developer options has nothing to do with it. It was root that caused your issue. The very first night the update was released I had flashed my T-Mobile Styli baxk to stock unrooted but had enabled developer options so I could use ADB as I had already downloaded the update.zip that had been uploaded. I wanted to try and flash it in the stick recovery and I used adb reboot recovery to boot to recovery but stock recovery on the stylo has no interface that I could use or atleast make come on screen. So this did not work. But I still got the update via OTA that night and I did have developer options enabled.

Well the thing is my Stylo wasn't rooted but didn't get MM update for 5+ days.

Case1) Stock KDZed -> updated 10J, 10L -> during update I got bored so unlocked developer option -> no root touched entire process -> No MM update

Case2) Stock KDZed -> updated 10J, 10L -> didnt mess with developer option, straight to software update -> no root touched entire process -> immediate MM update


It might be something else, I remember updating LG apps and Google Default Apps on Case1) but the clear difference was whether I unlocked DEV option or not.
 
Upvote 0
Well the thing is my Stylo wasn't rooted but didn't get MM update for 5+ days.

Case1) Stock KDZed -> updated 10J, 10L -> during update I got bored so unlocked developer option -> no root touched entire process -> No MM update

Case2) Stock KDZed -> updated 10J, 10L -> didnt mess with developer option, straight to software update -> no root touched entire process -> immediate MM update


It might be something else, I remember updating LG apps and Google Default Apps on Case1) but the clear difference was whether I unlocked DEV option or not.

Do you remember what time of day ot was when you flashed the kdz file the second time? The rime is a factor as the update app only checks for updatea from 11 p.m. to 4 a.m. this is why people have to turn of the time sync in settings to trick the update app.
 
Upvote 0
Can confirm having that on has absolutely nothing to do with when you receive the update. I flashed the T-Mobile KDZ on my Metro Stylo and waited 24 hours with no success, developer options were turned on soon after I flashed the KDZ. After waiting 24 hours I flashed the T-Mobile KDZ one more time and again turned on developer options, promptly received the 10L OTA and started to set up my phone as usual. Not five minutes after downloading all my apps (developer options had been on since a little after first boot, checked for MM OTA and nothing) I checked the Software Updates section and there it was, the Marshmallow OTA.

TL;DR Developer options has nothing to do with receiving an OTA, there's no point trying to look for correlations like that, I could venture to say that to get the MM OTA you have to flash a T-Mobile KDZ and take OTA's up to 10L twice, but there's no cause and effect relationship there, just coincidence.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones