Do we get update Android N if our device is rooted?
Or we have to flash stock rom..?
Rakesh8857 said:
Do we get update Android N if our device is rooted?
Or we have to flash stock rom..?
Click to expand...
Click to collapse
You will get an update notification.. But to apply that update you need to have the stock recovery installed..
Sent from my Moto G4 Plus using Tapatalk.
zazzy24 said:
You will get an update notification.. But to apply that update you need to have the stock recovery installed..
Sent from my Moto G4 Plus using Tapatalk.
Click to expand...
Click to collapse
Even if you have the stock recovery flashed, the update will fail if your device is rooted.
xtermmin said:
Even if you have the stock recovery flashed, the update will fail if your device is rooted.
Click to expand...
Click to collapse
I don't think so bro.. I distinctly remember updating my moto g3 by just re-flashing the stock recovery and still being rooted. I lost the root after the update of-course..
Sent from my Moto G4+ using Tapatalk.
From my understanding systemless root will be written over with an update. Will need to root the device again once updated. But stock recovery will need to exist before update.
zazzy24 said:
I don't think so bro.. I distinctly remember updating my moto g3 by just re-flashing the stock recovery and still being rooted. I lost the root after the update of-course..
Sent from my Moto G4+ using Tapatalk.
Click to expand...
Click to collapse
http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049
From what I've seen, any changes made to system.img (which many apps that require root make changes to) results in the OTA not applying even if you have stock recovery.
xtermmin said:
http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049
From what I've seen, any changes made to system.img (which many apps that require root make changes to) results in the OTA not applying even if you have stock recovery.
Click to expand...
Click to collapse
It is always advisable to re-flash the stock rom before updating and that's what i also do most of the time. And even i ran into some trouble on moto G 2015 while updating with xposed still installed. But can say from experience that i have had no issues with updating while still rooted.
However since i would lose the root anyways after the update, there is not much sense in updating while still being rooted! Just laziness i guess [emoji14]
Sent from my Moto G4+ using Tapatalk.
Don't have to reflash the whole stock rom before ota update. Just do unroot and incase if you flashed custom recoverys reflash the stock recovery only. Trust me thats enough for successful ota update.
Sent from my SM-T231 using XDA-Developers mobile app
gowthamgam said:
Don't have to reflash the whole stock rom before ota update. Just do unroot and reflash the stock recovery only incase if you flashed custom recoverys. Trust me thats enough for successful ota update.
Sent from my SM-T231 using XDA-Developers mobile app
Click to expand...
Click to collapse
I agree that will work. Also be aware that you will get the OTA download even though you're rooted, it just won't install.
Rakesh8857 said:
Do we get update Android N if our device is rooted?
Or we have to flash stock rom..?
Click to expand...
Click to collapse
Small updates such as camera patch or monthly security patches will not install and give an status 7 error because these check for unmodified system....
But for android n update the whole system img will be replaced and current system is not checked for modification...
So you can install Android N update but you cant install any update in between...
And about recovery....I remember updating my old phone (lava pixel v1) with TWRP instead of stock...since using stock recovery wont install because of OTA bug(Yes official OTA wont install on stock)...I'm sure you can install using TWRP but to be on safe side use stock one...
May be thats your lava smartphone's bug only. Not all smartphones with that ota bug. I've updated lenovo k3 note from lollipop to marshmallow successfully by official ota update, That too only after the unrooting,flashing stock recovery back process. I've tried this method on other devices too and it works successfully.
Sent from my SM-T231 using XDA-Developers mobile app
gowthamgam said:
May be thats your lava smartphone's bug only. Not all smartphones with that ota bug. I've updated lenovo k3 note from lollipop to marshmallow successfully by official ota update, That too only after the unrooting,flashing stock recovery back process. I've tried this method on other devices too and it works successfully.
Sent from my SM-T231 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thats what I said bro...Im just adding you can use twrp also...but stock is recommended.
srinu427 said:
Thats what I said bro...Im just adding you can use twrp also...but stock is recommended.
Click to expand...
Click to collapse
Here comes the complete answers for all questions here
Source official TWRP website
Official OTA Updates and TWRP
Installing official updates from your manufacturer or carrier is not supported by TWRP.
Most official updates are differential in nature. On a completely stock device when used in the way that Google and manufacturers intend, users will never modify the system partition. A differential update means that the update does not replace the entire system. In many cases the update doesn't even replace entire files and instead just patches the difference between the old file and the new file to bring it up to date for the new version. This method makes the updates smaller which is good when you have thousands of devices that will be downloading the update over a carrier's data network, usually within a short time frame. Unfortunately this method also means that users who have modified their system by rooting, installing busybox, and removing unwanted system apps may experience unexpected behavior when they install a differential update.
Also, device manufacturers may have made changes to their recoveries that we aren't aware of and device makers do not have to release source code for their recoveries (AOSP recovery is Apache license which does not require them to release their source for these changes). Those changes may not be present or supported by TWRP which may result in unexpected behavior, especially when it comes to updating items like radios, bootloaders, and modems.
Installing official updates usually removes root and replaces your custom recovery with a copy of a stock recovery. Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install.
If you've read all this and still insist that you want to install an official update from your manufacturer, the recommended process is to first return your device to completely stock including replacing TWRP with a copy of the stock recovery. Because the methods for returning to stock vary depending on the device, you will need to use Google to locate a guide for returning to stock and/or finding and installing a copy of the stock recovery. Note that there is no "uninstall process" for removing TWRP. In almost all cases the process is to simply install a different recovery.
Sent from my SM-T231 using XDA-Developers mobile app
gowthamgam said:
Here comes the complete answers for all questions here
Source official TWRP website
Official OTA Updates and TWRP
Installing official updates from your manufacturer or carrier is not supported by TWRP.
Most official updates are differential in nature. On a completely stock device when used in the way that Google and manufacturers intend, users will never modify the system partition. A differential update means that the update does not replace the entire system. In many cases the update doesn't even replace entire files and instead just patches the difference between the old file and the new file to bring it up to date for the new version. This method makes the updates smaller which is good when you have thousands of devices that will be downloading the update over a carrier's data network, usually within a short time frame. Unfortunately this method also means that users who have modified their system by rooting, installing busybox, and removing unwanted system apps may experience unexpected behavior when they install a differential update.
Also, device manufacturers may have made changes to their recoveries that we aren't aware of and device makers do not have to release source code for their recoveries (AOSP recovery is Apache license which does not require them to release their source for these changes). Those changes may not be present or supported by TWRP which may result in unexpected behavior, especially when it comes to updating items like radios, bootloaders, and modems.
Installing official updates usually removes root and replaces your custom recovery with a copy of a stock recovery. Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install.
If you've read all this and still insist that you want to install an official update from your manufacturer, the recommended process is to first return your device to completely stock including replacing TWRP with a copy of the stock recovery. Because the methods for returning to stock vary depending on the device, you will need to use Google to locate a guide for returning to stock and/or finding and installing a copy of the stock recovery. Note that there is no "uninstall process" for removing TWRP. In almost all cases the process is to simply install a different recovery.
Sent from my SM-T231 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes exactly... this one you posted from TWRP website tells about differencial updates,Ive already mentioned that after root you cant install differencial updates...But Android N update is NOT differential update since it replaces whole system partition so you CAN install it Using TWRP...But you CANT install any minor(differential) updates if youre rooted.
How to reflash stock recovery & can we unroot from menu given in Supersu
Related
I know the S3 you can't install updates if you unlock the bootloader. But if I unlock/root I can still get future updates right?
Why does it matter? If you are unlocked and rooted then you will be running a ROM someone made, so all you have to do is install a new version of whatever ROM you want when a new update is released. Custom ROM's are pretty much always up to date with the latest source.
There are plenty of reasons to root without installing custom roms. I only root my devices to get wireless debugging.
My unlocked Galaxy Nexus got the latest ota. It broke root, but is still unlocked. I've not rooted my nexus 10 yet.
You'll be able to install OTA updates cleanly as long as you're using stock recovery and haven't modified any system files that the update expects to be there.
Fromako said:
You'll be able to install OTA updates cleanly as long as you're using stock recovery and haven't modified any system files that the update expects to be there.
Click to expand...
Click to collapse
I can verify this. I just got my Nexus 10 and in order to move saved game data and some other stuff I rooted and unlocked the bootloader so I could run Titanium backup. I didn't change system settings or anything and I am not running a custom rom. About 10 minutes after I had finished rooting and moving saves from my Samsung GTab 10.1 I received the 4.2.1 OTA Update. No issues so far and as far as I can tell it's still rooted.
Anyone tried and confirmed working the old adb backup method that doesn't require root?
http://forum.xda-developers.com/showthread.php?t=1420351
Was hoping to use this method to backup before unlocking. I got into the usual problem of not wanting to unlock right away (in case issues etc.) then once I was comfortable with the unit too lazy to want to set up all up again from scratch....
Use helium. Backup each app individually. There are some apps that will Bork restore.
Sent from my Nexus 7 using XDA Premium HD app
bummer screw that for a joke then LOL
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
wintermute000 said:
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
Click to expand...
Click to collapse
Unlocking doesn't prevent you from getting the OTAs.
If you want root to be compatible with OTAs, see this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
yeah I know that, I know I can reflash stock recovery and unroot etc. just too lazy to be bothered setting up all my apps losing saves etc. at this point short of mucking around with carbon. TBH if the multitouch issue is fixed or at least toned down there's not a lot of incentive to root for me aside from adblock.
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
wintermute000 said:
yeah I know that, I know I can reflash stock recovery and unroot etc.
Click to expand...
Click to collapse
My point is you don't need to unroot nor flash stock recovery (though it is safest to flash stock recovery)
The JSS15J OTA update will flash fine with root and twrp with just the small fix I referenced.
wintermute000 said:
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
Click to expand...
Click to collapse
JSS15J already included firmware updates, it updated aboot, sbl, tz, and rpm. Bootloader went from 3.05 to 3.14 and it flashed ok with root and twrp (though again, personally I suggest using stock recovery)
Also you don't need to install twrp persistently to root. I just boot into twrp one-time by using fastboot boot twrp.img to install the root files and leave stock recovery on the tablet.
With the one simple fix referenced above, you can have stock recovery, root, and be totally compatible with future OTAs, no need to revert anything. Of course after the OTA is successful, just re-run the SuperSU zip and the fix to set yourself up with root and await the next OTA.
On this nexus, you need to unlock even to do the official factory restore google published. The official images don't come with signatures.
To answer the question re adb bu, yes it works just fine.
Sent from my Nexus 7 using Tapatalk 4
I have a stock rooted Nexus 4 running Android 4.3 (JWR66V) and a custom recovery. Recently, the JWR66Y update showed up on my phone and I turned on OTA survival mode in SuperSU and proceeded to install the update. It booted into TWRP and proceeded to install up until a certain point but then it froze. I cancelled the installation and rebooted my device and I even got the "Updating Applications" indicator on the first boot. However, I checked the version and it was still on JWR66V and my device no longer shows an update available. I did the exact same thing with my Nexus 7 (2013) with the JWR66Q update and the same thing happened. Is there any way I can install an OTA update on a rooted device? Every time an update is available for one of my devices, I end up doing a full factory reset of my device to install an update. I have only been able to find things like Clean ROM and Shiny ROM and while I do appreciate the work these developers are doing for the community, I would prefer to be able to either download a fully stock and non-deodexed flashable zip for my device or find a way to install the OTA update without losing root. It would also be great if I could do so without a computer because I currently only have a Chromebook. Thank you very much.
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Nathanation said:
Are you sure it was the update to the Y version? What did the file size show as in the system update notification? There have been 2 very small (1.8mb) updates which don't change the build number, maybe that's what you installed.
I am also stock rooted and have received each system update as usual, remember they take time to roll out world wide.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
KeanuKe said:
Now that you mention it, I'm actually not sure. However the update didn't complete either way. It froze on a step involving the boot.img (sorry I can't remember exactly what it was doing). I don't really need a fix for it anymore as I have already manually installed the updates using a friends computer but I only know how to do so by flashing the factory image and losing all of my data along the way. But just so I know for future updates, do you use OTA Survival mode or OTA Rootkeeper or anything like that or do you simply install the update as you would on a non-rooted device? Thanks for your reply.
Click to expand...
Click to collapse
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
xda6969 said:
The root isn't the problem. The custom recovery is. You need to be on stock recovery for the update.
Click to expand...
Click to collapse
Can I fastboot flash the stock recovery after I've already flashed a custom recovery and still have root? And if the answer to that is "yes" will I still be rooted after the next OTA update?
I am having the same problem. Both my nexus 4 and 7 recieved an update (1.8MB) but it seems that i cannot get the update to install. Both devices were rooted using the Nexus Root Tool kit.
When i got the update the devices booted in recovery mode with TWRP. Do not know what to do. I saw no update in the baseband or build number.
I am running stock android.
Please advise
I used Google's batch file on windows to flash the stock 5.0, having unlocked the bootloader and also installed the chainfire root. Just wondering whether I'll get any fixes, or whether i'll have to always repeat this process, wiping out everything on the device in the process.
You may get prompted to download and install new updates when they arrive, but they will fail upon installation unless you're 100% stock.
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Does the Google image download page (https://developers.google.com/android/nexus/images) get updated as Lollipop gets updated? Or am I going to have to do OTA updates?
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
igeigeige said:
hmm.. im not sure which comes first.. but, if you want to get OTA, you'll have to wait for your device to get its turn for the notification to appear. The effect will still be the same though if you flash that google image to your device.. And flashing that device, will save you time from waiting for your OTA to appear on your device.
Cheers! :good:
Click to expand...
Click to collapse
Well, I'm a bit confused. I'm on stock, but i need root, so i installed cfar, which I think included super su. when a new version of super su came out (i was alerted via google play), i needed to install the twrp recovery (which I didn't have installed at that point) to update it. So I guess I'm not stock any more, even though I've not actually put a non-stock image on. So even if the OTA update message popped up, I doubt it's safe to install it that way, even if it let me. I'm just not sure whether I need to a factory reset/wipe etc before updating, or if I can do a dirty update (the OTA is effectively a dirty update, isn't it?). And, like i said, i'm not sure whether that page gets updated with new images, or whether you're supposed to just put the initial one down and then do OTA updates (and only then root, change the recovery etc).
You have a stock rom but with a CUSTOM recovery. Yes, ota will prompt you to update, but DON'T. You should convert to stock recovery first. Because if you do, the update will push through, but once it asks you to boot to make the update in effect, you will have a NO COMMAND error - bootloop, and only fastboot and recovery (sort of dysfunctional). Just like most of the people here, including me. So make backup of your files first before doing the update. Cheers :good:
Sent from my Nexus 10 using XDA Premium 4 mobile app
If having a custom recovery is an issue, why could I flash ota zips from custom recoveries ever since buying the tablet?
igeigeige said:
there will be an OTA update notification if you have stock rom wether you have a sotck or a custom recovery. But if you download and install the OTA update having a custom recovery, the installation will fail and will show an installation or update error. You will be stucked in "no command" image. so better restore your stock recovery as well before downloading any OTA updates..
Click to expand...
Click to collapse
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Rizz67 said:
Should have read this first. In the bootloop. Tried flashing back to stuck with nexus toolkit. No luck. Suggestions?
Click to expand...
Click to collapse
Hi, what i did was flashing the official factory image from google via fastboot/bootloader... Make a nandroid backup first though.. Because you'll need to clean flash (system partition/cache and data) to avoid future problems.
please educate me
A few weeks ago I rooted my N4 with CFAR (& of course had to wipe out everything). My understanding was that now that my bootloader is unlocked, I can sideload new images, thus sparing me a rewipe -- & in my ignorance, was anticipating that ChainFire would make 5.0.1 images in due course.
So, If I want to root subsequent 5.x.x releases, how would this work in real life??
Can i just restore stock recovery and then install the 5.0.1 ota update without losing everything?
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.