Related
I live in the Dallas area and today My tab is telling me it has in update downloaded and ready to install. I haven't done it yet for fear of losing root. Does anyone know what it could be? I can't imagine it would be the touchwiz update since the roll out doesn't start till the 5th. The only android phone I've had is a hero so I don't have much experience with ota updates. Would making a nandroid save me if I wanted to test it out?
Also just a note, my tab is rooted, as previously mentioned, but I also don't have the stock recovery, so I'm baffled as to why I would get an OTA update in the first place.
maybe it is a 11.22mb file which will add google video to your device. It may unroot your device, i also updated this file couple of days ago and it was not TW. But on the safe side you should ask more expert user. By the time i updated this file i was on stock rom with stock recovety and was unrooted. So wait for more answers and do whatever you decide.
tabing said:
maybe it is a 11.22mb file which will add google video to your device. It may unroot your device, i also updated this file couple of days ago and it was not TW. But on the safe side you should ask more expert user. By the time i updated this file i was on stock rom with stock recovety and was unrooted. So wait for more answers and do whatever you decide.
Click to expand...
Click to collapse
Yah after seeing another thread that's what I think it is. I'm not sure what Google videos would do but I've already purchased vplayer so il probably just skip it or now.
whitewillsmith28 said:
Yah after seeing another thread that's what I think it is. I'm not sure what Google videos would do but I've already purchased vplayer so il probably just skip it or now.
Click to expand...
Click to collapse
With the 11 MB update you will loose root, at least myself and others posted this, but you can easily get it back. It also locks your tab if you were previously unlocked. I would recommend reading some of the other postings on lock/unlock because it only limits one method of recovery. You can still apply (most) all of the other tweaks/ROMS/Kernals.
I live in the Fort Worth area and I am still awaiting the update........
Finally some attention from Verizon! Aside from the obvious fact that the few of us still with Vk810's, I'm also looking forward to a few of the development projects finally having what they need to complete.
http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
KDZ http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1C0KL032R7A3O65BE508U/VK81035A_08.kdz
When???
Looked at the pdf and (unless I missed it) there is no date availability indicated.
Just tried my update feature and it says my software is currently up-to-date with 24A!
Obviously verizon will do their usual "it will come when it comes"!
rant said:
Finally some attention from Verizon! Aside from the obvious fact that the few of us still with Vk810's, I'm also looking forward to a few of the development projects finally having what they need to complete.
http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
Click to expand...
Click to collapse
harryzee said:
Looked at the pdf and (unless I missed it) there is no date availability indicated.
Just tried my update feature and it says my software is currently up-to-date with 24A!
Click to expand...
Click to collapse
It's common for KDZs of official releases to be available before the OTAs get sent out. First they create the KDZ, and then they create the "diff" files necessary to OTA from the last official update (24A_00) to the newest official update. That said, I never believe that a release is official and final until everything else arrives, but that doesn't keep me from flashing it. The presence of the KDZ and of the PDF give good evidence this is final official. On the VS985 G3, we had three leaks of lollipop, 23A, 23B and 23C_00. Then the official release was 23C_01. Sometimes someone is able to get a hold of a leak's OTA file, but not for more than a few users here and there, as what happened on the VS985.
Even once the OTA is made it's very often not rolled out to everyone at once, it's staggered. So while your IMEI (and mine) might say no update, there may be other IMEIs of VK810.4Gs which do report 35A_08 as an available update. I don't think we're sure if they go in numerical order of IMEI or what determines what order they go in.
We might not see the OTA for weeks. Who knows.
You can use LG Mobile Tool 2014 (not the official LG/Verizon flash tool) on a Windows PC to flash this 35A_08 KDZ. You can try "Normal" mode which will keep your data, or "CSE" mode which will wipe everything including internal storage (not the additional Micro SD card).
roirraW "edor" ehT said:
You can use LG Mobile Tool 2014 (not the official LG/Verizon flash tool) on a Windows PC to flash this 35A_08 KDZ. You can try "Normal" mode which will keep your data, or "CSE" mode which will wipe everything including internal storage (not the additional Micro SD card).
Click to expand...
Click to collapse
It amazes me that the Verizon VK810 got this update before the V500. Although thinking back on it we did get a Korean "leak" as well...
muiriddin said:
It amazes me that the Verizon VK810 got this update before the V500. Although thinking back on it we did get a Korean "leak" as well...
Click to expand...
Click to collapse
It amazes me, too! Not expected at all. Maybe they work best when hordes aren't clamoring for an update, kinda like our generous devs here on XDA.
Update Concern
roirraW "edor" ehT said:
It amazes me, too! Not expected at all. Maybe they work best when hordes aren't clamoring for an update, kinda like our generous devs here on XDA.
Click to expand...
Click to collapse
Is anyone "concerned" over the wifi issue with the LG G3 update (5.01) that may or may not impact the gPad?
I have kept both my Lg G3 and gPad "stock" this time around and when the G3 updated a short time ago, I could connect with but no longer utilize my home wifi. I have to connect to another close by xfinity wifi in our condo unit that is open and it works fine!
There is a supposed work around that I am just too stubborn to do it as I wish to remain stock with these two units. Those of us impacted by the Verizon/LG issue (apparently "legions") are still waiting for a fix to be uploaded which as of today is still not forthcoming.
However, this experience concerns me regarding this update for the gPad unless the 5.02 has taken care of the 5.01 issue.
harryzee said:
Is anyone "concerned" over the wifi issue with the LG G3 update (5.01) that may or may not impact the gPad?
I have kept both my Lg G3 and gPad "stock" this time around and when the G3 updated a short time ago, I could connect with but no longer utilize my home wifi. I have to connect to another close by xfinity wifi in our condo unit that is open and it works fine!
There is a supposed work around that I am just too stubborn to do it as I wish to remain stock with these two units. Those of us impacted by the Verizon/LG issue (apparently "legions") are still waiting for a fix to be uploaded which as of today is still not forthcoming.
However, this experience concerns me regarding this update for the gPad unless the 5.02 has taken care of the 5.01 issue.
Click to expand...
Click to collapse
I just wanted to chime in that I likely won't be able to test whether this too will have the WIFI issue since I haven't had the issue on my Verizon G3 at home, work or elsewhere. I know it's real, I've just been lucky. Someone else will have to let us know.
You can always roll back to 24A_00 or any other KDZ though, just as on the G3.
KyPbP said:
KDZ http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW1C0KL032R7A3O65BE508U/VK81035A_08.kdz
Click to expand...
Click to collapse
<3
I installed it, seems to work fine after a cache wipe. I did lose root.
roirraW "edor" ehT said:
I just wanted to chime in that I likely won't be able to test whether this too will have the WIFI issue since I haven't had the issue on my Verizon G3 at home, work or elsewhere. I know it's real, I've just been lucky. Someone else will have to let us know.
You can always roll back to 24A_00 or any other KDZ though, just as on the G3.
Click to expand...
Click to collapse
I have been unable to have my Verizon G3 at home reproduce this issue either. I do not doubt that the problem exists, unfortunately I am unable to determine if the problem also occurs on a G-Pad (V500). I have a V500 with the Korean lollipop release installed and am testing it currently, trying to see if I am going to run the US Image stock when it is released. The wifi issue as I have read about in the Verizon G3 forums does not appear to occur for me on my wifi access points.
;60871525 said:
I installed it, seems to work fine after a cache wipe. I did lose root.
Click to expand...
Click to collapse
If you want root on 35A_08, you can roll back to (flash) the 24A KDZ, re-root with Stump, go through the brief hoopla to get TWRP installed (I've done it so many times I don't know it like the back of my hand but I'm very comfortable with it), and flash my completely stock ROM that's almost done uploading in the Development section. You WILL have to separately flash the latest SuperSU.zip by @Chainfire (detailed and links in my ROM OP) to have root before you leave your custom recovery.
I saw yesterday that the update was rolling out. Manually checked on the tablet twice this morning and it said no update available. Then, not a half an hour later I got the OTA notification. Just finished downloading and updating itself - took about 40 minutes. I did lose Root.
After I finished downloading the kdz file and checked again then I got the OTA version. It took 2-3 reboots after I finished installing before the lag went away. Now it is faster than ever.
Sent from my VK810 4G using XDA Free mobile app
Lollipop OTA Success
rfarrah said:
I saw yesterday that the update was rolling out. Manually checked on the tablet twice this morning and it said no update available. Then, not a half an hour later I got the OTA notification. Just finished downloading and updating itself - took about 40 minutes. I did lose Root.
Click to expand...
Click to collapse
My update came through this (5/21) afternoon.
Absolutely no problems or issues with the download or install.
Running smoothly with v 5.02 and with absolutely NO issues with my home wifi!
Now if only Verizon and LG would pull their collective heads for their collective orifices and put out a v. 5.02 for the LG G3 to correct the wifi issues with 5.01, I would feel my life had been fulfilled!
Absolutely no WiFi issues with the gPad update so "go figure"!
Running nicely, but work to get installed
Got it installed and it appears to be running well. I will post more when I have had some more time with it and tested more features.
I did have a tough time getting it installed, probably because I was rooted. I was getting "Err 0x13e" on the updater screen and then error 402 when it rebooted into KK and said it failed.
What I did to get it installed:
- Unrooted - still errors
- Used Verizon upgrade software to "repair" the tablet
- download LG drivers and install
- connect tablet and run installer that is mounted on Windows
- Repair stated that it would preserve data, etc., then said that method failed and it would need to erase data to repair
- Chugged for a while repairing and succeeded
- On reboot, it was still running KK and all of my data was still intact (hmmm...but good)
- Then, updated to LP with the OTA
The Verizon tool doesn't even install for me. It says installing, then it disappears.
Edit: Never mind, Lollipop's up and booting
When Nougat gets released for this phone in how ever long it takes do you think someone will eventually be able to root it on this phone?
Seriously?
joe3681 said:
Seriously?
Click to expand...
Click to collapse
you don't have to be a douche
FreshIce21 said:
you don't have to be a douche
Click to expand...
Click to collapse
You don't have to call him a douche. Honestly, I was thinking "Seriously?" as well because this is the first thing you think (rather, post of) before Nougat even comes out. We can't see the future, so this question will probably go without an indefinite answer. My input on it, though, is that root is possible if engboot still works, but if it doesn't then we're probably screwed. And I doubt engboot will work without having even MORE issues than it already does, if it even works at all.
But seriously, the name calling was unnecessary. You're the one asking the question, no need to call people names.
SkyAttacksX said:
You don't have to call him a douche. Honestly, I was thinking "Seriously?" as well because this is the first thing you think (rather, post of) before Nougat even comes out. We can't see the future, so this question will probably go without an indefinite answer. My input on it, though, is that root is possible if engboot still works, but if it doesn't then we're probably screwed. And I doubt engboot will work without having even MORE issues than it already does, if it even works at all.
But seriously, the name calling was unnecessary. You're the one asking the question, no need to call people names.
Click to expand...
Click to collapse
thank you for your reply on your thoughts about it, thats all I was looking for. The person did not have to comment "seriously" he could have just ignore my post all together, I believe he was being a douche. The commenting of "seriously" was unnecessary. I appreciate your answer as I was just curious. Have a good day
Seriously?
FreshIce21 said:
When Nougat gets released for this phone in how ever long it takes do you think someone will eventually be able to root it on this phone?
Click to expand...
Click to collapse
It'll come precisely 2 months, 1 week, 3 days, 10 hours, 30 minutes, 6 seconds and 83 milliseconds of nougat drop date
Sent from my SAMSUNG-SM-G930A using Tapatalk
So rooted MM or non-related Nougat... that will be the question
Sent from my SM-T715Y using XDA-Developers mobile app
I don't understand the reasoning behind the question. Nougat isn't even out yet. If you want root, then root your phone. If you want rooted Nougat, wait a couple days after release for someone to build a rooted ROM on it. Why would you want to flash back to stock just to root again instead of just flashing the rooted version from the beginning? I'm assuming that's why you got the "seriously?" reactions. Well, that and the fact that since Nougat hasn't even been released yet, so it's physically impossibly for anyone to know if it can be rooted. But yeah, I'd advise you to wait until someone uploads a rooted Nougat ROM for your phone instead if flashing back to stock and hoping to root that way. Its a million times easier to root it before putting it on your device
Based upon my understanding of how KNOX operates along with the stricter changes made to dm-verity in 7.0, I wouldn't hold my breath when it comes to rooting the S7. I know that the guys that come up with these rooting methods are very creative and smart, but KNOX, combined with SELinux, dm-verity, and locked bootloaders, is almost impossible to overcome. I've been looking at the people discussing the dirtyc0w exploit as an alternative root method, and I don't think it's possible to use it because of these safeguards.
We were extremely lucky with the leaked engboot method of rooting the S7. Without that, it's very possible that we still wouldn't have root on it.
Just a bit of addition to this conversation: It's likely our current root method won't work on Nougat. It depends on how different the kernels are, but since the engboot is built for MM there's no guarantee it's compatible with a new version. There's no guarantee it won't prevent flashing the engboot kernel once you're on it, and flashing a rooted system and then switching kernels won't help since the new kernel will verify the system.
I just really hope that we can get SuperSU on Nougat now that It has began to roll out today on my AT&T Galaxy S7. I've captured the ota update for it but someone else has already posted them on the forums so I won't waste my time. Despite how beautiful Nougat looks, I'm gonna wait and stick with MM. Why? Root. I'm almost certain that once you've updated to Nougat, it won't let you flash back to MM because of the locked bootloader, and for me personally, I want to keep root so bad because of the Viper4Android equalizer. The thing gives great sound quality and music wouldn't be the same without it. Honestly, If you really wanted to keep root then my advice is to stick with MM and wait (as long as it may take) for a working root method to come out for this new update.
Cheers!
KingOfTheNet said:
I just really hope that we can get SuperSU on Nougat now that It has began to roll out today on my AT&T Galaxy S7. I've captured the ota update for it but someone else has already posted them on the forums so I won't waste my time. Despite how beautiful Nougat looks, I'm gonna wait and stick with MM. Why? Root. I'm almost certain that once you've updated to Nougat, it won't let you flash back to MM because of the locked bootloader, and for me personally, I want to keep root so bad because of the Viper4Android equalizer. The thing gives great sound quality and music wouldn't be the same without it. Honestly, If you really wanted to keep root then my advice is to stick with MM and wait (as long as it may take) for a working root method to come out for this new update.
Cheers!
Click to expand...
Click to collapse
You can downgrade back to MM. Both the updates are on bootloader v4.
KingOfTheNet said:
I just really hope that we can get SuperSU on Nougat now that It has began to roll out today on my AT&T Galaxy S7. I've captured the ota update for it but someone else has already posted them on the forums so I won't waste my time. Despite how beautiful Nougat looks, I'm gonna wait and stick with MM. Why? Root. I'm almost certain that once you've updated to Nougat, it won't let you flash back to MM because of the locked bootloader, and for me personally, I want to keep root so bad because of the Viper4Android equalizer. The thing gives great sound quality and music wouldn't be the same without it. Honestly, If you really wanted to keep root then my advice is to stick with MM and wait (as long as it may take) for a working root method to come out for this new update.
Cheers!
Click to expand...
Click to collapse
Which V4A version are you using. I can't find one that works with my phone. I'm on APK1 stock rooted.
dirtydodge said:
Which V4A version are you using. I can't find one that works with my phone. I'm on APK1 stock rooted.
Click to expand...
Click to collapse
I simply downloaded and am currently using the latest update from the developers website. Be sure to download the latest version of the app listed under "Viper4Android FX" and make sure BusyBox is properly installed on your device under /system/xbin or /system/bin. I was previously on APJ4 and just upgraded to APK1 today and haven't noticed any problems.
http://vipersaudio.com/blog/?page_id=48
Cheers!
I am currently rooted with MM on my S7-Edge, SM-G935A and yesterday I got the notification from AT&T that it wanted to update my phone to the newest version of Android, Version 7 (Nougat).
I thought about UN-Rooting my phone and let the OTA finish the process and complete the upgrade. But after looking around there isn't a stable version for Root on Nougat yet for the AT&T Phone, so I think I going to wait.
But my question is if I just let OTA update the phone without Un-Rooting it, what would happen to the phone. Would it just become Un-Rooted and be an Updated Android 7.0? Or would there be problems? I can say for sure that I would not do this as I like having Root Access and I don't think I would like living without Root. But I was just curious what would really happen?
I only have one phone and don't want to mess it up, but there are a lot of people on these forums that experiment with phones all the time.
Anyway, just a question for all of you in the know.
Judging from what happened with a minor update on my at the time rooted s6e, it'll just error out before anything is done due to the engboot not being what it expects.
It checks the hashes of that file and a lot of others before applying the update from what I can tell
dragynbane222 said:
Judging from what happened with a minor update on my at the time rooted s6e, it'll just error out before anything is done due to the engboot not being what it expects.
It checks the hashes of that file and a lot of others before applying the update from what I can tell
Click to expand...
Click to collapse
Thanks for the reply. That is what I expected. I am not going to try this but like I said just curious. And you answered my question.
Again thanks.
Yup it wouldn't update.
Sent from my SM-G935V using Tapatalk
[Deleted]
I have a xt1602 with may security patch.
If I flash the earlier stock ROM would it hurt?
Will the bootloader will face any problems?
Whatever you do, just skip the bootloader part when downgrading! Other than that, there is no risk.
ProudlyTM said:
Whatever you do, just skip the bootloader part when downgrading! Other than that, there is no risk.
Click to expand...
Click to collapse
Thank you very much! Being a noob that I am, can you please tell me how can I skip it? Or point me to a tutorial that does it.
manasn said:
Thank you very much! Being a noob that I am, can you please tell me how can I skip it? Or point me to a tutorial that does it.
Click to expand...
Click to collapse
No problem! When you are flashing the stock ROM files with fastboot, just skip the fastboot flash bootloader command.
ProudlyTM said:
No problem! When you are flashing the stock ROM files with fastboot, just skip the fastboot flash bootloader command.
Click to expand...
Click to collapse
Thank you, I am just preparing myself towards rooting and having a safe way back when official nougat gets released.
manasn said:
Thank you, I am just preparing myself towards rooting and having a safe way back when official nougat gets released.
Click to expand...
Click to collapse
Just be careful if you've downgraded that you don't install an OTA update, especially if your bootloader and your system are not at the same patch level. We've seen many instances of downgraded devices being bricked as the OTA patches their newer bootloader (as the OTA appears to assume that your system is the same patch level as your bootloader), which corrupts to the point of requiring a blank flash or a motherboard replacement.
If you've downgraded, the safest way to update would be to wait for the fastboot 7.1.1 stock ROM rather than chance it with the OTA.
echo92 said:
Just be careful if you've downgraded that you don't install an OTA update, especially if your bootloader and your system are not at the same patch level. We've seen many instances of downgraded devices being bricked as the OTA patches their newer bootloader (as the OTA appears to assume that your system is the same patch level as your bootloader), which corrupts to the point of requiring a blank flash or a motherboard replacement.
If you've downgraded, the safest way to update would be to wait for the fastboot 7.1.1 stock ROM rather than chance it with the OTA.
Click to expand...
Click to collapse
Oh, thank you! You just saved a noob's device (mine) from getting bricked in future.
I went ahead yesterday and rooted my device.
Things have happened in the following manner
I purchase a moto g play xt1602 retin
I get may security patch OTA, I install it. All stock.
I unlock bootloader and flash TWRP
Take a backup of new rootless pristine system using TWRP
Root using supersufixer.zip and supersu.zip in TWRP, take another backup.
Now, my plan was as following
Stay on rooted stock, reap AdAway benefits and lower brightness below minimum(didn't happen)
Wait for Nougat OTA
When it arrives, follow https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797 this guide but just skip flashing bootloader
Boot into newly flashed stock and proceed with updates
But reading your reply makes me sure that this process will possibly brick my beloved moto g4 play. So I should either wait for may stock build or Nougat stock build zip and not apply OTA when it arrives. Am I correct?
Apologies for being so verbose but I'm sweating. I don't like sweating.
manasn said:
Oh, thank you! You just saved a noob's device (mine) from getting bricked in future.
I went ahead yesterday and rooted my device.
Things have happened in the following manner
I purchase a moto g play xt1602 retin
I unlock bootloader and flash TWRP
Root using supersufixer.zip and supersu.zip in TWRP, take another backup.
Now, my plan was as following
Stay on rooted stock, reap AdAway benefits and lower brightness below minimum(didn't happen)
When it arrives, follow https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797 this guide but just skip flashing bootloader
Boot into newly flashed stock and proceed with updates
But reading your reply makes me sure that this process will possibly brick my beloved moto g4 play. So I should either wait for may stock build or Nougat stock build zip and not apply OTA when it arrives. Am I correct?
Apologies for being so verbose but I'm sweating. I don't like sweating.
Click to expand...
Click to collapse
I followed a similar path - happily remaining on stock MM with July 2016 patch level for the last 8 months. I block OTA updates by disabling/freezing Motorola Update Service (com.motorola.ccc.ota). Simple, effective, works.
Device (XT1607) is fully unlocked, rooted and rocking Xposed with a small but potent suite of modules that brings out the best in this phone. I'm in no hurry for stock Nougat. Will update in time once migration path is clear and benefits outweigh effort/risk. I lack nothing Android 7.x brings to the table.
Don't forget to take an occasional nandroid in TWRP; store it on the SD card or off-device. Can be a life saver.
Wait - what about that ancient xxx patch level? OMG!! I'll be pwned by evilness everywhere. Relax, surf responsibly....everything will be fine.
I don't like to sweat about mundane things either. There is no reason to. Many sweaty soles are self inflicted. Don't become one of them.
Davey126 said:
I followed a similar path - happily remaining on stock MM with July 2016 patch level for the last 8 months. I block OTA updates by disabling/freezing Motorola Update Service (com.motorola.ccc.ota). Simple, effective, works.
Device (XT1607) is fully unlocked, rooted and rocking Xposed with a small but potent suite of modules that brings out the best in this phone. I'm in no hurry for stock Nougat. Will update in time once migration path is clear and benefits outweigh effort/risk. I lack nothing Android 7.x brings to the table.
Don't forget to take an occasional nandroid in TWRP; store it on the SD card or off-device. Can be a life saver.
Wait - what about that ancient 716 patch level? OMG!! I'll be pwned by evilness everywhere. Relax, surf responsibly....everything will be fine.
I don't like to sweat about mundane things either. There is no reason to. Many sweaty soles are self inflicted. Don't become one of them.
Click to expand...
Click to collapse
Okay! Haha I feel much better now, lets see what happens
manasn said:
Okay! Haha I feel much better now, lets see what happens
Click to expand...
Click to collapse
As Davey126 has mentioned, you might as well enjoy your ad-free device and treat your eyesight and not worry too much about getting the Nougat OTA. Besides, you'll want to wait to see if there are any pertinent issues with the 7.1.1 update (even with the soak test, some bugs might still emerge in wider deployment), which you may avoid if you don't need to upgrade to the newest patch
Furthermore, mods like xposed don't work fully on Nougat (rovo89 hasn't released an official xposed, and the unofficial builds are still hit and miss), so Marshmallow might be more for you if you really like to customise. As for being behind on security patches, I concur with Davey126 that as long as you're sensible about where you download and install APKs from, you should be in good stead. Security patches are nice, due diligence and being aware about what you're putting on your device is crucial to staying safe.
In other words, enjoy the flexibility of your rooted device and when the fastboot Nougat ROM comes out, then you can think about whether you wish to update or wait for any bugs to be ironed out. Alternatively, I'm sure someone will release a TWRP flashable build of the stock 7.1.1 (which shouldn't touch your bootloader/GPT anyway, so should be safe to use). Either way, waiting will mean you don't risk your bootloader or GPT and still have a device you can enjoy