Bought and activated used phone 2 weeks ago. Phone worked fine thru Friday night. Woke up Saturday to find I could not connect to cell network. Call to carrier revealed my IMEI number does not match the number they have. Somehow my phone IMEI changed to 350000000000006. Internet search revealed many others with same problem. The main difference between their situations and mine is the fact that in almost all of their cases their phone was rooted and they flashed many different ROMS to their phones and something obviously went wrong. My phone is NOT rooted and I have not tried to modify anything. Simple as that. Went to bed working, woke up broken.
I have now researched this the last few days and have no clear answer. Is it possible to set my IMEI back to my correct, legal,clean and not blacklisted value? Any help is greatly appreciated.
My guess is without a backup of the original, you can't do anything about it. Best bet is probably return it to the store you got it from and get a refund/exchange.
Edit:
Fastest and safest bet would be refund/exchange.
Little research has shown other people had a similar issue. Check Nox to make sure the phone hasn't been rooted before, if it has, you know what happened. If it hasn't, chances are the phone was flagged as lost/stolen after being sold (if 2nd hand).
As for a fix, I found this:
http://forum.gsmhosting.com/vbb/f898/g925f-imei-350000000000006-a-2044425/
Recover corrupt IMEI (without prior EFS backup folder)
Items needed
Root Explorer
Efs folder (no need to have a backup of this prior to the disappearance of IMEI folder, but it has to be this folder on the phone)
Obviously having a rooted phone
Instructions
1- With the Root Explorer to back efs folder to the SD Card
2- For safety make a second copy of the folder to the PC
3- Once both copies made to proceed to erase the original EFS folder on your phone
4 Restart the phone
5- When you start the phone, it will automatically create a new folder EFS, Root Explorer to delete the files and nv_data.bin.md5 nv_data.bin found inside the new EFS folder.
6 Copy the folder from the SAI IMEI folder we saved on the SD card and stick it on the new EFS folder created in the root directory of your phone
7- Since the SAI folder we saved on the SD card .nv_data file copy, paste into the new folder EFS generated in the root directory and rename it nv_data.bin phone, then recopy again .nv_data file rename it nv_data.bin.bak
8- With Root Explorer /efs/nv_data.bin change the owner
9. Restart the phone
If all went well you should have recovered the IMEI can check if recovered by entering * # 06 # on the phone dialer.
Thanks for the response ProdigyThirteen.
The Knox is clean 0x0. Everything I have found says the original IMEI is clean and not flagged.
I will definitely look into the procedure you provided. It looks promising. I'll take any sign of hope I can get.
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Copy the nv_data file from the SD card to the newly generated EFS folder on the phone and name it nv_data.bin. Then make another copy in the same EFS folder and name it nv_data.bin.bak.
Then you need to set the permissions for EFS folder/nv_data.bin file. They need to be set to rw-r-r. However for this procedure you need to be rooted.
Shaggydoo said:
Just tried the recommended procedure but no luck. It is possible that I screwed up steps 7 + 8 because they were not clear to me.
Click to expand...
Click to collapse
Could you tell me did it work?
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Shaggydoo said:
No, unfortunately it did not work. After following all the steps again, the IMEI still comes up incorrect. The search continues ..........
Click to expand...
Click to collapse
Have you tried flashing the stock firmware again? Either by smart switch or odin?
Will try again tonight when I get home.
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Shaggydoo said:
Callumbr1, No dice on the stock flash. I installed Smart Switch and tried to do the reinitialization. It gets along in the process and then fails in the " Device does not have DRK" error. Also have DM-verity error. I tried to find solution briefly but didn't get far. Ran out of time tonight. Will try again tomorrow. Still appreciate your help.
Click to expand...
Click to collapse
I remember I did have the exact DRK error on my s6 edge one and dm verity fail. The way I fixed it was by flashing stock firmware through Odin. Quote me when you try again and I'll do my best to help mate.
IMEI
If you want to get back your IMEI try Dashboard .
you will find all your devices there, then try to find a way to write your IMEI in your phone (may need root)
Dashboard (https://myaccount.google.com/dashboard?hl=en)
Related
Hi, I'm wondering If anyone can help me with a strange issue I'm having with my Vibrant. I unlocked my phone a while back using the method in this forum
http://www.communityhosting.net/sgsunlock/vibrant.html and it worked fine.
Then I installed custom roms, I first had a froyo rom and then most recently used Eugene's Gingerclone. However a couple days ago I went to look at my phone and the APN settings were all jacked up (There was no signal just a cancel sign where the bars used to be). I've went back to the stock 2.1 rom- T959UVJFD using Odin and the service works, however when I upgrade to any other ROM the APN issue remains and I have no network service at all with any rom I've tried. I really don't know what the issue is...if anyone could help I would greatly appreciate it...because I would hate to be stuck with the stock ROM. If you have a paypal account we can work something out. I am using AT&T sim card with T-Mobile Vibrant.Thanks
Hi,
When you go to Settings > About Phone > Status...
Does your IMEI read correctly? Or do you have a generic number that starts with 044xxxxxxx or something like that?
It appears to be a generic 0044 # under the stock rom. Thanks!
Justindawg1506 said:
It appears to be a generic 0044 # under the stock rom. Thanks!
Click to expand...
Click to collapse
No problem. Please download and install Root Explorer (cost money but worth it) and browse to your EFS folder. When you are there post up the files in that directory. This may be correctable as your unlock wasn't fully successful.
EFS Folder
.android
.imei
.nv2.bak
.nv_data.bak
.nv_data.bak.md5
.nv_state
nv
nv_data.bin
nv_data.bin.md5
Justindawg1506 said:
EFS Folder
.android
.imei
.nv2.bak
.nv_data.bak
.nv_data.bak.md5
.nv_state
nv
nv_data.bin
nv_data.bin.md5
Click to expand...
Click to collapse
First, copy the full EFS folder somewhere else on the phone like the Internal SD storage section or to your PC. Now, delete nv_data.bin and nv_data.bin.md5. After those are deleted, copy .nv_data.bak and .nv_data.bak.mdf. After they are copied paste them in the same EFS directory and rename them to nv_data.bin and nv_data.bin.md5. Reboot the phone and let me know if you have your IMEI number back. This may re-lock the phone but atleast you have an intact IMEI number. Then copy the EFS structure in full valid form to somewhere else on the phone or PC and now you can mess up that section as much as you want trying to unlock and you can always restore the good folder and retry. Or if you want to send it to me, I can unlock and maintain a valid IMEI for you...
Nope, IMEI is still the same. The phone only creates a new nv_data.bin file and no nv_data.bin.md5 is created.
I stumbled upon your mobile tech video on Youtube(repairing the IMEI). After watching that, I'm pretty convinced my Vibrant's IMEI is lost forever. I'm just confused because the dates modified on the nv backup files are from last October (before I even tried unlocking or doing anything with the efs folder). I'm probably going to just put this phone on eBay. Thanks again for helping me figure this out.
After 2 days and a lot of head scratching i've managed to finally get my phone back after a random corruption of my /efs folder... heres what i did:
the important part: you need to be able to access /efs with root explorer etc. and check the 2 files; .nv_data.bak & .nv_data.bak.md5
in order for this to work, these backups must be dated earlier than their .bin counterparts... in my instance, the .bins were modified sep 14th 2011 @ 09:45am (the time i rebooted the phone when i noticed i had no signal and the corruption occured), but my .bak files were both dated dec 31st 2010...
in adb shell, i ran
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
i then downloaded 7-zip, used it to open the .tar file
i deleted the corrupt files;
nv_data.bin
nv_data.bin.md5
i then renamed;
.nv_data.bak > nv_data.bin
.nv_data.bak.md5 > nv_data.bin.md5
after closing and saving the changes, i then went back to adb shell and ran
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/efs-backup.tar.gz -C /
reboot
and voila! i was prompted to select my network provider, check status and all my IMEI, IMEI SV and other info was back to normal!
hope this helps someone out there, as i had a hard 2 days trying all sorts of different methods to get this working and was getting to the point of giving up...
good luck
Dickie.
Original post
right, i've been banging my head against the proverbial brick wall all morning over this... this is the score;
This morning i had no signal - 0 bars with a little x from memory
i switched it into flight mode, thinking when i brought it out it might reconnect
when i entered the power menu again, the flight mode button was greyed out (but it said it was switched on), also 'Call' in settings is greyed out, 'flight mode' is UNticked in 'wireless and networks', and trying to enable bluetooth returns an 'In flight mode' message...
reboots, cache/dalvik/full wipes, reflash of rom, flash of stock from odin inc. modem etc all do nothing...
In settings>about phone>status i am missing a lot of info, including phone number, network type and IMEI/IMEI SV...
i can enable wifi, and i downloaded an airplane mode toggle widget, which re-enables 'call' settings, bluetooth, and replaces the aiplane symbol with a circle with a cross through it...
I'm pretty stuck at this point and all i can think is that perhaps the EFS has become corrupt... anyone got any ideas?? all suggestions appreciated... in the mean time i'm going to look into the EFS stuff which i have no idea about yet lol
cheers,
Dickie.
Click to expand...
Click to collapse
yes you have corrupted /wiped your EFS or IMEI ,
If you backed up your EFS its not a problem just restore .
Plenty of restore EFS posts around broken IMEI etc .
jje
I'm looking in the EFS folder now, all seems to be present, but i am missing my IMEI (*#06#)...
not sure how this has happened, not done anything recently... very strange... but it does seem to be specifically the IMEI as my macs etc all all there and ok...
not backed it up so i'll see if theres a way around it :/
Cheers,
Dickie.
This happened to me 3 days back. Was sure I needed to send it in for service (reflashed and everything without avail) but then someone mentioned the EFS folder corruption issue.
Thankfully, I bumped into Rawat's thread a few weeks prior, and promptly backed up my EFS then.
It only took about 3 minutes in the terminal to fix the problem afterwards, no pc needed.
No EFS backup would usually mean a trip to Samsung service.
I got the same problem sice yesterday... tried all with the help of some guys here but nothing helped!
@eiraku: Do you like to explain me how you fixed the issue in the terminal, because my was /efs folder was also backed up but overwriting doesn't helped
ive just realised, my nv_data.bin & nv_data.bin.md5 have todays date in root explorer, i'm guessing thats a last modified date and that happend during the time in f*cked up, but the nv_data.bak & nv_data.bak.md5 are dated 31 dec 2010...
does this mean all i have to do is rename those backups and all should be sweet???
cheers,
Dickie.
dickie2007 said:
ive just realised, my nv_data.bin & nv_data.bin.md5 have todays date in root explorer, i'm guessing thats a last modified date and that happend during the time in f*cked up, but the nv_data.bak & nv_data.bak.md5 are dated 31 dec 2010...
does this mean all i have to do is rename those backups and all should be sweet???
cheers,
Dickie.
Click to expand...
Click to collapse
Sounds hopeful.
I'd suggest you take a copy of those backups & put them on an external device before renaming anything.
i took 2 backups of the entire /efs folder, then renamed the bak files to bin, but i'm having trouble copying or pushing them to /efs...
anyone know how to mount it as r/w, i cant through root explorer and not sure via adb
any help appreciated...
Dickie.
---------- Post added at 06:24 PM ---------- Previous post was at 05:40 PM ----------
ok, i have tried the following:
busybox umount /efs
busybox mount -o rw -t ext4 /dev/block/mmcblk0p1 /efs
busybox mv /efs/.nv_data.bak /efs/nv_data.bin
busybox mv /efs/.nv_data.bak.md5 /efs/nv_data.bin.md5
then when i check with root explorer all appears correct with the baks gone and the bins dated 31 dec, but upon rebooting its all gone back to the way it was before...
again, anyone got any ideas??
Dickie
Did you found a solution? I'm thinking about going to a service center
i'm trying to work out how to get the damn /efs folder to remain r/w...
everytime i change the files, moments later its reverted to what it was...
just trying a different insecure kernel to see if that helps... even sometimes whilst i'm deleting/renaming the files it suddenly becomes read only again...
really wish someone who knew how to make either an update.zip or an Odin flashable tar could do so with my renamed .bak backup files to overwrite the original bin files...
Dickie
happened to me but the problem solved in a couple of hour without doing nothing
tried making an update.zip but i get a status 6 error... stuck again...
could anyone take a look at this for me?? ive been on this almost 18hours and im tired and need to sleep...
again, any help appreciated!
Dickie
This happened to me whenever my phone restarted after cleaning the battery stats with Battery Calibration app (by NEMA) from App Market. At first, I restored my nv_data.bin file that was backed up (efs backup), but it continued to have same problems for next few reboots...
BUT!
I believe I have a possible simple remedy for this problem:
1. Turn off phone.
2. Remove SIM.
3. Turn on phone.
4. Wait until phone fully boots. (my phone did not detect SIM card and had emergency mode available, showed normal information in About Phone options)
5. Turn off phone.
6. Re-insert SIM.
7. Turn on phone.
nk_blu said:
This happened to me whenever my phone restarted after cleaning the battery stats with Battery Calibration app (by NEMA) from App Market. At first, I restored my nv_data.bin file that was backed up (efs backup), but it continued to have same problems for next few reboots...
BUT!
I believe I have a possible simple remedy for this problem:
1. Turn off phone.
2. Remove SIM.
3. Turn on phone.
4. Wait until phone fully boots. (my phone did not detect SIM card and had emergency mode available, showed normal information in About Phone options)
5. Turn off phone.
6. Re-insert SIM.
7. Turn on phone.
Click to expand...
Click to collapse
thanks for the input but it made no difference...
i now what i need to do, i need to replace those bin files with the bak backup files... i just cant get it to stick after a reboot... its like i never did it...
cheers anyway bud
Dickie
http://forum.xda-developers.com/showthread.php?t=859914
Don't get rid of this ****ing efs corruption !!!
red103 said:
Don't get rid of this ****ing efs corruption !!!
Click to expand...
Click to collapse
using root explorer, look in /efs.
is there a difference in the dates between nv_data.bin and .nv_data.bak??
Dickie
It works !!!!!!!!!!
Thanks a lots dickie2007 !
Yesterday i updated kernel on Revo 2.7.1 via KitchenPro app (for infos from CFROOT_KI3.zip to CFROOT_KI3_v4_2.zip) everything seem fine but this morning no imei, no baseband...
I search a lot before finding your thread (i think this one should be sticky !)
Your procedure is clear & simple (and hoppefully work in my case).
Thanks again dickie2007
PS : It seem since the serie KI* there's a lot of similar problems (i saw many thread during my research this morning about this kind of trouble)
If u flash different carrier branded firmware in CSC & do not set it correctly,
u may find that u can't see ur IMEI via *#06#.
Don't worry. It is still there. This is my way to solve it.
(just several seconds and without efs backup)
1.edit carrier branded code in "/efs/imei/mps_code.dat" to meet what you flash.
Ex. My S2 is CWT in the beginning, so I flash a CWT CSC and edit the code to CWT
2.use *#06# to ensure if IMEI could be shown correctly
3.To double check, u can use *#272*imei#. If u can reset carrier branded code then it is done.
nokia8250 said:
If u flash different carrier branded firmware in CSC & do not set it correctly,
u may find that u can't see ur IMEI via *#06#.
Don't worry. It is still there. This is my way to solve it.
(just several seconds and without efs backup)
1.edit carrier branded code in "/efs/imei/mps_code.dat" to meet what you flash.
Ex. My S2 is CWT in the beginning, so I flash a CWT CSC and edit the code to CWT
2.use *#06# to ensure if IMEI could be shown correctly
3.To double check, u can use *#272*imei#. If u can reset carrier branded code then it is done.
Click to expand...
Click to collapse
Does this also work even if baseband is shown as unknown? I flashed a stock ROM with Odin and lost both baseband and IMEI. dickie2007's method didn't work but maybe yours would have...
I been playing with my phone for a few days now trying to get it to work and I haven't had much success although I have been learning a hole bunch and now able to load any rom onto my phone easily and flash kernels and such with ease...
The situation is that I received a phone from a friend SGSII I have never had a rooted phone and it came pre rooted, never knew much about it as it is my first Android phone and now love it
never knowing I had to do these things like "backup EFS directory" and such as I know now... anyhow, a few days ago what has happened is I have a stock rom + CF-Root and my phone all a sudden started telling me there is no IMEI and no SIM card present.. after much research, flashing of roms, kernels, bricking the phone, re flashing and so on and so foth....... xda-developers is a FANTASTICK site full of useful information btw now I'm still at the same point but a lot more knowledgeable, I have learned that the problem lies with my efs folder and have found a .nv_data.bak file that is dated dec 31 of last year, at this point it is my only so called backup and hope that it will restore proper functions of the phone, as per some of the guides and other posts and questions I have learned to do this.. so what I have done was copy using ADB my files to my sdcard folder renamed my nv_data.bin to nv_data.bak and my .nv_data.bak to nv_data.bin
also I have used root explorer to copy the hole efs folder to a location on my external sd card and used HC-kTool to make a backup of my efs folder
now I have been trying to use the command to copy my nv_data.bin file in the sdcard folder to my efs folder and it is not working as it gives me msges of write protected file or file exist canot copy... the commands I have been trying to use are
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/
I have tried also
rm command to remove the file but nothing has been working...
one thing I should mention is that I have been connecting withough usb cable as I can't seem to connect with that I keep getting device not found so I been using the wireless adb function
abd connect "ip addressort"
I have tried installing the kies driver for usb and the google sdk drivers and none seem to work, in fact kies doesn't reconize my phone aswell... but Odin seems to function through my USB just fine.... not sure if that matters or not but trying to give as much info as possible
Thank you in advance for the help.... this is a great site with very knowledgeable ppl
permissions have to be reset as the back up does not copy the permissions. Use cwm recovery to reset the permissions.
Thank you very much for you quick response, however I have just tried that, booted into cwm recovery, went to advanced and reset permissions, rebooted my hone and still cannot copy the file
Try using a Root Explorer from the market.Connect via wifi obviously if your phone cant detect sim.Phone needs to be rooted.Give Root Explorer root permission and set to R/W from R/O and copy paste the nv.data files and IMEI to the efs folder in the root of your phone,reboot,boot to recovery and "fix permissions" and boot again.
sorry I guess I should of mentioned that aswell but thank you very much for the suggestion... I have tried to edit the file weather just delet it or overwrite or change permissions with Root Explorer and to no success.. also when I push the mount r/w button in the efs folder... nothing happens and the button stays as mount r/w
I found this.Maybe it will help.
http://forum.xda-developers.com/showthread.php?t=1258734
http://forum.xda-developers.com/showthread.php?t=1261948
http://forum.xda-developers.com/showthread.php?t=1085374
and if you manage to get it back then use this:
http://forum.xda-developers.com/showthread.php?t=1308546
Thank, I havent had time to read through them all but I will try tonight and see if I can come up with a solution... I will post here my findings weather they are good or bad..... but thank you very much for the info
I have read and tried and seen all those post, thankyou for the info the problem is still that I cannot modify my nv_data.bin file in any way... I cannot overwrite to it or anything using rootexplorer or adb or any other program... does anyone know of any other programs or command lines to strip the read only permissions on this file as it seems stuck on this and it's driving me insane lol
Gave up
I gave up and had it done professionally, they couldn't figure it out either and had to replace the phone.... Thank you all for the great help, even tho we didn't get it figured out it was great that help was provided
Thank you XDA-Developers your awesome!!
ive the same issue,got a rooted s2 with cwm all the forums cay copy the efe data but i cant find a way,anyone know how to do it?,i need to eddit it to unlock my phone:ie the simlock.
thanks
thank you for sharing your ideas
My s3 stopped recognizing the Sim yesterday, so i searched for a solution. i read in xda that its the EFS partition. I got no IMEI and no Baseband. Somehow i found 2 files on the internal SD Card: "efsbackup.tar" and "efsdev-mmcblk0p3.img".
I read this thread, but it didnt help me.
Any idea how i could fix it?
Btw, Android Revolution HD 11.0 with stock kernel
I'm guessing your Rom auto backs up the efs, so best to ask on their thread about reinstalling it
Restore your EFS backup .
jje
im going to install now arhd 11.3 and then do the restore of the efs backup.
i noticed that the backup was built yesterday evening, when the problem already was. well it seems like i got no backup, when it was working
I followed in this thread this post:
Process:
1. make a copy of your EFS folder using root explorer and store it somewhere safe (on your SD card and external SD card should do it).
2. delete the EFS folder from the root of your phone using root explorer.
3. reboot the phone
4. open root explorer and go to the EFS folder (yes, it is still there! The Android OS has generated a new one for us) and delete the following files:
nv_data.bin
nv_data.bin.md5
nv.log
.nv_data.bak
.nv_data.bak.md5
nv_data.bin.bak
and the entire IMEI folder.
5.Now go to your backed up EFS folder on your sd card and copy the IMEI folder and the " .nv_data" file (note the dot) to your new EFS folder.
6.Make another copy of the ".nv_data" file in your new EFS folder. Rename one of them to "nv_data.bin" and the other one to "nv_data.bin.bak".
7. Connect your phone to your PC and start up EFS PRO. After your phone has been detected, press the "Repair nv data" button to correct the ownership and permissions.
8. Reboot your phone into recovery mode using the three botton combo and flash the original modem firmware (the modem.bin file that you extracted earlier) to your phone using Odin (use the "phone" button for the upload) or Heimdall (use the "radio" partition for the modem.bin file upload).
9. Reboot the phone normally and your IMEI number will be restored and you will be able to connect to your mobile network again
Click to expand...
Click to collapse
and now i got an IMEI, but its still not mine: 004999010640000 / 01
If you have an efs.tar file why dont you put it in PDA in Odin?.
wont work.
deleted
Ok....then I dont understand why it backs up as a tar file then
yesterday i flashed siyah kernel, siyah probably made a efs backup. but that backup was already after that problem happened.
well i got now the 0049 imei
So you dont have a back up of you original IMEI is that what your saying?.Flashing ROMs normally is what makes a backup not flashing a kernel so Id say the backup is original.
Read this
http://forum.xda-developers.com/showthread.php?p=30682712
i read this but i dont know what to do with it. i understand that this are options to backup the efs partitions but not how to restore it how to restore it if already lost
x Schieby said:
i read this but i dont know what to do with it. i understand that this are options to backup the efs partitions but not how to restore it how to restore it if already lost
Click to expand...
Click to collapse
you need to read better then
You'll need to perform an "IMEI injection" which is a kludgy last-resort restore method that manually writes the IMEI to NVRAM; the link I provided in Part C of "Backup" will tell you how to do it.
x Schieby said:
My s3 stopped recognizing the Sim yesterday, so i searched for a solution. i read in xda that its the EFS partition. I got no IMEI and no Baseband. Somehow i found 2 files on the internal SD Card: "efsbackup.tar" and "efsdev-mmcblk0p3.img".
I read this thread, but it didnt help me.
Any idea how i could fix it?
Click to expand...
Click to collapse
That's what the efs backup is for xD
Calm down, or you'll make things worse. Unzip the efs.tar to /efs and reboot your phone (DON'T PULL THE BATTERY)
Everything should work like a charm again
Hope I could help!
LG familyguy59/Beatsleigher
slaphead20 said:
you need to read better then
You'll need to perform an "IMEI injection" which is a kludgy last-resort restore method that manually writes the IMEI to NVRAM; the link I provided in Part C of "Backup" will tell you how to do it.
Click to expand...
Click to collapse
sorry, but i still dont get it with the qpst. thats the part c you are thinking of right?
familyguy59 said:
That's what the efs backup is for xD
Calm down, or you'll make things worse. Unzip the efs.tar to /efs and reboot your phone (DON'T PULL THE BATTERY)
Everything should work like a charm again
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
going to try this now
familyguy59 said:
That's what the efs backup is for xD
Calm down, or you'll make things worse. Unzip the efs.tar to /efs and reboot your phone (DON'T PULL THE BATTERY)
Everything should work like a charm again
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
well, thats how my phone ended. i did that yesterday and my phone finally didnt even booted.
then i went to my carriers shop and told them it wont boot, and today i got a brand new phone
anyway thanks to all help!
Hi. i cant understand the sticky threads at all. i have read it 1000 times.
Lost the signal after flashed Imperium ROM.
I believe i can recover that by restore a cwm backup i did some time ago ?
BUT i have formated the internal phone and no restore files are located. I have it on PC but
have not been able to copy the backup folder to the phone so that CWM can find it ??
And the stickys makes no sense to me..
Damn it.
Just knew i was going the wrong way in Imperium AROMA installer .. :/
Any help plz ?
I have found a way in the forums to find the files in CWM...
/data/media/clockworkmod/backup..... I put them there and i could find the recovery file.
But i just glanced somewhere that i wont restore them modem . :/
Anyway its restoreing, and i hope it works.
If you made a full nandroid then it will restore your modem, but not your efs folder - which is responsible for most no network issues.
You'll have to read through the stickies, particularly the 'before you root' and 'imei know this stuff' ones. I'm not going to type it all out for you.
Follow the instructions to flash a stock ROM with an EMG4 baseband, which solves many efs issues. If it doesn't then you'll need to pay for a repair, about £20.
just realised its bricked.
i have a copy of efs folder on pc but not sure what to do.
EFS Proffesional cant find a backkup in restore tab, even though i believe i did make one.
In my efs folder are.
bluetooth
drm
factoryapp
emei
wifi
and 7 files.
can i copy and paste something to the phone to make it work ?
Yes , copy those backed up efs folder files to your phone's efs folder and reboot. It should work.
sent from the state where marijuanated muffins are NOT illegal !
I would recommend using ADB as copy doesn't retain the required permissions.
Full step-by-step adb guide for this in my IMEI / EFS thread
rootSU said:
I would recommend using ADB as copy doesn't retain the required permissions.
Full step-by-step adb guide for this in my IMEI / EFS thread
Click to expand...
Click to collapse
I use root explorer to copy paste and it did retain permissions but yeah to be on safer side using bridge is more preferable
sent from the state where marijuanated muffins are NOT illegal !
kangerX said:
I use root explorer to copy paste and it did retain permissions but yeah to be on safer side using bridge is more preferable
sent from the state where marijuanated muffins are NOT illegal !
Click to expand...
Click to collapse
Yes root explorer may be better than other file managers with root permissions to be fair. But most people think root exploring is a simple thing that can eb done by any free app
hi and thank you.
I was not able to copy efs folder to phone, or to say, i managed to copy it via Es file explore to the root efs.
But phone ended up with Factory error, so now i have the screen thing on the phone.
I tried to type the guide from root SU in Terminal with no luck, nothing worked or would be regonized, sadly.
I read somewhere that i stock rom might solve the things, so thats where im going now.
I have removed binary counter to 0, and it says im on stock firmware and recovery.
I have installed stock recovery.
BUT im stuck at finding my STOCK ROM.
Im using THIS guide......
http://forum.xda-developers.com/showthread.php?t=2323847
AP: I9300XXEMG4
CP: Unknown
CSC: I9300NEEEMG2
As far as i can read i shall find I9300NEEEMG2 on this page.....
http://samsung-updates.com/device/?id=GT-I9300
But its not there, there are many I9300XEMG4 ?.
I have tried installing KIES, to find my firmware/model. But it wont find my phone.
Im stuck at those 1000 stock roms.
Help plz.
sup3rbuck said:
I was not able to copy efs folder to phone, or to say, i managed to copy it via Es file explore to the root efs.
But phone ended up with Factory error, so now i have the screen thing on the phone.
Click to expand...
Click to collapse
This is because you did not follow suggestions. ES will not do the trick because it will not retain permissions. ADB was your option, or perhaps root explorer.
I did try this page http://developer.android.com/tools/index.html and downloaded SDK pack.
Its pure madness to me, and i was unable to find something that looked like a file browser.
Root explore i did look at, but it did cost some money. And maybe it wont work !
sup3rbuck said:
I did try this page http://developer.android.com/tools/index.html and downloaded SDK pack.
Its pure madness to me, and i was unable to find something that looked like a file browser.
Root explore i did look at, but it did cost some money. And maybe it wont work !
Click to expand...
Click to collapse
FX Explorer and Root add on is free .
Service centre repair is relatively cheap .
I have paid 5$ a month in some insurance, so last resort is i smash it with a hammer so they wont be able to connect it to a computer.
And get a new one. But i wanna learn this stuff for the future.
I tryed fx explore, and the Factory mode has gone now. But still no network, and eimei says null/null ?
sup3rbuck said:
I have paid 5$ a month in some insurance, so last resort is i smash it with a hammer so they wont be able to connect it to a computer.
Fraud and theft is not allowed on XDA .
Click to expand...
Click to collapse
Sure no problem.
as a Blacksmith, stuff might happens when sheit hits the fan.
Thanks for all you answers.
I have fixed my phone with a stock firmware install. :highfive: