Database Info

How to fix LG G2 with IMEI issue

Long story short, I bricked my lg g2 d801 after flashing twrp recovery and trying to flash custom rom. The phone would restart randomly. I had no connection and the signal bars crosses out in red. In settings most of my info like baseband, imei etc were missing. I was looking up and many people bricked their phones with no EFS backup to restore the IMEI. This is how I fixed my phone. This should also help people who have zeroed out IMEI after bad flash or whatever reason. But you should at least have IMEI number ready (from your box/ receipt or call t-mobile)
1. Flashed the phone to factory firmware using LG support tool. I used the following guide:
http://androidcure.com/unbrick-lg-g2-stock-firmware/
used the firmware: T-Mobile KitKat D80120A_00.kdz
there's also similar guides in xda, follow whichever you prefer. Goal is to revert the phone back to stock.
After flashing the phone, the phone was woking; however imei was null. In phone settings my IMEI was 0. To fix the null/bad imei follow this guide (Not all the steps are my work; this guide helped me http://forum.xda-developers.com/showthread.php?t=1942417 , also watched some you tube videos):
2. You need the following drivers and software:
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
QPST_2.7_378
imei converter: http://www.sendspace.com/file/a3spfh
3. After installing the driver; turn on USB debugging and connect the phone to computer
4. Install QPST, run QPST configuration from from start menu
5. Click on Ports tab. Click Add new port. Your phone should be COM4/5. It will say USB after the port. Select the port and click OK.
6. The port should come up on active phones. Select the phone and and click on "Software Download" from start clients menu
7. Click on Backup tab. Your port should appear. Backup by clicking on start
8. Now go to Program Files/qualcomm/qpst/bin folder
9. Run RF_NV_Manager program
10. Click File read from phone. Your IMEI should appear on number 550; NV_UE_IMEI_I
11. In my case; there was no item 550 as my IMEI was missing. Don't worry.
12. Click on file> Read supported RF NV items
13. Now click on item 550. It should show 9 blank fields.
14. Start IMEI converter. Type in your IMEI in enter IMEI click on convert IMEI
15. There will be 18 digits in groups of 9
18. In RF_NV_Manager program; click on Hex by Write NV button
19. IN the 9 boxes; type in the numbers from IMEI converter starting from left. Type in first group of two numbers in the first field, then go to the next field and type in second 2 digits
20. After you fill in; click on write NV
21. Now click on File> Read from phone. NV item number 550 should appear now.
22. Unplug, Restart your phone and your IMEI number should be there and phone should connect to network.
Above process fixed my phone with full 4G LTE data. Now depending on the how bad your EFS was damaged; you might not get 4G lte data. But at least now; you will be able to send the phone back to LG for repair or return to t-mobile as IMEI number will be in your phone.

You can do this with EFS Professional. It does all the conversion for you and you dont need QPST. Just simply type in IMEI and write to device.
Sent from my LG-D802 using Tapatalk

I've tried the this guide and it didn't work for me. I get an error when I try to write NV. The good news is that I don't have an immediate need to change/fix IMEI but I was wondering if it ever gets zeroed out I have a way to restore it. I will give your tool a try.

lyriquidperfection said:
You can do this with EFS Professional. It does all the conversion for you and you dont need QPST. Just simply type in IMEI and write to device.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
So the EFS Professional is compatible with phones other than Samsung? Once I've unzipped the file I see a bunch of binaries for Samsung phones, but nothing for LG G2. When I try to run it generates an error the app is for Samsung devices only... Where can I get a compatible binary for LG G2 or EFS professional that works with LG G2?
I've tried Qualcomm NV Tools instead of EFS Professional and I cannot create a backup. When backup is being created it errors out saying the device has been disconnected... Also if I write the IMEI it says it was accepted but it doesn't change.
PS: I should probably start screweing around with these apps since I may introduce the problem. My IMEI is fine.

tpaxadpom said:
So the EFS Professional is compatible with phones other than Samsung? Once I've unzipped the file I see a bunch of binaries for Samsung phones, but nothing for LG G2. When I try to run it generates an error the app is for Samsung devices only... Where can I get a compatible binary for LG G2 or EFS professional that works with LG G2?
I've tried Qualcomm NV Tools instead of EFS Professional and I cannot create a backup. When backup is being created it errors out saying the device has been disconnected... Also if I write the IMEI it says it was accepted but it doesn't change.
PS: I should probably start screweing around with these apps since I may introduce the problem. My IMEI is fine.
Click to expand...
Click to collapse
Imei will only write if zeroed out. You are correct, EFS Professional is for samsung devices but the Qualcomm NV Tools is universal. I am currently in the middle of updating it so more features can be used on other devices.
Sent from my LG-D802 using Tapatalk

lyriquidperfection said:
Imei will only write if zeroed out. You are correct, EFS Professional is for samsung devices but the Qualcomm NV Tools is universal. I am currently in the middle of updating it so more features can be used on other devices.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
got it. Thank you.

Ey guys , im new in this foro. Sorry but my english.....i have a LG D802 , the imei said unkown ....I tried the method in this post but always obtain error when i use RF_NV_Manager , when i trie to read files from phone give me an error...the phone bricked when install a new custom rom.
Help please.....

the driver is correctly and the program detect the phone in port 26...

the error is this....

kamaleonico said:
the error is this....
Click to expand...
Click to collapse
did you try restoring the the phone with flash tool first?..

thank you so much, just did it and it worked perfectly fine !

kingroach said:
Long story short, I bricked my lg g2 d801 after flashing twrp recovery and trying to flash custom rom. The phone would restart randomly. I had no connection and the signal bars crosses out in red. In settings most of my info like baseband, imei etc were missing. I was looking up and many people bricked their phones with no EFS backup to restore the IMEI. This is how I fixed my phone. This should also help people who have zeroed out IMEI after bad flash or whatever reason. But you should at least have IMEI number ready (from your box/ receipt or call t-mobile)
1. Flashed the phone to factory firmware using LG support tool. I used the following guide:
http://androidcure.com/unbrick-lg-g2-stock-firmware/
used the firmware: T-Mobile KitKat D80120A_00.kdz
there's also similar guides in xda, follow whichever you prefer. Goal is to revert the phone back to stock.
After flashing the phone, the phone was woking; however imei was null. In phone settings my IMEI was 0. To fix the null/bad imei follow this guide (Not all the steps are my work; this guide helped me http://forum.xda-developers.com/showthread.php?t=1942417 , also watched some you tube videos):
2. You need the following drivers and software:
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
QPST_2.7_378
imei converter: http://www.sendspace.com/file/a3spfh
3. After installing the driver; turn on USB debugging and connect the phone to computer
4. Install QPST, run QPST configuration from from start menu
5. Click on Ports tab. Click Add new port. Your phone should be COM4/5. It will say USB after the port. Select the port and click OK.
6. The port should come up on active phones. Select the phone and and click on "Software Download" from start clients menu
7. Click on Backup tab. Your port should appear. Backup by clicking on start
8. Now go to Program Files/qualcomm/qpst/bin folder
9. Run RF_NV_Manager program
10. Click File read from phone. Your IMEI should appear on number 550; NV_UE_IMEI_I
11. In my case; there was no item 550 as my IMEI was missing. Don't worry.
12. Click on file> Read supported RF NV items
13. Now click on item 550. It should show 9 blank fields.
14. Start IMEI converter. Type in your IMEI in enter IMEI click on convert IMEI
15. There will be 18 digits in groups of 9
18. In RF_NV_Manager program; click on Hex by Write NV button
19. IN the 9 boxes; type in the numbers from IMEI converter starting from left. Type in first group of two numbers in the first field, then go to the next field and type in second 2 digits
20. After you fill in; click on write NV
21. Now click on File> Read from phone. NV item number 550 should appear now.
22. Unplug, Restart your phone and your IMEI number should be there and phone should connect to network.
Above process fixed my phone with full 4G LTE data. Now depending on the how bad your EFS was damaged; you might not get 4G lte data. But at least now; you will be able to send the phone back to LG for repair or return to t-mobile as IMEI number will be in your phone.
Click to expand...
Click to collapse
Hey kingroach, amazing guide, wonderful!
I followed everything step by step. Right now I have some generic IMEI which does not work, I'm trying to write my original one back, but at step 20, when I click "Write NV", the numbers change, the Hex unchecks and the popup comes out. When I close it, Hex goes back to being checked and numbers return to what I made them. and I get this popup:
Here's a video.
lyriquidperfection said:
You can do this with EFS Professional. It does all the conversion for you and you dont need QPST. Just simply type in IMEI and write to device.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Hi, thank you for your help too in these threads. I tried EFS Pro, everything checks out, it says IMEI written, but when phone is restarted, nothing has changed. Do you know if EFS Pro need some other setting enabled to actually change the IMEI?

Try deleting 550 nv item which contains the imei and save. Restart the phone and add it.

kingroach said:
Try deleting 550 nv item which contains the imei and save. Restart the phone and add it.
Click to expand...
Click to collapse
nope, it dont work
im genuinly surprised the procedure works for lg g2 and not for nexus 5

how did you delete item 550?

asterix005 said:
how did you delete item 550?
Click to expand...
Click to collapse
I couldn't - you try with the custom list, under tools I think. You move item 550 from the right column, and it dissappears, but when I read NV phone items, its there. It's untouchable I tell you!:silly:

kingroach said:
Long story short, I bricked my lg g2 d801 after flashing twrp recovery and trying to flash custom rom. The phone would restart randomly. I had no connection and the signal bars crosses out in red. In settings most of my info like baseband, imei etc were missing. I was looking up and many people bricked their phones with no EFS backup to restore the IMEI. This is how I fixed my phone. This should also help people who have zeroed out IMEI after bad flash or whatever reason. But you should at least have IMEI number ready (from your box/ receipt or call t-mobile)
1. Flashed the phone to factory firmware using LG support tool. I used the following guide:
http://androidcure.com/unbrick-lg-g2-stock-firmware/
used the firmware: T-Mobile KitKat D80120A_00.kdz
there's also similar guides in xda, follow whichever you prefer. Goal is to revert the phone back to stock.
After flashing the phone, the phone was woking; however imei was null. In phone settings my IMEI was 0. To fix the null/bad imei follow this guide (Not all the steps are my work; this guide helped me http://forum.xda-developers.com/showthread.php?t=1942417 , also watched some you tube videos):
2. You need the following drivers and software:
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
QPST_2.7_378
imei converter: http://www.sendspace.com/file/a3spfh
3. After installing the driver; turn on USB debugging and connect the phone to computer
4. Install QPST, run QPST configuration from from start menu
5. Click on Ports tab. Click Add new port. Your phone should be COM4/5. It will say USB after the port. Select the port and click OK.
6. The port should come up on active phones. Select the phone and and click on "Software Download" from start clients menu
7. Click on Backup tab. Your port should appear. Backup by clicking on start
8. Now go to Program Files/qualcomm/qpst/bin folder
9. Run RF_NV_Manager program
10. Click File read from phone. Your IMEI should appear on number 550; NV_UE_IMEI_I
11. In my case; there was no item 550 as my IMEI was missing. Don't worry.
12. Click on file> Read supported RF NV items
13. Now click on item 550. It should show 9 blank fields.
14. Start IMEI converter. Type in your IMEI in enter IMEI click on convert IMEI
15. There will be 18 digits in groups of 9
18. In RF_NV_Manager program; click on Hex by Write NV button
19. IN the 9 boxes; type in the numbers from IMEI converter starting from left. Type in first group of two numbers in the first field, then go to the next field and type in second 2 digits
20. After you fill in; click on write NV
21. Now click on File> Read from phone. NV item number 550 should appear now.
22. Unplug, Restart your phone and your IMEI number should be there and phone should connect to network.
Above process fixed my phone with full 4G LTE data. Now depending on the how bad your EFS was damaged; you might not get 4G lte data. But at least now; you will be able to send the phone back to LG for repair or return to t-mobile as IMEI number will be in your phone.
Click to expand...
Click to collapse
i tried. but at step 5, my my PC said "No Phone". can you help me ????

I keep getting
Exception Thrown!!
NvManager::getNvItemsFromPhone( const string comport )-
QpstServer::sendSyncImpl - Bad response from phone (DM packet
commands 19-24)
Any ideas? Please tag me in this.

Did you first reflash the stock rom? Someone was getting similar error and flashing stock rom fixed it.

Use EFS Professional to write your Original IMEI ....

please help a117 owners, you experiance is needed.

Hello xda friends.... im new here and i need a help from u guys. Please help mee..
i just bricked my micromax magnus a117. What i did--- rooted my phone then installed an app meteos6589 (something like that) to increase app storage. Then i restarded my phone(with usb debugging off(if it afffects anything )). And after that it is showing micromax logo only.
so anyway i downloaded stock rom v4 from mounlisky. and tried to flash with sp tools. But but but problem is arising something like "pmt didnt mathched...................." . So sp tools is saying to select and do format+download option. But i have nothing in backup only microsd and internal sd data.
So the point is i dont have backup of nvram or anything else, phone is bricked at micromx logo, usb debugging off. So how do i get my phone back to life.
anyone please....
Any detailed help is appreciated.. thank you..

so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?

ranganitesh said:
so i did it. i flashed it with stock rom. and as i was afraid of it, imei erased. but i got imei back by using mtkdroid tool(got imei numbers under mobile battery) but serial number,bluetooth address lost and in wifi showing avirtual wifi named nvram warning:err= 0*10. how to get them back?
Click to expand...
Click to collapse
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.

syserr said:
This is a trap that I have fallen into also in the early days of my MTK experience. The way MTKDT backs up data is NOT sufficient to restore a phone or tablet back.
(Sorry, I will rant for a few)
MTKDT backs up the /data/nvram files. I almost wish MTKDT didn't exist because people think they have a copy of everything they need, but it is not everything they need as you've found. (it may have improved since my knowledge is old) The proper thing to do is backup the "NVRAM" block with SP Flash Tool. You would determine where it was by looking at the scatter file. A better safeguard is to backup the whole ROM with SPFT, then you don't even have to worry about offsets, because your offset is 0x0.
Sidenote:
When you wipe the /data partition, the /data/nvram that you've restored using MTKDT will be wiped also. So you will have to restore it again.
I think where you are at now, your only option is to inspect the NVRAM block by dumping it to your computer. You will probably also need to inspect someone else's NVRAM block that has the exact model you have. From there you can look at it with a hex editor and try to figure out how to put your information back. I have to admit, I've only had limit success in doing this. I've found for example where the Wifi MAC should go, but it repeats at different locations within the block and I think I was never successful. To check to see if your hexediting is correct, you wipe /data. On first boot MediaTek's linux/android creates the /data/nvram/* files from what it finds in your NVRAM block.
I'm sorry I'm not more help.
Click to expand...
Click to collapse
So what files are needed to be backup along with mtk droid tool, just wanna know.

ranganitesh said:
So what files are needed to be backup along with mtk droid tool, just wanna know.
Click to expand...
Click to collapse
I don't use MTKDT at all. I do see some uses for it though. SPFT is a pain, but I wish every device (SoC maker) had an SPFT so you could read or write any chunk of flash.
If you look at a scatter file you will see lots of blocks/partitions that the flash is divided into. Each of these has a purpose of course, but the one marked NVRAM (a horrible confusing name) is the most important to get backed up, it has unique "calibration data" for your specific unit. You may find a "nvram.bin" that MTKDT created... this may be exactly what SPFT would backup too... if you are lucky.
So if MTKDT made a nvram.bin that is about 100x better than having a nvram.tgz or however he archives the /data/nvram files.

NVData / EFS issue / already created backup, verify image?

Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?

penandweb said:
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
Click to expand...
Click to collapse
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly.
There are different backup solutions (e.g. EFS Pro) confirmed working which may help you prevent future issues. I prefer the manual backup using adb shell or terminal emulator:
dd if=/dev/block/mmcblk0pXX of=/storage/SdCard/efs.img bs=4096
(XX needs to be replaced with the model specific partition number as they use different partition tables)
Restore:
dd if=/storage/SdCard/efs.img of=/dev/block/mmcblk0pXX bs=4096

thanks LS.xd, but i guess i have a pretty solid backup as i did create backup various ways, some were corrupt, but one that i working with has nvdata and every other file along with imei pretty intact....
i can open it up with winrar, and open the nvdata with hexeditor, i was wondering if i could confirm some way that the back up is actually 100% solid?
wondering if the partition's aren't aligned. I don't know for sure if EFS folder in the root directory is the same as being pointed by /mmcblkp03/platform/by-name/EFS ?
i mean they should be the same thing, its just a redirection right?
what should i be doing now? the baseband is unknown and the imei wont just work, waste the phone? or it could be done via some boxes or some other process?

there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..

penandweb said:
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
Click to expand...
Click to collapse
So you got some non TWRP made EFS backup, too? You can list your partitions using shell:
[email protected]:/ # cat /proc/emmc
You can use the dd command once you know the layout. Backups not generated manually may only be restored with the specific app/version and are probably not compatible using other restore methods. For my OnePlus 3 EFS backup can generated fine using TWRP but restoring it screws up the partition. Manually created image works fine. As I don't have a Note 3 Neo I don't know how it behaves for your device.

any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?

penandweb said:
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
Click to expand...
Click to collapse
After 3 years I had to retire my HTC One S. I flashed roms and firmwares up to 3-4 times a week without having any issues. One sunny day some update bricked then nvdata. I spent a bunch of hours trying to restore it in different ways, extracted data from stock firmware as well as using dumps from other user's phones, as some users reported this error fixed doing so. Even when the files was identical it just did not work for me. Changing the mainboard was the only possible solution so I decided to get a new device.
All I want to say is try to restore a valid backup in a way confirmed working. If you don't have a usable backup ask in your device's forum for somebody may upload it. Or spend 100 hours messing around with hex editors until you reach then point where you realize its cheaper to switch the device as wasting a year's holidays browsing the internet for some solution.

Kiwami Samurai FTU152D stock Lollipop 5.1, Root and Xposed, Help and Tips

This post is to help users who have accidentally or on purpose tried to upgrade to Android 6.0 on their Kiwami Samurai FTU152D using software for FTJ152D (Japanese version of phone), and to help with root and installing Xposed on your phone. There is a risk of getting the phone stuck on boot screen if a user uses certain versions of SuperSU. If you searched the net and found this thread, and are still on Stock Rom for your FTU152D, Do not Upgrade until you have read this thread. Upgrading by flashing a rom using SP Flash Tool you risk losing your IMEI information in the phone forever. I am going to write this thread with an assumption that reader has upgraded the software in their phone using the Japanese Firmware. You can read through and use this thread based on your situation and if confused, better to ask questions on the thread than trying something on your own. I do not take any responsibility if you brick or hard brick your phone, so please be careful and do not just randomly flash things without full understanding, confused? ask questions.
Note #1: First and Foremost, Be careful to not flash a preloader.bin file in your phone from other phone models. You run the risk of permanently bricking your phone. Use the correct preloader made for your phone.
Note#2: Make at least a 5 GB backup dump of your phone using SP Flash Tool 'Read Back' tab before you attempt root or other customizations on your phone. This can be done using the scatter file from stock rom of FTJ152D Android 6.0 available at needrom website at:
https://www.needrom.com/download/freetel-samurai-kiwami-ftj152d/
You will need to input scatter file in the download tab before SP Flash tool will allow you to do a 'Read Back' dump of your phone. Be very careful when attempting this and do not accidently download (the whole reason of this thread and my troubles is because I did exactly that). In 'Read Back' tab, you can click on 'Add', name the raw dump, and add the starting address (that will be 0 of course) and make the length equivalent of at least 5 gigabytes, make sure that you have selected the 'EMCC_USER' as your region. Use 'Add' to add another 'Read Back', this time for preloader (in boot_1 region). You can open the scatter.txt file from the rom you downloaded earlier to see how long this 'Read Back' needs to be. Next, click on 'Read Back' to start the backup dump, power off and connect your phone via usb to the computer. (You may need the VCOM drivers, if the phone is not detected by SP Flash Tool or you keep getting errors, search for the driver online or download it from the needrom website, same page where the rom is (link above). Keep these two dump files safe as these are effectively your backup in case you mess up your phone.
ROOT and Xposed:
If on lollipop there are at least couple of options to root using kingroot (personally dislike) and others. If on Marshmallow, you can use my posts in this thread to root using Magisk:
https://forum.xda-developers.com/general/help/how-to-root-freetel-kiwami-samurai-t3610015
Recover from Japanese firmware and/or Going back to Lollipop:
In case you have flashed the Japanese firmware and now have problems using the phone and want to go back to FTU152D stock rom (Android 5.1) with correct baseband, use the attached file (mega link below) with SP Flash Tool. First, find an nvram.bin file online compatible for mtk6795 chipset or look at this page as you can download a nvram.bin from there:
https://afterroot.wordpress.com/2015/07/22/mtk-restore-nvram-bin/
***Very Important Note*** Nvram.bin file as the one on the above website will fix your phone, especially the baseband (all the better if you made a backup using the method mentioned in Note#2 above, you can use the scatter file and hex editor (such as HxN from download.cnet.com) to cut out the nvram.bin and secro.img (need both to restore imei and baseband) partition file from the raw dump) but the IMEI numbers will be specific to the nvram.bin file you use (and this is why i didn't provide my backup nvram file, but i did provide secro.img as it contains baseband info), and using wrong imei number with your phone may not be legal. If you use the file from the above website, your IMEI numbers will be specific to that file and you MUST change your IMEI numbers to your original numbers using a number of apps or other methods available online, just search the web.
You should unzip the rom zip from this link:
https://mega.nz/#!1v4GUaBC!Wj4JW6fZkxNB-ZISrdPmBcR_hu_XSu9NoCrnOKYMdYo
that I put together by dicing raw dump of my phone using SP Flash Tool and putting together some of the files from the MM folder. Some of these files may not be needed for a successful installation but i just wanted to be sure because I had issue with some folders not being visible in the phone's internal memory. Make sure you insert an nvram.bin file in the rom folder before proceeding otherwise your phone sims will be greyed out, choose the scatter file in the folder with SP Flash Tool download tab, and use 'format all + download' option in download tab, click on 'Download', power off the phone and attach to PC via USB cable. Once download is done, power up your phone and you are done. Now you can root and install xposed, and fix your IMEI numbers if they are wrong using the tips and link provided above if like.
I am trying to get a custom recovery to work with this phone but so far because there is no touch in recovery mode, TWRP doesn't work. If anyone have been able to install or use custom recovery, please share your experience and help out others. Thanks.

If anyone have internal phone storage not showing DCIM, Alarm, Ringtones, and other folders, make sure you don't have an SD card in the phone, do full factory reset after flashing, go to storage settings and make sure the internal phone storage is selected for write to memory, then insert SD card in the phone. That fixed this issue for me. It is just how this phone is setup that you have to select internal phone storage or external sd card for where the stuff gets stored.
Another fix that worked for me was to remove SD card from phone, format whole flash except bootloader in format tab first, flash all files except userdata.img and cache.img in download mode, and then make sure you go directly to stock recovery at first power on (hold volume up while powering up the phone), wipe cache and wipe data/factory reset, and then allowing the phone to boot up the first time.

Another tip for other Kiwami Samurai users i wanted to share is that both Freetel roms (5.1 & 6.0) come pre-installed on either variant of phone with 3 potential malware or PUPs that i just detected using Malwarebytes (see screenshot). I wouldn't have expected this from a Japanese smartphone manufacturer. These are installed as system apps and require root and an app like Titanium Backup to freeze and/or remove these. 'Debloater' app by Gatesjunior on xda forums can also remove these.

Thank you for the thread.
I have this phone, the US version FTU152D.
From what I can find on XDA and other places. there is no update to Marshmellow available for the US version. Can you confirm?
I see your methods above. I am thinking of flashing stock ROM to the phone to clean up some issues. Think of it as a clean install.
Thank you,

Elephone U Pro IMEI and Baseband thread

Lost IMEI and Baseband on your U Pro.
lets search for a solution.
forword:
if we flash the 2080227 stock rom we will lose the IMEI and Baseband information in Settings.
the IMEI and Baseband is still there its just that it dont show in settings anymore.
Why:
stock rom 20180227 contains all images of the official Stock Rom as dump.
also modemst1.img and modemst2.img. in that images are the imei information stored.
baseband information is stored in fsg.img
but why it dont restore also the imei info in settings ? maybe its region related. we dont know that yet.
lets Discuss and find a Solution/fix for that

reserved
here i will post the possible solution ..............
1.
This will restore the IMEI numbers into settings for slot 1.
Slot1 and slot2 will be similar then.
1. Install xposed manager APK. You have to have root for that.
https://xposed-installer.de.uptodown.com/android
2. Download in the app framework v90.beta3 and install it ( all in the app)
3. Download this app from playstore (IMEI changer)
https://play.google.com/store/apps/details?id=com.vivek.imeichanger
4. Your imei is written on your u pro box back cover.
Enter the IMEI in the app. Save it and reboot.
Done!

can you maybe transfer from eragon rom thread to here the posts concerning imei?
thank you

jimibxl said:
can you maybe transfer from eragon rom thread to here the posts concerning imei?
thank you
Click to expand...
Click to collapse
Don't need to. .
In 10min .
Look into post #2
First solution will be there

I have already tested several apps from different vendors, unfortunately without success.

xdaONLINEuser said:
..
Click to expand...
Click to collapse
First solution is online

Found another solution just now.
Will check that that in a few hours.
If that works we can restore all

xdaONLINEuser said:
I have already tested several apps from different vendors, unfortunately without success.
Click to expand...
Click to collapse
The first solution was also tested by me. It worked. Try it

unfortunetly if xposed is uninstall imei is lost again

jimibxl said:
unfortunetly if xposed is uninstall imei is lost again
Click to expand...
Click to collapse
LOL . I did not tested that.just uninstalled framework and xposed app and the IMEI is gone. You are right. WTF
In ~2hours I will know if the other fix I found will work

Maybe helpful information:
For me without any changings the IMEI isn't gone. With *#06# I see two IMEI
I'm on eragon 4 but I've had to make a factory reset after update from 3 to 4 (there were some problems like system settings not working)

Laptapper said:
Maybe helpful information:
For me without any changings the IMEI isn't gone. With *#06# I see two IMEI
I'm on eragon 4 but I've had to make a factory reset after update from 3 to 4 (there were some problems like system settings not working)
Click to expand...
Click to collapse
I guess the problem of losing the IMEI was caused if someone flashed the stock rom 0227. It was overwriting modemst 1 and 2 where the IMEIs are stored. Eragon doesn't do that.

I have found appropriate tools (also via xda), which perfectly fulfill the task...
QUALCOMM smartphone write IMEI tool 1.01
QMSL IMEI and SN writer 1.4
But apparently the tools do not support the chipset, or I have not yet found a way to use the tools accordingly.
If someone has experience with these tools…
Thanks in Advance

xdaONLINEuser said:
I have found appropriate tools (also via xda), which perfectly fulfill the task...
QUALCOMM smartphone write IMEI tool 1.01
QMSL IMEI and SN writer 1.4
But apparently the tools do not support the chipset, or I have not yet found a way to use the tools accordingly.
If someone has experience with these tools…
Thanks in Advance
Click to expand...
Click to collapse
Already tested them a few days ago. They don't work.
Feedback of my progress so far:
I use NV ram tool to try to restore IMEI.
I was able to build IMEI but it did not flashed it because of a driver (diagnostic mode) problem.
I just have to find the right driver. Lol.
Sound funny , but I have around 100 different diagnostic drivers for Qualcomm devices.. one is the right one I hope ....
Gesendet von meinem U_Pro mit Tapatalk

skeleton1911 said:
Already tested them a few days ago. They don't work.
Feedback of my progress so far:
I use NV ram tool to try to restore IMEI.
I was able to build IMEI but it did not flashed it because of a driver (diagnostic mode) problem.
I just have to find the right driver. Lol.
Sound funny , but I have around 100 different diagnostic drivers for Qualcomm devices.. one is the right one I hope ....
Gesendet von meinem U_Pro mit Tapatalk
Click to expand...
Click to collapse
all the best man to succeed, we are with you

Been looking through XDA threads hoping to get some ideas on missing IMEI thing. I'm also trying to run a NV Backup using the QFIL program and up to now I wasn't able to do that, the blue 'start' button was always disabled(diagonal gray stripes) with the COM port and diag driver ON. I think, the problem is related to the lack of IMEI/ESN etc.., because today I hooked up my spare Moto G4 Play and got the NV bckp from it. Then, after that, I actually had a little success with Upro, I used the same diag driver which poped-up with Moto, HS-USB 9091 (instead of 900D), it's also a Qualcomm driver, found it on my desktop(uncheck: show compatible drivers to see it) Not a total success but, at least I could start the bckp. It failed, still, I've never gotten this far. Can you try and see if you're able to get the NV backup w/o IMEI#?
Is there a way to somehow convert to text the .qcn files? How about editing it, if that's possible then the imei could be written into saved files and fed back into the phone using 'restore'. Just saying, am clueless on that.
Ok, here is that link from another XDA thread and you'll find two screenshots below:
https://forum.xda-developers.com/moto-g4-plus/help/diag-mode-g4-qpsd-t3591683/page2
https://drive.google.com/file/d/1pCyf1xcrtsESGYCTbpJLiSoF102Kik5q/view?usp=sharing
https://drive.google.com/file/d/1xawPNNMCD39nzQJaoBfwwnf0zVFCwQTA/view?usp=sharing

I am ready to try the IMEI edit on my Upro. I was dry practicing today on .qcn files extracted from Moto 4g Play, navigating the .qcn with this editor http://mh-nexus.de/en/hxd/ , finding the proper columns and rows, playing with hex./dec. conversions guided by this: (watch?v=zn_D6TEFABQ)
But I'm still missing the most important element: the actual Qfil generated .qcn backup files from my Upro, can't get it. You guys have any suggestions?

How can i unlock lte band i do have my imei showing when i do *#06# but qpst/qxdm doesn't read my device in qpst it says no phone no esn in the com port used by my phone

jimlap30 said:
How can i unlock lte band i do have my imei showing when i do *#06# but qpst/qxdm doesn't read my device in qpst it says no phone no esn in the com port used by my phone
Click to expand...
Click to collapse
Are you in diagnostics mode? Which driver # do you see.

skeleton1911 said:
reserved
3. Download this app from playstore (IMEI changer)
https://play.google.com/store/apps/details?id=com.vivek.imeichanger
4. Your imei is written on your u pro box back cover.
Enter the IMEI in the app. Save it and reboot.
Done!
Click to expand...
Click to collapse
Its a placebo fix or better only a solution for fake/anonymize the IMEI for apps only!
If the provider needs the IMEI to connect to his network it is not working!
With a app on phone you can not bring back the IMEI, its stored in the NVRAM.
You have absolut no write access to this "partiton" on a running system.
for real restoring you must flash it!