Develop Bugs

LS990 Update Issues

hello everybody, quick question and i apologize in advance if this has been covered somewhere else or for just being a dumb question in general; I have the LG G3 from sprint and a little over a month ago i had a friend root my phone and convert it back to stock android. In anticipation for android 5.0 I removed the root. for over the past week I have been spamming the update software button and still have no lollipop. one of my good friends told me that by converting back to stock android i probably disabled the over the air updates. I was wondering about how to go about getting the updates, i have seen some posts suggesting to use the lg flash tool but I did not really comprehend how to use it. sorry if this is something stupid still really new to android.
thanks

jonsimpson93 said:
hello everybody, quick question and i apologize in advance if this has been covered somewhere else or for just being a dumb question in general; I have the LG G3 from sprint and a little over a month ago i had a friend root my phone and convert it back to stock android. In anticipation for android 5.0 I removed the root. for over the past week I have been spamming the update software button and still have no lollipop. one of my good friends told me that by converting back to stock android i probably disabled the over the air updates. I was wondering about how to go about getting the updates, i have seen some posts suggesting to use the lg flash tool but I did not really comprehend how to use it. sorry if this is something stupid still really new to android.
thanks
Click to expand...
Click to collapse
You have to put in a valid Sprint sim card for the OTA to show up

itsbighead said:
You have to put in a valid Sprint sim card for the OTA to show up
Click to expand...
Click to collapse
I already have a sprint simple card in the phone but no update, should I go get a new one?

jonsimpson93 said:
I already have a sprint simple card in the phone but no update, should I go get a new one?
Click to expand...
Click to collapse
In that case its best if you take into your local sprint store and see if they can fix it for you
I highly do not advise trying to flash the Lollipop TOT files as a fair majority of people have bricked their phone since they did not do it properly or something went wrong during the process

Brand New LG G3 Rooted

Hi I'm hoping somebody here can help me. I just bought a new LG G3 & upon further inspection of the Phone I noticed an app installed called SuperSU. I did a little digging & it turns out this Phone is rooted. I don't want to lose my Warranty or OTA updates from T-Mobile so can somebody please walk me through the steps to remove this & start fresh from stock T-Mobile Phone please.
I'm not the best at this kind of stuff so I'll need a very nice person to walk me through this or if you have a video with clear instructions. Please & Thank you.

b49adam said:
Hi I'm hoping somebody here can help me. I just bought a new LG G3 & upon further inspection of the Phone I noticed an app installed called SuperSU. I did a little digging & it turns out this Phone is rooted. I don't want to lose my Warranty or OTA updates from T-Mobile so can somebody please walk me through the steps to remove this & start fresh from stock T-Mobile Phone please.
I'm not the best at this kind of stuff so I'll need a very nice person to walk me through this or if you have a video with clear instructions. Please & Thank you.
Click to expand...
Click to collapse
This is the best way I know of going back to stock.
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Use either the KDZ or TOT method.
There is no "easy" one-click method and you are at risk of bricking your phone.
You can also try the LG Mobile Support Tool
This page is pretty easy to follow and is what I always use when refreshing my phone.
http://www.lg.com/us/mobile-phones/TMUS_Update
Good luck!

b49adam said:
Hi I'm hoping somebody here can help me. I just bought a new LG G3 & upon further inspection of the Phone I noticed an app installed called SuperSU. I did a little digging & it turns out this Phone is rooted. I don't want to lose my Warranty or OTA updates from T-Mobile so can somebody please walk me through the steps to remove this & start fresh from stock T-Mobile Phone please.
I'm not the best at this kind of stuff so I'll need a very nice person to walk me through this or if you have a video with clear instructions. Please & Thank you.
Click to expand...
Click to collapse
this cant be a "new phone" if Superuser was installed and its rooted

Having root doesn't void the warranty. Furthermore, by buying off somebody instead of a tmo rep, you already don't even have a warranty, unless Tue guy you bought it off still has one one it currently.

