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.
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
artorelis said:
What comes to my mind at first that something wrong with your sim card but if you insist that everything is ok with your card so I don't know what to suggest to you. Is it not related with your Omega ROM?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ya, I was asking this question on the Omega forum and I am waiting for the right response.
Sent from my GT-N7100 using xda premium
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
joshphilips said:
It does seem to be Efs related. Did u downgrade from the latest firmware ? Check these links-
http://forum.xda-developers.com/showthread.php?t=2332913
http://forum.xda-developers.com/showthread.php?t=2331833
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Yes, I did downgrade from v17 back to 16 since something went wrong with Poweramp but I forgot that if I selected for the efs backup or not since I (stupidly) didn't think that efs is important...:banghead:
Sent from my GT-N7100 using xda premium
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
If the answer to this is yes: Then you should contact your carrier as it sounds like your IMEI might have been blacklisted (often if a phone is reported stolen)
If the answer is no: Then you need to fix your IMEI so it matches as it should. This would usually be done by restoring your EFS backup. I suggest restoring a totally stock Firmware if they don't match and you don't have an EFS backup. But you should have one somewhere, surely? Every tutorial out there tells you to back it up...
Good luck.
Click to expand...
Click to collapse
Thanks for replying, I should have a backup, but it probably be the wrong one. Anyway I will go for a full stock restore since I have the firmware with me now.
Sent from my GT-N7100 using xda premium
muppetmania said:
Do some basic troubleshooting:
Does the IMEI number from dialling *#06# match the one on the sticker?
Good luck.
Click to expand...
Click to collapse
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Dan Law 001 said:
Do you mean the one in the About Device ==> Status? In fact, the IMEI from the dialing does match the one in About Device ==> Status. However, I don't get your instruction since if in the case where IMEI from the setting matches the one on the dialer means that my phone is reported to be stolen, then why I have to make the IMEI in the setting and the one shown in the dialer the same?
Click to expand...
Click to collapse
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
muppetmania said:
No, when I say "The one on the sticker" I, strangely enough, mean the one on the sticker.
Take off your battery and the phone will have a sticker/label with the IMEI on it. Verify that number matches.
Click to expand...
Click to collapse
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Dan Law 001 said:
Thanks for your clearification No, it wasn't.:good: Then, I need to flash a stock firmware via Odin, right? In addition, when they say stock firmware, they mean the one that is on sammobile.com, right? In other words, if I have a Hong Kong version of GT-N7100, the file from this link (http://www.sammobile.com/firmwares/3/?download=15126) would be the correct one, isn't?
Click to expand...
Click to collapse
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
muppetmania said:
That's correct, yes. It doesn't actually matter which N7100 image you flash, but if you have a Hong Kong version you might as well flash that image. Just make sure you don't have a N7105 (the LTE/Dual Carrier version) - flashing A N7105 to an N7100 (or the other way around) is a recipe for major disaster.
Flashing the image should fix the problem, but it also depends. If the EFS is really totally corrupt, it won't help, you need to have that EFS backup or take the phone to someone who can repair it for you. There are specialist tools to repair EFS, but they cost quite a bit of money. Most reliable phone unlocking places should have something that can help you.
Anyway, hopefully restoring to stock will fix the problem.
Good luck.
Click to expand...
Click to collapse
Thanks for information, but how do I know that if the EFS is "totally" corrupt, "partially" corrupt, or not corrupt at all? In fact, I never touch the EFS in the root. Also, as I am not quite sure that if I have any previous EFS(S) backup or not, so, if possible, where does the backup(s) most likely to be found?
If you haven't taken an EFS backup yourself, then you won't have any.
I don't know the difference between corruption levels either, all I know is I've read a number of forum posts where someone has reflashed stock and their EFS data (i.e. the right IMEI number) is back. So I'd consider that to be a partial corruption. Others have flashed back to stock and it's still a bogus IMEI
Basically, flash back to stock. If it doesn't work, you'll have to take it in for repair.
UPDATE: Please read on - this information is incorrect - it is possible to recover with the correct modem flashed.
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
NOTE: The information from me in this post below is wrong
Dan Law 001 said:
Before doing the flash with Odin, do I have to perform a factory reset? Since all the app data and homescreen layout remains the same after the reboot and the IMEI is also the same as before. And is it normal that my device got unrooted after flashing the stock firmware?
Click to expand...
Click to collapse
It's normal your device got unrooted, yes. If your IMEI is still the same after ODIN and stock flash, then you have major issues (sorry!)
Doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What IMEI does *#06# show?
muppetmania said:
it's normal your device got unrooted, yes. If your imei is still the same after odin and stock flash, then you have major issues (sorry!)
doing a factory reset etc won't help. Your /efs partition is either gone or corrupt.
What imei does *#06# show?
Click to expand...
Click to collapse
004999010640000 / 01
Dan Law 001 said:
004999010640000 / 01
Click to expand...
Click to collapse
Type 004999010640000 into Google...
Sorry man. Good luck getting it fixed.
just flash ME4 modem everything will be alright
bhasg1007 said:
just flash ME4 modem everything will be alright
Click to expand...
Click to collapse
Interesting to know - why does that work? (I don't doubt you, I just like to know why things work)
Just go through this thread http://forum.xda-developers.com/showthread.php?t=2333216
Even i had the same problem no network no imei nothing after downgrading so i just changed the modem and now everything is fine as it should be
Please help me with my situations.
It is almost 1 week phone start making this problem. From beginning my phone getting boot loop. I have not root the phone. It is originally stock rom. I thought that the system get corrupted and then try to flash the phone with stock rom N7100XXUFNG4_N7100OLBFNG1_N7100DXUFND2_HOME.tar with odin.
This was my first time flashing this phone so I did not know anything about any EFS backup. After successfuly flashing the stock rom, at first I feel glad but suddenly I have got emergency call only. Then after what I have been searching and reading for almost a week, it was my IMEI 0049.
I have tried flash the stock rom again but the problem still remain. I have tried downgrade to 4.1.2 but the odin won't let me flash it. I have tried delete the EFS folder and paste the backup nv_data.bin but the IMEI 0049 still there. I don't have any service box so I can't repair my EFS from my computer. Is there any solutions I really really appreciate if and you guys can help with my problem. Thank you :good:
Did the imei in the phone match the imei on the label under the battery?
audit13 said:
Did the imei in the phone match the imei on the label under the battery?
Click to expand...
Click to collapse
Of course not, usually IMEI starts with 3***.
I know your phone has a generic imei.
What I meant is this: did the imei in the phone matched the imei on label before the problem started.
The phone was new when you got it?
audit13 said:
I know your phone has a generic imei.
What I meant is this: did the imei in the phone matched the imei on label before the problem started.
The phone was new when you got it?
Click to expand...
Click to collapse
Ops sorry, yes it was matched and the phone working perfectly normal before it getting boot loop. Can my phone still can be save without sending to samsung?
You try using nvwriter to inject the imei.
Have you tried flashing the stock rom again? I assume nd2 is the latest rom for your phone.
audit13 said:
You try using nvwriter to inject the imei.
Have you tried flashing the stock rom again? I assume nd2 is the latest rom for your phone.
Click to expand...
Click to collapse
I have not try the other version firmware yet, is it possible the wrong firmware corrupted my imei?
It is possible that the ROM flashed is too old.
I see stock ROMs here: http://www.sammobile.com/firmwares/database/GT-N7100/
audit13 said:
It is possible that the ROM flashed is too old.
I see stock ROMs here: http://www.sammobile.com/firmwares/database/GT-N7100/
Click to expand...
Click to collapse
Can you suggest me stock firmware? I am from Malaysia
I don't see firmware specifically for Malaysia. What is the original country or carrier for the phone? Where did you get the firmware that you flashed to the phone?
audit13 said:
I don't see firmware specifically for Malaysia. What is the original country or carrier for the phone? Where did you get the firmware that you flashed to the phone?
Click to expand...
Click to collapse
Well my country carrier starts with +6. I just ask my cousin to download that firmware for me since my house internet always disconnected I don't know why. I just ask him to download the latest firmware for my country.
That nvwriter guide is not for my phone. Is it work also with my phone?
Sorry, I'm not too familiar with nvwriter. I just know that some people have used it with Samsung phones.
The nv writer look promising, but it cannot read my phone cause when I select the rmnet/rndis/+dm+modem, it is only showing unknown device. Hmm my samsung usb driver already up to date.
Hello guys! I buy sgn4 from ebay. Problem is that imei and phone model on sticker and from phone "about" is different. Network is good, i can make calls, etc. Ok, i think that motherboard was changed. But serial number is only "0" as i know it is factory s/n. What should i do with this device. What happens if i flashed it with custom? I`m afraid that my imei will broke and i can use it only in "iPod touch" mode
Altair7610 said:
Hello guys! I buy sgn4 from ebay. Problem is that imei and phone model on sticker and from phone "about" is different. Network is good, i can make calls, etc. Ok, i think that motherboard was changed. But serial number is only "0" as i know it is factory s/n. What should i do with this device. What happens if i flashed it with custom? I`m afraid that my imei will broke and i can use it only in "iPod touch" mode
Click to expand...
Click to collapse
I understand your worries. I hate even giving advice on touchy matters like this, because depending on why the imei doesn't match. But I'll go over a couple senerios. For one the samsung serial number is all zeros. Mine is to.
Now the big concern is why the imei doesn't match. It's either the mother board was replaced or someone hacked it. Is the model number the same? Cause that's gonna make a big difference as to what to do.
Lets say someone replaced the mobo, but its not a Sprint mobo, then that's gonna effect how and what roms you flash on the device.
Before we move on, give me more info. In About phone, what does it say for the following:
Software version
Hardware version
Model number
Baseband version
Also do you have Twrp? And/or root?
Get me that info, and i wouldn't flash anything until you figure exactly what hardware the device is and have a full backup plus Efs backup.
aaron74 said:
Before we move on, give me more info. In About phone, what does it say for the following:
Software version
Hardware version
Model number
Baseband version
Also do you have Twrp? And/or root?
Get me that info, and i wouldn't flash anything until you figure exactly what hardware the device is and have a full backup plus Efs backup.
Click to expand...
Click to collapse
Thanks for your reply! The phone about says that i have:
Software version: N910PVPS4DQB3
Hardware version: N910P.05
Model number: SM-N910P
Baseband version: N910PVPS4DQB3
I have no root and stock recovery with ticked Knox counter
the same as my phone, my SN number is array of 0, but the phone is working flawless without any problem. You can try many roms for N910P
zRoNz said:
the same as my phone, my SN number is array of 0, but the phone is working flawless without any problem. You can try many roms for N910P
Click to expand...
Click to collapse
Ok, i try them) Tell me one more thing. I have a grid in center of screen like chess deck. Its visible only on white background. Is that normal? There was nothing like this on my previous Note 3
Altair7610 said:
Ok, i try them) Tell me one more thing. I have a grid in center of screen like chess deck. Its visible only on white background. Is that normal? There was nothing like this on my previous Note 3
Click to expand...
Click to collapse
oops, i think your phone maybe have some parts that were replaced from the seller. so why don't you contact him and ask about the phone for more information and got the refund if he sold you a bad quality phone ? the normal phone doesn't have any ghost image or blur grid on the screen. And you tell that your IMEI from system is differented from it's sticker ? Your phone maybe hard-bricked and lost IMEI, and the seller used tools to write another Phone's IMEI to your phone.
Altair7610 said:
Thanks for your reply! The phone about says that i have:
Software version: N910PVPS4DQB3
Hardware version: N910P.05
Model number: SM-N910P
Baseband version: N910PVPS4DQB3
I have no root and stock recovery with ticked Knox counter
Click to expand...
Click to collapse
That all looks good.
Now the back of phone says it's a SM-N910P? Correct?
But the IMEI's just don't match, Correct?
If this is the case, it seems that the mobo was replaced.
The main thing here to know, is if that this is indeed N910P hardware. You should be fine flashing or using Odin!
If you decide to start flashing custom roms, the first thing i would do is Flash TWRP and do a Full Backup (boot,system,data,EFS,modem,cache). And save it in a safe place (like off device, on a pc).
I believe you should be fine, either mobo was replaced or someone hacked the imei so it didn't show as stolen. Either way as long as you don't mess with your EFS, everything should be fine.
FYI, there are no guarantees with flashing! Make sure you research what your doing!
Edit: I just seen your other post about grid. I agree with @zRoNz , the screen could have been replaced with cheaper parts (digitizer) or is a burn in effect.
Edit : 1 more thing you can do. Is install 1 or more Device Info apps. And compare the hardware info they state your phone has. Just to make sure it's truely Note4 hardware!
@aaron74 thank you very much for helping. I just asked seller about this. I think that screen was replaced with no original one. And last questuon: I cant press left sensor button with s-pen. It's should work i think?
Altair7610 said:
@aaron74 thank you very much for helping. I just asked seller about this. I think that screen was replaced with no original one. And last questuon: I cant press left sensor button with s-pen. It's should work i think?
Click to expand...
Click to collapse
That all makes sense now. It's probably because of the digitizer installed. Not sensing in that region. I'm no expert on this, but that all adds up!
If you just bought this, you could try to see about a replacement. But if you can't get one, i would say how much is there to really worry about it. As long as everything is correct except that, how often will you need the spen for just that? It works everywhere else, i assume.
Good luck!
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