Related
Hi there I have a I9300 (International Version) of S3
So I'm just getting straight to the point
I had bought a s3 from a private seller from ebay and it was running 4.1.2.
I have a bit of experience in using Odin and I had downloaded some UK BTU android 4.3 version from sammobile.com which I usually use to update my phone.
But today if went wrong
I never did root because I never did like it and never made an efs backup
I had flashed I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 file to my phone and everything went perfectly fine
BUT THEN!
I tried calling some of my friends and I noticed that my sim wasn't being recognised
It didn't take long until I realised that my IMEI number had been to some random 0049***** number (I had found out that this was generic and was'nt my real IMEI Number)
I had then checked the IMEI number on the back of the phone and it did not match what was said in my phone settings
I have now clocked that it was the 4.3 android which was screwing me up
I have never installed any custom roms .etc and have only ever installed official ones from sammobile
So why would my phone's EFS get f***ed up and I also did'nt do any in Odin like phone efs clear
My phone had also ran out of warranty so I can't play dumb either
I have researched and found that it is possible to edit the nv_data file.etc like on http://forum.xda-developers.com/showthread.php?t=1804117
I have also tried downgrading but now odin wont allow but probably has something to do with samsung (downgrading policy)
I have also NOW made a backup of my efs folder and my phone is fully functional but my IMEI AND my SERIAL NUMBER was changed
Be honest do I have a realistic chance of recovering my phone or would I have to shell out of repairs and if so how much would it cost?
@mizzeeboy,
Try this?
~ RazorMC
Hey
U can try this too http://forum.xda-developers.com/showthread.php?t=2544109
RazorMC said:
@mizzeeboy,
Try this?
~ RazorMC
Click to expand...
Click to collapse
I have unfortunately tried this and I have realised that some of the phone data in the s2 is different compared to the s3
Also just one question if I could downgrade back to 4.1 would I get my IMEI back?
mizzeeboy said:
I have unfortunately tried this and I have realised that some of the phone data in the s2 is different compared to the s3
Also just one question if I could downgrade back to 4.1 would I get my IMEI back?
Click to expand...
Click to collapse
Sorry for the wrong link.
Maybe this?
- Try to reflash latest 4.3 for your country (this will most likely solve the issue if your efs is not broken)
- You can also try the methods in the link (there are many)
In my limited experience; downgrading to 4.1.2 after 4.3 gave me bootloop and it can't read efs2 (from 4.3)
~ RazorMC
Flash this modem through Odin (http://www.mediafire.com/download/s79zs955sok085h/modem.bin) it's MK6, it should fix the problem for you.
Saad_ said:
Flash this modem through Odin (http://www.mediafire.com/download/s79zs955sok085h/modem.bin) it's MK6, it should fix the problem for you.
Click to expand...
Click to collapse
Thanks I have tried this before and I have unfortunately failed along with your same file.
Hi there.
I wanted to unlock my bootloader, root and flash a custom rom. So I first flashed the global fastboot rom 7.2.5, later flashed the s-twrp recovery and flashed the lineageOs 7.1. I realised that my sim cards weren't working so therefore switched to resurrection remix. Even then, I couldn't get the network even though wifi was working. So I flashed the global fastboot rom again. I still couldn't get the network. Then I realised that my IMEI number might've been erased while flashing even though I followed every step correctly. I dialed *#*#4636#*#* and found out that my IMEI numbers were now unknown. I got to know that my IMEI numbers were definitely wiped. I tried flashing recoveries, boot images, modem files, etc and now I can't even use WiFi. I tried using the WriteDualIMEI application but unfortunately it isn't finding the COM10/20/9/11 port. I have no clue what to do as of now. Can somebody help me with necessary links and details?
Thanks in advance.
Had this problem yesterday. You may refer to my thread on MIUI forum and see if it can help you. Assuming you have Kenzo variant like I do, refer to this and this first to recover IMEI number as well as EFS, then read the rest of my thread to get signal once you recover the IMEI.
slaveration said:
Had this problem yesterday. You may refer to my thread on MIUI forum and see if it can help you. Assuming you have Kenzo variant like I do, refer to this and this first to recover IMEI number as well as EFS, then read the rest of my thread to get signal once you recover the IMEI.
Click to expand...
Click to collapse
Hey there! Thanks for the quick response! It really means a lot.
The EFS thing makes sense now since all my details such as MAC Address, Baseband, IMEI number, etc are all unavailable or unknown. I tried flashing the modem files but are still unknown. Any tips?
keshavkd said:
Hey there! Thanks for the quick response! It really means a lot.
The EFS thing makes sense now since all my details such as MAC Address, Baseband, IMEI number, etc are all unavailable or unknown. I tried flashing the modem files but are still unknown. Any tips?
Click to expand...
Click to collapse
Did you try this guide to restore baseband/IMEI/MAC etc first? You may also use this QCN in case the XQCN in the guide didn't work. Follow carefully the guide. Then after you get everything, you may change the IMEI using tool found here . After that, follow my thread to flash everything possible to get all the connection back.
slaveration said:
Did you try this guide to restore baseband/IMEI/MAC etc first? You may also use this QCN in case the XQCN in the guide didn't work. Follow carefully the guide. Then after you get everything, you may change the IMEI using tool found here . After that, follow my thread to flash everything possible to get all the connection back.
Click to expand...
Click to collapse
That QCN file was vital! Thank you so much! Now all there's left to do is fix the signal! I've successfully got my IMEI numbers back and the baseband!
keshavkd said:
That QCN file was vital! Thank you so much! Now all there's left to do is fix the signal! I've successfully got my IMEI numbers back and the baseband!
Click to expand...
Click to collapse
Yes that's great! Follow my thread and flash some needed files. Next time please make a full nandroid backup before doing anything okay
Hi! I have successfully revived a GS3 motherboard after it was dead because of SDS using this tool. As everything was wiped from it and replaced with zeroes I have lost original EFS (the former owner didn't root it so ... no backup of EFS). I flashed stock ROM via Odin (Baseband version is I9300BVUGNB2 and it's I9300XXUGPE1 firmware). I saw that others are having even a missing baseband version but mine is here. The IMEI is generic (0049...), when enabling Bluetooth I get a reboot, Samsung Internet and com.google.android.gapps are force closing and there's such a big delay between the time I'm pressing any button to wake the screen and the screen wake up.
1. I have no backup (obviously)
2. I have a working S3 with I9300XXLFB modem and I tried to restore its EFS to my other S3 motherboard with no luck
3. Don't tell me to flash stock ROM via Odin as it's obvious that a stock ROM won't restore a unique number which is missing from it's place. Or will it? Is it hardwritten somewhere in the memory?
4. No Samsung Service here in my city (and I'm not planning to search all over Romania for a service... I don't think it even exists )
What can I do to restore that backup? Also how can I change the IMEI back to original (I have it written on the paper) because I don't want to get the same IMEI on two devices
P. S. The other EFS is my property so I'm not breaking any rules or laws because I'm using it's base to repair another phone. Then I will change it to original. I hope I won't need to use the backup maybe it will work another way. How the services are repairing you broken EFS? ?
Any help would be greatly appreciated
The first thing to do is flash a stock firmware. Have you tried the recovery mode in kies?.
shivadow said:
The first thing to do is flash a stock firmware. Have you tried the recovery mode in kies?.
Click to expand...
Click to collapse
I have successfully written my IMEI and SN but now I'm getting 2 issues:
1. Not registered in the network
2. When turning on Bluetooth on 4.1 it won't turn on and on 4.3 it will freeze the device. Now I'm trying to fix the first one but the second one I couldn't fix. Any ideas? Should I rewrite BT MAC address too to fix it?
How did you write the imei to the phone?
minealex2244 said:
I have successfully written my IMEI and SN but now I'm getting 2 issues:
1. Not registered in the network
2. When turning on Bluetooth on 4.1 it won't turn on and on 4.3 it will freeze the device. Now I'm trying to fix the first one but the second one I couldn't fix. Any ideas? Should I rewrite BT MAC address too to fix it?
Click to expand...
Click to collapse
I have just fixed the network error but... BT is still freezing my phone
No IMEI Fix?
minealex2244 said:
I have just fixed the network error but... BT is still freezing my phone
Click to expand...
Click to collapse
minealex2244 said:
I have successfully written my IMEI and SN but now I'm getting 2 issues...
Click to expand...
Click to collapse
audit13 said:
How did you write the imei to the phone?
Click to expand...
Click to collapse
Why did you marked the thread as [SOLVED] & don't you answer @audit13's question & maybe help an other user with the same problem finding this thread?
As for your Bluetooth freezing problem I would say flash stock Samsung again after Formatting Data (not wipe see https://twrp.me/faq/datamedia.html for an explanation of the difference) & try an other modem.
I am running on S3 i9300 the I9300XXUGOK1 modem (2015-Nov-25) which I attached to this post as well as I9300UBUGNK1 (2014-Nov-6) & both are more recent than the I9300BVUGNB2 (2014-02-18) that you have on that device @ the present.
***
curiousrom said:
Why did you marked the thread as [SOLVED] & don't you answer @audit13's question & maybe help an other user with the same problem finding this thread?
As for your Bluetooth freezing problem I would say flash stock Samsung again after Formatting Data (not wipe see https://twrp.me/faq/datamedia.html for an explanation of the difference) & try an other modem.
I am running on S3 i9300 the I9300XXUGOK1 modem (2015-Nov-25) which I attached to this post as well as I9300UBUGNK1 (2014-Nov-6) & both are more recent than the I9300BVUGNB2 (2014-02-18) that you have on that device @ the present.
***
Click to expand...
Click to collapse
Thank you for your answer. I have already answered him in PM. I was busy with some exams and I didn't have time to write here something.
To write the IMEI you can use a tool from the web (payment recommended). Something like Chimera Tool or Z3X Pro
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Arnys said:
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Click to expand...
Click to collapse
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
metalfangs said:
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
Click to expand...
Click to collapse
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that.
And more important, what was full build number for your phone, aka ane-lx3c779, something like that, can you find it? Then I maybe be able to help.
And ,wulda be great if you type down all you did with phone, what used, etc.
Arnys said:
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that..
Click to expand...
Click to collapse
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
metalfangs said:
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
Click to expand...
Click to collapse
Hm, did you tried erecovery method ? Maybe that can fix your problem
metalfangs said:
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Click to expand...
Click to collapse
Hello there brother. May I humbly ask how did you get your bootloader unlocked after downgrading? Can you share some steps please if you don't mind. Thank you
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
What original firmware was on it?Most definitely,always make a full back up first thing.
Surgemanxx said:
What original firmware was on it?Most definitely,always make a full back up first thing.
Click to expand...
Click to collapse
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Guille05 said:
I tried to crossflash my G8X to the US Open A11 software and screwed up quite badly during the process. I've had to restore my phone from having no partitions and do not have the original LUN5 files, only the 7 required for the crossflash. I've also rooted and installed twrp on this device so if anything that could help needs that I'm able to use it.
I expected the fingerprint sensor not to work, however now the light sensor, accelerometer, gyroscope, magnetometer, etc. don't work either.
Is there something I can do to get this functionality back? I've mostly given up on fixing the imei and network issues but I would like to at least have the phone in a usable state on Wifi.
If more details are needed please do tell and I will do my best to provide them.
Click to expand...
Click to collapse
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
mclarenf195 said:
The same thing happened to me, I came from a10 sprint and installed a11 from Canada, I was left without a network and without a fingerprint sensor, but the other sensors work without problem, to fix network and ntcode I think it is only possible by box, I don't know if of the fingerprint sensor is caused by the lack of serial and imei.
if you come up with a solution let me know bro
Click to expand...
Click to collapse
Did you restore your 7 bin files after flashing the A11 software?
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
They don't have a backup,that's the reason I ask what version software it was.
Guille05 said:
It was originally on version 20p of the sprint software. And yeah, I definitely hadn't quite read up on all of the important things I needed to backup beforehand.
Click to expand...
Click to collapse
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Guille05 said:
Did you restore your 7 bin files after flashing the A11 software?
Click to expand...
Click to collapse
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Surgemanxx said:
Use this firmware.It will correct your issues.
Download LG Firmware for LG G8X ThinQ LMG850QM _Unknown kdz stock USA Rom
Download _Unknown KDZ stock firmware for download with direct link
lg-roms.com
Click to expand...
Click to collapse
I've got version 30c of that firmware installed, you think going back one update would fix it?
mclarenf195 said:
I have the backup of the 7 partitions but they are useless if all the original partitions have been deleted, that is what I understand, I restored the partitions of a KDZ a10 and then flashed it to a11
Click to expand...
Click to collapse
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Guille05 said:
I've got version 30c of that firmware installed, you think going back one update would fix it?
Click to expand...
Click to collapse
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Surgemanxx said:
Yes,go to 30b it will all work.I tried 30c on my sprint model,and had issues with network connectivity as well.
Click to expand...
Click to collapse
I have the 30a, it would be to try
Guille05 said:
When you flashed the A10 kdz, you followed netmsm's guide right? Did you get any errors when flashing the partitions with fhloader? When I extracted the kdz a few files were missing from the ones used by that code but every kdz I've extracted doesn't have them either.
Click to expand...
Click to collapse
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
mclarenf195 said:
yes, the netmsm's guide, fhloader only use it to restore the luns, restore the kdz partitions one by one with qfil, just try what Surgemanxx suggested first and tell me how it goes.
Click to expand...
Click to collapse
It works very well.I tried 30c,and noticed it was slow and laggy and rolled back to 30b and it worked flawless.Fingerprint scanning and all worked with a T-Mobile sim with no issues.They should be good with 30b,all but the IMEI issue they have.
All right I completely erased the flash again and reinstalled following the steps very carefully. I'm now on 30b and can confirm that the sensors work once again. Although the major issues I think were deeper than just the update, because I updated before doing a full erase and it still wasn't working. Now I just have to keep trying to fix the IMEI and FP sensor.
Also I think I may have found my IMEI number thanks to having the ftm partition backed up and therefore still having the serial number. The first 8 digits are always 35886110 for the LG G8x sprint model (and maybe others in the US), the next 6 are the last 6 digits of the serial and the last one is a check digit that you can look up online. I've checked the number on multiple sites and it seems legit so I hope it's actually my number. Now I'll try to write it to the phone somehow, but at least having the IMEI back is a very big step forward.
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Guille05 said:
IMEI is fixed, or at least it appears as such in the phone. I went through with the tutty method of installing the IMEI, and after much trouble (and tutty saying error to my command to write the IMEI) I was able to restore the IMEI to the phone. I confirmed this first using EFS Pro and going into qualcomm NV tools. The IMEI was still as 0 in my phone but after putting in a sim it appeared in the OS and has stayed there. However it still appears as permanently locked when a sim is inserted and the nt-code error does still happen, so the network doesn't work yet.
Click to expand...
Click to collapse
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Surgemanxx said:
That LUNS backup is for the Sprint U.S. model G850UM9.The IMEI is stored in modemst1 and 2 which is LUNS5 that I didn't include for that reason.The NT Code error shouldn't be there if it's the same model/region.Keep me posted.
Click to expand...
Click to collapse
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Guille05 said:
I've flashed your backups and the NT Code error indeed disappeared. However I've still got the perm locked error (so my doesn't work), and the fp sensor still refuses record fingerprints. Was your phone network unlocked when you made that backup? Idk if that maybe interferes with the sim or something
Click to expand...
Click to collapse
Yes,it was network unlocked for sure.You're not the only one that has faced this after trying to repair the IMEI.It's perma blocked because it's embedded in the chipset itself,and so far I haven't seen any fix for it as of yet.