I upgraded my OnePlus 9 LE2115 from OOS 11 to OOS 12, and every time the phone reboots after completing the update, the touch screen is completely unresponsive, so it stays stuck at the lock screen forever.
I upgraded from OOS 11.2.10.10 to OOS 12-C36. I understand that I need to get to C36 before upgrading to C40.
Here are the steps I tried:
1. Downloaded C36 full upgrade zip and placed on root of internal storage.
2. Started local upgrade with this file.
3. System rebooted and touch screen won't work at all.
I also tried it through Fastboot:
1. Downloaded C36 full upgrade zip and extracted all images from payload.bin.
2. Followed all fastboot command steps from this post.
3. Rebooted to system and touch screen still won't work.
Only option I have is to downgrade to OOS 11 with the downgrade zip.
Anyone have any suggestions?
Sometimes a downgrade is an upgrade... better get while the getting's good.
I was having the same issue until I MSM'd back to stock 11.2.2.4 and relocked the bootloader. Then I upgraded through the system update menu normally. I just unlocked the bootloader once I was fully upgraded to Android 12. Hopefully it'll be there same for you
jshinn1 said:
I was having the same issue until I MSM'd back to stock 11.2.2.4 and relocked the bootloader. Then I upgraded through the system update menu normally. I just unlocked the bootloader once I was fully upgraded to Android 12. Hopefully it'll be there same for you
Click to expand...
Click to collapse
Thanks for responding.
Which MSM tool did you use?
TikiThePug said:
Thanks for responding.
Which MSM tool did you use?
Click to expand...
Click to collapse
I initially used the 9 Pro Indian MSM tool,, but Ive been using the Global MSM with no issues recently, I was finally able to get the Global MSM working consistently by disable the "Auto-reboot" and "SHA-256 check" options and also selecting "O2" as the "Target"
Try this Msm tool
Global/US unbricking guide.
Global/US OnePlus 9 Unbricking Guide Tested and used on a LE2115 variant device. YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST...
forum.xda-developers.com
jshinn1 said:
I initially used the 9 Pro Indian MSM tool,, but Ive been using the Global MSM with no issues recently, I was finally able to get the Global MSM working consistently by disable the "Auto-reboot" and "SHA-256 check" options and also selecting "O2" as the "Target"
Click to expand...
Click to collapse
badreddine uday said:
Try this Msm tool
Global/US unbricking guide.
Global/US OnePlus 9 Unbricking Guide Tested and used on a LE2115 variant device. YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I am trying this but keep getting Saraha Communication failed. I have tried multiple cables and ports and still the same issue.. it always seems the Global MSM tool does this for me, but the OP9 Pro Indian tool does not. I can restore it to the Indian variant, but I do not know how to update to the correct OOS 12 version for Global variant after that, without unlocking the bootloader.
TikiThePug said:
Thanks, I am trying this but keep getting Saraha Communication failed. I have tried multiple cables and ports and still the same issue.. it always seems the Global MSM tool does this for me, but the OP9 Pro Indian tool does not. I can restore it to the Indian variant, but I do not know how to update to the correct OOS 12 version for Global variant after that, without unlocking the bootloader.
Click to expand...
Click to collapse
Well i tried both of 9 and pro i got succed . About 9 proi i had to intall magisk root for oxygen updater apk i gave it the permissions then i choose the full global os 12 then wipe the data and have a fun. About sahara failed tru to uninstal drivers then reboot pc and instal it again i mean qualcom snapdragon usb drivers. I think you should desactive the antivirus protection and choose os on msm tool . Dont give up dude .
TikiThePug said:
Thanks, I am trying this but keep getting Saraha Communication failed. I have tried multiple cables and ports and still the same issue.. it always seems the Global MSM tool does this for me, but the OP9 Pro Indian tool does not. I can restore it to the Indian variant, but I do not know how to update to the correct OOS 12 version for Global variant after that, without unlocking the bootloader.
Click to expand...
Click to collapse
Read this it may help you a lot
How to Unbrick OnePlus 9/9 Pro/9R using MSM Download Tool
In this guide, we will show you the steps to unbrick the OnePlus 9/9 Pro/9R devices using MSM Download Tool.
www.droidwin.com
OK, I can get rid of the communication failed message by holding power+volume up for a few seconds, but now when I disable the "Auto-reboot" and "SHA-256 check" options and also select "O2" as the "Target", I see "Start Download Firehose Binary" for 18 seconds, then I get the Sahara Communication failed again. I tried doing the same steps but selecting "Use Lite Firehose" only, and I get stuck at "Param preload" with "Device not match image".
TikiThePug said:
OK, I can get rid of the communication failed message by holding power+volume up for a few seconds, but now when I disable the "Auto-reboot" and "SHA-256 check" options and also select "O2" as the "Target", I see "Start Download Firehose Binary" for 18 seconds, then I get the Sahara Communication failed again. I tried doing the same steps but selecting "Use Lite Firehose" only, and I get stuck at "Param preload" with "Device not match image".
Click to expand...
Click to collapse
Here follow this guide which showed me how to get back to Global firmware after flashing the Indian MSM tool: https://www.droidwin.com/msm-tool-unable-to-recognize-oneplus-9-sahara-connection-error/
CHeck under the FAQ section titled "FAQ: Switch From OnePlus 9 Pro to OnePlus 9 Firmware". That should at least get you back to stock firmware for your region and then you can update from there before unclocking the bootloader
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also move all other OPS files out of this folder.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
TikiThePug said:
OK, I can get rid of the communication failed message by holding power+volume up for a few seconds, but now when I disable the "Auto-reboot" and "SHA-256 check" options and also select "O2" as the "Target", I see "Start Download Firehose Binary" for 18 seconds, then I get the Sahara Communication failed again. I tried doing the same steps but selecting "Use Lite Firehose" only, and I get stuck at "Param preload" with "Device not match image".
Click to expand...
Click to collapse
I had same issues well try the 9 pro msm with previous steps
TikiThePug said:
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also remove all other OPS files.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
Click to expand...
Click to collapse
I told you . Happy for you dude good work. It needs little patience
TikiThePug said:
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also remove all other OPS files.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
Click to expand...
Click to collapse
Awesome! Happy you got it working I think we've all been at this point with this phone. I like it but this might be my last OnePlus phone
jshinn1 said:
Awesome! Happy you got it working I think we've all been at this point with this phone. I like it but this might be my last OnePlus phone
Click to expand...
Click to collapse
Hi, i have a same problem with my LE2110, but it's possible you share your package modified with a good .xml please ?
coolporteur84 said:
Hi, i have a same problem with my LE2110, but it's possible you share your package modified with a good .xml please ?
Click to expand...
Click to collapse
Sorry it was @TikiThePug that posted about that I never used that method on my device
jshinn1 said:
Sorry it was @TikiThePug that posted about that I never used that method on my device
Click to expand...
Click to collapse
OK i'm sorry, I thought you also used this method.
TikiThePug said:
Thanks guys, I got it all working now.
Here's what I had to do:
1. Get both OP9 Global and OP9 Pro India MSM packages.
2. Decrypt both OPS files using this tool: https://github.com/bkerler/oppo_decrypt
3. Open settings.xml in OP9 Pro India extract folder, and copy header and footer from there to the settings.xml file of the OP9 Global extract folderm. Steps described here: https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/page-2#post-86155365
4. Repack the firmware to a new OPS file and copy this to the MSM main folder. Also move all other OPS files out of this folder.
5. Launch MSM tool and put phone in EDL mode -> flash by choosing Auto Reboot and Firehose Lite opens checked.
6. Phone rebooted to OOS 11 Global. Updated to OOS 12 C36 through System Update.
7. Reboot system to OOS 12 with touchscreen ACTUALLY WORKING. Updated to C40 through System Update.
8. Reboot system to C40 with everything still working.
9. Reboot to fastboot and unlocked bootloader. Rebooted and finished.
Click to expand...
Click to collapse
Hi, Could you share the finished package with the modified .XML ?
coolporteur84 said:
Hi, Could you share the finished package with the modified .XML ?
Click to expand...
Click to collapse
You can get it from here: https://easyupload.io/8aafk2
Link will expire in 6 days.
TikiThePug said:
You can get it from here: https://easyupload.io/8aafk2
Link will expire in 6 days.
Click to expand...
Click to collapse
Thank you very much !!! I'm trying this evening.
Related
hi Guys
I'm in the forum for a very long time as an assistant helper now it has got me hard I have an Axon 10 Pro with curly boot loader and trying to flash a TWRP I have somehow the device or SotA and SlotB have shrunk. The Axon Bootet permanently in 0.5 second cycle and also a FULL Restot or FULL Flash with EDL Tool has not changed anything. Likewise, a new flash about fastboot with the command (fastboot flash boot_a boot.img) the same for boot_b then try with fastboot command (fastboot boot twrp.img) Recovery to start without success fastboot erase boot_a and boot_b has also flashing new but it does not start. Always bootloop:crying::crying::crying::crying:
the Axon 10 pro is back because he had no backup of all we had from my Axon 10 pro made a backup with the edl tool (Backup all) and have then copied his efs backup purely and then this with then on the Axon 10 flashed the Axon 10 pro is now back
Where did you get the twrp from?
From udev
On his donload page
https://forum.xda-developers.com/showpost.php?p=80156866&postcount=3
I had a bootloop issue as well and even though I reflashed using the EDL tool, it doesn't erase and the errors remained, but when I entered EDL mode and reflashed using the Xiaomi Flash Tool, storage was completely erased and the device was flashed cleanly and booted correctly.
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
jbeaulieu said:
I've encountered a similar issue with my Axon (2020U version). I can boot into EDL but nothing else (no fastboot, recovery, etc.). I previously had TWRP up and running successfully, not sure what happened.
Is there a full EDL zip or similar that I can flash to return everything to stock? I tried restoring with the EDL tool but with no success
Click to expand...
Click to collapse
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
jim262 said:
The reason the EDL tool may not work is that is doesn't have the capability to erase. The boot loop that occurs is usually due a corrupt bootfile. Use the MiFlash fastboot recovery tool. Make sure to select the clean all button at the bottom. Place your phone in EDL mode. Hit refresh to make sure your phone is detected. Select the EDL file and then hit flash.
Click to expand...
Click to collapse
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
jbeaulieu said:
Apologies for my ignorance - what exactly am I flashing? I see the "clean all" radio button, but I'm not sure what EDL package to flash after selecting that option - is there a 2020U package floating around that I'm not seeing?
Click to expand...
Click to collapse
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
jim262 said:
The EDL package, use the same EDL package that you used with the EDL tool. Just select the "clean all" radio button. Select the path to the EDL , hit refresh once phone, in EDL mode, is detected, hit flash.
Click to expand...
Click to collapse
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
jbeaulieu said:
Okay, I'm trying to use MiFlash to restore the backup I took through the original EDL tool. The MiFLash tool is only timing out with a "cannot receive hello packet" - was this something you encountered as well?
Click to expand...
Click to collapse
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Ah, okay. I have the US version - A2020U. Unless I'm mistaken, it looks like there isn't a full EDL zip file available for my version yet, so I might be stuck
There were EDL files up, but apparently they were taken down for some reason.
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Chris axon 7 said:
in the russians there are the 1.6 of the g model as edl (which one can use in a brick) but I do not know if this is synonymous with the u model as you would have to ask @Unjustified Dev or something
@MOD
I hope that the links are allowed here else delete please
1.6 g model edl
http://4pda.ru/forum/index.php?showtopic=965431&st=0#entry88768840
And the lonk too the forum
http://4pda.ru/forum/index.php?showtopic=965431
Click to expand...
Click to collapse
Thanks for sharing these. @Unjustified Dev do you happen to know if the 1.6 2020G EDL would be able to be flashed to a 2020U model to recover from a brick? Or if not, is there a place to obtain the proper files, either here on the forums or via PM?
jim262 said:
I did attempt to flash the wrong EDL file (They are region and device specific) and received that error. I have the Chinese version and once I downloaded the correct EDL file, I had no issues I have even maintained an unlocked boot loader, flashed Magisk and taken OTAs.
Click to expand...
Click to collapse
Please share us the EDL file for the Chinese version.
has anyone found the US EDL file yet?
Futility's Forgotten Soldier said:
has anyone found the US EDL file yet?
Click to expand...
Click to collapse
Still waiting. I'm stuck on the EU version.
Hi every one Im new here and was hoping for some help.
Ive been reading the forum quite a lot and only got so far and now need a bit off help please
so ive used the Axon 10 EDL Tool to unlock my bootloader
after getting the modified one for the chinese partiton table
as i have the Chinese Axon A2020
and now i want to put on the european rom but need a guide please as i have not read anything on here succeeding in this with every thing working
also tried to but on TWRP recovery but just get written protection error with fastboot
ps im new to this
please help
sorted thanks To Jim262 and T1nt3
jim262 said:
Have you converted yours successfully? I recently did mine after trial and error, but it is now running 1.8.
Here are the steps I used.
1) I rebooted to TWRP and wiped everything and refortmatted data.
2) I then rebooted the phone to EDL from within TWRP.
3) I then started the MiFlash tool by Xiaomi, which I had downloaded to my PC.
4) I made sure the CLEAN button was selected in the lower right side.
5) I then made sure my phone was detected by selecting REFRESH.
6) I then chose the path to the 1.6 EDL file from Dimitri and selected flash.
7) After the flash was successful the phone rebooted. It took a long time for the initial bootup.
8) Once setup was complete, I rebooted to EDL and used the EDL_tool to unlock the bootloader.
9) Once unlocked, I rebooted to fastboot and booted TWRP. I then flashed Magisk.
If you want, there is a link to 1.8 that was posted by Dimitri, which you can then place on your SD card and upgrade from there. If you do upgrade to 1.8, you will need to do steps 8 and 9 again.
Jim262
Click to expand...
Click to collapse
T1nt3
Sure,
You need EDL Chinese Tool, 1.6 EDL EU firmware and miflash
1. Using EDL Tool make a full EDL Backup
2. Flash EDL firmware, after that you phone will be bricked
3. Using EDT Tool unlock bootloader after this there will be a menu, select power off
4. Put the phone in EDL mode and using miflash flash the backup you made earlier
5. After restart select wipe
6. You're done
I think miflash restores just some of the files, because it takes just five minutes to do the flash
Everything is working, even updates, mine is now in 1.8 after OTA update
If you now wanna unlock the bootloader use EDT Tool no chinese.
I am looking for an "all backup of an Axon 10 4G "
China Model.
Of course without your EFS data.
I want to make a China device out of my EU device
ONEPLUS 9 china unbrick what i must to do to bypass model id and flash device
What are you stuck on, give me exact details. I have same device and have done it every which way. PM if needed. Plus there are other threads with exactly what you need.
illusiveairforce said:
What are you stuck on, give me exact details. I have same device and have done it every which way. PM if needed. Plus there are other threads with exactly what you need.
Click to expand...
Click to collapse
i got china version i flash this :
How To Guide [FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AAnow device edl mode only
mhammadleo said:
i got china version i flash this :
How To Guide [FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AAnow device edl mode only
Click to expand...
Click to collapse
Hello I think this should help you. You just have to make sure that your device is recognized by the adb and fastboot tools with the command "fastboot devices" and then run the file "flash-all_slotb.bat" as administrator.
I want to clarify that this is a supposed compilation for the oneplus 9 to which I replaced the files that it flashes with those of the official rom of the normal oneplus 9 that is on the official page of oneplus.
Fastboot OOS_11.2.7.7.LE25BA.rar
drive.google.com
Same .. Can someone please provide us with the chinese MSMTool
Extract Files - TeraBox
Please enter the password to extract your files.
www.terabox.com
Password: cn1d
MSM Tool for OnePlus 9 2110 Chinese variant.
Hi, my phone is currently bricked and in a bootloop. My MSM tools have no problems recognizing op9, but all of them give me a "device not match image" error, I'm using Lite Firehose option, because I can't stop my phone from constantly rebooting...
forum.xda-developers.com
Good day!
Is there any way to get the official OnePlus 9 T-Mobile (LE2117) OxygenOS zip file? Android version does not matter (11 or 12).
I want to install it by:
adb sideload <file>.zip
Click to expand...
Click to collapse
I found official OOS from the OnePlus website, but it has only global version. (BTW I was able to sideload it and it works)
PS: I found the MSM Download Tool for it, but I'm having trouble with installing it, as it is stuck on "Waiting for device". Although I installed Qualcomm HS-USB QDLoader 900 driver.
Thank you!
You'll need this driver for MSM to work.
Also you need to boot to EDL: Power off, Hold down both vol up and down, connect device to USB. Then click enum in MSM and the device will show up.
FYI it'll only work with USB 2.0, anything else will fail on donwloading super.img.
c0d3f0rc37 said:
Good day!
Is there any way to get the official OnePlus 9 T-Mobile (LE2117) OxygenOS zip file? Android version does not matter (11 or 12).
I want to install it by:
I found official OOS from the OnePlus website, but it has only global version. (BTW I was able to sideload it and it works)
PS: I found the MSM Download Tool for it, but I'm having trouble with installing it, as it is stuck on "Waiting for device". Although I installed Qualcomm HS-USB QDLoader 900 driver.
Thank you!
Click to expand...
Click to collapse
How did u sideload global rom
rizzmughal said:
How did u sideload global rom
Click to expand...
Click to collapse
I wanted to install StagOS as shown here. After booting into recovery mode I found out that I can easily sideload zip file. So, instead of StagOS file I used OxygenOS one.
Note: my phone's bootloader is unlocked.
_MartyMan_ said:
You'll need this driver for MSM to work.
Also you need to boot to EDL: Power off, Hold down both vol up and down, connect device to USB. Then click enum in MSM and the device will show up.
FYI it'll only work with USB 2.0, anything else will fail on donwloading super.img.
Click to expand...
Click to collapse
I was hoping to find the official zip file and install it the easy way. But, I think the MSM is the only way for now. So, will try your guidance. Thank you!
Thread 'Tmobile 11.2.8.8 msm' https://forum.xda-developers.com/t/tmobile-11-2-8-8-msm.4504361/
Ayúdame
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
Follow this, use the first link to download the tmo MSM India mod msm tools, when done, unlock the bootloader, then boot into fastbootd mode "not talking about regular fastboot/bootloader mode" and then download fastboot enhanced and extract it
then go here https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
Then click on Signed flashable zips > LE25AA Global > 11.2.2.2 then download it, extract the payload.bin, move the payload.bin to the same directory as the fastboot enhanced folder would be "not required but just for easier access to the payload.bin file", when it's done flashing, reboot to recovery, wipe data, then reboot to system, then do an OTA update to Android 13
If you have any problems please reply back