Related
Hi all, I have messed up my Galaxy Tab GT-P1000 (Aus-Optus-CDMA) trying to flash. I managed to get it going on the following FROYO.XXJME Version 2.2 Kernel 2.6.32.9 rootatSEI-28 #1
Unfortunately I did not do a full backup!
My problem is now,
1/ No imei shown
2/ No serial number shown
3/ Not recognize my sim card
4/ Tab reboots regularly
Have done the factory reset however I am not sure if due to my flashing is it the original rom?
I have the imei written but cannot get the Tab to find it, thus cannot connect to Kies to get the samsung updates which would fix things, "I think".
Can anyone help
Thanks
DanTanBjAj said:
Hi all, I have messed up my Galaxy Tab GT-P1000 (Aus-Optus-CDMA) trying to flash. I managed to get it going on the following FROYO.XXJME Version 2.2 Kernel 2.6.32.9 rootatSEI-28 #1
Unfortunately I did not do a full backup!
My problem is now,
1/ No imei shown
2/ No serial number shown
3/ Not recognize my sim card
4/ Tab reboots regularly
Have done the factory reset however I am not sure if due to my flashing is it the original rom?
I have the imei written but cannot get the Tab to find it, thus cannot connect to Kies to get the samsung updates which would fix things, "I think".
Can anyone help
Thanks
Click to expand...
Click to collapse
Did you flash with ODIN?
Did you get an error message?
Have you tried re-flashing to a stock ROM?
You should read through the following thread before flashing anything else
http://forum.xda-developers.com/showthread.php?t=888071&highlight=no+imei+after+flash
And you are correct in assuming that a factory reset would only re flash the ROM you "replaced" your stock ROM with.
Also remember that using the SEARCH button usually will get you a lot more answers than just waiting on a reply here.
Did you unlock the tab first, no network lock, no sim lock... If you didn't this may explain whats happened. Don't know how you're gonna fix though....
Your Gtab is also NOT a CDMA tab, its GSM as you use a sim card... You may have bricked it if you flashed a CDMA rom.... Lucky if it starts up at all...
You need to tell us more info, what rom you flashed, how you flashed it - ODIN, Heimdall , Kies or just by pure magic. Then you might get more help....
the /efs folder contains all information/numbers about your gt including IME, mac address, bluetooth,etc.. It may have been deleted yet there should be a bak file inside the folder. since you are able to boot as you mentioned then you can still go into download mode and reflash a ROM?
Hi "theREDlegion" & thanks for your time.
Yes I did flash with Odin.
I got a red FAIL in Odin & an error message, trying to remember what it said exactly.
I am not sure which is the correct ROM to use for me here in Australia, CSC file & Pit etc, I'm kinda new to this stuff.......as you guessed!
I rooted the Tab with z4root, then used the repair nv_data to unlock the network which was succesful, so it said by entering the code.
So will the "Gingerbread" ROM work on my Tab?
I tried P1000XXJQ1_P1000XXJQ1_P1000XXJPZ_HOME.tar which failed.
Thanks again.
Hi ultramag69, appreciate your help.
I was installing a game when my Tab froze. No matter what I did I could not get it to respond. This is why I thought lets try & install Gingerbread. I managed to get it connected to the PC, however I am not sure if I did as you said "sim unlock". I did the network unlock. My Tab runs okay now but will loop boot when idol for 30 sec. I still whish to do Gingerbread if it is possible, or "overcome"
Thanks again.
Hi bongski55, thanks for your assisstance.
I have the backup of the efs & the files in it are dated 27/10/2010 which would indicate they are the originals. I have replaced the new efs files with these but still no change.
Not sure which file is the imei info though.
Here is my plan,
1/ Do factory reset - this will allow me to reroot
2/ Root the Tab & unlock network, learn how to unlock sim?
3/ Remove SD & SIM cards.
4/ Use Odin to flash with Gingerbread, I think I have the right ROM!
Wot u think!!!!!!!!!
Is your bootloader safe? Do you know what your original firmware version was ?
edit for my english: is "was" at the good place in the second sentence?
You've tried chainfire's safe rom, have you checked out the overcome thread, there's a safe rom you can install through ODIN there too... Might work. Also, do a search for Telstra rom, might take back to stock Froyo but with all the Telstra bloatware, I started on this.
After you take back to Froyo stock you can try again for GB. Can't say if this will work though as you have an Optus tab, mine was Telstra from the start...
Good luck...
Without restoring the efs folder CORRECTLY. All your efforts are futile. Follow this thread to restore /efs folder: http://forum.xda-developers.com/showthread.php?t=859914. Reboot your phone, Charge it and try flashing a stock ROM.
Some very helpful information has been posted here, thanks to the very helpful members of xda.
If I was in your shoes I would do the following:
1) Follow the link provided by DarkPal in post 10, complete the steps necessary to restore the efs folder.
2) Follow the link I provided in post 2 and confirm your bootloaders and take necessary actions to patch if necessary.
3) Your device (on Optus) should be WCDMA/GSM. I would go over the OVERCOME thread and follow instructions on flashing a stock safe rom and attempt to flash the OVERCOME rom. It is important to follow the instructions step by step for a successful flash. The OVERCOME guide is very detailed, if you follow it correctly you should not have any issues with the flash.
Do post back your results and good luck.
DarkPal said:
Without restoring the efs folder CORRECTLY. All your efforts are futile. Follow this thread to restore /efs folder: http://forum.xda-developers.com/showthread.php?t=859914. Reboot your phone, Charge it and try flashing a stock ROM.
Click to expand...
Click to collapse
Thanks for your help so far,
I have been able to find the backup of my efs/ which was created during unlock process.
Thank god.........I have now done this, patched bootloader.
1/ Used Overcome safe rom & flashed
2/ Flashed to Overcome "Jupiter" v3.3.0 & changed file system to ext4
3/ restored efs/
4/ My imei is now back to original....Yippee....also is my serial number.
Now when I boot it gives me full bars of service & Yes Optus on the screen..Great!
But I still canNOT connect. My Wifi works fine.
I notice my IMEI SV is now 05 but was originally 01.
I am not sure how to see what csc I have & don't know if it matters?
Any suggestions....
Cheers
Google "optus apn settings" and check yours (settings, wireless network, apn).
Check if wireless mode is auto.
What is your baseband (modem version)?
Because you see optus on your screen, your voice service is fine, but no data connection means your apn values are incorrect or missing.
theREDlegion said:
Some very helpful information has been posted here, thanks to the very helpful members of xda.
If I was in your shoes I would do the following:
1) Follow the link provided by DarkPal in post 10, complete the steps necessary to restore the efs folder.
2) Follow the link I provided in post 2 and confirm your bootloaders and take necessary actions to patch if necessary.
3) Your device (on Optus) should be WCDMA/GSM. I would go over the OVERCOME thread and follow instructions on flashing a stock safe rom and attempt to flash the OVERCOME rom. It is important to follow the instructions step by step for a successful flash. The OVERCOME guide is very detailed, if you follow it correctly you should not have any issues with the flash.
Do post back your results and good luck.
Click to expand...
Click to collapse
Good morning all, well I would like to thank everyone on this forum, particularly those who have promptly responded to my questions.
I am glad to say that after 3 days of stress I have finally got my Galaxy Tab back on the Optus Australia internet service, I had to change the APN from Optus (Internet) to Optus (connectcap) in the Access Point Names & also at the bottom of those settings I had to select Internet. The connectcap option is not there by default, you have to add a new APN & choose these settings. My sim card is a data plan only.
So I now have my Tab running Overcome Jupiter, thanks guys, love your work, on the ext4 file system and already it is noticably faster.
Now......probably a good time to do a proper backup......yep I'm learning!
So thanks again everyone.
- SOLVED! Flashed a different ICS Rom along with Semaphore kernel and everything works again!
Hey all!
I have a BIG problem... Yesterday I flashed SlimICS 2.9 on my friend's Galaxy S device through CWM. Installation went fine and system booted up OK. I quickly noticed that there was no mobile network available and I went to check the IMEI as I was suspecting the worst. The IMEI showed up as blank on the phone...
I checked the /efs folder and all the files were present (nv_data.bin and such). I also noticed that there was a /efs backup on the internal sdcard. I tried overwriting the files from the backup to the /efs folder on the root to no avail. Upon deleting the /efs folder or any files in the folder, they are automatically placed back. Why does that happen?
I cannot use the phone's usb port since it's broken.. so all has to be done from within the phone. (External sdcard still functions, ofcourse).
Spent a lot of hours searching and reading - I'm desperate!
Robin2 said:
Hey all!
I have a BIG problem... Yesterday I flashed SlimICS 2.9 on my friend's Galaxy S device through CWM. Installation went fine and system booted up OK. I quickly noticed that there was no mobile network available and I went to check the IMEI as I was suspecting the worst. The IMEI showed up as blank on the phone...
I checked the /efs folder and all the files were present (nv_data.bin and such). I also noticed that there was a /efs backup on the internal sdcard. I tried overwriting the files from the backup to the /efs folder on the root to no avail. Upon deleting the /efs folder or any files in the folder, they are automatically placed back. Why does that happen?
I cannot use the phone's usb port since it's broken.. so all has to be done from within the phone. (External sdcard still functions, ofcourse).
Spent a lot of hours searching and reading - I'm desperate! Therefore I'll happily reward the person who can help me out with $15! I know it's not much, but I cannot spare much money at this moment..
Click to expand...
Click to collapse
There is an app "Mobile Odin" .. us this to flash stock firmware on your friend's phone.. I haven't used this app myself but it should work.. you can download the stock firmware from sammobile.com .. once you flash the stock firmware your IMEI number should be restored... then you can try flashing rom once again
PS: Please don't offer money like this.. donating to the developers of Roms and apps is enough.. they are the ones doing the main stuff..
Didn't know that Mobile Odin existed! Seems like a great program.. I installed it and upon opening it tells me that ''A compatible device was detected, but with unexpected partition layout. Mobile ODIN cannot operate. This is a common error on CM and MIUI ROMs on some devices.''
What ROM would I flash through CWM to get this app to work for me? Is Mobile ODIN incompatible with ICS?
UPDATE:
I flashed a different ICS Rom, Codename 1.5.6, and now the IMEI shows up when dialing *#06#! I was also able to unlock the SIM!
EDIT:
I was able to call! However Data connection does not work! Even with the right APN settings... Would this be caused by the firmware?
dont worry,i had the same bug.you have to flash another kernel,Glitch,or Semaphore for example...then you will get data connection
Lawrrer said:
dont worry,i had the same bug.you have to flash another kernel,Glitch,or Semaphore for example...then you will get data connection
Click to expand...
Click to collapse
Yes this is what worked for me. Figured this out like 5 mins before you posted.
Thanks for the reply, though!
Sorry, wrong place
So, just a heads up guys (and gals); it looks like ATT blocked my device (reported it stolen) and now I'm locked out of the wireless network.
I still need to call them to see if I can resolve this issue, but it happened after I flashed the latest nightly CM10 and was running it all weekend with no problems, wake up this morning and I can't text, get no data. Try making a call and it states; "This device has been blocked". After using Google, that message is one that happens when a device is reported stolen.
Since I've had this device for it's entire life, there is no chance someone else reported it stolen.
I'll keep this thread updated with what ATT does, if they re-enable my device, etc.
Somebody else had this happen to them on CM10, and it was because their IMEI became generic overnight. You can read about it in the Helly Bean thread.
korockinout13 said:
Somebody else had this happen to them on CM10, and it was because their IMEI became generic overnight. You can read about it in the Helly Bean thread.
Click to expand...
Click to collapse
Huh. How does it overwrite the IMEI on it's own?
I did have a backup of my IMEI from last october (the entire EFS folder) I used ES File explorer to copy it over... But forgot to fix permissions... SLAP forehead.
(Fixed Permissions)
Now I'm back on ATT, guess it wasn't there fault.
:cyclops:
So after reading the other thread, I have to wonder if changing /System to RO mode (via SGS Toolbox) will prevent the EFS folder from being overwritten again? Or am I going to run into this again? The problem seems pretty clear, the EFS folder for some reason has R/W privileges, when it should be RO.
The second part of the equation, is _what_ in JB is deleting that folder?
scythekain said:
So, just a heads up guys (and gals); it looks like ATT blocked my device (reported it stolen) and now I'm locked out of the wireless network.
I still need to call them to see if I can resolve this issue, but it happened after I flashed the latest nightly CM10 and was running it all weekend with no problems, wake up this morning and I can't text, get no data. Try making a call and it states; "This device has been blocked". After using Google, that message is one that happens when a device is reported stolen.
Since I've had this device for it's entire life, there is no chance someone else reported it stolen.
I'll keep this thread updated with what ATT does, if they re-enable my device, etc.
Click to expand...
Click to collapse
This same exact thing happened to me, but I'm on CM9 Stable... Still trying to figure out why my IMEI is the generic one...
I had this happen to me also,,and when I called att customer service they told me that the emei belonged to an iphone that was stolen,,in my case this actually happened three times,,I finally flashed back to stock to reset the emei and it seems to be holding,, I was running helly bean v24 and had been on the rom for a day or something ( well since that version came out ) in fact I have two captivate handsets and one was on v23 and they both switched the emei to the same one,,I have no idea what caused the emei to change but it sure caused some hair pulling on my part lol,, all seems well now
wilson735 said:
This same exact thing happened to me, but I'm on CM9 Stable... Still trying to figure out why my IMEI is the generic one...
Click to expand...
Click to collapse
Same here, but on CM 7.2.0 RC2. I'm not sure if the IMEI just now changed or if it was this way since I flashed CM and AT&T is now cracking down.
The above posts, kind of confirm what I'm sensing is ATT doing something that flashed a stolen IMEI onto rooted android devices.
1) What was the timing of your problem? - For me this happened yesterday morning, or Sunday night after 9 PM PST. I restored my IMEI about 9 AM, and the service restored itself around 13:32 8/20/2012 PST
2) It makes me wonder IS this the custom ROM that changed the IMEI to a stolen iPhone? Why would the ROM choose an iPHONE IMEI? I think this was pushed by ATT. Was it a mistake or was it intentional? Proof? CM 7.2, CM9, CM10 and HellyBean (which is based on CM10 with custom kernel, partitioning). ALL of them set the IMEI to the stolen iPhone THIS last weekend though?
For those of you still needing to restore your IMEI and you don't have a backup, use this thread;
http://forum.xda-developers.com/showthread.php?t=881162
EDIT:
You can also flash back to stock via ODIN to restore your IMEI.
So it looks like the CM10 flash I did Saturday did muck up my IMEI. I was logging into the Google Play store to try and restore my apps from the web, and found out I have two captivates registered.
One with the correct IMEI, the other with this bogus IMEI:
IMEI: **********640000
Here's the whole story:
On Sunday, in the course of 5 hours: 3 times AT&T blocked my device, I called them and got in unblocked. In one of those times, the guy says that the system logs say that my sim card was in an iPhone 3gs that was reported stolen. They also credit me with $25 for each of the 1st 2 times I called.
Anyway, on the 3rd time I ask to speak to a floor supervisor. She is able to tell me that because my phone is reporting an IMEI of a stolen phone, she'll forward it to the Stolen Devices team/department, and that they would get back to me on Tuesday. She can unblock it again on the spot, but eventually it'll get read by the system and blocked again.
I confirm with her that the IMEI that my phone software is showing is the Generic one (004999010640000), and not my actual one that I read to her from underneath the battery.
I was reading through the forums all day on Monday and came to the following conclusions:
1) That Generic IMEI may be what a ROM is mistakenly putting in place, it must use this as a failsafe of some sort, so it can have an IMEI, any IMEI. In reality it should be reading the hardware's IMEI.
2) Our IMEI's did not necessarily get changed this weekend. Last time I flashed, it was when CM9 Stable was released, and that was a couple of weeks ago. So, we may have had this IMEI for weeks, if not months. I know I may have. 1 month ago, my phone got blocked. They said that someone reported it stolen. I called, got my $25 credit, and the service reinstated. I may have had that Generic IMEI at the time.
Last night a technician from the Stolen Devices team instructed me to remove my SIM card from the device for 24 hours so that the network can refresh the IMEI (his exact words, I don't know exactly how the network works, but...) and that this was necessary. Yes, I could ignore him and put by SIM card back into my Captivate, but eventually it would get blocked again. So leave it out of the Cappy, he said, use it in any other device, and after 24 hours you can slip it back in. He said that recently (in the past day or two), many users had been calling about the same problem.
Anyway, just to be on the safe side, I'll be following fohdeesha's instructions here:
http://forum.xda-developers.com/showpost.php?p=30563493&postcount=1780
Flashing back to stock 2.3.5, and seeing if I can get the correct IMEI. If so, I'll backup that EFS folder in 10 different places, revert back to ICS or JB, and if the IMEI is messed up there, I'll restore my EFS backup.
wilson735 said:
Here's the whole story:
On Sunday, in the course of 5 hours: 3 times AT&T blocked my device, I called them and got in unblocked. In one of those times, the guy says that the system logs say that my sim card was in an iPhone 3gs that was reported stolen. They also credit me with $25 for each of the 1st 2 times I called.
Anyway, on the 3rd time I ask to speak to a floor supervisor. She is able to tell me that because my phone is reporting an IMEI of a stolen phone, she'll forward it to the Stolen Devices team/department, and that they would get back to me on Tuesday. She can unblock it again on the spot, but eventually it'll get read by the system and blocked again.
I confirm with her that the IMEI that my phone software is showing is the Generic one (004999010640000), and not my actual one that I read to her from underneath the battery.
I was reading through the forums all day on Monday and came to the following conclusions:
1) That Generic IMEI may be what a ROM is mistakenly putting in place, it must use this as a failsafe of some sort, so it can have an IMEI, any IMEI. In reality it should be reading the hardware's IMEI.
2) Our IMEI's did not necessarily get changed this weekend. Last time I flashed, it was when CM9 Stable was released, and that was a couple of weeks ago. So, we may have had this IMEI for weeks, if not months. I know I may have. 1 month ago, my phone got blocked. They said that someone reported it stolen. I called, got my $25 credit, and the service reinstated. I may have had that Generic IMEI at the time.
Last night a technician from the Stolen Devices team instructed me to remove my SIM card from the device for 24 hours so that the network can refresh the IMEI (his exact words, I don't know exactly how the network works, but...) and that this was necessary. Yes, I could ignore him and put by SIM card back into my Captivate, but eventually it would get blocked again. So leave it out of the Cappy, he said, use it in any other device, and after 24 hours you can slip it back in. He said that recently (in the past day or two), many users had been calling about the same problem.
Anyway, just to be on the safe side, I'll be following fohdeesha's instructions here:
http://forum.xda-developers.com/showpost.php?p=30563493&postcount=1780
Flashing back to stock 2.3.5, and seeing if I can get the correct IMEI. If so, I'll backup that EFS folder in 10 different places, revert back to ICS or JB, and if the IMEI is messed up there, I'll restore my EFS backup.
Click to expand...
Click to collapse
Good information. I've restored my EFS from a backup I made last october when I first rooted and flashed CM7.
Not sure what leaving the SIM out does? Does it correct the IMEI folder on it's own?
Sooo, I ended up having this situation for first time last night.
What I did was:
1) One click kk4 stock
2) Flash Devil's kernel to get CWM
3) Flash Helly Bean 8/13.
4) Flash ugjk4 modem.
Bam wrong IMEI.
Did the whole thing again, this time using ugjk3 modem - bad IMEI again.
Then I just copied back my efs folder, chown to radio:radio, chmod to 0700 and reboot - IMEI got fixed.
What is really shady is when is this happening? After the initial devil kernel flash? Or the initial helly bean flash when it does the partitions and reboots you back into recovery?
scythekain said:
Good information. I've restored my EFS from a backup I made last october when I first rooted and flashed CM7.
Not sure what leaving the SIM out does? Does it correct the IMEI folder on it's own?
Click to expand...
Click to collapse
Leaving the SIM card out cannot change, reset, or fix your imei, it can't effect it at all.
Leaving the sim card out simply blocks your phone from being able to "phone home" to att, and report the incorrect imei to att. Because when att sees this, that is when they block your device.
This is why I suggested in other posts that when you are flashing a new rom, leave your sim card out. This way if the rom flash does reset your imei, you can repair it and THEN put your sim card back in, without the phone automatically phoning home to att with the wrong imei right off the bat and getting your phone blocked
Ok I have a quick question. I copied my entire EFS folder and copied it into my external SD card. Do I need to do anything else to back it up? I have the correct IMEI and want to make sure it stays that way. I noticed one person mentioned the need to fix permissions. Is that all I need to do. Thanks.
I would make a copy and put it on ur computer as well.
Sent from my SAMSUNG-SGH-I897 using xda premium
Has this been figured out yet? Anyone have any idea why this is happening to some people and not others? What's the common factor here? After several initial failed flash attempts I went from one click froyo, to several cm9 nightlys, to hellybean 8/13 , to cm10 nightly 8/18, to cm10 nightly 8/22. So far I've had zero imei issues. My number still matches the back of the phone. Is this something att is sending out, an app, or one of the ROMs being flashed? I just checked and the permissions for my efs folder are set to rwx r-x r-x. It may help if everyone lists their history.
Sent from my SGH-I897 using xda app-developers app
rickneworleansla said:
Has this been figured out yet? Anyone have any idea why this is happening to some people and not others? What's the common factor here? After several initial failed flash attempts I went from one click froyo, to several cm9 nightlys, to hellybean 8/13 , to cm10 nightly 8/18, to cm10 nightly 8/22. So far I've had zero imei issues. My number still matches the back of the phone. Is this something att is sending out, an app, or one of the ROMs being flashed? I just checked and the permissions for my efs folder are set to rwx r-x r-x. It may help if everyone lists their history.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
1) I used one click root, to root my phone back in October, then backed up my EFS.
2) Odin CM7 CWM.
3) Flashed CM 7.1 stable, got fed up with the /datadata limitation pretty quickly. Tried Miui. (had same problem)
4) November, flashed last available nightly for CM 7.1 (till march of this year) this change the structure of /datadata to have about 400 Megs and to warn when it's getting full.
5) January, started flashing nightly kangs weekly.
6) Mid March, flashed CNA 4.0.3 - Horribly laggy.
7) Flashed AOKP, CM9 nightlies etc. Ended up sticking with CM9 nightlies.
8) 8.18 flashed CM9 nightly.
9) 8.18 flashed UXKH2 modem (awesome voice quality)
10) 8.20 no wireless data/signal - device blocked.
According to the Google Play store, the incorrect IMEI was registered on Monday. Which means something deleted it Sunday night Monday morning while I was sleeping.
(if you want to you can view your account history and registered devices here
https://www.google.com/dashboard/
IMEI
this recently happened to me over the weekend. I simply flashed back to stock KK4 and i had my IMEI number back to what its supposed to be. I never had to call AT&T to unblock it. once I got my IMEI back, I flashed a custom corn kernel and installed root. while I still had the original IMEI I downloaded an app called Galaxy S Unlock and in this app there is an option to back up only your efs folder and its contents. after making two back ups I decided to flash the latest Helly Bean from Der Teufel whilst leaving my SIM out. once all was said and done I still had my stock IMEI number with CM10 Helly Bean. the only number that I notice changed is the IMEI SV. it went from 00 at stock KK4 to 05 on cm10. I don't know what that number represents but it doesn't seem to affect me. good luck to anyone with this issue.
cheeesboiger said:
this recently happened to me over the weekend. I simply flashed back to stock KK4 and i had my IMEI number back to what its supposed to be. I never had to call AT&T to unblock it. once I got my IMEI back, I flashed a custom corn kernel and installed root. while I still had the original IMEI I downloaded an app called Galaxy S Unlock and in this app there is an option to back up only your efs folder and its contents. after making two back ups I decided to flash the latest Helly Bean from Der Teufel whilst leaving my SIM out. once all was said and done I still had my stock IMEI number with CM10 Helly Bean. the only number that I notice changed is the IMEI SV. it went from 00 at stock KK4 to 05 on cm10. I don't know what that number represents but it doesn't seem to affect me. good luck to anyone with this issue.
Click to expand...
Click to collapse
The "SV" is the Software version, it doesn't affect your IMEI (your device identifier).
http://imeimobile.blogspot.com/2009/11/structure-of-imei-and-imeisv.html
Your sim card has been blocked after put in the lose/stollen AT&T phone .
Your sim card has been blocked after put in the lose/stollen AT&T phone .
For the last month my wife has been using her new Tab S2 on WIFI only while vacationing abroad. Yesterday we got home and I inserted her sim into the tablet and she was able to connect via the LTE system and access the internet. This morning suddenly she could not access the internet via LTE. In the ABOUT tab the baseband is blank and the IMEI shows up as null. Nothing was installed nor were any updates received that I can tell. It seems clear that the EFS file is corrupted.
1. The information I have found (none of it from XDA) about repairing the problem all seem to assume a backup of the EFS file, which, of course I don't have.
2. Some require root, which I would prefer not to do, as the tablet is under warranty and don't want to void it.
3. There is an EFS Repair tool online, which is a bat file which tries to created a copy of the EFS file and then to have ODIN rewrite it. The backup phase fails with a message that there is no EFS file to backup. (It's not clear to me how backing up and then restoring a corrupt file would help anyway).
4. There is no access to the phones internal control panel via secret code, or the page that comes up is blank.
5. I tried a factory reset but it did not fix the problem.
Any help out there?
thanks
sblevine
sblevine said:
For the last month my wife has been using her new Tab S2 on WIFI only while vacationing abroad. Yesterday we got home and I inserted her sim into the tablet and she was able to connect via the LTE system and access the internet. This morning suddenly she could not access the internet via LTE. In the ABOUT tab the baseband is blank and the IMEI shows up as null. Nothing was installed nor were any updates received that I can tell. It seems clear that the EFS file is corrupted.
1. The information I have found (none of it from XDA) about repairing the problem all seem to assume a backup of the EFS file, which, of course I don't have.
2. Some require root, which I would prefer not to do, as the tablet is under warranty and don't want to void it.
3. There is an EFS Repair tool online, which is a bat file which tries to created a copy of the EFS file and then to have ODIN rewrite it. The backup phase fails with a message that there is no EFS file to backup. (It's not clear to me how backing up and then restoring a corrupt file would help anyway).
4. There is no access to the phones internal control panel via secret code, or the page that comes up is blank.
5. I tried a factory reset but it did not fix the problem.
Any help out there?
thanks
sblevine
Click to expand...
Click to collapse
Just flash rom on it via Oden it will not trip Knox as long as it is a stock rom
stinka318 said:
Just flash rom on it via Oden it will not trip Knox as long as it is a stock rom
Click to expand...
Click to collapse
reflashing did not fix it. The baseband is still unknown and the imei is still null. (I must admit I was wondering where the stock rom was going to get the IMEI from during flashing).
Any other ideas, please?
sblevine said:
reflashing did not fix it. The baseband is still unknown and the imei is still null. (I must admit I was wondering where the stock rom was going to get the IMEI from during flashing).
Any other ideas, please?
Click to expand...
Click to collapse
You may need to send it back to Samsung to get it fixed they will be able to pull a log cat and see what happened.
Hello,
I'm french, excuse my langage...
I have 2 note 8, an N950F (single sim) and an N950FD (double sim). I specify immediately that the 2 have already worked and that I have only one sim (one being for me and the other as a gift for my wife lol)
- On the N950F, install via odin 3.14 of twrp 33.1.2, then hadesrom 12 then magisk 20.4 => everything is ok
- Purchase of the N950FD, hassle with installing twrp because I had to put my sim in it to change the time and have access to the usb options, in short, it works, then same as hades and magisk => everything is ok
I have well customized the N950FD, I made a full save (all partitions) with twrp and I said to myself I do a full install on the N950F ...
At the time I did not watch out ...
I calmly use the N950FD and then, I still hack the N950F, I install other custom roms to see, lineage 17, etc etc and all that I do it without sim, with the dex dock connected in ethernet, in me saying that when I'm done, my wife will just put her sim there ...
And then something bothers me, it's a small prohibition logo at the top left instead of the network. I tell myself that this is normal because I did not put a sim, so I take that of my N950FD and there bah it is not recognized ...
I do not panic, I tell myself that I made a false manipulation, I wipe, I reinstall hadesrom and same concern, I take another custom rom and same concern ... I redo a full install with twrp and same concern .. .
I take a stock rom (the last, then the first, always in 4 files either with the csc or with the home-csc), I flash with odin 3.14 and 3.13 and always the same problems, the rom remains blocked on the screen samsung, the first with "samsung note 8 powered by android". So I tried the last rom with 3.14 and 3.13 then the first and still the same problem, it does not start (I waited 5 minutes roughly) despite the wipes ...
Since I no longer have twrp, I reflash, it works, I tell myself that the custom was still installed and I reflash via twrp hades (I tried the stock rom file but it didn't work) and again same concern, the sim is not recognized ...
I try the flash of the hades kernel, it works but the sim is still not recognized ...
When I go to the phone * # 06 # I do not have imei, but a black screen, when I go to parameter / connection / sim card manager => black screen with the message "com-android-phone does not respond" ...
I looked a little on the net, but nothing conclusive, I specify that all my files come from XDA but that given my English I prefer to try to find an answer in French ...
I do not have a backup of the N950F it would have been too simple, I tried another sim than mine but ditto it is not recognized and before making a tablet I would like to try everything to recover it. ..
It would seem that flashing a stock rom solves the problem ... But as said above, my phone remains stuck on the samsung logo despite the wipes
I still tried other things like just flashing parts of a stock rom but I still have the same problem ...
I also tried the flash of a stock with the extra pit and the nand erase and distribution options ... and similar, no start ...
I even reinstalled twrp after a stock, save it, "mix" it with another backup I had (efs and modem from the stock and the rest of the custom) but then again, it doesn't work, such reboots well but still no network access and no recognized sim card ...
Finally, I looked at chimera tool, but no tutorial in French so no way to see how it works or if it will meet my need ... taking an exclusive samsung license on chimera does not cause me any concern IF it allows me to do other things than what I have already tried ...
I also looked at the prog to change the imei because there is nothing left, not even 0, no no, a black page just like when I go to the sim card settings, I have a black page. ..
I also flashed several custom roms from different countries but it didn't work ...
By cons I observed that I had the location for 2 sim, still inactive ...
How to put the note 8 in single sim and recover imei and then the network ???
there, I block ... if you have ideas I am taker, thank you all ...
amthium said:
Hello,
I'm french, excuse my langage...
I have 2 note 8, an N950F (single sim) and an N950FD (double sim). I specify immediately that the 2 have already worked and that I have only one sim (one being for me and the other as a gift for my wife lol)
- On the N950F, install via odin 3.14 of twrp 33.1.2, then hadesrom 12 then magisk 20.4 => everything is ok
- Purchase of the N950FD, hassle with installing twrp because I had to put my sim in it to change the time and have access to the usb options, in short, it works, then same as hades and magisk => everything is ok
I have well customized the N950FD, I made a full save (all partitions) with twrp and I said to myself I do a full install on the N950F ...
At the time I did not watch out ...
I calmly use the N950FD and then, I still hack the N950F, I install other custom roms to see, lineage 17, etc etc and all that I do it without sim, with the dex dock connected in ethernet, in me saying that when I'm done, my wife will just put her sim there ...
And then something bothers me, it's a small prohibition logo at the top left instead of the network. I tell myself that this is normal because I did not put a sim, so I take that of my N950FD and there bah it is not recognized ...
I do not panic, I tell myself that I made a false manipulation, I wipe, I reinstall hadesrom and same concern, I take another custom rom and same concern ... I redo a full install with twrp and same concern .. .
I take a stock rom (the last, then the first, always in 4 files either with the csc or with the home-csc), I flash with odin 3.14 and 3.13 and always the same problems, the rom remains blocked on the screen samsung, the first with "samsung note 8 powered by android". So I tried the last rom with 3.14 and 3.13 then the first and still the same problem, it does not start (I waited 5 minutes roughly) despite the wipes ...
Since I no longer have twrp, I reflash, it works, I tell myself that the custom was still installed and I reflash via twrp hades (I tried the stock rom file but it didn't work) and again same concern, the sim is not recognized ...
I try the flash of the hades kernel, it works but the sim is still not recognized ...
When I go to the phone * # 06 # I do not have imei, but a black screen, when I go to parameter / connection / sim card manager => black screen with the message "com-android-phone does not respond" ...
I looked a little on the net, but nothing conclusive, I specify that all my files come from XDA but that given my English I prefer to try to find an answer in French ...
I do not have a backup of the N950F it would have been too simple, I tried another sim than mine but ditto it is not recognized and before making a tablet I would like to try everything to recover it. ..
It would seem that flashing a stock rom solves the problem ... But as said above, my phone remains stuck on the samsung logo despite the wipes
I still tried other things like just flashing parts of a stock rom but I still have the same problem ...
I also tried the flash of a stock with the extra pit and the nand erase and distribution options ... and similar, no start ...
I even reinstalled twrp after a stock, save it, "mix" it with another backup I had (efs and modem from the stock and the rest of the custom) but then again, it doesn't work, such reboots well but still no network access and no recognized sim card ...
Finally, I looked at chimera tool, but no tutorial in French so no way to see how it works or if it will meet my need ... taking an exclusive samsung license on chimera does not cause me any concern IF it allows me to do other things than what I have already tried ...
I also looked at the prog to change the imei because there is nothing left, not even 0, no no, a black page just like when I go to the sim card settings, I have a black page. ..
I also flashed several custom roms from different countries but it didn't work ...
By cons I observed that I had the location for 2 sim, still inactive ...
How to put the note 8 in single sim and recover imei and then the network ???
there, I block ... if you have ideas I am taker, thank you all ...
Click to expand...
Click to collapse
If you didn't take a backup of your /efs folder which is where all of the phones important information is stored such as your IMEI then you are screwed because you can't flash any other phones EFS FOLDER.. However if you have a backup efs folder, restore it.
the concern is that I do not have a backup of the efs file ...
is it possible to put an efs file of another note 8 n950f and where to find this file on the net?
amthium said:
the concern is that I do not have a backup of the efs file ...
is it possible to put an efs file of another note 8 n950f and where to find this file on the net?
Click to expand...
Click to collapse
MrMike has already answered this, you can't share or use any other EFS.
The fact you can flash a custom rom and it will boot tells me you don't have a hardware issue, try flashing stock again as this can sometimes fix the EFS file, it has done for me in the past and a few others users. Although I can't tell you why you get stuck after flashing stock, this is the best way for you to hopefully resolve your issue as you don't have a EFS backup.
Except by flashing a stock, is there a way to restore the n950f to factory condition?
because with odin, if I flash the last stock, it does not start even if I make the wipes and if I try an old stock, odin blocks ...
can the chimera program allow me to find an original n950f?
amthium said:
Except by flashing a stock, is there a way to restore the n950f to factory condition?
because with odin, if I flash the last stock, it does not start even if I make the wipes and if I try an old stock, odin blocks ...
can the chimera program allow me to find an original n950f?
Click to expand...
Click to collapse
Not that I am aware of, I am only aware of restoring by flashing stock with Odin or by using Samsung smartswitch.
You can't flash older filmware than what is already on the phone, that is why Odin is blocking that, but when you flash the latest filmware does Odin give you the green pass?
I am not familiar with the Chimera program so can't speak on that.
Yes with odin I have the green pass, but then the note 8 does not start, it remains blocked on the logo, even if I do the wipe ...
I even tried to save right after with twrp and recover the efs but it does not work ...
If I find a broken Note 8 can I recover the efs file by saving it and then putting it on my own?
hainguyenthao said:
Device will not boot while there is an error in efs partition so u need to fix it first i have same device and i can help you to boot it
Click to expand...
Click to collapse
Thanks for your help, how to start it in stock rom?
I specify that it starts in custom rom ...
the first photo is before the installation of the stock rom with odin, the second is at the end of the installation (odin ok, pass in green), the third is after the restart which has not worked (blocking on samsung note 8)
hainguyenthao said:
Sorry error when loading images 404 Not Found upload it again or send it to my email
Click to expand...
Click to collapse
Could you please explain to us all in here how you're going to fix his /efs folder when he never made a backup of it.. Where are you planning on getting him an /efs folder that held all of his phone's information when he accidentally deleted it?
hainguyenthao said:
By root device and download Root Explorer, browse to the efs folder the delete everything EXCEPT the 'FactoryApp' and 'prov_data' folders it should restore IMEI
Click to expand...
Click to collapse
I gave this a shot but it didn't work for me.