Develop Bugs

Verizon 10/30 - Update.zip file??

Hey all, wondering if anyone has the update.zip file for the 10/30 Verizon update to Software Build: VS98511C
I have a buddy who's rooted (like me) but is receiving errors trying to install it so I'm hoping this will help. His phone is set up basically exactly the same as mine but only he has had the error and we've exhausted all possibly fixes
Thanks guys

Looking for the same.. Do we have a way to upgrade while keeping root?

I am also looking for update.zip for VS98511C.

Cyber Warrior said:
Looking for the same.. Do we have a way to upgrade while keeping root?
Click to expand...
Click to collapse
If you can update via the ota, you will keep root. I did it just fine and it's been reported from others that they haven't had a problem either. My friend's phone is having some sort of unique error that we can't figure out :/

xxxdc5 said:
If you can update via the ota, you will keep root. I did it just fine and it's been reported from others that they haven't had a problem either. My friend's phone is having some sort of unique error that we can't figure out :/
Click to expand...
Click to collapse
So you kept root while updating? No need to re-root? Any tricks like using root keeper? I never took an ota while rooted so it makes me nervous.. I always manually updated with a rooted version. I have some stuff modified and frozen.. I guess un-doing all my mods and putting things back to stock shouldnt be too much of a pain so i can take the ota. Its always been easier to just flash something though. Maybe i'll wait a few days to see if theres a better way.

If you have twrp installed and take the ota you will boot into twrp until you do a twrp terminal hack or tot/kdz back to fresh stock.

I have twrp installed also. So how do we take the update then without going into a twrp boot loop?

Cyber Warrior said:
So you kept root while updating? No need to re-root? Any tricks like using root keeper? I never took an ota while rooted so it makes me nervous.. I always manually updated with a rooted version. I have some stuff modified and frozen.. I guess un-doing all my mods and putting things back to stock shouldnt be too much of a pain so i can take the ota. Its always been easier to just flash something though. Maybe i'll wait a few days to see if theres a better way.
Click to expand...
Click to collapse
ThePagel said:
If you have twrp installed and take the ota you will boot into twrp until you do a twrp terminal hack or tot/kdz back to fresh stock.
Click to expand...
Click to collapse
marcogiudice said:
I have twrp installed also. So how do we take the update then without going into a twrp boot loop?
Click to expand...
Click to collapse
I don't have twrp installed so I'm not sure
I didn't use any tricks or special apps or anything. I saw that others took the ota while rooted and it turned out fine so I just went for it. I figured there's really no scenario I could get into that I wasn't comfortable finding a fix for so I just lazily shrugged and pushed update LOL. I didn't need to worry though as everything updated fine and normal for me.
Again though, I don't have a custom recovery installed so idk how it'll work out with twrp :/

I didnt have a custom recovery..only root with xposed and some other mods. I defrosted anything that i froze.. put back any tinkered system files..uninstalled xposed. I took the ota system update.. Everything is working great and still have root access.

[Q] Does SuperSU Pro Survival Mode work on SM-T800?

I used the KINGOROOT technique to root my SM-T800. I had to downgrade to firmware T800XXU1ANF8_T800XAR1ANF6_XAR (ANF8) to allow KINGOROOT to work.
The SM-T800 is now offering an OTA update. The only detail provided is "Size 39.96 MB" No clue what version it is.
Is there any way to determine what version of update would be loaded?
Would root be maintained?
I have purchased SuperSU Pro, and enabled "Survival Mode", which says it "attempts" to keep superuser access across OTA updates.
Can anyone confirm whether SuperSU Pro's "attempts" are actually successful on the SM-T800?

Once rooted you should disregard small updates.
You never know what this update will do. It could do anything from something simple to locking your bootloader. It won't be the first time people have ended up locked out of their device after an update.
If you really want to flash it, let it download then flash it with FLASHFIRE.

