Hi Guys,
My phones had about one billion different ROMS on it in the past.
Today, I tried to install the un"official" leak of 4.2.2 and now my phone recognise ANY sim inserted into it - even ones from different networks. It's important to note though, the phone DOES boot into the O/S but shows the "no entry" sign for any SIM that's inserted. In addition, CWM has also stopped working and if I hold down up arrow, power and menu the phone simply keeps looping the boot "Samsung Galaxy III" screen. I've also tried re-flashing CWM but the same issue occurs i.e. the boot loop.
I can still get ODIN to work and have tried applying a previous (proper) official ROM but had no luck.
Any ideas?
Other info -
Android Version: 4.2.2.
BasBand: Unknown
Kernal: 3.0.31-611730
Build Number: JDQ39.I9300XXUFME3
Network: Unknown
Signal Strength -113dBm
Mobile Network Type: Unknown
Service State: Out of Service
Mobile network State: Disconnected
My Phone number: Unknown
IMEI SV: Unknown
Your IMEI number is blank, so you'll not get any network to connect. Restore your IMEI back up and the network should then connect.
Regarding CWM, does the leak restore the stock recovery on each boot like official roms do? If so delete or rename the file it's using and try flashing Philz recovery to test.
It looks like you've had some partition or data corruption during the flash.
boomboomer said:
Your IMEI number is blank, so you'll not get any network to connect. Restore your IMEI back up and the network should then connect......
Click to expand...
Click to collapse
IMEI backup? Without shouting "did you not backup your IMEI", how could that have been done and how can I restore it?
You can only restore a backed up EFS .
No EFS backup then no restore .
how could that have been done>>> all in the stickied basic faqs and guides .
Looks as a paid for service repair .
jje
Have a very careful search through internal storage and external sd, some roms backup your IMEI during installation so you might get lucky - also some have recovered it by flashing a full stock rom via odin. Worth a try, otherwise you need a service centre as JJ says.
boomboomer said:
Have a very careful search through internal storage and external sd, some roms backup your IMEI during installation so you might get lucky - also some have recovered it by flashing a full stock rom via odin. Worth a try, otherwise you need a service centre as JJ says.
Click to expand...
Click to collapse
I'd happily give another (another!) stock rom a go via ODIN but the only ones I could find used CWM and of course, that wasn't working ..... maybe that wasn't working for another reason?
Monty Burns said:
I'd happily give another (another!) stock rom a go via ODIN but the only ones I could find used CWM and of course, that wasn't working ..... maybe that wasn't working for another reason?
Click to expand...
Click to collapse
Stock roms in the stock rom thread or hundreds of them on sammobile.com
jje
Fixed!
Hi Gents,
thanks for your advice and help!
I was fortunate enough over the weekend to succeed in repairing the phone by bombarding various different versions of CWM until eventually one of them took hold and worked. Don't know why this happened or how but I'm now currently running a PureLook HD ROM with the ability to make and receive calls! :laugh:
Related
Initial state(stock 4.0.4. ROM):
Device was working properly;
Could call, could use 3G internet;
Everything was good.
After CWM zip installing FoxHound ROM:
Simptoms:
Could not call; for every GSM/3G interogation to telecom operator I get: "Not registered on network";
In my pursuite to fix this, I don't know how, now my device ended in Factory Mode(a yellow box with some debug information appears on my screen and the power button now instantly shutsdown the device and no lock screen available).
The IMEI returned by *#06# is different by the one on the back of the device. It's not a generic one "000...", it almost looks like the original, both seem to be valid after some search, but this is odd. I don't know if it was different before installing FoxHound ... never cared.
What I've tried to do:
I've actually feasted on half of internet for a solution to my problems;
I've tried to flash with Odin tons of stock firmwares, modems, CSCs, including well known ones, my operator ones(Cosmote), my country ones(Romania) -> no luck;
I've tried to restore previous nandroid backups -> no luck;
I've tried to CWM zip install custom ROMs -> no luck;
I've tried everytime to wipe cache, factory reset, delete dalvik, fix permissions, reset battery stats -> no luck;
I've tried all the solutions for the "Factory Mode On" problem, including "echo -n ON > /efs/imei/keystr; chown 1001:1001 /efs/imei/keystr" -> no luck;
I don't have an /efs/ backup before installing FoxHound.
Used GalaxSim, everything was green, no unlock needed.
My device is still in the same condition. No one has an answer. Do you have a solution?
Have you tried flashing with mobile odin?
How did you do a nandroid? With s3 toolkit?
Sometimes when it doesn't work I have to re install the samsung drivers and then try again on full charge.
Something else I noticed with the toolkit was that if I choose a different firmware from the options I done the nandroid with it doesn't work.
Also you may have to flash the insecure image again.
Sorry all could think of.
Sent from my GT-I9300 using xda premium
Samsungnooby said:
1.Have you tried flashing with mobile odin?
2. How did you do a nandroid? With s3 toolkit?
3. Sometimes when it doesn't work I have to re install the samsung drivers and then try again on full charge.
Something else I noticed with the toolkit was that if I choose a different firmware from the options I done the nandroid with it doesn't work.
4. Also you may have to flash the insecure image again.
5. Sorry all could think of.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
1. I haven't tried with mobile odin. This is the first time I've heard about it. I only used desktop odin for flashing.
2. I did a nandroid backup of the stock version of my device, the one which was functional, but without s3 toolkit(also the 1st time I hear about it). My curiosity is why it still wasn't unable to function after I've restored the functional nandroid.
3. I'll try this, thanks.
4. Never heard of insecure image. I'll search for it. Thanks.
5. Thank you very much for your reply. I'll keep you up to date if I'll manage to repair it.
goliathj said:
1. I haven't tried with mobile odin. This is the first time I've heard about it. I only used desktop odin for flashing.
2. I did a nandroid backup of the stock version of my device, the one which was functional, but without s3 toolkit(also the 1st time I hear about it). My curiosity is why it still wasn't unable to function after I've restored the functional nandroid.
3. I'll try this, thanks.
4. Never heard of insecure image. I'll search for it. Thanks.
5. Thank you very much for your reply. I'll keep you up to date if I'll manage to repair it.
Click to expand...
Click to collapse
Get yourself the galaxy s3 toolkit, free from here or you can make a donation.
I like how you numbered my quote
Sent from my GT-I9300 using xda premium
Sad ...
Your EFS data is fu**d and your modem refuses it (and refuses to let you on the network). As far as I know running with an invalid IMEI is illegal in every single country, and in most can land you in actual jail. That being said - search the post about ariza (who had the original modem patch post, but decided to go on a different way) or download this - http://db.tt/PDH8Bc64 !
IMEI broken restore your backed up EFS folder .
jje
Samsungnooby said:
Get yourself the galaxy s3 toolkit, free from here or you can make a donation.
I like how you numbered my quote
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I've download it. Great! Also numbering makes you follow up easier
xclub_101 said:
Your EFS data is fu**d and your modem refuses it (and refuses to let you on the network). As far as I know running with an invalid IMEI is illegal in every single country, and in most can land you in actual jail. That being said - search the post about ariza (who had the original modem patch post, but decided to go on a different way) or download this - !
Click to expand...
Click to collapse
I don't know why my EFS ended ****ed up, and yes, it's illegal. AFAIK, if it's a soft problem, it can be fixed. Isn't the IMEI code embedded into the hardware? Why can't I just wipe everything, from /, and flash a stock ROM? The EFS should be fixed, right?
JJEgan said:
IMEI broken restore your backed up EFS folder .
jje
Click to expand...
Click to collapse
This is important for me, please follow:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
NO
No EFS backup in a nandroid .
Rule one is backup your EFS folder .
If you have a custom rom or kernel that may have auto backed up your EFS to a file efs xxxx.tar .gfz
No EFS then before a service centre try .
http://forum.xda-developers.com/showthread.php?t=1308546
jje
The nandroid ...
goliathj said:
I don't know why my EFS ended ****ed up, and yes, it's illegal. AFAIK, if it's a soft problem, it can be fixed. Isn't the IMEI code embedded into the hardware? Why can't I just wipe everything, from /, and flash a stock ROM? The EFS should be fixed, right?
This is important for me, please follow:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
Click to expand...
Click to collapse
IMEI is no longer so much in "hardware" - it is stored in a protected way in nv_data.bin, which is located in the EFS partition and under normal circumstances is NEVER written by a ROM. Unfortunately the normal nandroid backup does not contain an image of the EFS partition, but some of the better ROMs create a backup (sometimes on the external SD card, sometimes not) - look after something called efsbackup.tar.gz or efsdev-mmcblk0p3.img.gz !
Also the IMEI and serial number from under the battery can (and should) be placed back in a form of edited nv_data.bin - but most likely you will never be able to run that with any of the stock modems and you will still need the patched one that I linked somewhere above.
JJEgan said:
I have a nandroid backup of my working stock ROM. Does this backup contain my working EFS? Note that I've restored it, and I still get the network error.
NO
No EFS backup in a nandroid .
Rule one is backup your EFS folder .
If you have a custom rom or kernel that may have auto backed up your EFS to a file efs xxxx.tar .gfz
No EFS then before a service centre try .
http://forum.xda-developers.com/showthread.php?t=1308546
jje
Click to expand...
Click to collapse
Thank you. Leason learned. Will backup EFS from now on.
xclub_101 said:
IMEI is no longer so much in "hardware" - it is stored in a protected way in nv_data.bin, which is located in the EFS partition and under normal circumstances is NEVER written by a ROM. Unfortunately the normal nandroid backup does not contain an image of the EFS partition, but some of the better ROMs create a backup (sometimes on the external SD card, sometimes not) - look after something called efsbackup.tar.gz or efsdev-mmcblk0p3.img.gz !
Also the IMEI and serial number from under the battery can (and should) be placed back in a form of edited nv_data.bin - but most likely you will never be able to run that with any of the stock modems and you will still need the patched one that I linked somewhere above.
Click to expand...
Click to collapse
Thanks for the info. Good to know.
Finally, my device works. I've contacted a private service.
The Factory Mode problem, which was always on, was fixed by flashing a stock 4.0.4 ROM.
The "Not registered on network" problem had various reasons:
My IMEI had been changed so my modem wasn't accepting any calls. He had rewritten the original IMEI(the one from the back) with "the box".
For unknown reasons for me, 4.1.0+ has some built-in protections and will brick my device everytime I flash it. So, for the moment I'm sticking with 4.0.4.
Some people experienced this problem after updating, so it has something to do with the built-in protections(but the question is "protection against what?"). There's something smelly about our IMEI, we, the ones having this issue. I've bought this device over ebay.co.uk and it arrived unsealed(the merchant told this because he had to check the phone) but with root installed and had 1 count of custom binary flashed, in the download mode screen. This is odd. From now on, I'll ask for IMEI.
I thank everyone for helping me. Best regards!
Stuck on EDGE and in Factory Mode
I have literally over 16hrs trying to get my I747 back working correctly. It all stared when I tried the "Hellfire" rom. I have had my phone rooted running custom roms for over 6 months with no problems. After flashing the "Hellfire" rom I noticed that I was stuck on "EDGE" network, unable to make or receive phone calls or text. After further inspection, I noticed I had "0" for an IMEI#. So I injected my IMEI back on the phone... Still the same problem. I reverted back to stock ROM, Kernel, and Modem... Same problem stuck on "EDGE" network. Several hours later of no stop research, I noticed that my "ERI version Not available". After alot more research I noticed that my "efs" folder was missing the ".nv_data" file. So I backed up the "efs" folder, saved it to my extSD, and then deleted the "efs" folder for the root of the phone. Now I'm in "Factory Mode" even after replacing my backed up "efs" folder with the new one that was created at the root of my Internal sd.
I need help... If anyone has any ideas...:crying:
You might try what they talk about in this thread, don't know if it applies to your situation or not...
I can't post off site URL's, so google "Not registered on network" + stuck in Factory Mode ON - no solution works
It's the thread on androidpit dot com
Hi, basically i tried to update my s3 to a custom jelly bean software and during the process, i got no signal. I then got my friend to look at it and then he rolled it back to 4.0.4 but now there is no sim in the phone and it says no service? Also, there is no imei number or bluetooth number and the phone doesnt connect to wifi? What should I do?
Reboot into recovery, do a factory reset and see if it works then. If not, try reflashing a stock ICS ROM.
nope didnt work
try to flash stock ROM and kernel with ODIN....
BAD NEWS
labeeqhussain said:
Hi, basically i tried to update my s3 to a custom jelly bean software and during the process, i got no signal. I then got my friend to look at it and then he rolled it back to 4.0.4 but now there is no sim in the phone and it says no service? Also, there is no imei number or bluetooth number and the phone doesnt connect to wifi? What should I do?
Click to expand...
Click to collapse
You wiped the EFS folder... that's not good, not even close
If your phone is not the intl version, and you got no signal after flashing the ROM, you most likely reverted the soft unlock (which involves altering files in this folder, which is in the root of Android on most sammy devices) - that's why you didn't get a signal (or maybe you just didnt have the right modem flashed with the rom you downloaded, but this is unlikely)
And when your friend rolled back he wiped the EFS folder by accident, or tried to unlock your phone and screwed up without having backed it up first
My friend, i do not know if these folders have files specific to each device, if not, just look for a backup on the forums and paste it in the root folder of the device, otherwise, you are beyond ****ed up, you may have bricked your s3 (or maybe your friend did)
Please write back if developments occur
EDIT: The only solution is to take it to a service center and *hope* they repair it, as modifying the IMEI is likely ilegal (and talking about it is against the rules of XDA) - The EFS folder is DEVICE SPECIFIC, if you didnt make a backup you basically bricked your phone... i'm sorry my friend, i hope the SC can get it done for you
Hey everyone. The other day, I was installing a custom ROM and was also trying to unlock my Galaxy SIII. After both, Airplane mode somehow locked on... I did a factory reset - didn't help. I also reinstalled the stock image - didn't help. I tried several tar recovery files - didn't work or help. I tried everything! I can disable airplane mode in settings but my device simply displays a circle with a cross through it instead of the signal meter in the notification bar. It also doesn't detect SIM cards now... I don't know what is wrong. Help would be GREATLY APPRECIATED!!!!!
Thanks for your answers in advance!
My first thought is the Unlock process stuffed things for you. What did you try for the Unlock? Did you get it right? I've never had a locked phone so I don't know the process but try asking around on threads where they talk about unlocking phones.
What ROM did you try? Can you still get into the phone for menus etc?
And the biggie - did you try Restoring your Nandroid backup? (you DID do a Nandroid at some point, didn't you? )
If you've only done a factory reset from the phone I'd try getting MegaWipe and flash it in Recovery. Then try a ROM you know to be working for others.
Another thing to look at might be your Modem - I use Purelook HD ROM - one of the updates had a modem that screwed with my wifi and phone connection so I flashed the previous one that had worked well and all was right again.
You might also need to try a megawipe and then flash a stock ROM via Odin - get the phone back to a working state and then start ROM'ing again.
Yeah, I can get into menus alright. The MegaWipe didn't seem to work though Or the Purelook HD ROM. I've flashed the stock ROM about 100 times, restored Nandroid and did a full stock restore however nothing worked. Thanks anyway!!!
Do you have an EFS backup?
Is your modem correct? if not, restore your EFS backup
Another thing, dial *#06# on your phone and look at your IMEI. Do you see a bunch of zeros?
xpmode said:
Another thing, dial *#06# on your phone and look at your IMEI. Do you see a bunch of zeros?
Click to expand...
Click to collapse
When I dial *#06#, a box pops up and simple says "IMEI". There is no actual IMEI number displayed... That must be bad..??
astronomynerd said:
When I dial *#06#, a box pops up and simple says "IMEI". There is no actual IMEI number displayed... That must be bad..??
Click to expand...
Click to collapse
Yep, it says EMEI: null / null
astronomynerd said:
Yep, it says EMEI: null / null
Click to expand...
Click to collapse
Your EFS is corrupted. If you have a backup please restore it. If not Flash a fresh stock ROM and start over.
If I'm right, you turned your phone to a Wi-Fi tablet. There is not a real at-home solution other than searching your whole computer and your phone's internal memory and all SD cards you used on your phone for files that have "efs" in their names and hope you find some kind of EFS backup you took before. (About that, can you post a list of the ROMs you installed before? I know Sotmax takes[or used to take, don't know the new versions] automatic EFS backups, maybe other Samsung ROMs do too)
If you can't find any, you should contact with your carrier and ask if they can repair it. It won't be covered by warranty, and you would probably be asked to bring evidence(receipt and such) to prove the phone is not stolen.
Make sure you tell them the whole story, and don't try to cover up the fact that you rooted your phone, or you may end up being questioned by the police.
If they accept, they will restore your IMEI using advanced debugging hardware and software. If they reject, then you may want to start looking for a new phone.
(Procedures may vary)
actually, it will be covered by warranty if you restore it to complete stock
They may still look at the binary counter and tell Odin has been used.
Other than that, lying in such conditions may result in big trouble, so if they ask if you have rooted your device, you should say yes. Not worth risking much bigger trouble for a paid repair.
There is triangle away.
Triangle away+flash stock rom = full stock no binary counter.
Why do you say there might be problems with the police? Since the gs2 there have been lots of cases of lost/corrupted efs without doing anything. Are all those people in jail?
If there's proof of ownership, then there's nothing to it. I really don't know how much is the standard rate for lost/corruped efs fixing outside of warranty, if it involves motherboard replacing, its gonna be as expensive as a new phone.
I'm talking from looking at my country's regulations, so they might be different in other countries. Hence the "procedures may vary" in my reply.
Hi all. I rooted my phone couple of weeks ago and I didn't like the rom that I flashed and I decided the unroot my phone. So today I tried to unroot my phone and applied triangle away solution. Everything went perfect. I flashed a stock rom, I unrooted my phone successfully. Since this I have no connection at all. No 2g, no 3g. I've done some research on the Internet but couldn't find a proper answer. The phone shows the imei number but it doesn't match with the number under the battery. What should I do?
Marashlim said:
Hi all. I rooted my phone couple of weeks ago and I didn't like the rom that I flashed and I decided the unroot my phone. So today I tried to unroot my phone and applied triangle away solution. Everything went perfect. I flashed a stock rom, I unrooted my phone successfully. Since this I have no connection at all. No 2g, no 3g. I've done some research on the Internet but couldn't find a proper answer. The phone shows the imei number but it doesn't match with the number under the battery. What should I do?
Click to expand...
Click to collapse
go through this post and find a solution:
http://forum.xda-developers.com/showthread.php?t=2344125
Marashlim said:
Hi all. I rooted my phone couple of weeks ago and I didn't like the rom that I flashed and I decided the unroot my phone. So today I tried to unroot my phone and applied triangle away solution. Everything went perfect. I flashed a stock rom, I unrooted my phone successfully. Since this I have no connection at all. No 2g, no 3g. I've done some research on the Internet but couldn't find a proper answer. The phone shows the imei number but it doesn't match with the number under the battery. What should I do?
Click to expand...
Click to collapse
As per the faqs and guides restore your backed up EFS folder .
Not read the basics and no EFS backup then its a paid for service repair.
jje
I have no efs back up. I rooted my other phone million times but I've never backed it up. So jje you basically mean there is no exact solution for the issue. I need to send my phone to the service?
If you flashed a custom rom it may have a EFS backup look for EFSbackup.tar on your phone .
Looked for it but there is nothing. I've sent a PM one of the XDA users who is an expert with IMEI. I'm waiting for his answer. If he can't fix it I'll visit a Samsung repair centre. The phone is now out of warranty, isn't it? How much they are gonna charge me roughly?
did you try to flash an emg2 or emg4 baseband? some have reported that this can restore network connection
ashraf sharif said:
did you try to flash an emg2 or emg4 baseband? some have reported that this can restore network connection
Click to expand...
Click to collapse
You are amazing mate. Your suggestion fixed the problem. I now have 2G, 3G connection on my phone. Thank you so much.
make sure that going forward if you flash any other baseband or rom that includes a baseband as all stock roms do and also some custom roms as well, that you flash one that is newer than what you have now. the older basebands can no longer read the efs folder because beginning with emg4 the efs folder is modified so older radios will not work properly. back up your efs folder because it may get corrupted. if that happens than only a backup can restore your network connection, this time you got lucky it was not corrupted yet. the format changed but the info was intact. please read the stickies all the answers are there.
ashraf sharif said:
make sure that going forward if you flash any other baseband or rom that includes a baseband as all stock roms do and also some custom roms as well, that you flash one that is newer than what you have now. the older basebands can no longer read the efs folder because beginning with emg4 the efs folder is modified so older radios will not work properly. back up your efs folder because it may get corrupted. if that happens than only a backup can restore your network connection, this time you got lucky it was not corrupted yet. the format changed but the info was intact. please read the stickies all the answers are there.
Click to expand...
Click to collapse
Dear Ashraf sharif,
My sgs3 gt i9300 currently has baseband version I9300 DDEMG2 and bulid number JZ054K.I9300XXEMG5.
I had flashed resurrection remix rom and i got my IMEI changed and baseband version unknown then i restored everything back with a lot of help form rootsu,now my issues are:-
which all baseband i can flash or which roms are suited for this ie what should i look for in a rom while flashing as far as baseband and not ****ing up my imei is concerned?
and does that means in addition to flashing a custom rom i need to flash a baseband also as you mentioned that few custom roms have baseband ie all doesn't have basebands???
thanks in advance.......
I am no expert on this issue as I have not experienced it myself. With that being said , it is my understanding that once a g series modem or baseband is used reverting to an older baseband will result in no network. Read the thread in general called " attention 19300xxemg4 changes efs folder". some firmwares do not touch the baseband only affecting system+ kernel+ recovery.
Since you are on mg2 baseband it is probably safest for you to stick with it because it works . If you do decide to change it make sure you flash a baseband that is either the same or newer. Also make sure csc code is correct for your region.
Make several backups of your efs and save to external sd and computer and flashdrive. Read the stickies .
wait and see before flashing . Read reviews for newly released firmwares. This is how I avoided this relatively new issue with efs imei . I simply read the thread "attention 1900xxemg4 changes efs folder.
Hello!
Today I decided to go back to the stock ROM of Samsung S3 (international).
So, I downloaded the original from sammobile :
http://www.sammobile.com/firmwares/3/?download=16458
Went into the Download mode of my phone:
With Odin3 (v3.07) I loaded the .tar.md5 file which I just downloaded. (by the PDA ofcourse).
Then my phone restarted and just follow the steps as you just get your new Samsung S3, like account configuration etc etc etc.
Did the tutorial to reset the flash/binary counter, just worked.
After this, I was planning to install Whatsapp again,
THEN noticed I had no network signal , except WiFi .
Probably there was no signal when the phone already got started.
I checked *#06# for the IMEI, and there it is.. the 004999xxxxxxxxxx / 08 .
So, I've checked some topics and tried a thing that should repair the IMEI.
But no success!
When I installed CyanogenMod, they didn't told me to backup the EFS folder (or I just didn't see that at all!)
So, I followed this topic:
http://forum.xda-developers.com/showthread.php?t=1264021
Didn't worked.
I'm root again btw on the stock ROM.
Then I noticed I've a backup of my phone BEFORE CM. Made it with the CWM itself, which I moved later to my computer.
So, I moved that one back to my phone. and when I go to CWM Recovery and select Restore
It says:
Couldn't open directory.
No files found.
So, checking for that error, someone came up with moving the backup files to
/data/media/Clockworkmod/backups/
Did not work!
What to do?
I'm questioning myself now, even if the restore is going to work, will the IMEI be restored too?
EDIT: Monday it will be shipped to Samsung.
- Back to stock
- Reset flash/binary counter
- Unroot
- Wipe cache and back to factory
Couldn't get rid of the 0049 IMEI and 0000000 S/N
I'll keep this post up to date when I hear something.
No CWM does not backup efs....I suggest you go here http://forum.xda-developers.com/showthread.php?t=2393289 because they will close this thread soon due to this question being asked many times before
I've seen that topic indeed, then I will put it back with flash/binary count to No , and the status to Normal.
Hope Samsung will fix it then when it just doesn't work.
https://dl.dropboxusercontent.com/u/23869279/Temp/xxemg4.zip
Flash via CWM. If you don't want to flash it via CWM you can also extract "modem.bin" file and flash as MODEM through your Odin.
JustArchi said:
https://dl.dropboxusercontent.com/u/23869279/Temp/xxemg4.zip
Flash via CWM. If you don't want to flash it via CWM you can also extract "modem.bin" file and flash as MODEM through your Odin.
Click to expand...
Click to collapse
Thanks for your reply!
I've set everything back to stock and reset the counter/binary to No , and the rest Samsung official again.
Today I went to the shop where I bought my phone, and they're going to sent it to Samsung.
Forgot to mention here that my S/N is also 0000000.
Let's hope that they will repair it.
I've red a news article, that Samsung has a new policy.
They now also repair rooted devices and even when a custom ROM was installed.
I'll find out when I got a message from the service centre.
When I know something, I'll post it here.
Thanks again anyway!
Should have tried your modem.bin
I've red a news article, that Samsung has a new policy.
They now also repair rooted devices and even when a custom ROM was installed.
Doubt that but just in case do let us know if Samsung reject warranty .
JJEgan said:
I've red a news article, that Samsung has a new policy.
They now also repair rooted devices and even when a custom ROM was installed.
Doubt that but just in case do let us know if Samsung reject warranty .
Click to expand...
Click to collapse
Will do :good:
Did you read the IMEI / EFS post on the general forum?
I had a similar problem... to make the story short before CM 10.1.3 I was on stock MG4, after CM I decided to go back to my carrier's stock ROM (needed to send my phone for repair, USB port was faulty) and I noticed the IMEI problem. What happened is that Samsung decided to change the efs format with MG4 (July 13th) so any rom prior to that won't be able to read the efs.
If your rom is prior to that then you need to flash a newer modem (MG4 or later) so it can work properly.
jmvelazquezr said:
Did you read the IMEI / EFS post on the general forum?
I had a similar problem... to make the story short before CM 10.1.3 I was on stock MG4, after CM I decided to go back to my carrier's stock ROM (needed to send my phone for repair, USB port was faulty) and I noticed the IMEI problem. What happened is that Samsung decided to change the efs format with MG4 (July 13th) so any rom prior to that won't be able to read the efs.
If your rom is prior to that then you need to flash a newer modem (MG4 or later) so it can work properly.
Click to expand...
Click to collapse
Yeah, I must have red over that... But I tried fixing it spending about 10-12 hours on it, cuz of searching and read it carefully.
I had no EFS backup, stupid that the CWM Recovery didn't backed that up , and of course, stupid of myself :silly:
I will now wait if Samsung is going to repair it under my warranty.
If not, they will probably call me about fixing it for a price.. (If the article isn't true about repairing rooted / flashed devices)
Update 15-11-'13
Phone is repaired under warranty!
They reprogrammed the phone and did a software update. I'm not sure if this is the 4.3.
Can pickup my phone monday, because the shop doesn't receive delivery on saturday -_- ..
But at least, it should be working fine now.