Database Info

IMEI=0 - how to enter working IMEI?

Hi everyone & thanks for reading this!
I bought 2 new, unused Nexus 5 as presents for my sisters for Christmas (not via playstore, but via a reseller. Still: new, sealed, unused.)
I unlocked, installed a custom recovery, rooted both devices without problems, then set up one in a smartphone-newbie-friendly way, which took quite some time. Then, to save me some time, I fear I made quite a big mistake: I made a nandroid-backup of the newly-setup device and restored/installed it on the second nexus (so I wouldn't have to change all the settings again, install apps, etc).
Unfortunately, this seems to have erased the IMEI on the second device (it shows as IMEI=0), so I can't connect to any cell service. Some googling leads me to believe that this might be due to a corrupt/missing EFS-folder, which, second mistake, I did NOT make a backup of beforehand. I know, it's my own fault - my thinking was: why backup, there's nothing backupworthy on the device *yet*.
FML. :crying:
I am not sure if the phone is still in warranty (and even if it was - I guess I voided that by unlocking/rooting?!). I want to re-iterate that I own both devices LEGALLY, I have the bill, I have the original sticker with the original IMEI - I just need a way to re-enter it. Any dialer-code for that? Any modify-able EFS-backups? Any other way?
Thanks in advance!
PS: tried so far & found useless: other simcard (not working) & simcard in other phone (working), so it's a device-issue; factory-reset;

Try fastboot flashing the cache.img from the factory image.

jd1639 said:
Try fastboot flashing the cache.img from the factory image.
Click to expand...
Click to collapse
thanks for the super-quick reply jd1639!
to make sure I understand you correctly:
I can use the factory image from
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
(nexus 5, android 4.4.2), extract the cache.img from there & flash that via fastboot? (or would it have to be a factory image of this very device - which I do not have, unfortunately)
and, just for my understanding: how does that restore the imei? I mean, the factory image itself (or it's cache) can't really contain MY imei. does this just delete the invalid imei & force the phone to get it's original imei from some other, not yet overwritten source? e.g. hardware?

Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk

Thank you for clarifying, rootSU - that gives me hope.
I will try tomorrow & hopefully report success

Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).

RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...

RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato

charesa39 said:
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
Click to expand...
Click to collapse
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).

CellPhish said:
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
Click to expand...
Click to collapse
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!

RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
If all fails you can try to contact LG service and tell them your situation. Though its not good to lie, just tell them you got the IMEI=0 problem, they'll say its a hardware problem and will replace the motherboard(if your device is on warranty)
Sent from a potato

You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.

rootSU said:
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The IMEI is stored in the EFS partition, not the cache partition.
RogerG said:
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
Click to expand...
Click to collapse
Sounds like you turned the phone into a $400 paperweight. TWRP backs up and restores the EFS partition by default, and each device has a unique EFS partition, which contains the IMEI among other things. I don't know of a way of manually restoring the EFS data. This is unfortunately a $400 lesson for people who tinker without first doing their homework.

Hey guy. Let's not be so judgemental. There's always a risk of the imei being corrupted when you flash a ROM. As a matter of fact just before I even unlocked my nexus the imei got corrupted and I had to factory flash my phone to save it. Its scary but op, if you manage to get your phone working again make a backup and store it on your PC and or email yourself the backup.

BirchBarlow said:
The IMEI is stored in the EFS partition, not the cache partition.
Click to expand...
Click to collapse
Ha ha thanks! Can't believe you think I don't know that :/
Actually the "EFS partition" is 2 partitions..
/dev/block/platform/msm_sdcc.1/by-name/modemst1
And...
/dev/block/platform/msm_sdcc.1/by-name/modemst2
That doesn't change the fact that reflashing the cache.img is a known fix for missing IMEI. Corrupt cache can make the imei appear as 0 even when the EFS imei is in tact so reflashing the cache.img can resolve this.
Unfortunately though, I didn't read the OP fully. I just elaborated on an earlier response for the OP
jd1639 said:
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
Click to expand...
Click to collapse
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk

rootSU said:
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes but all talks about how to change it in any way are not allowed here. Legally the only people that are allowed to do so is the OEM. You can look at international news reports of cellular dealers that are doing so are being closed down and arrested.
That is why it is well know to back up the efs before you do anything.
Bat cave One

My newly bought Nexus 5 shows IMEI 0 also
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
i just update my newly bought nexus 5 from initial 4.4.2 to 4.4.4 which is appear at update section but then my IMEI appear =0 .. dont understand what to do..
if your problem solved, pls tell me the detail procedure to recover my IMEI no.

RogerG, did you ever get this working? I'm on 6.0 and having the same problem, flashing cache.img also does nothing.
Thanks.

[Q] Up to date stock OPO software?

Hi,
can anyone enlighten me as to what is the most up to date software.
Is it the "fix" software distributed by Oneplus
https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
Or s it the Cyanogenmod Factory fastboot images here
https://cyngn.com/products/oneplusone/
I have examined the contents and much of the content seems to be the same (img files have same name and size) but there are exceptions such as boot.img
What is the most up to date boot .img to use?
Any ideas?
I dont have any of the problems listed and my OPO is spot on, but I still want to know what the most up to date "stock" software is.
I have asked the same question to oneplus but have not yet received a response.

would like to know as well.

jeffrey1027 said:
would like to know as well.
Click to expand...
Click to collapse
Hopefully, if there is anything new in the OPlus fix it will be released as a new image by Cyanogenmod soon. That way we have a decent reference point.

They are essentially the same, the "Fix" has the ColorOS partitions included (Persist.img & Reserve4.img) which alleviates some problems which some has experienced. But the software is the exact same version. I can tell you that the "Fix" version is a VERY easy way of updating your phone, as its a series of only 3 files you have to run compared to quite a number of fastboot commands for the Cyan Factory images version. In the end though both are 38R.

S M G said:
They are essentially the same, the "Fix" has the ColorOS partitions included (Persist.img & Reserve4.img) which alleviates some problems which some has experienced. But the software is the exact same version. I can tell you that the "Fix" version is a VERY easy way of updating your phone, as its a series of only 3 files you have to run compared to quite a number of fastboot commands for the Cyan Factory images version. In the end though both are 38R.
Click to expand...
Click to collapse
Will the the 'fixes' remove unlock and root?

JeffDC said:
Will the the 'fixes' remove unlock and root?
Click to expand...
Click to collapse
YES, it will wipe your device entirely leading to loss of root and it re-locks your bootloader. If you are already on 38R i don't see any advantages for you to flash this "FIX"

Thanks for the info. Appreciated. Any more detail on what the reserve4 and persist IMG do, can they be flashed on top of an existing install (38r factory).

What is the supported boot.IMG?

JeffDC said:
Will the the 'fixes' remove unlock and root?
Click to expand...
Click to collapse
zaphodbeeb said:
Thanks for the info. Appreciated. Any more detail on what the reserve4 and persist IMG do, can they be flashed on top of an existing install (38r factory).
Click to expand...
Click to collapse
YES, they can be flashed on top of a currently installed 38R without any data lost etc. AFAIK both persist and reserve4 are ColorOS specific partitions which somehow become corrupted during CyanogenMod software updates. This leads to all kinds of issues e,g, Lost IMEI,Boot Loops,CM Lockscreen FC etc. Any by simply erasing them and re-flashing them fixes many of the above if not all.

Tested the new "fix"
Does not fix my wif issue where it turns orange after idling.

[Q] Other firmware on the same model

Can i flash other firmware of s4 on my phone (shv-e300s). For example, i want to flash shv-e330s lollipop or indian's lollipop firmware for my shv-e300s. Will it work? Does my network/signal will be removed or still stays? Thanks for answer.

MarcJustCons said:
Can i flash other firmware of s4 on my phone (shv-e300s). For example, i want to flash shv-e330s lollipop or indian's lollipop firmware for my shv-e300s. Will it work? Does my network/signal will be removed or still stays? Thanks for answer.
Click to expand...
Click to collapse
It may work but there is no guarantee at all. Another region's firmware will include another modem version (May affect your signal / reception) and in some cases the partition table is different from the one your phone actually use, which means you can get trouble if you want to flash your region's firmware later. In any case make a backup of the phone's "EFS" partition to be sure your IMEI will not get lost and the phone become unusable.

