Database Develop

PDS Partition Fix (Very risky - Not for the faint of heart!)

I no longer have this phone!
---
Are you having problems flashing custom ROMs and then getting bootloops? Are you sick of using the Stock ROM?
I found that it is caused by accidentally wiping the PDS partition in some versions of CWM an TWRP.
By going into Settings > About > Status the serial number will no longer be shown. (Unknown or Error.)
A long time ago, someone posted their PDS (yay!) here.
The second post has an extracted PDS.
You will need to download both the pds.img and efi.zip for this tutorial.
To see where the PDS is located for the XT890, look here. (mmcblk0p12)
~
Note: I've attached some pics to help - see below.
Step One:
While booted into Android, you need to use the following commands: (Make sure you enable USB Debugging.)
Code:
adb push pds.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/pds.img
dd if=/data/local/tmp/pds.img of=/dev/block/mmcblk0p12
exit
exit
adb reboot
At this point, if you boot into fastboot, you'll notice the PDS is fixed, but it will not show YOUR serial number.
Step Two:
Extract efi.zip
Open up efi\factory\fti using a hex editor (I use XVI32)
Find the decimal address (Address > Goto) 21
Insert your serial number as a text string T********H (Edit > Insert string)
Remember, the serial number is TEN characters.
Remove the old serial number using Delete on the keyboard.
You should end up with your serial number and EA4 on the end.
Save the file and copy it to your phone.
Using a root explorer file manager (I use ES File Explorer) mount / as RW
Browse to /pds/factory/, copy your edited fti file and overwrite.
Step Three:
Restart the phone and boot into fastboot.
Code:
fastboot erase cache
fastboot reboot-bootloader
fasboot should now show the correct serial number.
Congrats!
I hope this has helped you, please give feedback.

Good find. Thanks for the contribution

So my Serialnumber is the MSN on my phonebox right, the one right above the IMEI? Cause mine is not beginning wit a "T", but it has 10 characters.
Btw, the Serialnumber is not the only thing that is unique - the mac adress is saved in the pds too. I will try to change mine later, should work with the same method, i just create a new one i guess - dont know how to get my old one.

I lost my box a long time ago, but had my serial number saved in a screenshot from when I unlocked the phone's bootloader.
Thanks for the info on the MAC address, I'll look into it later.
Sent from my XT890

Worth a try with the Moto X Style?

AlertRobotdude said:
Worth a try with the Moto X Style?
Click to expand...
Click to collapse
Maybe, but not this one. Do know u are in the "Razr I" forums of XDA and not in the "Moto X Style" forums.

[GUIDE][FIX] Boot loop on Lollipop 5.0 and above (fix persist partition)

What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
Can't access to internal storage.
No signal even after formating cache and fastboot flash cache.img
IMEI number is lost even after formating cache and fastboot flash cache.img
Boot loop on Lollipop 5.0 and above
You get "e: cannot mount /persist" in recovery
then your persist partition have to be fixed.
Requirements to proceed:
Ability to use adb command.
TWRP or Philz touch recovery.
Universal Naked Driver for recovery. (Windows users)
Root.
Setting up adb, rooting and installing drivers are not part of this guide. If you have to do that then please use @rootSU's great thread to find the guides you need.
Let's start!
Reboot your phone to recovery.
Connect USB cable.
Open CMD or Terminal application.
Enter following commands in CMD or Terminal application:
adb shell
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
Click to expand...
Click to collapse
You should be prompted to repair or fix errors. Keep pressing enter until the process finishes.
If you are not prompted for repair or you still have problems then follow my instructions.
Get to that point again when you entered the adb shell command then type the following command:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Click to expand...
Click to collapse
Reboot your phone.
Now all your problems should be gone now, but your wifi and bluetooth addresses should be fixed to prevent further problems or bugs.
Download this rar file.
Extract it.
(Linux users should enable show hidden files)
Open .bdaddr with a hexeditor.
You should see following:
BC F5 AC 00 00 00
Click to expand...
Click to collapse
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .bdaddr.
Open .macaddr with a hexeditor.
You should see the following:
8C 3A E3 00 00 00
Click to expand...
Click to collapse
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .macaddr.
Copy both files to your sdcard.
Enable USB debugging on the phone.
Open CMD or Terminal application. (If you closed it)
Enter following commands in CMD or Terminal application:
adb shell
su
Click to expand...
Click to collapse
Grant access on the phone.
cd /persist
mkdir bluetooth wifi
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
cp /sdcard/.bdaddr /persist/bluetooth
chown bluetooth:system ./bluetooth/.bdaddr
chmod 660 ./bluetooth/.bdaddr
chown wifi:system ./wifi
chmod 770 ./wifi
cp /sdcard/.macaddr /persist/wifi
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Click to expand...
Click to collapse
Reboot your phone. All your problems should have gone now. You can delete .bdaddr and .macaddr from your sdcard.
About the other files:
SNS.reg will be regenrated, but the DRM releated files will not. Nobody ever complained about the missing DRM files, but I still want to make it possible to restore them. If anyone could make an md5 checksum about the files on the persist partition that would be great.