ashyx said:
Once rooted you should disregard small updates.
You never know what this update will do. It could do anything from something simple to locking your bootloader. It won't be the first time people have ended up locked out of their device after an update.
If you really want to flash it, let it download then flash it with FLASHFIRE.
Click to expand...
Click to collapse
I wasn't thinking of the small updates - I was going jump ahead and flash the latest stock Lollipop (T800XXU1BOE2_T800XAR1BOC5_XAR) Android 5.0.2?
At this point I've got the tablet usable with KitKat - thanks for all your help!
I won't have time to mess with it for a few weeks probably, so I'll defer the Lollipop update till then.
I guess I have already let it download something, although it doesn't say what. However, it is nagging me to install the OTA update all the time. So how can I
1) Capture the downloaded update file?
2) Find out what version it is so I can decide if I want it?
3) Stop the nagging to install the update?

If you're going the whole hog then just flash Lollipop with Flashfire and you'll keep root.

to Root or not to Root? Unlocked LG G4 H815

I just got my G4 Unlocked international H815 model. It's running 5.1 software on ATT. It keeps bugging me trying to OTA software update. Not sure what it's trying to update to exactly, because the only way to see more info is to hit continue with update and there's no turning back from there.
I love this phone unlocked! it didn't have any bloatware I usually root to delete when I get my phone from the carrier. It's got stuff like Wifi hotspot stock and the FM radio and charges over QI instead of Powercrap ... etc.
My question is
if it's already got most of the stuff I root to access, do I let the OTA update happen and risk not being able to root?
not sure what all I'd gain.
I'm wary about rooting because my last phone was the LG G3 and I rooted it and despite me disabling all update processes, it updated itself one day on my way to work and got screwed up so bad I had to force a downgrade and put a rom on it and after a couple days of holding a 600$ paperweight, I finally got it up and running on a rom... still had some bugs but it worked.
I REALLY want to avoid that nightmare with this 3 day old phone.
opinions welcome!
Thanks

Are you saying it's already rooted? If it is, the OTA won't work anyway. You have to unroot and flash the update using LG bridge. but then you can just root it again using the same method. The update doesn't block root. Lots of us have done it. Read the rooting threads.

G4 TweaksBox. One reason to root. ^_^

Adaway, no more adverts in apps. another (big for me) reason to root.

What version are you on now? It's probably only the stagefright fix.

Root...flash TWRP...flash cyanogen 12.1
Install xposed framework and get the YouTube adaway module. That's deffo a reason to ROOT.

Hally79 said:
Root...flash TWRP...flash cyanogen 12.1
Install xposed framework and get the YouTube adaway module. That's deffo a reason to ROOT.
Click to expand...
Click to collapse
You need an unlocked bootloader to flash TWRP / CM.
I'm running stock v10d + root. Works awesomely.

Juzman said:
You need an unlocked bootloader to flash TWRP / CM.
I'm running stock v10d + root. Works awesomely.
Click to expand...
Click to collapse
Yeah the guy said he had unlocked international h815, if he has I was just suggesting flashing CM
That's my DD and it is awesome

Hally79 said:
Yeah the guy said he had unlocked international h815, if he has I was just suggesting flashing CM
That's my DD and it is awesome
Click to expand...
Click to collapse
Yes mine's unlocked, NOT rooted. apparently the update it was trying to do automatically wasn't a big update because it decided it had waited long enough and did it on its own, rebooted and its still at
5.1
I'm still trying to wrap my head around all the terminology and methods of rooting droids- I came from the dark side- I've jailbroken every iphone since the first one they ever produced. My G3 was my first real phone, but like I said, I had it for a couple months stock, rooted it, and almost immediately it went kamikaze OTA update while rooted and went haywire. I limped by with a mediocre rom for another 8 months, until some drunk A Hole destroyed it on Halloween. I may or may not be said A Hole haha
So I guess now my question is, once rooted, am I stuck at 5.1 forever with no security updates, software patches ETC?
and since most people don't have a true unlocked phone, is this process easier to do? I'm probably asking in the wrong forum section now aren't I?