How to reset Note 7 to pre-OTA (back to stock)?

My wife and I have decided to hang onto our Note 7s, because why risk it with just one when you can play life in hard-mode? Sadly, she upgraded via the forced OTA, not knowing any better. Now that her battery is limited to 60%, she's extremely irritated by the popup notice she has to close every time the screen is turned on. I have tried searching, but cannot find instructions on resetting the phone back to stock (pre-OTA). Any help would be greatly appreciated. Thanks.
* Please spare this thread of the "omg you're crazy, return your bombs immediately" posts.

NarcissusV said:
My wife and I have decided to hang onto our Note 7s, because why risk it with just one when you can play life in hard-mode? Sadly, she upgraded via the forced OTA, not knowing any better. Now that her battery is limited to 60%, she's extremely irritated by the popup notice she has to close every time the screen is turned on. I have tried searching, but cannot find instructions on resetting the phone back to stock (pre-OTA). Any help would be greatly appreciated. Thanks.
* Please spare this thread of the "omg you're crazy, return your bombs immediately" posts.
Click to expand...
Click to collapse
Hi, well I won't say your crazy because I truly love my N7 and was very reluctant to do as requested and return and purchase a new phone. But I finally relented and bought the new Google Pixel Xl and have now been waiting over a month to receive it. Called Verizon last week they said I would have it Monday(yesterday), never did get it. Meanwhile I've managed to keep postponing this update I knew was the battery limiting ota for more than a week now. That is until tonight when I accidentally hit update. I am extremely pissed as I work for a government contractor and am constantly on my phone, and now must deal with only a 60% max battery to get me through a day when even a fully charged one couldn't. My only thought is maybe if I rooted the phone I would somehow be able to do something that way, perhaps by flashing the original factory software prior to the OTA. But I am just waiting on my new replacement and don' t really want to root for what could only be a day then un root to send back when my Pixel XL arrives. But it may be worth a shot on your wife's N7. Although I understand your decision to keep your N7's , as I really love mine, this deliberate hijacking of my personal property by Samsung and Verizon, has only streangthened my resolve to never purchase another Samsung phone again, I've owned every Note that has been made and as much as I love owning and using them, this will be the last time I allow them to take my money and reneder my phone useles. Samsung may not go under because of losing me as a customer, but they are definatally feeling the loss of the many who chose a different brand to replace their N7's. Good luck to you with your wife's N7. Please update if you try the root method so that others may also benefit.
Best wishes.
LvnInOC

Sadly, I believe it's impossible to revert back to 100% battery if you've already taken the update.

Get the PHE firmware from SamFirm, since SamMobile has removed all US Note 7 firmware, and use Odin to reflash it and then block the PK1 update (60% battery) with PDP or PDP+ (use manual mode to enter the package names) by disabling these 2 packages.
com.sec.android.soagent
com.samsung.sdm

Interpretation please
Woofa59 said:
Get the PHE firmware from SamFirm, since SamMobile has removed all US Note 7 firmware, and use Odin to reflash it and then block the PK1 update (60% battery) with PDP or PDP+ (use manual mode to enter the package names) by disabling these 2 packages.
com.sec.android.soagent
com.samsung.sdm
Click to expand...
Click to collapse
For those of us who have not yet learned the technical jargon, could someone help with more details about exactly how to do what you described. Is there a another thread or instructions somewhere that would detail this step-by-step for the novice? Better yet, if there is someone in the Tucson/Phoenix Arizona area who is in EXPERT at doing these and have been successful, I would be happy to pay a small success fee to have them do this for me..

garybiz said:
For those of us who have not yet learned the technical jargon, could someone help with more details about exactly how to do what you described. Is there a another thread or instructions somewhere that would detail this step-by-step for the novice? Better yet, if there is someone in the Tucson/Phoenix Arizona area who is in EXPERT at doing these and have been successful, I would be happy to pay a small success fee to have them do this for me..
Click to expand...
Click to collapse
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730

