Hi there!
Recently, there were a plenty of cases with imei changed to zero. In this sub-forum, there were already three cases ([1][2][3]), and in our local ex-USSR community there were a lot more of them. The problem comes up in an absolutely random way. In my case, it started when I tried 'format sd-card' function, built into the MIUI rom. But if you look through, you'll find that other cases have nothing in common. So, the conclusion is that there is a bug in Huawei internal firmware, that leads to nulling the IMEI. Further comes the problem workout:
in our community (4pda.ru) we've found an app (it's attached), that is able to back-up and restore IMEI. we've revealed, that the code for IMEI back-up is
dd if=/dev/block/mmcblk0p5 of=/sdcard/imeibackup/5.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/imeibackup/10.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/imeibackup/11.img
It reads all data from mmcblk0pXX partitions and writes it into XX.img files (images) in the imeibackup folder, stored on the sd-card. The main idea of how to restore our broken IMEI's is:
1. create the backup of IMEI using this app;
2. replace our current IMEI with our actual IMEI in theese *.img files (images);
3. restore IMEI using this app;
The idea is perfect and is easy-to-guess, but non of theese images contain IMEI in raw. Probably, they are crypted, and with no key to encrypt them, we would not be able to replace current IMEI with actual IMEI.
I will be happy to be wrong and if anyone of you could help to find the IMEI string in theese images (all info is in attach).
But there is also another way. Android SDK contains android.telephony.TelephonyManager.getDeviceId() function that returns an IMEI of the current phone. The idea is to find the body of the function (Android OS source is free-to-download, isn't it?) (it might be decrypting those partitions for further IMEI fetching) and using it, understand how to turn our IMEI into factory condition.
There might be a problem if this function only makes a RemoteProcedureCall to the phone firmware and the phone firmware actually decrypts those partitions and fetches an IMEI. In this case, we'll need some reverce-ingeneering: we'll need to write a core module, that will set hooks on the open/read_file/partition functions of our mmcblk0pXX partitions, open the stack, make a backtrace and a dump of the functions that called for them.
actually, my programming skills are too poor both for the first easy way (find the getDeviceId() function body) and surely, for reverce-ingeneering. Thar's why, there is a request for the xda-developers community:
If you are a Java programmer, could you please help us to find the android.telephony.TelephonyManager.getDeviceId() function body? If yes, could you please explain us its algorithm in a common language? We will be glad for any help.
for moderators: yes, i've already read all the cautions about the responsibility of IMEI change (in any purpose), thank you.
Sounds cool. Sadly im not a developer so i can't help. If you get this working, it could save so many devices. Mine lost imei and bricked, but this would have solveed the imei problem. Good luck, hopefully you'll get it working!
Since this require dev attention, maybe u should PM stockwell/dzo/genokolar.. Or just post this in the dev section.. Its great to have one thing less to worry about when flashing phone..
I don't think it would be as easy as just hexediting the IMEI into the relevant location in the image (or at least, I hope it isn't). Remember that the IMEI is used to uniquely identify phones on the cell network so that it can be blocked if the phone is reported as stolen. For this reason it's not supposed to be easy to change, and it's illegal in some places to do it.
I know that this would be intended to be used to restore the IMEI, but it could just as easily be used to change the IMEI for stolen phones.
Forcing the response from the Java call won't do anything - it would only be used to show the number in android, and not by the hardware.
Send your phone back under warranty.
stockwell said:
I don't think it would be as easy as just hexediting the IMEI into the relevant location in the image (or at least, I hope it isn't). Remember that the IMEI is used to uniquely identify phones on the cell network so that it can be blocked if the phone is reported as stolen. For this reason it's not supposed to be easy to change, and it's illegal in some places to do it.
I know that this would be intended to be used to restore the IMEI, but it could just as easily be used to change the IMEI for stolen phones.
Forcing the response from the Java call won't do anything - it would only be used to show the number in android, and not by the hardware.
Send your phone back under warranty.
Click to expand...
Click to collapse
But in my case I want to restore it not change it.. so its my right. And because some may miss use it I will not reveal how.
Sent from my u8800 using xda premium
stockwell said:
Send your phone back under warranty.
Click to expand...
Click to collapse
We do not mind to send the warranty, but it will not take as imei = 0
stockwell said:
Send your phone back under warranty.
Click to expand...
Click to collapse
Of course, it would be the simpliest way to solve the problem, but in any warranty there is a clause that warranty becomes invalid if IMEI has been changed We would not mind the problem and would just send our phones to warranty, but... it has become invalid, so now we need to have our IMEIs restored...
stockwell said:
Forcing the response from the Java call won't do anything
Click to expand...
Click to collapse
You've missunderstood me. The idea is to reveal an IMEI decryption algorythm by looking through the getDeviceId() functions body. I expect to see there something like this (func names are not real):
Code:
function getDeviceId()
{
$imei = fread(0x12345678); //some code to reveal where IMEI is stored
$imei_num = decrypt_sha1($imei, $key_to_decrypt); //some code to reveal the decryption key and method
return $imei_num;
}
Something like this may help us to write some other code to restore our broken IMEIs and warrantys, for example:
Code:
function restoreDeviceId($imei_to_restore)
{
$imei_encrypted = encrypt_sha1($imei_to_restore, $key_to_decrypt); //here we use an encryption key we discovered in prev. step
if(fwrite(0x12345678, $imei_encrypted)) return true; //here we use the mem adress we discovered in prev. step
return false;
}
Of course, I don't expect this to be that easy as in examples above, but I'm ready to digg
PS: i've just sent an email to the Huawei support with problem description. hope, they can help...
Kindly let me know if they reply positive ,need to restore mine too.....
Hello ppl...
I have the same problem, IMEI = 0.
I'm pretty sure that the IMEI was not in any way changed, since I can register on my network.... and supposedely that is not possible with an IMEI nulled.
By the way, I was with CM7 and also formated the SD Card within android system, guessing that could be the reason for that.
Related or not, I started having troubles with non working wifi and SD Card with 2.3 based roms... with original roms or FLB (2.2.2) system works fine.
It would be very helpfull to some of us if one of the Devs could take a look at this problem.
Thank you all!
stockwell, genokolar, dzo...
Can you help us ?!?!?! PLEEEEEAAAASSSSEEEEEEEEEEEEEEE
I miss my 2.3 roms
My X5 also had nulled IMEI.
Also it had WI-FI MAC address changed to new value and SD-card problems (unknown hardware on my PC and recognized as CD-drive).
Service center guy said that it all hardware issues and main-board to be replaced. So it's covered by warranty (despite the fact that I admitted that I had rooted the phone and had installed custom ROM).
Today a was notified that the phone was fixed. I'll get it back tomorrow.
I'm from ex-USSR too (Moscow).
Garry,
If problema was hardware ir wouldnt work also with 2.2.2 roms... And in fact they work perfect.
Problem is 2.3 related... Lwts see when huawei gives official update. They refer the delay is related with... Guess? WIFI!
Sent from my U8800 using XDA App
Does it going on here?
My IMEI = 0, too
In Germany (homenetwork vodafone) I have no problems to login to the network, having phone calls etc.
Now I'm in Sweden and I can't login to any network here. Or, I am logged in not correctly 'cause I see the signal is changing, but I can only do emergency calls. In the status the network provider is unknown.
Today I was in Kopenhagen, Denmark and there I was able to login to TDC A/S and had a phone call - I received SMS...as usual
So what is that? -.-
nrdl said:
Garry,
If problema was hardware ir wouldnt work also with 2.2.2 roms... And in fact they work perfect.
Problem is 2.3 related... Lwts see when huawei gives official update. They refer the delay is related with... Guess? WIFI!
Click to expand...
Click to collapse
Yes stock ROM (2.2) was almost working (some issues with USB access from PC). Custom ROMs (2.3) and most other of Huawei ROMs (2.2) all had broken WIFI and PC USB access. It's not just 2.3 issue it looks for me like different appearances of one bug. I think it happened because of some hardware issue.
Does ToolBox5iromV1.0.4.2.apk work?
ufukyayla said:
Does ToolBox5iromV1.0.4.2.apk work?
Click to expand...
Click to collapse
I've read about it but google translate is giving me a headache.. But i think the Chinese community have tool to backup IMEI n restoring them..
izzoe said:
I've read about it but google translate is giving me a headache.. But i think the Chinese community have tool to backup IMEI n restoring them..
Click to expand...
Click to collapse
The question about this is that you had to have made backup before... wich doesn't happend... most users don't even noticed their IMEI is now 0.
me too,IMEI is 0
So will this problem be a problem without any solution forever???
in theory, if we could edit backup img to our original imei... solution would be simple...
Justa need the help of some devs or programmers to be able to edit that file. ;-)
Sent from my U8800 using XDA App
Related
Hurrah! this has been fixed WOO!.
see here.
well done guys, you have made me a happy g2 owner again!!
Hi Everyone,
i figured we might need to clean up the
http://forum.xda-developers.com/showthread.php?t=805024
conversation.
as i see it, there are 2 issues
1. people receive an unlock code, the phone accepts it but then it cannot find any network
2. people receive an unlock code, have troubles entering the code but eventually get it in ok.
please do not post anything "setting" related - apn's, bands etc as this has been tried and shown not to work (yet)
it might be helpful if people who have issue number 1 could post some answers to some questions.
as i am not at all smart enough to work out what we need to know from these people, id appreciate it if those in the know could pm me what they think could be useful, and ill make a template for people to follow
troubleshooting template
----
----
----
----
Current Theories: (please PM me if i have anything wrong here or if i need to add details.)
-------------
Theory #1
Ghul99: the code is accepted, but the phone is still locked?
http://forum.xda-developers.com/show...&postcount=121
------------
interesting information
this seems to support theory #1
1. i unlocked phone - code entered successfully, and i was no longer prompted to enter an unlock code
2. i perm-rooted my phone - all went to plan
3. i put the vision rom on my phone (http://forum.xda-developers.com/showthread.php?t=834450) loaded ok
4. i put a sim in my phone and now i am prompted for an unlock code.
5. i tried to re-enter my code but it would not accept it (it is the same code from step 1)
Nice idea for taking the initiative to clean up the thread which was getting excessilely long!
I'm hoping we can see some progress in a few days as I'm really missing being able to get any cell reception on a MOBILE PHONE!?
Regards.
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
That's really exciting.
Thanks for bring up the good news!
Sent from my T-Mobile G2 using XDA App
guhl99 said:
I will summerize my knowledge later but one thing upfront.
IntuativNipple posted today in IRC that he found the way to get real S-OFF which would also allow SIM-unlock without code.
So there is hope for a solution, but keep your patience.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Just to help guhl and catch up with some unnecessary posts.
Common solutions like Reboot, different sims to try, Hard reset, flash stock ROM or trigger the unlock window to reenter the code doesn't work
Summary of my knowledge so far
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
Which information could help us:
1. The output of the following AT-Command sequence from successful and unsuccessful unlocks
Code:
ATE1
ATV1
[email protected]?
[email protected]?AA
[email protected]?40
[email protected]?80
I will try to write a HowTo later for Windows.
For linux see the following posting from the old thread (http://forum.xda-developers.com/showpost.php?p=8750299&postcount=121)
2. The next thing that would help is a logcat from the first unlock process itself.
Howto:
Start the first logcat using the USB-cable and adb before you boot the phone with the foreign SIM.
Code:
adb logcat -b radio > lc_unlock.txt
leave the logcat running and complete the unlock procedure till the phone reboots (the logcat will end automatically)
As soon as the first logcat exits start a new one using:
Code:
adb logcat -b radio > lc_after_unlock.txt
leave it running for 1 minute and then stop it using <Ctrl>-C
3. The next thing that really would help is that you do not post anything in this thread (use the old one instead) that has to do with:
- the APN
- trying another SIM (you would be very lucky if you had one that fits the arbitrary SIMlock)
- reboot, factory reset, use a stock or non stock firmware
- use the hw/sw-keyboard, wait for the right outside temperature or other esoteric procedures
Finally I would like to ask moodecow to edit his original posting and incorporate or link everything that he finds important or helpful in his posting so that it will stay an top.
That is some very exciting news, thank you for the update!
One quick question, when we achieve radio-s off it esssentially would mean everyone could unlock their phones for free?
Thanks.
Sent from my T-Mobile G2 using XDA App
I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.
ms93 said:
I have 2 ideas, which can help:
1. For people before unlock - maybe performing S-off before unlock will help.\
2. For people after unlock: in bootloader there is "SIMLOCK" option. When you open it, it shows file not found etc. As I think, it can be used to simlock phone for operator, whose numbers are in some file. There is my solution - find what that files are in phone's source code or by any other method, then put them in right place, enter numbers of operator you want to use, open that "SIMLOCK" and lock phone to your network. I don't know if it will work, but it makes some sense.
Click to expand...
Click to collapse
Your first idea sounds reasonable and I would support it.
Your second idea is something that is worked on, but you do not only need the correct file (which is actually called DMCID.dat) but there also has to be some "magic number" (like on a gold card) on the micro-sd card.
an important piece of info to carryover from other thread:
1- No APNs are listed
2- if you try to define one, it doesnt save
No APNs being listed is related to the rom more or less, not the issue we're having.
APN is software issue, correct me if I'm wrong so either way it shouldn't pose as an issue to us.
im saying its a symptom that seems to go along with the problem in the title of this thread, so, worth noting.
ie: i think everyone who has the post-unlock no-connection problem, cannot save APNs. all others can.
if you are a counterexample please say so. that would help.
guhl99 said:
For case 1 which was the original problem my theory is the following.
Cause:
Because of problems with the write procedure to the emmc memory the MCCMCN to which the phone is locked did not get cleared but set to an arbitrary value in my case "C3AB".
The CID value is still the same as it used to be (and also in case of a successful unlock would stay the same) which is "T-MOB010". The CID is a 8 character string and the case where all characters are the same (i.e. "11111111") is called Super-CID.
It is of no relevance if you use or used the hardware or software keys, T-Mobile or third party sources. The only reason where it would be your fault is if you pulled the battery!
The unlock-code that we possess (regardless if official or from a different source) is not valid to unlock the phone from this value "C3AB". If one tries again (directly with the modem, using my modified libril.so or a different ROM) the lock counter will increase.
Potential ways to repair this state:
1. Give it back to T-Mobile if you can In my opinion this is a clear warranty case
2. Find someone who has the MegaSIM and the HTC-diag software.
This will definitely work but it is going to be hard to find someone because the SIM is rare and very new.
3. Wait until (or help achieving) the so called "real S-OFF" state of the phone (when also the radio has security disabled) is reached.
When this is achieved one can disable the SIM-lock without any code.
There are still some very good developers after this goal even if for different reasons.
.
Click to expand...
Click to collapse
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect
kabir_del said:
i have got HTC MEGA SIM and Almost all DIAG files but
T-mobile G2 case =After putting unlock code NO NETWORK cant be solved because when we give s58 clear command it shows SIMLOCK CORRUPTED
i can post the detailed info and pictures if you want it would be a pleasure if could help in any kind of DEVELOPMENT
BTW
if we don t put code in the same version,same country,purchased in the same lot of handsets and use MEGASIM directly without touching anything than it works perfect
Click to expand...
Click to collapse
Posting any further details and/or pictures would be much appreciated!
So if megasim has failed due to corruption I think that the only way to solve our issue is to write directly to emmc partition holding locking information. And I don't now how easy and plausible this is...
I think if we get S-Off for Radio, we'll be able to write to that partition. I hope
andrewklau said:
I think if we get S-Off for Radio, we'll be able to write to that partition. I hope
Click to expand...
Click to collapse
I am a little bit worried about writing this information directly because the partition will be encrypted.
And also copying the complete partition from a working phone or one that is still unlocked will not be an option because the IMEI will also be there and we would not want to overwrite that.
So my hopes are more that there is some kind of a restore procedure from a secure area (I know that Nokia phones can do this, but HTC ?) or that we can lock the phone again with the SIMLOCK option in hboot.
Sent from my T-Mobile G2 using XDA App
well I guess time will tell, does tmobile or htc do replacements (or has anyone tried) for phones no longer on a contract or that are now unlocked?
Sent from my T-Mobile G2 using XDA App
andrewklau said:
Posting any further details and/or pictures would be much appreciated!
Click to expand...
Click to collapse
here we go Pictures first Video coming soon
First Red colour is the error we get on when we try the command
1=clear s58 data
2ND IMAGE is the one when we press the DEVICE INFO
today is sunday not much time will upload the full clear video tommorow and still i have not tried to the all options of the diag maybe it can repair it but sure i will do some more things tomm.
88
I have tried to use my HTC vision G2 as I unlocked it but after that I am unable use as I am unable to find anything which would be hlpful for me as I have the first case problem. I just want to know that would it help me that if someone would flash my HTC Vision G2. I just want to know about that as now I am in Pakistan
Sent from my T-Mobile G2 using XDA App
Does anyone backup the IME on Nexus4 not, how to do his guidance?
Dont think its necessary. From what i have read, only samsung phones have efs partition vulnerable.
boyboyxmen said:
Does anyone backup the IME on Nexus4 not, how to do his guidance?
Click to expand...
Click to collapse
No need in case of Nexus 4. For more details, refer
http://www.xda-developers.com/android/guide-to-imei-numbers-and-preserving-them-on-android/
Are you curious about what IMEI stands for? Do you want to learn how to interpret the parts of IMEI numbers to learn more about a device? XDA Senior Member xsenman has written a guide to IMEI numbers that aims to explain all this, along with details on how to preserve them on your phone during ROM flashes.
IMEI stands for “International Mobile Equipment Identity,” and is a 15 digit number that uniquely identifies each mobile phone. Because they are unique, they can be used to track a stolen phone, or block carrier access to any device. It is illegal to change it in most regions, so preserving your IMEI number is extremely important.
While the area that the IMEI number is stored on is protected on most phones, many Samsung devices have it saved on the EFS partition, which is easily accessible with a rooted phone. That’s why there are chances that while flashing a ROM to your device, you might end up messing up the EFS partition and thus losing your IMEI number.
For more information on IMEI numbers, a complete description of what their digits stand for, and details on how to preserve them on your phone, head over to the forum thread. The thread also links to validators for checking if an IMEI number is valid or blacklisted, and a couple of other useful threads that guide you with fixes to EFS-related problems that can effect your IMEI number.
hi I was trying to unlock my g900w8 galaxy s5, I guess I ended up erasing my efs.
I ended up with imei=unknown, the baseband and everything else reads correct. but I keep getting the 'mobile network not available' or the "not registered to network" error'
and no my imei is not blacklisted I just need to get it back on my phone.
I did make a back up of the nv with nv writer and a back up of qcn with qpst. but I did not make a copy of my efs folder.
my problem is I cannot restore my nv nor can I restore my qcn. its getting blocked from some kind of permission. for example when I try to restore in nv writer I get these errors:
Writing NV-items from a file:
Unsuccessfully written NV-items:
00001 (0x0001) - Read only item
00002 (0x0002) - Read only item
00003 (0x0003) - Read only item
00550 (0x0226) - Access denied
00855 (0x0357) - SPC (6 digits) is required
01943 (0x0797) - Read only item
05597 (0x15DD) - Read only item
05598 (0x15DE) - Read only item
10155 (0x27AB) - Access denied
Done.
and similar issues with qcn back up.
is this because of the s5 firmware?
how do I force a successful write?
or if possible how can I extract my efs info from my two back ups?
when I open the qcn file as an archive with 7.zip I do see several folders like EFS_Backup, NV_Items, NV_NUMBERED_ITEMS, Provisioning_Item_Files. but I don't know what to do with them or how to convert them into something I can put back in my phone.
thanks any help would be appreciated.
We're sorry to hear that your phone got messed up. Just goes to show that the very first thing anyone ought to be doing is making backups just in case you need them. That should be common sense but we're all guilty of taking risks sometimes.
However, we can tell that you didn't do much of a search or read more than about two posts in the forum before posting. If you had you would have found countless posts asking this question and the inevitable response i.e. discussing how to change /repair /modify, etc IMEI numbers is not permitted on this forum. It's too easy to abuse or facilitate the trade in stolen phones.
And no, I doubt that the staff will make an exception just for you. You'll have to rely upon Google or possibly your carrier will replace your phone under warranty regardless of cause. Often if you don't volunteer information, they don't really look too closely at why a phone fails. Samsung will have no problem ultimately repairing the original phone when it goes their refurbishment process.
.
fffft said:
We're sorry to hear that your phone got messed up. Just goes to show that the very first thing anyone ought to be doing is making backups just in case you need them. That should be common sense but we're all guilty of taking risks sometimes.
However, we can tell that you didn't do much of a search or read more than about two posts in the forum before posting. If you had you would have found countless posts asking this question and the inevitable response i.e. discussing how to change /repair /modify, etc IMEI numbers is not permitted on this forum. It's too easy to abuse or facilitate the trade in stolen phones.
And no, I doubt that the staff will make an exception just for you. You'll have to rely upon Google or possibly your carrier will replace your phone under warranty regardless of cause. Often if you don't volunteer information, they don't really look too closely at why a phone fails. Samsung will have no problem ultimately repairing the original phone when it goes their refurbishment process.
.
Click to expand...
Click to collapse
thank you for you reply, I have searched, I've searched all over the net even, I do know that talking about changing the imei is not permitted on this forum but in my searches I have come upon many threads regarding imei problems and recovery, coming from this board as well. I have tried many different things and programs, wiped my phone a few times reinstalling the firmware, rooting, unrooting etc. but I still do not have a solution to my problems
I am not trying to change my imei, I lost it while trying to unlock my phone. I am just trying to recover my imei through my back ups or any means to get my phone back up and running.... even if it was just help to get my back ups to actually back up to my phone I would be really greatfull because at the moment it is just a really expensive paperweight.
thank you.
sakohunter said:
I am not trying to change my imei
Click to expand...
Click to collapse
You are trying to change your IMEI. From it's current value to the original one. And posting how to change an IMEI can be expected to be abused by thieves and the like. You can't say, I know the rules say don't explain how to pick locks. but it's okay because i will only use it to get into my own house. Umm, no. Once posted, miscreants will have access to the information as well. No doubt the reason why XDA staff don't allow the type of discussion you want to engage in.
Since you know that this isn't permitted you should have simply dropped it rather than try to justify an exception. If you felt strongly about the subject you could try to persuade staff to change the rules, rather than skirt them. The latter suggests that you are ignoring them mostly because it would be an expedient way to fix your phone.
.
ok, im not here to argue with you, I was only seeking help and being honest about it.
I could have left imei out of my whole post and just asked for help in restoring my nv and qcn backups.
or rather why my phone is not writing the backups. which is my whole intention.
ive seen many posts regarding them nv, efs and qcn but you seem to be fixated on the term imei so lets just let the post die or have it closed.
I understand what you are saying in regards to imei but that is just a part of nv efs and qcn backups. it is a risk that everyone takes when modding or customizing their phones, so backing them up and restoring as needed is always recommended.
If you have a backup of your EFS, simply restore it. That is straightforward, easily done and not controversial.
I thought you said you hadn't made a backup which is unfortunate. And I do have sympathy for the situation. But as you just said that is an expected risk of modding our phones. Having a broken phone isn't cause to ignore a set of rules that say this topic is forbidden due to abuse.
.
Hey mate,
I had almost the same problem. After a few days i finally got my phone working by doing what is in this post:
http://forum.xda-developers.com/showpost.php?p=55953093&postcount=29
Good luck and let me know if you need any help or if what i did isn't clear and i can give you some proper instructions. Make sure you backup everything before you do this just in case something even worse happens.
Mod Edit
Changing imei is illegal.
No such discussions are allowed on XDA.
Thread closed
malybru
Forum Moderator
This guide is for those who have lost their IMEI, have corrupted EFS, or erased EFS partition. So, follow these under your own risk, it may or may not work, and if something happens or doesn't happen, then i am not to blame. So, once again i will not take credit for bricked phones or something along those lines, however i will take full credit if this works for you. I will also provide assistance to those who could not restore their EFS following this guide.
Before proceeding with this guide, backup what you have left. Use twrp to backup and in case something goes wrong and your problem escalates, you can restore using twrp backup.
Restore EFS
Change IMEI Number
Restore EFS
Do this if and only if you believe your EFS is corrupted, or you somehow erased it. If you are not sure about it, then simply follow the next guide to change you IMEI number. In most cases people loose their IMEI only and not the whole partition. Again, it may or may not work, so do this on your risk, and i am not to blame if anything bad happens, but if you do succeed, then don't forget to give me credit.
Note:
If your EFS is erased or corrupted, your IMEI and Baseband will be shown as unknown. In this case recover the EFS following this post, and then change the IMEI following the next post. If your IMEI is shown as 0, then you EFS is safe and most probably your IMEI is gone. In that case, no need to recover EFS, only change the IMEI number following my next post.
In TWRP, backup of kate wont show on kenzo and the backup up kenzo wont show on kate. In case no backup is shown even if you are using the right device, then try the dump flashing method or try changing the TWRP recovery.
Flashing this will only restore your EFS partition, but the IMEI will still be gone, so you will have to follow the next guide to change your IMEI.
Even after flashing a new EFS, you Mac and BT address will not recovery. The android system will assign a software generated address to both devices. Dont worry cause even without the EFS partition there will be a Mac and BT address assigned to your device and both the things will work normally.
If your Baseband is still unknown, even after flashing a new EFS, then try flashing latest radio file. It can be found in any firmware update package, either the official or the one from the strix.
1. Download the required files from the link given below.
EFS Backup[Kenzo] - Contact me if someone has backup of this.
EFS Backup[Kate] - Contact me if someone has backup of this.
2. Extract the Dump Backup files and flash them using the following commands.
Code:
fastboot flash modemst1 modemst1
fastboot flash modemst2 modemst2
3. Now reboot and voila you have you a new EFS partition at your disposal.
Change IMEI Number
Requirements:
Root
USB Debugging is turn on
Windows Driver Signature is turned off
ADB and Fastboot Binary Files
Latest MiFlash Installed for the latest drivers
1. Connect your device to pc and open the adb folder. Then open a command promt window.
Code:
>> [B]Shift + Right Click[/B] anywhere in the adb folder
>> Click on [B]Open Command Window Here[/B]
2. Type the following command to enable Diagnostics mode. Allow debugging if asked.
Code:
adb shell
su
setprop sys.usb.config diag,adb
4. Download the IMEI Changer from the link given below.
IMEI Changer [Credit: Archeolot]
5. Now, open the imei changer, and enter imei number in both the fields. And click on start. After a moment it will show as passed. If it fails make sure that you have followed the points i stated.
Note: Make sure that the driver in driver management under ports is listed as "Qualcom HS-USB Android DIAG 901D" and not as "Marshall London HS-USB Android DIAG 901D". If it is listed in any other name, then go to driver management and update driver. Select browse driver, then let me pick driver from a list. Then select "Qualcom HS-USB Android DIAG 901D" and then finish.
WOW.. Thanks mate..
It's gonna very Helpful for me & other ppl.. ??
Sent from my Redmi Note 3 using Tapatalk
didn't work..
showing error as no diag even after typing those commands
kindly help me
nuk.nama said:
showing error as no diag even after typing those commands
kindly help me
Click to expand...
Click to collapse
At what part, the imei change or flashing.
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Broski32 said:
The simplest, and the fastest guide to restoring EFS and IMEI! I haven't backed up my EFS and this revived my phone! Much apprecieated!
Click to expand...
Click to collapse
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
archit.bajpai.ab said:
Glad i could help mate. Can you confirm your mac address and bluetooth address, whether it is same or changed.
Click to expand...
Click to collapse
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Broski32 said:
Can't confirm. My EFS partition was so corrupted from trying other tutorials to restore my IMEI that I didn't even bother backing it up because I thought that it could have been changed already (tried writing to NVRAM with QPST). Since I don't have my original mac and bluetooth addresses written down anywhere (I haven't written them down myself and I don't think they are to be found anywhere on the box or on the phone) I think the only way to check it would be to compare my current addresses on the phone to the addresses contained in your EFS backup. Can you extract them so I can check if they match or not?
Click to expand...
Click to collapse
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
So, using this way, one can change the IMEI no. also?
mGforCe said:
So, using this way, one can change the IMEI no. also?
Click to expand...
Click to collapse
Yes, just use the imei changer in the rar file to change your imei. But make sure to backup or atleast note down your imei before doing so.
archit.bajpai.ab said:
The mac address and bluetooth address in the efs are my own. I only changed the imei so that no one else can copy it, i didnt know anyway to change mac address. Besides the mac address doesnt matter that much, and i dont think that we will ever be on the same wifi network.
If you dont know then i can explain, that the mac address is required to maintain switches and broadcast in the router, so it technically does not matter.
You can change it later with some apps or use it like that if you wish, if i find any way to restore you mac i will post it too. In the mean time just post a snapshot of wifi mac and bluetooth address so that i can compare them with my own.
Click to expand...
Click to collapse
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Broski32 said:
Current addresses on my phone:
MAC - 00:0a:f5:a9:XX:XX
Bluetooth - 7C:7F:F0:82:XX:XX
Left out some numbers just in case they are mine. For the purpose of checking that will still be enough
Click to expand...
Click to collapse
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
archit.bajpai.ab said:
Yup, they are not mine. Mine start with 64:cc and so on for both mac and bluetooth. They may be software generated or may be your own, technically i am not sure.
Edit: did you use imei changer to change imei no. Or are you using the default values. If you are using the default values, pls post them too. If you change them, then give your review, ie was it hard or easy, did you encointer any problem, stuff like that.
Click to expand...
Click to collapse
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Broski32 said:
After flashing your EFS backup both IMEI values were set to "0". On the default values I don't think the phone would be able to register on any network with the sim inside, but I haven't tried that. Then I flashed my IMEI with the app you provided in the .rar. Set my IMEI same for both slots because I've got only one written down on the box so I think it is set how it should be out of the box. After that I've rebooted to EDL and flashed global developer rom. And it's all working, I'm able to make calls from both sim slots, however didn't try having 2 sims inside.
All in all the process is very easy, definitely the easiest out there. I haven't encountered any problems, however I think others may have a problem with drivers to get "Qualcom HS-USB Android DIAG 901D" working. Mine was working already because I tried this tutorial before. Thank you for this guide, and providing your backup
Click to expand...
Click to collapse
Enjoy your revived phone buddy.
Thanks buddy!!!!! you saved my phone
pandyajoe said:
Thanks buddy!!!!! you saved my phone
Click to expand...
Click to collapse
It do what i can do buddy...
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
chr0m said:
Guys. I messed up my phone by restoring a nandroid backup from a different one.
I was able to restore my IMEI using some qualcomm tools. My problem now is that fingerprint scanner won't work on any rom, even official.
Any idea what else I have messed Up? I don't think restoring this efs will fix my fingerprint scanner. Is fingerprint scanner info in a different partition?
Click to expand...
Click to collapse
Have you checked with miui7 stock rom. As far as i know there are three sensor modules for fingerprint, on of them is goodfix which is currently not supported by many roms. If your is goodfix then it will not be supported too. You can flash miui rom to check whether the fingerprint works or not...
If it doesnot work, then try to resotre your nandroid backup agaian. This tym simply untick efs.
I have recently bought an Essential Phone from ebay with broken radios. No imei, no wifi... After troubleshooting, I found out that the QCN file was completely wiped. I have the original imei written on the phone and paper but need the copy of QCN to restore it. Could somebody please help ?
guggaburggi said:
I have recently bought an Essential Phone from ebay with broken radios. No imei, no wifi... After troubleshooting, I found out that the QCN file was completely wiped. I have the original imei written on the phone and paper but need the copy of QCN to restore it. Could somebody please help ?
Click to expand...
Click to collapse
give me imei and ill hex edit mine and sent it to u
Tech_Savvy said:
give me imei and ill hex edit mine and sent it to u
Click to expand...
Click to collapse
It's not safe to share imeis. Could you just edit yours with dummy imei and pass me the file? I can hex edit my original imei into it myself.
guggaburggi said:
It's not safe to share imeis. Could you just edit yours with dummy imei and pass me the file? I can hex edit my original imei into it myself.
Click to expand...
Click to collapse
So u don't trust a guy with 655 thankx.... willing to offer his qnc backup?? What would I do with ur IMEI besides convert it to hex and make it easier for you..that way I know you actually have a legit IMEI and not just a stolen one
Tech_Savvy said:
give me imei and ill hex edit mine and sent it to u
Click to expand...
Click to collapse
Tech_Savvy said:
So u don't trust a guy with 655 thankx.... willing to offer his qnc backup?? What would I do with ur IMEI besides convert it to hex and make it easier for you..that way I know you actually have a legit IMEI and not just a stolen one
Click to expand...
Click to collapse
You are right. Actually, I dont have much to lose anyways as the phone is becoming replacement parts if I can't repair it. I will sent the imei via pm. Also, not sure if qcn restore if even enough, there is a chance of broken efs as well.
guggaburggi said:
You are right. Actually, I dont have much to lose anyways as the phone is becoming replacement parts if I can't repair it. I will sent the imei via pm. Also, not sure if qcn restore if even enough, there is a chance of broken efs as well.
Click to expand...
Click to collapse
Qnc fixes efs....if it doesn't you could send me your nvrf partition,I could inject your IMEI into the one I pulled from mind and send you the fixed one...
Hi
Hello everyone I am so sad. Because A few days ago I noticed that the baseband was unknown. IMEI 1 and 2 unknown and Android ID Null from my Asus rog phone 2 Zs660kl version I001DC Global version and I cannot do anything because there is no any Qcn file for this phone , I am unable to do anything in my own, I do not live in United states, I cannot send it to repair, it would cost me the tax again, like 147 dollars again that I paid for the customs. Please if anyone has a good hearth to back up the Asus rog phone 2 file from the same version with the qpst toll... I would really appreciate. I need it , I tried to find the IMEI with Hxd editor and there is not any 1111 to find the error so I am unable to to that. There is no any Qcn file. I need a Qcn file from the same phone with a phone that has the baseband and the rest fine".
I need to have the Qcn file from this same phone I have issues with the baseband IMEI unknown and Android id Null, by doing this you can help through diag mode you just follow this just download Adb minimal, open it and and write Adb devices, then Adb shell then Su and finally setprop sys.usb.config rndis,diag,Adb enter and in device manager you will see in ports, Qualcomm devices which you can continue doing the next step which is installing latest drivers from Qualcomm on this video you can follow the steps After installing the latest qualcomm driver, the qpst tool will recognize your phone because it is now on diag mode since you did the previous step, by checking this video you can back up the Qcn file which is what many people need and there is no other way to solve the issue only with a phone which is in perfect condition as yours
how to use the qpst tool to backup the Qcn file , First diag mode with the commands I gave you second is installing the latest qualcomm drivers then backup and restore Qcn , and then you will have it done,
download the qpst tool and the Qualcomm drivers and it is an example of my problem with the baseband, you can guide with the one video and the third , the one video do not use the commands given by the YouTuber, because that do not works, use the commands I gave you , that works for our phones, and then the third video is explaining how to backup the Qcn file which contains the data? I was unable to edit myself the Qcn data from my damaged phone cause the IMEI is not there, there is no any 11111 number to replace it for my own IMEI, sadly,... Just need the Qcn from a good phone, please!!l
If anybody is still offering to do this and can help me... My phone is hard bricked and I can't do anything... I feel I can fix it with a QCN... Anyone want to help?