wrong imei in phone. - HTC Excalibur

hi. i need help for repair imei of htc dash. it was used with tornado sim for unlock but now phone do not working with it and imei is danger. when i try see imei *#06# phone show 00440000350111200.
if any have how help me for repair imei original, i thanks you

tictac_m said:
hi. i need help for repair imei of htc dash. it was used with tornado sim for unlock but now phone do not working with it and imei is danger. when i try see imei *#06# phone show 00440000350111200.
if any have how help me for repair imei original, i thanks you
Click to expand...
Click to collapse
arent imei's coded to the hardware like a MAC address? not sure if there is much we can do...
when you say imei is danger, are you referring to a sidekick kinda danger? if so, you got me stumped. how did you manage to change the imei?

i talk over imei of phone, it is wrong phone imei original is 351553016438023 but when you try see imei with *#06# phone show 00440000350111200, the two finish numbers is for t-mobile phone but same imei is bad.
the history is: the phone working good 2 weeks with tornado sim for unlock but one day phone show new time sp code entry, tornado sim do not working more for unlock it phone, the own contact to me for unlock it phone and it when i see that imei is bad.
phone is not in black list or other ilegal case. if have error in imei.
i try with wst 4.2.2 and program show it
-----------------------device info:
Wizard Service Tool v4.2.2
29/08/08 09:18:09
CPU Manuf. FAILED
IMEI:
=> Bootloaders:
IPL: þÿÿê (G3 device)
SPL date unknown
Registry AKU: .3.0.1
after it program show error and close.
-----------------read cid
[red]Decrypted stored sum: 2020202020202020
Decrypted calcd sum: CB2C31FAACFE5801
Checksums did NOT match!!
Could not determine a key index to decrypt it.
Your CID block must be corrupted or file isn't
from a valid CID dump!!
Aborting operation.[/red]

cant you call the provider and ask them? it doesnt sound like something that can be fixed on a forum...i may be totally wrong like usual though.. jockyw2001 might have some insight...i dunno

dang thats weird yea jus go with gixxum and call them that would be my best gues

Messing with IMEI numbers is how phones are cloned and, consequently, is illegal in most countries.
There are plenty of tools available but I suspect the Mods will stomp all over a thread regarding their use.
Also, it's a really bad idea to post your IMEI number on a forum.
Honest.
** EDIT - If you must, then post a friends, sit back and watch the bills keep rolling in ...

I had the same problem with my t-mobile wing; which i am using att sim card; the phone and card both unlocked. the only way i found to get rid of the error message was to re flash my phone with a different rom from xda developers. The phone would dial out upon every time it was restarted and cost me 15 cents every time. now i don't have to worry about turning off my phone and getting nickel and dime to death.

i also have the same problem

It is illegal to change an IMEI for ANY reason. Even if it is done accidentally. I suggest not calling your service provider and just getting a new phone.

Related

Imei number

Hi
Im gonna unroot my phone when i get home.....will this change or have any affect on my imei number?
Reason is, i called t-mobile to get them to unlock phone ( and gave them my imei number) they say it takes about 10 days, will flashing my phone again during this time balls up the process ?
thanks
As far as im aware this will not change your IMIE < Thats actually illegal in the uk and various other countrys.
the IMIE should be device specific, whatever the mod or rom flash.
cheers Potter

Professional Help and advise needet.

Hello to everybody,
First of all sorry for my english.
So about what is the tread
There is arround 10 bricked phones in Bulgarian Android Forum.Becouse we cant find where is the problem I decide to ask here.
Problem: After flashing stock test 4.3 and downgrade after back to 4.1.2 the result is --IMEI 0049 and Permanent Test Mode.
what we know until now:
Phones bought from shops for phones reported they downgrade back without issues
Phones bought from mobile operators -bricked IMEI
Flashing again 4.3 after brick do not restore IMEI
P.s
Sorry if the tread is on wrong place and 10x for your opinions about problem
Find someone knows English better to translate it for you
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2420881
If you dont have efs backup then you probably need the z3x box to make repair for your imei and change it to the original one didnt test the ariza patch on this kind of problem but why not give it a shot
Sent from my GT-N7100 using xda app-developers app

