Develop Bugs

workaround to the OTA 4.1.2 with red triangle signal

My phone prompted me to update to 4.1.2. Everytime I press install, it would boot and then stops half way with a red triangle icon. A few minutes later it will boot to 4.1.1. Someone suggested that it may be due to build.prop file. I mucked around with the build.prop trying to get google wallet to work. I don't care about the wallet anymore. All I want is to upgrade to 4.1.2 with no data loss.
Someone on this forum suggested using the GNex TOOLKIT V9.1 to flash Google Stock Image to phone and then the OTA update would work. If I do that, will I lost any data on the phone?
Sorry, NB to android. Thanks.

you messed with system files, the OTA will not install because of that.
you need to replace the files you modified with the original build.prop and any other files that you modified
if you want to go to stock: http://forum.xda-developers.com/showthread.php?t=1626895

Ahh ... it took me a while to get my gnex configured to the way I want. That method sounds like a clean method but at the same time will wipes everything I have configured so far.
I should probably create a second thread to ask a different question, is there a way to disable the 4.1.2 OTA notification nag? I will keep this phone for another month or so before I pass it to someone else.

If you don't care about any changes you've made to the system partition, you can just flash the boot and system images. This will keep your data.
I upgraded this way before the official OTA was out. It will, of course, blow any changes you've made to /system away, but it will keep your user data and all your settings, etc. You normally don't upgrade by "dirty flashing" over top of another system, but nobody I've seen has reported any issues with going from stock 4.1 to stock 4.1.2 this way. I did it, and have had zero issues. Always take a nandroid backup if possible, just in case.
Follow efrant's guide, just only flash boot and system (and NOT userdata)

[Q] ZVB Update Fails Every Time

I received the OTA ZVB update today, and I tried to install it using the standard OTA procedure. The device started applying the update, but it failed at about a quarter of the way through (the icon turned to a tipped over Android with a red triangle) at which point the phone rebooted and no changes were made.
I am rooted, and I have done the shutter fix (I deleted the camera_click.ogg and turned the forced shutter off in the build.prop). Besides that I haven't changed any system files. I tried replacing both files with original copies, and the update still fails. Is there anything I'm missing when it comes to updating to Jelly Bean? I was pretty sure you can update on top of root (although root will be lost) or am I mistaken and need to unroot to apply the update? Like I said, the only modifications I have done are 1. Rooting 2. build.prop edit 3. Deleted camera_click.ogg. I have reverted the build.prop and the camera_click.ogg.
Is anybody else having this problem? I searched and didn't find anything similar.
Any help would be appreciated, and if possible I would prefer not to factory reset because I have apps and things I would like to keep (I could probably back them up with Titanium though); but if that is the only option I would consider.

[You never said if you were unlocked or not, but this might be an option for you. http://forum.xda-developers.com/showpost.php?p=38558967&postcount=1
Theres a link from there to a stock zvb zip if you can use it. I'm not too sure you're gonna be able to save your stuff.
edit. If I were you, I'd unlock, run the stock zvb zip, and call it good. It's probably your best option

Ive had the same issue, tried everything including unroot. ended up reseting phone and reverting back to zv7 using lgnpst and updating software that way and it worked fine.

This is what I decided to do
stealthily said:
Ive had the same issue, tried everything including unroot. ended up reseting phone and reverting back to zv7 using lgnpst and updating software that way and it worked fine.
Click to expand...
Click to collapse
This is exactly what I'm doing right now. So far so good, I just finished installing the ZV9 update so one more to go. I'm crossing my fingers that this will work. Also, interestingly enough I didn't lose any of my files which was a huge plus!

On VS98510B, just want to upgrade to latest android, please help.

I have a VS985 LG G3. I was running marshmallow yesterday, but after trying to root and unlock mobile tethering and hotspot (because I am on unlimited data) I managed to brick my phone while typing in adb commands because my phone decided to randomly shut off. So after plugging it into the USB and figuring out a way to put it into download mode, I flashed it to VS98510B. After that, I rooted with Stump Root and installed SuperSU, following some guides. It works fine once again but I'm not where I want to be.
After multiple times trying to open adb shell and get it to just recognize my device, I'm done. I know there are people out there who know this stuff by heart, so please, at this point, just tell me what to do step by step so I can do it and move on with my life. I have spent hours upon hours on this and it never seems to just work. Please.
All I want is to be able to install the latest TWRP or whatever is recommended., and then install either the SkyDragon Rom or the stock marshmallow VS98546A rom, but with the verizon apps disabled since in one guide it warns that those report for modified device, which I am not sure what that means but it doesn't sound good.
I'm on VS98510B. Rooted and SuperSU installed.
I want to be able to use mobile hotspot and tethering.
There's just information overload to the extreme, I'm overwhelmed.
Thanks again if any help is possible.

If you're already rooted with TWRP installed, the hard part should really be over. You shouldn't need to be plugging into a computer and running adb commands at this point. You also said you need step by step instructions, and to really spell it all out would be a lot, but considering how far you already got I don't think you really need every little detail, so I'll give you the general idea then if you have questions I can try to fill those gaps.
Basically you'll need to find and download the new ROM you want. The easiest thing to do is download it directly from your phone so you don't have to mess around with transferring it from your computer to your phone. Many custom ROMs will also require Gapps, but if you're flashing a stock ROM (or a custom ROM based on stock) you don't need to do this because it's included in the ROM.
After you've downloaded the ROM (should just be a zip file), you need to reboot to recovery (TWRP). If you don't know how to do this, there's an app called Quick Reboot that can do it for you (01400) personally haven't used it but I assume it works).
Once you're in recovery, you normally want to make a backup first in case anything goes wrong. This is done by selecting the backup button. After you have a backup, you want to "wipe" data before installing. Select the wipe button, then I click advanced and select everything except internal data and external data. This will wipe all apps, settings, etc. from your phone so make sure you're ok with that before you do it,
After wiping, you're ready to install. Back at the first main screen of TWRP, select Install, then browse to where you downloaded the ROM and select it, then select the Install button and swipe to confirm. Assuming all goes well, when it's finished it'll give you the option to reboot. Do this and it should start booting up to your new ROM.
Also, you mentioned SkyDragon, but I just wanted to point out that this isn't the latest version of Android, I believe that's still Lollipop (not Marshmallow). You also mentioned not wanting your rooted status to be reported to Verizon, but if you're currently on stock, rooted, and don't have any apps disabled, then you already are running this risk.
Let me know if you have any questions. I think this will be easier than me trying to walk you through every detail and confirmation screen.

