Please help me, my phone can't detect sim card after upgrading to JB. Even if I flash other firmware JB/GB still same. I dont have backup of anything, i'm screwed. Search everywhere, the only resolution that i think will work is using those flash box wich are expensive and i do not have those special cables that are needed.
Any help that you will post is highly appreciated.
LOL
Boxes... bricked Nokia phones... bad ol' days!
AFAIK, the reason resides in the modemfs and EFS partitions, which are different between EU and Asian firmwares. You would need to flash an Asian stock ROM which contains at least efs.bin.md5, but I don't think there may be any.
LaXiS96 said:
You would need to flash an Asian stock ROM which contains at least efs.bin.md5, but I don't think there may be any.
Click to expand...
Click to collapse
But why? How about if i restore backup of working ace?
Sent from my Z120
mark_sgy said:
But why? How about if i restore backup of working ace?
Sent from my Z120
Click to expand...
Click to collapse
If you find someone which has a working Asian Ace 2, yes, you could dd dump the EFS and modemfs partitions, but then you will have his same IMEI because of the EFS lol
There isn't any hope, so the best thing to do is sending it to RMA, since they usually don't mind (if they are not Samsung official Service) and send you a new phone.
LaXiS96 said:
If you find someone which has a working Asian Ace 2, yes, you could dd dump the EFS and modemfs partitions, but then you will have his same IMEI because of the EFS lol
There isn't any hope, so the best thing to do is sending it to RMA, since they usually don't mind (if they are not Samsung official Service) and send you a new phone.
Click to expand...
Click to collapse
This is not valid for NovaThor U8500 Chip based phones (8160, 8190, 9070)...
The IMEI is (not 100% proved but quite sure) in CSPSA_FS partition. MAC for Wifi and Bluetooth is in MODEM_FS...
The role of EFS (which is for many other phones the place for IMEI) is not clear up to now....
Normaly you NEVER overwrite you CSPSA_FS partition if you only flashed original FW.
Therefore I think there could be still a chance to recover your Phone.
Please tell me the exact details of your Phone (8160/8160P) and the FW you flashed right before your phone stucks.
Futhermore you can try this (TEE Folder method)
http://forum.xda-developers.com/showthread.php?t=2159250
fluffi444 said:
This is not valid for NovaThor U8500 Chip based phones (8160, 8190, 9070)...
The IMEI is (not 100% proved but quite sure) in CSPSA_FS partition. MAC for Wifi and Bluetooth is in MODEM_FS...
The role of EFS (which is for many other phones the place for IMEI) is not clear up to now....
Normaly you NEVER overwrite you CSPSA_FS partition if you only flashed original FW.
Therefore I think there could be still a chance to recover your Phone.
Please tell me the exact details of your Phone (8160/8160P) and the FW you flashed right before your phone stucks.
Futhermore you can try this (TEE Folder method)
http://forum.xda-developers.com/showthread.php?t=2159250
Click to expand...
Click to collapse
Yeah, but WiFi and BT MAC addresses cannot be located in the modemfs partition, since they are unique per physical device and flashing any FW would mean changing it (and then many people would have the same MAC)... They must be elsewhere.
LaXiS96 said:
Yeah, but WiFi and BT MAC addresses cannot be located in the modemfs partition, since they are unique per physical device and flashing any FW would mean changing it (and then many people would have the same MAC)... They must be elsewhere.
Click to expand...
Click to collapse
If you flash the MODEM_FS and EFS (via DD ADB) from an other Phone you will have also the Wifi MAC of this phone!
Made this recently during my test to bring back 8160P... see sig.
If I flash an foreign DUMP to my phone and flashback my MODEM_FS + EFS my original MAC is recoverd.
Do you have anything to prove your statement?
fluffi444 said:
If you flash the MODEM_FS and EFS (via DD ADB) from an other Phone you will have also the Wifi MAC of this phone!
Made this recently during my test to bring back 8160P... see sig.
If I flash an foreign DUMP to my phone and flashback my MODEM_FS + EFS my original MAC is recoverd.
Do you have anything to prove your statement?
Click to expand...
Click to collapse
Then it would mean that when flashing a stock FW the modemfs and EFS partitions do not get wiped but instead just updated.
LaXiS96 said:
Then it would mean that when flashing a stock FW the modemfs and EFS partitions do not get wiped but instead just updated.
Click to expand...
Click to collapse
First of all show me an original full FW that inculded MODEM_FS or/and EFS (and/or CSPSA)... I do not know one!
That leads me to the opinion that they stay untouched (or only being updated while first boot after ODIN flash)
BUT: The well known RUS GB FW has quite all partitions included - also the obove mentioned. And this do not change IMEI and/or MAC adresses...
Comparted them with my original partitions recently and it looks like that the RUS FW has emty parts in there...
But this is still not proven how this all works...
fluffi444 said:
First of all show me an original full FW that inculded MODEM_FS or/and EFS (and/or CSPSA)... I do not know one!
That leads me to the opinion that they stay untouched (or only being updated while first boot after ODIN flash)
BUT: The well known RUS GB FW has quite all partitions included - also the obove mentioned. And this do not change IMEI and/or MAC adresses...
Comparted them with my original partitions recently and it looks like that the RUS FW has emty parts in there...
But this is still not proven how this all works...
Click to expand...
Click to collapse
I was going to upload the RUS GB ROM tar image until i read the last part of your message :laugh:
Now everything is clearer, at least to me.
Related
So... I seem to be having the efs corruption issue with my co-worker's phone. I've been searching all over and have found how others have solved the problem, but it seems that our nv_data.bin is not located in our efs directory.
Does anyone have any idea where these files are? I need to check the last modified dates of their backup files to see if I can restore them >.<
Any help is greatly appreciated!!
Bump.. If anyone knows where these files are this could help us from running into the corrupt efs problem that many people have had. Usually backing up your efs prevents your phone from becoming unable to function as a phone.
I do remember reading something about our unlock code not being present in our nv_data.bin.. And when I check my efs folder in both my, as well as my co-worker's phone there is no nv_data.bin so maybe it has been relocated??
Anyone with knowledge on this subject.. your input would be greatly appreciated! I'm also gonna read over the unlock threads to see if there is any relevant info there.
I am having this problem now, I know you posted this over a month ago, but please tell me you know the location of the backup files or any other solution for this?'
Thank you,
[Q] T989 - Baseband and IMEI Unknown
I have searched and read many threads already. I understand the i9100 uses a file called nv_data.bin and requires its .bak file for a fix.
But, I dont think the t989 is the same because these files dont seem to exist, or at least not in the locations the threads for i9100 state. I am wondering if anyone has had this problem and/or how they fixed it. I know it was caused because of trying to unlock, but I'm looking for a solution.
Thanks!
just buy one of those $20 online unlock or go to your local phone kiosk to have it unlocked
any one with a machine to unlock Samsung phones can get this phone unlocked easily
there's no software unlock yet, as you have found on your searches
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
svahora said:
I have T-Mobile and don't really care for the unlock, it was a mistake. At this point, I just want to fix the unknown IMEI and unknown Baseband issue. Because of this problem my phone cannot get a signal... Will performing a machine unlock fix this problem?
Note: When I type in *#06# the response is not my IMEI number. It says "null"
Click to expand...
Click to collapse
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
KillaHurtz said:
You can try to find someone locally with a SPT Box2. This unit can flash, unlock & repair IMEI on SGH-T989(d). I was gonna pick one up, but they are like $250 yikes !!
Click to expand...
Click to collapse
What does the (d) stand for?
And, how can I make sure this never happens again in the future? I know there are backup options out there (CWM, Nandroid), but are there any that make a complete clone of the phone's image? In case I mess up the efs or IMEI files again I can restore and be ok.
Thanks!
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
AllGamer said:
T989D = Canadian release of T989
they are identical, the just use the D for Canadian
Click to expand...
Click to collapse
Would a Nandroid backup fix this in the future?
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
AllGamer said:
is hard to say, we have no idea where is the real IMEI information is being stored in the new models, but is no longer in the old EFS folder
Click to expand...
Click to collapse
I wonder if the new Galaxy Nexus has its IMEI files stored similarly. If so, we can join forces with that forum group.
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
-Mr. X- said:
If Android is not mounting your firmware properly in the system this will cause no baseband and no imei detected. i would try and flash the stock rom to make sure.
Click to expand...
Click to collapse
Did it twice, the stock rom, modem, and kernel.
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
cyberjam said:
The radio (modem firmware) might have got corrupted if somebody tried to flash international GS2 ROM or modem.
Try to flash only the Radio (KL1 is the latest for T-Mobile) via ODIN (use PDA slot).
Click to expand...
Click to collapse
Would the KL1 work any different than the older one? I tried ODINing the original one, and it didn't work and increased the count so I didn't try the KL1.
I just got my replacement phone yesterday for this same problem. Flashed the stock kernal, and also the modem just to be safe and nothing would fix it. From what I know its just a hardware issue, not software. I was chatting with samsung and t-mobile people about this trying all kinds of fixes to nothing left but hardware defect.
Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
samdev09 said:
Phone: Samsung Galaxy Nexus GT-i9250TSGGen
I had a stock android version, that I never rooted or flashed. Suddenly the SIM stopped working, I figured out that there is no IMEI number and the baseband is unknown.
I flashed to a custom ROM, and tried to do few things using the Galaxy Nexus Toolkit:
1) custom ROM android 4.1
2) Flashed a custom radio
3) made a copy of the /efs folder, deleted the original and replaced it after restart.
The Samsung service center said the entire board has to be changed, with an estimated cost of $140 USD.
Can someone help me with my options? Is it definitely a hardware problem? is there anyway to know for sure?
Click to expand...
Click to collapse
If you have a nandroid back up, try and restore with it. This could solve ur problem.
saishyamk said:
If you have a nandroid back up, try and restore with it. This could solve ur problem.
Click to expand...
Click to collapse
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
samdev09 said:
Thanks, but I hadn't created a back up before. Is there a way to use a back up from a different phone? where would l find more information?
Click to expand...
Click to collapse
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
saishyamk said:
I had an old nandroid back up and I used the method in this post to fix my IMEI problem: forum.xda-developers.com/showpost.php?p=47048361&postcount=9
And when you said you took a back up of the /EFS folder, you meant pulled the .bin and .md5 files from the /factory or the /radio folders OR did you use something like kTool? Because, as people have pointed out in other threads there is no /EFS folder for the Galaxy Nexus. The IMEI information is stored in the Radio and Factory Folders. For more information on how IMEI works on the GNEx, refer to this post: http://forum.xda-developers.com/showpost.php?p=47045295&postcount=6
But you are saying the baseband is also unknown. A radio flash should have fixed it. Try restoring Stock ICS using Odin. i hear this fixes some problems like this. U can use thus guide forum.xda-developers.com/showthread.php?t=2065470
If Odin is a little complicated, try the Nexus Root Tool kit. U gotta experiment to find the right problem and them fix it. No other go. I doubt that replacing the board will solve it as it looks like a software issue, unless you fried your radios.
Click to expand...
Click to collapse
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
samdev09 said:
Thanks again. Yes, the /efs folder is not where it was supposed to be. I did find the correct location and moved it. I will try using your ideas. Just one more question:
Since I had not done anything that would wipe out my IMEI number (neither software hacking nor physical damage). I wonder why this problem suddenly occurred. Just to eliminate a possibility, how can I know for sure that I have not "fried the radios"?
Appreciate your help. If I know that it is a software problem, I can continue to play with the Nexus toolkit and try different solutions.
Click to expand...
Click to collapse
I'm not sure how to check if your radio is fried. Basically, it means something's wrong with your hardware, where you experience occasional or complete signal loss. But in your case, you lost your IMEI. So, back up your nv_data files, flash using NRT or ODIN and see what happens.
NRT will push the stock radio while doing the "Flash Stock + Unroot" Option. So, you'll get the stock baseband as well. This should fix it. If your IMEI still doesn't work, try restoring the nv_data.bin and md5 files you backed up as mentioned in the link I posted.
Let me know how it works out. :good:
Always make a backup of /EFS (Support in both PhilZ_CWM & TWRP )for safety, though the IMEI would be only wiped by CWM wipe /factory option......happened to me a few days back, luckily i got my /efs restored & flashing stock doesn't bring any IMEI back since it's actually phone specific plus comes with a proper MD5 !!
the above method should work and here more info on the EFS
Hi, I've been trying to find a solution for the problem of null IMEI I'm having after wiping EFS partition on the Chinese TWRP, maybe it's not that and it is because I've erased modemst1, modemst2 and flashed modem+fsg.
I'm pretty sure it had to do with one of those procedures, when I wiped the EFS I've got some error saying it couldn't be done but something went missing.
I've got a more direct question now, my brother just bought a Moto Z Play yesterday, if I backup his EFS on my phone (he already asked if I want to do that) will both of us would be able to use our phone normally?
can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs
kkarora said:
can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs
Click to expand...
Click to collapse
No way, like you already now, each phone has an individual IMEI. Your phone is unfortunately unusable.
What did you attempt to do? Flash another firmware package ?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
No way, like you already now, each phone has an individual IMEI. Your phone is unfortunately unusable.
What did you attempt to do? Flash another firmware package ?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
isn't there ANY way of rewriting this thing back?
mcaxtr said:
isn't there ANY way of rewriting this thing back?
Click to expand...
Click to collapse
Unfortunately no
mcaxtr said:
isn't there ANY way of rewriting this thing back?
Click to expand...
Click to collapse
Lenovo could generate it. But they probably instead replace the main board. You may ask them how much the repair is.
I think I'll just take it there and see if they can do anything about.
well, lesson learnt hard way
mcaxtr said:
I think I'll just take it there and see if they can do anything about.
well, lesson learnt hard way
Click to expand...
Click to collapse
New motherboard unfortunately
Now you know not to use fishy Chinese recoveries.
efs
Hey you can use sigma box to restore imei which will cost you around 800 rs,same thing happened for me but still not fixed just using with wifi
If partition can be wiped, then is not read only. If is not read only, should be possible to write backup back. Otherwise, what's the point of the backup?!
Each phone should/must have different IMEI, depending of the network. In theory, should be possible to take partition from one phone and write to another. However, Moto maybe prevents that checking some hash, serial number... If it's possible to write partition from another phone, again question is can those two phones be on the same network in the same time. I also saw a way to change IMEI, I think even on this sub forum.
If someone solve this problem I definitive pay to that sir, he would be rich In the first day..
kkarora said:
can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs
Click to expand...
Click to collapse
did u got efs, im too wiped my efs partition
Anybody has an idea how I can get my CSC and PDA back?
I flashed a 4-parts stock firmware prior to ResurrectionRemix with OXA (DBT) CSC for my country Germany.
And now I have the situation as you can see in attached screenshots (taken from Phone Info +).
regards
If you have no issues with call reception / mobike data, just dont care. I also flashed Hong Kong firmware first (as it was latest by date) and have no issues since then.
j1gga84 said:
Anybody has an idea how I can get my CSC and PDA back?
I flashed a 4-parts stock firmware prior to ResurrectionRemix with OXA (DBT) CSC for my country Germany.
And now I have the situation as you can see in attached screenshots (taken from Phone Info +).
regards
Click to expand...
Click to collapse
Pretty much all of that is stored on the EFS partition. Just restore your EFS backup.
The problem is that I guess I have no efs backup..
Regards
Sent from my SM-G960F with Tapatalk
j1gga84 said:
The problem is that I guess I have no efs backup..
Regards
Click to expand...
Click to collapse
You can modify the EFS yourself with root.
@ashyx
Can you tell me how to do that? Or is there a manual here on XDA or somewhere else?
I guess this error occured while switching from my broken Tab S to a new one..
regards
j1gga84 said:
Anybody has an idea how I can get my CSC and PDA back?
I flashed a 4-parts stock firmware prior to ResurrectionRemix with OXA (DBT) CSC for my country Germany.
And now I have the situation as you can see in attached screenshots (taken from Phone Info +).
regards
Click to expand...
Click to collapse
It looks exactly the same on my tablet as well. I don't think it's a big problem if you don't have problems with calls. If you do, try flashing a stock firmware before modifying the EFS - I had such an issue and flashing the latest firmware for my country fixed it. You should also make an EFS backup in case it gets corrupted.
marti201 said:
It looks exactly the same on my tablet as well. I don't think it's a big problem if you don't have problems with calls. If you do, try flashing a stock firmware before modifying the EFS - I had such an issue and flashing the latest firmware for my country fixed it. You should also make an EFS backup in case it gets corrupted.
Click to expand...
Click to collapse
Making the EFS backup is mandatory for Samsung devices right after you get root. Also, PARAM partition is worth being backed up. In my T805 topic, I explicitly put the backup step as a ground requisite for flashing anything.
marti201 said:
It looks exactly the same on my tablet as well. I don't think it's a big problem if you don't have problems with calls. If you do, try flashing a stock firmware before modifying the EFS - I had such an issue and flashing the latest firmware for my country fixed it. You should also make an EFS backup in case it gets corrupted.
Click to expand...
Click to collapse
As already mentioned in my first post, I did flash a 4-piece stock firmware but this did not help..
maybe I have to do some special settings in ODIN?
It must be possible to get CSC and PDA back...
I have a broken T805 where the display does not work anymore but I could try to backup the EFS.
Would it be possible to restore that EFS on my other T805?
regards
First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.
JoiaDG said:
First of all, i started being a newbie, i just wanted to install magisk for cam2api, but i messed up: i combined for error 2 different system (mine that was ios9 and ios8). So i tried to read more and more threads and it just got worse. to make the story short: i had to get to test-point and restore the phone with Xiaomi Mi Flash tool & an original rom stock.
So now that i can go inside the Android System and use the phone, my sim card is just not working, i checked and my imei was 0 and my IMEI SV also 0.
I tried deleting modemst 1 and 2, i tried to reflash the phone with another stock images, updating the phone via android (normal way), i tried to restore my imei with the QPST Dual Imei (and it worked but the IMEI SV still in 0). nothing is working Please i need help i think my efs folder it's corrupted but i'm not shure.
Also i don't have any EFS backup or System backup, nothing.
Click to expand...
Click to collapse
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this https://zfirmware.com/how-to-repair-qualcomm-imei-via-qualcomm-write-imei-tool/
Sadly not working
SubwayChamp said:
I´m not sure what you mean by ios8 and ios9, maybe oreo and pie.
For the next time just so you know test point method is not recommended while you are not completely bricked (although is recommended out there without care), on a unlocked device most probably you won´t need it to solve this kind of issue, there are other resources to try previous to this stage.
I never had this kind of problem, you might try this
Click to expand...
Click to collapse
Sadly, it didn't work. i was thinking if there was a way to do it with root
JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here: https://androidmtk.com/download-qualcomm-smartphone-write-imei-tool
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.
I need help
TheoXSD said:
Try rewriting the IMEI's from the box (I hope you still have the box and paperwork since there is the original IMEI's) with the Qualcomm IMEI Tool. Reflash full stock rom.
The tool is here:
If everything fails and your knowledge is not helping you to find a solution and you are still under warranty and respect the warranty for physical aspect of the device (no scuffs, no damage, no aftermarket replaced parts that may damaged warranty voids inside the phone) you can flash it stock, lock bootloader and file a warranty replacement as "damage from OTA". The service will replace your motherboard.
Click to expand...
Click to collapse
I know i have to use that tool, but my device is not recognized by that app, i tried to install all the drivers, but nothing's working.
JoiaDG said:
Sadly, it didn't work. i was thinking if there was a way to do it with root
Click to expand...
Click to collapse
I knew that there is a method to restore IMEIs via adb but I don´t remember commands so I never need it. First I do before tinkering device is to backup IMEI/EFS/NVram.
I had a theory that years ago I proved, IMEI is not really lost but just overlapped so if you have some friend that can give you their backup this will recover the yours but won´t overwrite/replace the yours. Not sure if it works yet.
About the tool that I linked maybe you need to get it through either in fastboot or download mode, try both; I don´t think that detect it while device is on.
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial
JoiaDG said:
https://forum.xda-developers.com/mi-a2-lite/how-to/sim-network-solution-alternatively-t3914161 i fixed the phone with this tutorial
Click to expand...
Click to collapse
Yeah this fixed my phone too, now I'm making backups