Great thread @bitdomo. Thanks for adding this to the forum. I added it to the root guides section of sticky roll-up
Sent from my Nexus 5 using Tapatalk

Nice job! ?

This should be very helpful, well done!

I keep getting not found when i enter that comand in cmd.

Great thread. Didn't even know about such a partition to be honest.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Juniluis said:
I keep getting not found when i enter that comand in cmd.
Click to expand...
Click to collapse
Have you added adb to your PATH?
Sent from my Nexus 5 using Tapatalk

Man your a life saver thank you so much I just copy your and I stop typing because I was typing something bad.

One question the Mac address WiFi and Bluetooth steps in hex editor only the ones that had problem with the first qoute ta was ef2sck .....etc and needed to go to the second quote that was make ef4 ..,.etc need to do it right?

bitdomo said:
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
Can't access to internal storage.
No signal even after formating cache and fastboot flash cache.img
IMEI number is lost even after formating cache and fastboot flash cache.img
You get "e: cannot mount /persist" in recovery
then your persist partition have to be fixed.
Requirements to proceed:
Ability to use adb command.
TWRP or Philz touch recovery.
Universal Naked Driver for recovery. (Windows users)
Root.
Setting up adb, rooting and installing drivers are not part of this guide. If you have to do that then please use @rootSU's great thread to find the guides you need.
Let's start!
Reboot your phone to recovery.
Connect USB cable.
Open CMD or Terminal application.
Enter following commands in CMD or Terminal application:
You should be prompted to repair or fix errors. Keep pressing enter until the process finishes.
If you are not prompted for repair or you still have problems then follow my instructions.
Get to that point again when you entered the adb shell command then type the following command:
Reboot your phone.
Now all your problems should be gone now, but your wifi and bluetooth addresses should be fixed to prevent further problems or bugs.
Download this rar file.
Extract it.
(Linux users should enable show hidden files)
Open .bdaddr with a hexeditor.
You should see following:
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .bdaddr.
Open .macaddr with a hexeditor.
You should see the following:
Change the last three 00 to something else.
You can use 0-9 numerals and A-F letters.
Save the modified .macaddr.
Copy both files to your sdcard.
Enable USB debugging on the phone.
Open CMD or Terminal application. (If you closed it)
Enter following commands in CMD or Terminal application:
Grant access on the phone.
Reboot your phone. All your problems should have gone now. You can delete .bdaddr and .macaddr from your sdcard.
About the other files:
SNS.reg will be regenrated, but the DRM releated files will not. Nobody ever complained about the missing DRM files, but I still want to make it possible to restore them. If anyone could make an md5 checksum about the files on the persist partition that would be great.
Click to expand...
Click to collapse
I have a big problem: when I enter "e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist", it says that the journal has data and can't set superblocks, and when I enter "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist" the problem persist..:crying:

thaaaaaaaaaanks the phone is work O_O

I need a professional guy help
rootSU said:
Great thread @bitdomo. Thanks for adding this to the forum. I added it to the root guides section of sticky roll-up
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
im really stuck on the starting adb and fastboot is their any guy to whom should i show this nexus 5 imei gone. storage corrupt and baseband null even camera is also not working.
i live in pak please prefer a guy who can resolve my problem
Thanks

I registered in the forum to thank you @bitdomo ! My Nexus 5 lost signal a few weeks ago and I did EVERYTHING. Started with trying to add apn stuff manually, then in-android factory reset, wipes, then stock flash, a few more flashes, and I started to go crazy. My IMEI was lost. But this got it back! Thank you very much!

The same thing here! Thanx a lot,bitdomo!