I don't have TWRP installed. What is the best course of action to take to install it?
As far as disabling verizon apps, is it as simple as just going into the application manager and disabling them or is there a tool I need to download?
Thanks for all the help so far!

I see, it's been a couple years since I installed TWRP and I was thinking it was part of the rooting process. I believe this is the post I followed to install TWRP: http://forum.xda-developers.com/lg-...mp-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
Like I said, this was a few years ago and it's kind of a one-time thing. I don't know if there's something better available now or what, and I don't remember the details. I don't remember running into any problems, so if you happened to have any I'm not sure how good I could help.
As for disabling things, the things that need to be disabled are system apps and can't just be disabled from the stock application manager (Verizon doesn't want to make it easy for you to disable their software ). There are different ways this can be done, but I personally use Titanium Backup to disable (or "freeze" as they call it) apps. It will let you freeze anything, which also means it gives you the ability to break things, so don't just go in freezing random things. I don't remember if freezing requires the paid version of the app or not, but you can get it from the play store and find out.
Sent from my VS985 4G using Tapatalk

As far as Titanium Backup goes, is it along the same lines as TWRP? Like do they do the same things? Do you recommend I do one over the other?
Also as far as verizon apps reporting root, what do they do and what does that matter?
Also, I'm currently dealing with the LG DemiGod Crash Handler problem that seems to have started up on my phone the other day. I'd never rooted or messed with my phone in any way and that started happening, I thought perhaps flashing a new ROM might fix it, but I guess not. If you have any sort of tips on how to fix that, other than replace the battery (which I have not yet done, but supposedly that can solve the problem) I'd be grateful.

Titanium Backup and TWRP are two different things. Titanium Backup is a "normal" app that you can get from the Play store, while TWRP is a custom recovery and isn't ran from within your ROM. TWRP lets you do full image backups of your phone (like your entire phone in a single backup) and can also be used to install ("flash") ROMs. Titanium Backup lets you backup, freeze, and uninstall specific apps.
I use them both because they both serve a specific purpose. You have to use TWRP to install ROMs, then as far as backups, I use TWRP to make a backup of everything in case I flash a ROM that I end up not liking (I can use the backup to easily go back to my previous ROM and still have apps and everything all setup just like they were). If I do like the new ROM I flashed, I'll use Titanium Backup to restore a lot of my apps/data to the new ROM (ex. text messages, my alarm clock app, etc.)
As far as Verizon knowing about your root status, honestly I'm not sure what all that would mean. I'm sure they wouldn't like it, rooting voids your warranty so you probably couldn't get things replaced under warranty, if you have insurance through Verizon they would maybe use your root status as a reason to deny a claim, etc. I don't think you'd have to worry about them calling you up or cancelling your service or anything like that, but getting them to assist you with problems might be more frustrating than usual
Regarding the demigod crash thing, I know what you're talking about but I don't really know much about it. A while ago I would get those every once in a while and it was frustrating. I think at the time I kind off wanted to try a new ROM anyways and I think I did but I still got it occasionally. Now that you mentioned it though I haven't had one in quite a while. I'm not sure if those ROMs both happened to cause it, if it was a Lollipop thing (doesn't seem like I've had it since Marshmallow), or if it's all just a coincidence or I've just been lucky. I haven't gotten a new battery though, so that's definitely not it (for me anyways).
Sent from my VS985 4G using Tapatalk

Help removing "dm-verity?"

