Database Users

[Q] Upgrade Available - Rooting possible?

Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper

charlyee said:
Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
Click to expand...
Click to collapse
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...

cwburns32 said:
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...
Click to expand...
Click to collapse
Thanks, but I don't want to take the route of custom ROMs, sorry.

I had to unlock my bootloader first using RSDlite and the small .sbf file (pudding.rar) Click here to download
My bootloader was supposed to be already unlocked but I guess the updated firmware didn't realize it. I couldn't run fastboot flash without getting an error
I then rooted by flashing preinstall.img and running commands to install the superuser binary and .apk. Instructions here
I don't know of a way to root 4.5.141 without unlocking the bootloader first. If you find a way let me know

http://briefmobile.com/motorola-atrix-4g-root should work.

lauterm said:
http://briefmobile.com/motorola-atrix-4g-root should work.
Click to expand...
Click to collapse
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.

charlyee said:
Thanks, but I don't want to take the route of custom ROMs, sorry.
Click to expand...
Click to collapse
Just wondering.. Why not? ;o

nthon9 said:
Just wondering.. Why not? ;o
Click to expand...
Click to collapse
It's kind of a "Been there, done that" kind of thing from my Win Mob days. lol
I am pefectly happy with stock Atrix ROMs, and just want to be able to retain root or re root to use a couple of apps like Titanium Backup.

Has anyone with an unlocked bootloader/rooted Atrix tried the update?
I like to stick with the stock rom for now but I haven't found directions for updating to 141 yet. I'd like to keep root and not hard brick my Atrix...After the 2nd time Moto might get suspicious

I wasn't able to use the OTA updates once I rooted (even before I unlocked my bootloader). Of course, that could be Bell building in a check. I even tried unrooting (using GingerBreak) and that still wouldn't allow me to use an OTA update.
I would think you'll have to root, unlock bootloader, and then flash an firmware file from this tread: http://forum.xda-developers.com/showthread.php?t=1125944.

Actually, you're right in that the OTA update will probably fail without me going to a more "out of the box" state. I suppose I'd have to first create a nandroid, a titanium backup then flash my phone with a 4.5.91 stock image using fastboot, do the OTA, then re-root, and restore the titanium backup to get back to where I was. And if anything fails restore from my nandroid.
Does that sound right?

I've heard there could be issues relating to going back to a locked bootloader file. So I'm not sure on specifics there. I just run CyanogenMod to avoid all that stuff.

penderway said:
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.
Click to expand...
Click to collapse
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).

gnahc79 said:
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).
Click to expand...
Click to collapse
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
My bootloader was unlocked long ago but I still couldn't flash the preinstall partition without running the pudding unlock .sbf first. Idk

I wasn't even able to boot into fastboot without unlocking the bootloader first.

penderway said:
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
Click to expand...
Click to collapse
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.

I love how no one is answering your question just telling you to unlock your bootloader...

I downloaded the ota update, installed and got failed to boot 4 starting rsd node.. i had unlocked bootloader before update help please!! I pulled the battery for now.

gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Well then, that settles it. The OP (who also doesn't have an unlocked bootloader) should be able to do the same.

gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Is there any way to get step by step instructions for this

Unable to update after root

Hi
I am running on LMY47V, Version 5.1.1.
About 2 days ago i got an update of 20 MB which got downloaded into my device but failing to apply.
Whenever i Click the Restart and Install button the device gets restarted and goes into ClockworkMod Recovery v6.0.4.7 asking to fix the root access which is possibly lost . I tried both the options Yes and No then the device gets started with no update.
Then the same notification comes in asking me to Restart and Apply.
I have rooted and applied CM Recovery recently and this never happened to me before rooting.

It is normal that OTA updates do not work when rooted. There are a few workarounds, but they are not super easy (you can normally install the updates manually using adb-tools if I remember correctly).
adithyagem said:
About 2 days ago i got an update of 20 MB which got downloaded into my device but failing to apply.
I have rooted and applied CM Recovery recently and this never happened to me before rooting.
Click to expand...
Click to collapse

Yeah, to use the OTA updates you need to be completely stock. Stock ROM, locked bootloader, no root and stock recovery.

theminikiller said:
Yeah, to use the OTA updates you need to be completely stock. Stock ROM, locked bootloader, no root and stock recovery.
Click to expand...
Click to collapse
Bootloader does not have to be locked, but you are correct about everything else.

ariesgodofwar said:
Bootloader does not have to be locked, but you are correct about everything else.
Click to expand...
Click to collapse
Oh, that's good to know.

I went through this over the weekend (flashing back to stock in order to get the OTA update).
I cannot say enough good things about this Nexus Root Toolkit by WugFresh: http://www.wugfresh.com/nrt/
Made it super simple for me to flash back to stock, get that OTA update, and then flash TWRP right back (so that I could enable 4G/LTE again).

Arson Smith said:
I went through this over the weekend (flashing back to stock in order to get the OTA update).
I cannot say enough good things about this Nexus Root Toolkit by WugFresh: http://www.wugfresh.com/nrt/
Made it super simple for me to flash back to stock, get that OTA update, and then flash TWRP right back (so that I could enable 4G/LTE again).
Click to expand...
Click to collapse
I strongly recommend you learn how to use fastboot. You would not have had to flash back to stock to update. You could have flashed the system and boot images and been done with it. NRT is a good tool but you have much more flexibility if you understand what you're doing with fastboot.
Sent from my Nexus 9 using XDA Free mobile app

Downgrade from 7.1.1 to anything lower with a locked bootloader?

In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!

matistight said:
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
Click to expand...
Click to collapse
Hi... Did the bootloop came from nowhere or what were you doing when it happened?
What error do you get when you sideload the ota?
Tried formatting cache or factory reset?
Edit: You can't downgrade with a locked bootloader.

matistight said:
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
Click to expand...
Click to collapse
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.

v12xke said:
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
Click to expand...
Click to collapse
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N

matistight said:
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
Click to expand...
Click to collapse
If you erase or corrupt the bootloader then the phone is hard bricked (if it already isn't). I think you need an unlocked bootloader to do that anyways. Any flashing or erasing command in fastboot is going to need an unlocked bootloader. Even if you did somehow manage to delete the bootloader, without the phone being unlocked you can't flash a new one = hard brick.
If your phone is BL locked, you can't access Android, recovery doesn't help, you're mostly out of luck. Some people have said that using MSkips toolkit recovered their phones, but others had no such luck. There's a lot of people in the same boat as you. Others have tried calling Google about the issue despite their warranty status. Your phone is locked and a stock OTA took it out, from the sounds of it. Maybe they'll be willing to work with you. The worst they can do is say no, can't hurt to try. Good luck!

Why do you want to downgrade?

rchtk said:
Why do you want to downgrade?
Click to expand...
Click to collapse
Never really like 7.x and it has been the only OS that has bricked my phone without being rooted.

Unfortunately you can neither use an OTA to downgrade nor flash a factory image without BL unlocked.
And I'm not sure that would help either. Your device corrupted itself for a reason and that might be the flash failing (which the Nougat update exhibited, but Nougat isn't the root cause probably). You could rather wait for a higher OTA and hope.
Any recovery log to post?
How old is the phone? 1 year?

[OTA] Marshmallow Build MCG24.251-5-5

Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.

TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.

ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.

TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?

3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.

TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?

koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.

Yee!

I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk

mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795

I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia

I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.

Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.

So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?

g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store

TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk

mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.

trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.

Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason

RS988 21d OTA in the wild

The RS988 finally has a new OS update with Google patch level Dec 1st, and that means that we are finally good against blueborne and krack!
Sent from my RS988 using Tapatalk

I just installed it. It's about time. I was beginning to wonder if they had stopped support on the RS988. I hear the LG G5 is supposed to get Oreo, but I have a feeling that the RS988 will get left out based on how the updates have gone so far.

Hi! Has the modem changed?

I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?

Nispero said:
I rooted my device with SuperSU and TRWP, is it advisable install this update? Won't it remove or disable the root access?
Click to expand...
Click to collapse
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk

kattolo said:
From what I know, in order to get the ota your bootloader needs to be the stock one, but I could not find it outside of full kdz packages.
I have not rooted yet waiting for this specific update (given the security fixes).
I would suggest you to backup all of your apps and settings with an app like Titanium Backup, flash stock, install the ota, reinstall TWRP, root and magisk and then restore apps and settings from the backup
Sent from my RS988 using Tapatalk
Click to expand...
Click to collapse
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader

spinoza_web said:
Hi! Has the modem changed?
Click to expand...
Click to collapse
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info

Nispero said:
Sorry for asking, but where do I get the flash stock? I loaded SuperSU-v2.82-SR5-20171001224502.zip and TWRP-3.0.2-1-RS988.img to root after unlocking the bootloader
Click to expand...
Click to collapse
the best source of full stock roms as well as info on the phone I could find so far is https://forum.xda-developers.com/lg-g5/how-to/info-autos-g5-thread-t3350648

The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.

kattolo said:
I'm not completely sure (did not write down the previous baseband)
I'm attaching the current info
Click to expand...
Click to collapse
Here's the baseband version with RS98821c: MPSS.TH.2.0.c1.4-00047-M8996FAAAANAZM-1.88674.1.101802.1
The numbers are slightly different at the end compared to RS98821d , but I'm not sure what if anything might have changed.

maybe, for getting OTA should we just get unroot? How to do it properly?

If recovery is not the stock one, it will not be possible to install the OTA.
Alternatively you might need to wait for someone to make a flashable zip you could flash with TWRP, but given the fact development on this phone is not too active you might need to wait for a while before is available
Sent from my RS988 using Tapatalk

Awkydee said:
The way I had to update was to flash 21a and then take OTA's up to 21d because when I flashed 21c back to stock using TWRP and tried to update it gave me an error and then rebooted and said I can't update because I had rooted the device.
Click to expand...
Click to collapse
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.

brewerywagon said:
I was also planning on flashing the complete 21c zip so that I could take the 21d OTA. Glad to know that might not work.
Anyone know if it would be possible to install just the stock 21c recovery image? It's my understanding that having a custom recovery installed is what makes the OTA installation fail. If TWRP is what's getting in the way of installing the OTA, wouldn't replacing TWRP with stock recovery solve the problem without touching the system? If anyone who knows more about this stuff than me could chime in, I'd appreciate it.
Click to expand...
Click to collapse
First I flashed the magisk uninstaller and rebooted back to recovery. Then I flashed the 21c COMPLETE ZIP and didn't flash magisk so it would replace TWRP with the stock recovery on reboot. Then I rebooted and when I tried to update it went to the stock and threw up an error then rebooted. Upon reboot it displayed a message saying that I couldn't update because my device had been rooted. So I rebooted back in to bootloader and flashed TWRP again. Then I flashed 21a COMPLETE ZIP and no magisk so that the stock recovery would replace TWRP. I rebooted and went through setup and took OTA updates until I was on 21d. Then rebooted back into bootloader and flashed TWRP. Then rooted and we've through setup. I tried every other way but this was the only way that worked for me. I hope it helps!

should be an easier way. Did u see some changes to the radio?

Some of you may remember that last year I had the misfortune of installing the Brightpoint ROM on my Unlocked G5, which completely messed the phone up by not allowing it to connect to AT&T's LTE. It was a process to re-flash the older ROMs/Bootloader and then rebuild it to a stable 21c. I had used it for a while like that, and the only problem I had was that when ending a voice call (HSPA) it would take a while to change back to LTE.
I ended up going with the S8 over the summer (Samsung discount + Note 2 trade in) which got it for $18/month. I've been using it ever since and the LTE to HSPA Voice to LTE change-off on the S8 is done within a second, unlike the G5.
My mom had been using an unlocked Samsung S5 for almost a year now, and it's constantly dropping calls, and this past week it froze on her and required a battery pull, so was thinking of having her try out my (unused) G5 to see if she liked it more. When I turned the G5 on today, I updated all the apps, and then installed the 21d OTA update. The hand-off from voice to LTE still is not as fast as my S8, but seems to be improved from the 21c firmware.

ROM Posted
Just to let you all know, I have posted the latest 21d stock ROM in my thread here: https://forum.xda-developers.com/lg-g5/development/stock-21c-roms-flashable-zips-imgs-t3679907

Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.

ingressor said:
Hi. After 21d received my phone starts to rebbot when I try to play music on phone. No matter if this is stock player or google music. After self reboot music plays normally but if I click pause and wait until first stand by mode, the problem returns. Want to ask you guys to check if you have the same problem or I should download full version of 21d and check if the problem still exists. Thanks.
Click to expand...
Click to collapse
I'm not having any reboot issues when playing music.