So i accidently erased my persist partition and i don't have any backup... Can someone with the same model upload the persist.img for me?
Mod edit: Thread closed as duplicate of
HTC U11 persist.img needed for Europe (401) dual sim
So i accidently erased my persist partition and i don't have any backup. Can anyone with the same model upload the persist.img for me :cry:
forum.xda-developers.com
i want to convert my t-mobile op8 to global my questions :
1# is there a specific msm tool for my op8
2# how exactly do i backup my persist
3# how do i restore my recovery i accidentally .. overwrote the a - b partition with twrp on a11 and afterwards read that that would not work like on every other phone cause i'm a smart***
4#without adding second imei to the phone how would 2 sim support work do i have to flash t-m modem ?
Was wondering if anyone would help the OP 8 community by posting the first QCN file for t-mobile OP 8, I need it very badly cuz I recently messed up my persist partition and I had to SMT download with MSM to make it boot again, but it booted with no IMEI no MEID no fingerprint.
Now I can't unlock the bootloader by flashing the "unlock_token.bin" file, as it gives an error
"Verify failed (3: -2)" I think it's because of the messed up persist partition. I could fix the persist issue if there was some way to bypass the T-Mobile unlock token nonsense cuz I have a backup of my persist and efs partition before the accedent, I saw in the threads that there are modded MSM tools to convert to global without unlocking the bootloader so a "fastboot oem unlock" command would be sufficient to unlock the bootloader in global fw.
A ".elf" firehose programmer file would be a help too.
To all the devs laying out there it's ur time to shine rn.
I would appreciate the help from you guys as it's my first post and I'm sorry if it's not in the right cat.
I have the same problem with my OP 8 t-mobile, did you find the solution?
L0ND0NB0Y said:
Was wondering if anyone would help the OP 8 community by posting the first QCN file for t-mobile OP 8, I need it very badly cuz I recently messed up my persist partition and I had to SMT download with MSM to make it boot again, but it booted with no IMEI no MEID no fingerprint.
Now I can't unlock the bootloader by flashing the "unlock_token.bin" file, as it gives an error
"Verify failed (3: -2)" I think it's because of the messed up persist partition. I could fix the persist issue if there was some way to bypass the T-Mobile unlock token nonsense cuz I have a backup of my persist and efs partition before the accedent, I saw in the threads that there are modded MSM tools to convert to global without unlocking the bootloader so a "fastboot oem unlock" command would be sufficient to unlock the bootloader in global fw.
A ".elf" firehose programmer file would be a help too.
To all the devs laying out there it's ur time to shine rn.
I would appreciate the help from you guys as it's my first post and I'm sorry if it's not in the right cat.
Click to expand...
Click to collapse
Is this a file I would have somewhere on my phone? I have a bone stock T-Mobile On|plus 8. If it's on my phone I would be more| than happy to send it.
Did you fix this sh#t have same issue
L0ND0NB0Y said:
Was wondering if anyone would help the OP 8 community by posting the first QCN file for t-mobile OP 8, I need it very badly cuz I recently messed up my persist partition and I had to SMT download with MSM to make it boot again, but it booted with no IMEI no MEID no fingerprint.
Now I can't unlock the bootloader by flashing the "unlock_token.bin" file, as it gives an error
"Verify failed (3: -2)" I think it's because of the messed up persist partition. I could fix the persist issue if there was some way to bypass the T-Mobile unlock token nonsense cuz I have a backup of my persist and efs partition before the accedent, I saw in the threads that there are modded MSM tools to convert to global without unlocking the bootloader so a "fastboot oem unlock" command would be sufficient to unlock the bootloader in global fw.
A ".elf" firehose programmer file would be a help too.
To all the devs laying out there it's ur time to shine rn.
I would appreciate the help from you guys as it's my first post and I'm sorry if it's not in the right cat.
Click to expand...
Click to collapse
[GUIDE] Complete Step-by-Step Convert T-Mobile to Global (or other) firmware
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case. *** USE USB 2.0 Port and Windows Machine !!! BEFORE YOU CONTINUE, POST #3 CONTAINS AN IMPORTANT MESSAGE SPECIFICALLY FOR...
forum.xda-developers.com
Use this to downgrade to stock ops then flash with unlock ops ( guide is given in this thread) then unlock bootloader flash fastboot rom then write imei meid with miracle box [email protected] if not solved then flash qcn hope it works
Tecno Spark 10C KI5K Flash File 100% Tested Update [ Firmware] OK - Borsha Mobile Flash File 100% Tested Update [ Firmware] OK
Tecno Spark 10C KI5K Flash File
bak2461.blogspot.com
Realme C35 RMX3511 Flash File Update Stock Firmware [Borsha Mobile ] - Borsha Mobile Flash File 100% Tested Update [ Firmware] OK
Realme C35 RMX3511 Flash File, Realme C35 RMX3511 Flash File Firmware, Realme C35 RMX3511 Flash File Firmware Download, Realme C35 RMX3511 Flash File
bak2461.blogspot.com
I have a T-Mobile OP9 that I just purchased used. The bootloader was unlocked and I received the file along with the phone. The phone was originally on A11 L2115 (but still showed L2117 in Settings / About). I rooted and grabbed the modemst1, modemst2, and persist.img files with Partition Backup before anything else. I then subsequently updated officially to A13 through an update via local storage then through the OTA updater and it was then fully seen as L2115. I then realized that the rom I wanted needed A12 firmware so I went back to A11 then unlocked bootloader again and attempted to update firmware only off the CrDroid A12L update page. I chose not to flash the modem during that flash and then afterwards my service stopped working. It read the IMEI and baseband and would recognize that it was T-Mobile but no calls/text/data. I then got the bright idea to go back to Tmobile A11 through MSM then unlock bootloader, root, and use Partition Backup to restore the modems and persist imgs. After that, even though I can successfully flash the full Tmo MSMDownload Tool ops file, it only bootloops. If the MSM tool can't fix it - is it done for?
es0tericcha0s said:
I have a T-Mobile OP9 that I just purchased used. The bootloader was unlocked and I received the file along with the phone. The phone was originally on A11 L2115 (but still showed L2117 in Settings / About). I rooted and grabbed the modemst1, modemst2, and persist.img files with Partition Backup before anything else. I then subsequently updated officially to A13 through an update via local storage then through the OTA updater and it was then fully seen as L2115. I then realized that the rom I wanted needed A12 firmware so I went back to A11 then unlocked bootloader again and attempted to update firmware only off the CrDroid A12L update page. I chose not to flash the modem during that flash and then afterwards my service stopped working. It read the IMEI and baseband and would recognize that it was T-Mobile but no calls/text/data. I then got the bright idea to go back to Tmobile A11 through MSM then unlock bootloader, root, and use Partition Backup to restore the modems and persist imgs. After that, even though I can successfully flash the full Tmo MSMDownload Tool ops file, it only bootloops. If the MSM tool can't fix it - is it done for?
Click to expand...
Click to collapse
Sounds like it's not factory resetting when running MSM tool. Boot into recovery and wipe device. Then it will boot.
Regrettably, I've already tried with and without wipes in recovery. I've successfully flashed the recommended T-mobile firmware and there seems to literally only be one option to try for this variant I've seen anywhere. I know the file, Downloader, drivers and USB cable work as I used it to successfully go back a couple of times before the reflashing of the modems and persist files. It also passes still without error but it'll reboot after it sets on the T-mobile boot up for a couple of minutes.
mattie_49 said:
Sounds like it's not factory resetting when running MSM tool. Boot into recovery and wipe device. Then it will boot.
Click to expand...
Click to collapse
es0tericcha0s said:
Regrettably, I've already tried with and without wipes in recovery. I've successfully flashed the recommended T-mobile firmware and there seems to literally only be one option to try for this variant I've seen anywhere. I know the file, Downloader, drivers and USB cable work as I used it to successfully go back a couple of times before the reflashing of the modems and persist files. It also passes still without error but it'll reboot after it sets on the T-mobile boot up for a couple of minutes.
Click to expand...
Click to collapse
U can fix ur bricked device anytime with op 9 pro india msm but i would say if u want try global u shuld try msm conversion without unocking bootloader if problem exist flash 2115 a11 with fastboot enhance u will be out of bootloop i have been there solved it this way
Thanks so much for the reply. I downloaded an Indian 9 Pro firmware but I couldn't get it to flash. Is there a specific one? I used the one recommended in the main thread for unbricking, I thought but I've been trying so many things at this point its blurring together.
Is it possible to fastbootd flash when locked to a different model's firmware?
rizzmughal said:
U can fix ur bricked device anytime with op 9 pro india msm but i would say if u want try global u shuld try msm conversion without unocking bootloader if problem exist flash 2115 a11 with fastboot enhance u will be out of bootloop i have been there solved it this way
Click to expand...
Click to collapse
I was able to recover with the Indian version - thanks! Still don't have my baseband or IMEI though.
es0tericcha0s said:
I was able to recover with the Indian version - thanks! Still don't have my baseband or IMEI though.
Click to expand...
Click to collapse
Flash modded tmo msm with target id india
rizzmughal said:
Flash modded tmo msm with target id india
Click to expand...
Click to collapse
I did try this last night. I am able to flash this successfully, but it sends me into a bootloop.
Same as the original Tmo MSM did before I flashed the Indian 9 Pro MSM (I haven't had luck changing the Target back to something that will work with the original Tmo MSM file yet). With or without factory data reset, I get a bootloop on a Tmobile version of the MSM. Boots up fine with Indian 9 Pro.
I can also switch to global firmware with the official 1+ zip after it boots with the Indian MSM either via temp custom recovery or via local storage updates but it still leaves me with null IMEI and no baseband. I've tried to flash just the Tmo NON-HLOS.bin file in fastbootd while on the Indian firmware and just got a bootloop too. It definitely seems related to the me screwing up the baseband / radio situation but seems odd that the normal fixes aren't sticking. At least I got it to boot to something, but it's still unuseable.
es0tericcha0s said:
I did try this last night. I am able to flash this successfully, but it sends me into a bootloop.
Same as the original Tmo MSM did before I flashed the Indian 9 Pro MSM (I haven't had luck changing the Target back to something that will work with the original Tmo MSM file yet). With or without factory data reset, I get a bootloop on a Tmobile version of the MSM. Boots up fine with Indian 9 Pro.
I can also switch to global firmware with the official 1+ zip after it boots with the Indian MSM either via temp custom recovery or via local storage updates but it still leaves me with null IMEI and no baseband. I've tried to flash just the Tmo NON-HLOS.bin file in fastbootd while on the Indian firmware and just got a bootloop too. It definitely seems related to the me screwing up the baseband / radio situation but seems odd that the normal fixes aren't sticking. At least I got it to boot to something, but it's still unuseable.
Click to expand...
Click to collapse
U cannot flash modem or anything thru fastboot without unlock bootloader
rizzmughal said:
U cannot flash modem or anything thru fastboot without unlock bootloader
Click to expand...
Click to collapse
Right, but I can go back to the Indian 9 Pro MSM then unlock. I just re-attempted the flash for the Tmobile MSM target IN and same - bootloop. It flashes everything successfully with no errors. I have tried with and without all of the boxes checked. It won't work with either Lite Firehose or SHA256 checked. Have flashed, reset, then flashed again. Doesn't seem to make much sense that one version will work but the actual one for my phone will not. I really, really dislike the T-Mobile variants of the past few 1+ phones. It really limits them and makes it a huge hassle to run anything custom.
I believe it is my EFS partition that is corrupted when I attempted to restore the modemst1 and modemst2 files through Partition Manager.
Update: I've fixed my baseband issues by fastboot wiping the modemst1 and 2 partitions. This has allowed me to now successfully flash and boot the Tmo firmware via the modded MSM for target IN. Now I am just left with repairing the IMEI which now reads 0.
Update 2: Was able to restore IMEI once I got the bootloader unlocked and reflashed my modemst1 and 2 with Fastboot Enhance.
Whew. Thanks for all the help!
es0tericcha0s said:
Right, but I can go back to the Indian 9 Pro MSM then unlock. I just re-attempted the flash for the Tmobile MSM target IN and same - bootloop. It flashes everything successfully with no errors. I have tried with and without all of the boxes checked. It won't work with either Lite Firehose or SHA256 checked. Have flashed, reset, then flashed again. Doesn't seem to make much sense that one version will work but the actual one for my phone will not. I really, really dislike the T-Mobile variants of the past few 1+ phones. It really limits them and makes it a huge hassle to run anything custom.
I believe it is my EFS partition that is corrupted when I attempted to restore the modemst1 and modemst2 files through Partition Manager.
Click to expand...
Click to collapse
That might be possible u shuld go for bootloader unlock first of all everything great to hear that u got it fixed
hi guys !
i would ask you please if anyone has backup for nv data or solution for this problem
Info :
model 21091116c
MTK_6877
8g /128
chinese version
unlocked bootloader
firmware global 14 .0.2
thanks for reading my post
i solve this problem by :
flashing firmware pissarro_ru_global_images_V14.0.2.0.TKTRUXM_20230313.0000.00_13.0_ru_98ade91a9a
unlock bootloader
after flashing by unlocktools go to mediatek section and go to restore NV
from this attached file choose Nv data -nram also proinfo
PS phone will not working if bootloader locked