Hey guys,
I've had this phone for a while; bootloader unlock/rooted a few months ago without any issues. I'm looking to sell the phone, and wanted to restore everything back to stock:
So I ODIN'd to stock CPF3. I noticed that the phone was suspiciously laggy, and found out that it's caused by spyware left behind by KingRoot, and is fixable by clearing the EFS folder from root.
So I went back to BPA1, unlcocked BL/rooted, and deleted everything from the efs folder. After reboot, phone was running good as new without any hitches.
The issue arised when I tried to ODIN flash the CPF3 full firmware provided by hsbadr. ODIN would go fine, but when the phone would reboot into the recovery, I'd get a dead Android bot saying "DRK is not installed. Please install DRK" or something along those lines. I ignored it, and the phone booted with no issues.
When I tried to factory reset from within the OS, however, I'd face the DRK and dm-verity verification failure when the phone would boot into the recovery, and it would'nt continue with the factory reset.
Now alarmed, I backed down to BPA1, and when the phone would boot back into recovery after a successful ODIN flash, the process would restart the phone when the progress bar would hit ~1/3 of completion (this happens in the recovery).
Rebooting into the recovery would show an orange "dm-verity failed," and when I try to OTA to CPD1 via external sd, It gives the "cannot update from external sd" error.
Googling the DRK keyword showed that it is KNOX being tripped that caused the issue. So far, neither Google nor the xda-forums have showed how to fix the issue on the 910-V.
I really want to restore the phone to as close-to-factory as possible, and removing this DRK issue would be a great help. Any help is greatly appreciated.
Edit #1: I have tried both this guide and this one to absolutely no avail. What am I missing? DM-Verity refuses to go away
EDIT #2: My brother also has a 910-v, and he hasn't cleared his EFS folder (stupid me for not making a back-up, eh?). Is it safe to clear mine again, and copy-paste his EFS folder into my phone? What are some adjustments I should make to avoid a corrupted IMEI? Any help is appreciated.
EDIT#3: I've tried this method, and it removes DM-verity on the first boot. It returns after factory reset. Currently trying a few different combos of flashing kernels/recoveries etc. to see if I can get it to stick. Permanently. Is it still OK to get by bro's EFS folder?

dm-verity and lagginess
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V

notsonerd said:
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V
Click to expand...
Click to collapse
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.

SirLaughsalot said:
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.
Click to expand...
Click to collapse
I have a vzw note 4 and I'm getting the dm verity verification failed when I try to a factory reset...been at this for a week so I'm pleading for help.
I posted on dr.cools attempt to fix this before I saw this post. sorry for double posting.
edit--I'm attempting the OP's number 3. will report back. Downloading BOG5 because that's what my version shows on the phonw
Question--Right now I'm stuck at BOG5. Do I need to do anything special to get to PA1 so I can start the root/unlock process again?
edit--just flashed firmware and modem and was able to do a factory reset...now back to rooting and bootloader unlock, hopefully.

Wi-Fi calling volte and carrier related (Devs-only)

I just wanted to make this thread since N update because of the issues with Wi-Fi calling and volte on international and us based roms.
This thread is for all Devs working on these issues to talk about what we have tried or may try to figure out what's going on.
To post logs of stock or custom roms to compare.
The main goal is to figure this out because we should not be limited and we can figure this out together.
If mods feel this is an inappropriate place to post this please move

Reserved

Has anyone tried to install ruu and setup with out sim card and then proceed to flash recovery and extract system?
I've been up too long some nights trying everything to figure it out. Most the logs are the same as the bugs in stock.
I think that what I seen and attempted that it's a one time thing. As in when you fresh install an ruu and it tells you to reboot . That's it. It's sets the carrier config upon that moment. This is half theory rite now.
Does anyone agree or has thought along the Same lines?

twinnfamous said:
Has anyone tried to install ruu and setup with out sim card and then proceed to flash recovery and extract system?
I've been up too long some nights trying everything to figure it out. Most the logs are the same as the bugs in stock.
I think that what I seen and attempted that it's a one time thing. As in when you fresh install an ruu and it tells you to reboot . That's it. It's sets the carrier config upon that moment. This is half theory rite now.
Does anyone agree or has thought along the Same lines?
Click to expand...
Click to collapse
Yeah same here, have tried that, no go, still doesn't work. Still will not work restoring a stock system from a working wifi calling system and volte. You have to restore stock system image for it to work again. You can root a stock system and it still works but any third party ROM does not work and restoring the system image from stock also breaks it.

Mikee4fun said:
Yeah same here, have tried that, no go, still doesn't work. Still will not work restoring a stock system from a working wifi calling system and volte. You have to restore stock system image for it to work again. You can root a stock system and it still works but any third party ROM does not work and restoring the system image from stock also breaks it.
Click to expand...
Click to collapse
I have a system.img rooted with supersu 78-sr5 that I flash via fastboot to get back to working Wi-Fi calling and volte however I don't flash boot though just system as it seems that boot.img gets written to and I'm encrypted with pin on startup.