I sure hope at this point if you truly have an unlocked bootloader, that you have the latest MM version 20B installed and have root! - I find that the stock ROM is the best performing and least buggy of any of them (with some minor tweakin)

Unable to Unlock BootLoader. SOS!!!
Hi guys! need a lil help here. I have LG G4 H815. Now this is what's happening :
1. I have tried t install LG drivers a million times but in the device manager, there's always some problem with them during the installation.
2. Therefore, I'm unable to locate my phone using 'adb devices'. I'm stuck on this first step for last 1 week and I have tried every available lg driver on the internet but still the result is same.
3. I'm using Windows 8 Pro.
What's the solution here guys? Your help will highly be appreciated.

you need "disable driver signature verification" to install it
(advanced reboot options from windows)

Still stuck!
skdubg said:
you need "disable driver signature verification" to install it
(advanced reboot options from windows)
Click to expand...
Click to collapse
I did as you said and disabled the driver signature verification at restart. Uninstalled the driver and installed again but still the problem persists.
When I connect the phone, LGE Android phone appears with a yellow question mark in the device manager. When I try to update the driver, it says that
"Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device.
The system cannot find the file specified."
Still can't locate the device with adb. Please help me!

However bootloader unlock is not available for the H815P... :/
Sent from my LG-H815 using XDA-Developers mobile app

But...but...
But sir, my phone is H-815, not H-815P.
Please help me where I'm making the mistake. I want to root my phone but nothing is helping me out.

FireTV 1 unrooted?

Hi all,
I'd previously rooted, installed recovery, etc on my FireTV version 1. Everything was working great, and I thought I'd disabled updates. I turned it on recently and It somehow lost root. Everything is still installed, but can't open SuperSU, towelroot says the device isn't supported. Still says that Xposed is installed with the framework though.
The system says I'm now on 51.1.4.1_user_514013920 for some reason. Checking for system update still gives an error. What went wrong, and is there any way to fix it?
@AFTVNews, I'm mainly looking at you

Does anyone know?

If you disabled updates its probably the fact that the fire tv has updated its self, im afraid thats why su (root) isnt working & your device isn't supported because your firmware has upgraded. You have no way to root at the moment in time unless a os5 root for AFTV gen1 is created sometime in the near future? It is possible because Rbox is making a Os5 root for Gen 1.... But i think you need root already for that? My advice would be if you still want root, get a AFTV 2 while root is still possible & root/block updates & wait for the new recovery & rom being developed by Rbox which fingers crossed should be very near to be released. I still cant get over why you would want to unblock updates for when you had root & exposed framework? oh well whats done is done now.
If this helps press that thanks button

If he install clockword mod and if he can still get into it, couldn't he flash the latest rom and get root back?

That's very confusing?
Disabling updates should've been the first thing you did after rooting (presumably a long time ago if you have gen 1.)
Disabling updates, successfully or not, shouldn't've caused you to lose root. If you have CWM, your aftv should not be able to receive a stock update. Of course towel root won't work because your firmware is based on stock software that is not rootable. Are you certain you did nothing else other than disable updates?
I'm basing all of this off the assumption you have CWM. If so then just push the same firmware you currently have installed to /sdcard and flash it again. Install busybox and I'd think you'd be ok. You probably already know this but aftvnews has all rbox's prerooted roms.

Maybe you only disabled ota on your router? Have you taken it anywhere else? Or got a new router?
Sent from my SM-G900F using Tapatalk

Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...

ldeveraux said:
Yes, I disabled updates when I first rooted. I did this on the firetv, not my router. I followed @aftvnews guide to do it, and it worked perfectly. I'm not looking to get another device, but to restore this one. I still have cwm, busybox, supersu all installed (I think I still have cwm, don't remember how to boot to it). I still don't believe you can just flash a rooted rom over top...
Click to expand...
Click to collapse
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk

deanr1977 said:
If the firmware has gone to an updated latest unrootable firmware I'm sure what ever you flash onto it will brick your device even if you do have cwm?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.

ldeveraux said:
Yeah that's what I assumed. I thought it might be too far gone. Was hoping AFTVnews might see this and offer advice.
Click to expand...
Click to collapse
You're not understanding. First, the firmware you have MUST have boot menu installed. Therefore you can choose to boot recovery from there. OR connect adb and reboot recovery. Adbfire simplifies this...
You should be fine to flash a prerooted rom and it should fix whatever got messed up.
Again, theres NO way youre running stock because im fairly certain rbox's recovery wont allow the installation. Theres an issue with you su no doubt but im thinking youre still rooted.

Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.

AFTVnews.com said:
Sorry I missed this thread until now. Do you know what version pre-rooted ROM you had installed last? You say it's on 51.1.4.1, but are you positive that is not the version it was always on? If by some strange way it did install a stock update, there's no way it would have updated to 51.1.4.1 since Amazon is pushing 51.1.6.3 to all devices now. Just because you can't open SuperSU doesn't mean you lost root. What happens when you connect via ADB and enter the "su" command? Is your bootloader unlocked? Here's how to check.
Click to expand...
Click to collapse
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?

ldeveraux said:
Huh, looks like everything is still good. I ADB in and "su" still shows [email protected] I guess I still have root and unlocked bootloader. I disabled automatic updates again just in case, it says "Package com.android.dcp new state: disabled". I feel like I should update the the ROM though as my install is feeling a bit awkward. Is there a guide on AFTVnews?
EDIT: I just checked and I don't have RBOX's Boot Menu installed. Does that mean I should downgrade to 51.1.4.0, install the boot menu, then upgrade the ROM in that order?
Click to expand...
Click to collapse
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3

AFTVnews.com said:
Yes, install 51.1.4.0, then install the boot menu, then install 51.1.6.3
Click to expand...
Click to collapse
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?

ldeveraux said:
Hey cool everything works.
Only issue right now is the google play store. I installed it as in your guide, but it keeps updating and won't work at all on version 6.0.5. I saw this user UnderXP (http://forum.xda-developers.com/fire-tv/help/how-to-disable-google-play-store-auto-t3135642/page2) who used XPrivacy to stop the storee/services from auto updating. I've had no luck at it.
What do you recommend?
Click to expand...
Click to collapse
I haven't looked into the Google Play Store in a while. I plan to update my guide once Fire OS 5 is released to older devices, since any changes I make now likely won't work after the update.

System update notice

Greetings. I am already running mm on my d851 and just received an ota this morning. I have saved it and can post it too my mega off anyone wants to look at it. My question is if anyone else has gotten it yet and if it breaks our bootload/twrp?

I guess is this? - http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FWB9HI4652POATWA28CB0D6/D85130e_00_0711.kdz
Maybe July or June security patches

Probably is it. My dump its only 78mb

just received mine today .... whats this update is for ? have you updated

I have not yet, I keep telling it to remind me later since I dont want to break root/twrp

BoredKender said:
I have not yet, I keep telling it to remind me later since I dont want to break root/twrp
Click to expand...
Click to collapse
same here...

is it somekind of sec patch because i did not see any changes / improvements in it can i find details about this patch ???
---------- Post added at 07:48 PM ---------- Previous post was at 07:28 PM ----------
This update was released for the LG G3 to bring the device to android 6.0.1 with build number D85130e. This update included Google Security Enhancements, and a software stability update.

Android version is still 6.0 in this update:
Android version: 6.0
Android security patch level: 2016-07-01
Kernel version: 3.4.0
Build number: MRA58K
Software version: D85130e
Security software version: MDF v1.1 Release 2
Click to expand...
Click to collapse

Maybe this is for the quad rooter Qualcomm bugs? PS, just got mine too, waiting to see if it breaks root. If it is just updated Qualcomm drivers, maybe not.
Sent from my LG-D851 using XDA-Developers mobile app

