For some reason my imei changed ri 0049xxxx. I dont know how it happend. Tried to roll back by recover the efs folder from a backup. No success. Also tried several ways described around thid board. No success either...
So iam pretty much helpless. Anybody please help me out.
Big thanks in advance.
Running Litening Mod 6.1 with Ninphetamine 2.1.3
XXKH3
Sent from my GT-I9100 using xda premium
sad to hear that...
Apart from searching the forum and trying all the fix efs IMEI posts nothing return to service centre .
jje
Yes,but sad does not make the point :-\
What can the service guys do,that i possibly cant do on my own?
Sent from my GT-I9100 using xda premium
biba.butzemann said:
Yes,but sad does not make the point :-\
What can the service guys do,that i possibly cant do on my own?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Well they can search this forum for the fix and apply it. So far all evidence seems to suggest that you cannot do this on your own.
While restoring from an efs backup, it's important to restore the appropriate rights for the files too. A simple copy-paste doesn't work. If you have properly backed up the efs folder (not copy-paste), a correct restore action should work.
Even if everything fails, service guys should be able to regenerate the efs folder with the correct IMEI, but they won't do it for free, since your warranty is invalid by now.
aydc said:
Even if everything fails, service guys should be able to regenerate the efs folder with the correct IMEI, but they won't do it for free, since your warranty is invalid by now.
Click to expand...
Click to collapse
You can do this on your own if you follow the steps in a few guides knocking around on the forum.
Can anyone point me the exact thing to backup so that I can restore when I get issues? I'm worried now.
I've made a copy of my EFS folder. Isn't that enough? If so, Can you point me out to the correct direction to backup and restore b ack??
@aydc : i know 1001:1001
Sent from my GT-I9100 using xda premium
@intratech : i tried,even the stuff with the hexeditor. For some reason i have no success. Would you helo me out,please
Sent from my GT-I9100 using xda premium
Same problem on my phone.
Running Litening Mod 6.1 with Ninphetamine 2.1.3
XXKH3
I tried all guides incl. reformating of the efs partition, but with no success
What did you do? Did you send the phone to samsung?
If Samsung will not help and you have no other option contact me via PM, I maybe able to help you.
Related
Does a stock rom image for the continuum exist that can be flashed with Odin and not CWM? I dont think my phone is bricked cause I can get into the download and recovery screens. I just cant do anything from the recovery screen its stuck.
Im either gonna fix this or smash this phone to pieces. Any help would be appreciated.
Thanks
Lol, chill... I'll go on my computer now and share the link with you xP
Sent from my SCH-I400 using XDA Premium App
Ok so I might not smash it but boy is this frustrating.
Thanks for your help lol =)))
Ive done some extensive searching and I havent found a single stock continuum rom for odin anywhere. So if you could create one or point me in the direction of where I could download one I would appreciate that.
http://forum.xda-developers.com/showthread.php?t=967165
Check that out.... Flash with Odin.. Then find (in the Continuum Android Development section) the DL17 update zip, and put that on your sdcard (named update.zip)...
Then you should be good to go...
However, i highly suggest you getting CWM working... Recovering is a lot easier with it... If you are having difficulty go log onto the IRC (http://webchat.freenode.net/) with the #Samsung-Continuum and i will help you out
You are my effin hero... All I needed was the kernel and it fired right up. Ill be keeping these files close cause Im sure Ill need them again.
Thank you!!!!
Justin
Lmao, no problem man.. haha.. Thank imnuts too for all of his development
BTW: If you stop by the IRC i will help you get cwm up and working.. Then you can flash themes, make backups, and flash my awesome Softkey Modifications
Any idea why I cant access data? Im on the phone with verizon but still no luck..
Also cant access the sd card from my pc and wifi on the phone will not connect..
Verizon is stumped they told me to take it back to the store for a replacement..
What a long day lol =)
Also voice service works I can make calls and send/receive text messages just no data. No 3g indicator.
Nevermind I got it figured out.. Everything is running normally with the DL17 clean rom.
Thanks again
jaizero said:
Nevermind I got it figured out.. Everything is running normally with the DL17 clean rom.
Thanks again
Click to expand...
Click to collapse
How were you able to get the data signal back, please email me with information [email protected] thanks in advance. i tried almost everything and no luck
Go to settings, about phone, then tell me what your baseband info is....
Sent from my SCH-I400 using XDA Premium App
I have been all through the forums and can't find a working stock image
I'm feeling a little too tired to type everything so I uploaded a video to Youtube with my problem to help give a better idea where I'm stuck.
youtube. /watch?v=Iw4iAxuCAl0
I will take a look when I get home and see what I can do XD
Sent from my SCH-I400 using XDA Premium App
I would be very appreciative,
Thanks for your time!
hey i saw the video, just a quick question, do you have cwm installed? because i have my nandroid backup that you might be able to use, or you can also you adrynalynes roms and imnuts' kernel that you can load on to there and see if that works, and i saw what file you were tryin to load on odin, i have that same fine and it works for me to you may want to try and re-download it, any questions feel free to pm me
Nooooooooo nandroid backup sharing!!??!!
Sent from my SCH-I400 using XDA Premium App
trailblazer101 said:
Nooooooooo nandroid backup sharing!!??!!
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
lol its not really mine, its one that this other person sent me, just to see how it would react when i bricked my phone..i'm guessing to your reaction thats a bad idea?
torque240 said:
lol its not really mine, its one that this other person sent me, just to see how it would react when i bricked my phone..i'm guessing to your reaction thats a bad idea?
Click to expand...
Click to collapse
Lol, with Nandroid backup, it makes a compleeeete backup of everything.... Which means it backs up your email logins, facebook logins, GOOGLE logins, everything... Which means they could buy apps on the market using your account..... Not good, lol..
trailblazer101 said:
Go to settings, about phone, then tell me what your baseband info is....
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
oh and sorry to bring this question back up, but is there a radio file for the continuum out somewhere?
trailblazer101 said:
Lol, with Nandroid backup, it makes a compleeeete backup of everything.... Which means it backs up your email logins, facebook logins, GOOGLE logins, everything... Which means they could buy apps on the market using your account..... Not good, lol..
Click to expand...
Click to collapse
oh ok, well either way i did the cwm before i entered in my information on the phone, but i see what you mean..give me a break i just woke up..lol, but do you think flashing clean roms and kernels might help him?
hey guys,
i have a big problem. i just flashed the newest cm7 nightly for my i9000 and now there is no baseband version anymore. i tried to flash a lot of versions but its still "unknown" and therefore no connection is able.
i also tried to restore my old nandroid backups with a working baseband version but didn't help.
can you please help me to get my phone working?
ty in advice
Treat it as a fresh install. Flash back to froyo to restore your baseband then flash cm7 again.
Sent from my GT-I9000 using XDA Premium App
but isnt it possible to do something else?
and have you a good howto for me? ty!
Baseband unknown is probably a corrupt IMEI, If you made the efs backup before flashing CM7, then restore that, and make sure you have a compatible modem (i had this issue with MIUI yesterday)
Then after restoring the efs backup, reboot, and that should fix it.
If not then as mentioned above, do a fresh install.
Search for EZBase / EZROM to flash back to froyo. and then follow the installation procedure for CM7...
always have a current backup of the efs,. leave a copy or two on your PC, this will save you from having to do this whole fresh install again
trust me... i learned the hard way.... 3 times lol
mhm it seems to be the IMEI stuff. once i did an efs backup while installling the cm7 with a script called something like efs_backup
where can i find this backup and how to restore it?
ty man!
does someone know how to restore the IMEI. I did a backup before and i think i found the folder: /sdcard/backup/efs
CZECHer said:
does someone know how to restore the IMEI. I did a backup before and i think i found the folder: /sdcard/backup/efs
Click to expand...
Click to collapse
Yes thats correct, copy the NV_data.bin and the NV_data.bin MD5 to /efs using root explorer or similar.
once done reboot and check when the phone boots back up.
should i delete all files in the directory /efs first before i copy those 2 files in?
another hint. i tried to backup the efs and then installing a fitting modem:
when i try to install the modem (JVK - definetly working before) i get this message in cwm: asser failed: write_raw_image("/tmp/modem.bin","radio") insallation aborted
so can help me?
ty
Ok first of all, copying the relevant items from /backup /efs to /efs will just overwrite, so no need to delete - you can if you want.
as for the modem issue, maybe it was a bad download, try re-downloading. Also, make sure THAT particular modem is compatible, there have been some issues with the latest CM / MIUI releases, there is a link somewhere to all modems for this specific release..
EDIT: here are the modems for the latest release of CM / MIUI http://codeworkx.de/download/cyanogenmod/
I have a feeling in the end you will find that just going back to froyo first is still your best option.
Search in the General thread for my name and CM7 install to find my guide. Follow it and you will be fine.
Sent from my GT-I9000 using XDA Premium App
rschenck said:
I have a feeling in the end you will find that just going back to froyo first is still your best option.
Search in the General thread for my name and CM7 install to find my guide. Follow it and you will be fine.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
hah i made it thanks to azzledazzle i love you man < 3 no need to do a fresh install 3 times
ok the imei was corrupted and i had to delete the whole contetnt of /efs first. in addition i had no fitting baseband version^^
where did you get this link from? will it be up to date?
what is your favourit baseband version btw?
ty all this day is rescued
CZECHer said:
hah i made it thanks to azzledazzle i love you man < 3 no need to do a fresh install 3 times
ok the imei was corrupted and i had to delete the whole contetnt of /efs first. in addition i had no fitting baseband version^^
where did you get this link from? will it be up to date?
what is your favourit baseband version btw?
ty all this day is rescued
Click to expand...
Click to collapse
Congrats....and the link from azz is fine, straight from codeworkx. You really ought to read the dev thread to stay up on these things.
Sent from my GT-I9000 using XDA Premium App
rschenck said:
Congrats....and the link from azz is fine, straight from codeworkx. You really ought to read the dev thread to stay up on these things.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
which one is the current dev thread? and which baseband is your favourite one?
Hey there,
I would love to change my stock rom, but here is problem:
I flashed Lightening ROM one month ago and I destroyed my motherboard with it and warranty was not accepted and I had to pay for another one, so Im scared to death that if I flash another ROM this is gonna happen again :S Can you guys tell me what should I do?
prof.kiwi said:
Hey there,
I would love to change my stock rom, but here is problem:
I flashed Lightening ROM one month ago and I destroyed my motherboard with it and warranty was not accepted and I had to pay for another one, so Im scared to death that if I flash another ROM this is gonna happen again :S Can you guys tell me what should I do?
Click to expand...
Click to collapse
Damn, how in the world did you destroy your motherboard? Were you messing about with voltages and the like?
You should try flashing CheckRom Revolution from the android development section, that's the one I use and it's awesome!
prof.kiwi said:
Hey there,
I would love to change my stock rom, but here is problem:
I flashed Lightening ROM one month ago and I destroyed my motherboard with it and warranty was not accepted and I had to pay for another one, so Im scared to death that if I flash another ROM this is gonna happen again :S Can you guys tell me what should I do?
Click to expand...
Click to collapse
destroyed the motherboard by flashing a rom.... wow, superman act!!! try again, but read the rom thread properly before trying
Well, I just did what Lightening thread said to do, and my phone didnt read SIM card next day... People at Samsung said that root damaged motherboard :S
prof.kiwi said:
Well, I just did what Lightening thread said to do, and my phone didnt read SIM card next day... People at Samsung said that root damaged motherboard :S
Click to expand...
Click to collapse
That just sounds like things when wrong in the /efs folder when you flashed, which will cause that problem I believe. You should backed up the folder so if that does happen, you could just restore your efs/ folder again, and things should have been hunky dory. I use this tool to back up my /efs folder, you can find it here: http://forum.xda-developers.com/showthread.php?t=1308546
I suggest you might want to read this:
http://www.xda-developers.com/android/backup-and-restore-your-efs-folder-on-samsung-devices/
Candanga said:
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centers.
Click to expand...
Click to collapse
Im confused now, they told me that that was hardware issue with motherboard, how could something about software help me with that?
prof.kiwi said:
Im confused now, they told me that that was hardware issue with motherboard, how could something about software help me with that?
Click to expand...
Click to collapse
Just from how you described what happened, a problem with the /efs sounded like the most likely cause of your problem. Obviously I don't have your device so I can't tell you what actually happened. The problem of your phone not reconsigning your sim after flashing is the main symptom of a corrupt or damaged /efs folder, that's why I thought to suggest you back up your /efs folder, so if it was your problem last time, and it happens again, you can just restore the folder and things should be fine.
Ok, I will think about that but Im scared to death of paying $200 again :S
If your aint 100% confident on flashing, you shouldnt be flashing anything.
Sent from my GT-I9100 using Tapatalk
I suspect they were lying, but I'm no computer engineer or technician. I just cannot see your phone sending high enough voltages or enough heat, to physically damage your motherboard. Nor can I see how flashing a rom through CWM messing with your bootloader.
kyleforge said:
You should try flashing CheckRom Revolution from the android development section, that's the one I use and it's awesome!
Click to expand...
Click to collapse
Whats this Rom got that makes it awesome?? Just wondering.
Sent from my GT-I9100 using XDA App
If I were you I would Flash a stock Rom and stick to it mate. You don't sound very confident in what you are going.
Sent from my GT-I9100 using xda premium
After screwing up my device by messing up the build.prop I would like to share that the best thing you could possibly to for your device would be to create a backup in recovery. Had I not done that my device would be bricked.
If all you did was mess with the build.prop, then it's only soft bricked. Wipe and Flash a new ROM.
Also maybe don't change/edit something unless you know the consequence/outcome maybe?
Sent from my Transformer TF101 using xda premium
littleemp said:
If all you did was mess with the build.prop, then it's only soft bricked. Wipe and Flash a new ROM.
Click to expand...
Click to collapse
Normally I would agree without you but the build.prop I edited has a tag for no sd card, so it couldn't be mounted in recovery.
Making a backup is android modding 101...thanks for the revelations
A nandroid is awesome
Should be done before any kind of modification and is a huge tool - unique
DN41
Sent from my DHD @ ARHD 7.0.0
Wow I thought this would be something to do with nvflash techniques.
Instead I learned that someone else discovered common sense way to go buddy!!!
Sent from my Transformer TF101 using xda premium
If you don't have a working recovery, then try using Nvflash to restore it to working condition. Also READ before you do anything.
Sent from my MB860 using XDA App
=_=
search function and fully understanding is your tools
repeat the mantra and never brick your device again
ohm
roflcopterofl said:
After screwing up my device by messing up the build.prop ....
Click to expand...
Click to collapse
Sorry for noobing aroung guys..just want to learn. How can you screw up your device by changing the DPI? You have to go far under 130 something (or is this kind of a BS information?^^), don´t you?
brooon said:
Sorry for noobing aroung guys..just want to learn. How can you screw up your device by changing the DPI? You have to go far under 130 something (or is this kind of a BS information?^^), don´t you?
Click to expand...
Click to collapse
Yeah you would have to do something amazingly stupid in the build.prop to cause a soft brick and even then it's just boot looping and you reflash or restore a backup. Actually with build.prop you go advanced restore restore system done thats like a 2-3min job tops.
I was excited about this thread at first (the title)..... I think it should be closed Backing up is on every devs front page and almost an un-written part of the xda banner/root/mod community.
Sent from my Transformer TF101 using xda premium
Hi,
Love this site for the sheer amount of knowledge people have. I've searched for an answer to this but can't find a clue. I flashed my Fascinate with CWM and then TSM Resurrection with build EH03, Firmware 2.3.5. I did a backup of my stock Froyo before moving over to a custom ROM but I can't find the NANDROID backup file on the sdcard. I then did another backup after upgrading and now I can't see either of those backups.
Has this happened to anyone else with Fascinate? I've checked in clockwork/backup but the files are not there.
Thanks for your help.
There not in
SD card>clockwordmod>backups?
Sent from my SCH-I500 using Tapatalk
No, don't see em there.
You got me...
Sent from my SCH-I500 using Tapatalk
Appreciate the help shelby04861.
Does anyone know where the files could be or what the issue could be?