faizanfarooq86 said:
im really stuck on the starting adb and fastboot is their any guy to whom should i show this nexus 5 imei gone. storage corrupt and baseband null even camera is also not working.
i live in pak please prefer a guy who can resolve my problem
Thanks
Click to expand...
Click to collapse
Did you try any of the suggested guides/links by rootSU in the OP? The required information on getting ADB/fastboot working correctly is all there, see link http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273

Thank you very much! This helped me a lot.

The best way is to flash factory images.
I had this issue in the morning and solved it in no time.
Goodluck

DaGr81 said:
The best way is to flash factory images.
I had this issue in the morning and solved it in no time.
Goodluck
Click to expand...
Click to collapse
This issue won't be solved by flashing factory images. Hence the thread.

Thanks!!!!!!!!
I love my Nexus 5. This did the trick. I did have to flash-all at the end because I screwed it up too much while trying to fix it.
By the way the symptom I was experience was the phone was in a endless forever loop on the boot and I was seeing the color dots animation for a couple days.

Don't copy the whole OP page to ask a simple question please #swag
Sent from my Nexus 5

Guys can this only be done in adb? My nexus 5 is in a bootloop, tried reflashing stock. Still the same. I can get into bootloader, tried going in recovery but it just bootloops after that. Help please. Thought it was the power button. Replaced but still the same

[GUIDE][UNLOCK BOOTLOADER]Guide to unlocking the bootloader on the L90 [ALL VARIANTS]

Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
Over the last few months development on the LG L90 has made some great strides, up to the point where we can actually install roms! In order to do this, however, you'll need an unlocked bootloader.
The problem that arises is that there are different models of the L90, being the D405, the D405n, the D410 and the D415. For most of the models the unlock process is very similar, but for the D415 another method is needed.
This guide is aimed at explaining the entire unlock process in a complete and simple way, so even if you have no experience flashing custom recoveries or roms at all, you should still be able to follow this guide. If you run into problems, please just post a reply or send me a PM and I'll do my best to help you.
First of all I'd like to note that I did not develop any of the bin files or apks in this guide, I'm only collecting all the unlock methods in one place for easy reference. Therefore I am not responsible for you bricking your device or causing any kind of damage to it. You follow this guide AT YOUR OWN RISK! That being said, let's get to the unlocking!
What you'll need to unlock the bootloader
1. A rooted LG L90
You can root the phone by going to https://towelroot.com in your mobile browser and tapping the lambda sign. Save and install the apk (make sure unknown sources are enabled in "menu > general > security"). Google will warn you about the app, this is because of the exploit which will enable the root access. Execute the program and tap "make it ra1n", then install supersu from the play store. Open supersu and choose to rebuild the binaries. This will fail, but after a reboot supersu should be installed and working properly.
UPDATE: If towelroot doesn't work for you, you've probably got the L90 with an updated firmware. In that case you can follow this guide by @gdjindal to obtain root access. Afterwards you can follow the rest of this guide again.
2. Have adb installed.
just download the Android sdk and install it or, if you don't care about the SDK itself, the minimal adb from the bottom of this post (thanks to @shinobisoft for the upload). Now add the C:/path_to_the_sdk/sdk/platform-tools to your windows PATH variable (Windows 7: right click my computer > properties > advanced system settings > environment variables) or the foler in which adb.exe is located if you downloaded the minimal adb..
On your phone go to "menu > general > about phone > software information" and tap build version a few times untill it says you're a developer, then go to "menu > general > developer options" and enable usb debugging. Connect the phone with your PC and choose to connect in software mode and install the drivers and tools. When you get a message on your phone that your PC want to access usb debugging make sure you check the checkbox and accept. Now open a cmd prompt and type "adb devices" without the quotes. If it shows a series of letters and numbers followed by device, you're good to go. If it says unauthorized, you haven't accepted the prompt on your phone yet. If your device doesn't show up at all you haven't installed the drivers correctly.
3. Find out which device and software version you're running.
Go to menu > general > about phone > Hardware information for your Model number. Mine is LG-D405n, so my model is D405n.
Go to menu > general > about phone > Software information for your Software version. Mine is V10b-EUR-XX, so I've got version v10b.
4.1 If your model number is D405, D405n or D410, you'll need a modified aboot.bin to unlock the bootloader.
Go to the bottom of this post and download the file with your model and software version. I used the L90_D405n_v10b_hack.zip. Extract the aboot.bin in the zip file to a folder on your PC.
4.2 If your model number is D415, you'll need another method to unlock the bootloader, which is explained in this thread made by @aSuperSaiyanG0D.
Unlocking the bootloader on the D405, D405n and D410
1. Open a cmd window an CD to the folder where you've saved the aboot.bin you've downloaded in step 4.1
2. Execute the following commands:
Code:
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Right after the su command, supersu will give you a root request on your phone that you'll have to accept!
This will also make a backup of your current aboot partition as stockaboot.bin on your external SD card. If you don't have an external SD card, this won't work and you'll have to use /storage/emulated/0 (this is a zero, not the letter o) instead of /storage/external_SD/ like this:
Code:
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin 5429599
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
3. That's basicly it, you can now install a custom recovery. I suggest downloading the latest TWRP (2.8.0.0 right now) from @shoxxy's thread, which can be found here. Just use ROM Toolbox to install it, choose rom installer, press settings > flash image and select the TWRP image from @shoxxy's thread. Afterwards you can boot to recovery using ROM Toolbox, or by shutting down the phone, holding volume down and power untill the lg logo shows, then releasing and immediately pressing those buttons again. You should get a screen asking to perform a factory reset. Choose yes twice (don't worry, it wont actually perform the reset) and TWRP should boot up. Now you can create backups and install custom roms too!
If you're a fan of cyanogenmod, you should visit @Quarx's thread, which can be found here. His CM11 is already mostly functional (right now on some models the front camera doesn't work and the ir blaster doesn't have any software, but most other functions actually do work very well, while it is faster than LG stock and gives almost twice the battery life), so if you like CM it's a thread worth keeping an eye on.
Flashing back the stock rom (in case of a brick)
If you've bricked your device, or want to revert to stock for any reason, you can follow this guide made by @gdjindal.