It doesn't change the android version, kernel version, build, or security software version. I don't think that it will remove root or TWRP but I'm not trying it until someone can confirm.
Here's the issues that the update should address: https://source.android.com/security/bulletin/2016-07-01.html#security_vulnerability_summary

has anyone got any fix for that low wifi signals in MM

The update does break root and without root I can not access TWRP manager. Until a root method is found, stay away from this update.
jdmst77 said:
It doesn't change the android version, kernel version, build, or security software version. I don't think that it will remove root or TWRP but I'm not trying it until someone can confirm.
Here's the issues that the update should address: https://source.android.com/security/bulletin/2016-07-01.html#security_vulnerability_summary
Click to expand...
Click to collapse

Strange. It did not remove root for me (SU) but did blow away TWRP. I was able to re-install TWRP using the app and I was able to reboot into TWRP. So, I guess proceed at your own risk.....

I had installed "Twilight" before the update to D85130e. No problems at all but since I updated the "Screen overlay detected" don't let me use any (ANY) app that requires access to SD or SMS, so I am unable to use whatsapp, LINE, even the gallery....
I go to the permissions page and turn off and on everything but it still show up the error.
I did a hardreset and didn't work. Same error "Screen overlay detected". I cant watch videos, listen to music, etc. is just a feature phone now (unless I downgrade).
Any ideas what is going on with this problem?

mrashoo said:
has anyone got any fix for that low wifi signals in MM
Click to expand...
Click to collapse
I'm glad that I'm not the only one noticing that. I thought I had a hardware issue
jmacguire said:
The update does break root and without root I can not access TWRP manager. Until a root method is found, stay away from this update.
Click to expand...
Click to collapse
out of curiosity, what method did you use to root and are you using Chainfire's SuperSu?
boulos said:
Strange. It did not remove root for me (SU) but did blow away TWRP. I was able to re-install TWRP using the app and I was able to reboot into TWRP. So, I guess proceed at your own risk.....
Click to expand...
Click to collapse
SuperUser by the CM team or SuperSu by Chainfire or something else?

jdmst77 said:
I'm glad that I'm not the only one noticing that. I thought I had a hardware issue
out of curiosity, what method did you use to root and are you using Chainfire's SuperSu?
SuperUser by the CM team or SuperSu by Chainfire or something else?
Click to expand...
Click to collapse
SuperSU (v2.76) by ChainfireXDA

Under D, I rooted with King Root. Rebooted into TWRP and installed Chainfire's SuperSU regular. Once my phone booted, I uninstalled SuperSu and installed my pro version from the play store. So I am back to D now. Some of the cosmetic changes in E are poor so I made sure to turn off LG Update and now I do not get the nag messages about T-Mobile has an update available.
jdmst77 said:
I'm glad that I'm not the only one noticing that. I thought I had a hardware issue
out of curiosity, what method did you use to root and are you using Chainfire's SuperSu?
SuperUser by the CM team or SuperSu by Chainfire or something else?
Click to expand...
Click to collapse

jmacguire said:
Under D, I rooted with King Root. Rebooted into TWRP and installed Chainfire's SuperSU regular. Once my phone booted, I uninstalled SuperSu and installed my pro version from the play store. So I am back to D now. Some of the cosmetic changes in E are poor so I made sure to turn off LG Update and now I do not get the nag messages about T-Mobile has an update available.
Click to expand...
Click to collapse
good to hear that you still have root. losing TWRP was unexpected but since there are no kernel changes, I would have been surprised if E would unroot a device. I have the same setup as you but I haven't tried E yet. Wwith root, TWRP isn't hard to get back, just mildly annoying to have to do it again on E

I could not update the latest patch!! I have stock rooted MM Rom and custom TWRP recovery. Whenever a window pop up install update i click install and restart the phone restarts and goes to TWRP and it does not start the update process !! any body help me out from this problem how can i update ?

Should be able to force it using the LG Update tool on PC I would think