Related
So i recently decided to update my Oneplus 7 Pro from the public stable release to the OxygenOS 11 Open Beta 3 on a whim. Tried to go back to the old stable release by flashing fastboot roms from Tool All In One and it somehow broke everything, even though I did it multiple times before.
Phone can't boot into anything -- even with stock roms installed. Simply shows the bootloader is unlocked screen and nothing after. I can get into recovery and edl and fastboot, but nothing else. I think I flashed an older version from TAIO's fastboot rom flasher, making it impossible (!) for my computer to interact with my phone.
MSM Tool also doesn't work. Param preload, even though I have the QC and OP drivers installed.
Anything I can do?
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
@soka said:
You could try, moving the 10 stable on to a usb drive you could plug into the phone, then fastboot boot twrp.img via fastboot . Once in, format and install A10 from usb drive, done it many times
Click to expand...
Click to collapse
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
VictimOfMagic said:
That's just it -- I can't fastboot anything. Be it roms or TWRP.
Besides, my phone doesn't really interact with my computer so no adb. Only edl (i think).
Thanks for replying
Click to expand...
Click to collapse
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
@soka said:
Sorry about that bud, sounds like your drivers are not installed properly. Maybe start there. I used the tool in one app to install the needed drivers. Worth a shot.
Try this post
Fastboot waiting for any device
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay...
forum.xda-developers.com
Click to expand...
Click to collapse
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
VictimOfMagic said:
Well, TIAO only installs google's WinUSB. I already had that installed. I just don't know why I keep getting stuck on the param preload, even with all the drivers that could be needed being installed. Maybe it has something to do with the OOS version? I have GM1915, fastboot flashed to 10.0.4 Global.
Also, I think i messed up my msm tool since now it always says connected lmao
Thanks for replying.
Click to expand...
Click to collapse
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
md5hasher said:
I had the same problem with drivers. (I tried the ones that come with the device (in an .iso image I think?) and then I tried with the patched L2 drivers.)
What worked for me: installing the ALL IN ONE tool (on windows) then runing it as administrator*, then installing the drivers from within the All In One Tool program.
Click to expand...
Click to collapse
Running TAIO as an admin? That still only downloads WinUSB.
Can you expand on what you mean?
Under windows 10 open CMD as admin and enter bcdedit /set testsigning on
now reboot. This resolved for me the driver issue and phone was then correctly seen by msm unbrick tool
I'm really new to all of this so sorry for the ignorance. I'm trying to revert my OP8T KB2003 back to OxygenOS and get rid of Lineage and TWRP. Can't seem to find a proper tutorial on how to do that. Any help would be greatly appreciated.
You can revert via MSM tool.
Rootk1t said:
You can revert via MSM
Click to expand...
Click to collapse
Thanks for the reply. So I tried the different firmware and followed the instructions, but it doesn't seem to be able to pick up the phone. I'm holding down both volume buttons for a few seconds before plugging it in. Does the bootloader being unlocked have something to do with it? If so i'm unsure how to lock it again.
rando_lando said:
Thanks for the reply. So I tried the different firmware and followed the instructions, but it doesn't seem to be able to pick up the phone. I'm holding down both volume buttons for a few seconds before plugging it in. Does the bootloader being unlocked have something to do with it? If so i'm unsure how to lock it again.
Click to expand...
Click to collapse
Does the phone show in device manager as Qualcomm HS-USB QDLoader 9008?
If yes, try entering edl mode again.
If no, you need to install the Qualcomm drivers.
Rootk1t said:
Does the phone show in device manager as Qualcomm HS-USB QDLoader 9008?
If yes, try entering edl mode again.
If no, you need to install the Qualcomm drivers.
Click to expand...
Click to collapse
It shows up as QUSB_BULK How would I go about installing the drivers?
I also wasnt able to start the MSM Tool with pushing Buttons. If drivers are correct you should Google Boot edl Mode via ADB command. This worked for me.
There is a good thread in the "guide" section that could make it alot easier for you.
[ROM][STOCK][FASTBOOT] Stock OxygenOS Fastboot ROMs For OnePlus 8T
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you 😉. I have extracted all images from the stock zip...
forum.xda-developers.com
I'm also trying to get back to oos from derp. Can't I just use the flashable beta zips using twrp and then format data?
So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all
DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp
d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.
FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD
FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.
So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?
Fuwlz said:
So, I flashed LineageOS recovery and installed LineageOS.
This was very buggy for me so I want to go back to stock OxygenOS (11).
I cannot for the love of everything that is holy figure out how to do this.
I downloaded OOS ROMs but I cannot sideload them on the Lineage Recovery.
Also I tried MSM Tools, but this staight up just won't start.
Anyone has a tutorial for me or can tell me what I'm doing wrong?
Click to expand...
Click to collapse
Hello, did you follow the instructions here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3954325/
?
Yes, MSM tools just doesn't work
Me too, I can't start this EDL mode, it just goes straight to fastboot.
I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.
WookieTookie said:
I did it! I finally was able to use the EDL mode and MSM tool by using an old laptop that had USB2 ports! The laptop I was using had only USB3. After I've installed the Qualcomm drivers on the second laptop, EDL mode started as explained in the guide and MSM found it immediately.
Hope this helps.
Click to expand...
Click to collapse
Hi,
Just experiencing the same. I would like some help pls !
Tried LineageOS. Not stable enough on OP7 so I want to go back to OOS.
Got OnePlus 7 - 1903 model EU, so I believe it's GM57BA that I have to deal with.
Tried fastboot methods, not successful. I followed this post. Tested this on linux.
Encountered "Flashing is not allowed for Critical Partitions" even though I got :
Code:
❯ fastboot flashing unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
❯ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Device was stuck during boot (left it about an hour to try, nothing happened).
At some point I faced Qualcomm Crashdump Mode Screen.
Now I think the only option is to go for MSM method but not available for linux, so I switched on windows.
Instructions on this post seem pretty clear but when I plug the phone on PC, device is not recognized, don't know why I can't install phone driver properly (but probably not important at this stage).
Qualcom drivers are installed but I can't get my phone to boot on "EDL mode" ?
vol - and vol + while shutting down/powering on the device, plugged/unplugged to PC (tried few combos).
So device is not recognized and I can't run MSM Enum.
I have probably missed something... if anyone could give a hint on how to do that, I would greatly appreciate it.
Ok so I finally found a way to solve my issue.
Followed instructions from this video.
Basically I had to disable driver signature enforcement on my pc. This allowed me to properly boot on EDL and detect the device using MSM.
Hope this will help
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.