Hi everyone,
First, thanks everyone for all the information I have found in this forum for the past few weeks.
Now my problem : I have a Moto G 4G XT1039 that keep losing signal randomly. The only way to get my signal back to call or receive sms seems to be a reboot of the phone.
I don't remember exactly when it started but I think it was around June. Until a month ago I never tried to root or flash my phone. I just used the official updates from Motorola. I live in France and the phone is perfect for me except this problem.
I read here and there that a lot of people seems to have the issue but I'm surprised nobody seems really pissed of.
I downgraded to 4.4.4 to see if it would solve my problem but it did not. I read that the signal loss could be caused by Android 4.4.2 so should I downgrade further ?
This weekend I flashed a nightly from CM 13, the problem is still here.
What can I do ? The problem seems to be related to the radio firmware, can I downgrade the radio firmware and keep a recent android or CM13 ?
For information my baseband version is m8926_309101.02.03.14r.
I'm not sure I post my problem in the good forum but it could help other people in my situation.
If someone has an idea....
Thanks
Firstly try the Stock ROM and Radio Firmware available here: http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816 - follow flashing instructions to the letter - after this you can move on to CM13 if desired.
Well I have already done that, after I tried the 4.4.4 version.
I was on 5.1 then I downgraded to 4.4.4 then got back to 5.1 then tried CM 13.
RadiNash said:
Well I have already done that, after I tried the 4.4.4 version.
I was on 5.1 then I downgraded to 4.4.4 then got back to 5.1 then tried CM 13.
Click to expand...
Click to collapse
Did you fastboot flash the Radio Firmware from that thread? Commands are in FAQ.
Yes I did. I event tried to flash the 5.1 radio firmware while still having the 4.4.4 android.
The baseband version I gave in my opening post is the last one for the EU region I believe.
Other Solutions to try:
1) Change SIM card / get a new SIM
2) Fastboot flash the Stock Factory Firmware Image for your phone - http://forum.xda-developers.com/mot...falcon-factory-firmware-t3110795/post64203816
Thanks, I was going to order a new sim card to try this solution.
I already flashed the latest stock firmware last week but i will try again from scratch to be sure.
Provide fastboot logs (copy and paste command prompt) when flashing the firmware image. Fastboot may not provide errors, "okay" can mean total failure.
Hi,
Just to say that there is apparently no more signal loss with the CM13 nightly from 12/11. I hope it will last.
In the end I didn't flash stock firmware.
Thanks again for your suggestions, I will come back if the problem is back.
Last night, I saw a new firmware version available and updated to it - 6.0.1-7VAB-UEB0 (6045I).
Right after the update, the SIM card is not recognized.
Rebooting didn't help.
I also tried restarting the phone without the SIM card and then restarting again with the card back in.
Any idea how to fix this?
How do you update? Ota or flashing rom via TWRP? Maybe is modem problem..or missing some partitions.
OTA
Was the update issued by a carrier?
Edit: I got the 7VAB OTA update in mid-2016 and got notice of OTA another update to 7VGE yesterday for my Canadian Idol 3 6045I.
Maybe check for OTA updates again?
Very weird.
I ended up doing a Factory Reset and then the phone was able to read the SIM.
Right after the Factory Reset, I got the update notice for 7VGE-UEE1.
After this update, everything seems to be fine.
Maybe, the previous update itself was for the 7VGE - but, the update failed, leaving it at 7VAB?
Is that possible?
I'm really not sure as my phone is still running a stock 5.02 ROM and the update I received on the phone was the 7VGE, not the V7AB.
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
finshan said:
Getting a new-in-box Note10+ today from Swappa, so I assume it will be on some Android 9.0 TMO firmware. I need to get it onto the Verizon firmware.
SamFirm only gives the latest Android 10 firmwares. (It may be important to note that the VZW and XAA files both have the exact same filename: SM-N975U1_10_20200118102941_hj8esiossq_fac)
Is it safe to open the box > go straight into download mode > flash the newest VZW firmware via Odin?
Or are there other things I should do first? For example (in no particular order):
- first boot
- updating the software via settings
- flashing XAA firmware, THEN first boot with verizon sim already in phone per this thread, THEN flash VZW firmware
Thank you. Also any other suggestions are welcomed.
Click to expand...
Click to collapse
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Youdoofus said:
100% safe to immediately flash VZW firmware. The phone wont know any difference if you booted it first or not.
Click to expand...
Click to collapse
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
finshan said:
Thank you. And I just noticed this is the Note 10 forum not the 10+ forum (thanks google)...
What about concerns per the thread I linked where flashing VZW firmware is still recognized as a TMO device unless you boot the XAA firmware with the verizon sim before flashing the VZW firmware? Is that an old issue that's no longer a problem now?
The device won't mind that I'm jumping from an older version of Android to a newer version? What about the bootloader version, when does that get updated, as I understand it's currently on version 2 and how will that affect this process?
Thanks again, you post was short and being an $800 device I obviously am trying to have all my bases covered before messing with it.
Click to expand...
Click to collapse
you cannot go backwards in bootloader revisions, but you can go backwards in android versions as long as theyre on the same BL revision(not likely, but who knows? I didnt look yet). Also, the worst thing that could happen if you try to flash an older BL version is that itll fail in Odin and will still allow the phone to boot normally (usually, and if it doesnt, its still fixable). The only issue with booting it after flashing new firmware with your current sim is that itll install the carrier specific stuff on the phone so long as the CSC needed for that is in the multi CSC pack you flashed on the phone, and if it does install the carrier crap you dont want, just factory reset it and reboot with the actual sim you want you use
no problem man, thats what we are here for
Hello all,
I purchased a Galaxy A52 4G dual-sim model, and am (mostly) very happy with it. I bought it specifically for two reasons: because of the dual sim support, and the fact that there was a LineageOS rom available here at XDA. So, I promptly unlocked the bootloader and flashed TWRP and LineageOS 19.0 (big thanks to Simon1511 for his work on that!).
Everything is working great except for the second sim slot, which ranges from almost-functional (everything except voice calls work, no audio at all in call) to completely non-functional (cannot even connect to the tower), depending on which of my SIMs I put in it. The other slot is fully functional with either sim.
I noticed under Settings->About Phone that the phone reports it's model as SM-A525F, but the baseband version shows as A525MUBU4BVC2. According to the info at sammobile.com, that version is intended for an SM-525M, which this phone says it is not. I have no idea how that happened, and I wish I had done some testing with the phone when I first got it, before blowing away the stock rom. Ah well.
Hoping that my sim slot problems are the result of the wrong baseband firmware being installed, I downloaded the latest version for the SM-525F from sammobile (A525FXXS4BVD1), extracted the modem.bin and NON-HLOS.bin files, and tried flashing them to the device using Heimdall v2.0.1 (Linux user here, so Odin isn't an option and the 'official' Heimdall v1.4.2 threw various libUSB errors. v2.0.1 is an unofficial fork that worked, used it to load TWRP without problems.).
It uploaded, but the download mode screen displayed SECURE CHECK FAILED, and after rebooting the version listed under settings had not changed. Everything still works as well as it ever did, which is nice. Knowing that a mistake in this area could potentially brick the phone, I decided to create an XDA account and post here looking for some advice before making further attempts.
As I was putting this post together, it occurred to me to check the invoice. I bought it through Amazon, and it was listed as an A525M on the invoice, for what that's worth. And, the fine print on the back of the phone itself reads SM-A525M/DS. So perhaps it is an SM-A525M and the baseband version is correct, with the settings showing model: SM-A525F being the error. That would explain why the baseband firmware wouldn't flash, it knows it's not the correct bin file for the phone.
I suppose there is also the possibility that it's simply a hardware problem, and the second sim slot has something physically wrong with it.
Can anyone point me in the right direction?
Hi,
I'm certainly in no capacity to guide you, but I just brought the phone myself and have been lurking this forum to harvest a few guidelines. Regarding LineageOS, I saw there might be some problem with Dual Sim there :
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com
It could be you have the same issue as the guy and this is not related to your baseband firmware?
If I may ask, as a fellow Linux user myself, would you mind describing the guidelines to use download a working version of Heimdall and use it to flash e.g. TWRP on the phone? That would be much appreciated.
Flash the proper firmware for your device using odin. Then try installing lineage again.
@Flyos: I haven't seen or used any options for turning off SIM slots, so hopefully that isn't part of the problem. The source for the copy of Heimdall I used is available at https://git.sr.ht/~grimler/Heimdall/ . You'll have to compile it yourself.
@Ryzen5950XT: Thanks, but that's not terribly useful advice, given that part of the problem is that the device is giving me conflicting information regarding it's model number.
I'm still going to take it, though. I'll assume it actually is an SM-A525M and go from there. And I'll use Heimdall. It's served me well with every other samsung phone I've used, and Odin simply isn't an option without Windows, which I don't have and am not interested in getting.
ralanar said:
@Flyos: I haven't seen or used any options for turning off SIM slots, so hopefully that isn't part of the problem. The source for the copy of Heimdall I used is available at https://git.sr.ht/~grimler/Heimdall/ . You'll have to compile it yourself.
@Ryzen5950XT: Thanks, but that's not terribly useful advice, given that part of the problem is that the device is giving me conflicting information regarding it's model number.
I'm still going to take it, though. I'll assume it actually is an SM-A525M and go from there. And I'll use Heimdall. It's served me well with every other samsung phone I've used, and Odin simply isn't an option without Windows, which I don't have and am not interested in getting.
Click to expand...
Click to collapse
There should be a sticker on the box the phone came in that tells you which variant it is.
...yes, and I touched on that, in the original post. The phone is physically stamped SM-A525M/DS, the Settings->About Phone page says SM-A525F, and the baseband version indicates SM-A525M again. Conflicting information.
Which is why, two-to-one, I'm assuming SM-A525M is correct, and will follow your advice and reflash the stock firmware, downloaded from sammobile.com.
Hello,
You can install Phone INFO ★SAM★ 3.8.5 to see the result
Phone INFO ★SAM★ 3.8.5 APK Download by vndnguyen - APKMirror
Phone INFO ★SAM★ 3.8.5 APK Download by vndnguyen - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Phone INFO pour Android - Téléchargez l'APK
Téléchargez l'APK 3.8.5 de Phone INFO pour Android. All-in-One Info et outils pour les appareils Samsung.
apkpure.com
Ok, did a bit more testing, pretty sure this is a problem with the LineageOS rom.
Re-flashed the latest stock firmware for an SM-A525M from sammobile.com (used the brazil firmware), and Settings->About Phone now reports the model as SM-A525M/DS, which is correct. Baseband firmware version did not change, nor did I expect it to.
Tested each sim individually in each slot, then both slots together, then swapped sims between slots. Audio worked in every voice call, regardless of which sim was used for the call or which sim was where.
Then I re-flashed LineageOS as per the instructions.
Starting with the VBMeta_Disabled image, then a recovery image (Used the LineageOS recovery from that thread this time, used TWRP from the TWRP website on the previous attempt), then LineageOS, MindTheGApps, and Magisk.
After re-booting Lineage, the phone once again reports it's model as SM-A525F under Settings->About Phone, and neither sim has working in-call audio when in slot 2, regardless of whether the other slot has a sim in it.
I'll add a post to the thread linked above to report the problem, and crosslink to this thread for reference.
For the moment, I've put the sim cards back in the phones I pulled them from and shelved this A52. I'll try again when a new release is available, and see what happens.
Thank you Flyos and Ryzen5950 for your assistance!
ralanar said:
Hello all,
I purchased a Galaxy A52 4G dual-sim model, and am (mostly) very happy with it. I bought it specifically for two reasons: because of the dual sim support, and the fact that there was a LineageOS rom available here at XDA. So, I promptly unlocked the bootloader and flashed TWRP and LineageOS 19.0 (big thanks to Simon1511 for his work on that!).
Everything is working great except for the second sim slot, which ranges from almost-functional (everything except voice calls work, no audio at all in call) to completely non-functional (cannot even connect to the tower), depending on which of my SIMs I put in it. The other slot is fully functional with either sim.
I noticed under Settings->About Phone that the phone reports it's model as SM-A525F, but the baseband version shows as A525MUBU4BVC2. According to the info at sammobile.com, that version is intended for an SM-525M, which this phone says it is not. I have no idea how that happened, and I wish I had done some testing with the phone when I first got it, before blowing away the stock rom. Ah well.
Hoping that my sim slot problems are the result of the wrong baseband firmware being installed, I downloaded the latest version for the SM-525F from sammobile (A525FXXS4BVD1), extracted the modem.bin and NON-HLOS.bin files, and tried flashing them to the device using Heimdall v2.0.1 (Linux user here, so Odin isn't an option and the 'official' Heimdall v1.4.2 threw various libUSB errors. v2.0.1 is an unofficial fork that worked, used it to load TWRP without problems.).
It uploaded, but the download mode screen displayed SECURE CHECK FAILED, and after rebooting the version listed under settings had not changed. Everything still works as well as it ever did, which is nice. Knowing that a mistake in this area could potentially brick the phone, I decided to create an XDA account and post here looking for some advice before making further attempts.
As I was putting this post together, it occurred to me to check the invoice. I bought it through Amazon, and it was listed as an A525M on the invoice, for what that's worth. And, the fine print on the back of the phone itself reads SM-A525M/DS. So perhaps it is an SM-A525M and the baseband version is correct, with the settings showing model: SM-A525F being the error. That would explain why the baseband firmware wouldn't flash, it knows it's not the correct bin file for the phone.
I suppose there is also the possibility that it's simply a hardware problem, and the second sim slot has something physically wrong with it.
Can anyone point me in the right direction?
Click to expand...
Click to collapse
Do you happen to know the exact build BEFORE you flashed a custom firmware?
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com
Bugs
Fingerprint sensor on A72
No audio in calls with second SIM card