Database Info

How the heck do I stop OTA update?

I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks

jasondhsd said:
I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks
Click to expand...
Click to collapse
Flash a custom recovery/ROM. That should do it
But I'm not sure what else if the fwupgrade freeze didn't work

Yes. How do I stop this crap!?
I have 2 of these both rooted and hers keeps trying to install it. Its already downloaded on hers. I interrupted mine by killing the internet connection as soon as I saw it start downloading.
I'm sure when I'm sleeping it will try to install itself. So ill just shut my phone off.
Grr...

I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.

jasondhsd said:
I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.
Click to expand...
Click to collapse
Thats an issue with no-sympathy.... Most ROM's block the OTAs so you don't even need to worry about them.
This is actually the first ROM i've heard of that allows OTA's to even show up on the prompts.

Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?

jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
You would have to ask the ROM's developers. Refuse it, and flash to another ROM that does it automatically for you. Obviously No Sympathy didn't think of an OTA... whynot I dunno. But every other developer did.

jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
Install an old version of synergy?

Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.

jasondhsd said:
Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.
Click to expand...
Click to collapse
I just did that. sdm 1.0 frozen. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from my Land Line using xda premium

Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.

Blue6IX said:
Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.
Click to expand...
Click to collapse
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...

shuura said:
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...
Click to expand...
Click to collapse
So far so good on freezing SDM. We'll see tomorrow morning.

[Q] Unable to get back to stock

I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse

TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks

I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.

nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.

dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.

nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?

dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.

nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?

dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM

back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks

empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.

unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?

empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845

not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?

Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.

empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...

nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.

jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?

[Q] How to take OTA update after Sunshine

Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!

Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!

Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!

Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.

The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...

Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!

I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!

berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.

Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img

Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app

mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.

Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!

I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.

Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.

I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.

Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!

I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!

Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol

Is 21r rootable?

So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?

shxrm_ said:
So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
Click to expand...
Click to collapse
I have the same question. According to the release notes for 21r, the purpose was to update security. It appears that this is the stagefright patch.
EDIT: Appears to still be rootable.

There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.

aybarrap1 said:
I have the same question. According to the release notes for 21r, the purpose was to update security. I hate to think that AT&T might have intentionally worked to prevent rooting and Bump'd. Would not surprise me. AT&T has strangely been releasing a lot of updates over the last 6 months or so which is very unlike them. I have to wonder if they have not been working to prevent rooting as rooting has become harder and harder.
Click to expand...
Click to collapse
That's literally the only reason why I'm still on 20f, and usually I would just update my phone right away to get the security. I just wanted to know if it's possible

autosurgeon said:
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
Click to expand...
Click to collapse
I see your point.

21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk

The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.

pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Hopefully it works for me, cause people said root worked for them on 21q, but it never worked for me

pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Looks like I will go through the long process of unrooting now. Been avoiding the OTAs since lollipop update because of the hassle of having to unroot. I am glad to see that AT&T actually worked quickly with LG on patching stagefright. Being able to root again was a main concern.
UPDATE: Thus far, after backing up all my data and apps (I use both LGs backup and TiBu to do batch backups), I have downgraded to stock unroot, and it took 3 OTAs (21f, 21q, and 21r) to get to where I am at. The unroot method only took about 10 minutes but I already had everything set up from my previous upgrade to Lollipop. The OTA updates were painful as they took a while to download and install (700+mB, 205mB, and 23mB respectively so about 1gig of wifi data) along with the optimization of apps each time. I have now successfully rooted.

Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues

Firebourne said:
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Click to expand...
Click to collapse
Thanks for the confirmation of root as well as the the exact method that worked for you. I will be giving this a shot this afternoon. I want to take advantage of the stagefright patch while keeping root.
UPDATE: This root method worked. Had to do it twice but got it working.

Mjengles said:
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.

It still refuses to work for me. I didn't change the diag port from when I restored back to stock, and I've tried it a few times just now, all to no effect.
Edit: the thing finally worked for me! I just closed the command prompt after the "send_command" part didn't work for me, and just did that part over, and it worked!!

CAUTION!!!!
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh

shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol

shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
You don't need to start all over. Just install the Gabriel kernel in twrp and you are good.
Sent from my LG-D850 using XDA Free mobile app
---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------
Firebourne said:
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
Click to expand...
Click to collapse
That only refers to secure boot errors booting twrp not booting the phone.
Sent from my LG-D850 using XDA Free mobile app

Link please? I searched the development threads, but didn't find the kernel you mentioned

shxrm_ said:
Link please? I searched the development threads, but didn't find the kernel you mentioned
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/lollipopstockkernelgabriel5-d855-t3120893

aybarrap1 said:
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
Click to expand...
Click to collapse
Second method of rooting worked for me. Hello control.....goodbye warranty
Sent from my ASUS MeMO Pad 7 using Tapatalk

Is there a bootable zip of the lastest stock Att ROM? Thanks.

Oreo 8.1 out of Beta!!!

FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.

electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!

electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.

Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.

Updating now!!!

dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.

The fact that it was not released to beta first makes me think it may just be an official release of the beta

crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.

I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.

dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!

epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are

tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.

GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....

NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)

Wonder if Essential pushed it since Pixel is now offering pre release of Android P?

My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice

GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.

Can anyone tell me if stable has multitouch issues that were on beta?

Rooted 7.1.1 took the update just fine, lost root and twrp

Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.