Database Users

[HowTo] Update Your Transformer Without Problems

How many of you have tried updating to a new firmware and you got the yellow exclamation mark?
Well, you probably have a combination of these modifications:
Custom Kernel
ClockworkMod Recovery
Rooted
If you have any of these, this is what you should do.
First, download and run this ONLY FOR INSTALLING/UNINSTALLING STOCK/CLOCKWORKMOD RECOVERY. - Thread
Read the instructions on how to boot into APX Mode.
Backup your /data with CWM.
After you have backed up your data, you should restore the STOCK ROM of your device.
When you get an update, it /should/ complete without any errors.
DO NOT DO ANYTHING TO THE ROM AT THIS POINT.
Alright. So at this point, you should have a completely stock, updated ROM.
Here are the next steps.
DO NOT ROOT YOUR ROM. DO NOT CHANGE A KERNEL.
Boot into APX Mode.
Make a backup of the STOCK Recovery. (Download From Linked Thread If You Haven't.)
Reboot into APX Mode.
Install ClockworkMod Recovery. (Using Brk's RootKit Script.) Once again. Without Rooting. Without changing the kernel.
Update ClockworkMod Recovery to 3.2.0.1. - Thread
Make a backup of EVERYTHING. (boot, system, data, cache, sd-ext).
After the backup is complete, you can ROOT and install a custom Kernel.
When You Get A New Update: DO NOT INSTALL. DO NOT POSTPONE.
Boot into ClockworkMod Recovery.
Restore the stock Boot.
Restore the stock System.
Boot into APX.
Restore stock recovery. (Using Brk's RootKit Script.)
Now everything should be back to stock.
Your data should still be intact.
When you apply the update, it should complete without a hitch.
Complete these steps again to be ready for the next update.
Cheers.

Thanks !! This did the trick for me. Had previously un-rooted and lost the update. Couldnt get it back until I did this !

I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks

bmcgarry67 said:
I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks
Click to expand...
Click to collapse
You should go here: http://tabletroms.com/forums/transf...stock-3-2-recovery-roms-unbricking-tools.html
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.

Thanks and follow up
The Dark Lestat said:
You should go here:
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.
Click to expand...
Click to collapse
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again

bmcgarry67 said:
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again
Click to expand...
Click to collapse
When I NVFlashed to 8.6.5.6, I could not receive the update.
Since I used the file from Asus to update, it enabled FOTA somehow.
Anyways, the guide is the same.
If 8.6.5.6 is available, then you can NVFlash 8.6.5.6, then download and update to 8.6.5.9

Thank you.
I NVFlashed to 8.6.5.6 and wiped everything.
The FOTA arrived immediately and updated flawlessly.
Thanks again

Is this update even worth unrooting then root again?

it does fix the issue with browser shortcuts. You no longer have to rotate the screen.

I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.

Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.

daoist said:
Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.
Click to expand...
Click to collapse
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.

bmcgarry67 said:
I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.
Click to expand...
Click to collapse
Has this been verified?

pigskins said:
Has this been verified?
Click to expand...
Click to collapse
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.

The Dark Lestat said:
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.
Click to expand...
Click to collapse
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?

pigskins said:
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?
Click to expand...
Click to collapse
Yes. The thread that I posted has all the updated CWM and Root methods. You can use those to root.

The Dark Lestat said:
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.
Click to expand...
Click to collapse
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.

I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.

daoist said:
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.
Click to expand...
Click to collapse
You don't have to root to use CWM. FOTA won't work with CWM.
I use Root only for setCPU and Titanium.
I like getting the update as soon as possible. Not waiting a couple days for it.
Sei911 said:
I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.
Click to expand...
Click to collapse
If you just rooted and did not make any changes to the system, then in theory, it should work. Depending on the root method.

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

ROOT!~

So yeah i installed Marshmallow on my K3 Note via the OTA update (had to replace CWM with stock recovery for it to work, but in the end it did)
Now the question is, how do i root my phone?
Will the same Lollipop process work for Marshmallow?

I dont think that method will work.

Read here: http://www.needrom.com/download/row-s422/

please help me too..!!!
shinudgr8 said:
So yeah i installed Marshmallow on my K3 Note via the OTA update (had to replace CWM with stock recovery for it to work, but in the end it did)
Now the question is, how do i root my phone?
Will the same Lollipop process work for Marshmallow?
Click to expand...
Click to collapse
i had tried everything no use.. anyone please help to root the update version... lenovo k3 note...:crying::crying::crying::crying::crying::crying:

Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start

it work well...
shinudgr8 said:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
Click to expand...
Click to collapse
no ya it works well.. but cant find a way root it....

ChainFire Beta SuperUser for Marshmallow K3 Note
Hi,
You may try the steps "androiding.how" on how to root the Lenovo K3 Note after the Marshmallow OTA update.
NOTE : THE ABOVE WOULD ONLY WORK THROUGH CWM/TWRP Recovery. Use the older Lollipop TWRP/CWM recovery. It should work.

Where is the link??

Fizix7 said:
Where is the link??
Click to expand...
Click to collapse
androiding.how is the website. Just go to the website and you will find the information on the webpage. It wont let me put the link in the post.
Hope it helps!!

massguy786 said:
androiding.how is the website. Just go to the website and you will find the information on the webpage. It wont let me put the link in the post.
Hope it helps!!
Click to expand...
Click to collapse
Interesting, never thought it could be this easy, I literally installed marshmallow the other day and now hopefully now I can root it again
So what's the final verdict boss? Did you try the process yourself? Was it successful? Or am I to be the first guinea pig?

I also got back to stock recovery from TWRP. but my update to marshmallow failed, can you help? I had rooted with Lenovo k3 note manager by prince3v. it also installed twrp. Using the same tool I went back to stock. Thanks.

shinudgr8 said:
Alright, I first updated my phone to marshmallow, then flashed twrp recovery. Until then everything was alright, it was working just fine.
Then I installed the update.zip for lollipop to root it, and installed the zip via twrp.
It resulted in my phone going into something we all know as "soft brick". It did proceed the lenovo screen, but after that I was greeted with an static black screen. ADB wasn't working either, so I couldn't boot it into bootloader or recovery. I manually booted into the recovery mode using the button sequence (volUp+volDown+power) and wiped the data. Nothing, still didn't boot. Then I finally gave up, downloaded the stock lollipop rom from somewhere, and flashed it via spflash tool. Then updated everything back to marshmallow
In short, the old twrp and cwm recoveries (probably, mostly actually) work with marshmallow, so I guess that's a start
Click to expand...
Click to collapse
That supersu file is the one causing problem. I started from scratch, and got marshmallow working. But as soon as I flash data.zip file, it gets stuck at empty black screen. It works without supersu fine, sadly no root.

shinudgr8 said:
Interesting, never thought it could be this easy, I literally installed marshmallow the other day and now hopefully now I can root it again
So what's the final verdict boss? Did you try the process yourself? Was it successful? Or am I to be the first guinea pig?
Click to expand...
Click to collapse
LOL... It will work.. You are not the Guinea pig...

Strange root / Recovery issue. Please help

Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you

The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse

Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?

Should be, but it's not safe since you do not know the current root method.

Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse

Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha

tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??

Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse

tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??

Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.

Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin

Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you

Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse

Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..

tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal

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.