Related
Right so i've done something to my phone, i added that battery circle thing for the galaxy s but i think it didn't take, and now it just loads up into the phone and keeps turning the screen on and off like its trying to load but it never does. OBVIOUSLY i've done something terribly wrong all i want to do is jsut wipe everything and start again fresh so it works! is there anyway to do this through odin or something? help would be appreciated..
Seems like odin and download mode is my best bet but can anyone talk me through what i have to do? i dont care what i put on my phone, as long as it works. seems like a good time to update my firmware anyways.. Just help lol, s**tting bricks at the moment and the thought of having a nice expensive paper weight...
if you want to fix it with minimal work and risc you can just goto recovery and make a wipe data/factory reset.
if you want to upgrade the firmware while you are at it, read this. we can not explain the procedure for every noob user again and again! it's not that hard...if you have any specific problems, report back here.
i recommend XWJM2 or XWJM5 from here
Already tried the simple factory restore and it just does the same thing as when it was before i did. loads up and then when it starts to load the data and the status bar it stops and then screen turns off and then back on and tries again. and again and again lol. I understand that you cant explain again and again and thats why im looking for myself but thought it was worth asking anyways. I have a feeling that the uhh is it framework file? the file that does all the status bar and stuff has gone weird and that didn't didn't get restored to factory settings when i restored factory settings as each time the phone boots, it doesn't show the status bar before it retries. And since the metamorph and the super battery circle indicator mess around with it. im assuming its to do with that.
woot got the phone working with a flash of odin. weird thing is that all my original files such as my back ups and the lag fix are still there in my internal sd card but i have no idea if they're still working because my actual apps in my app drawer such as rom manager have gone. Any idea what i can do now lol? should i delete the files and such from the internal card such as the lag fix files and the backups since im on jm5 now rather than JF3 that i was on before all this happened.
i think it would have been possible to save your old "installation" but not to explain to you how
when you flash with odin, all settings and apps are deleted. what remains is the data they saved on the sdcard. you can delete it or leave it, as you wish . i don't know which of all the lag-fixes you had running but i's not "active" any more so you can delete the files made by it if you are sure you know what to delete
btw. if you did a nandroid backup you could restore it now so be sure to do one next time you try new stuff
Questions and Suggestions.....
I just got a second captivate, this one WITHOUT a cracked screen!! Now i realize i could just teardown and swap the main board, or the digitizer itself, but... that would be too simple!
Or i could just call my provider and change my imei with them... but who wants to talk to their provider??
Or.... i could do something fun and learn, by cloning my phone. from what i understand, all i would need to change is my IMEI, contained in my EFS.. and i have several backups of my good efs, and could easily backup the new one.
Is it simply as easy as copying the efs folder over with root privilages? or better to do an ADB dd (data dump) then tar it and odin? or ADB push/flash....
Is there anything im not considering? Is there any real risk if I have my EFS backed up? Any other ideas? suggestions? discussion?
any neat/interesting things to do with a copied phone set?
I have mine dd'ed and ready to flash with heimdall(i don't think ODIN will touch the EFS partition, but Heimdall will if you put it in there) So IDK, I would talk to conexxion2005 or AdamOutler about this!
thats what i was thinking...
Yahh, Or contact Benjamin, I forgot his last name, but he made Heimdall
Just dd the efs partition and flash it with heimdall. Thats all you have to do.
Code:
dd if=/dev/block/stl3 of=/sdcard/sdext/efs.rfs
do the same with your new phone to make a backup of it. Change the name of the efs file so you dont overwrite it. When you get done, swap the serial number stickers. I didnt tell you all this. Its illegal
it's personal development for learning purposes.
This is why I value second opinions.
now to get 2 (active) sims for the same imei.....
they both have ICS RC3.1 on them ive had the one a few hours.
one with silver speaker mod, one with out. if you dont know silver speaker mod, GO FIND IT NOW! READ THE FIRST 4 PAGES AT LEAST!
this is what ive been dealing with for the past 2 months......
but it works just fine....
I dropped it a good 10 feet, but it was fine, 20 minutes later took out of my pocket to see this...
http://dl.dropbox.com/u/19201431/Images/cracked%20to%20****%20but%20works.jpg
Lol my sister's looks exactly the same!
Just flashed it yesterday, it's weird to feel all those cracks under your thumb, and it still works.
I'm not sure DDing then flashing it to another device will have the correct effect but it's worth a shot. I can do remote IMEI repair for the Infuse and Vibrant 4G but their EFS structure is different from the Captivate. I know for a fact you can't just throw nv_data.bin files around and expect the IMEI to follow as it won't. However, DDing the zone then flashing could result in the desired effect.
LET US KNOW!
How would I know for sure? By checking the about> phone?... Running ice cream sandwich so I'm not sure if the dialer codes will work
I wonder if any of this would help me with my borked IMEI? I'm on the network default IMEI (the one ending in 0000) and I really want my original IMEI back...
Any ideas?
Do you think it would help flashing to stock including CSC files? Then immediately booting into stock recovery to force it to apply this CSC?
I know it does some funky things in that first recovery boot.. Applying settings and such...
adzidek said:
I wonder if any of this would help me with my borked IMEI? I'm on the network default IMEI (the one ending in 0000) and I really want my original IMEI back...
Any ideas?
Click to expand...
Click to collapse
This would only help if you had a backup of your original
IMEI
TRusselo said:
This would only help if you had a backup of your original
Click to expand...
Click to collapse
crap.
Any ideas on how/who might be able to help me?
There is a guide in the captivate development section on how to restore imei
TRusselo said:
There is a guide in the captivate development section on how to restore imei
Click to expand...
Click to collapse
thanks, but I tried all that already. I'm looking for someone who can decrypt/hex edit my original IMEI into my nv_data.bin...
Sent from my SGH-I897 using Tapatalk
connexion2005 said:
I'm not sure DDing then flashing it to another device will have the correct effect but it's worth a shot. I can do remote IMEI repair for the Infuse and Vibrant 4G but their EFS structure is different from the Captivate. I know for a fact you can't just throw nv_data.bin files around and expect the IMEI to follow as it won't. However, DDing the zone then flashing could result in the desired effect.
LET US KNOW!
Click to expand...
Click to collapse
It worked for me.
I have tried to find more about my situation but asking seems to be the only way since all the info is either scattered or not available!
For two weeks I've been trying to fix my note from this ics emmc bug which made me loose efs folder and I have tried several methods with no luck, so I thought that repartitioning sd might kill the bug, so I repartioned just (parts)7,9,10,11 and also went for efs part that was empty anyway thought it might clear bad blocks, although afterwards I flashed efsfix.zip from another thread on here somewhere, because of which network and everything works just no lock screen and power button dialog? And when I flash any rom stock/custom it says (in red) error mounting efs, I found a solution for that by using terminal emulator and commanding "mount", But gotta do it manually afer every reboot?
And my imei is not the same as under my fone, how could I manually edit the imei and insert original fone info?
Could anyone help or guide me to a link so that I can recreate efs partition to ext 4 and the sort out other issues?
Edit: info in-depth!!
Thanks!
Does anyone know how to create/recreate an efs ext 4 partition on galaxy note? Is there a command or certain way to mount efs part as ext 4?
without efs backup you have lost your emei. Unless you resort to illegal methods in most countries (expensive z3x box)
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it.
Anyway, how did you analyze its efs thats corrupted, cause if you can flash gb from pc odin succesfully its not super bricked
Sent from my GT-N7000 using Tapatalk 2
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
That emei stuff is so overrated by secret agencies.
Sent from my GT-N7000 using Tapatalk 2
Thanks for the reply baz77.
Basically, I wasnt aware of this emmc wipe bug when I bought Note, I got my rom flashing experience and knowledge from SGS2, so after like a week of purchase I tried to flash ICS stunnner on my Note with squeaky clean, but resulted in getting my fone back from samsung after being revived, took 3weeks to return.
At this point I still didnt know about the bug because I had assumed that my own doing caused the super hardbrick, till I flash a criskelo rom with a wipe and my problems started off with not registered on network, after that I have been krazily searching and flashing to have the fone working flawless again without having to send the fone back to samsung becasue of the wait and tiny chips n crack on my fone.
And I figured that efs is corrupted by googling and gathering info about my particular problem and everything pointed towards efs being corrupted!
I am really hoping for them release a fix and I can get my fone back working as a whole again!
Edit: added missing words! Lol
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + no lock screen and power button dialog!?!?
Could I plz ask, where can I get the stock gb with pit file samsung
Sent from my GT-N7000 using xda premium with Alliance Rom v1.2 + No lockscreen and No Power button dialog!?!?
baz77 said:
recreate can be done by flashing gb with pitfile and option clear efs. Then you should get generic emei. Which stupidly is also blocked in some countries.
Click to expand...
Click to collapse
Apparently, pitfile and efs clear option doesn't work, I tried GB with pitfile got the red 'error mounting efs' and tried stock UK ICS 4.0.3 from (thanks to) Dr.Ketan but Ive still got the error and no lockscreen and faulty power button?!? Plus:- Sim Network is gone :banghead: , i'll just have to flash that efsfix.zip and do the terminal "mount" procedure again!!! manually!
"Probaly Leagality issues there" I'll try the same pitfile procedure with rom from another country if it doesnt work then dont really want to but guess this fone's going back to Samsung for repairs before I sell it off.
Many Thanks for your help!!
<<SUNG>>from my <<SAM>> GT-N7000
baz77 said:
At this point, just go to Samsung and have them illegally legally restore it lmao, they somehow are allowed to do it. 2
Click to expand...
Click to collapse
I have the custom binary count reset, so they shouldnt have any problems with repairing illegally then?? With stock UK ICS 403 Rom from this forum!?!
<SAMSUNG><ASONG> From GT-N7000!
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
I thought each rom had efs file, not so sure anymore. download and install 7zip, open the tar md5 rom file with it and ignore the warnings. should be efs. img in there, if not best download one, same csc as you have, if you know what it was before it became corrupt. I think kj4 has one, so you can flash whole gb rom with options efs clear and the pitfile.
If that fails, then perform a factory reset with code, do this only from gb, *2767*3855# in dialer. That might force the efs to reset itself to generic. Should not be needed, but hey it cant harm trying on gb. note own risk
If that fails, flash stock ics which you had in first place and ask them to fix it.
You need them anyway to get original emei back, which is why I said best go there. However if you still want to try above could give you a working emei. Its generic test emei and blocked in some countries thought, so if you need to travel...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Hey baz77,
I tried the same pitfile method with a GB236 Rom built from HongKong and flashed it twice, because I read on this forum somewhere that in the event of errors, missing files and apps after a flash, roms should be flashed atleast once more to get'em fully loaded but unfortunately even that method failed to mount the efs part.
Afterwards, I was just googling for more solutions and I decided to download and flash another GB236 rom Open europe built (wipe version) from Dr. Ketan's stock rom deposites and to my joyous surprise there were 2 extra tar. files, one named efs.md5.tar, so I quickly got my fone in download mode and flashed the rom with pitfile and when that was done, I got the fone back in download mode and Flashed the efs.tar (PDA), CSC, Modem (PHONE) and for the first time in 2 weeks the fone booted up normally as it should with the welcome screen, working lock screen and power button dialog! pheeeewwww!!!
But the imei is still not the same as under the hood, but I guess since the efs part had been corrupted, my fones probabaly using the emergency imei, Im using Alliance v1 with no apprent faults or errors.
i'll flash the GB Rom and try the factory rest code method by you and if it works then dont have to go to samsung and if doesnt then i'll keep using the fone as it is for as long as I have it and keep looking for solutions, if nothing happens then i'll get it sorted from samsung before selling it.
Your help is much appreciated, Thanks baz77!!! :thumbup: :thumbup:
<SAMSUNG><ASONG>from<GT-N7000
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
letters_to_cleo said:
back then.. there was an application on playstore that can fix IMEI issues... its called GSII repair.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
It worked mostly on all phones that I have heard of.. including the Note's of my friends whom their IMEIs got toasted.
See if you can give that a shot bud..
Ps. by the way.. most corrupted IMEIs have a mocked imei of 004999010640000
Others said that they were able to restore their original IMEI by flashing to stock GB, root the phone and install Root explorer, after that, you need to go to /EFS folder inside your phone(thru root explorer) and backup first your orig ' nv_data.bin ', now if you see a nv_data.bak in there with a previous date different from the bin file, then delete accordingly the nv_data.bin and rename the bak file to nv_data.bin reboot phone and check if orig IMEI is back on your phone.
Now this isn't applicable if your bak and bin files for ( nv_data) are all on the same date though.
don't try this yet unless your willing to give all possible options to restore back your original IMEI. Don't forget to try first the link I showed to you at the top.
Cheers.
:good:
Click to expand...
Click to collapse
Hi Letters_to_cleo,
Thank you for the suggestions mate, at the moment Im on Alliance v.1 403 rom, and I have just tried the fix from your link, did the steps1 & 2 restarted checked imei and it's the same serial (#to#) as you have stated, then i tried the step 3 which indicated that the nv_data.bin file is missing from that folder.
I have already gone to certain extents to return the fone in its generic state, so it won't matter if I tried once more besides trying repairs on GB rom is probably much safer then on ICS builts as long as the fone doesnt die on me,(completely again!), I 'll try your 2nd method in a bit and report back after!
Thanks for the support!!:thumbup:
<SAMSUNG><ASONG>from<GT-N7000
yeah that app wont work if you dont have efs backup. It distills from original. bak file the emei, now with the reflash of efs, even before you had lost it. only generic stuff left.
you need as mentioned before to go to samsung to repair emei, or find a phone place that can do it. You can yourself but in most countries its illegal. You need z3d box or equivalent for that, 150$$$$ lol, I have seen people who bought it offer that service for small fee. But be careful as ot could be illegal in your country, even if its going from generic emei to original emei lol.
Oh and you are welcome, been there done that, with the efs stuff. Samsung fixed mine.
My help is free, now if another has this you know how to help them
After Samsung fixes it,stay on gb, root phone and backup efs on multiple locations(pc, cdrom, floppy disk, bank vault you get it) In future when you buy android do that first. How to is in dr ketans toolbox thread in general section.
edit efs backup is not in nandroid, nor titanium backups. In fact still to date there is not one solution that can back everything up on your phone.
Sent from my GT-N7000 using Tapatalk 2
letters to cleo, corrupt emeis are empty or 0000000000000000000000000,
the 490000 emei is given when resetting efs. That is not corrupt anymore to my knowledge
Sent from my GT-N7000 using Tapatalk 2
oh I ran into missing lockscreen issues after fully fixing it, I have in my profile then statistics started a thread which links to a solution for that
Sent from my GT-N7000 using Tapatalk 2
Hi Enseven reporting,
@Letters_to_cleo, the methods you suggested dont work but thanks for trying to helping, i didnt find the bak file in efs folder but there 2 nv_data files, and they're both dated from Jan2011, renaming them just disable's the network and doent change the imei#, it remains the same!
@baz11, Yes mate, you are right this fone's going back to samung bcuz im not looking to $pend 150 on some box that I wont even use twice.
Im not really that fussed about imei not being as same on fone hardware, just as long the fone works, but like you said it probably is illegal to sell a fone with messed up serial no.
And on top of that fone's price would drop for having software issues, only wanted to fix it so that I could sell it on without loosing much $$ from the original price I paid for it, it'll be disapointing since Ive only had the fone for just over 2 months.
And I did manage to fix the welcome/lockscreen/power button issues by flashing efs.tar I got from that wipe version Open Europe Rom but even after the flash, it restore's the needed files but doesnt really prompt the features so I gotta insert this command through terminal emulator: "echo n- ON> /efs/imei/keystr" "sync"and factory reset, then the fone reboots normally with everything working but the IMEI ofcourse!
Wonder if your lockscreen fix works ive looked for it on your profile's statistic's tab but uable to find it, could you plz provide a link. Thanks
Ive tried all methods with some luck and no further progress apart from having to buy expensive equipment, so I guess i'll keep using the fone and looking for any miraculous solution till I resort to Samsung.
P.S: If they cant find a fix for the emmc bug by working on scripts , they should atleast invent a nano tech powder (gadget bug killer) to sprinkle on the motherboard, LOL!!!
because this problem goes way back, like another user said on here you could make a movie about now, and ithink it started off as a scifi now its a scifi/thriller, "shall I wipe before flashing & risk hardbrick Or shall I wait for samsung to pace up the support!!!
Thanks to xda and memebrs for being online 247 and all the support though!!
<SAMSUNG><ASONG>from<GALAXY-GTN7000>using xda premium!!!
Hi En7,
Sorry to hear my steps didn't work on your phone bud.
I checked some forums here in XDA and I've come across this one: http://forum.xda-developers.com/showthread.php?t=1804117. (I'm not sure though if you have come across that link before or not).
It is for the S3 forum but there's a tool in there that you can try to download and run to somehow restore your corrupted IMEI. It's worth taking the risk I should say but who knows..any given tool/info is highly useful and it could be a clear shot in bringing back your original IMEI back right?
Cheers bud!
lol that cracked me up nano powder hahaha good one.
you found the lockscreen fix, its the same fix I found while back from some guru.
I guess you can change emei to original with someone who has such a box. Finding is not to difficult, just need to go to a shop that can repair emei. Preferably Samsung thought, Just go to a samsung service centre, or store where you bought phone. Best unroot and put stock firmware that matches your phones original csc, to avoid anoying questions. Just tell the truth you updated phone and emei was gone/changed and you want original imei back. Samsung can fix it. Note, this time dont use pit or clear csc. Its not needed anymore.
I searched hard and long when I had that issue with emei, wasnt without a backup able to change it back to original, other then Samsung or such a box.
It annoyed the crap out of me. I can relate to what you were going through.
Everybody is nandroid this titaniun backup that, apparently efs is the only thing not standardly backed up with any standard mainstream solution.
Sent from my GT-N7000 using Tapatalk 2
oh, and good idea, maybe you should write a scifi thriller
Sent from my GT-N7000 using Tapatalk 2
Edit: Solved by going back to Stock GB. Thanks everyone!
I've got a friend who got a new Captivate from the US. And he flashed CM10 right after getting it, without making a backup of the efs folder. Now, the efs partition is completely empty, and of course it says "Unknown baseband, unknown imei", etc".
I've looked around, but all the imei restore methods seem to require at least one efs file. However in this case we have none. So, is there any way to restore the efs/imei? Maybe mounting it to the pc and running a file restoration software (might sound desperate, but we are).
Also, I have another captivate (this one is mine) with the efs. Would it be possible to modify my backup to use his original imei and then restore it in his phone?
Any ideas are welcome. Thanks in advance.
Installing CM should automatically backup /efs to the sdcard. Look for a folder called "backup." Also, flashing to stock can sometimes resolve these issues without tampering with /efs
I can't give you a 100% guarantee, but the two phones that I've had to recover IMEI's for both regained the efs folder contents when I flashed to stock GB from an ICS or JB rom.
Waiting 5mins inbetween postings sux.
The easiest way I could find to restore my IMEI was to re-flash back to a stock (in my case it was a rogers rom) then go forth from there. Like it was mentioned above, CM9/10 save the efs and restore it after flash. I lost my IMEI while flashing Helly and was frustrated at reading the "fixes". It was just easier to format, reflash stock then go back to CM10 (Which I'm running now and it's great).
Thanks for the replies.
Apparently, he tried to flash CM9, and in the process he thinks the internal memory (/sdcard/) was somehow wiped and now he can't find that folder. I told him to use recuva or something like that to try and get them back, let's see how that goes.
But in case he can't recover that folder, is there any other way? Maybe mounting efs partition on the memory and using recuva then?
He really has bad luck...
Well, there really is NO backup. I can't find the efs backup on the sdcard. Even tried with Recuva and there's nothing there.
What's funny about it is that there's no files in the efs partition, yet the df command says it's full. Any ideas?
As a last resource thing, I was thinking about using the efs from MY captivate and see what happens. Thoughts?
I really apreciate any comment!! Thanks in advance.
moikop said:
Well, there really is NO backup. I can't find the efs backup on the sdcard. Even tried with Recuva and there's nothing there.
What's funny about it is that there's no files in the efs partition, yet the df command says it's full. Any ideas?
As a last resource thing, I was thinking about using the efs from MY captivate and see what happens. Thoughts?
I really apreciate any comment!! Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1300843 Go there and get one of the One-Clicks that will take you to stock GB. As several other people have said that is your best bet for getting the efs folder back.
m1batt1 said:
http://forum.xda-developers.com/showthread.php?t=1300843 Go there and get one of the One-Clicks that will take you to stock GB. As several other people have said that is your best bet for getting the efs folder back.
Click to expand...
Click to collapse
I can't believe my eyes, it worked! Thank you very much!! :laugh:
moikop said:
I can't believe my eyes, it worked! Thank you very much!! :laugh:
Click to expand...
Click to collapse
Now before you go anywhere else back up your efs folder!
Sent from my SGH-I897 using xda app-developers app
could anyone help with this, i bade a backup of the efs, and imei folder,I can find it no prob. just dont know how to restore it. cant get into diag mode to try a qpst restore either
SPEED_RACER_5.0 said:
could anyone help with this, i bade a backup of the efs, and imei folder,I can find it no prob. just dont know how to restore it. cant get into diag mode to try a qpst restore either
Click to expand...
Click to collapse
Just do a search on xda, there are losts of threads than can help you work through this.
I was able to restore my IMEI using this method:
http://forum.xda-developers.com/showthread.php?t=1264021
I did it via the terminal emulator on the phone.
I didn't have a good backup of my original /efs folder, either.
it just happened, that my solution for restoring imei on sgs3 i9300 came by installing Android Revolution HD rom. Maybe it happened because it's based on stock. You should try, maybe it will help. :good:
stevegrin said:
I was able to restore my IMEI using this method:
http://forum.xda-developers.com/showthread.php?t=1264021
I did it via the terminal emulator on the phone.
I didn't have a good backup of my original /efs folder, either.
Click to expand...
Click to collapse
I just used the method you linked and it worked like a charm. Thanks!
Cant restore imei
I updated me galaxy s5 g990f and lost network etc due to no imei even *#06# shows null imei.. I had phone direct from o2 brand new..ive tried nv read write..qpst tools..qdxm tools and when reboots still no imei flashed firmware before recent update and same thing..any one know how to solve this as o2 ridicukus tell me not covered by insurance or warranty..i looked at rooting but the apps for imei just fool websites not a network..i know can have fixed online but id rather attempt myself to get imei bk or edit system so I can put the imei on..its a galaxt s5 g900f on marshmellow 6.0.1 with snapdragon processor/qualcom..thanks
Hows it going guys. Been using a Captivate now for a month (mostly on CM9, CM 10 as of a yesterday) and now I am being told I ahve an IMEI error. I have ALWAYS had issues with this phone as far as data connection goes (sometimes I can only use Opera as a browser) and maybe this has been the main problem. The software IMEI does not match the number behind the battery door. Is this a problem that AT&T would fix?
sjorge3442 said:
Hows it going guys. Been using a Captivate now for a month (mostly on CM9, CM 10 as of a yesterday) and now I am being told I ahve an IMEI error. I have ALWAYS had issues with this phone as far as data connection goes (sometimes I can only use Opera as a browser) and maybe this has been the main problem. The software IMEI does not match the number behind the battery door. Is this a problem that AT&T would fix?
Click to expand...
Click to collapse
You can restore your IMEI by going back to stock KK4 with Odin (or Heimdall). Or if you have a backup of your efs folder (highly suggested).
You can go back to CM10 after without any problem. KK4 -> flash Corn kernel -> Flash CM10 and Gapps.
Hopefully your IMEI will stay fine but if not, you have your efs backup so just swap it by either mounting system or with a root explorer.
And usually to prevent additional mismatches in IMEI, it's advised to remove the SIM card before flashing. I haven't had a problem doing that.
So i apparently made a big mistake. I simply flashed back to stock kernal while still running CM10, so that obviously messed things up. I then use oneclick un brick and went back to 100% stock. While running Keis to update back to gingerbread, the update failed and now I have the phone ! computer screen showing. Neither my laptop nor my desktop are recognizing the device. What should I do now?
sjorge3442 said:
So i apparently made a big mistake. I simply flashed back to stock kernal while still running CM10, so that obviously messed things up. I then use oneclick un brick and went back to 100% stock. While running Keis to update back to gingerbread, the update failed and now I have the phone ! computer screen showing. Neither my laptop nor my desktop are recognizing the device. What should I do now?
Click to expand...
Click to collapse
Search before posting? lol
Here it is: http://forum.xda-developers.com/showthread.php?t=1953930
There's abolutely no reason to go back to 2.1 eclair. You should flash Odin KK4 without bootloaders when things like this happen. Now you'll have to flash Odin KK4 with bootloaders
Ok. So i have FINALLY got my phone back up and running after all sorts of issues. I found myself in a position were I had to build a jig to make this damn phone work again.
Ok so, I once again have thie IMEI conflict. I am sitting on 4.2.1 AOSP Jelly Bean. I installed everything without having the sim card in this time, so now I am unsure why this error occurred. I can use my phone to make calls, send texts, and use the internet, so im not really sure what it's deal is. All i know is that I don't want to be stuck using my old blackberry again, so I am going to make sure I know the correct steps to follow to fix this.
sjorge3442 said:
Ok. So i have FINALLY got my phone back up and running after all sorts of issues. I found myself in a position were I had to build a jig to make this damn phone work again.
Ok so, I once again have thie IMEI conflict. I am sitting on 4.2.1 AOSP Jelly Bean. I installed everything without having the sim card in this time, so now I am unsure why this error occurred. I can use my phone to make calls, send texts, and use the internet, so im not really sure what it's deal is. All i know is that I don't want to be stuck using my old blackberry again, so I am going to make sure I know the correct steps to follow to fix this.
Click to expand...
Click to collapse
I believe I mentioned this before but when flashing to stock KK4, you should make a backup of your efs folder. It contains your IMEI and restoring your backup would fix your problem.
so, just to be clear. I just need to flash the stock KK4 kernal to my phone to fix the IMEI number? I would use odin to do this right?
Sorry for all teh noob questions. I just dont wanna end up in the same terrible situation i got myself into last time.
sjorge3442 said:
so, just to be clear. I just need to flash the stock KK4 kernal to my phone to fix the IMEI number? I would use odin to do this right?
Sorry for all teh noob questions. I just dont wanna end up in the same terrible situation i got myself into last time.
Click to expand...
Click to collapse
You'd need to use Odin KK4 to get back to stock, make a backup of your efs folder, flash Corn kernel and then flash the ROM you wanna use.
BWolf56 said:
You'd need to use Odin KK4 to get back to stock, make a backup of your efs folder, flash Corn kernel and then flash the ROM you wanna use.
Click to expand...
Click to collapse
Thanks! I for some reason thought this is what I tried to do before, when it ended up crashing my phone. The stock kernel will run with what ever custom rom I still have installed?
sjorge3442 said:
Thanks! I for some reason thought this is what I tried to do before, when it ended up crashing my phone. The stock kernel will run with what ever custom rom I still have installed?
Click to expand...
Click to collapse
Odin KK4 is a ROM, it will bring you back to stock GB. From there, you'll have to follow the steps I posted above.
so ive been having issues with my phone as I've been too busy to reset to the stock rom. Is this what I should be using? With or without bootloaders? forum.xda-developers.com/showthread.php?t=1386924
sjorge3442 said:
so ive been having issues with my phone as I've been too busy to reset to the stock rom. Is this what I should be using? With or without bootloaders? forum.xda-developers.com/showthread.php?t=1386924
Click to expand...
Click to collapse
Without bootloaders if you're already on GB or higher.
ok. So i have sucessfully created backups of my EFS folder using both EFSPro and Super Manager. Problem now is that I cannot get EFSPro to recognize that my captivate with HellyBean installed is connected to me PC. Also, Super Manager will not allow me to paste my copied EFS folder into the directory. What should I do now?
EDIT: Alright, So I flashed to stock, flashed a semaphore kernel and then installed CM9.1. From here after connecting and disconnecting the phone a few times I was able to get EFSPro to push the recovery tar to my phone. It reboot, but when I check the IMEI, it still is the generic one.
sjorge3442 said:
ok. So i have sucessfully created backups of my EFS folder using both EFSPro and Super Manager. Problem now is that I cannot get EFSPro to recognize that my captivate with HellyBean installed is connected to me PC. Also, Super Manager will not allow me to paste my copied EFS folder into the directory. What should I do now?
EDIT: Alright, So I flashed to stock, flashed a semaphore kernel and then installed CM9.1. From here after connecting and disconnecting the phone a few times I was able to get EFSPro to push the recovery tar to my phone. It reboot, but when I check the IMEI, it still is the generic one.
Click to expand...
Click to collapse
You could simply make a copy of your efs folder and use a root explorer to switch it if your IMEI doesn't match.
so the efs folder i backed up with Super Manager cannot be restored by Super Manager? If I have to buy root explorer, thats not a big deal, but if i dont, well then its silly to purchase it it. Root explorer will however allow me to restore the efs folder that I have backed up onto my pc?
sjorge3442 said:
so the efs folder i backed up with Super Manager cannot be restored by Super Manager? If I have to buy root explorer, thats not a big deal, but if i dont, well then its silly to purchase it it. Root explorer will however allow me to restore the efs folder that I have backed up onto my pc?
Click to expand...
Click to collapse
I suggest root browser lite. It is the best root explorer I've personally used and its free.
Sent from my SGH-I897 using xda app-developers app
sjorge3442 said:
so the efs folder i backed up with Super Manager cannot be restored by Super Manager? If I have to buy root explorer, thats not a big deal, but if i dont, well then its silly to purchase it it. Root explorer will however allow me to restore the efs folder that I have backed up onto my pc?
Click to expand...
Click to collapse
m1batt1 said:
I suggest root browser lite. It is the best root explorer I've personally used and its free.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
There are a few free root explorers out there, I personally use Root Explorer but you can use a free one. It only needs root right.
ok so I am still having issues over here. I have efs folder that I backed up with Super Manger while I was still on Gingerbread right after rooting with a working IMEI. It has three files and one folder in it. an empty IMEI folder, a Cryptprop_onetimeboot, cyrptprop_securewipe data, and nv text document. When I used root explorer light to copy the backup folder to the current efs folder, I found about 7 files there. I deleated them, pasted the backup folder contents and restarted my phone and I still have the generic IMEI. There was also a folder in current efs folder called lost and found which I cannot deleat.
sjorge3442 said:
ok so I am still having issues over here. I have efs folder that I backed up with Super Manger while I was still on Gingerbread right after rooting with a working IMEI. It has three files and one folder in it. an empty IMEI folder, a Cryptprop_onetimeboot, cyrptprop_securewipe data, and nv text document. When I used root explorer light to copy the backup folder to the current efs folder, I found about 7 files there. I deleated them, pasted the backup folder contents and restarted my phone and I still have the generic IMEI. There was also a folder in current efs folder called lost and found which I cannot deleat.
Click to expand...
Click to collapse
Did you verify the backup you made before flashing? The IMEI shouldn't be empty so I'm thinking you got a bad backup.
Are you getting any error with your generic IMEI?