Hello, so the was a magisk update some time ago, I decided to do it this friday (a week ago) (from v23 to v24.1). My phone went into a boot loop so I decided to just flash stock and reflash 24.1, I tried for a few hours, but 24.1 didn't work and I always had a boot loop, so I got back the 23 and thought that's the end. Sadly my IMEI became invalid in the process. I'm not sure what is needed to fix this, or what info would be needed, so please tell me in the comments or something. I don't have any backups of EFS.
I've same problem. Also looking for way to bring my device back to life
Hmm I didnt get this. IMEI not showing in system properties?
*Wait you didnt have backups? Live and learn my friends.
(I keep one that is 15gb on my measely 64gb card in my phone, and a base backup copy on my desktop.)
Nope IMEI is not showing in properties.
Yep I know, no backup is my fault, totally my fault.
My phone even tells me I can't use the *#06# code because it's not supported on show imei, I didn't even know you could break your IMEI. Is there any way of writing the IMEI or something or is it just done?
Sunderw3k said:
My phone even tells me I can't use the *#06# code because it's not supported on show imei, I didn't even know you could break your IMEI. Is there any way of writing the IMEI or something or is it just done?
Click to expand...
Click to collapse
*#06# doesn't work for me nether.
Altho I was aware of possibiity of breaking IMEI, I was in rush which led to wiping/overwriting efs partition I think
Hello. I have the same problem with the Imei number on this phone. * # 06 # does not work. Displays info that Imei is not supported on this model.
NetBos said:
*#06# doesn't work for me nether.
Altho I was aware of possibiity of breaking IMEI, I was in rush which led to wiping/overwriting efs partition I think
Click to expand...
Click to collapse
Well so we are in that together, I found something about fixing the IMEI with combination firmware, but it didn't work for me... "Please get the approval to use factory binary : param". Maybe you can try it. Tell me if it works for you
Guys, are your phones also a32's? If so can you check on a rooted phone if /data/nvram Is here? I'm pretty sure that's something important and it's missing for me.
Sunderw3k said:
Guys, are your phones also a32's? If so can you check on a rooted phone if /data/nvram Is here? I'm pretty sure that's something important and it's missing for me.
Click to expand...
Click to collapse
Rooted. I made the warning thread so survived it. No data/nvram present on phone.
i have the same problem i have efs folder but how to restore?
Try
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
In TWRP console maybe?
I'm having the same problem with an a32 4g so I'm lurking.
TimmyP said:
Try
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
In TWRP console maybe?
Click to expand...
Click to collapse
doesn't that mean to completely erase those two modem partitions? Won't it finish destroying the phone capabilities?
Hi,
Same problem here after flashing my SM-A326B (A32 5G) with boot.img patched with magisk 23.0 (tried to use v24.1 but phone enters bootloop): it lose the IMEI at the instant I tried to call someone (it was working for a few days, until I tried to call. Receiving a call was no pb.).
I do have a BACKUP of EFS and SEC_EFS partitions made with the "Partitions Backup" app (by Wanam) just after rooting (because you need root to make backup of those partitions). I restored them, which restored IMEI #2 (not the first one) for a few minutes before being empty again (I think it was when I activated WiFi). SIM card was not in the slot. Now restoring the partitions does not change anything. IMEI always empty.
Maybe I should try to flash the original unpatched image and restore the EFS partitions to get the IMEI back (hopefully), then root again using TWRP this time...? The thing is I already have data and apps on the phone and I am tired of reinstalling everything.
I hope description of my pb helps to solve this bug...
dronkit said:
I'm having the same problem with an a32 4g so I'm lurking.
doesn't that mean to completely erase those two modem partitions? Won't it finish destroying the phone capabilities?
Click to expand...
Click to collapse
Ya, but when you reboot it might reset efs after they are wiped. Seen this in the past. Phones are already missing \efs completely with no backup.
TimmyP said:
Try
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
In TWRP console maybe?
Click to expand...
Click to collapse
I tried this, doesn't work (error partition not found)
rousselmanu said:
I tried this, doesn't work (error partition not found)
Click to expand...
Click to collapse
this isn't for Mediatek based phones as far as I know, only for Qualcomm Snapdragon.
Even with a backup of EFS/SEC_EFS, it seems that it doesn't help much to recover the IMEI numbers...
I flashed the original firmware, installed TWRP plus magisk 23 from TWRP, then flashed the .img of EFS and SEC_EFS with adb using following commands:
adb shell
su # root
dd if=/dev/zero of=/dev/block/sdc2 # wipe EFS partition
dd if=/dev/zero of=/dev/block/sdc3 # wipe SEC_EFS partition
dd if=/mnt/sdcard/efs.img of=/dev/block/sdc2 # restore img of EFS before loosing IMEI
dd if=/mnt/sdcard/sec_efs.img of=/dev/block/sdc3 # idem for SEC_EFS
(phone automatically reboots between dd commands). Then I entered TWRP and wiped cache/davlik/data.
IMEI is still empty.
I reinstalled again the original firmware with ODIN (no root, no twrp), hoping that the restored EFS partition would do it with the untouched firwmare => IMEI still empty.
All in all, it seems that a backup of EFS/SEC_EFS doesn't help. Maybe these partitions are not damaged by magisk after all?
Comparing content of the img files before/after loosing IMEI I can spot a few differences in the files, I can detail if someone is interested...
TimmyP said:
Ya, but when you reboot it might reset efs after they are wiped. Seen this in the past. Phones are already missing \efs completely with no backup.
Click to expand...
Click to collapse
No, EFS is not reset after wiping with:
adb shell
su
dd if=/dev/zero of=/dev/block/sdc2 # wipe EFS partition
dd if=/dev/zero of=/dev/block/sdc3 # wipe SEC_EFS partition
For those who succeeded in rooting the A32 5G without this IMEI issue, could you detail the procedure? With version of the tools etc?
BTW, how come that even just unlocking the bootloader can erase the IMEI? see : https://forum.xda-developers.com/t/sim-not-working-on-a326br.4398149/
Related
Warning
i m not responsible if any thing went wrong with your phone
use this guide at your own risk
and this guide is only for restoring your lost IMEI during the flashing procees
it is not for changing your imei
this guide is for those users who have used "factory flash.bat"
And lost their phone IMEI & Persist partition
flash tissot_images_7.8.23_7.1 firmware using edl via mi flash
(to boot your phone to edl
boot it to fastboot and give the command "fastboot oem edl")
after flashing process is completed
just press and hold power key of the phone until you feel vibration
and let the phone to boot to normal
_____________________________________________________________________________________________________________________
if your persist partition is currupted
than you will notice that your phone will automatically reboots in under 60 seconds
_____________________________________________________________________________________________________________________
to restore persist partition download persist.img
reboot phone to twrp
and copy persist.img file to root of phone storage
now open terminal in twrp and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
this will restore your persist partition and fixes the issue of reboot
______________________________________________________________________________________________________________________
now to restore your imei
first download the following files
qualcomm_diag_driver.zip
MI A1 QCN AND PERSIST
imei to hex converter
hex editor
NEW QCN AND PERSIST
and
QPST
______________________________________________________________________________________________________________________
Restoring IMEI
now search for qcn edit guide on xda
convert your imei to hex using imei converter
and replace the required value with yours
now switch on the phone
and type *#*#717717#*#*
this will enable diag port of your phone
open qpst software download tool
go to restore tab
browse the ports and select qualcomm hs-usb diagnostics
browse xQCN file and select your modified file
enable allow phone mishmatch
click on start and wait for the process to be completed
when the status shows that "Restore is completed"
restart your phone
and your imei is now restored
_____________________________________________________________________________________________________________________
NOTE:
in the case you if your imei is not restored using above steps
than you need to wipe EFS and repeat the process from begening
to wipe your EFS use the following commands in twrp terminal
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p15
_____________________________________________________________________________________________________________________
thankss
Shared on telegram, thanks!
I'm not using qcn
not edl mode using
1. Flashing 7.8.23
2. 7.8.23 root ( patched_boot.img flashin using fastboot mode )
3. Usb diag mode on (dialler open trying or adb using su diag mode open )
4. Dualwriteimei using and restart phone aaaand booom imei restore (dualwriteimei is youtube searching only small size program and very very best )
5.Phone fastboot mode on and 8.1.10 rom flashing and booom
New telegram link:
https://t.me/joinchat/G1MMfkc6EbEZL-62Ii5YmA
thats not permanen, at last for me, maybe work on 7.8.23, but after update via ota or fastboot, after reboot or reset factory on setting imei unknow again
my solution right now, using custom rom, with august security and push modem file from latest stock rom for update baseband
It works, but if you want to update whole system, you have to backup partitions modemst1, modemst2 or EFS in TWRP, after you backup that, flash the new oreo firmware without data, if dont starts, recover the EFS and try again, if dont, do factory reset and if you haven't IMEI yet, restore de EFS, the problem here is, if you restart your EFS would be corrupted, so you have to restore the EFS and force update to the lastest update with EFS already installed, if youre lucky your EFS never be corrupted again
In my case everything is working fine
No issue upon updating or restoring
than so much raj bro 100% working method
I followed this procedure some time ago and haven't had issues. However today I flashed a new Oreo image and suddenly my IMEI was 0 again.
I restored my EFS partition using TWRP and now everything is fine again, except that my smallband version is back to 953_GEN_PACK-1.... which I think is the version that shipped with tissot_images_7.8.23_7.1. I wonder if it's a problem to run with an older smallband version?
Someone there who can help me fixing my IMEI? I have pushed the "flash_factory.bat"-button...
Mi A1 is working and rooted, no 30sec boot loop anymore, but QPST recognize my mobile just for secondes.
I'm holding my IMEIs in hand but unable to get them into QCN sinced days.
i was Restored persist.img via twrp terminal but my phone still restaring continously
raaz1431994 said:
Warning
i m not responsible if any thing went wrong with your phone
use this guide at your own risk
and this guide is only for restoring your lost IMEI during the flashing procees
it is not for changing your imei
this guide is for those users who have used "factory flash.bat"
And lost their phone IMEI & Persist partition
flash tissot_images_7.8.23_7.1 firmware using edl via mi flash
(to boot your phone to edl
boot it to fastboot and give the command "fastboot oem edl")
after flashing process is completed
just press and hold power key of the phone until you feel vibration
and let the phone to boot to normal
_____________________________________________________________________________________________________________________
if your persist partition is currupted
than you will notice that your phone will automatically reboots in under 60 seconds
_____________________________________________________________________________________________________________________
to restore persist partition download persist.img
reboot phone to twrp
and copy persist.img file to root of phone storage
now open terminal in twrp and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
this will restore your persist partition and fixes the issue of reboot
______________________________________________________________________________________________________________________
now to restore your imei
first download the following files
qualcomm_diag_driver.zip
MI A1 QCN AND PERSIST
imei to hex converter
hex editor
NEW QCN AND PERSIST
and
QPST
______________________________________________________________________________________________________________________
Restoring IMEI
now search for qcn edit guide on xda
convert your imei to hex using imei converter
and replace the required value with yours
now switch on the phone
and type *#*#717717#*#*
this will enable diag port of your phone
open qpst software download tool
go to restore tab
browse the ports and select qualcomm hs-usb diagnostics
browse xQCN file and select your modified file
enable allow phone mishmatch
click on start and wait for the process to be completed
when the status shows that "Restore is completed"
restart your phone
and your imei is now restored
_____________________________________________________________________________________________________________________
NOTE:
in the case you if your imei is not restored using above steps
than you need to wipe EFS and repeat the process from begening
to wipe your EFS use the following commands in twrp terminal
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p15
_____________________________________________________________________________________________________________________
if anyone have any issue in editing qcn to write your imei
plz join the telegram group Qualcomm IMEI Solution
thankss
Click to expand...
Click to collapse
Thanks Boss for your help
i was Restored persist.img via twrp terminal but my phone still restaring continously.....wht should i do???
Please Tell me boss.....i a totaly helpless
Can anyone please make a video tutorial regarding this fix or any referral video?
It'll be great help for me. I would really appreciate if anyone of you do this for me or users like us. PLEASE
?
imu hasib said:
it'll be great help for me. I would really appreciate if anyone of you do this for me or users like us. Please
?
Click to expand...
Click to collapse
after flashing rom and fixing persist, root your phone using twrp and magisk then use qpst , otherwise does not work
---------- Post added at 10:16 AM ---------- Previous post was at 09:54 AM ----------
fayshal_ahamed said:
thanks boss for your help
i was restored persist.img via twrp terminal but my phone still restaring continously.....wht should i do???
Please tell me boss.....i a totaly helpless
Click to expand...
Click to collapse
follow the steps and root your phone then connect with qualcomm drivers in qpst , restore qcn file created for ur imei,
THANK U @raaz1431994 UR SOUTION WORKED 4 ME
Solved it. Thank you, RAAZ MALHOTRA You are one of a kind!
Byramklc said:
I'm not using qcn
not edl mode using
1. Flashing 7.8.23
2. 7.8.23 root ( patched_boot.img flashin using fastboot mode )
3. Usb diag mode on (dialler open trying or adb using su diag mode open )
4. Dualwriteimei using and restart phone aaaand booom imei restore (dualwriteimei is youtube searching only small size program and very very best )
5.Phone fastboot mode on and 8.1.10 rom flashing and booom
Click to expand...
Click to collapse
Can You help me with that?
Or any one can help me to restore my stupid imei?
I dont understend 1# method
and your method dont work for me...
Im sooo stupid kiddo :crying::crying::crying:
Bro my telegram @Byramklc add me
Sent from my Mi A1 using XDA Labs
While I did finally manage to restore my IMEI, I found your "guide" really confusing.
You should without a doubt write it better, so people might understand it better as well.
I've been doing custom Android stuff for around 10 years. While I have never developed anything, I have gotten as far as to the point to where I have had to edit files and input hex.
You should _really_ mention when and how you use the files you provided.
You should also provide the "how-to" on editing the files.
I finally got it to work, but I had to read three different guides before I got it.
Still.. Thanks
Can someone confirm that PSN and FSN will missing if using flash_factory ?? (FSN&PSN can be found on *#*#6484#*#* Version Information)
hello guys ,thanks for the guide, i've restored my imei but the mobile data network still wont work, what it can be?
EDIT: I've resolved by using a newer version of qpst software, the 2.7.472.4 one
I managed to get IMEI back wifi and bluetooth working but sim network lost.
Sent the mobile to service center and they changed the motherboard.
Is this the only solution.......
---------- Post added at 06:28 AM ---------- Previous post was at 06:26 AM ----------
were you able to restore sim network as well???????
If yes pls write a complete guide with all the tools and files used
hello,
how are you team,
the problem with g955u,,,, its converted to g9550, so i flashed g955u and after flash baseband is gone,
so i try to flash lot of combinations latest FW,s u/u1 but still same ,,, now i,m in u5,
so i need to suggestion or solution to fix this **** ,
share your experience.
You mean you lost imei? Have you tried way to recover it via combination fw? If yes, then what you see in imei page in combination fw? Null, zero, or blank
i have the exact same problem sadly and no solution yet
ionut2003 said:
i have the exact same problem sadly and no solution yet
Click to expand...
Click to collapse
try this method problem will solve (IN SHA ALLAH)...
1.Boot into TWRP recovery.
2.From TWRP’s main screen, select Advanced » then Terminal.
3.Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
4.Reboot device.
after i use fastboot mathod my phone imei was gone
Fastboot doesn't erase phone's IMEI, unless you wiped /EFS partition by means of Fastboot.
You may watch this video
I wotched this but it can't help
jwoegerbauer said:
You may watch this video
Click to expand...
Click to collapse
Original title: Looking for backup of super partition for T-Mobile variant
If anyone is still on the latest stock T-Mobile ROM and can back up their super partition from TWRP and send it to me, that would be great.
My bootloader is locked btw.
A few days ago I tried running the DSU Loader that is enabled in Developer Options.
When I received the notification to reboot into the Generic System Image, my phone booted to a qualcomm error screen, and then after rebooting again, it showed a screen that said "Your phone is corrupt. It can't be trusted and will not boot."
From research, it seems to have messed up the system partition, and using Qualcomm Product Support and Oneplus Phone Reset tools I can backup and write to the phone partitions directly. If someone with a T-Mobile Oneplus 9 and has a unmodified super partition could be so kind as to upload a backup of their super partition, I would greatly appreciate it.
You can upload to mega.nz, they give you 20GB on sign-up.
avid_droid said:
Why not just MSM?
Click to expand...
Click to collapse
So I don't lose userdata
avid_droid said:
Doubt anyone will provide a super partition of "Their" current data. Reason being why I mentioned using MSM. No offense to you,but,caution should be taken before flashing anything knowing the dangers of flashing. Not sure if anyone will provide it,but, I would recommend MSM.
Doing a flash on anything is solely the users mistake/error and owns responsibility.
Trust me. I've flashed and bricked at my own discretion and advise everyone to do the same with any type of flash.
Click to expand...
Click to collapse
My bootloader is locked. It shouldn't be possible for my device to end up like this.
I did not personally flash anything, it was DSU Loader in Developer Options. Also I can not flash anything, my bootloader is locked.
Also the super partition only contains system.img, system_ext.img, vendor.img, odm.img, and product.img.
Any user data is stored in the userdata partition.
avid_droid said:
I'll see if I can extract and provide for you later. If worst comes to worst,just prepare to do a MSM restore
Click to expand...
Click to collapse
Oh I'm prepared for MSM restore, I've just been doing research to see if there is anyway around wiping userdata.
Thank you for your help.
I see you have a Oneplus 9 Pro, unless you happen to have a Oneplus 9 as well? I need the super partition for only Oneplus 9 non-pro Tmobile variant.
Part of the security are some of the properties found in build.prop in the super partition. For example, the build fingerprint needs to match exactly
com.android.system.build.fingerprint: "OnePlus/OnePlus9TMO/OnePlus9TMO:11/RKQ1.201105.002/2107151801:user/release-keys"
I assume on the pro it would have different build fingerprint?
I ended up in an EDL loop when trying to convert my second OP9. I think I took a full backup of the T-Mobile firmware before I set it up. When I check, I'll let you know if I have a super backup.
I think I've figured something out.
I can back up all the partitions from EDL mode using this EDL tool, and then I can MSM reset, unlock the bootloader, and then flash my backed up partitions through fastboot. Anyone know of any reasons why this wouldn't work?
The only issue I can think of is if there are encryption keys resident in some place other than the UFS storage and they get cleared by MSM reset.
Yup, looks like the keystore partition I backed up is all zeros, might just be an unused partition though
Hi everybody,
A few days ago, I found a way to restore my Nokia 3, because it was dead (at least, I thought that). I flashed the ROM through brom mode, so it's working again. But there's a problem. After I made it up and running, I tried to root it and install TWRP, but I had a few errors, and when I reflashed it, accidentally formatted everything (SP Flash Tool Format all+download). Soo, I lost IMEI, and SN too. I successfully reflashed nvram partition, but I can't restore IMEI, and SN. I found the real SN from a previously opened CMD prompt, but I don't have an idea how to restore it. Unfortunately, with formatting everything, I also locked back the bootloader too, moreover I don't have a real SN on the device (123456789ABCDEF) so I can't unlock it through fastboot. I also made a ROM file for WwR to extract the ROM, so I have the nvdata, nvram, protect1, protect2 and other partitions (attached a picture of them), that 've been copied before fully wiping the device. I was wondering about, is it possible to reflash some partitions to get back the IMEI and SN, and with the real SN on the device unlock the bootloader again?
gurtnyi said:
Hi everybody,
A few days ago, I found a way to restore my Nokia 3, because it was dead (at least, I thought that). I flashed the ROM through brom mode, so it's working again. But there's a problem. After I made it up and running, I tried to root it and install TWRP, but I had a few errors, and when I reflashed it, accidentally formatted everything (SP Flash Tool Format all+download). Soo, I lost IMEI, and SN too. I successfully reflashed nvram partition, but I can't restore IMEI, and SN. I found the real SN from a previously opened CMD prompt, but I don't have an idea how to restore it. Unfortunately, with formatting everything, I also locked back the bootloader too, moreover I don't have a real SN on the device (123456789ABCDEF) so I can't unlock it through fastboot. I also made a ROM file for WwR to extract the ROM, so I have the nvdata, nvram, protect1, protect2 and other partitions (attached a picture of them), that 've been copied before fully wiping the device. I was wondering about, is it possible to reflash some partitions to get back the IMEI and SN, and with the real SN on the device unlock the bootloader again?
Click to expand...
Click to collapse
have you been able to fix it?
mvikrant97 said:
have you been able to fix it?
Click to expand...
Click to collapse
Fortunately yes, reflashed protect1, protect2, proinfo partitions from a full phone backup made earlier with WWR MTK (I guess that was its name)
For everybody, who's reading this cause having the same problem:
Instead of trying that as a method (you can, but do it on your own risk), write me a dm and I'll try to preapare some instructions for you iny free time.
Ps.: proinfo contains the SN, so with a hex editor, I was able to check my SN and I could probably rewrite it too.