Post reserved

So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"

Gabe.INc said:
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Click to expand...
Click to collapse
If you have a problem with step 4.2 only, I assume you have a D415 and you should actually ask this question in the thread that step 4.2 links to. Or isn't that what you meant?
EDIT: please note that step 4.2 is for the D415 ONLY.

Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405

Gabe.INc said:
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Click to expand...
Click to collapse
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.

SubliemeSiem said:
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
Click to expand...
Click to collapse
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?

Gabe.INc said:
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Click to expand...
Click to collapse
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Mind that I've only tested this using the external SD, but it should work both ways.

Error 1
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse

Gabe.INc said:
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse

BTW: what's the output of
Code:
adb devices
?

SubliemeSiem said:
Gabe.INc said:
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse

Gabe.INc said:
SubliemeSiem said:
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse

SubliemeSiem said:
Gabe.INc said:
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse

Gabe.INc said:
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Where did you get the not found message? And what do you mean you flashed stock again? If you couldn't execute the dd commands then your bootloader is still locked and all you've done so far is root the device..

UPDATE: I don't get a response, but it seems this user previously flashed the wrong aboot.bin (or did something else, unfortunately he's not being very clear on that) so please only follow this guide when you have a stock recovery + aboot partition. If you did try some things before, please flash the stock rom back first and then follow this guide.

Thats awesome! Thank you! :cyclops:

guilherme.fuzo said:
Thats awesome! Thank you! :cyclops:
Click to expand...
Click to collapse
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).

SubliemeSiem said:
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
Click to expand...
Click to collapse
I found no problem, but anyway thanks dude! :laugh:

guilherme.fuzo said:
I found no problem, but anyway thanks dude! :laugh:
Click to expand...
Click to collapse
Then don't say thanks, but hit the thanks button on the first post!

[GUIDE] [SEED ONLY] FIX YOUR DEVICE'S IMEIs (NO SIGNAL)