Verizon shut down service ?
chrisnosleep said:
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Click to expand...
Click to collapse
Thanks,
BUT, what is your opinion - will / can verizon stop service to all N7 phones eventually. Then all this is for nothing . What is the consensus on that one ???

chrisnosleep said:
Here's a link to what I believe he's talking about: http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ For Verizon, click the link next to the SM-N930V with the long filename. Be careful which download button you press! I downloaded the file, which is 2.66 GB, and scanned it with antivirus. FYI, I have not tried flashing the ROM yet as my phone has not been updated.
You'll also need the Odin software, which there is a link to, with instructions, towards the bottom of that page. EDIT: After looking more closely, the download link for Odin is impossible to read. Here is a better link: http://odindownload.com/download/#.WCzsCCRGZgE If none of this makes sense, dig in to the XDA forums. Everything you need is here.
Please report back if this actually works!
Also, PDP = Package Disabler Pro: http://forum.xda-developers.com/verizon-note-7/help/update-forced-to-phone-verizon-t3495730
Click to expand...
Click to collapse
Using that link, next to the SM-N930V has a link to the PHE firmware, which is precisely what I don't want, correct? If I'm correct, I'm guessing the PH1 firmware is what I would want to flash, yes? Is it as simple.? Just...flashing back the stock PH1 firmware via ODIN? I see people having issues that try and root after accepting the PHE update, so why wouldn't they be able to just do this (flash PH1 and complete the root process)?
FYI: PH1 stock firmware here: http://forum.xda-developers.com/ver...-your-verizon-note-7-and-quick-guide-t3443994

Verizon Galaxy Note 4 Battery Drain

First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.

soccerplayer00321 said:
First off, I am a newbie here, so please be kind.
I have a Samsung Galaxy Note 4 (SM-N910V), running Android 6.0.1 stock Verizon ROM.
I have been getting some strange battery issues. Not charging to 100%, shutting off at 35%, stuff like that.
I have wiped the cache partition and done a factory reset with no luck.
I have replaced the battery.
When I boot into recovery mode, I get dead Android, no command.
I don't know if the problems are related, but I suspect so.
Don't know what else to do. Any help would be appreciated.
Click to expand...
Click to collapse
Do you have an unlocked bootloader (root)? You could try reflashing twrp with odin to get recovery back.

No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.

soccerplayer00321 said:
No, not rooted. Have always been afraid to brick the device. If that is the direction that I have to go then I will give it a shot. I figure there are enough directions on here I could probably figure it out.
Click to expand...
Click to collapse
If you don't want to root, you could try flashing the cpd1 firmware with odin and that should overwrite what might be throwing off your battery calibration. Unless it's a hardware problem that is. Are you comfortable using odin? Also if you have no interest in rooting, you could flash the most recent firmware.

I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.

soccerplayer00321 said:
I am a little familiar with Odin. I used it to put Android 6.0.1 onto my phone. Cpd1? This is the first that I am hearing (or reading) anything about cpd1. I would be interested in rooting, the biggest problem that I have with doing so is that most of the instructions that I have found are written for someone who has a better grasp of this stuff that I do. Do you know of any simple step-by-step walkthroughs? One that a newbie like myself could actually follow.
From what I've read about rooting, I am definitely interested, but still paranoid about bricking the phone. I do have an S5 as a backup if need be, so I am reluctantly willing to give it a shot.
Click to expand...
Click to collapse
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!

