Hello guys! Anyone knows how to erase NVM for these phones?
Few days ago I repaired IMEI for LG E510 and E400. I used RiffBox and LGTool.
First I dumped full with RiffBox just in case. Than I made full flash chip erase,resurrected boot. Than I flashed with LGTool and phone was alive without IMEI. I wrote NVM from live phone and success. Phone has repaired IMEI.
Now I have a barred P700,but I dont want to spend so many hours dumping full and soldering wires.
Is there a way to erase NVM data? LGTool doesn't write NVM,if the NVM in phone is in working condition,but I need to repair IMEI.
Related
Hello to all. I'm trying to fix my friend's s4 i9505 because it shows that it's Baseband is Unknown and IMEI is null/null.
He told me the baseband and imei changed when he upgraded to 4.3 using wifi.
I have tried to flash stock rom but unfortunately the phone is in 4.3 so no downgrade.
I have tried flashing different modem.bin but still no avail.
He did not back up his EFS folder before upgrading to 4.3 but I still looked at the folder anyway.
I noticed that inside the EFS folder, there is no nv_data.bin and md5 file which is I think needed for the IMEI.
Is there a free way of recovering these files?
Is this a hardware failure?
I tried the different methods on recovering IMEI in the forums but all of them involves those 2 files so I can't continue.
I have another friend who has a i9500, can I copy and use his nv_data files? (He is willing to do it BTW to help my friend)
FYI: WIFI, Bluetooth and other functions are OK. It's just the call an text function which do not work.
Currently in JB 4.3 XXUEMJ5
No more warranty on the phone.
Any help would be greatly appreciated.
Thank you for taking the time to read our problem.
thetruth34 said:
Hello to all. I'm trying to fix my friend's s4 i9505 because it shows that it's Baseband is Unknown and IMEI is null/null.
He told me the baseband and imei changed when he upgraded to 4.3 using wifi.
I have tried to flash stock rom but unfortunately the phone is in 4.3 so no downgrade.
I have tried flashing different modem.bin but still no avail.
He did not back up his EFS folder before upgrading to 4.3 but I still looked at the folder anyway.
I noticed that inside the EFS folder, there is no nv_data.bin and md5 file which is I think needed for the IMEI.
Is there a free way of recovering these files?
Is this a hardware failure?
I tried the different methods on recovering IMEI in the forums but all of them involves those 2 files so I can't continue.
I have another friend who has a i9500, can I copy and use his nv_data files? (He is willing to do it BTW to help my friend)
FYI: WIFI, Bluetooth and other functions are OK. It's just the call an text function which do not work.
Currently in JB 4.3 XXUEMJ5
No more warranty on the phone.
Any help would be greatly appreciated.
Thank you for taking the time to read our problem.
Click to expand...
Click to collapse
This phone isn't that old! I have only today contacted Samsung as there is nothing in my EFS folder, they are sending out a jiffy bag for me to send the phone to them to repair under warranty!
Be careful talking about swapping efs partitions from phone to phone as the mods in here get funny about it, I would try contacting Samsung to return it if you can? When did you get it?
I would suggest you do the same. I can't fix mine either.
thetruth34 said:
Hello to all. I'm trying to fix my friend's s4 i9505 because it shows that it's Baseband is Unknown and IMEI is null/null.
He told me the baseband and imei changed when he upgraded to 4.3 using wifi.
I have tried to flash stock rom but unfortunately the phone is in 4.3 so no downgrade.
I have tried flashing different modem.bin but still no avail.
He did not back up his EFS folder before upgrading to 4.3 but I still looked at the folder anyway.
I noticed that inside the EFS folder, there is no nv_data.bin and md5 file which is I think needed for the IMEI.
Is there a free way of recovering these files?
Is this a hardware failure?
I tried the different methods on recovering IMEI in the forums but all of them involves those 2 files so I can't continue.
I have another friend who has a i9500, can I copy and use his nv_data files? (He is willing to do it BTW to help my friend)
FYI: WIFI, Bluetooth and other functions are OK. It's just the call an text function which do not work.
Currently in JB 4.3 XXUEMJ5
No more warranty on the phone.
Any help would be greatly appreciated.
Thank you for taking the time to read our problem.
Click to expand...
Click to collapse
try to flash latest modem twice (MKF or MKE) twice. first flash un-tick "auto-reboot".
benbird7 said:
This phone isn't that old! I have only today contacted Samsung as there is nothing in my EFS folder, they are sending out a jiffy bag for me to send the phone to them to repair under warranty!
Be careful talking about swapping efs partitions from phone to phone as the mods in here get funny about it, I would try contacting Samsung to return it if you can? When did you get it?
I would suggest you do the same. I can't fix mine either.
Click to expand...
Click to collapse
Should I try this too? I've just seen on Samsung website that mobile phones are covered for 24 months. I've only had this 8 months.
It's weird I have imei number when I type *#06# but nothing in efs folder!
Sent from my GT-I9505 using xda app-developers app
Thanks for all the replies. I tried to check it with my local technicians and all of them told me that my main board needs to be replaced.
I didn't know that a software mishap can result to a hardware failure to the extent of changing the main board.
I have tried flashing the recommended modems above but unfortunately still does not work.
I have noticed that when I type *#1234# in the Phone app, It shows me the AP and CSC and that is all written in the screen. No word modem and no modem version.
When I try to flash a firmware or a modem it says it flashed successfully but when I check the phone, still no service.
Again, wifi, bluetooth and other phone functions are working.
Technicians told me it is a "no service" unit and "cannot be fixed by software" because I have a "broken baseband/modem".
Is there really no hope for this unit?
Again any help or info is welcome.
Thank you for reading friends.
Bump
What do you want anyone here to say if you've been told by someone qualified that it needs a motherboard replacement ? In some (many ?) countries, this would be fixable by 're-writing' the IMEI to the device (either by a Samsung service centre or other repairer), but if that's not possible for whatever reason in your country & the way they fix it is a motherboard replacement, you don't really have any other option, do you ?
Edit - Attempting to move EFS files between devices normally ends up in both being blacklisted. Not recommended.
Hello,
I have exactly the same problem, with the i9505 phone version, do i have to change the motherboard or it can be fixed the "soft way"?
I was having the dreaded "Sim card not detected" message and decided to try replacing the mainboard of my Koodo/Telus S4 SGH-i337m with another from the exact same model but different company.
I rooted the phone (etc) and used the tool at http://forum.xda-developers.com/gal...ool-antaresone-s-imei-backup-restore-t2975136 to do a complete backup of the EFS and stuff
I was able to swap out the boards with no trouble and confirmed the newly repaired phone had an IMEI before doing a restore using the above tool as well, but after doing so, the IMEI says Unknown.
I put the phone into DM mode and enabled cp logging in recovery so the phone could be recognized by Windows (otherwise it was saying USB Device Not Recognized)
I tried Octoplus and it can get the software and firmware info from the phone, but does nothing else. NV Items reader writer gives an "Unknown Command" error for even just reading the full phone.
Not sure what I need to do to fix this. Thinking about contacting an unlocking guy here in Canada who says he can repair the IMEI remotely, but I don't want to do that if it's something simple I'm overlooking. Unfortunately most of the documents talking about IMEI repair refer to options that don't exist in my service menu (for example #6 Common and turning off FTM mode). Would appreciate any help.
The backup method is for the i9505 and I understand that, hardware-wise, the i337m has the same hardware but the major difference is support for LTE frequencies in Canada.
You tried to restore the imei from the original motherboard to the replacement motherboard? Do you have a back up of the replacement motherboard's imei information?
With the s4, I don't think all of the imei information is in the efs folder. Nvdata may be written in a hidden partition.
Yup I took a backup of both before doing anything
The tool I linked to says it supports the i337m and it detected it and did not complain at all.
audit13 said:
The backup method is for the i9505 and I understand that, hardware-wise, the i337m has the same hardware but the major difference is support for LTE frequencies in Canada.
You tried to restore the imei from the original motherboard to the replacement motherboard? Do you have a back up of the replacement motherboard's imei information?
With the s4, I don't think all of the imei information is in the efs folder. Nvdata may be written in a hidden partition.
Click to expand...
Click to collapse
The tool backed up several partitions it seems, not just the efs.
Just an FYI. Both motherboards are for Canadian models. My original was with Koodo and the new one is from Bell. Both are identical. It shouldn't have a problem with that.
You tried to restore your old imei to the replacement board? Any particular reason this was necessary? Both motherboards were running the same ROM although I'm not sure this makes a difference.
I wanted to keep it as close to the original as possible (guess I'm a bit OCD like that lol) and I'm pretty sure the seller I bought it from on eBay set the imei on it to a fake number, as I checked it online and nobody had any information on it (whereas my original Imei was recognized as coming from an s4).
Did you try flashing a stock rom on the replacement motherboard? If that doesn't restore the imei and you don't have the replacement's original imei, you may be out of luck.
You confirmed that the replacement is an i337m in download mode?
I am trying a stock Bell firmware using odin now and will then restore the imei backup I took of the new motherboard to see what happens.
Trying to restore the imei backup from the Koodo phone may make it worse.
After flashing a stock rom, check to see if wifi and Bluetooth works before trying to restore the imei.
audit13 said:
Trying to restore the imei backup from the Koodo phone may make it worse.
After flashing a stock rom, check to see if wifi and Bluetooth works before trying to restore the imei.
Click to expand...
Click to collapse
Still working on it, but previous attempts have had absolutely no other issues. Wifi, camera, et al have worked fine.
Okay so I flashed back the Bell stock firmware and my backup of the new motherboard, and the IMEI is back, but I am almost 100% sure it's a fake one. None of the sim unlock methods work and online tools cannot identify it. It's not the old 0049 or any other known fake/invalid one, which is quite weird.
Which method are you using to sim unlock?
I just purchased an unlock code for my original imei and am stuck at this point unless I can figure out why it doesn't work on the new motherboard.
Unlock codes are tied to the imei. Since you can't get your imei into the replacement board, you can't use the unlock code.
Also, some carriers can detect an altered imei and will not activate the phone on their network. Not sure if this is always the case.
We dont support nor allow discussion of imei changing, thread closed.
Hi, after by accidently flash my mi a1 with the factory.bat and lost my imei and the persist partition finally i was able to recover my Imei but i have no signal still, there is a fix for this?
Sorry for the bad english btw
Have you tried restarting your device?
gsnmartinh said:
Hi, after by accidently flash my mi a1 with the factory.bat and lost my imei and the persist partition finally i was able to recover my Imei but i have no signal still, there is a fix for this?
Sorry for the bad english btw
Click to expand...
Click to collapse
Check your imei ID and imei slot!
Because you used the factory.bat you destroy the persist data and of course the IMEI information.
Whoever put the MyFlash script factory.bat would deserve to kick it.
I made the same mistake, I got my mobile started with the instructions, see. below.
Here's the solution: https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
hey guys..
anyone has qcn for this device..? or rooted device and i need modemst parts. for repairing my device imei.. it is NULL..
t-mobile_mda said:
hey guys..
anyone has qcn for this device..? or rooted device and i need modemst parts. for repairing my device imei.. it is NULL..
Click to expand...
Click to collapse
What happened to your device losing this information? Could you tell what version of Android it is on? Add a print screen with the screen where the IMEI Null is displayed.
I lost the IMEI on my device, but after a few hours of work I was able to recover it.
I can try to help you.
I somehow erased my IMEI (it shows 0 in Settings) after flashing custom ROMs. I have no way to restore it as I did not backup the efs partition and I can't find the box for the phone with the IMEI sticker on it. I wiped modemst1 and modemst2 but that didn't change anything. I still have service but I'm worried I might get into legal trouble for using a phone without an IMEI. I also can't send it to ZTE as I can't be without a phone for days/weeks. Should I keep the phone or get a new one?
Odd that you still have service... I would keep using it.
same thing here on two boards. no luck with service on either, though. (Tmobile) both have no imei, no serial. fortunately, i have another DD axon and 1 body to test and work on the two boards. the best theory i have is to use QPST to backup .qcn and restore it. i feel like imei and serial are stored in the qfuse system. i cannot, however find a detailed answer on how to do that aside from videos and posts here and there that claim CDMA workshop ($100) will fix/restore it. my belief is that there is a function within qpst and qfil to do this, but i cant get my handset booted and recognized in a mode that allows such. there is also the lack of detail on how to boot into diagnostic mode (which i thought was EDL, but that doesnt work). really, i wish someone from ZTE would just say here is the factory image file (not edl, the whole emmc flash file) and this is how you flash it. Wishful thinking, i know.
so in a strange twist of events, restoring my efs backup reflashing b35 edl, despite it breaking touch, wiping data and flashing b29 edl (which restored my touch) netted me my IMEI back. i dont know why, but it did. finally. month long task finally back.
@bkores did you figure it out?
EDIT: i finally restored mine. took updating to b35 and wiping internal to register again for some weird reason. but its back.