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
Related
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Jaszka said:
Hello there,
About year ago I've done an update to 6.0 android. Battery was charged near full and everything seemed okey. But, after update I faced a bootloop. So I tried to flash stock firmware and... failed. Many times. I'm unable to boot into recovery mode. Factory mode also isnt working. So, I tried to unlock my bootloader and flash another image, but when I try to unlock, I get a: "Check allow oem unlock in developer options". Sadly, I cant boot to check this option Is there any way to unlock oem without running android? What can I do? :crying:
Click to expand...
Click to collapse
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
MotoJunkie01 said:
You can flash the /persist partition from a device which has had OEM Unlock previously enabled in Developer Options.
Click to expand...
Click to collapse
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
acejavelin said:
How can you flash the /persist partition in a device with a locked bootloader? Doesn't this contain other information as well?
I think the real problem here is either the OP is not using the correct factory firmware image, or incorrect user procedure.
Click to expand...
Click to collapse
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
MotoJunkie01 said:
You are probably correct. Even with a locked bootloader, certain partitions can be flashed as long as downgrading is not detected. Example, if I have an xt1548 Moto G3 running on stock 5.1.1 firmware, and I have a locked bootloader, I can flash either an updated 6.0.1 stock firmware package or I can reflash the 5.1.1 firmware with the same build as the one already installed. The bootloader will, however, prevent downgrading. In flashing the /persist partition, the .img being flashed would need to be from an equal or newer build as well.
But again, your statement regarding the correct firmware procedure and/or correct firmware package is likely correct.
Click to expand...
Click to collapse
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
purplefruity said:
You can't flash anything except a bootloader. I was in this situation as MotoJunkie knows and nothing works. I did have a full backup of every partition on the phone and none flashed. Today I bricked it so badly that it doesn't even turn on anymore. My tip is to not mess with the bootloader and stuff and just use the phone normally as many things are encrypted on this phone.
Click to expand...
Click to collapse
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
MotoJunkie01 said:
Yes I recall your situation and your hard brick. I'm saying that under normal circumstances you can flash full firmware packages with a locked bootloader, as long as downgrading is not attempted.
Click to expand...
Click to collapse
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
purplefruity said:
You can't flash regular ones too. It has to be a newer firmware for the locked bootloader to let it pass
Click to expand...
Click to collapse
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
MotoJunkie01 said:
That's what I was saying. An equal or newer one. Downgrading isn't permitted.
Click to expand...
Click to collapse
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
purplefruity said:
Mine was on marshmallow and it wouldn't want to flash marshmallow stock so what I was saying is that you can't go anywhere unless stock nougat is released for this device.
Click to expand...
Click to collapse
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
MotoJunkie01 said:
You obviously developed corrupt partitions some way or another. I flash stock firmware packages with a locked bootloader on a regular basis. You should always be able to flash the same firmware build that is currently installed on your device.
Click to expand...
Click to collapse
O well I guess my device was different then. Won't turn on at all now . Gonna sell it for parts so at least I get some money back.
Will someone please help me, i cant figure out how to fix the phone. Both MSM Tools dont work, India version which is my origin, and the Global.
It says device model is wrong.
Well I did the FFastboo_SlotB.bat
from the First Sticky, OOS 1.2.4.4AA Fastboot.
it flashed everything and then it went to reboot Fastboot and I was stuck.
Now I get Device Not Matched Image on both MSM Global and MSM India
I'm in the same situation.
I was able to get my phone back into a semi-functional state, but I had to use the OP9 Pro Indian MSM tool (even though I have an OP9 5G Global) . All others failed with "Image not match device".
Now I'm trying ot figure out how to get back to the OP9 Global image.
Yeah, using the OP9 Pro MSM Tool and checking "Lite Firehouse" before flashing should bring your device back to life. Once your device is back on track, you can flash it with your MSM tool for the device.
zborn said:
Yeah, using the OP9 Pro MSM Tool and checking "Lite Firehouse" before flashing should bring your device back to life. Once your device is back on track, you can flash it with your MSM tool for the device.
Click to expand...
Click to collapse
Yeah thats what I though. I'm continuing to get the "Device not match image" error when attempting flash my device with the correct image now.
I finally got it to do something also. Im in the same position now as you are. OnePlus 9 Pro 5G.
My buddy told me to try and do DSU Loader: GSI+GSM Arm64 under Developers Settings and have the Global MSM Tool running.
Ima give it a whirl.
So after flashing OP9 Pro India, fastboot booted to twrp image and flashed latest full signed zip for my device ( OP9 Global). I booted to system and it worked but had some issues like uncertified play store. I then installed latestupdate via system updater and everything is good to go.
gorilla p said:
So after flashing OP9 Pro India, fastboot booted to twrp image and flashed latest full signed zip for my device ( OP9 Global). I booted to system and it worked but had some issues like uncertified play store. I then installed latestupdate via system updater and everything is good to go.
Click to expand...
Click to collapse
I thought your device was the same as mine LE2110?
So should I try and flash my OTA the India one
Yeah, it is. Thats the screwed up part. The only MSM tool that would work and not gove "device not match image" error was thr Oneplus 9 Pro India tool. Once in that, I could boot to twrp and flash full signed zip.
Weird.
Now I just did the same thing. Bam! Back to my DA OnePlus 9 version. Man it feels good.
I have exactly the same problem you managed to start again thanks to which msm version?
Well we did MSM India Pro...
Then use the MSM Tool that matches your phone.
ok weird at home any tool I have the same error
hello brother how are you?
i hope you will be fine
i need your help brother i also have le2110 in edl state
illusiveairforce said:
Well we did MSM India Pro...
Then use the MSM Tool that matches your phone.
Click to expand...
Click to collapse
Anyone who has installed the correct drivers and MSM tool keeps failing with "Image not match device" even though youre using the correct MSM tool for your device, try the One plus 9 Pro - India tool. From there, you can boot to twrp and flash latest full signed zip, then flash update from internal updater so correct image is on both partitions.
Background:
I unlocked the bootloader and then proceeded to flash the device from 12 to 11 using THIS tutorial. When I got to the first "fastboot reboot fastboot" the phone never rebooted. The screen is all black. I can't get into recovery or back into fastboot using the button method.
I downloaded the MSM Global tool and got all the drivers installed. I was able to start the flashing process but get "Device not match image" early in the process. I have called OnePlus customer service. They didn't ask any questions just told me to send in the phone. I would rather fix this myself if possible. Any insight and or help is much appreciated.
UPDATE: I found this information, and it had me flash the India 9 Pro version. It worked. I have a booting phone and can now work on getting it back to the US version.
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
EtherealRemnant said:
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
Click to expand...
Click to collapse
Thanks for that! The phone is back to fulling functioning with the proper version of OOS. It has been a long time since I rooted and ROMed. Fastboot used to be a straightforward method of flashing a stock ROM. Doesn't seem like it is anymore.
hillmom said:
Thanks for that! The phone is back to fulling functioning with the proper version of OOS. It has been a long time since I rooted and ROMed. Fastboot used to be a straightforward method of flashing a stock ROM. Doesn't seem like it is anymore.
Click to expand...
Click to collapse
Glad that it worked. Did you have the bootloader locked? I am just trying to confirm I'm not crazy and that I was actually able to use it with a locked bootloader lol.
Yeah fastboot flashing was the gold standard way to avoid a brick back in the days before A/B partitions and Android Verified Boot came along but not so much now. This device in particular seems to be really fussy about fastboot flashing. I never managed to brick my Pixel 3 XL doing it but I have had to MSM multiple times trying to do fastboot commands and custom recoveries to flash custom ROMs on my OP9. I have got the process down tova science at this point lol. I just went back to stock and rooted it and I'm much happier with that than I was with custom ROMs that were plagued with issues.
EtherealRemnant said:
Glad that it worked. Did you have the bootloader locked? I am just trying to confirm I'm not crazy and that I was actually able to use it with a locked bootloader lol.
Yeah fastboot flashing was the gold standard way to avoid a brick back in the days before A/B partitions and Android Verified Boot came along but not so much now. This device in particular seems to be really fussy about fastboot flashing. I never managed to brick my Pixel 3 XL doing it but I have had to MSM multiple times trying to do fastboot commands and custom recoveries to flash custom ROMs on my OP9. I have got the process down tova science at this point lol. I just went back to stock and rooted it and I'm much happier with that than I was with custom ROMs that were plagued with issues.
Click to expand...
Click to collapse
Sorry, I did it with the bootloader unlocked.
I might go back to Stock soon enough. While not as big a pain as Samsung, also not the easiest phone I've played with either.
EtherealRemnant said:
I wish people would stop following the guide for fastboot flashing. Just use the MSM while it still recognizes your device because if fastboot flashing fails, you end up having to flash it multiple times as it's not recognizing it as the correct unit anymore with that level of corruption.
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.11_OTA_0110_all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
If you download it directly to the phone or copy it over with a PC, the file may disappear. Enable USB debugging and use adb.
adb push nameof.zip /sdcard/
Click to expand...
Click to collapse
Hii! My phone is LE2115 a12 C60 can i use this file to go back to OSS11? Also do i need to unlock my bootloader or i can use this even with bootloader locked? Last one where can i find "local update tool"? Thanks a lot
eliasdeejay said:
Hii! My phone is LE2115 a12 C60 can i use this file to go back to OSS11? Also do i need to unlock my bootloader or i can use this even with bootloader locked? Last one where can i find "local update tool"? Thanks a lot
Click to expand...
Click to collapse
Yes, you can use this to go back to OOS11. You shouldn't need to unlock the bootloader as this is an officially sanctioned downgrade package.
Since you're on Android 12 you need to install the local upgrade APK:.
https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Install that, push the downgrade zip to /sdcard/, open the newly installed system update app, hit the gear, and it should show you the zip file waiting.
EtherealRemnant said:
Yes, you can use this to go back to OOS11. You shouldn't need to unlock the bootloader as this is an officially sanctioned downgrade package.
Since you're on Android 12 you need to install the local upgrade APK:.
https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
Install that, push the downgrade zip to /sdcard/, open the newly installed system update app, hit the gear, and it should show you the zip file waiting.
Click to expand...
Click to collapse
Hii! by chance do you know where I can download the previous versions of A12 update? specifically C.48. And if i can install it via local upgrade APK. Thanks!
eliasdeejay said:
Hii! by chance do you know where I can download the previous versions of A12 update? specifically C.48. And if i can install it via local upgrade APK. Thanks!
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip
There is a pinned post with them. This is C.48 for global and yes, you use the local upgrade but since you're on OOS11, you don't use the APK, use the update function in system settings and tap the gear and you'll see it.
Hi i tried to use the updater on android12 and try to downgrade it to .48 but it return error. So i need to downgrade to android 11 first and then update it again to .48?
cruzzmz said:
Hi i tried to use the updater on android12 and try to downgrade it to .48 but it return error. So i need to downgrade to android 11 first and then update it again to .48?
Click to expand...
Click to collapse
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
EtherealRemnant said:
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
Click to expand...
Click to collapse
Hii is 11.2.10.10 a lot better than 11.2.8.8? Sorry for a lot of questions im new to OnePlus
EtherealRemnant said:
Correct. Only the specific downgrade packages can downgrade. It will also wipe the device. There's no way around this. Once you are back on 11, you can do the local upgrade to flash the full C.48 ROM instead of having to do the whole OTA process (normal process is downgrade, OTA to 11.2.10.10 (it will say it's C.48 but have a file size of like 150MB but it's not), OTA to C.48 so you get to skip a step if you just use the full update package).
Click to expand...
Click to collapse
Ok if i understand correctly, i just use the updater to flash the android 11 zip file that you provided and it will do a full wipe and will restore to android 11. Then i just use the updater again to flasj it to .48
am i correct?
eliasdeejay said:
Hii is 11.2.10.10 a lot better than 11.2.8.8? Sorry for a lot of questions im new to OnePlus
Click to expand...
Click to collapse
I don't know because I didn't get my phone until February so I went right to 11.2.10.10. It is important to update though because it gets you a working OS on both slots instead of just one.
cruzzmz said:
Ok if i understand correctly, i just use the updater to flash the android 11 zip file that you provided and it will do a full wipe and will restore to android 11. Then i just use the updater again to flasj it to .48
am i correct?
Click to expand...
Click to collapse
Yes, if you want to go back to 12.
EtherealRemnant said:
Yes, if you want to go back to 12.
Click to expand...
Click to collapse
yes i want to go to 12 but not the crappy .60
cruzzmz said:
yes i want to go to 12 but not the crappy .60
Click to expand...
Click to collapse
Lol yeah. I'm not too happy with C.60 either. I really don't want to wipe my device and lose my Signal chats again.
EtherealRemnant said:
Lol yeah. I'm not too happy with C.60 either. I really don't want to wipe my device and lose my Signal chats again.
Click to expand...
Click to collapse
my sentiment exactly dunno how OP fk up with the model and the update
so i dont need MSM Tool to downgrade??
cruzzmz said:
my sentiment exactly dunno how OP fk up with the model and the update
so i dont need MSM Tool to downgrade??
Click to expand...
Click to collapse
I don't know what you aren't understanding but I'm tired of repeating myself. Read what I wrote and it answers your question.
EtherealRemnant said:
I don't know what you aren't understanding but I'm tired of repeating myself. Read what I wrote and it answers your question.
Click to expand...
Click to collapse
Ok done it ... on OOS11 now .... no need to unlock bootloader can just flash the file directly.
Will try OOS11 for a while and see if it is worth updating to OOS12
Hello,
Just got a Oneplus 9 today. Installed Jaguar to try it out. Wanted to go back to stock to compare a few things.
I grabbed the "stock" files and tried to flash using this guide: https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/
This bricked the phone.
I was able to restore the phone via MSM using the Indian one (lemonadep_22_I.07_210412), but in OxygenOS it states the Phone is a 9 Pro.
I tried flashing the STOCK file again just to see (since I now know I can recover in EDL), but it bricked the phone again.
This allowed me to confirm that for Global LE2115, the European MSM (lemonadep_22_E.05_210324) also works to restore the device!
Unfortunately again, it says the Phone is a 9 Pro.
How would I proceed if I wanted to return a LE2115 to stock and relock the bootloader?
Thanks
Found my answer in this post: https://forum.xda-developers.com/t/fixed-hard-bricked-le2115.4452435/#post-86967531
Copy pasta:
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
Click to expand...
Click to collapse
Can confirm this works!
I used the unnbrick tool from one community server and restored my one plus 9 5g 2115.to stock and locked the bootoader. But I could not get to install any rom because it always took me to crash dump. Hope it helps to get back to proper version for you
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.