LS.xD said:
It may work but there is no guarantee at all. Another region's firmware will include another modem version (May affect your signal / reception) and in some cases the partition table is different from the one your phone actually use, which means you can get trouble if you want to flash your region's firmware later. In any case make a backup of the phone's "EFS" partition to be sure your IMEI will not get lost and the phone become unusable.
Click to expand...
Click to collapse
I actually lost my IMEI before and lost my signal. Then i went to repair shop for a fix. They fixed the signal, but they haven't restored my original IMEI. it still shows fifteen 0(zeros)/01. how can i reshow it?

MarcJustCons said:
I actually lost my IMEI before and lost my signal. Then i went to repair shop for a fix. They fixed the signal, but they haven't restored my original IMEI. it still shows fifteen 0(zeros)/01. how can i reshow it?
Click to expand...
Click to collapse
You can't. For that you create a EFS backup BEFORE youn start modding your phone...

LS.xD said:
You can't. For that you create a EFS backup BEFORE youn start modding your phone...
Click to expand...
Click to collapse
but i can still backup my efs/IMEI even if it shows 000000000000000/01 ?

MarcJustCons said:
but i can still backup my efs/IMEI even if it shows 000000000000000/01 ?
Click to expand...
Click to collapse
"EFS" is one of the phones partitions storing somje data. You still can backup it, but thats not very usefull as the partition already got screwed up. With IMEI 0 you should not get any carrier signal // reception.

LS.xD said:
"EFS" is one of the phones partitions storing somje data. You still can backup it, but thats not very usefull as the partition already got screwed up. With IMEI 0 you should not get any carrier signal // reception.
Click to expand...
Click to collapse
so it means, backing up my efs doesn't do anything if ever i flash a different firmware and screwed up for restoring?

MarcJustCons said:
so it means, backing up my efs doesn't do anything if ever i flash a different firmware and screwed up for restoring?
Click to expand...
Click to collapse
As long your phone is not usable for getting signal or accepting your simcard you will gain absolutely nothing my performing a EFS backup as there seems notghing on it that can be saved.

LS.xD said:
As long your phone is not usable for getting signal or accepting your simcard you will gain absolutely nothing my performing a EFS backup as there seems notghing on it that can be saved.
Click to expand...
Click to collapse
My phone is still usable and has signal. It means backing up still makes sense?

MarcJustCons said:
My phone is still usable and has signal. It means backing up still makes sense?
Click to expand...
Click to collapse
I'm really curious about it as your carrier will normally refuse establishing connections to simcard in a device with invalid IMEI but in that case backup your EFS.

LS.xD said:
I'm really curious about it as your carrier will normally refuse establishing connections to simcard in a device with invalid IMEI but in that case backup your EFS.
Click to expand...
Click to collapse
Me too. i think they changed my IMEI. i saw them holding another phone and checking the imei at the back of the phone while repairing my phone. Anyways, i will try backing up my efs. Thankyou so much! ^^

MarcJustCons said:
Me too. i think they changed my IMEI. i saw them holding another phone and checking the imei at the back of the phone while repairing my phone. Anyways, i will try backing up my efs. Thankyou so much! ^^
Click to expand...
Click to collapse
Please press the "thanks" button at the bottom of my posts if I helped you

LS.xD said:
Please press the "thanks" button at the bottom of my posts if I helped you
Click to expand...
Click to collapse
i will, for giving me a lot of informations and help.

Question Rog phone 5 fingerprint error when I covert version CN -> WW

1.I have a rog phone 5 covert to tecentgame. When I move to version WW but then there is a fingerprint error (losing the system fingerprint authentication). Who can help me?
2.There is an opinion that restoring the system partition can fix the above situation, do not know if it is true or false?can anyone guide me on how to do the above?

RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com

It's a known issue. As of yet, it appears this is a drawback to the conversion.

I'm currently working on a solution to get fingerprint working after a conversion. I've located the error and a Magisk module should be able to fix it. I can't make any promises until that theory is fully tested, though.
Of course my Magisk install is broken and won't install from storage...