MESSAGE ME FOR THE DOWNLOADABLE FILES, I CANNOT PUT THE LINK, IM JUST A NEW MEMBER HERE. THANK YOU​
REQUIREMENTS
adb and USB drivers (if you’re already installed this drivers, skip this)
QPST
Hex Editor
IMEI Converter
.qcn file
Rooted phone (recommended)
Getting your IMEI:​
You can get your IMEI at your phone factory box or inside the phone, and take note them to notepad.​
Setting up your phone:​
Go to Settings/About and rapidly tap the Build Number, until the “You are now a developer” appears, then go back to Settings/Developer options.
Enable USB debugging mode
Connect your device to your computer, and if your phone notifies an RSA key, press Remember my Choice, and press Allow/Accept.
Go to Command Prompt or Windows PowerShell on your computer, then type this command:
Code:
adb shell
su
setprop sys.usb.config diag,adb
Don’t disconnect your phone. We will use it later on QPST.
Converting IMEI to Hex values:​
Open IMEI Converter.exe
Type your IMEI 1 then press convert, copy the converted IMEI to your notepad.
Type your IMEI 2 then press convert, copy again the converted IMEI to your notepad.
Editing your .qcn file:​
Open the .qcn file you’ve downloaded on HxD
Find (Ctrl +F) “08 8A 56 48 03 42 40 12 43”, set Datatype to “Hex-values,” and Search Direction to “All.”
Replace it with your converted IMEI 1 earlier.
Find again “08 8A 56 48 03 42 40 12 24”
Replace it with your converted IMEI 2 earlier.
Save it to Desktop for easy find.
Restoring .qcn:​
Install QPST.exe or Setup.exe, and wait to finish installation.
After the installation, search and open QPST Configuration.
Go to Ports/Add New Port, uncheck “Show Serial and USB/QC Diagnostics only,” click OK.
A new port will appear on the box.
Go to Start Clients/Software Download. Navigate to “Restore” tab.
If your Device/COM appears on “Port,” browse your .qcn file that you edited earlier, and open it.
Click “Start,” and wait for the process to finish.
Exit QPST and reboot your device.
Finally, checking your IMEI:​
On your device, go to Dialer/Phone, then dial *#06#.
It will show the 2 IMEIs of your device.
CONGRATULATIONS!!!!!!!!!!!!!​
:victory::victory::victory::victory::good::laugh:​

HELP
Does it need to be rooted? I have non-rooted, stock Android One 2nd-Gen that have NO SIGNAL. All connections (WiFi, Bluetooth) are OK. Cellular signal is NOT OK.

HEXEDIT
i put the qcn on hexedit and search with the converted imei NO MATCH FOUND where i did it wrong

turx said:
Does it need to be rooted? I have non-rooted, stock Android One 2nd-Gen that have NO SIGNAL. All connections (WiFi, Bluetooth) are OK. Cellular signal is NOT OK.
Click to expand...
Click to collapse
if you managed to switch on your diag mode without rooting then its OK. Otherwise you can' t use
Code:
phone:$ su
.

Qcn
bro i need qcn file for Find (Ctrl +F) “08 8A 56 48 03 42 40 12 43

bro my mi a1 is not showing imei and have noo network signal, please share files so i can perform above operation

no works in Huawei kirin 960 ????

aureliomilitao said:
no works in Huawei kirin 960 ????
Click to expand...
Click to collapse
bro its work only qualcom

[email protected] said:
i put the qcn on hexedit and search with the converted imei NO MATCH FOUND where i did it wrong
Click to expand...
Click to collapse
same here bro plzz help somebody

Imei related issue
In. Hex editor when i search in converted imei it says cant find plzz help

I did it on my Redmi 7 device QFIL status is successful but imei is not updating

This Method is only valid for Qualcomm devices ,what for MTK devices like redmi note 8 pro like stuffs plz reply

Note 8 Qualcomm after restore QCN imei back but signals not working, what missing ?

PHONE IS ROOTED BUT DIAG MODE NOT SHOWING

Redmi Note 8T, phone is rooted.
adb shell
willow:/ $ su
Permission denied
13|willow:/ $

IMEI Details INVALID

Hi Guys,
I was flashing a custom rom on my Le2 X526 Snapdragon version, somehow I've managed to Delete the IMEI details. The Mobile Network section is grayed out, Although the Wifi and BT are working fine.
No, I didn't perform a backup before flashing.
The bootloader is unlocked, the phone is rooted. It turns on and everything just no network.
I've tried flashing IMEI number using Qualcomm Flashing tools and QFIL, they seem to get stuck at Connecting and ultimately fail. Although I can see my device connected in DIAG Mode in Device Manager (Qualcomm HS-USB Android DIAG 901D - COM !=1X)
I've also tried the method which included the following adb shell commands:
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
These give me a weird Write Error saying "write error: No space left on device"
Even though there is plenty of space.
Can anyone suggest some things which can be done to investigate this further, can it be some other issue pertaining to partions or something like that.
Any leads and suggestions would be appreciated,
Thanks