I'm wondering if it's a good idea to do a factory reset/clean install of the official firmware when Pie is released.
I would think it would help prevent issues as it's a full version difference.
1031982 said:
I'm wondering if it's a good idea to do a factory reset/clean install of the official firmware when Pie is released.
I would think it would help prevent issues as it's a full version difference.
Click to expand...
Click to collapse
For Oreo from Nougat (May 2018), I did Upgrade via LGUP.
But it never hurts to do a clean install.
I'll probably have to edit the WTF INSTRUCTIONS after that to include Pie KDZ...
Sent via open market LG US998 V30/V30+
Ok. I know rumors put the pie release outside the US this or next month, I'm trying to decide on what way to go.
This way I have time to prep.
1031982 said:
I'm wondering if it's a good idea to do a factory reset/clean install of the official firmware when Pie is released.
I would think it would help prevent issues as it's a full version difference.
Click to expand...
Click to collapse
Yeah. Factory resseting is generally a good for major android updates.
PS: Next time please post in appropriate thread. This is the development thread and a question shouldn't be posted here.
tech_infinity said:
Yeah. Factory resseting is generally a good for major android updates.
PS: Next time please post in appropriate thread. This is the development thread and a question shouldn't be posted here.
Click to expand...
Click to collapse
Sorry I must have been in development instead of Q&A. If a mod wants to move it, that would be appreciated.
1031982 said:
Sorry I must have been in development instead of Q&A. If a mod wants to move it, that would be appreciated.
Click to expand...
Click to collapse
No problem
I think pie is very far for us right now. Maybe just upgrade to pie when it comes and reset if you've any issues.
tech_infinity said:
No problem
I think pie is very far for us right now. Maybe just upgrade to pie when it comes and reset if you've any issues.
Click to expand...
Click to collapse
Well, AT&T just got Pie on the V35, so I can't imagination we are too far behind.
Funny thing is, I already have a couple issues. Nothing serious, but they are annoying.
1. Do not disturb does not abide by it's set schedule. It will turn off, but not turn on without me either restarting my phone, or manually turning it on.
2. (May not be a bug, but I haven't found anything about it so eh...) Every so often, pressing the volume buttons causes it to jump by 5 points instead of one. This is from both on the phone, and using the headphones that came with it that have volume buttons.
There are times I press volume up and it starts blaring, so I quickly turn it back down and use the screen to change the volume until I reboot my phone to correct it. I have verified that I am not double pressing or holding the volume button.
They both started when I upgraded to US998 20H. To be clear, I used the following KDZ images to upgrade in order : A, E, F, G, and finally H.
Instead of wiping my phone now, I figured that I would just wait until Pie is out for little bit and then so a clean install. Hopefully it will fix those issues, and prevent any others from arising for that update.
Related
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
cainman said:
Hi guys,
So i just downloaded and installed the latest T-mobile update and now my phone is slower.
Every time I hit the home button, the image blinks and redraws and there's just a hint of stutter.
The app drawer also takes a little longer now.
What the heck?
It used to be so zippy and fast. How do I fix it, anyone know?
Click to expand...
Click to collapse
Might help to post which update you received.
reTARDIS said:
Might help to post which update you received.
Click to expand...
Click to collapse
D85110r
cainman said:
D85110r
Click to expand...
Click to collapse
Try disabling hw overlays in developers options to help with that redraw stutter. Remember you have to set it everytime you boot, unless you're booted with xposed installed, then you could download the module that keeps it active at all times.
This seems to have helped a lot of people with your issue.
Thank you.
It's sadly still doing it.
cainman said:
Thank you.
It's sadly still doing it.
Click to expand...
Click to collapse
Did you take the ota or download one of the twrp upgrades floating around? Either way in your situation you probably need to do a factory reset. Alternatively follow the twrp method HERE if you haven't already and I can personally guarantee a better than ota install. If you want it to be done correctly to fix any problems you need to wipe the system and data partitions before flashing. Also don't forget to download super su if you want to keep root (linked in guide). There is another upgrade twrp file in the development section I think that is not a perfect 1:1 image and could give problems. Not saying that particular rom is bad or that it is the problem, its just not a 1:1 like the guide I linked you to it is directory/installer script dependent. The one I made transfers the whole untouched partition over and inside has all the symlinks and permissions preset by LG.
Factory Reset
Can not wait for the official Nougat version! Here are the latest model which I can get for you.
Not much to say，here's link for QA1, every person can flash that with Odin and then OTA to Nougat by @norbarb 's way.
Simply speaking, upgrade is divided into two steps. First flash my QA1. Then usd adb update to QC5.
Flash QA1 by Odin:
https://mega.nz/#!EFAiXTKC!S0LvpCIedF_ubVgszflUaN3U_O2zwQoeH6ku68gqnDM
QA1-QC5 Adb files from @norbarb
https://docs.google.com/uc?id=0B4sOy1rlqVoYdnROaFU4LXQybjA&export=download
Warning
Whether Odin or Adb will formate data on your phone. Please backup and then do it.
smxwang said:
Can not wait for the official Nougat version! Here are the latest model which I can get for you.
Not much to say，here's link for QA1, every person can flash that with Odin and OTA to Nougat by @norbarb 's way.
Simply speaking, upgrade is divided into three steps. First flash my QA1. Then usd adb update to QB2. Finaly using adb update to QC5.
Flash QA1:
https://mega.nz/#!EFAiXTKC!S0LvpCIedF_ubVgszflUaN3U_O2zwQoeH6ku68gqnDM
QA1-QB2:
https://forum.xda-developers.com/att...-plus-t3563086
QB2- Nougat:
https://forum.xda-developers.com/att...rvers-t3574757
Click to expand...
Click to collapse
Thanks man...great job
Is this ready for "daily driving"?
Iam on PBH4 (agaust security patch)
can i flash QA1 directly?
TeldenW said:
Is this ready for "daily driving"?
Click to expand...
Click to collapse
Working great for me as DD. Battery life is better than 6.x, but I'd expect that it'd be a little better anyway after a full wipe & fresh install.
samsung lo said:
Iam on PBH4 (agaust security patch)
can i flash QA1 directly?
Click to expand...
Click to collapse
I was on the PK1 yesterday, then I ODIN'd to PL1 (using Norbarb's instuctions and wiped my device in the process).
I then realized that since the device was already wiped, I simply ADB directly to QC5 (as it was already 1.5GB in size and should already contain the previous updates).
Battery life is now horrible, although I'm still trying to get used to the new features by turning off / disabling what I don't need. The update is worth it. as the theme makes me "feel" as though I got a new device. The touchwiz additions replace quite a number of third party apps that I'd have downloaded separately otherwise.
jaxf250 said:
Working great for me as DD. Battery life is better than 6.x, but I'd expect that it'd be a little better anyway after a full wipe & fresh install.
Click to expand...
Click to collapse
As you probably did, I'm using a non-rooted AT&T Galaxy Note 5 (N920A}. I'm familiar enough with ODIN to know that I'll probably mess it up the first try... And spend a lot of time figuring out my mistakes.
Did you have any difficulty with the update process?
TeldenW said:
As you probably did, I'm using a non-rooted AT&T Galaxy Note 5 (N920A}. I'm familiar enough with ODIN to know that I'll probably mess it up the first try... And spend a lot of time figuring out my mistakes.
Did you have any difficulty with the update process?
Click to expand...
Click to collapse
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH
I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware. Please let me know there if you want 4CQA1 to 4EQC6 update also.
jaxf250 said:
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH
Click to expand...
Click to collapse
Dude, thanks man. I'm gonna do my research over the next couple days.
Good lookin' out.
norbarb said:
I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware.
Click to expand...
Click to collapse
I just got QC5 sideloaded last night. I stayed up restoring my apps and data as close as I had it before on my PK1. This was a time-consuming process.
norbarb said:
Please let me know there if you want 4CQA1 to 4EQC6 update also.
Click to expand...
Click to collapse
You can't now just drop the QC6 on me like that so I have to go through that process all over again.
Hence I'll say "No, thank you" :highfive:
norbarb said:
I will post in Nougat update thread new update to 4CQB2 to 4EQC6 firmware. Please let me know there if you want 4CQA1 to 4EQC6 update also.
Click to expand...
Click to collapse
that's great. No matter what new model is better than elder one.
jaxf250 said:
The only problem I encountered was the need to perform the large address aware fix to adb so it would sideload the S4CQB2-to-U4EQC5.zip file for me, otherwise it went fine. Just takes time. I went step by step after first backing all my stuff up. I was on an older MM release that had not been patched with any of the last 3 or 4 security patches, so I began with a complete wipe and ODIN of CPK1. Then sideloaded the rest, one at a time and switching USB debug on each time before the next update: CPK1-to-PL1, then PL1-to-CQA1, then CQA1-to-CQB2, then the final S4CQB2-to-U4EQC5. About 90 minutes maybe, a little less? I can't recall, but wasn't a big deal. It took Google longer to load my 180 apps back on at the end LOL. All the tips (like the large address fix) are in the other thread - just read it over before starting. I see we have a new update too to version QC6.... I may flash that or wait another week or two to see if more updates come out. Honestly it is running just great and I have no issues. Snappy. HTH
Click to expand...
Click to collapse
Where did you find the QA1-to-QB2 file?
trsanning said:
Where did you find the QA1-to-QB2 file?
Click to expand...
Click to collapse
Here : http://forum.xda-developers.com/showthread.php?p=71184332
Originally from servers
Clicking from Edge of Galaxy
Help
Hello !
Please help, yesterday i try slideload with ADB from U2AOI6 to U2APB2 , i don't know how i did it, but now i have bootloop and messages " dm-verity verification failed "... " update from ADB is disabled " in downloading mode ... Is there any issue to do not loose my data. ..? If not, is the link of S4CQA1 provide here sufficient to make a full flash with odin ?
dakkidd said:
Hello !
Please help, yesterday i try slideload with ADB from U2AOI6 to U2APB2 , i don't know how i did it, but now i have bootloop and messages " dm-verity verification failed "... " update from ADB is disabled " in downloading mode ... Is there any issue to do not loose my data. ..? If not, is the link of S4CQA1 provide here sufficient to make a full flash with odin ?
Click to expand...
Click to collapse
ADB sideload always wipes after it completes
There is an app named Flashify which does not wipe after applying updates but that only works on rooted phones (and you cant root the AT&T Note 5)
Therefore no, there is (currently) no way to prevent sideload wipe
Thank you very much Dezborders!
Now it will be my first time to use Odin, pleaz can you give me the link of the more stable marshmallow for you on N920A... ?
dakkidd said:
it will be my first time to use Odin, pleaz can you give me the link of the more stable marshmallow for you on N920A... ?
Click to expand...
Click to collapse
Seriously dude!
See Page 1 Post 1 Link 1 of this thread.
dezborders said:
Seriously dude!
See Page 1 Post 1 Link 1 of this thread.
Click to expand...
Click to collapse
Lool... I have seen, but the idea was that the last update is not necessary the more stable... But ok, i'll do whith...
Thank you very much.
Sorry for my english, it's not my first speech :good:
Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justin
Cry_Cry said:
Hi,
I recently got a hold of a HTC 10 which came preinstalled with Android marshmallow. Since I had bought this two years after intital release I realised that the Oreo update was available. So in the midst of my excitement I updated to Android nougat but then to Oreo straight after. That was when the problems occured. So on battery, I lock my phone and around 5 seconds after, the phone wont turn on. Not from the power button alone. I found the only way to turn it on was by pressing and holding both volume down and the power button to go to the Download mode and then reboot from there. But if I leave my phone screen off for around 5 secs again then it happens again. None of this would occur on charge. I have tried flashing other Oreo ROMs like leedroid 10, purefusion 8.0 and lineage 15.1 but this occurs across all of them.
I then decided to downgrade and flashed a few nougat ROMs like lineage 14.1 and purefusion 7.1. This fixes my random shut down issue but then a new one popped up. I realised that I couldn't use my home button or fingerprint scanner at all. I have tried checking Generic.kl under 'keylayouts' but according to it. The home button was not disabled.
So basically on Oreo, I get random shut downs and on nougat my home button and fingerprint don't work.
I would appreciate if I could get any sort of help on this, thanks.
Thanks, Justinhttps://www.youtube.com/watch?v=
Click to expand...
Click to collapse
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately
yldlj said:
Your fingerprint scanner doesn't work because of a firmware mismatch. Nougat roms need nougat firmware. As for the battery problems this has been reported ALOT lately
Click to expand...
Click to collapse
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?
Cry_Cry said:
Ah that’s a good point. Do you think a battery replacement might fix my Oreo firmware issue?
Click to expand...
Click to collapse
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.
yldlj said:
I don't know. I highly doubt that's it happens only on Oreo. Give it time and I think it will happen no matter what firmware your on.
Click to expand...
Click to collapse
So basically there is no fix for my problem?
Cry_Cry said:
So basically there is no fix for my problem?
Click to expand...
Click to collapse
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Are you SOFF? What's your CID?
yldlj said:
From previous posts that I have seen it sounds like a battery problem. The first thing I would do is flash an RUU. If the problem is still there it's most probably hardware.
Click to expand...
Click to collapse
Cry_Cry said:
I have thought of that, but I cant find any Nougat RUUs. Do you think you could link me to one or anywhere that may lead me to one?
Click to expand...
Click to collapse
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?
Cry_Cry said:
Ok nevermind, I found one, just one last question, with RUUs do I need to flash Gapps with it or do they come with it?
Click to expand...
Click to collapse
Nope flash RUU and that's it.
I get a lot of random crashes and power offs since I've upgraded to Oreo. It's really been driving me nuts.
Can't wait for the OP6 or U12+ to come out - I really need a new phone.
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
thayl0 said:
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
Click to expand...
Click to collapse
try to wype partition cache
UNIK97122 said:
try to wype partition cache
Click to expand...
Click to collapse
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
thayl0 said:
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
Click to expand...
Click to collapse
do you have the same with another camera app ?
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
blackhawk said:
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
Click to expand...
Click to collapse
Sadly I don't think I can go back to pie I believe there's a different bootloader version
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Try the new Beta,it might fix it
TheViciousGames said:
Try the new Beta,it might fix it
Click to expand...
Click to collapse
Trying to find the first beta so it can update to latest. No luck so far
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Yeah they like to lock the doors behind you... just remember the lesson.
I learned the hard way with Kitkat; the last update did nothing except make easy root impossible.
With lollipop AT&T/Samsung purposely screwed up the graphics on just that old model for contacts and the music play list making the S4+ next to unusable.
They'll say it will run better, be more secure.
BS.
Never had a OS "upgrade" that wasn't bigger, hoggier and slower then the original on Android.
Never in 6 years of running outdated OS's on Androids had to do a reload from a virus or worm.
Sure it can happen but rarely does if you don't do stupid things.
Play with it, eventually you'll sort it out
Androids wuv being played with...
Hello
Before few days ago, i received official ota update to android 11 of my motorola g5g plus.
I was very happy, that finally the android 11 is here and immediately updated my device(big big mistake)
After the update process, my phone start to be more and more laggy.I use it only at 90hz refresh rate and sometimes when i use it is goes on frames, which is madness..
I am really unhappy about that..I don't want to factory reset my phone.
Any possible way to resolve this lag issue or return easy to android 10 and never update again?
I do not play games or other heavy stuffs..
just ebay calls browsing nothing so heavy...
ideas guys?
You could use the Moto Flash Tool to flash the latest version of 10 - note that you'll (very probably) have to do a data wipe when asked to avoid problems afterwards.
To be sure, I'd check with @vache as to whether a downgrade is possible, but I don't see why not.
giociampa said:
You could use the Moto Flash Tool to flash the latest version of 10 - note that you'll (very probably) have to do a data wipe when asked to avoid problems afterwards.
To be sure, I'd check with @vache as to whether a downgrade is possible, but I don't see why not.
Click to expand...
Click to collapse
Thanks.I am new in the motorola world( untill now only xiaomi, and downgrade there was not a good idea).Maybe will try the factory reset, if work will stay with android 11, but really hate to do factory reset...
galev_90 said:
Thanks.I am new in the motorola world( untill now only xiaomi, and downgrade there was not a good idea).Maybe will try the factory reset, if work will stay with android 11, but really hate to do factory reset...
Click to expand...
Click to collapse
Check in settings for blur, and turn it off and see if that helps. Sorry, I don't use stock so I'm not sure exactly where it is. Developer settings maybe, or display
Beetle84 said:
Check in settings for blur, and turn it off and see if that helps. Sorry, I don't use stock so I'm not sure exactly where it is. Developer settings maybe, or display
Click to expand...
Click to collapse
Thank you.
This method work at the moment.In the developer settings it is located..Hope with some next build to be fixed the things and the blur work.
Sad news again.Phone become laggy again even on only 90hz refresh rate with turned off blur.Yesterday the phone work fine, today i woke up and surprise lagging on normal stuffs like scroling across the screen or open menu app and etc.I am almost sure that it run on less than 60hz.Absolutely dissapointing....
Thank you motorola.Last phone from this brand...