Related
I know Samsung doesn't post changelogs for their new updates but I just wanted to make a thread for the MG3 update and maybe future updates to point out the changes in the firmware. If you notice any changes, please post it here and I will give it a "thanks" if I can confirm that it's real and I'll put it in the OP (along with your name of course).
Sent from my GT-I9505 using xda app-developers app
WIFI Broken after MG3 firmware update
Just went ahead with my S4 (i9505) MG3 firmware update via Kies (the firmware update version is PDA:MGA / PHONE:MGA / CSC:MG3 (BTU)), everything installed without a hitch, phone rebooted, AND WIFI IS NOW BROKEN!! Meaning the Quick Toggle remains grayed-out even if you press it to turn it on, and going into System Settings and trying to turn on WiFi from there also doesn't work-- the WiFi is simply not turning on! This is a MASSIVE bug which is utterly unacceptable being in an OEM update!!
I've since restored my NANDroid backup to go back to i9505XXUAMDM. At least the WiFi works in that firmware. Yeesh.
criptyque said:
Just went ahead with my S4 (i9505) MG3 firmware update via Kies (the firmware update version is PDA:MGA / PHONE:MGA / CSC:MG3 (BTU)), everything installed without a hitch, phone rebooted, AND WIFI IS NOW BROKEN!! Meaning the Quick Toggle remains grayed-out even if you press it to turn it on, and going into System Settings and trying to turn on WiFi from there also doesn't work-- the WiFi is simply not turning on! This is a MASSIVE bug which is utterly unacceptable being in an OEM update!!
I've since restored my NANDroid backup to go back to i9505XXUAMDM. At least the WiFi works in that firmware. Yeesh.
Click to expand...
Click to collapse
I had the wi-fi bug a few days after I flashed the MG3 firmware (wi-fi toggle, both on settings and quick settings are greyed out and stuck at connecting). If you're running the international version you should flash the latest modem.
Sent from my GT-I9505 using xda app-developers app
kevin95 said:
I had the wi-fi bug a few days after I flashed the MG3 firmware (wi-fi toggle, both on settings and quick settings are greyed out and stuck at connecting). If you're running the international version you should flash the latest modem.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Same thing happened to me, had to flash the latest modem like you said: good:.
I recieved this update also. Has someone installed it without the modem problem???? This is the only issue found???
Exception
wcharon said:
I recieved this update also. Has someone installed it without the modem problem???? This is the only issue found???
Click to expand...
Click to collapse
My Galaxy S4 I9505 BTU UK is the living proof of a no failure update. Everything works silky smooth.
dklhs90 said:
My Galaxy S4 I9505 BTU UK is the living proof of a no failure update. Everything works silky smooth.
Click to expand...
Click to collapse
So you didn,t have the Modem issue. Great....
Also, do you have the Talb Back issue that you can't disable it?????
Thanks once again....
wcharon said:
So you didn,t have the Modem issue. Great....
Also, do you have the Talb Back issue that you can't disable it?????
Thanks once again....
Click to expand...
Click to collapse
As for the Talk back issue you are talking about I have no idea what you are talking about. I have never experienced such thing. Maybe it is because i have my Talkback setting to off.
dklhs90 said:
As for the Talk back issue you are talking about I have no idea what you are talking about. I have never experienced such thing. Maybe it is because i have my Talkback setting to off.
Click to expand...
Click to collapse
Ok.. Le me explain a little. I installed No Led and it requires accesabilty option in order to function. When i let it have accesability it turns activates the Talkback function besides of the phone having the Talback function unticked... Heard that also other applications haves the same issue so it is a 4.2.2 issue....
wcharon said:
Ok.. Le me explain a little. I installed No Led and it requires accesabilty option in order to function. When i let it have accesability it turns activates the Talkback function besides of the phone having the Talback function unticked... Heard that also other applications haves the same issue so it is a 4.2.2 issue....
Click to expand...
Click to collapse
That means that so far I have not had the need to install an app that needs accessibility which then turns on the talkback function.
dklhs90 said:
That means that so far I have not had the need to install an app that needs accessibility which then turns on the talkback function.
Click to expand...
Click to collapse
Yepppppp. I like No Led becuase it have sound and screen notifications with missed SMS, Calls, emails, etc.... Great application.....
Thanks for your help...
I used CRASHXXL's method to root 4.4.4 and have noticed a few weird bugs. First, the quick settings button in the notification panel doesn't work. Also, bluetooth sometimes won't connect to any device and attempting to turn off bluetooth causes the freeze. The rest of the phone works fine though. The only way to fix is reboot the phone, but the issue eventually comes back. Any ideas?
dcoaster said:
I used CRASHXXL's method to root 4.4.4 and have noticed a few weird bugs. First, the quick settings button in the notification panel doesn't work. Also, bluetooth sometimes won't connect to any device and attempting to turn off bluetooth causes the freeze. The rest of the phone works fine though. The only way to fix is reboot the phone, but the issue eventually comes back. Any ideas?
Click to expand...
Click to collapse
That's strange. I rooted several times with CrashXXL's method (currently unrooted) and never had any problems with anything. What launcher are you using? It could be that or some app you have installed. Have you installed Xposed and/or Gravity Box? If so, could be some module interfering with something.
Maybe you should consider returning to stock unrooted and doing the procedure all over again.
I'm just using the stock launcher and haven't installed xposed or busybox. Is there an easy procedure to get back to stock unrooted and redo? Thanks!
dcoaster said:
I'm just using the stock launcher and haven't installed xposed or busybox. Is there an easy procedure to get back to stock unrooted and redo? Thanks!
Click to expand...
Click to collapse
Yes, just use RSD to flash the stock su6-7.2 firmware. Here is the link to the firmware file:
http://motofirmware.center/files/category/18-droid-maxx/
If you want to save all your data and apps then flash the 1FF firmware file.
If you want to start over clean then flash the CFC file.
I updated my stock L09C636B170 to B560(I think, cant check with it just saying test keys) using Firmware finder proxy method . Everything seemed to be in order, it downloaded the update and applied it.
System seems faster but I've noticed that my bluetooth can't be turned on (I use it frequently for my smartwatch and car). Also certain apps seem to be missing. (clock, updater, etc)
I'm not sure how to fix these issues and really need you guys to help me out here.
DQEight said:
I updated my stock L09C636B170 to B560(I think, cant check with it just saying test keys) using Firmware finder proxy method . Everything seemed to be in order, it downloaded the update and applied it.
System seems faster but I've noticed that my bluetooth can't be turned on (I use it frequently for my smartwatch and car). Also certain apps seem to be missing. (clock, updater, etc)
Click to expand...
Click to collapse
I don't know for sure, but it sounds like you're in the early steps of how I messed up myself just recently.
Here's how I managed to fix my device again: https://forum.xda-developers.com/showpost.php?p=72794604&postcount=6 (Obviously, I can't guarantee anything, it's just what worked for me. Maybe you don't have to do quite as much as I did, since your phone still boots, at least.)
I hope it works out for you, too. :fingers-crossed:
Edit: Just read you are on a stock ROM by now. I don't think you have to unlock your bootloader for that, but I could be wrong. Should you encounter any problems in the process, this may(!) be cause.
DQEight said:
I updated my stock L09C636B170 to B560(I think, cant check with it just saying test keys) using Firmware finder proxy method . Everything seemed to be in order, it downloaded the update and applied it.
System seems faster but I've noticed that my bluetooth can't be turned on (I use it frequently for my smartwatch and car). Also certain apps seem to be missing. (clock, updater, etc)
I'm not sure how to fix these issues and really need you guys to help me out here.
Click to expand...
Click to collapse
I have the same problem with my phone did you manage to fix your if yes how did you do it
jezzain1 said:
I have the same problem with my phone did you manage to fix your if yes how did you do it
Click to expand...
Click to collapse
Unlocked bootloader, factory reset with twrp and flashed the second zip from the download using twrp.
DQEight said:
Unlocked bootloader, factory reset with twrp and flashed the second zip from the download using twrp.
Click to expand...
Click to collapse
I have the same problem. Where can I find the "second zip from the download"? Thank you.
DQEight said:
I updated my stock L09C636B170 to B560(I think, cant check with it just saying test keys) using Firmware finder proxy method . Everything seemed to be in order, it downloaded the update and applied it.
System seems faster but I've noticed that my bluetooth can't be turned on (I use it frequently for my smartwatch and car). Also certain apps seem to be missing. (clock, updater, etc)
I'm not sure how to fix these issues and really need you guys to help me out here.
Click to expand...
Click to collapse
Hi I have exact same issue and I have NXT-L09
I was on NXT-L09C636B191 and used Firmware finder auto DNS method and now have build number under "About Phone" is "NRD90M test keys"
I ham on 7.0 Emui 50 with this version but bluetooth can't be turned on , apps missing , clock missing , System Updater button missing.
Please tell me whats the easiest way to get onto Official Huawei firware ... I am a newbie .
please help !!!
thnx
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
What version of magisk are you using?
snake218 said:
What version of magisk are you using?
Click to expand...
Click to collapse
it's v16 stable
boydzethuong said:
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
Click to expand...
Click to collapse
Bro I'm having the same, loosing randomly my second sim card... Thought it was caused by some apps abusing of phone permission, but no luck it's not that. I cleared cache and art yesterday, now it's has not happened, but I guess it will happen again soon
Tonio78r said:
Bro I'm having the same, loosing randomly my second sim card... Thought it was caused by some apps abusing of phone permission, but no luck it's not that. I cleared cache and art yesterday, now it's has not happened, but I guess it will happen again soon
Click to expand...
Click to collapse
it will, unfortunately. i tried almost everything except uninstall magisk, lose root and restore TA & stock image. maybe it will fix the problem but whats the point if we no longer have root right?
back to nougat it was running flawlessly so i have a doubt that it has something to do with the combination of oreo + magisk + ta_poc method but i have no idea.
in ta_poc method i see it executes something like ua_modem_switcher. does it has something to do with modem?
@serajr you mind having a look pls. sorry to bother you the master but im running out of hope...
boydzethuong said:
it will, unfortunately. i tried almost everything except uninstall magisk, lose root and restore TA & stock image. maybe it will fix the problem but whats the point if we no longer have root right?
back to nougat it was running flawlessly so i have a doubt that it has something to do with the combination of oreo + magisk + ta_poc method but i have no idea.
in ta_poc method i see it executes something like ua_modem_switcher. does it has something to do with modem?
@serajr you mind having a look pls. sorry to bother you the master but im running out of hope...
Click to expand...
Click to collapse
Yes, removing magisk will lead to loose root access. But we can keep SONY features with kernel and TA.
The idea is :
-trying running stock OREO without root
-then adding custorm kernel with or without TA (original or drm_fix)
-at least adding magisk
I guess we need to try each step for a while
Maybe Serajr will have an idea, on my side i will try these steps and report...
highly appreciate that. i will do some more testings on my side too. the point is, although i know it will happen eventually but it happens so unpredictably its not easy to reproduce.
it may sound odd but you're here so i can at least hope it is just a software problem not hardware.
I was never be able to get my xz working with magisk 15 or 16. Always get the sim not recognized problem, maybe yours is magisk related.
snake218 said:
I was never be able to get my xz working with magisk 15 or 16. Always get the sim not recognized problem, maybe yours is magisk related.
Click to expand...
Click to collapse
Hmmm how come? Try this yet? https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
Both ta_poc and drmfix working.
hmmm anyone?
boydzethuong said:
hmmm anyone?
Click to expand...
Click to collapse
My phone is working fine for some days so far. Just cleared cache and dalvik as I mentionned earlier. BTW before doing this I've updated my Magisk from 15.3 to 16 without clearing anything (maybe the problem is related). Will report soon if it's still working or not...
Tonio78r said:
My phone is working fine for some days so far. Just cleared cache and dalvik as I mentionned earlier. BTW before doing this I've updated my Magisk from 15.3 to 16 without clearing anything (maybe the problem is related). Will report soon if it's still working or not...
Click to expand...
Click to collapse
I did that, many times. clearing cache and dalvik seems do the trick. but it actually doesn't. it will work for a few days and the issue will happen again. unfortunately.
by the way I spent some times paying high attention to the screen just to wait for it to happen. It looks like the moment when it happens, SystemUI (or Home Launcher I dont know) is terminated (stopped) then I am brought back to lock screen and at that moment, one of my SIM gone. So to me it looks like a service (or an app) is terminated and isn't restarted properly?
have you tried using stock rom and see if the problem persists?
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Pandemic said:
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Click to expand...
Click to collapse
oh nooo!!!
Pandemic said:
Damaged motherboard.
I had the same with my xz so buyed a new XZs and throw away my xz
Sent from my Sony Xperia XZs using XDA Labs
Click to expand...
Click to collapse
@Pandemic hmmm im not saying i dont believe but how do you explain it runs just fine for days after restart? usually 2 3 days then it happens.
and like i said the moment when it happens it looks like the whole systemui and running apps get force stopped.
lets say im playing a game then it becomes a bit laggy like its running out of memory then everything just closed then im brought back to lock screen and one of the signal indicator on status bar disappears.
do you happen to know any command that can restart the modem / cell / signal service? or any services related? just wanna try to manually execute it see if it fixes it.
also wanna mention again that im using ta_poc method for the drm sh!ts and it does have something like ua_modem_switcher executed. no idea whether it could be related
Hy guys, juste a quick update, my phone was working fine until 2/3 days. I've removed magisk but problem still happening, even clearing cache and dalvik didn't fixed it. My guess is, it could it be app related or crash due to RAM to high (my ram usage average is about 2.5 Go/day)...
Hi guys,
I have the same issue on a Note 4 (sm-n910f)....
I have been flashing roms in a long time and this is the first time it happens to me.
For me, the phone shows some lag, it auto restarts and the signal is lost. I can get it back by clearing delvik and cache, but this will happen at least twice a day.
I flashed stock and the problem goes away, does not happen even once on stock. So this tells me its not a hardware issue (i was so close in thinking its a motherboard issue)...
From reading various threads on this, i get to the conclusion that it is not device specific.
I have flashed half a dozen roms and only stock eliminates the issue. I stayed on stock for 3 days no issue, then reflashed lineage 15.1 and the problem is back. The really weird part is that this happened suddenly, not after a new flash or any operation on the phone.
Anyone figured this out?
---------- Post added at 07:20 PM ---------- Previous post was at 07:14 PM ----------
vasilis_84 said:
Hi guys,
I have the same issue on a Note 4 (sm-n910f)....
I have been flashing roms in a long time and this is the first time it happens to me.
For me, the phone shows some lag, it auto restarts and the signal is lost. I can get it back by clearing delvik and cache, but this will happen at least twice a day.
I flashed stock and the problem goes away, does not happen even once on stock. So this tells me its not a hardware issue (i was so close in thinking its a motherboard issue)...
From reading various threads on this, i get to the conclusion that it is not device specific.
I have flashed half a dozen roms and only stock eliminates the issue. I stayed on stock for 3 days no issue, then reflashed lineage 15.1 and the problem is back. The really weird part is that this happened suddenly, not after a new flash or any operation on the phone.
Anyone figured this out?
Click to expand...
Click to collapse
Adding some additional info from my experience:
- Tried flashing latest BL and CP files (using odin) without any luck
- Tried various 15.1 roms as my device is not officially supported by lineage, again no luck
---------- Post added at 07:32 PM ---------- Previous post was at 07:20 PM ----------
pijes said:
have you tried using stock rom and see if the problem persists?
Click to expand...
Click to collapse
I have and the problem goes away....thing is the device is so much better on OREO
alex.do said:
yesterday I got it happened again: one of my sim cards suddenly lost signal. completely. and since then it keeps happening so randomly. please help!
im currently on oreo 41.3.A.2.75, BL unlocked, kernel packed by serajr's tool using ta_poc method with my own original TA, magisk installed, systemlessly xposed. i got it all working fine. until this issue happened.
i've also tried different ways: reflash, wipe data completely including sdcard, switch to DRMfix method, remove app by app, remove xposed... even switching SIM slots.... no luck so far.
about the issue, it just happens randomly without any clue. one of my SIM card just disappears. sometimes this one, sometimes the other. until now the only way is restart and pray it won't happen again.
please help! please!
Click to expand...
Click to collapse
similar thing i replied here
plzzz see
https://forum.xda-developers.com/showpost.php?p=77103551&postcount=190
Hi,
After unlocking the bootloader with the latest official app, I cannot change the screen lock method of my Zenfone 6 with a message saying "Screen lock was already changed, try again with the new screen lock" and I can only choose "None" or "Swipe". The fingerprint breaks as a consequence because it relies on PIN/password/Gesture.
The phone comes with a fingerprint + password authentication before the unlocking, which seems to cause my issue due to mess-up of the TEE. Factory reset / Reflashing the whole image doesn't work.
Anyone experiencing similar issues? Is there any way to re-enable other unlocking methods?
Thanks!
Same happened to me,
I got back the pin option only when I relock the bootloader.
I used the official asus application, I'm gonna try the adb unlock option
Same thing here. Unlocking the bootloader breaks it. I fixed mine by flashing the downgrade to P zip, setting my phone all back up and then updating to Q. You might be able to just reflash Q and have it work, but if that fails go to P and then upgrade. Haven't had an issue since.
Did you downgrade to P being bootloader unlocked? If so , did you use the official asus method with their apk, or did you unlock with adb?
Thanks for your response !!!
[Removed]
DaConcho said:
Same thing here. Unlocking the bootloader breaks it. I fixed mine by flashing the downgrade to P zip, setting my phone all back up and then updating to Q. You might be able to just reflash Q and have it work, but if that fails go to P and then upgrade. Haven't had an issue since.
Click to expand...
Click to collapse
I can confirm that reflashing stock Q image doesn't work.
joesa said:
Did you downgrade to P being bootloader unlocked? If so , did you use the official asus method with their apk, or did you unlock with adb?
Thanks for your response !!!
Click to expand...
Click to collapse
I could never get the adb unlock method to work at all. I used the app to unlock, stayed unlocked and flashed back to Pie, then updated to Q
DaConcho said:
I could never get the adb unlock method to work at all. I used the app to unlock, stayed unlocked and flashed back to Pie, then updated to Q
Click to expand...
Click to collapse
Thanks,. A will try your method this weekend and let you know :good:
DaConcho said:
I could never get the adb unlock method to work at all. I used the app to unlock, stayed unlocked and flashed back to Pie, then updated to Q
Click to expand...
Click to collapse
It worked !!!!
Did exactly what you did and now I got back the screen lock options,
Thanks !!!!
So, I am on a custom ROM, but I understand that you solved this on stock. Does anyone have experience how this can be solved on a custom ROM? Thanks!
Hey, I was having the same problem and tried doing several things without success (Like deleting files in the /data/misc/keystore, changing different ROMS, etc). What fixed it for me was restoring the vendor partition, the problem was that I removed the enforced encryption flag and that was causing problems with the GSIs I was installing.
Xanderco said:
Hey, I was having the same problem and tried doing several things without success (Like deleting files in the /data/misc/keystore, changing different ROMS, etc). What fixed it for me was restoring the vendor partition, the problem was that I removed the enforced encryption flag and that was causing problems with the GSIs I was installing.
Click to expand...
Click to collapse
how did you restore the vendor partition? did you use the backup on twrp or something? is there a flashable zip?
also did this happen after you unlocked or after you installed a custom ROM with encryption disabled?
Did you guys manage to fix it? I actually have the same problem with my Redmi 8A after flashing Magisk on Havoc and Stock ROM. I tried to delete the locksettings. db and .key files but i still can't set a pattern or PIN
redm4227 said:
Did you guys manage to fix it? I actually have the same problem with my Redmi 8A after flashing Magisk on Havoc and Stock ROM. I tried to delete the locksettings. db and .key files but i still can't set a pattern or PIN
Click to expand...
Click to collapse
Do This It will Work Tried and Tested
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
Do This It will Work Tried and Tested
for video reference -https://www.youtube.com/watch?v=WOsUbcTQhrY
Above link is not my video so
What worked for me was re-locking the phone with fastboot. I didn't have to mess with any files.
drish malhotra said:
Do This It will Work Tried and Tested
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
Do This It will Work Tried and Tested
for video reference -https://www.youtube.com/watch?v=WOsUbcTQhrY
Above link is not my video so
Click to expand...
Click to collapse
Spot on !
Removing the .key and lockfiles from /data/system works !
I can set PIN again
....
Swipe TWRP on your phone, enter the system, and delete 2 locksettings....file in the DATA\ SYSTEM\ folder directory.. The file at the beginning can be successfully protected by restarting and setting a password or fingerprint.
abprie said:
So, I am on a custom ROM, but I understand that you solved this on stock. Does anyone have experience how this can be solved on a custom ROM? Thanks!
Click to expand...
Click to collapse
just aslo wipe vendor before flashing the rom it will help u. If doesnt work just ping me.