I need the system/vendor/etc/vendor_(something)_styles.xml
Started a thread for it, since those with a working reader are unlikely to be looking through this thread.

losing fingerprint sensor happend always or its random issue?

yaser86100 said:
losing fingerprint sensor happend always or its random issue?
Click to expand...
Click to collapse
It's basically part of the conversion until that is perfected.

twistedumbrella said:
It's basically part of the conversion until that is perfected.
Click to expand...
Click to collapse
maybe one day thats be perfect ?

yaser86100 said:
maybe one day thats be perfect ?
Click to expand...
Click to collapse
Probably. They got there on the 3, from what I've seen.

..................

twistedumbrella said:
It's basically part of the conversion until that is perfected.
Click to expand...
Click to collapse
Unlocking BL and converting WW, there is a chance of losing your fingerprints, but back up the persist partition before conversion, you don’t have to worry about losing your fingerprints. Once you lose your fingerprints, you only need to restore the persist partition and your fingerprints will be normal. But it can only correspond to this phone, and restore on other phones is not possible.

yaser86100 said:
losing fingerprint sensor happend always or its random issue?
Click to expand...
Click to collapse
The quote below was meant for you. No idea why I was tagged instead.
johnny886 said:
Unlocking BL and converting WW, there is a chance of losing your fingerprints, but back up the persist partition before conversion, you don’t have to worry about losing your fingerprints. Once you lose your fingerprints, you only need to restore the persist partition and your fingerprints will be normal. But it can only correspond to this phone, and restore on other phones is not possible.
Click to expand...
Click to collapse

twistedumbrella said:
I need the system/vendor/etc/vendor_(something)_styles.xml
Started a thread for it, since those with a working reader are unlikely to be looking through this thread.
Click to expand...
Click to collapse
what shoul i change?
i rooted my rog phone 5
i dont know what to do to being back my fingerprint
i havent backuped

shayantt98 said:
what shoul i change?
i rooted my rog phone 5
i dont know what to do to being back my fingerprint
i havent backuped
Click to expand...
Click to collapse
Follow one of the newer threads. The info here is extremely outdated.

Question Persist partition needed for OnePlus 9 T-Mobile

I was trying to unlock the sim-lock on my OnePlus 9 T-Mobile and somewhere read that it can be done by deleting modemst1, modemst2, and persist partitions. So, I deleted them, but it didn't work. Instead, the WI-FI also stopped working.
After trying different MSM Download Tools for weeks, somehow modemst1 and modemst2 partitions were restored, but still cannot restore the persist partition. Without persist partition sensors are not working. For example, it does not auto-rotate, brightness auto-adjustment does not work, etc.
Can anyone help me with this?
Thank you!

c0d3f0rc37 said:
I was trying to unlock the sim-lock on my OnePlus 9 T-Mobile and somewhere read that it can be done by deleting memst1, memst2, and persist partitions. So, I deleted them, but it didn't work. Instead, the WI-FI also stopped working.
After trying different MSM Download Tools for weeks, somehow memst1 and memst2 partitions were restored, but still cannot restore the persist partition. Without persist partition sensors are not working. For example, it does not auto-rotate, brightness auto-adjustment does not work, etc.
Can anyone help me with this?
Thank you!
Click to expand...
Click to collapse
So in essence you broke your device. You probably have lost fp scanner,wifi,nfc,rotation. I really don't know what to tell you other than msm your device back to stock. And you didn't back up persist . This partition is device specific. If you do get it fixed properly I'd leave it the hell alone.

You can't just delete critical partitions

So, there's no way to fix this? I can assume that the phone is wasted?

c0d3f0rc37 said:
So, there's no way to fix this? I can assume that the phone is wasted?
Click to expand...
Click to collapse
Try and contact OnePlus and get a remote session. One of their techs will get you on correct MSM and get phone fixed.

c0d3f0rc37 said:
So, there's no way to fix this? I can assume that the phone is wasted?
Click to expand...
Click to collapse
The persist partiton can only be fix by oneplus in factory or spending money for someone that has the hardware required to fix it.