Need help correcting bad MEID and ESN

I bought a used LS990 on Ebay and I rooted it and installed TWRP and later tried activating it but it refused to connect to sprint's network so I did a complete factory reset with the .tot method and that did reset it and get rid of the secure boot errors but it also changed the ESN, MEID, IMEI, and all other identification information. I have tried using CDMA tool, QXDM, and also dial codes to modify those values but whenever I use computer based tools it seems to either not go through or revert immediately. Right now it is showing obviously corrupt data
Phone number: 0000008784
MIN: 000008784
ESN: 808D1BB1
MEID HEX: 35030526000000
IMEI: is correct, I was able to change it to my actual MEID and CDMA tool added a 3 to the end
Brand: Chameleon
My SPC/MSL code is 000000, I guess that's the default one
I'm not sure where to go from here, I have spent about 6 hours total working on this, have factory resetted more times than I can count on both hands and tried everything I could find on various forums
bump
Unfortiatly thats a touchy subject on here i cant tell u how to do it but get cmda workshop or dfs it can help.
Unfortunately, someone tried to modify the EEPROM themselves without the proper tools, and the information you are seeing is the result of that. Unless you have a backup of the original EEPROM, you will not be able to repair it yourself. You can't just change the ESN/MEID that easily for Sprint (or most networks, for that matter). I can not go into details on how it's actually done, even though you probably would not be able to obtain the right proprietary software to do it with. Unless you know someone who works at a Sprint repair shop or somewhere similar, I wouldn't even try to modify the EEPROM yourself. You'll just end up with a lot of frustration and a headache and lost time. It might even be illegal.
I recommend going to the Swappa site and entering in the MEID from the sicker under the battery into the checker. If the MEID on the sticker is clean, simply take it into a Sprint repair shop and request they either send it in to be re-programmed, or they might be able to do it in shop. I'm not sure if they will charge you for that or if it would be covered under any warranties.
If it's not clean, the only way to even get a MEID dirty is to report it stolen or to not pay your bill for too long. So it sounds like the eBay seller probably shafted you if the MEID comes up dirty. Only Sprint would be able to remove it from the blacklist if the previous user didn't pay their bill. If it is blacklisted because it is stolen, Sprint will not clean the MEID at all for any reason, regardless.
Hope that helps. Good luck!
AlwaysLucky said:
Unfortunately, someone tried to modify the EEPROM themselves without the proper tools, and the information you are seeing is the result of that. Unless you have a backup of the original EEPROM, you will not be able to repair it yourself. You can't just change the ESN/MEID that easily for Sprint (or most networks, for that matter). I can not go into details on how it's actually done, even though you probably would not be able to obtain the right proprietary software to do it with. Unless you know someone who works at a Sprint repair shop or somewhere similar, I wouldn't even try to modify the EEPROM yourself. You'll just end up with a lot of frustration and a headache and lost time. It might even be illegal.
I recommend going to the Swappa site and entering in the MEID from the sicker under the battery into the checker. If the MEID on the sticker is clean, simply take it into a Sprint repair shop and request they either send it in to be re-programmed, or they might be able to do it in shop. I'm not sure if they will charge you for that or if it would be covered under any warranties.
If it's not clean, the only way to even get a MEID dirty is to report it stolen or to not pay your bill for too long. So it sounds like the eBay seller probably shafted you if the MEID comes up dirty. Only Sprint would be able to remove it from the blacklist if the previous user didn't pay their bill. If it is blacklisted because it is stolen, Sprint will not clean the MEID at all for any reason, regardless.
Hope that helps. Good luck!
Click to expand...
Click to collapse
No, the meid and esn were correct when I got it, it was totally stock. I changed the aboot which gave it a secure boot error and i did a sort of sloppy copy of my old lg g3 to the new one and some things broke but I just wanted it as a backup and/or media player. I gave it to someone as an upgrade and because of the modified aboot among other things it refused to connect to sprint networks so I did the tot factory reset and when I did that it overwrote the ESN and MEID. I checked the sticker and it didn't appear to be tampered at all and came out clean. I know tampering with the MEID and ESN are a legal grey zone but I'm trying to restore mine, not change it to someone else's. I already tried dfs and cdma workshop and both of them refused to actually change the values. I even resorted to using that manual qualcomm tool, I forget what it's called but it is used for editing those things among other things. The weird part is that I was able to successfully edit the imei to be the correct one but I was not able to edit any of the other values. I tried many things, I made sure the diagnostic mode or debug mode was enabled through the dialer, I tried it in download mode for fun, I made sure ADB was enabled, I tried changing the serial connection parameters and so much more but the ESN and MEID always refused to stick. I was thinking about resorting to editing the tot restore file somewhere with the correct values in hope that it would fix it. I'm really out of ideas at this point.
https://swappa.com/esn/shared/B7K9L8K9
that was the result when entering the hex meid
same problem
I'm having the same problem with EXACTLY the same invalid entries, after a similar system copy via TWRP from one device to another. Did you ever manage to correct the MEID and ESN?
AlwaysLucky said:
If the MEID on the sticker is clean, simply take it into a Sprint repair shop and request they either send it in to be re-programmed, or they might be able to do it in shop. I'm not sure if they will charge you for that or if it would be covered under any warranties. :
Click to expand...
Click to collapse
I tried taking a LG G3 LS990 with the same MEID/IMEI mismatch to a Sprint repair store. They said they could probably correct the problem IF the phone was on an active Sprint account, without an account there was nothing they could do.
holistone said:
I tried taking a LG G3 LS990 with the same MEID/IMEI mismatch to a Sprint repair store. They said they could probably correct the problem IF the phone was on an active Sprint account, without an account there was nothing they could do.
Click to expand...
Click to collapse
Apologies if this is a dumb question, but if you don't have an account with Sprint, why do you want the phone to have the right MEID? Are you selling it perhaps? If you plan on using the phone on Sprint, you could always sign up and then have them send it in? I must be missing something.
AlwaysLucky said:
Apologies if this is a dumb question, but if you don't have an account with Sprint, why do you want the phone to have the right MEID? Are you selling it perhaps? If you plan on using the phone on Sprint, you could always sign up and then have them send it in? I must be missing something.
Click to expand...
Click to collapse
I've tried to activate the phone on RingPlus, a Sprint MVNO that uses the Sprint network. Activation fails and I assume it is due to the mismatch.
fenguepay said:
I bought a used LS990 on Ebay and I rooted it and installed TWRP and later tried activating it but it refused to connect to sprint's network so I did a complete factory reset with the .tot method and that did reset it and get rid of the secure boot errors but it also changed the ESN, MEID, IMEI, and all other identification information. I have tried using CDMA tool, QXDM, and also dial codes to modify those values but whenever I use computer based tools it seems to either not go through or revert immediately. Right now it is showing obviously corrupt data
Phone number: 0000008784
MIN: 000008784
ESN: 808D1BB1
MEID HEX: 35030526000000
IMEI: is correct, I was able to change it to my actual MEID and CDMA tool added a 3 to the end
Brand: Chameleon
My SPC/MSL code is 000000, I guess that's the default one
I'm not sure where to go from here, I have spent about 6 hours total working on this, have factory resetted more times than I can count on both hands and tried everything I could find on various forums
Click to expand...
Click to collapse
Did you ever get this fixed?
I have the same issue.
Ls990 g3 Sprint phone and Sprint sim
Tried to do unroot and flash stock Rom. On reboot i lost data sim and sd issues popping up. Tried to flash the stock tot again and out came up as corrupt or invalid. Don't recall. Plugged into the cdma workshop and out gives all the exact (exact) same info as you posted.
So looking into the build prop it seems to be set GSM prepaid not Sprint spcm postpaid all Sprint apps are missing and the carrier folder no apn settings are set and there's no option to add using the short cut tool i can open add apn but no settings save at all flipping the airplane mode didn't help. The sim locks due to no network....
Same problem on my LG G2. We need to put a BIG FAT warning out that the ToT method will destroy our Sprint LG phone.
DFS Professional can correct IMEI. With CDMA workshop, write all zeroes to ESN using LG method and then you can write MEID. Your phone will still probably need to be programmed properly though. This will help, but maybe not completely http://forum.gsmhosting.com/vbb/f799/qcn-file-thread-1867281/index11.html#post12138691
I had similar happen to a VS985, still not 100% right but it is mostly functional
edit:
i guess i'll add, without cdma workshop, you may be able to get away with downloading proper qcn from link i provided and using DFS Pro to write IMEI, MEID, and ESN to qcn before flashing with qpst. Seemed flakey for me though.

Logic Board Replaced/Problems with SIM Card

Hi everyone, not long ago I posted this thread http://forum.xda-developers.com/galaxy-note-2/help/bootloop-enters-recovery-stock-enters-t3336838 where I had some issues with the EMMC chip. Today I bought a second hand logic board, my note 2 model is GT N7100 International Version, and so is the logic board that I bought, I replaced the logic board and the phone booted, everything is working fine, wifi, camera, sound, etc. The only thing it is not working is the sim card. I tested 3 different sim card carriers, it recognizes 2 of them. But I'm not able to make any phone calls or send SMSs. When I pull down the notification panel it says the name of the carrier on the bottom, with the other carrier it says "Insert SIM Card".
The phone is running jellybean 4.1.2. rooted with stock recovery. No efs backup.
It could be some problem with the logic board replacement? I mean everything is working fine but the sim card.
The previous owners just told me that he had an generic IMEI, and he could make calls without any problem(he was selling the logic board because the screen broke up). Do I need to look for a guide to replace efs folder or something?
thanks to all in advanced!
Generic imei? Sounds like the seller changed the original imei to something that would work with the seller's carrier and not your carrier.
I can think of no valid reason to change a phone's original imei unless the original imei had been blacklisted. You could try restoring the logic board's original imei.
yes, that's the same thing I think of, phone is blacklisted and seller sold it on parts. You can try to change imei to some old phone, that you own.
Try to update to stock kitkat
yaro666 said:
yes, that's the same thing I think of, phone is blacklisted and seller sold it on parts. You can try to change imei to some old phone, that you own.
Try to update to stock kitkat
Click to expand...
Click to collapse
audit13 said:
Generic imei? Sounds like the seller changed the original imei to something that would work with the seller's carrier and not your carrier.
I can think of no valid reason to change a phone's original imei unless the original imei had been blacklisted. You could try restoring the logic board's original imei.
Click to expand...
Click to collapse
Yes, what he is telling me is that he bought the phone in Colombia, so in order to the phone work here in Venezuela he had change the imei for a generic one. That's what he told me. I did not know any of this things until I did a research on Google and I read several methods to solve this problem. But the thing, correct me if I'm wrong, generics imei start with 0049.... And the imei that is on the phone does not Stat with 0049. It shows other number and in the end shows /01, I've never seen that before.
The phone is rooted, I was triying to update it but when I plugged into the computer it is not recognize by it. I use Windows 10, and when I plugged in the phone it sounds both the phone and the computer, but there is no sign of the phone in the computer. I wanted to flash a custom recovery so I can make a backup of the efs folder just in case.
So, I can replace my old imei, (the one that is on the bad logicboard) on this new-second handed logic board?
I think that the original imei won't work here since the phone is from Colombia.
I would like to know if there could be a solution. Because I've done some research on Google, and I've seen soooo many tutorials and every single one is different. And since I don't know exactly what is wrong with the phone I'm afraid to do something wrong and mess up the logicboard.
I think the problem is due to the altered imei. The imei is suppose to match the phone and manufacturer.
Im really sorry for your trouble and you may post on xda for help and assistance but changing IMEI number is illegal and can't be discussed on xda I'm afraid. The fact the seller told you he changed the IMEI number to a generic one sounds like it could have been stolen, if you have the original efs folder you may be able to restore that
Thread Closed

help to update moto z play!!!!

good afternoon friends, I come to you for some doubts that I have about the update of my team .... I have a moto z play with android 6.0.1 I want to update for compatibility issues in applications, but I have activated the good dual sim so I bought it second-hand, can I update directly to 7.1.1? and from there go up to 8 by means of adb sideload? and what is the procedure since I read that you need to omit the lines of the modem and the sfg to not have problems with the imei ..... someone could help me please? and excuse me but occupy the translator to create the theme.
Can we see a screenshot of your Settings>about phone screen please, showing your device and build number? This should help us figure what device you have and what builds to flash.
Provided you flash the correct firmware for your device, your IMEI should be okay.
echo92 said:
Can we see a screenshot of your Settings>about phone screen please, showing your device and build number? This should help us figure what device you have and what builds to flash.
Provided you flash the correct firmware for your device, your IMEI should be okay.
Click to expand...
Click to collapse
It does not allow me to upload links, but I leave the details of my system ....
Android version: 6.0.1
Baseband: M8953_10208.08.04.47R ADDISON_ROWDSDS_CUST
compilation: MPN24.104-44
I downloaded the firmware: XT1635-02_ADDISON_7.1.1_NPNS26.118-22-2-12_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
* I do not know if that serves me, if I can directly flash and if I should omit the lines of the commands Modem and Fsg, to avoid losing the imei .....
CondeLuis said:
It does not allow me to upload links, but I leave the details of my system ....
Android version: 6.0.1
Baseband: M8953_10208.08.04.47R ADDISON_ROWDSDS_CUST
compilation: MPN24.104-44
I downloaded the firmware: XT1635-02_ADDISON_7.1.1_NPNS26.118-22-2-12_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
* I do not know if that serves me, if I can directly flash and if I should omit the lines of the commands Modem and Fsg, to avoid losing the imei .....
Click to expand...
Click to collapse
Thanks, if you're updating, usually it's a good idea to full flash, including modem and fsg. Else you'll have issues with OTA updates.
Normally flashing stock firmware shouldn't cause problems with your IMEI, but without knowing the history of your device, it's difficult to say. If you want to, could you provide your device's get var info?
A) assuming you have ADB and the Motorola drivers set up on your computer, boot your device into the bootloader. Connect your device to your computer via USB.
B) open an ADB terminal and in the terminal type 'fastboot devices' without quotes. Press enter, that should return your device's serial.
C) if you get a response, type 'fastboot getvar all' without quotes in the ADB terminal. Press enter to display a output of your device's parameters.
D) copy paste that output here or upload it somewhere. You may wish to omit your IMEI from the output. That output should tell us if the device was previously unlocked or flashed with a newer firmware.
echo92 said:
Thanks, if you're updating, usually it's a good idea to full flash, including modem and fsg. Else you'll have issues with OTA updates.
Normally flashing stock firmware shouldn't cause problems with your IMEI, but without knowing the history of your device, it's difficult to say. If you want to, could you provide your device's get var info?
Click to expand...
Click to collapse
ok I understand, I explain the equipment I acquired it from use and has a blockage for non-payment in ATTMX that is why they activated the second sim, I do not have backup of the efs and the recovery does not let me, my idea is to go up to 7.1.1 and then go to Oreo by means of adb and already being there to activate the dual sim again and be able to continue using it ... so I ask you if I can skip those commands to avoid taking risks with the imei
CondeLuis said:
ok I understand, I explain the equipment I acquired it from use and has a blockage for non-payment in ATTMX that is why they activated the second sim, I do not have backup of the efs and the recovery does not let me, my idea is to go up to 7.1.1 and then go to Oreo by means of adb and already being there to activate the dual sim again and be able to continue using it ... so I ask you if I can skip those commands to avoid taking risks with the imei
Click to expand...
Click to collapse
Again, if you're updating with the correct firmware and the device had not been flashed with custom ROMs or had downgraded firmware in the past, I do not think you will lose your IMEI. I would recommend you use those commands.
However, if your device was blocked for non payment, are you sure you can even use dual Sims? I'm concerned the previous owner's network provider may have black listed IMEI 1, so even if you update to Oreo, you may only have one active SIM. I'm also hoping that device is from non payment and not stolen...
echo92 said:
Again, if you're updating However, if your device was blocked for non payment, are you sure you can even use dual Sims? I'm concerned the previous owner's network provider may have black listed IMEI 1, so even if you update to Oreo, you may only have one active SIM. I'm also hoping that device is from non payment and not stolen...
Click to expand...
Click to collapse
I suppose they stopped paying, and if right now the dual SIM is activated in the first line which is the original IMEI does not signal, but in the second that is the IMEI 0 if I can use my line but the same way only works for ATTMX, that's why I want to think that updating to 7.1.1 and later to oreo can activate the dual sim back and that it works again like now .....
CondeLuis said:
I suppose they stopped paying, and if right now the dual SIM is activated in the first line which is the original IMEI does not signal, but in the second that is the IMEI 0 if I can use my line but the same way only works for ATTMX, that's why I want to think that updating to 7.1.1 and later to nougat can activate the dual sim back and that it works again like now .....
Click to expand...
Click to collapse
Even if the device says it's dual SIM, the IMEI for one of the SIM slots is likely blocked not by ATTMX but for other providers too (hence the blacklist). I doubt if you update whether you will get dual SIM usage, as your IMEI stays the same usually, so even if you're updated to Oreo, you may still have only one SIM active. The network may just keep rejecting that IMEI number.
I'd honestly think about returning it unless you're happy with just single SIM access.
echo92 said:
Even if the device says it's dual SIM, the IMEI for one of the SIM slots is likely blocked not by ATTMX but for other providers too (hence the blacklist). I doubt if you update whether you will get dual SIM usage, as your IMEI stays the same usually, so even if you're updated to Oreo, you may still have only one SIM active. The network may just keep rejecting that IMEI number.
I'd honestly think about returning it unless you're happy with just single SIM access.
Click to expand...
Click to collapse
does not look, I mean the original equipment is a sim which is blocked for lack of payment, they activated the second sim and obviously that is 0 which if I line with ATTMX and good until now I have no problem it works for me and apart I bought it cheap, the only thing I want is to update to be up to date and so already updated to activate the second sim
CondeLuis said:
does not look, I mean the original equipment is a sim which is blocked for lack of payment, they activated the second sim and obviously that is 0 which if I line with ATTMX and good until now I have no problem it works for me and apart I bought it cheap, the only thing I want is to update to be up to date and so already updated to activate the second sim
Click to expand...
Click to collapse
Yup, so if I've understood you correctly
SIM 1) Blacklisted IMEI due to non-payment by the original owner . Likely will not work even if you update.
SIM 2) I don't think this IMEI 2 gets blacklisted automatically, IMEI 1 is usually the one that is blocked, unless the original owner or ATTMX asked for IMEI 2 to be blocked too.
However, I still think if you update to Oreo, you will not be able to activate the dual SIMs. IMEI 1 will still remain blocked. From what I understand, only the original owner/ATTMX can reverse the block, and as it's due to non-payment, you'd likely have to ask the original owner to clear their debt with ATTMX to clear the block. The block exists on the carrier level, so unless you can change the IMEI (which is something indiscussable on XDA), you are stuck with one SIM, despite having a dual SIM model.
echo92 said:
Yup, so if I've understood you correctly
SIM 1) Blacklisted IMEI due to non-payment by the original owner . Likely will not work even if you update.
SIM 2) I don't think this IMEI 2 gets blacklisted automatically, IMEI 1 is usually the one that is blocked, unless the original owner or ATTMX asked for IMEI 2 to be blocked.
Click to expand...
Click to collapse
if the original IMEI 1 is the one that is blacklisted by the operator, the IMEI 2, which is the one that was activated and is 0, is the one that gives me line, so I wanted to suppose that if I update and when I am in Oreo I could activate it again with the tutorial that goes on the web and thus continue to occupy the IMEI 2 with the line I have ..... now I hope to explain myself .. I doubt very much that the owner pays since we are not in contact.
CondeLuis said:
if the original IMEI 1 is the one that is blacklisted by the operator, the IMEI 2, which is the one that was activated and is 0, is the one that gives me line, so I wanted to suppose that if I update and when I am in Oreo I could activate it again with the tutorial that goes on the web and thus continue to occupy the IMEI 2 with the line I have ..... now I hope to explain myself .. I doubt very much that the owner pays since we are not in contact.
Click to expand...
Click to collapse
So you'd likely have only IMEI 2/SIM 2 active, especially if the original owner has not cleared the balance. I do not know of tutorials that could help you restore IMEI 1 (and they are likely not permitted on XDA). I wish you luck in this endeavour to get your dual SIM device working fully.

Categories

Resources