I have an EA ROM on an ATT device, but we all faced on the A11 that after fixing the NT code, we are not able to use LTE and mobile data, but then we had the PDC tool where we loaded the .mbn.
Now on the A12 and A13 we don't have the ability to use PDC so I was forced to do something to get LTE & mobile data back and I made some changes to the modem .img where the problem was fixed.
Note: I read before that some people were not able to fix the fingerprint after croosflashing ROMs, now we can do it but by cross-modem images.
Current patched mods are for EA ROM. A12+ but there are one version for A11 if you do not want to use PDC tool.
Spoiler: A11 patched modem
Patched modem only for A11
in the previous modified versions, users had the problem that Netflix did not work on their A11, with V1.2 or Universal version where the mentioned problems have been fixed.
Spoiler: A12 patched modem
We have three versions of the modems
V1 is with minimal changes only for EU bands A12(outside it wil work or not)
V2 & V3 is with slightly bigger changes and can be used outsde EU,
V1-L-51A modem with a fixed fingerprint after cross-flashing the EA firmware with right signals (only docomo JP variants).
Spoiler: A13 patched modem
For A13, only versions V1 and V2 were made accordingly because previously V1 had the least number of users on A12.
V1 with fewer changes
V2 with more changes.
Spoiler: Universal patched modem
Modem_Universal fully compatible with A10+ android but there are more changes than V3 A12 modem and can be some bugs like fingerprint does not work on A13
Spoiler: Patched modem JP variant
I would also like to make JP modems for A13 (Docomo & Softbank), anyone who wants to help in making a JP patched modem should contact me on Telegram @JigsawProfile.
Note: it is always better to use a modem with fewer changes, this ensures that the updates are original and newer.
5G and VoLte working.
You can flash modems easily via Fastboot to A/B slots or you can flash via Qfill.
Flashing patched modem won"t bricked /bootlop your device.
DOWNLAOD modem.img
Note: Planned to create a magisk module, in those cases it would not be necessary to flash the Modem partition, in those cases, by removing the magisk/module or resetting the device to factory settings, we lose the modem changes.
I would also like to mention that I don't have daily access to my computer, but only a few hours a week, and that limits my possibilities.
can this modem works in docomo variant crossflashed EA south african firmware
k.syedhussain said:
can this modem works in docomo variant crossflashed EA south african firmware
Click to expand...
Click to collapse
I do not sure but you can try.
I think it doesn't matter whether it is ATAT, TMO or some other variant should work
I have locked bootloader,..can convert into bin for edl
k.syedhussain said:
I have locked bootloader,..can convert into bin for edl
Click to expand...
Click to collapse
Yout can flash .img via qfil
JigsawMobile said:
Yout can flash .img via qfil
Click to expand...
Click to collapse
Will try ,did you modified volte capabilities will it catch volte signals after flashing modified modem
k.syedhussain said:
Will try ,did you modified volte capabilities will it catch volte signals after flashing modified modem
Click to expand...
Click to collapse
tried with locked bootlloader end with bootloop
k.syedhussain said:
tried with locked bootlloader end with bootloop
Click to expand...
Click to collapse
JigsawMobile said:
Yout can flash .img via qfil
Click to expand...
Click to collapse
can you modify my modem file enable volte vowifi for indian networks
i have Japanese docomo A51L version its only work with Japanese original backup modem.
i crossflashed european za firmware south african all work perfectly.but in network setting its show only cdma roaming option.
k.syedhussain said:
can you modify my modem file enable volte vowifi for indian networks
i have Japanese docomo A51L version its only work with Japanese original backup modem.
i crossflashed european za firmware south african all work perfectly.but in network setting its show only cdma roaming option.
Click to expand...
Click to collapse
so when you flash EU modifed modems all work but you do not have volte ?
sometimes when "cdma roaming option" option shows when NT code is not corect, do you have nt coe error ?
missing oprion in networks settings it not depend of modems.
JigsawMobile said:
so when you flash EU modifed modems all work but you do not have volte ?
sometimes when "cdma roaming option" option shows when NT code is not corect, do you have nt coe error ?
missing oprion in networks settings it not depend of modems.
Click to expand...
Click to collapse
No when i flashed EU modem my phone went to bootloop....
Yes i have NT CODE ERROR
I AM USING docomo v60 with EU firmware with docomo model....
Actually you sent me bootloader flashing file...
Can you flash both modified modem in your mobile and take backup from qfil share me....
Yes i can backup modems via qfill
try this first when you flash modifed modems via fastboot than backup via qfill and that modems try to open via qfil, and tell me will it open in the .7z.
well you can flash modifed images via qfill, qfill can flash and .img files
JigsawMobile said:
Yes i can backup modems via qfill
try this first when you flash modifed modems via fastboot than backup via qfill and that modems try to open via qfil, and tell me will it open in the .7z.
well you can flash modifed images via qfill, qfill can flash and .img files
Click to expand...
Click to collapse
Ok now i can t unlock the bootloader now.
Do you have modified modem backup
Hello, should I flash the .gz file or do I need to extract it? If so, it looks like both images are 2kb bigger than the original ones.
You van flash via fastboot or via qfill, qfill can flash and .img.
Exttact from .gz you will get
Img
I don't get any .img files, only files with no extension.
Tried to flash tem via qfil and fastboot, both methods give me a kernel crash.
Also, both qfil and fasboot warned me about those files not being the exact partition size which is 361.758.720 bytes, instead, they are 361.760.256 bytes.
I tried flashing them whole and also trimmed by deleting everything post 0x158FFF0, both made me kernel crash. Restoring the backed up modem partition gets me to boot again.
edit: I'm using 7zip to extract, maybe that's the issue?
lucasdessy said:
I don't get any .img files, only files with no extension.
Tried to flash tem via qfil and fastboot, both methods give me a kernel crash.
Also, both qfil and fasboot warned me about those files not being the exact partition size which is 361.758.720 bytes, instead, they are 361.760.256 bytes.
I tried flashing them whole and also trimmed by deleting everything post 0x158FFF0, both made me kernel crash. Restoring the backed up modem partition gets me to boot again.
edit: I'm using 7zip to extract, maybe that's the issue?
Click to expand...
Click to collapse
If showing like modem_a just click one more time and you will se modem_a.img.
I will reupload in the .rar
k.syedhussain said:
Ok now i can t unlock the bootloader now.
Do you have modified modem backup
Click to expand...
Click to collapse
If showing like modem_a just click one more time and you will se modem_a.img. it imgs reatore via qfill.
To reatore do not extract only modem_a, need to be with extension .img
I will reupload in the rar compression
I would like to test the LG v60 Japanese version on a machine that has been cross-flexed to the Canadian version. Can I allow download access?
Thank you for the access.
It also doesn't work in the Japanese version -> Canadian version.
I had a question when I saw the text file in the compressed file.
Are the modified folders image\sdx55m, sdx55, modem_pr\so" and other att original modem files placed in the ea modem?
andamiro00 said:
Thank you for the access.
It also doesn't work in the Japanese version -> Canadian version.
I had a question when I saw the text file in the compressed file.
Are the modified folders image\sdx55m, sdx55, modem_pr\so" and other att original modem files placed in the ea modem?
Click to expand...
Click to collapse
All changed files EA
I did not croosflash att and ea modems but i will test it method when i having att a12 original modem, i believe that we can get to work via croisflashiig original -> EA modems.
Note: if you want to try croisflash modem you need rooted device.
Why you using canadian rom version why not EA ?
Related
https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X3/Style/XT1572/EU
and also you can find other's firmware in it.
Good new for XT 1572 users!
Many thanks!
Okay. This looks really good.
A couple of noobish questions. This phones modem/OS version/Country/Pure-style mallarky is damaging my brain, compared to my old Samsungs..
I assume that this file needs to be extracted and each file installed via Fastboot. If so, how many of the files need to be installed. (Do I need Recovery.img, if I would rather not have to reinstall TWRP)
Even better, is it possible to flash this via TWRP ? (asking just in case...)
Can I flash this on top of my RessurectionRom 7.0.. Which was probably based on a MM modem ? Is everything needed in this package, or will the old modem result in no connection ?
Thank you in advance.
Great, thanks a lot! A small question, is there a difference between the NPH and NPHS versions of the firmware? I guess N stands for Nougat (since there's also L and M versions), but what does the S mean?
timmtn said:
I assume that this file needs to be extracted and each file installed via Fastboot. If so, how many of the files need to be installed. (Do I need Recovery.img, if I would rather not have to reinstall TWRP)
Even better, is it possible to flash this via TWRP ? (asking just in case...)
Can I flash this on top of my RessurectionRom 7.0.. Which was probably based on a MM modem ? Is everything needed in this package, or will the old modem result in no connection ?
Click to expand...
Click to collapse
extracted and flashed via fasboot or rsd
it can be flashed on any custom roms
it is not recommended to flash the file bootloader.img and gpt.bin
janpascal said:
Great, thanks a lot! A small question, is there a difference between the NPH and NPHS versions of the firmware? I guess N stands for Nougat (since there's also L and M versions), but what does the S mean?
Click to expand...
Click to collapse
it means that the version of this firmware is higher and newer,and the firmware has packed the latest security patch.
zi_mo said:
extracted and flashed via fasboot or rsd
it can be flashed on any custom roms
it is not recommended to flash the file bootloader.img and gpt.bin
Click to expand...
Click to collapse
Just what I was looking for. Thank you.
Previous android version: Android 11
Previous base-band version: A125USQU2BUG5
company: wireless cricket
In the context of flashing with the new firmware I used :
- Odin version: 3 v3.14
- Firmware used: Samfw.com_SM-A125U_USC_A125USQU2BUL1_fac_2
The error is related to the vbmeta check. Did you used a sock firmware or you have patched it with magisk? Btw i reccomend to use frija to download the firmware.
If i can suggest I would make this steps:
1) download latest firmware with frija
2) Flash the stock and see if it work
Otherwise if this not help:
1) download latest firmware with frija
2) patch the whole ap and not only boot.img with magisk
3) open odin and flash it using the patched ap on the ap slot
If nothing above works, I think you can try this... not sure it will work. Replace inside the ap the vbmeta.img with the attached one that have the disabled verified boot.
Oneplus# said:
The error is related to the vbmeta check. Did you used a sock firmware or you have patched it with magisk? Btw i reccomend to use frija to download the firmware.
If i can suggest I would make this steps:
1) download latest firmware with frija
2) Flash the stock and see if it work
Otherwise if this not help:
1) download latest firmware with frija
2) patch the whole ap and not only boot.img with magisk
3) open odin and flash it using the patched ap on the ap slot
If nothing above works, I think you can try this... not sure it will work. Replace inside the ap the vbmeta.img with the attached one that have the disabled verified boot.
Click to expand...
Click to collapse
Thanks for the reply.ok
1- The firmware is stock.
2- I didn't patch any of the files I got ( any recommended guide on how to proceed>?)
3- I' so new at this
But anyways, yesterday I kind of sorted out the stuck by adding BL file, and CSC file along the AP file to ODIN, the phone restarted ok but found out it hasn't been unlocked from the carrier yet, so I guess that by judging what u just said, there are few thing I need a guide to
- Flashing the stock
- Patching the AP file
Ps Frija opens up when executed, but it closes in less than 1 second. (Pc 's OS: win 10 enterprise 64 bits)
leonardo07746 said:
Thanks for the reply.ok
1- The firmware is stock.
2- I didn't patch any of the files I got ( any recommended guide on how to proceed>?)
3- I' so new at this
But anyways, yesterday I kind of sorted out the stuck by adding BL file, and CSC file along the AP file to ODIN, the phone restarted ok but found out it hasn't been unlocked from the carrier yet, so I guess that by judging what u just said, there are few thing I need a guide to
- Flashing the stock
- Patching the AP file
Ps Frija opens up when executed, but it closes in less than 1 second. (Pc 's OS: win 10 enterprise 64 bits)
Click to expand...
Click to collapse
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Oneplus# said:
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Click to expand...
Click to collapse
thanks for all that
- it s sim block
Oneplus# said:
When you flash with Odin you always need to use all the files provided on the stock firmware ap, bl, csc and cp. If u are upgrading you can use the home_csc instead of the csc file that will let you keep your data.
Are you sure you have installed the framework that Frija need?
For the ap patching, is only meant if you want root your phone, flashing the whole ap instead of the boot.img only will let you fix the vbmeta checks too.
Install the magisk app.
Open it and tap Install, it will ask for a file to patch, chose the ap file of the stock firmware you downloaded.
Final step, flash ap patched and the others (bl,csc,cp).
When you say unlocked by the carrier what do you mean? You have any sort of sim block? Or you only want remove your carrier apps and configs?
Click to expand...
Click to collapse
Mannn thanks!
I rooted my tab 5Se a long time ago and deleted the firmware files except the AP.
I got stuck on the same screen today when I re-locked my bootloader after a stock AP-only flash
Then I saw your reply here and got the rest of the files flashed and it worked and booted
And for those who are reading if you don't have a SIM on your tablet you don't need a CP that's why you won't find it in your firmware zip file
Cheerios
After successfully rooting my Nord 2T by backing up and then patching the stock boot.img I proceeded to patch the inactive slot within Magisk (it was unecessary of me..) and after rebooting entered a loop. Anyone know where I can get the factory ROM? I was on the May patch. Thanks in advance!
I am also looking for the factory OTA image.
How did you get the boot.img exactly?
jolaviska said:
I am also looking for the factory OTA image.
How did you get the boot.img exactly?
Click to expand...
Click to collapse
Good ol SP Flash but I think the backed up images are corrupted hence the need of factory firmware to use it to restore my device.
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
So extracting boot. img from your file won't be enough to do Root right?
Riski3Run said:
So extracting boot. img from your file won't be enough to do Root right?
Click to expand...
Click to collapse
You can't extract from the firmware. You must use spflash tool to pull the boot.img from the device (mediatek devices are a bit different to Snapdragon devices)
I'm going to do it today but I had to bring my daughter to the hospital after a fall she had which required stitches.
Once I have it extracted I might write a guide on how to do it with links to all firmware needed and have a thread where we will have both the stock and magisk patched boot.img's available.
Been like 6 weeks and no root on my device, this is the longest I have went without rooting in almost 7 years
garylawwd said:
You can't extract from the firmware. You must use spflash tool to pull the boot.img from the device (mediatek devices are a bit different to Snapdragon devices)
I'm going to do it today but I had to bring my daughter to the hospital after a fall she had which required stitches.
Once I have it extracted I might write a guide on how to do it with links to all firmware needed and have a thread where we will have both the stock and magisk patched boot.img's available.
Been like 6 weeks and no root on my device, this is the longest I have went without rooting in almost 7 years
Click to expand...
Click to collapse
Thanks. I rooted mine within a day but went too far with patching the inactive slot via Magisk and now phone is soft bricked. If you are still interested in extracting the boot image for patching then use this tool. I tried to use it to flash the payload.bin but phone still not booting. I even flashed all the extracted images manually in fastbootd. I guess the OTA file doesn't contain all the files needed to restore the device back to its factory state.
Anyone with the full firmware containing the SP Flash Scatter file please share it. You'll be saving everyone else. I bought my phone on a trip and there are no OnePlus repair centers over here so won't be using my phone until I can restore it myself
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
Hello
Can't you upload this zip file somewhere else?
Each time download is not finished.
Riski3Run said:
Hello
Can't you upload this zip file somewhere else?
Each time download is not finished.
Click to expand...
Click to collapse
Saw you were able to fully extract the payload.bin so could you mirror the files as well..
Issue is now resolved Thanks @Riski3Run and @garylawwd
Alternatively extracting and flashing the payload.bin ALSO works. No need to extract the images just use this beautiful tool
garylawwd said:
Apologies I did not realise you still needed the firmware. I have mirrored it here if you still need it May Patch Full ROM
Click to expand...
Click to collapse
Hi Garylawwd, when I click on the link it displays an empty folder. Can you perhaps reupload the firmware? My device is bricked and I'm unable to find the stock rom and scatter file for CPH2399 :/
woodiewood3 said:
Hi Garylawwd, when I click on the link it displays an empty folder. Can you perhaps reupload the firmware? My device is bricked and I'm unable to find the stock rom and scatter file for CPH2399 :/
Click to expand...
Click to collapse
Were you on the latest June security patch?
garylawwd said:
Were you on the latest June security patch?
Click to expand...
Click to collapse
Yes I was on the June patch, but I completely messed up my Phone.. can't boot into recovery or fastboot, screen stays black.
When I plug in the phone my computer recognizes it as Mediatek usb port.
When I try to use mtk_gui it is able to connect but it freezes after DA extension and thus I'm unable to read or write anything from or to the device via mtk_gui.
I hope that I can flash the stock firmware via SP flash tool, otherwise I will probably need to send it to OP repairs centre.
But to flash via SP flash tool I do need the firmware + scatter file. ATM I'm unable to find them.
I am unable to create the scatter file via MTKDroid it says --- Unknown ROM structure, backup NOT possible!
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
A week ago, I wanted to try updating my OP9 LE2117 to OOS12 that was on global firmware, since I was rooted and had TWRP on my device, I needed to go back to stock, so I followed this thread using the modded india TMobile MSM to OnePlus 9 pro firmware, and then downloaded OOS 11.2.10.10 here "signed flashable zips > LE25AA Global > 11.2.10.10", then used fastboot enhanced to flash the payload.bin file to go back to OnePlus 9 firmware with OOS11, and I did a local update to OOS12 C.48, but after I did, the phone touchscreen was unresponsive and didn't work, and the dual sim bug was present "where my phone couldn't recognize my sim unless I eject it and inserted back in it the sim, the only thing I could do to interact with the phone is the buttons on the phone and using a USB C wireless mouse, so I india MSM again and fastboot enhanced back to 11.2.10.10, I've also tried flashing a custom rom on the device, I've flashed Lineage OS 19.1, even though the compatible devices didn't list LE2117, surprisingly I was able to boot into LOS 19.1 but same thing, unresponsive touchscreen, only operable with USB C wireless mouse, is there is a reason why the touchscreen is unresponsive, and if there is a solution to get OOS12 on the device without any touchscreen issues/sim issues? Any help will be appreciated. If you need any more info I'm more than happy to provide
This is my first post on XDA forums, long time lurker here.
U will first have to msm to tmo modded with target id india then convert to global u wont have any touchscreen issues
TMO MSM India mod.zip
drive.google.com
rizzmughal said:
U will first have to msm to tmo modded with target id india then convert to global u wont have any touchscreen issues
Click to expand...
Click to collapse
Any exact guide on this?
underworld737 said:
Any exact guide on this?
Click to expand...
Click to collapse
Flash the msm above mentioned then just follow other safe convert mothod
rizzmughal said:
Flash the msm above mentioned then just follow other safe convert mothod
Click to expand...
Click to collapse
just tried flashing the tmo modded msm with sha256 checked and use lite firehouse unchecked, but i was getting "unsupported target eu", so i tried with sha256 unchecked and use lite firehouse checked, still got the same problem, currently the device is running 11.2.10.10 with twrp & magisk, flashed the payload.bin file via fastboot enhanced after using the oneplus 9 pro india msm.