I am really hoping someone can help me sort this problem. I recently bought a LG P970, and after long await from customs, i received it! On day 1 before even purchasing a simcard i rooted and changed roms. I went through all sorts of roms from nightly cm7 to cm10, nove, aokp etc.. I finally decided i like AOKP Rom and day 2 bought my sim card. SUPRIZE!! no network! IMEI unknown. Unfortunately i was to ignorant to do a backup and i have been searching for +- 40hours now to try resolve this issue.
I have tried the tutty/Hyperterminal.. Does not work! If i dial 3845#*970# and access the hidden menu. as soon as i select CP USB, the pc just makes the insert/ takeout sound constantly and does not install driver, but on AP USB, the sd card can be accessed, my device shows on system and everything is 100%. I have tried this on 2 windows 7 computers. So that option is out.
Does anyone know another way to restore the IMEI? I dont have any fancy box tools, just my pc.
jugz54 said:
I am really hoping someone can help me sort this problem. I recently bought a LG P970, and after long await from customs, i received it! On day 1 before even purchasing a simcard i rooted and changed roms. I went through all sorts of roms from nightly cm7 to cm10, nove, aokp etc.. I finally decided i like AOKP Rom and day 2 bought my sim card. SUPRIZE!! no network! IMEI unknown. Unfortunately i was to ignorant to do a backup and i have been searching for +- 40hours now to try resolve this issue.
I have tried the tutty/Hyperterminal.. Does not work! If i dial 3845#*970# and access the hidden menu. as soon as i select CP USB, the pc just makes the insert/ takeout sound constantly and does not install driver, but on AP USB, the sd card can be accessed, my device shows on system and everything is 100%. I have tried this on 2 windows 7 computers. So that option is out.
Does anyone know another way to restore the IMEI? I dont have any fancy box tools, just my pc.
Click to expand...
Click to collapse
The AOKP hasn't been updated in a while and has more bugs than CM10 and V30 repacks.
When did this start? You can only wipe IMEI if you select "Wipe Entire AP" or something like that on SFT. Does the problem persist on other ROMs? Also no network connection isn't related to IMEI, more likely ROM related.
If your really desperate you can extract your nv partition and hex edit your IMEI in and push back to device. All you need is microusb to usb cable and computer (and a hex editor, but thats free to download ), but I will only do this as a last resort.
xonar_ said:
The AOKP hasn't been updated in a while and has more bugs than CM10 and V30 repacks.
When did this start? You can only wipe IMEI if you select "Wipe Entire AP" or something like that on SFT. Does the problem persist on other ROMs? Also no network connection isn't related to IMEI, more likely ROM related.
If your really desperate you can extract your nv partition and hex edit your IMEI in and push back to device. All you need is microusb to usb cable and computer (and a hex editor, but thats free to download ), but I will only do this as a last resort.
Click to expand...
Click to collapse
Thanks for you reply,
When i bought the phone, before i put in a simcard, i ended up flashing and changing roms, so the next day i bought a sim and there was no network, did research and found out that my IMEI is missing. if i type *#06# then is just says IMEI and no number. I have flashed back to original rom but still no luck. I have tried many things on youtube but nothing works, i tried the tutty to try restore an IMEI but doesn't work,
What do you suggest i do? and is there a step by step guide to resolving this?
jugz54 said:
Thanks for you reply,
When i bought the phone, before i put in a simcard, i ended up flashing and changing roms, so the next day i bought a sim and there was no network, did research and found out that my IMEI is missing. if i type *#06# then is just says IMEI and no number. I have flashed back to original rom but still no luck. I have tried many things on youtube but nothing works, i tried the tutty to try restore an IMEI but doesn't work,
What do you suggest i do? and is there a step by step guide to resolving this?
Click to expand...
Click to collapse
This will only work with the P970
Use adb shell from your computer or use a app like terminal emulator.
Code:
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
where $IMEI is you IMEI
The large bold print is for people that can't read headings that might run this and brick their devices.
Something I learned that isn't mentioned on the forum is that its important to backup your nv partition since that contains info that can't be retrieved after damaging it and nothing backs it up for you. Like MAC addresses, your IMEI etc.
On you computor
Backup using
Code:
adb pull /dev/block/mmcblk0p11 nv.img
Restore using
Code:
adb push nv.img /dev/block/mmcblk0p11
EDIT: Added notrunc to not truncate the rest of the partition
xonar_ said:
Use adb shell from your computer or use a app like terminal emulator.
Code:
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
where $IMEI is you IMEI
Click to expand...
Click to collapse
Hey, Thanks for getting back to me. I tried the command on Terminal Emulator and it says IMEI not found and conv disabled. Any suggestion?
Did you try the official LG Mobile Update Tool?
There is emergancy and recovery mod where you can fix it.
sbdemir said:
Did you try the official LG Mobile Update Tool?
There is emergancy and recovery mod where you can fix it.
Click to expand...
Click to collapse
I tried the LGMobile Support Tool various times. The recovery module does not work, if i type IMEI adn select check phone, nothing happens. The strange thing is the support tool picks up my phone model as LGKU5900 version V10I. That could have happened with me trying to repair the phone with various programs and youtube videos.
I have tried uninstalling and reinstalling the support tool as well as the drivers but still no luck.... I reflashed the original rom V10F with no patch etc.. but still the Support tool picks up the model as LGKU5900, and when i select update phone, it downloads the update and during installing of update it stays on 6% for roughly 20 minutes then just stops. I have tried this numerous times and same things happens everytime.
If this is of interest to you to, you can take control of my system and check it out via team viewer.
jugz54 said:
Hey, Thanks for getting back to me. I tried the command on Terminal Emulator and it says IMEI not found and conv disabled. Any suggestion?
Click to expand...
Click to collapse
rather try this. included dd might not be up to standard
Code:
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
and replace $IMEI with your IMEI.
EDIT: The above should repair your IMEI, but if SFT fails to update your phone then it's wrong firmware or HW problem and it will cause problems elsewhere aswel.
xonar_ said:
rather try this. included dd might not be up to standard
Code:
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=8 conv=notrunc
echo $IMEI | busybox dd of='/dev/block/mmcblk0p11' obs=1 ibs=1 count=15 seek=4096 conv=notrunc
and replace $IMEI with your IMEI.
EDIT: The above should repair your IMEI, but if SFT fails to update your phone then it's wrong firmware or HW problem and it will cause problems elsewhere aswel.
Click to expand...
Click to collapse
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
jugz54 said:
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
Click to expand...
Click to collapse
dd should be included in busybox. What busybox are you using?
The conv=notrunc just tells it not to truncate the rest of the file (in this case don't truncate the rest of the nv partition)
the echo pipes the IMEI to dd which writes it to /dev/block/mmcblk0p11 (your nv partition) on two different spots. I
You need su permissions to write to /dev/block/mmcblk0p11. I forgot to mention that. Otherwise dd will fail and the included binutils dd doesn't always list error messages. Just terminates silently without doing anything most of the time.
You can also try reflashing just the baseband. (The fls file with SFT)
If all that doesn't work then you need to take it into repairs.
jugz54 said:
Still no luck, it says dd applet not found with the busybox command, and the abouve code i tried {$IMEI | dd of} just disabled my conv, thats all. Do you think the phone has no chance of being network active again?
Click to expand...
Click to collapse
I don't have a solution to your problem however I am in a similar situation. I purchased my Optimus Black from an ebay seller located in Hong Kong, it was advertised as an Optimus Black P970. The software version was similar to yours, outdated, so I grabbed a stable gingerbread version patched it with root etc. and flashed.
Upon reboot I had no cellular network, tried two different sims/networks. No Joy. Further troubleshooting uncovered the loss of the imei. I came across this thread and decided to give it a try, it didn't work. I suspect I messed up the command, in my case this was lucky because I was able to see the content of the mmcblk0p11 file using a hex editor. The imei is in there, and it is also in the same location as my Optimus Black P970, I assume it is stored elsewhere as well....
Long and short of this is you and I have purchased the KU5900, the Korean version not the P970, flashing with P970 firmware is what has messed the phones up.
Note. I did try flashing with the only Korean version that was available to me, a V30 something, that bricked the device. It is now unbricked but still shows no imei. I haven't given up but wading through reams of forum posts trying to get info on this is daunting ... My seller has agreed to replace the phone, but I fear I will end up with another KU5900 which isn't any good to me unless I can upgrade the firmware.
had the same problem recently..got it fixed because of this...
http://forum.xda-developers.com/showthread.php?t=2107419
IAP001 said:
had the same problem recently..got it fixed because of this...
http://forum.xda-developers.com/showthread.php?t=2107419
Click to expand...
Click to collapse
I just fixed one P970 with unknown IMEI by flashing it with Octopus box, I think that you can solve it by flashing with original flash file using SFT.
Best Regards.
Hi....few days back, I had the same problem....After flashing my phone to V30B(CIS version) which was not available for my phone in my country India, the IMEI then got removed automatically(*#06#- shows IMEI not available), then I installed the latest version V20G which was available for my country then (through smartflash tool) and then got back the IMEI. Try installing the latest version available for your country and do let us know if that solve your problem. Best of luck
Sent from my LG-P970 using xda app-developers app
sunnygunjesh said:
Hi....few days back, I had the same problem....After flashing my phone to V30B(CIS version) which was not available for my phone in my country India, the IMEI then got removed automatically(*#06#- shows IMEI not available), then I installed the latest version V20G which was available for my country then (through smartflash tool) and then got back the IMEI. Try installing the latest version available for your country and do let us know if that solve your problem. Best of luck
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
i had similar problem when installing cm10 rom and cici rom, after flashing those roms my device had no IMEI and no network, it didnt even rcognize my contacs in sim card. the strange part is that i was able to make calls, but when i flashed back to the rom i had, everything was back and looking good.
i had marvel v9 rom thats runs pretty good.
I purchased an unlocked, unbranded i9305 S3 LTE and have not been able to back up the NV Data.
I tried this with it completely stock and even though I have tried both settings with DM in Qualcomm USB settings and the port is found in QPST it always says 'No Phone'.
After trying this on several computers, I then installed Clockwork Recovery Mod and Rooted the phone successfully, and still had no luck connecting with QPST with the same 'No phone' message.
I also tried using EFS Pro and the Qualcomm NV Tools, the phone says at first it is connected but the program freezes and then says the phone has disconnected. I tried unticking 'Read Phone version information' and it connects. But as soon as I try to read any data the Rx Tx indicators flash a couple of times in the app and then I get the same Phone disconnected message.
Can anyone help? I have searched here and online and found lots of similar cases but no solutions...
Thank you very much in advance.
Stock ROM 4.1.2
CWM 6.0.2.9
Baseband version I9305BVBLL2
Kernel Version 3.0.31-633241
Build Number: JZO54K.I9305XXBLL5
-------------- SOLUTION -------------------
I managed to work out the solution!
Dial *#9090# and ensure that you have DM/DUN over HSIC selected.
Phone rebooted and was found!
DaveWoolly said:
I purchased an unlocked, unbranded i9305 S3 LTE and have not been able to back up the NV Data.
I tried this with it completely stock and even though I have tried both settings with DM in Qualcomm USB settings and the port is found in QPST it always says 'No Phone'.
After trying this on several computers, I then installed Clockwork Recovery Mod and Rooted the phone successfully, and still had no luck connecting with QPST with the same 'No phone' message.
I also tried using EFS Pro and the Qualcomm NV Tools, the phone says at first it is connected but the program freezes and then says the phone has disconnected. I tried unticking 'Read Phone version information' and it connects. But as soon as I try to read any data the Rx Tx indicators flash a couple of times in the app and then I get the same Phone disconnected message.
Can anyone help? I have searched here and online and found lots of similar cases but no solutions...
Thank you very much in advance.
Stock ROM 4.1.2
CWM 6.0.2.9
Baseband version I9305BVBLL2
Kernel Version 3.0.31-633241
Build Number: JZO54K.I9305XXBLL5
Click to expand...
Click to collapse
I don't own this phone but are you sure you have a Qualcomm processor? From these 2 pages:
http://www.morecellphone.com/phones/samsung-galaxy-s-iii-gt-i9305/304
http://www.gsmarena.com/samsung_i9305_galaxy_s_iii-5001.php
it should have an exynos processor, so those qualcomm tools won't work. (think qualcomms are just some specific models)
Can't you just get into some custom recovery, adb to it from your computer (or terminal emulator) and 'dd' an image from the /efs partition out of it (needs root)?
How i did it:
Opened terminal emulator and typed "mount" to check my mounts. Looked up the one that had /efs on it. It should also say something like "/dev/block/mmcblk0p3" (this is the one on mine, use whatever you got from "mount"). Then do something like:
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
where the "/sdcard" is the directory where you want your efs image to go. Then you just need to copy the efs.img file to a safe place and you're done.
If you need to recover just do the opposite
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3
Careful with the "if" "of" order, and with what you type. dd is a powerful command and it's easy to screw up irreversibly if you overwrite a different partition by accident.
Another method, I've manually copied /efs file contents with root explorer to my sdcard and later to my computer and was able to use them to recover my phone (had an app wiping my /efs by accident).
This is how i did on mine and worked but i've heard those qualcomm's (if you really have one) have a different method and what i'm saying may simply not apply
Thank you for your response. Unfortunately even though it does not have a Qualcomm processor it does use this chipset for the modem I believe.
I've been following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=1946915 but not having any luck. The phone is fine but it is not recognised correctly in QPST or EFS Pro....
I managed to work out the solution!
Dial *#9090# and ensure that you have DM/DUN over HSIC selected.
Phone rebooted and was found!
Can anyone provide me the qcn file for le2 indian version.
I cooked my imei number.
Any links, any help would be appreciated.
Thanks
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
Mr YesNoWhat said:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
Click to expand...
Click to collapse
my phone is not bricked plus i needed the qcn file for imei restoration.
scroll down and find Qualcomm IMEI Fixing Tool
Mr YesNoWhat said:
scroll down and find Qualcomm IMEI Fixing Tool
Click to expand...
Click to collapse
I have tried recovering the imei number by IMEI & SN WRITE but no success most probably its the port fault
The qualcom HS-USB Android DIAG 901D not showing and i have some other ports lined up, namely
Qualcomm HS-USB Diagnostics 9025
Qualcomm HS-USB NMEA 9025
got root and unlocked bootloader?
Mr YesNoWhat said:
got root and unlocked bootloader?
Click to expand...
Click to collapse
it it rooted, the bootloader is unlocked and i even have xposed module working.
I'm having the same issue
https://www.4shared.com/get/UBQdonhrca/x526_qcn_read_by_qpst.html
here you go, qcn for x526
i cant use it since mine is x522 but please pm me if you suceed
sparsh_iris said:
Can anyone provide me the qcn file for le2 indian version.
I cooked my imei number.
Any links, any help would be appreciated.
Thanks
Click to expand...
Click to collapse
I restored my imei through the following steps
1. root your rom
2. enable usb debugging
3. install minimal adb on your computer, goto the folder you installed it in, hold shift then right click, select open command prompt here
4. in command window, enter the following ( each line followed by pressing enter)
5. adb shell
6. su
7. grant su request on phone screen
7b. command prompt should look similar to "[email protected]_s2_na:/ #" without the quotes depending on the version of your phone.
8. on command prompt type
9. ls -al /dev/block/platform/soc.0/7824900.sdhci/by-name/
10. this lists out all your phones partitions ( not really necessary if you are using an le 2 but it's a good practice to confirm for the following steps)
11. confirm the following entries appear in the list
11a. fsg -> /dev/block/mmcblk0p18
11b. modemst1 -> /dev/block/mmcblk0p13
11c. modemst2 -> /dev/block/mmcblk0p14
11d. these three entries are where the phone stores the imei, wifi mac address, and Bluetooth address.
12a. if they don't then... if you are technical enough you cant edit this guide to suit your needs else STOP!!!
12b. if they do then you are all good. continue
13. on the command prompt enter
13a. dd if=/dev/block/mmcblk0p18 of=/sdcard/fsg.bin
13b. dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst1.bin
13c. dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst2.bin
14. this will backup the partitions and create 3 files on your sdcard 'fsg.bin' 'modemst1.bin' and 'modemst2.bin'
15. copy these to a safe place on your computer
16. this part restores your backup, on the command prompt enter
16a. dd if=/sdcard/fsg.bin of=/dev/block/mmcblk0p18
16b. dd if=/sdcard/modemst1.bin of=/dev/block/mmcblk0p13
16c. dd if=/sdcard/modemst2.bin of=/dev/block/mmcblk0p14
16d. reboot
17. after your phone reboots repeat steps 5 & 6
18. cross fingers
19. the next step will zero out (erase) the partitions so your phone can hopefully recreate them with the correct data
19. in the command prompt enter the following in this exact order
19a. dd if=/dev/zero of=/dev/block/mmcblk0p18
19b. dd if=/dev/zero of=/dev/block/mmcblk0p14
19c. dd if=/dev/zero of=/dev/block/mmcblk0p13
20. without rebooting your phone try to check the imei by dialing *#06#
21. if your imei is restored i would recommend making a qcn backup using qpst software on your computer ( the code to enable diag port on le 2 is *#*#76937#*#*) google for steps
22. if your imei is not restored then you have a different problem than i did. but do note that after following step 19-19c then and only then can you restore a qcn backup or edit your imei. and yes it works on Qualcomm HS-USB Diagnostics 9025 port. so hopefully you can progress from there.
Hi I am using LG v40 Version on Hovac 3.8 Custom Rom (Android 10) , rooted with Magisk. I Am trying to Put phone to Diag mode to get it recognized by Qfil to repair its imei. I have tried Services code method , Adb command method as well as terminal command method but my cell is not being recognized as Diag 901d port. Any leads?
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
FLAmbuRNE1 said:
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
Click to expand...
Click to collapse
only verizon roms doesnt have imei write protection (idk about A10 but for Pie its working)
if you imei on v40 already null you can try this guide
but use v40 verizon rom
on verizon rom for diag mode enable try this hidden menu code ##7764726405 and hit the call button type service code 000000
All guides seem to point towards the device being called HB-USB Diag 901D in the device manager.
I feel like this is a critical step towards being able to write protected NV items.
Trying to connect to the phone using QXDM tools does not work since the phone isn't recognized as being in Diag mode.
I've tried soooo many ways at this point but don't want to give up just yet.
Let me know if anyone has any luck in getting V40 to correctly connect in Diag mode - or prove to me that diag mode is achieved with the hidden menu (I don't see it working for me - guide me in case I'm misunderstanding something).
FLAmbuRNE1 - I stand corrected - via experimentation.
I was not seeing any ports change in Device Manager or any other application after issuing the
Code:
setprop sys.usb.config diag,adb
command as a super user or after enabling the diag port from the hidden menu.
QFIL's QCN Backup+Restore functionality kinda indicated that these commands do indeed make a difference. When QFIL Restoring QCN on my phone I noticed that QFIL was unable to reset the phone after sending data to the phone - unless I had done both of the above steps. As soon as I did, it would be able to restart my phone and verify that restore was completed.
I have some additional experiments on the way to try and figure out the exact memory locations in
Code:
modemst1, modemst2 & fsg
to modify and flash in order to restore my original IMEI. Fingers crossed...
I'll circle back here with what I find, or don't find. If I don't follow up, anyone interested, message me.
setprop sys.usb.config diag,adb
not work
C:\adb>adb shell
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
flashlmdd:/ $ su
flashlmdd:/ # setprop sys.usb.config diag,adb
flashlmdd:/ #