kevintm78 said:
I was just referring to the first mm firmware that ends with cpd1 and the reason I suggested that particular one was just in case you were thinking of rooting. If you use any of the "safe" firmwares you should be ok though. I agree about the rooting process, it's not the most user friendly thing I've ever seen, but it really isn't as bad as it looks. As long as your using the files provided in those threads there really isn't a huge risk in bricking your phone. Worst case scenario, you get into a jam that takes a little while to get out of so be sure that you leave yourself time to recover in case you can't use your phone for a couple hours. I think the worst part is the instability of kingroot which means you have to do all the adb commands as quick as possible and the fact that if you want mm you have to do the root process twice. These are the two posts that got me through it:
Lollipop
Marshmallow
Start with Lp first, it's necessary to unlock that before going to mm. If your problem is software related, installing the firmwares to root should fix things. Best of luck!
Click to expand...
Click to collapse
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.

soccerplayer00321 said:
First off, thanks for your help. I appreciate it.
I finally got around to trying to do this with my phone and I can't even get past the first step. Install King Root, 4.8.5. I've tried 4.8.5 and 5.0, and neither one of them can get root access. Don't know what else to try.
Click to expand...
Click to collapse
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?

Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Sent from my SM-N910V using XDA-Developers mobile app

kevintm78 said:
Did you ever have any luck with kingroot? If you haven't tried already, do a factory reset before you start the process and if it fails uninstall, reboot, reinstall and try again. I know it's a frustrating process and it seems to take most people many tries. When it fails on you how far does it get?
Click to expand...
Click to collapse
No luck on Kingroot. It usually dies around 25% or so. Sometimes a little before that and sometimes after that. It never even got into the 35% range.
What I think I am going to do is go back to kitkat, original samsung rom. Try Kingoroot and see if that works. If not, I will push lolipop to it and try kingoroot again. If that doesn't work, I will try to push Marshmallow to it and try one more time. Hopefully one of them will be successful.

Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.

fastjohnson said:
Ive never had issues bringing a device back on OS but this N4 is kicking my a&% bad. bought a used ( basically new ) sm-n910v it was updated to 6.0.1 mm and I'm not crazy about the MM I like KK and ive tried every firmware file known to man ive tried to slowly step back from 6.0 to 5.1.1 then 5.0 then 4.4.4 and they all fail says binary fused to boot 1 or something else and with 5.1.1 gets right to the end 99% then fails. would like to root and BL unlock any suggestions would be great. thanx in advance.
Click to expand...
Click to collapse
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.

kevintm78 said:
I believe you can only get root on kk with a developer edition version of the v model. If it's a retail version and you want root it has to be at least 5.1.1 unfortunately. Have you tried the links in this post? Imo those are the best guides that I've seen to get your bootloader unlocked.
Click to expand...
Click to collapse
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.

fastjohnson said:
Yah I've tried most of them 5.1.1 gets to 98% then pooches out its exciting then bombs out, lol 4.4 doesn't get passed cache then fails. I'm using Odin 30.9, high quality data cable, thing is I can't move 》 till I can root to unlock the bootloader. My CID is 150 so that's good and I'm factory resetting the phone and pulling the SD card so it cannot mess with the flash. I'm running the NO_ A boot firmware that flashed perfect. Maybe I'm doing something wrong but I'm following the directions to the point.
Click to expand...
Click to collapse
It may not make a difference, but there is a newer version of Odin here that you could try.

kevintm78 said:
It may not make a difference, but there is a newer version of Odin here that you could try.
Click to expand...
Click to collapse
I'll give it a shot, right now I'm a Lil burned out on trying this because my other phone LG g4 is boot looped for no reason so I'm down to just my N4 and my N3 my gf has it. I forsee a big cup of coffee at 3am and let the flashing begin. Oh FYI I did try I think Odin 3.10 version it failed quicker so I'll try this version in the morning. I appreciate your help very much you'll be the 1st to know if it pushes through. Merry Christmas btw.

back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?

fz798 said:
back on topic, I'm seeing kernel wakelocks for msm_hsic_host on Oscar kernel v1.3 but I'm pretty sure that was not always the case. Since that kernel hasn't been updated in a little while, I'm looking at others. Anyone got a preferred kernel with JasmineROM 7?
Click to expand...
Click to collapse
Reflashed and thought the wakelocks were gone, but not so. msm_hsic_host appears to be related to cellular.

