Related
Long story short, my imei is not the current one under the battery and i want to get it back. Before i thought my phone wasnt unlocked and that was the problem but its not. The phone is unlocked and i even have the codes, i just want to use my own IMEI. I currently can not connect to any networks with the captivate.
So far i have tried using the .bak file in /efs with no success (different imei).
I have tried several posts on xda but all seem to unlock and not give you your proper imei back.
Any advice or information would be greatly appreciated.
Buuummmppp
b0uncyfr0 said:
Long story short, my imei is not the current one under the battery and i want to get it back. Before i thought my phone wasnt unlocked and that was the problem but its not. The phone is unlocked and i even have the codes, i just want to use my own IMEI. I currently can not connect to any networks with the captivate.
So far i have tried using the .bak file in /efs with no success (different imei).
I have tried several posts on xda but all seem to unlock and not give you your proper imei back.
Any advice or information would be greatly appreciated.
Click to expand...
Click to collapse
How did u manage to mess it up, may I ask. This way atleast u could warn the rest of the community not to mess ours up.
Its quite simple really, dont back up your /efs folder and keep messing around with roms.
I don't think anyone has solved this. Everything around the nv_data.bin file relates to unlocking and it says you must have a good IMEI number to start with. There was some 3rd party software that can fix IMEI numbers - but it required a separate breakout box. I forget the name, but many downloaded the software only to discover they needed to buy the box to get it to work.
One of mine managed to wind up with the generic imei but I have yet to see any ill effects from it.
I am sorry to hear about this, and even sorrier to have to say this, but xda does not allow posting of instruction on how one can change the imei.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok if we cant talk about this thats fine. Right now i cant connect to any networks. If someone would be willing to upload their /efs for me so i can try it out. Would that work?
Im in Australia so anything apart from that should work right??
did you ever got to restore your original imei?
Check here for a how to restore your IMEI.
So, I have an XT1053 that I unlocked and got to 4.4.4 using the T Mobile stock ROM.
Everything was fine, I rooted it, it went all fine.
Then I installed the XPosed framework, got me some modules, and it was fine.
Then I got the Gravity Box to tweak my stuff.
Rebooted to activate it, and it was all fine and dandy until I changed setting that required a further reboot, like "show network activity indicators on WiFi/signal bars" and the navbar customizer.
I was hoping to come back and do some sweet customizations but instead, at reboot, my phone wouldnt get service, even though the SIM is detected, I have an IMEI and my SIMs phone number shows up on the About phone > status screen.
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Downloaded both the AT&T and Verizons 4.4.4 versions, but I cant flash them using RDS lite, apparently the preflash verification fails, it mentions the gpt. I guess I need to flash the TMobile 4.4.4, but there is no such file at sbf developers, only 4.4.3, Will flashing this brick my phone?
This guy https://forums.motorola.com/posts/41d92959b1 has the same symptoms as me, but as you all can see, no follow up.
Any idea what can I do to fix this?
I totally place blame on the gravitybox network activity indicators settings, but who knows.
Added screenshots, edited out some stuff.
Thanks in advance, Ive spent most of my morning trying to figure this out.
No one?
:c
no_un_bot said:
So, I have an XT1053
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Click to expand...
Click to collapse
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.
dtg7 said:
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.
Click to expand...
Click to collapse
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.
no_un_bot said:
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.
Click to expand...
Click to collapse
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.
dtg7 said:
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.
Click to expand...
Click to collapse
Boy oh boy was I wrong.
I fixed it, going to post what I did.
Turns out the /persist folder was not empty, root explorer showed everything was ok. he I thought, "Hey, XPosed + GravityBox caused (afaik) this mess, maybe it will get me out of it too. Maybe, as pointed out, xosed touched some partitions not normally accessible, lets see if they can do it again". So I installed those apps again, did the very same I did las time, and then uninstalled using the Xposed disabler .zip. Didnt work.
It was time to try and flash another stock ROM.
As Ive said before, I originally got into 4.4.4 with TMobiles ROM (my keyboard tilde key is broken, so bear with me), and attempting to flash AT&T/Verizon/BR Retail etc 4.4.4 stock ROMs would fail because of a security downgrade as far as gpt.bin goes.
I "fixed" this taking the gpt.bin file out of TMobiles OTA zip (the one that upgrades 4.4.3 to 4.4.4) and replacing the one on the ROM I was trying to flash with this. Meaning, I flashed the BR Retail 4.4.4 having replace gpt.bin with TMobiles OTA one.
Everything flashed ok, and, at the very last step, instead of using the command
Code:
fastboot oem config carrier vzw
like every guide out there says, I went for
Code:
fastboot oem config carrier ghost_retail
as per this page: https://github.com/CyanogenMod/android_device_motorola_ghost .
Phone rebooted with his Brazilian version and lo and behold, it was NOT working. Same symptoms.
I dug deeper, and the I remembered how someone with the same issues on another phone model fixed it by swapping his SIM for a friends, then using his again. I had already tried this, I even bough a SIM (because no one close to me uses a nano SIM) and it hadnt worked, but it did gave me some insight, maybe some sort of registration was not getting done.
Looking up stuff, I stumbled upon the "secret" testing menu on our Moto X, accessible by dialing *#*#4636#*#*
There I saw, to my horror, how my IMEI was 0.
Before giving up, I looked up how to fix this, turns out the BR modem was not quite right for Mexico. I flashed my country modem, getting he files from this video description (its in spanish, and the files are for Mexicos bands, but someone might find it useful): https://www.youtube.com/watch?v=oNSVRGvaKfY .
Rebooted, and to my relief, I had an IMEI again, though still no service, no wifi and no bluetooth.
Now, this special menu had some toggles that intrigued me, for they referenced to a possible registration, so I decided I should give it a go.
The toggles are pictured on the attached screenshot. These toggles, minus the CellInfoListRate, are only on and off.
I switched them so they would read "Turn radio off" (meaning it was on), "Turn off IMS regisration required" (meaning it was on, and my #1 suspect), "Turn off SMS over IMS" (seemed logical). I didnt play with the other 2 toggles.
Since I was cleaning, I left my phone on a table while I was sweeping, when suddenly the notification ringtone, one I hadnt heard in th past 2 days, sounded. I ran to my phone, and as angelic choirs played somewhere, I finally had signal bars, and an SMS had just gotten in.
Feeling relief, I was a bit let down when I still wasnt able to turn neither WiFi nor Bluetooth services. I called my brother, and when the call actually connected, I decided I might as well set my google account before anything else happened.
Now I had my contacts and data connection. I decided to turn the toggles that fixed this whole ordeal back to what I thought should be (thus now being as pictured on my screenshot) before rebooting.
Holding my breath, I rebooted and guess what: WiFi and bluetooth ould now be turned on, and connect.
This is the story of how I fixed this, hoping to help somebody out there.
Thanks to everyone who tried to help.
Moto X, you are a wild ride, but I love you.
I wrote a brief thread regarding my phone before...
I'll just give the details:
I'm the second owner, phone died while updating.
Phone was bootloader unlocked, and with TWRP recovery.
As such, baseband and IMEI info are missing, I have the original IMEI but, no efs backup or anything.
Any ideas? I've tried to re-install factory stock via both Skipsoft Toolkit and another Toolkit [Yes, I realize this is no help, now]
I've heard restoring another EFS from another phone may work...? I don't know though, I have two Nexus 5's and I can pull an EFS just to try to get back my original IMEI or I've read EFS Pro could help but, again I'm quite lost and just need a hand here.
Thanks.
Ive been an active user on this forum and the rules is that you cant discuss changing the imei here, because its illegal in many countries
Skickat från min Nexus 6 via Tapatalk
No changing!
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
RedHazy said:
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
Click to expand...
Click to collapse
here's a silly question.. how did you lose your imei? its not an issue on the n6 like earlier nexus phones, people just dont accidentally lose their imei, or their efs., unless they are restoring a nandroid from another phone, that has their efs backed up also..
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Sidenote: I did mess around with Titanium Backup but, I don't see that erasing my IMEI.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
If know the IEMI for your device there are threads on XDA that may restore it. If don't know the original IEMI you are dead in the water from the get go.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
i dont think that you are a criminal, seriously. i was just curious, as on the n5 and n4 that happens often. it really does happen very rarely on a n6. i think the phone dying while updating might of done it. if your bootloader is still unlocked, flashing the factory image might help you. but you will have to do it right, via fastboot while youre in the bootloader. dont use any toolkits, seriously!
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
RedHazy said:
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
Click to expand...
Click to collapse
heres some instructions, dont lock tbe bootloader after, just follow the flashing the factory image instruction. and if tou run into trouble, let us know, so we can help you http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
RedHazy said:
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
Click to expand...
Click to collapse
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Fingers crossed!
simms22 said:
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Click to expand...
Click to collapse
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
RedHazy said:
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
Click to expand...
Click to collapse
wipe the phone, factory reset i mean
(sorry for getting back so late)
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
droid4lif3 said:
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
Click to expand...
Click to collapse
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
graydiggy said:
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
Click to expand...
Click to collapse
The IMEI is stored in the CID partition. The CID is a small datablock containing the processor UID, Channel ID (different CID), a bootloader unlock flag, and IMEI. The CID is unique to each device, and controls several aspects of the device. This datablock has a signature on it so that your device information cannot be modified. Should you corrupt this partition, you will lose your IMEI, and the ability to unlock your bootloader. This is the only likely scenario in which you lost your IMEI. If you boot into your bootloader, you may see an error similar to
Code:
CID Datablock Error! 0xDEAD
otherwise I'm going to assume that is still intact. The IMEI has not been stored in the EFS for many years now. Check your CID on the device and make sure it's not 0xDEAD.
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
Click to expand...
Click to collapse
Did you seriously just ask an iPhone question? ???
Seriously though, bring it back to T-Mobile.
Lol, no, I knew I shouldn't of put that she had a iPhone 6S, now I will never be helped. I am just saying that I used a different sim card to make sure that it wasn't the sim card that was messed up.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
Click to expand...
Click to collapse
You can check by running the command
Code:
fastboot getvar all
in fastboot/bootloader mode.
You should see something like this:
Code:
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
The CID should be 0x00DE if it is not corrupt.
For the past half a year, I have been using Carbon rom on my Lenovo K3 Note, and it was fine, until it started slowing down. So, I decided to change it to another rom (Nexus), and the next thing I know, my SIM card is no longer detected.
Turns out, the IMEI was wiped.
How would I go about restoring this?
The things I have done:
MauiMETA = Never detects my phone. Places it into meta mode, but the light never turns yellow. Tried on 3 computers, and had no success on getting it to work. For two of the three, I couldn't find drivers for mt65xx and CDC.
MTK Droid Tool: The option to change the IMEI remained permanently greyed out, and was never given the option to change it.
Official rom: Didn't work. Currently using it, and still the same error (Null). Tried factory resetting it, no change.
Engineering mode: Always gave me an error when trying to enter command, never accepted it.
IMEI.EXE: Everything worked, except the IMEI's never changed in my device.
Have tried multiple roms, multiple wipes, SPFlash, CWM (Even ended up installing it again because I wiped my entire phone with SPFlash), and pretty much every trick I could find.
I need this think working in 12 hours.
EDIT: Problem was resolved with trying "official" roms until one allowed me to update within the rom. The Update that was installed via Lenovo's bootloader fixed it. The finished product was that of an untouched phone; I had to reinstall a bootloader, root, and a new rom.
If flashing stock doesn't help, and you have no kind of backup of where the imei resides, you likely need a service center to hopefully help.
But know that any talk of manually inputting imei numbers is not allowed on XDA, as its illegal in most areas.
Good luck!
Darth said:
If flashing stock doesn't help, and you have no kind of backup of where the imei resides, you likely need a service center to hopefully help.
But know that any talk of manually inputting imei numbers is not allowed on XDA, as its illegal in most areas.
Good luck!
Click to expand...
Click to collapse
So it isn't as simple as entering the two codes under my battery into some location, and rebooting?
I'm currently in Europe, and have no idea how any of that works (Studying abroad).
RocketPenguin1 said:
So it isn't as simple as entering the two codes under my battery into some location, and rebooting?
I'm currently in Europe, and have no idea how any of that works (Studying abroad).
Click to expand...
Click to collapse
That talk is not allowed, as I said. Inputting numbers falls under tampering and is illegal in most areas, as I said.
So try flashing stock, if you can. But without some sort of backup, you may be out of luck unfortunately.
Please keep number inputting talk off XDA, or I will need to close this thread. :good:
UPDATE: So, I flashed another "official" rom, which initially didn't work. However, it did give me the option to upgrade, which I did. With that upgrade, the IMEI is back, and my SIM card works.
Thing is, the ROM is almost entirely in Chinese.
How would I change my rom without wiping the IMEI?
Please post the link to download the ROM you used.
I have the same issue and even service centers failed to attempt this.
Thanx and regards
Raju
Chennai
You can easily rewrite imei number using snwriter tool, google it.
Long story short. I received a return on a phone I sold. The person who returned it tries to bypass the google lock on the phone by installing another firmware/rom. Instead of contacting me first so I could help them. they did not back anything up so all files were lost. I fix computer hardware and software but this is my first phone project. I read online how to flash it back to original firmware by using Odin 3.9 and a file I found online (N900AUCUCNC2_N900AATTCNC2_N900AUCUCNC2_HOME.tar.md5) this brought it back to droid 4.4.2. The padlock and custom icon are gone. But still, no IMEI or baseband both unknown. *#06# shows null/null. I need to get this phone able to work on my ATT network. I have no files to recover from. I don't know what files to be looking for or even what to do with them if I find them. I never rooted or jailbroke a phone first time flashing anything. so I need a bit of help. I can do it if I have clear and detailed instruction. but I myself do not know where to even begin. I have a computer and USB cable a note 3 sm-n900a and good computer and know how to get and download software and programs... just need to know what to download and how to use it. If you can help me I would be more than appreciative... thank you in advance!!!! I have attached photos.