Related
Hi community,
When I was flashing my device using MiFlash I made a mistake and chose "Flash and Unlock" then my device send this message: "This miui version can't be installed on this device". I can not install any ROM or Recovery because the phone is locked. I tried everything: EDL Point, MiFlash Unlocked. I don't wanna give up. I'm sure there's a solution but I need help. Any idea?
Thank you
VirusMagnus said:
Hi community,
When I was flashing my device using MiFlash I made a mistake and chose "Flash and Unlock" then my device send this message: "This miui version can't be installed on this device". I can not install any ROM or Recovery because the phone is locked. I tried everything: EDL Point, MiFlash Unlocked. I don't wanna give up. I'm sure there's a solution but I need help. Any idea?
Thank you
Click to expand...
Click to collapse
If the bootloader is locked, you might need to flash using an authorised account. They are only available at service centres these days..so that's your only choice ig.
Naveenthemi said:
If the bootloader is locked, you might need to flash using an authorised account. They are only available at service centres these days..so that's your only choice ig.
Click to expand...
Click to collapse
Yeah I friend of mine got a EDP account so he made the job. Now I tried to install a custom ROM but it doesn't work so I installed the original rom but when I'm setting up the phone I can't connect to Network (Wifi nor SIM) so I can not log in in MI Account. Any idea?
VirusMagnus said:
Yeah I friend of mine got a EDP account so he made the job. Now I tried to install a custom ROM but it doesn't work so I installed the original rom but when I'm setting up the phone I can't connect to Network (Wifi nor SIM) so I can not log in in MI Account. Any idea?
Click to expand...
Click to collapse
Maybe try to flash the ROM again.
Also, I need an authorised account too, could you please help me with getting one?
VirusMagnus said:
Yeah I friend of mine got a EDP account so he made the job. Now I tried to install a custom ROM but it doesn't work so I installed the original rom but when I'm setting up the phone I can't connect to Network (Wifi nor SIM) so I can not log in in MI Account. Any idea?
Click to expand...
Click to collapse
Ah that's a firmware issue, a lot of people experience that when they revert back. You would have to clean flash MIUI again.
Issues with WiFi and SIM card. I fixed
I Already skipped Mi Account log in. I had issues with WiFi and SIM card. I fixed WiFi with EFS files but SIM doesn't work yet. It can not recognize IMEI . A contact made a EDL flash but it didn't work.
I rebuild .qcn file for RN 7 but QPST software says files doesn't match with device, even though I rebuild the .qcn and it bricked the phone.
Any idea?
Problem resolved. Just needed to use the right .qcn file.
Hello everyone this is my first post as i can't find the solution to this problem any help will be highly appreciated.
So in september 2020 i faced qualcom crashdump mode issue in my oneplus 6 i tried flashing it with msm tool many times but the issue was still there so i tried msm smt download mode and yes lost my imei number and the phone was still facing qualcom crashdump mode so i gave up and bought a new phone but this oneplus 6 was still with me and then few months ago i heard that the phone was booting up my reballing the emmc and then i asked mobile technician if they can do this so they warned me that there is a dead risk too means there was 50-50 chances of reviving the phone. I took the risk and yes my phone was revived but then i faced this issue of unknown baseband, no imei and no meid the technician was also not able to fix this so i am here i tried flashing different roms but nothing worked.
yesterday i don't know how but when i woke up in the morning i checked it and i was surprised that imei was back wifi was working but sim was not working so i restarted it and again everything was gone no imei, unknown baseband
If anyone knows how to solve this please help
Nimnim12 said:
Hello everyone this is my first post as i can't find the solution to this problem any help will be highly appreciated.
So in september 2020 i faced qualcom crashdump mode issue in my oneplus 6 i tried flashing it with msm tool many times but the issue was still there so i tried msm smt download mode and yes lost my imei number and the phone was still facing qualcom crashdump mode so i gave up and bought a new phone but this oneplus 6 was still with me and then few months ago i heard that the phone was booting up my reballing the emmc and then i asked mobile technician if they can do this so they warned me that there is a dead risk too means there was 50-50 chances of reviving the phone. I took the risk and yes my phone was revived but then i faced this issue of unknown baseband, no imei and no meid the technician was also not able to fix this so i am here i tried flashing different roms but nothing worked.
yesterday i don't know how but when i woke up in the morning i checked it and i was surprised that imei was back wifi was working but sim was not working so i restarted it and again everything was gone no imei, unknown baseband
If anyone knows how to solve this please help
Click to expand...
Click to collapse
Just use MSM tool. There are a few of them in the Guides section. Read instructions in the thread for that MSM tool, which involves installing certain drivers on your windows PC, as well as putting your phone in EDL (emergency download) mode.
optimumpro said:
Just use MSM tool. There are a few of them in the Guides section. Read instructions in the thread for that MSM tool, which involves installing certain drivers on your windows PC, as well as putting your phone in EDL (emergency download) mode.
Click to expand...
Click to collapse
Yes bro i tried using msm tool but i wasn't able to recover imei as well as baseband
Nimnim12 said:
Yes bro i tried using msm tool but i wasn't able to recover imei as well as baseband
Click to expand...
Click to collapse
i believe that you tick the SMT when flashing using MSM?
if yes, AFAIK you can try to flash using SMT again.
Did this work out? I'm in a similar position with my Oneplus 6 and can't get Wifi or IMEI back.
I have same issue brother no sim wifi baseband unknown
yes bro flashing with msm smt download fixed my problem you can give it a try
once your baseband is fixed than imei restoration is easy
I try to flash whith smt but if give error after some time start flash
Anyone fixed this issue or not?
i flashed a couple times with msm (tmobile version), but this didn't fix my issue of unable to turn on wifi. this msmdownloadtool installed tmobile android 9.0 stock rom which didn't help fixed the issue. i then tried full resets and wipe data. still didn't work. i was going to give up, then i thought just do System Update thru cell data (since no baseband means no wifi). it installed the android 10 stock rom, and fixed the issue. now i have regain baseband and wifi.
hope this help anyone with the same issue
It could be a HW problem with the network IC (very common) but trying SW solutions like flashing first is advised
Well, I have a device called "Tectoy ON 5029Y", the same as "Alcatel 3L 2020" (White Label), I'm trying to install a GSI on it, but I lose the IMEI and Baseband every time I unlock the bootloader, but if I block they come back, what am i doing wrong? I've done a lot of research on this device and there is little useful information.
I've already started GSI's, but they also have the same problem.
info:
MediaTek: MT6762
android default: 10
Treble: vndk 29, arm64-A/B
MrJohn18 said:
Well, I have a device called "Tectoy ON 5029Y", the same as "Alcatel 3L 2020" (White Label), I'm trying to install a GSI on it, but I lose the IMEI and Baseband every time I unlock the bootloader, but if I block they come back, what am i doing wrong? I've done a lot of research on this device and there is little useful information.
I've already started GSI's, but they also have the same problem.
info:
MediaTek: MT6762
android default: 10
Treble: vndk 29, arm64-A/B
Click to expand...
Click to collapse
Flash your stock firmware to restore the device to its original specs and settings.
Droidriven said:
Flash your stock firmware to restore the device to its original specs and settings.
Click to expand...
Click to collapse
it's not my goal. thanks.
MrJohn18 said:
it's not my goal. thanks.
Click to expand...
Click to collapse
It will restore your IMEI, if it relocks your bootloader, you can unlock it again. Even flashing the newest version of your firmware should restore your IMEI and probably won't lock the bootloader in the process.
Droidriven said:
Ele irá restaurar seu IMEI, se ele bloquear novamente seu bootloader, você poderá desbloqueá-lo novamente. Mesmo a atualização da versão mais recente do seu firmware deve restaurar seu IMEI e provavelmente não bloqueará o bootloader no processo.
Click to expand...
Click to collapse
I've done this procedure before, about 4 times, the baseband and IMEI are never restored, only when I lock the bootloader. Also, until today I didn't have the stock of this smartphone, I used the Alcatel MU to restore it.
edit:
before I had restored after having installed the GSI, the bootloader did not come back locked, this time it came back! Then I unlocked it again and the IMEI disappeared again.
Droidriven said:
It will restore your IMEI, if it relocks your bootloader, you can unlock it again. Even flashing the newest version of your firmware should restore your IMEI and probably won't lock the bootloader in the process.
Click to expand...
Click to collapse
I don't think that restoring / changing IMEI is done this way.
OP is recommended to use Maui Meta Tool to repair the IMEI.
MrJohn18 said:
I've done this procedure before, about 4 times, the baseband and IMEI are never restored, only when I lock the bootloader. Also, until today I didn't have the stock of this smartphone, I used the Alcatel MU to restore it.
edit:
before I had restored after having installed the GSI, the bootloader did not come back locked, this time it came back! Then I unlocked it again and the IMEI disappeared again.
Click to expand...
Click to collapse
If you don't have EFS backup the only thing I know you can do is flashing stock ROM. That is what has been sorting it out for me. I think I've managed doing it once with ROM which was based on stock but I think that is very hard to happen in practice.
dedq said:
If you don't have EFS backup the only thing I know you can do is flashing stock ROM. That is what has been sorting it out for me. I think I've managed doing it once with ROM which was based on stock but I think that is very hard to happen in practice.
Click to expand...
Click to collapse
AFAIK on MTK devices an EFS partition / directory doesn't exist, but an NV ( NVRAM ) partition / directory.
BTW: A Stock ROM - the ROM compiled by OEM especially for each of its device models - never includes a device's IMEI. If it would be so then all phones of such a device series would have the same IMEI - which would be a complete nonsense.
xXx yYy said:
I don't think that restoring / changing IMEI is done this way.
OP is recommended to use Maui Meta Tool to repair the IMEI.
Click to expand...
Click to collapse
I don't think I can fix the IMEI without a baseband.
Try to factory reset! When i lost IMEI on ZTE blade X3 its too helpful than i reset when this situation happen. and try to lock BootLoader again. and try to back to original ROM. +Turn off cell network and eject SIM card again and Turn on cell network after than you put SIM card again
-Alex
cmfCyangenModteam said:
Try to factory reset! When i lost IMEI on ZTE blade X3 its too helpful than i reset when this situation happen. and try to lock BootLoader again. and try to back to original ROM. +Turn off cell network and eject SIM card again and Turn on cell network after than you put SIM card again
-Alex
Click to expand...
Click to collapse
I've already done that, the baseband and imei always disappear, when I lock the bootloader they come back. I don't know if this has to do with "Security boot MTK" or "AVB 2.0", I rooted and installed vbmeta, still the same problem remains.
@MrJosh18 Its maybe SIM problem.
Or ROM problem totally. MTK processors too vurneable to any BootLoader actions. Its maybe problems of Android telephony System apps.
cmfCyangenModteam said:
@MrJosh18 Its maybe SIM problem.
Or ROM problem totally. MTK processors too vurneable to any BootLoader actions. Its maybe problems of Android telephony System apps.
Click to expand...
Click to collapse
well I don't know what else to do, I can root, install GSI and then I'll do a twrp port, but I really don't know how to solve these obstacles.
BTW: it's not just on my device, other people have tested it too
ROOT hmmmm
I think what solves for this problem are.
Maybe BootLoader break SIM totally. Wait
MTK Enginering Mode can help you solving this problem.
cmfCyangenModteam said:
MTK Enginering Mode can help you solving this problem.
Click to expand...
Click to collapse
Doesn't work for me, MT6762
Totally a SIM problems goodbye SIM.
MrJohn18 said:
Doesn't work for me, MT6762
Click to expand...
Click to collapse
Use this CLI tool to back up (Read option) your NVRAM, NVdata and NVCFG prior to unlock it (you can back up any existent partition you want), after that you can use this tool even to unlock it and either, for sake of curiosity or for future reference, see if it produces a different result (i.e. not erasing IMEI). https://github.com/bkerler/mtkclient
Also, you're right, you need to firstly fix the baseband null issue to can fix IMEI. What Droidriven suggested was flashing your stock ROM after to unlock bootloader, a ROM from other device even if it is from a similar or from a rebranded device won't work/make the same that the firmware for your exact model, I know, probably is not available anywhere, but this is a fact.
@SubwayChamp Good he have problems with IMEI.
SubwayChamp said:
Use this CLI tool to back up (Read option) your NVRAM, NVdata and NVCFG prior to unlock it (you can back up any existent partition you want), after that you can use this tool even to unlock it and either, for sake of curiosity or for future reference, see if it produces a different result (i.e. not erasing IMEI). https://github.com/bkerler/mtkclient
Also, you're right, you need to firstly fix the baseband null issue to can fix IMEI. What Droidriven suggested was flashing your stock ROM after to unlock bootloader, a ROM from other device even if it is from a similar or from a rebranded device won't work/make the same that the firmware for your exact model, I know, probably is not available anywhere, but this is a fact.
Click to expand...
Click to collapse
thank you very much, i still haven't solved the problem but this tool will be very useful for me,
I will test here.
SubwayChamp said:
Use this CLI tool to back up (Read option) your NVRAM, NVdata and NVCFG prior to unlock it (you can back up any existent partition you want), after that you can use this tool even to unlock it and either, for sake of curiosity or for future reference, see if it produces a different result (i.e. not erasing IMEI). https://github.com/bkerler/mtkclient
Also, you're right, you need to firstly fix the baseband null issue to can fix IMEI. What Droidriven suggested was flashing your stock ROM after to unlock bootloader, a ROM from other device even if it is from a similar or from a rebranded device won't work/make the same that the firmware for your exact model, I know, probably is not available anywhere, but this is a fact.
Click to expand...
Click to collapse
The baseband is back, but still no IMEI
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
What MSM specifically? If it is the TMo one, then you won't get OTAs from 1+, they come from TMo. 11.2.8.8 is the latest from TMo
Phoenix47 said:
And the tmo to global conversion msmtool is not good. You get sim issue after updating to global oos12.
Click to expand...
Click to collapse
What SIM issues?
Phoenix47 said:
I was on TMO oos 11.2.9.9 before and got oos12 ota update with 5gb size. But now I only get ota till 11.2.8.8 on tmobile rom after using tmobile msm 11.2.2.2 available on xda.
.
.
Regarding sim issue, the global oos12 convert my single sim LE2117 to dual sim LE2115 which cause NO SIM bug.
Click to expand...
Click to collapse
Interesting, I never got 12 when I was TMo, only 11.2.8.8. Maybe different areas get different stages? It is weird the TMo ROM is so far behind though...
Did you follow step 9 of the conversion guide?
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Ah, I am not sure then how you'd fix the issue as I have an unlocked bootloader and root.
And I have not flashed the file yet or the Magisk fix. I have to send the phone off for screen repair, so I haven't popped a SIM in it since converting.
Phoenix47 said:
When I do msm on t-mobile variant, I get oos12 ota straight from oos 11.2.2.2 but it is not actually oos12 ota. It have 500mb size and updates phone to 11.2.8.8 version on tmo but can't get any more ota updates after that.
Click to expand...
Click to collapse
I'm also facing this issue
It's been over a week and still no updates after 11.2.8.8
My device was previously on OOS12 C.19 before i bricked it and uses the MSM tool
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
Did you run into SIM card issues after updating to C.48 using this method?
I'm just wondering if i can use the TMO-GLO MSM tool to get 11.2.2 them use the local update to 11.2.10.10 then go to C.48 to hopefully retain Cell service/SIM Card, any help on the matter would be appreciated!
Phoenix47 said:
It is weird that global rom shows dual sim on oos12. I mean there is single sim global model also.
.
And that magisk fix don't work on custom roms.
Click to expand...
Click to collapse
The T-Mobile model is actually dual SIM but with a single SIM tray from my understanding, hence the software bug.
Phoenix47 said:
Step 9 is flashing modem.img from tmo rom, which also require unlocking bootloader. Actually the issue can also be fixed by a small magisk module which convert phone back to single sim on oos12. Did you flash the tmo oos11 modem.img on global oos12 ?
.
I am just saying, there is no way to fix that issue on locked bootloader after using the conversion msm.
Click to expand...
Click to collapse
Flashing modem is only required on the 9 Pro because it has an mmWave modem.
Phoenix47 said:
So you are saying that adding dual sim tray will fix the NO SIM CARDS issue ?
Click to expand...
Click to collapse
No because it doesn't work right either.
EDIT: Looks like I misspoke anyway because it's only the LE2127.
ENABLE DUAL SIM ON TMO 9 PRO ONLY!!!
Frist off I'm not Responsible for anything that happens to your phone!!! THIS HAS BEEN TESTED AND WORKING 100% ON TMO 9PRO LE2127!!ALSO MODEM RETENTION. (THIS IT NOT FOR THE UNLOCKED 9PRO LE2125) DO THIS AT YOU OWN RISK!! THIS METHOD IS...
forum.xda-developers.com
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Does anyone have the TMO 11.2.8.8 or anything around there? I've heard of 11.2.9.9. I was on EU 11.2.10.10. it was mostly ok but I was having a few communication issues*. I want to compare to a stock TMO later-11 version. I'm currently on 11.2.3.3le5acb
I tried searching the forum but it doesn't allow searching for "11.2.8.8" type strings. Or short strings.
*Wifi stopped connecting to some of my APs. Until I toggled Mac randomization, then it was fine. It's no problem in my 7TP5G.
5G would drop off to LTE, no problem... But then, LTE would drop off into no data. SMS would sometimes get stuck until reboot. Visual voicemail worked when it wanted to. None of these were consistently happening but all more than once.
Overall it wasn't too bad really but I want to try a late-11 and see how it goes.
Thanks
EtherealRemnant said:
Really, all of these methods are outdated. The best way to do it is to use Fastboot Enhance.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
After doing that, you just have to flash the Magisk fix to get back working data (because of the aforementioned dual SIM bug).
Click to expand...
Click to collapse
i can agree with him. i was one of the first people to try this method on the thread he created. works wonderfully. hence why his thread was stickied to the top of xda oneplus 9 page.
I did look through bunch of threads but cant seem to find an answer . . Is there a way to enable dual sim on the LE2115 and if someone has tried successfully (with or without any known issues) ?
If someone can point me to the right steps to follow ?
TIA
centifanto said:
2.10.10. I quickly downloaded that, and lo and behold the upda
Click to expand...
Click to collapse
bguzz said:
This worked great on my le2117 That is SIM and Bootloader unlocked. I didn’t have to flash the modem at all. Interestingly, it didn’t change model to le2115 until did the local update to c.48. Then I was able to OTA to c.63.
the only thing I see is that Netflix does not work or allow me to update…anybody know the fix and are there any other apps that I should expect that behavior?
Great info on this thread…I think I’m going to try to load Nameless soon.
Click to expand...
Click to collapse
how you did the local update? did you have to unlock your bootloader?
centifanto said:
Howdy.
So, not trying to steal anyone's thunder, but this Convert T-Mobile OnePlus 9 to Global (or other) firmware thread has not been updated by the OP (@Lomeli12) in awhile, and I ran into some hiccups when following the directions, along with a couple clarifications scattered across different threads. Credit of course to the original thread above that is still very helpful minus being out of date, @craznazn for the conversion script, @Ju5t3nC4s3 for the OEM toggling tool, and the advice of other kind XDAers responding to my questions.
The key here, that the thread above does not indicate, is that the conversion takes you back to 11.2.2, and that when you try the OEM updater or the Oxygen Updater, both just want to take you straight to Android 12 (C.48). For whatever reason, probably some preliminary prep that takes place in later Android 11 updates, the C.48 update fails exactly at 25%. I tried the conversion and update multiple times, just to make sure that wasn't a corruption issue.
After this dead end, I decided to check out the sadly not current official OTA download site to see what was available. Interestingly, their current OTA was not C.48, it was 11.2.10.10. I quickly downloaded that, and lo and behold the update succeeded! Afterwards I checked and my device model had changed to the correct LE2115 as I wanted it too (it had not changed after running the conversion script).
Then I checked the system updater, and C.48 was waiting. Installed, rebooted, and boom I was on Android 12. Then C.63 with the August 5th security update was ready. Installed seamlessly.
Helpful tips/findings/clarifications:
You will receive this final error at the end of the conversion script, but you can ignore
fastboot -w
Erasing 'userdata' OKAY [ 0.317s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Done!
Please reboot to recovery via the menus and wipe everything prior to boot
Your device model will still show TMo (2117) until you successfully apply the 11.2.10.10 update
For anyone confused by multiple threads that are seemingly contradictory, you do NOT have to be SIM unlocked to do this. You just need this nifty little tool from @Ju5t3nC4s3 that enables you to toggle the OEM unlock and subsequently get the unlock code to submit to 1+ and then unlock the bootloader with the token 1+ sends you
If you don't plan on leaving TMo, then leaving SIM locked is fine. If you do decide to change carriers, you'll need this MSM to flash back to TMo firmware to then request SIM unlock
You definitely can apply OTAs with an unlocked bootloader. Just not a rooted boot.
If you have root, you can easily pull your modem and persist imgs via Partitions Backup & Restore
If you do not have root, I received confirmation from @EtherealRemnant in this thread that the modem and persist that I pulled via the above mentioned MSM are in fact valid.
Root is easy as booting, NOT flashing, a patched boot, then using Magisk manager to patch. This enables your to easily revert back to stock boot. If you flash, your stock boot is gone
Hope this helps someone else avoid many hours of thread scanning
Click to expand...
Click to collapse
why when i try to install 11.2.10.10 my phone reset and keep saying is LE2117, it won't let me install LE2115_11.F.16. Pls help
After all procedure I'm on latest global A13 with December security patch but I have very strange issue, after airplane mode or restart my sim stop working and I have to eject and re-insert the sim for network service any solution
Hello.
So basically, I have a T-Mobile OnePlus 9 (LE2117). I went through that whole ordeal of having that global conversion script brick then phone and then bring it back to life using the India 9 Pro MSM. I tried a bunch of stuff, eventually gave up and contacted OnePlus support to get to a working T-Mobile MSM tool.
When the T-Mobile MSM they used did its thing, it went back to the T-Mobile software, however there are two issues with it:
1. The pink T-Mobile splash screen doesn't show up on boot but instead a black one that just says "android" shows up (see attached image)
2. The software updates button is grayed out and cannot be hit
The original T-Mobile MSM you can find online also works now, but it still results in this same issue.
I ended up using the global conversion MSM on OOS 11 and a custom rom for a few months each, both of which worked perfectly, but this is still an issue that is here after using the T-Mobile MSM again.
Is there any good way of fixing this issue? I do have quite a few of the important partitions backed up if those are necessary.
Thanks!
BGW#10 said:
Hello.
So basically, I have a T-Mobile OnePlus 9 (LE2117). I went through that whole ordeal of having that global conversion script brick then phone and then bring it back to life using the India 9 Pro MSM. I tried a bunch of stuff, eventually gave up and contacted OnePlus support to get to a working T-Mobile MSM tool.
When the T-Mobile MSM they used did its thing, it went back to the T-Mobile software, however there are two issues with it:
1. The pink T-Mobile splash screen doesn't show up on boot but instead a black one that just says "android" shows up (see attached image)
2. The software updates button is grayed out and cannot be hit
The original T-Mobile MSM you can find online also works now, but it still results in this same issue.
I ended up using the global conversion MSM on OOS 11 and a custom rom for a few months each, both of which worked perfectly, but this is still an issue that is here after using the T-Mobile MSM again.
Is there any good way of fixing this issue? I do have quite a few of the important partitions backed up if those are necessary.
Thanks!
Click to expand...
Click to collapse
Can u use op9 to global conversion msm with any problem
rizzmughal said:
Can u use op9 to global conversion msm with any problem
Click to expand...
Click to collapse
If you are talking about the T-Mobile to Global conversion MSM, yes.
BGW#10 said:
If you are talking about the T-Mobile to Global conversion MSM, yes.
Click to expand...
Click to collapse
Did u update to oos12 were there anyproblems u face in that
rizzmughal said:
Did u update to oos12 were there anyproblems u face in that
Click to expand...
Click to collapse
The dual sim/no service bug. I am aware of the root fix, but I was looking to get the T-Mobile software working normally again.
BGW#10 said:
The dual sim/no service bug. I am aware of the root fix, but I was looking to get the T-Mobile software working normally again.
Click to expand...
Click to collapse
What is the target id for ur device is it india or tmo
rizzmughal said:
What is the target id for ur device is it india or tmo
Click to expand...
Click to collapse
I would say that it is tmo because the T-Mobile msm tools works no problem.