Related
Guys,
I just updated with the CM10 nightly and I am getting a prompt on bootup that my IMEI is not valid. The IMEI is not blank, and isnt something like 0123456789. Is this a big issue? My calling and texting are working fine, as is my mobile data.
Thanks
The same happens to me. I did an efs backup with root manager but is there any risk? Could someone explain please?
I backed up with cwm before loading cm10 0823. And did an imei restore from Nitrality and it says successful. However I still get an invalid imei on bootup
Sent from my GT-I9000 using xda premium
Updated to cm10 0824. Same issue. Should I do a full cwm restore?
Sent from my GT-I9000 using xda premium
Hey guys common issue if you want it back follow my guide http://forum.xda-developers.com/showthread.php?t=1845104 you might want to titanium backup your apps first then backup your sd
Sent from my GT-I9000 using xda premium
Restored cwm backup from before the issue started. No long have invalid imei. Update to latest cm 10 and invalid imei prompt on startup. However the imei screen under About has an imei number in it still.
Sent from my GT-I9000 using xda premium
Correct imei though as in the same as the one under the battery?
Sent from my GT-I9000 using xda premium
Nope. Its a different one.
Sent from my GT-I9000 using xda premium
webchaos said:
Nope. Its a different one.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
OK so its invalid try the link I previously posted if it works or not get back to me
Sent from my GT-I9000 using xda premium
After going back to stock GB, darky resurrection ROM, cm9 and finally cm10. IMEI is back and looking OK. Thanks.
Sent from my GT-I9000 using xda premium
That's good
Sent from my GT-I9000 using xda premium
Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium
webchaos said:
Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Well, in my case, my father's phone lost all efs backups, and nv_data.bin is corrupted (regenerated new one with default generic IMEI).
So, there is nothing to restore from. Reflashing to stock 2.3.6 JW5 firmware didn't help. So you think that I will have to reflash to 2.2.1? How so? I don't understand how older firmware may help restoring correct IMEI...and I don't own JTAG, z3w or SPT boxes...
And for morrons - no, there is no .nv_data.bin, no nv_data.bin.bak, or similiar...only new nv_data.bin(md5) with default, generic IMEI.
Is there any way to restore it? if somebody start to complain that I am thief, I can prove by photos of original phone box, and buying papers I have (my father gave them to me for this purpose).
And no, I don't have to steal anything, I own SGS3, SGS2, SGS, SGT10.1....so stealing another SGS is not an option for me
I just want to restore that phone to it's stock state (and then reflash again with CM10).
Anyone?
Virnik0 said:
I just want to restore that phone to it's stock state (and then reflash again with CM10). Anyone?
Click to expand...
Click to collapse
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details
xsenman said:
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details
Click to expand...
Click to collapse
Why are you so confident, that JVU will regenerate /efs?
as said before, my father was so genius, that he has wiped /efs partition out. I have restored some data, but without proper IMEI, so now I have generic one. I still do have old JVU package somewhere on my NAS, but I do not understand, how old firmware may help, because I am without any /efs backup anywhere... is that firmware customized so it checks and regenerates /efs if its damaged? If so, why is this feature missing from latest full JW5 firmare? Please understand that I know what I am doing, but right now, I have empty hands...without JTAG, z3w or similiar low-level gadget, it is really hard to restore proper /efs on my own...
But thank you for links, I will take a look on them...
More Clues On Fixing IMEI Issue (solved for me)
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert
robertrath said:
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert
Click to expand...
Click to collapse
Exactly that. Same goes with going from Gingerbread to Jelly Bean.
That critical intermediate rom... Is CM9
In other words, to safely preserve your IMEI,
Froyo/GB ---> CM9 ----> CM10/10.1/JB
Sent from my GT-P7510 using Tapatalk HD
I need some help flashing a modem onto my I896. I'm currently running the Helly Bean version of CM10 with the devilkernel. I boot into recovery mode and install the .zip file from SD card but afterwards I get no data signal/connection whatsoever. Am I doing something wrong? I'm trying one of the modems found here:
http://forum.xda-developers.com/showthread.php?t=1703597
Check if your imei starts with 004...if it is, the imei is broked and you need to restore it. I think some people in cm10 threads said to copy paste your backed up efs folder. A solution that MIGHT work for you is to flash to a stock ROM, but like I said, it might not work since all captivates are built differently. I can confirm that it works for me though. Build# 1101
Sent from my Nexus 7 using xda app-developers app
panda_mode said:
Check if your imei starts with 004...if it is, the imei is broked and you need to restore it. I think some people in cm10 threads said to copy paste your backed up efs folder. A solution that MIGHT work for you is to flash to a stock ROM, but like I said, it might not work since all captivates are built differently. I can confirm that it works for me though. Build# 1101
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My IMEI number is good, doesn't start with 004. Maybe I'll try flashing a different rom.
Perhaps try a modem from the development sticky?
Sent from a jelly bean
Hi Experts,
My device is GT-P1000. I was able to flash the nightly built from cyanogenmod site. I flashed cm-10.1-20130609-NIGHTLY-p1.zip. By the way, I came from AOKP ICS rom.
All is working well for me for the basic tasks that I've tested except that it can't detect our mobile networks here in Singapore which is pretty much a deal breaker. Wifi, bluetooth, etc. are okay. You can see in my attachment that it can't find any GSM network even if I search manually. Is this rom not compatible to Singapore local telcos? Did I miss anything? May be you experts got some ideas.
I have searched the android development forum for CM10.1 Nightly but can't find any relevant solution. Hence, I try my luck here if any of you guys experienced the same issue and was able to solve it.
Thanks in advance.
/f
What is your IMEI showing? If not 35xxxxx, say unknown, or 0049xxx then it won't work. Unknown is due to broken modem.bin. Wrong IMEI is due to corrupted EFS. Either restore from backup found in your sdcard or restock then reflash.
Sent from my GT-N7100 using xda app-developers app
unknown IMEI
priyana said:
What is your IMEI showing? If not 35xxxxx, say unknown, or 0049xxx then it won't work. Unknown is due to broken modem.bin. Wrong IMEI is due to corrupted EFS. Either restore from backup found in your sdcard or restock then reflash.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Hi Priyana,
Thanks for your reply. You're correct. I checked the IMEI and it's unknown(shown in attached image).
Correct me if I'm wrong, I need to restore to my backup AOKP ICS rom and then flash this CM10.1 rom again?
Or I need to flash a stock Gingerbread rom then flash CM10.1 rom again?
Thanks in advance,
/f
hi
the best way
flash cm9.1 befor flash cm10.1
work gsm
Unknown is due to broken modem. Just to to development subforum, there is a sticky thread for modem.
Get the JPZ modem, but don't flash it.
Unzip it, just copy the modem.bin to replace the one in /radio/ of your device.
Use root explorer or similar. Reboot and check baseband again. If IMEI still unknown, better restock.
Sent from my GT-N7100 using xda app-developers app
jalil123 said:
hi
the best way
flash cm9.1 befor flash cm10.1
work gsm
Click to expand...
Click to collapse
Hi Jalil,
I tried what you advised but still no luck. The IMEI is still unknown. I even restore my AOKP rom but still the same issue is happening. Thanks though.
I downloaded a stock firmware (gingerbread) and planning to flash it if priyana's advice doesn't work.
I will try priyana's suggestion first before I flash a stock firmware.
Hi Priyana,
I saw the thread that you replied in back in 2012 Oct. Will try your advice. Thanks.
/f
have you also check if you have a backup folder in your sdcard or external sdcard
that has efs folder in it.
Pick the oldest one which is more likely to be the good copy.
Copy the content to replace the one in /efs
Also make sure that you show hidden files in the file explorer, or you will miss important files from that efs back up folder.
Verstuurd van mijn GT-P1000 met Tapatalk
Fixed. Million THANKS guys!
Hi Priyana, KasSGT and Jalil,
I was able to fix my device. I did flash a stock rom, root it, and then flash the CM10.1 rom. I now backed up the /radio directory just to be sure.
Thanks for all your advice.
/f
Well after i stupidly got my phone soft bricked, I downloaded and flashed stock 4.3 rom correct to my region. Everyhting worrked fine after that i was able to call and send messages etc. But today i tryed to root the phone, With multiple ways actually, CF-root, thru CWM. but there was some problems, Bit off topic but after i flashed the CF-root i was rooted, But SuperSU asked me to update binary and after that i wasnt rooted anymore :/
and the problem thru CWM that it didnt root at all, Dont know what the problem was...
*knox warranty gone, didnt even know about such a thing before i searched abit...*
Well anyway now i flashed stock rom again, The same that i flashed earlier and now my phone is buggin with the sim card, It will detect it but its not detecting the network or twhatever it it, So its only allowing Emergency calls...
i have tryed pulling the sim out of the phone etc but hasnt worked
I was wondering it it can be phones fault, For the trys of rooting etc.. Or can it just be the sim cards or the providers error?
Did you check your IMEI? 000 or 04x or something weird?
Sent from my C6506 using xda app-developers app
IMEI is bunch of numbers, 3562970500.... I can post the full number code if needed and it isnt something personal or something
You have correct modem and APN settings ???
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
You have correct modem and APN settings ???
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
Well, I tryed to read all of those, And what i got from them is that flashing stock ROM should work, if not then flashing MODEM could work,
In the other hand, if the /efs is corrupted or something, Then if i dont have backup im ****ed
Is there anything i could do other than sending it into repair?
Pandastyl said:
Well, I tryed to read all of those, And what i got from them is that flashing stock ROM should work, if not then flashing MODEM could work,
In the other hand, if the /efs is corrupted or something, Then if i dont have backup im ****ed
Is there anything i could do other than sending it into repair?
Click to expand...
Click to collapse
Edit:
I looked my IMEI from *#06# on dialer, it looked alright but at the end theres " / 01", Should that be there?
The /01 is a check digit.... That should be there. ... Cant share from my Wikipedia app but.... Search for IMEI there, it'll describe it in detail...
Sent from my GT-I9505 using xda app-developers app
alesa1988 said:
The /01 is a check digit.... That should be there. ... Cant share from my Wikipedia app but.... Search for IMEI there, it'll describe it in detail...
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ok thanks.
Well i checked my IMEI behiind the battery, Its the same that is in the *#06#,
And the IMEI Shows on the setting/about device/status, I can see IMEI and IMEI SV, But stuff like IP address, Network are Unkown and Service state is Out of service. Im bit confused what the problem here is
I would try your SIM card on another phone just to make sure, you can usually get a duplicate for free or cheap if thats the issue.
If the SIM card issue is working fine, get hold of the PARAM and WIPE images for your model and run them through Odin, then flash a recent firmware.
At least that is what I would try, but I'm not sure if knox bootloader is going to make it easy for you or not.
Maybe someone else knows more?
Good luck!!!
Sent from my GT-I9505 using xda app-developers app
alesa1988 said:
I would try your SIM card on another phone just to make sure, you can usually get a duplicate for free or cheap if thats the issue.
If the SIM card issue is working fine, get hold of the PARAM and WIPE images for your model and run them through Odin, then flash a recent firmware.
At least that is what I would try, but I'm not sure if knox bootloader is going to make it easy for you or not.
Maybe someone else knows more?
Good luck!!!
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
The sim card cannot be dublicate, As when i bought the phone, Around 4-5 months ago, The normal sim card got changed to the micro-sim that fits into s3.
Im not totally sure what u mean with the "get PARAM and wipe images", and i have flashed the stock rom couple of times, Heck i even ran the Kies FW recovery thingy that does the same thing.. and yea, That ****ing Knox...
WIPE and PARAM are images similar to the firmware ones you used to flash your phone. Except that what they do is completely wipe and re-partition (Think of it like formatting your PC before you install Windows) and then configure the device for the first time. This way we can make sure that it isn't an issue with the way that the firmware was installed (issues can arise if you flash too many times or different roms / versions of android are installed without wiping in between) I don't own an S III so unfortunately I can't help you finding them, though I'm sure someone else will be able to link you to them...
Sent from my GT-I9505 using xda app-developers app
alesa1988 said:
WIPE and PARAM are images similar to the firmware ones you used to flash your phone. Except that what they do is completely wipe and re-partition (Think of it like formatting your PC before you install Windows) and then configure the device for the first time. This way we can make sure that it isn't an issue with the way that the firmware was installed (issues can arise if you flash too many times or different roms / versions of android are installed without wiping in between) I don't own an S III so unfortunately I can't help you finding them, though I'm sure someone else will be able to link you to them...
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick replys.
SO installing stock rom thru odin, OR Kies both can fail? if i understood correctly.
Does the region matter on those?
You are most welcome I hope I've been of some help. And yes, there is always a possibility of something going wrong if you do not wipe first (Not so much if you're upgrading from the same rom and android version eg: TouchWiz stock 4.2 to 4.2 , but yes if for example 4.2 to 4.3 or from stock to custom, or vice versa etc..)
As for region, if the model is the same there really shouldnt be an issue, at most you'll have a wrong CSC which would involve having to configure APN settings manually.... But to get that far first we'd need the phone to register on the network.... Which yours isn't doing at the moment... I do not think this is the problem.
Sent from my GT-I9505 using xda app-developers app
alesa1988 said:
You are most welcome I hope I've been of some help. And yes, there is always a possibility of something going wrong if you do not wipe first (Not so much if you're upgrading from the same rom and android version eg: TouchWiz stock 4.2 to 4.2 , but yes if for example 4.2 to 4.3 or from stock to custom, or vice versa etc..)
As for region, if the model is the same there really shouldnt be an issue, at most you'll have a wrong CSC which would involve having to configure APN settings manually.... But to get that far first we'd need the phone to register on the network.... Which yours isn't doing at the moment... I do not think this is the problem.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
So, If id now do full wipe/factory reset, And then flash the stock rom again, Whould it be possible to get the settings back, Or are they now kinda saved thgere?
I think its worth a try..
A wipe will clear all settings, but if you use the right region most will be configured automatically for you (I'm assuming you're refering to the APNs)
Sent from my GT-I9505 using xda app-developers app
alesa1988 said:
I think its worth a try..
A wipe will clear all settings, but if you use the right region most will be configured automatically for you (I'm assuming you're refering to the APNs)
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Did not help, Im at the same point as before, And it should be the right region as Kies also detects the same region code.
Well, Yea, akward....
I dont know if this did it or was it just the derpyness of me trying something. But what ever
http://forum.xda-developers.com/showthread.php?t=1946915
I flashed this param.bin, But It did nothing, as i guessed tbh.
Then i went to the access points, And then i realised the network operators. I had to register into network there
Yea, Well it is fixed now,
Fix: The problem was probably it just removed me fromt he networks when i tryed to root. And then iu need to register into network again.
Thanks for alesa1988 for quick awnsers
You're welcome, I'm glad it is now resolved
Sent from my GT-I9505 using xda app-developers app
I recently purchased a Samsung Note 4 (SM N910T) for from a guy on craigslist after saving up money to buy it, but it keeps turning off out of no where . the phone was having problems before I rooted it, after I rooted it, and after I odin'd the earliest version of kit kat of the phone.. The turning off occurs at any time, during boot, during flashing TWRP, during normal usage of phone, anytime. I recently purchased a brand new OEM Samsung Note 4 Battery and but still has problems. I'm currently on stock DOK2 and still having trouble. Does anybody know what I can do to fix this? I can't contact the original seller anymore
Is it rebooting on its own or shutting off completely?
Sent from my SM-N910T using Tapatalk
Starts rebooting on its own
qbanlinxx said:
Is it rebooting on its own or shutting off completely?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Reboots on its own
You have messed with kernel now flash stock kk and keep trouble away from you
junejo46726 said:
You have messed with kernel now flash stock kk and keep trouble away from you
Click to expand...
Click to collapse
If he's on dok2, likely stuck there and cannot go back to kk. For the op, I think you found why they were selling it..... I would recommend somewhere like swappa.Com over Craigslist.
Sent from my SM-N910T using XDA Free mobile app
Go into TWRP and wipe everything including internal sd. Then boot into download mode and flash the DOK2 firmware in ODIN. it could be the software related. If that doesn't fix it, then it might be hardware. You may have to take the phone apart and see if it's got a lose wire or a fried MB. Water damage can also cause this behavior.
So I have kept my device stock except for SuperSU and Busybox, no kernel flash, or rom flash yet, my question is, has Samsung fixed the issue with deleting NV data when flashing between roms? What I want to do, is flash TWRP and backup my current setup, then I want to unroot it, and back it up so that I can switch back and forth between rooted and stock, because I found out that screen mirroring breaks sometimes when you run the stock rom rooted and I want to know before hand if I need to backup my NV data with QPST before flashing back and forth between these two modes. I know I can do it in the terminal, but i've seen issues on my SGS3 with this being restored in a ROM that was not the one you backed up from, I.e. it seemed almost like the backup in the terminal assigned a unique identifier to the backup so when you flashed a ROM and needed to restore it would say the backup was corrupted, of course while I don't see any reason why the NV data would get destroyed during the process of what I'm trying to do, I just want to be fully prepared, because I'm pretty sure the .QCN generator I have for the SGS3 isn't going to write a new .QCN (NV data file) that is going to work on the note 4 seeing as how there were two or three updates to the .QCN version number for the SGS3.
Sent from my SM-N910T using XDA Free mobile app