Hello , Xda users
Last night trying to root my device I thought that its a international version and but isn't what exactly happened is that I just f****d up with my g4 h818n By following rooting guide ( http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765) and what I really did is that I mistakenly flashed system.img of a (h815)_international model into my Indian(h818n) and now I just losted IMEI no. of sim 2nd and even sim 1st isn't working at all and
I am getting some random Emergency Signals without/with SIM Card inserted And keep showing emergency calls only ,
I know it so bad I just want to fix so what should I do >??? Should I have to flash stock firmware ?? or what Please help me
You can try flashing original KDZ for your variant.
You are now in the realms of hard bricking your phone, proceed with extreme caution.
I suggest flashing KDZ for your phone and hope that your phone is recovered.
if the problem still persists, in my previous experience with galaxy S3, if the efs partition is broken, IMEI will be gone and network is unusable except for SOS call. this is irreversible without the partition backup.
Sent from my Nexus 7 using Tapatalk
imarcel99 said:
You can try flashing original KDZ for your variant.
Click to expand...
Click to collapse
Yea i jut downloaded India H818N 10F.kdz This file for my variend Hope it would work (crossfingers)
aquavalanche said:
I suggest flashing KDZ for your phone and hope that your phone is recovered.
if the problem still persists, in my previous experience with galaxy S3, if the efs partition is broken, IMEI will be gone and network is unusable except for SOS call. this is irreversible without the partition backup.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
so, if I wasn't able to fix up with flashing KDZ file then it impossible , I am under warranty will lg care help me for it ??
INDMAFIA011 said:
so, if I wasn't able to fix up with flashing KDZ file then it impossible , I am under warranty will lg care help me for it ??
Click to expand...
Click to collapse
Under warranty probably. If it arrives at their repair shop mysteriously bricked somehow, but with no hardware damage, they have the ability to reflash/replace the necessary parts and get it back to you.
Solution
waylo said:
Under warranty probably. If it arrives at their repair shop mysteriously bricked somehow, but with no hardware damage, they have the ability to reflash/replace the necessary parts and get it back to you.
Click to expand...
Click to collapse
aquavalanche said:
I suggest flashing KDZ for your phone and hope that your phone is recovered.
if the problem still persists, in my previous experience with galaxy S3, if the efs partition is broken, IMEI will be gone and network is unusable except for SOS call. this is irreversible without the partition backup.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
barrygoddard said:
You are now in the realms of hard bricking your phone, proceed with extreme caution.
Click to expand...
Click to collapse
imarcel99 said:
You can try flashing original KDZ for your variant.
Click to expand...
Click to collapse
i think I doesn't messed up with my EFS folder. and I Just flashed the Stock KDZ File and wonderfully Its worked .
thank you all for your support devs
Related
I've got this situation with my LGOG E975: a week ago i turned it on and after like 20 seconds after STOCK ROM was running , it rebooted.Then I also noticed the IMEI had gone. I wasn't rooted and the bootloader was locked. I tried everything from hard reset to flashing stock kdz. The only solution to the reboots is to flash teenybin and then a custom rom. Although I have no service and no IMEI. It's like having a 32 gigs ipod, almost useless. Also warranty was voided because the phone was disassembled.
Reading around the internet seems a EFS related issue but I have no idea how to fix it
Whats your advice? Hardware or software fault?
PS Also I noticed that ,with the stock rom, it doesn't scan the memory at startup, like it used to do.
Any help/idea would be appreciated!
Use ur EFS backup... U do have one?
Sent from my Optimus G using Tapatalk
Go to a gsm service and jtag it.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
davevinci said:
Use ur EFS backup... U do have one?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
nope:crying:
http://forum.xda-developers.com/showthread.php?t=2436647
http://forum.xda-developers.com/showthread.php?t=2510349
same problem here
Same problem here using stock rom and no root.
Phone reboot after a few seconds and no signal, no IMEI.
Is there a way to backup my data/photos in LG Recovery Mode ?
When the phone boots up I can see the files on pc but not enough time to save.
kimitza said:
Go to a gsm service and jtag it.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
Click to expand...
Click to collapse
I have jtag but it's possible to restore imei for our device(only for htc devices).Only bootloader.
Search for someone with OCTOBUS BOX.
solution suggest
Rockguy40 said:
I've got this situation with my LGOG E975: a week ago i turned it on and after like 20 seconds after STOCK ROM was running , it rebooted.Then I also noticed the IMEI had gone. I wasn't rooted and the bootloader was locked. I tried everything from hard reset to flashing stock kdz. The only solution to the reboots is to flash teenybin and then a custom rom. Although I have no service and no IMEI. It's like having a 32 gigs ipod, almost useless. Also warranty was voided because the phone was disassembled.
Reading around the internet seems a EFS related issue but I have no idea how to fix it
Whats your advice? Hardware or software fault?
PS Also I noticed that ,with the stock rom, it doesn't scan the memory at startup, like it used to do.
Any help/idea would be appreciated!
Click to expand...
Click to collapse
do you know where's your phone from?? I meet a lot optimus G from Korea with this kind of problem when owners tried to flash it with an international ROM (Korean versions use different ROM but you can flash it with international ROM with some CAUTIONS, or you lost your IMEI) look for an able-to-pull-out antena on top of it, next to heaphone jack. if there is one, that's Korean version.
I know one way to recover IMEI for those phones, may be it works for your case:
1. Find out what is your phone REAL version (E97x or F180L,F180K,F180S ...) because it can be changed after you flash new ROM.
2. FInd s.o with the exact version of your phone and beg for the IMEI back up from their phones with this tool
mediafire.com/download/iy0rhx8yv7lkvlb/IMEI_Backup_Restore.zip (cant post links)
3. Restore your phone with that IMEI with the same tool, your phone will have new IMEI and .... service (I hope so)
remember to turn on "USB debugging". the phone will restart after done (may be twice)
Good luck!!
P/S: use at your own risks
bluesight said:
do you know where's your phone from?? I meet a lot optimus G from Korea with this kind of problem when owners tried to flash it with an international ROM (Korean versions use different ROM but you can flash it with international ROM with some CAUTIONS, or you lost your IMEI) look for an able-to-pull-out antena on top of it, next to heaphone jack. if there is one, that's Korean version.
I know one way to recover IMEI for those phones, may be it works for your case:
1. Find out what is your phone REAL version (E97x or F180L,F180K,F180S ...) because it can be changed after you flash new ROM.
2. FInd s.o with the exact version of your phone and beg for the IMEI back up from their phones with this tool
mediafire.com/download/iy0rhx8yv7lkvlb/IMEI_Backup_Restore.zip (cant post links)
3. Restore your phone with that IMEI with the same tool, your phone will have new IMEI and .... service (I hope so)
remember to turn on "USB debugging". the phone will restart after done (may be twice)
Good luck!!
P/S: use at your own risks
Click to expand...
Click to collapse
If it will work I will love you <3
Yeah I think that could be possible.. just make sure the phone EFS u will be copying from is not the same with your network u can't have same IMEI on same network at same time
Sent from my LG-E975 using Tapatalk
davevinci said:
Yeah I think that could be possible.. just make sure the phone EFS u will be copying from is not the same with your network u can't have same IMEI on same network at same time
Sent from my LG-E975 using Tapatalk
Click to expand...
Click to collapse
actually, you dont need IMEI to be the same, just the same kind of version (eg. International ~ E975, AT&T ~E973 ...). we call that "fake IMEI" in our place :lol:
This methods works 100% with korean version, and some of my friends confirm it works on international version, even the AT&T's or Canada's (E973,E970). the most important is to clarify your phone's version, if you did wrong version, you have to "fake baseband". and then everytime you flash a ROM you have to do the 2 fake
bluesight said:
actually, you dont need IMEI to be the same, just the same kind of version (eg. International ~ E975, AT&T ~E973 ...). we call that "fake IMEI" in our place :lol:
This methods works 100% with korean version, and some of my friends confirm it works on international version, even the AT&T's or Canada's (E973,E970). the most important is to clarify your phone's version, if you did wrong version, you have to "fake baseband". and then everytime you flash a ROM you have to do the 2 fake
Click to expand...
Click to collapse
does not work on my e975
Hello to everyone, I was wondering if anyone can help with this. I have a Galaxy Note 2 branded by an Italian company (3hg Italia). It recently received its update to Android 4.3 (update N7100XXUEML2). It was the official update OTA, the phone is not rooted and it had the stock ROM on it. The update somehow messed up my IMEI making it appear as the generic 0049 forcing me on "Emergency calls only" mode. I already tried flashing the same ROM with Odin and repeating the update with KIES, but while the updates always results successful the IMEI remains 0049. I never made a backup of the EFS folder for this phone since I haven't rooted it or flashed any different ROM on it yet. There is any chance that the phone made an automatic backup? I live in the States right now and Samsung tells me I need to ship it back to Italy to have it fixed, but that costs a lot and would take forever, and I would much prefer try to solve the problem locally. Any suggestions would be greatly appreciated, if not for any fix that I can try myself, at least some place on the West Coast that can fix the problem!
Thank you!
Lorenzo
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
rext said:
Oh I forgot to add that because of Hardware problems I recently sent my phone to Samsung and they replaced the motherboard, which fixed the problem I was having. I don't know if that could be related!
Click to expand...
Click to collapse
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
phluid01 said:
Here's solution : http://forum.xda-developers.com/showthread.php?t=2539731
Click to expand...
Click to collapse
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
rext said:
I'm afraid that fix works just if you have your actual IMEI, I instead have the generic IMEI that starts with 0049. But I will check it out! Thanks!
Click to expand...
Click to collapse
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
phluid01 said:
Then you should simply flash another modem from here : http://forum.xda-developers.com/showthread.php?t=2044937 ... flash a custom recovery first.
Click to expand...
Click to collapse
Thank you so much! I'll take a look into it tomorrow and try it!
rext said:
Thank you so much! I'll take a look into it tomorrow and try it!
Click to expand...
Click to collapse
So I found someone nice enough to give me a hand with this situation, but still no luck yet! Here what they say:
At first glance, the EFS data on the phone was corrupt. I re-generated
that data and restored it to the phone without success.
The GSM radio itself is operational, and the firmware for it is
installed and functional. diagnostic data flows to the towers and back
to the phone but it's not reading the IMEI from the copy of
nv_data.bin contained within EFS. I've re-generated and installed
those files as well, again with no luck.
I rolled the device back to it's original factory firmware and radio
baseband, then ran through the update for the radio baseband, which
also regenerates the contents of EFS, and still no luck.
Given the situation, anyone have other suggestions?
I rooted my phone after 15 days the phone crashed with imei null error and i had to pay for motherboard replacement.
that is why every thread about rooting suggest to backup your efs partition.
deadlyheart4u said:
I rooted my phone after 15 days the phone crashed with imei null error and i had to pay for motherboard replacement.
Click to expand...
Click to collapse
Which method did you use to root?
Stumproot
If you had to pay for motherboard replacement, that means you wasnt able to turn the phone on? If its that, they couldnt prove your phone was rooted. If you were able to turn it on, you should simply flash stock and send it to repair center. So they wouldnt notice that phone was rooted. It is not for sure, that root your device made it to be imei NULL.
deadlyheart4u said:
I rooted my phone after 15 days the phone crashed with imei null error and i had to pay for motherboard replacement.
Click to expand...
Click to collapse
Im sorry to hear that we fell for you :crying: but thanks for leting us know, maybe you save some of us.
Can anyone suggest a good method to take a EFS backup? (without a cutom recovery)
robalm said:
Im sorry to hear that we fell for you :crying: but thanks for leting us know, maybe you save some of us.
Can anyone suggest a good method to take a EFS backup? (without a cutom recovery)
Click to expand...
Click to collapse
+1
Have you tried the method described in the #2 post here http://forum.xda-developers.com/lg-g3/development/root-root-lg-g3-easily-purpledrake-lite-t2821000 ?
pagegr said:
Have you tried the method described in the #2 post here http://forum.xda-developers.com/lg-g3/development/root-root-lg-g3-easily-purpledrake-lite-t2821000 ?
Click to expand...
Click to collapse
I have the similar problem as well, my phone couldn't switch on, and only stays at LG logo screen, and only can access fastboot mode.....
I didn't do the EFS back, so I'm planning to send it back to LG to change the motherboard.....
Or, is there any other way to fix it??
I really can't tell, sorry. About EFS, even if you could somehow establish communication between PC and G3 via adb you have to move those two files from SD in order to have them available after going back to stock.
My D850 has been rooted for 2 months my F400S was rooted until I dropped it and my F460S is also rooted. I've never had an issue with imei null error on any of my G3's. Did you do anything that could have caused this?
efs doesn't wipe by itself, if you have IMEI nul that means efs has been corrupted or deleted which is usually due to you doing a mod incorrectly. None of the current root methods will touch efs.
Lennyuk said:
efs doesn't wipe by itself, if you have IMEI nul that means efs has been corrupted or deleted which is usually due to you doing a mod incorrectly. None of the current root methods will touch efs.
Click to expand...
Click to collapse
So as I though and I wrote before. Root is not failure for IMEI Null. So, he should just flash kdz to stock and turn it back. In that way he could say it happen by itself, thats it. No paying for new motherboard.
Okay story so far, got Zuk Z2 from BG China to replace Mi5 that had a tumble
After a couple of weeks I decided to flash Custom Rom (LinageOS *UNOFFICIAL), seemed fine then I lost Network totally on both SIMS.... Zero bars! I've tried all sorts of ROMS and flashes of Baseband firmwares but to no avail. Now I think I've confused myself.
So if anyone has any advice before I cast this device from a high roof it would be most appreciated.
Thank you :good:
You flashed already different basebands via fastboot, erased modem after that?
Tried flash stock ZUI via qfil?
After all no network? IMEI's are there?
iBrumm13 said:
Okay story so far, got Zuk Z2 from BG China to replace Mi5 that had a tumble
After a couple of weeks I decided to flash Custom Rom (LinageOS *UNOFFICIAL), seemed fine then I lost Network totally on both SIMS.... Zero bars! I've tried all sorts of ROMS and flashes of Baseband firmwares but to no avail. Now I think I've confused myself.
So if anyone has any advice before I cast this device from a high roof it would be most appreciated.
Thank you :good:
Click to expand...
Click to collapse
Since you are not first one, I would dare to say that you are toasted...
Lacce said:
You flashed already different basebands via fastboot, erased modem after that?
Tried flash stock ZUI via qfil?
After all no network? IMEI's are there?
Click to expand...
Click to collapse
When it first gave up network I checked IMEI and it seemed to have duplicated them for both sim but after I QFIL back to ZUI 2.5 they returned perfectly... I've gone through the whole erase modemst process but still FUBAR....
Even stripped the device down to bits and checked the internal connections.
He strange part is I get the emergency only msg on sim so guessing the network is recognised but the signal is -90 dBm at best, getting to as bad as -130 dBm.
Even considering writing the IMEI from old bust Mi5 to handset to see if this would help...
Sent from my iPad using Tapatalk
nedooo said:
Since you are not first one, I would dare to say that you are toasted...
Click to expand...
Click to collapse
I noticed it seems to be an inherent issue.... guess that's why this is a cheap powerhouse handset.
Sent from my iPad using Tapatalk
try to flash stock zui rom and prepare china and INT baseband for testing.
iBrumm13 said:
I noticed it seems to be an inherent issue.... guess that's why this is a cheap powerhouse handset.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Yup seems like blame lab rat for not surviving experiment gone wrong
nedooo said:
Yup seems like blame lab rat for not surviving experiment gone wrong
Click to expand...
Click to collapse
Yeah I guess every other android and iOS device I've either rooted or jail broke was pure luck and the huge amount of posts on many sites including Lenovo regarding this baseband problem are all very similar 'lab rat' experiments.
Thanks for the constructive advice and answering my plea, great to know that xda developers are attracting helpful and intelligent like minded users and owners....
Sent from my iPad using Tapatalk
Same problem here. Anybody please share the QCN backup (or valid link to download this) to try repair QCN and IMEIS ?
seventech said:
Same problem here. Anybody please share the QCN backup (or valid link to download this) to try repair QCN and IMEIS ?
Click to expand...
Click to collapse
I had a dabble with QCN and managed to replace corrupt IMEI's but still didn't help. Can't be sure the BASEBAND was correct though.. I'm yet to try a full FACTORY DEFAULT configuration as suggested but will be this week.
Been suggested the IMEI may be blocked for some reason but seems unrealistic as it was working prior to FLASH.
iBrumm13 said:
I had a dabble with QCN and managed to replace corrupt IMEI's but still didn't help. Can't be sure the BASEBAND was correct though.. I'm yet to try a full FACTORY DEFAULT configuration as suggested but will be this week.
Been suggested the IMEI may be blocked for some reason but seems unrealistic as it was working prior to FLASH.
Click to expand...
Click to collapse
I see other tutorial for zuk z2 pro with good QCN backup and the problem was solved. I need the good QCN backup to try here.
seventech said:
I see other tutorial for zuk z2 pro with good QCN backup and the problem was solved. I need the good QCN backup to try here.
Click to expand...
Click to collapse
I second that!! The search continues... :good:
iBrumm13 said:
I second that!! The search continues... :good:
Click to expand...
Click to collapse
Oh my god... i find !
Any luck with a good QCN configure..
Did you fix your problem iBrumm13 ?
I have OnePlus 9 pro t mobile, I was using eu rom normally, when eu network problem gave, I returned to tmo via msm in hopes that the network problem would be solved. but i keep getting this error t mobile team They said that there is no problem, the network can be unlocked, please try again. , please help someone , i checked the imei on the back of the device and the same inside . If anyone has encountered this problem before, can you tell me the solution? Whatever the solution is, I'm ready to do it, I couldn't solve the problem no matter what I did, eu network didn't work, I tried custom rom, but the result is that I can't get the same network and I don't have a t mobile sim card. Please someone help with this. Is there any file that I can remove this lock on the computer? My English is a bit bad, sorry about that. I'm ready to give 50 euros to the person who can solve this problem, please help.
Under settings/about phone/status what do you see?
TheGhost1951 said:
Under settings/about phone/status what do you see?
Click to expand...
Click to collapse
selimo21 said:
View attachment 5814737
Click to expand...
Click to collapse
Have you tried going into settings/system and resetting network settings?
TheGhost1951 said:
Have you tried going into settings/system and resetting network settings?
Click to expand...
Click to collapse
yes i tried and no result
Something happened to the phone, now I'm getting this error, what happened? can someone help?
Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO
TheGhost1951 said:
Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO
Click to expand...
Click to collapse
I couldn't find the file you mentioned, can you help me? can you link the file
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Quick Google search
TheGhost1951 said:
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Quick Google search
Click to expand...
Click to collapse
I flashed it and the result is wrong, I still get the error you see above.
selimo21 said:
I flashed it and the result is wrong, I still get the error you see above.
Click to expand...
Click to collapse
Time to MSM to your original model number....
TheGhost1951 said:
Time to MSM to your original model number....
Click to expand...
Click to collapse
i did the result did not change , if i flash custom rom can i fix network eg pixel experience rom ?
How long was it working on Eu rom before it gave you a problem? Maybe you temporarily sim unlocked the phone for 30 days and that ran out?
OnePlus says you must go through tmobile to get it unlocked. Tmobile does need it on their network for a day or so to be able to unlock it. (They tried to do mine manually but there was no data for my phone and there is an exchange that takes place on their server so it has to be online).
Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.
I also had the same problem on OP9. It happened after playing with modemst partition.
joecool1029 said:
Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.
Click to expand...
Click to collapse
Unfortunately I don't have my own modem backups. but someone else has a backup, what can i do? please help me
ElitePotato said:
I also had the same problem on OP9. It happened after playing with modemst partition.
Click to expand...
Click to collapse
did you solve the problem? I have someone else's backup, do I have a chance to use it, please help
I have all the modem related imgs for A12 TMO if needed OP9P
TheGhost1951 said:
I have all the modem related imgs for A12 TMO if needed OP9P
Click to expand...
Click to collapse
Thank you very much for this. Finally, I'm thinking of taking a twrp backup and installing it. I've tried everything with modem backups and the result is unsuccessful I hope someone can fix this problem.
selimo21 said:
Something happened to the phone, now I'm getting this error, what happened? can someone help?
View attachment 5814789
Click to expand...
Click to collapse
Take ur SIM out then restart and connect to a US VPN and try again
L0ND0NB0Y said:
Take ur SIM out then restart and connect to a US VPN and try again
Click to expand...
Click to collapse
unfortunately i tried that too. this problem happened because i deleted modemst1 and modemst2 file in eu rom. I guess the tmo unlock application cannot read the phone's information so the unlock is refusing to bind.