flyers00 said:
Kingroot was really frustrating. It would never get past 52%. After countless tries I moved to kingoroot. Kingo root worked on first try. Glad I unlocked and rooted my note 4
Click to expand...
Click to collapse
What I've noticed with this bootloader unlock is, like right now I'm 5.1.1 and my bootloader is unlocked but not rooted. OK if I use the the no A boot 6.0.1 file to flash mm it's stay unlocked and you can be rooted but if you use the normal full firmware 6.0.1 cpd1 file you lose your unlocked BL and back to start. Normally you unlock a BL it's stays unlocked no matter what you do. OK bugs with the no A boot 6.0.1 mm file no WiFi that's it. I really dislike 5.1.1 it sucks so there's not a lot of choices here. Good work on this exploit though.

Updating question

Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks

pside15 said:
Ok, I start this off with the fact that this is my first phone with the whole slot A&B thing. I've done a ton of reading but it's still very confusing to me. I'm very confused on what exactly to do when it comes to updates. I'm stock rooted with TWRP installed on slot A. I'm also on the December build. I would like to update but I don't know what the easiest way to go about it is to be honest. I feel like an idiot but I guess that's because I'm really old school when it comes to this stuff. My rooting/roming goes back to the Samsung Captivate and countless other phones up until it got to be too much of a hassle to get a phone from a carrier that could be messed with. Now that I have rambled on, I thought it would be different getting a Pixel but this whole slot thing has me all confused. I basically want to stay stock rooted for now and possibly try a kernel down the line but I'm very happy with stock for now. Any advice would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292

Badger50 said:
@Homeboy76 will get you squared away :good:
https://forum.xda-developers.com/pi...-android-9-0-pie-unlock-t3857195/post77944292
Click to expand...
Click to collapse
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.

pside15 said:
Thanks for the reply. I've read throughout that thread numerous times and I still can't determine the easiest way to update my phone and the necessary steps to take to get there. I just want to be stock rooted like I am now but don't know what steps to take to get there. Like do I need to unroot first, relock bootloader? I'm sure all those answers are in that thread but I'm probably just too dense to see them. I haven't really had a solid rooted phone in like 3 years so I'm used to things being done way different. Some times I miss my old HTC Inspire/Desire HD. There was so much development for that phone and it was all very straightforward.
Click to expand...
Click to collapse
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:

Badger50 said:
This guide is how I update the monthly security patches. It is predicated on the notion that you have the latest platform-tools (28.0.1) and that your computer and phone are communicating well. It doesn't not require you to switch slots, and it will not wipe your data, and, you do not have to unroot before you begin. Happy flashing, and good luck
And never ever ever relock the bootloader! :crying:
Click to expand...
Click to collapse
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.

pside15 said:
Awesome, thank you very much for that. Yeah, I figured that about the bootloader. Does it matter if I have TWRP installed? That's the one main confusing thing to me. How you can have TWRP installed or not installed. I'm used to absolutely having to have TWRP or some other kind of custom recovery installed. But like I said it's been quite a while since I was really able to root/ROM a phone. I was basically forced to move to AT&T and opted for the Active line of Galaxy phones since I have little kids plus even the phones that were rootable and such seemed like more of a hassle than it was worth. The last phone I had that had some good development was probably the LG G3 on T-MOBILE. For some reason the T-MOBILE version had an unlocked bootloader or could be unlocked, don't remember exactly. But then a coworker got a Pixel 2XL and I got the itch again, not knowing how much had really changed though. Ok, I think I've rambled on enough now. Thanks again for the help.
Click to expand...
Click to collapse
Doesn't matter if you have twrp installed or not. When you fastboot the update, it'll wipe it out anyway :good: