Database Users

[HELP] Insert SIM card to access network services

Hey guys,
I'll put it as simple as I can :
-no SIM service whatsoever. Happened a few hours after i flashed Androidmeda ROM. no clue if thats the reason
I tried:
- restart
- wiping all caches and data
- factory reset ( 3 different ways )
- flashed 3 other ROM's
- recovered a very old nandroid backup i found
- drained the battery, recharged fully
- left battery out for a few hours
- slapped it around (gently)
Im drained out of ideas. Any clues? anyone?
Thanks in advance

Sim card in slot .
Check you have the correct network settings .
Check IMEI is the original one .
Wrong IMEI restore your backed up EFS folder .
jje

hey. u were right about the IMEI. It says unknown/unavailable on all IMEI, IMEI SV, WiFi MAC, Bluetooth addr. and baseband.
Just one Q.
what is and EFS folder and what if i did not back it up?

JJEgan said:
Sim card in slot .
Check you have the correct network settings .
Check IMEI is the original one .
Wrong IMEI restore your backed up EFS folder .
jje
Click to expand...
Click to collapse
How can I back it up?

bahkata said:
hey. u were right about the IMEI. It says unknown/unavailable on all IMEI, IMEI SV, WiFi MAC, Bluetooth addr. and baseband.
Just one Q.
what is and EFS folder and what if i did not back it up?
is rule one backup efs folder so you can restore your IMEI ..
The /efs folder​The /efs folder is a folder in your phone that contains information specific to YOUR phone, for example your IMEI number, product number, Wireless MAC addresses, and much more. There have been reports of people messing up their /efs folder when unlocking their phone or flashing new ROMs, here is an example from the Nexus S development forum (jump to page 111 to see everyone start to panic):
http://forum.xda-developers.com/show....php?t=1034130
Therefore, it is important to make a backup! Instead of just regurgitating guides on the forums already, here is a link to a very good one by Rawat:
http://forum.xda-developers.com/show....php?t=1068193 (Rawat)
The easiest way of doing it is by using terminal emulator rather then ADB (unless you have ADB all up and running and are confident with it)
You need to search the other multitude of IMEI posts see if you can find a fix .
If not its a service centre repair if you have proof of ownership and no custom rom and no root and custom rom counter set to zero .
jje
Click to expand...
Click to collapse

Imei nulled [problem workout]

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

Backup the IME on Nexus4

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.

[Q] Where to get a new SM-N9005 mother- / logic- / main board?

After spending days and nights with a fried EFS (IMEI null / null), which in no way can be restored - no receipt, no box, no more sticker under battery. I've read a lot of people got their motherboards replaced by service centers.
Where can I get these?
Service center is a no-go in my case, they said they can't help.
Edit: "GH82-07651A" is the official product number for one of the N9005 board types, maybe this one is for the 16GB version tho not sure

Soo Star said:
After spending days and nights with a fried EFS (IMEI null / null), which in no way can be restored - no receipt, no box, no more sticker under battery. I've read a lot of people got their motherboards replaced by service centers.
I take it as a new motherboard means you get a new IMEI?
If so, where can I get these?
Service center is a no-go in my case, they said they can't help.
EDIT: Okay.. searching for its spare part number is easier.. the thing is called "GH82-07651A"
EDIT2: GH82-07651A is the 16GB model I think
Click to expand...
Click to collapse
Yeah a new motherboard will contain a new IMEI. - How did you fry your EFS? - you know it can actually be saved with some ADB trickery (quite a few have done so)

radicalisto said:
Yeah a new motherboard will contain a new IMEI. - How did you fry your EFS? - you know it can actually be saved with some ADB trickery (quite a few have done so)
Click to expand...
Click to collapse
I've been trying day and night to restore it by flashing hundreds of stock roms - of no avail.
Well the IMEI most likely got formatted away by odin by the previous seller - though if I could restore it I could file a proper lawsuit against the vendor, cause it's obviously stolen (no sticker etc).
Which "ADB trickery" method did you refer to? Cause every method I've found so far requires the IMEI to be reentered from a sticker / receipt or whatever

Soo Star said:
I've been trying day and night to restore it by flashing hundreds of stock roms - of no avail.
Well the IMEI most likely got formatted away by odin by the previous seller - though if I could restore it I could file a proper lawsuit against the vendor, cause it's obviously stolen (no sticker etc).
Which "ADB trickery" method did you refer to? Cause every method I've found so far requires the IMEI to be reentered from a sticker / receipt or whatever
Click to expand...
Click to collapse
Ahh, I (assumed) thought you had the original IMEI somewhere, in regards to the ADB I mentioned, there is a thread by Marek on how to restore IMEI and Serial number - The EFS partition btw doesn't actually ever vanish. The Note 3 has the ability to rebuild the EFS by itself using the correct scripts and commands. So all hope isn't lost tbh :good:
EDIT: Have you tried the Fire script?
---------- Post added at 12:31 PM ---------- Previous post was at 12:28 PM ----------
As if by magic here is the link

radicalisto said:
Ahh, I (assumed) thought you had the original IMEI somewhere, in regards to the ADB I mentioned, there is a thread by Marek on how to restore IMEI and Serial number - The EFS partition btw doesn't actually ever vanish. The Note 3 has the ability to rebuild the EFS by itself using the correct scripts and commands. So all hope isn't lost tbh :good:
EDIT: Have you tried the Fire script?
---------- Post added at 12:31 PM ---------- Previous post was at 12:28 PM ----------
As if by magic here is the link
Click to expand...
Click to collapse
Actually I've given it another shot with the EFS Pro tool & Qualcomm NV Tools though somehow I can't get the QC tools to connect properly causing the tool to crash... I'd say it's because there is no IMEI (or null/null, where it should be), if I knew better.
fire's script didn't restore the missing IMEI ever tho ..guess I'm really fubar'd
EDIT:
radicalisto said:
The EFS partition btw doesn't actually ever vanish.
Click to expand...
Click to collapse
apparently partition is just perfectly fine up to the contents of the /efs/imei (nv files missing). I've seen things like people recreating the imei from their meid?
But whenever I read oft it, it proven not to work in the later posts of the threads lol -_- (why I tried QC again)
EDIT 2: "I'd say it's because there is no IMEI (or null/null, where it should be), if I knew better."
It might have something to do with EFS Professional switching the USB settings from "MTP + ADB" to "DIAG + Modem + ADB" when starting up NV Tools. (Since I get "Mobile Network not available" after dialing *#7284#) ..it's probably connected to the "Baseband unknown" thing.. idk

Google SuperIMEI, I think it's your only hope here.

The first
Efs partition not contain imei number on qualcomm device!
It is stored on mmcblk0p 12 and mmcblk0p 13 if you try use the script from the beginning of my threat if it not work... Just find someone with proper box to repair it.

mirek190 said:
The first
Efs partition not contain imei number on qualcomm device!
It is stored on mmcblk0p 12 and mmcblk0p 13 if you try use the script from the beginning of my threat if it not work... Just find someone with proper box to repair it.
Click to expand...
Click to collapse
Still can't post in your thread lol
I did run through the process as described in Soft bricked [ SOLVED ] again. With the sole difference that I had to use a different CWM (6.0.4.7) from
[RECOVERY]CWM Based Recovery 6.0.4.7 for N900 N9005 N900T N900S because it wouldn't work with "n9005-cwm-recovery-6.0.4.4(1025)" - I've read it's a KK bootloader issue.
So I ran all the 23
Code:
dd if=/external_sd/mmcblk0xxx of=/dev/block/mmcblk0xxx
as
Code:
dd if=/storage/extSdCard/mmcblk0xxx of=/dev/block/mmcblk0xxx
and can't start the phone anymore at all. It bootloops right after the "Samsung GALAXY Note 3 SM-N9005" write. (doesn't go to the pulsating logo).
I doubt it's cause the CWM I've used has another mount point for the ext SD ;;
Sure an octopus or something might help, but it will be hard to find someone in Switzerland lol.
EDIT: After that, I'm flashing the latest stock KK it boots again, but the IMEI remains null/null, as well as Baseband unknown

From my post just push mmcblk0p11 but you need root and adb on PC and busy box on android.

ㅠㅡㅠ
mirek190 said:
From my post just push mmcblk0p11 but you need root and adb on PC and busy box on android.
Click to expand...
Click to collapse
Kay, on a clean stock ROM I put;
- CWM with recovery su,
- SuperSU-v1.99r3 app
- booted and put busybox
- set super su to perm root / default access [ grant ]
Then I adb to the device and found it suddenly refusing root access.
So I upped to file to sd card, use terminal emu and dd mmcblk0p11...
that's right so far?
rebooted and still
View attachment 2785241

Help, QCN file needed

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?