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
Related
Hey there... I was trying to get my OnePlus 7 -That I just bought - to a rooted Android 10, updating was the easy part but while trying to "fastboot flash boot twrp.img" I think I somehow got myself stuck making the bootloader (aka fastboot mode ) as my main thing the phone load into and now when I turn on the phone it goes straight to fastboot mode I go and try to "fastboot flash boot twrp.img" it says OKAY twice but I can't load into recovery it takws me back to the fast boot again.... Idk what to do... Help
More into:
I got to the twrp before once during the process and idk why dumb me rebooted when I couldn't access my phone files from pc I wanted to put the image of OOS on a flash drive and via OTG but once I restarted by mistake after that whatever choice I make on the fastboot screen will quickly restart and get back to the same screen, so I can do "fastboot flash boot twrp.img" successfully but I can't load to it I hit reboot to recover or Start or Reboot Bootloader nothing takes me to twrp,
Also when I try "fastboot flash recovery twrp.img"
It says sending recovery okay, writing recovery failed, (remote: (recovery_b) no such partition)
I hope to get any help and I'm sorry if it's an obvious thing I couldn't notice, I'm not the sharpest between my brothers. Momma says. ? with me. I'll appreciate it I promise.
Have you tried this Fastboot ROMS?
Use this:
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
After that just put offical Rom zip for your region on internal memory and after that install update. voila
Unbrick tool also available for OxygenOS pie https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325 :good:
Help
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.
sourabhone said:
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.
Click to expand...
Click to collapse
"sahara server" problem : disable driver signature / update drivers
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Qualcomm dr: https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)
First of all twrp.img is a recovery image. You would normally use fastboot flash recovery twrp.img.
Secondly, you aren't supposed to flash twrp.img but use fastboot boot twrp.img and then boot to twrp and flash the twrp installer. If you can boot into fastboot, type fastboot boot twrp.img(twrp.70 for android q) and then flash twrp installer and oos. And if you can't boot into recovery you will have to use the msm tool.
daitalos said:
"sahara server" problem : disable driver signature / update drivers
Qualcomm dr:
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)
Click to expand...
Click to collapse
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging
sourabhone said:
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging
Click to expand...
Click to collapse
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english
Thanks
daitalos said:
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : h t tp s: // forum . xda-developers . com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english
Click to expand...
Click to collapse
Thank you so much daitalos.
At last i was able to recover my phone from being a paperweight.Used my other laptop and it worked perfectly first time.Maybe my 1st laptop was having some issues.
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
Dear XDA,
Please read before hitting me with the "use the search function"
I've been at it for two days now, trying to unbrick my Nebula Blue EU GM1913. It was stock on latest OOS, and I wanted to root it. I unlocked kernel, and upon flashing twrp I got stuck in fastboot mode. The phone currently can only enter EDL mode and Fastboot mode, nothing else.
What I have tried:
- 2 different laptops, plethora of cables, and every port in each laptop. I've even formatted both laptops so there's no driver clashes, and still keep getting the same errors.
- Different MSMtools: every tool I try gives me the following error 'Param Preload - Device not match image.'
- Fastboot roms via op7 pro All in one tool: I keep getting errors with those too, some files missing. Tried both EU and GLOBAL roms.
I dont know what else to do anymore.. the phone does get to fastboot, but I cannot go beyond this point. Any help is welcome!
oliverisboss said:
- Different MSMtools: every tool I try gives me the following error 'Param Preload - Device not match image.'
Click to expand...
Click to collapse
Are you running MSMtools with admin privileges?
Of course you know by now that you shouldn't flash TWRP on these phones. I can't help you with a stock recovery image since I have a different model, but you might be able to get one somewhere else. Alternately, I've had luck with Lineage recovery (albeit on that different model: https://download.lineageos.org/guacamole )
Have you tried these unbrick instructions? https://forum.xda-developers.com/t/...ide-for-a-hard-bricked-oneplus-7-pro.3934659/
When you try to flash a fastboot custom ROM, are you flashing in fastboot or fastbootd? See the ROM install instructions. Also, most of them suggest using platform tools rather than an op7 pro all in one tool.
And in reference to the "device does not match image" error: are you sure you have the latest Qualcomm drivers and that your phone is in EDL mode? It does switch to charging mode after something like 10 second of inactivity.
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
lostneedfound said:
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
Click to expand...
Click to collapse
WiFi not working because the boot.img you flash is not match your system version.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
ULTRAJC said:
WiFi not working because the boot.img you flash is not match your system version.
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot oem edl results in FAILED (remote: unknown command). tried it in minimal adb and fastboot and platformtools.
and that is the guide ive been following. however i keep getting partition issues.
lostneedfound said:
and that is the guide ive been following. however i keep getting partition issues.
Click to expand...
Click to collapse
Fastboot unbrick guide didn't work for you?
Maybe continue to try the key combination, open device manager, if you see devices name: …QDLoader 9008(driver installed) or …QHUSB_BULK(driver not install). That's EDL mode.
Some guide suggest this two command may work:
"fastboot reboot edl"
"fastboot reboot-edl"
Also can try "fastboot boot recovery that have adb.img" then use command "adb reboot edl".
okay so i none of that worked just continues to say unknown command or unknown partition. with the qual com i dont see anything otherthan android device for phone related stuff in the device manager. is there something ican do to get these partition errors to go away? last night i wasn't having any trouble with them and now they are everywhere and i really dont understand why becuase i hardly flashed anything last night. today i started flashing stuff from the guide you recommended/the one ive been using all this time and thats when the partition errors started and now im seeing them everywhere and i followed the guide down to the dime.
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
lostneedfound said:
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
Click to expand...
Click to collapse
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
nujackk said:
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
Click to expand...
Click to collapse
Exactly @nujackk ,
I have found the most likely reason for an "unknown command" message to a newer fastboot command is an old fastboot.exe version.
So today I tried out a couple of different custom OS´s for my OP8t all worked fine until I wanted to install a different OS again.
I was somehow not able to get into the lineage OS recovery, I tried flashing both 18.1-20211025 and 18.1-211028 which both flashed without issue but I still could not boot Into the recovery.
Then I tried twrp 3.5.2_11-0 but same problem here.
All my phone does is, show the startup logo for 0.5 seconds then the message about the unlocked bootloader and then it just shows the startup logo again.
What I have tried to fix the issue:
-Boot into recovery via fastboot
-Boot into recovery via key combination
-flash the stock recovery + boot image
-MSM Download Tool (the device shows up but when clicking start it shows an error message 1: open serial device failed 2: automatic detection of ddr failed)
-Followed this guide
Kinda helpless right now :/
I would be happy if anyone could help me solve this problem
PS. attached the MSM logs below
Your MSM log doesn't show a connection to your phone. Attached are a screenshot and MSM log that you would get if you get a successful connection to the MSM Tool and do nothing else.
I suggest you go back to the MSM Tool thread and make sure you've:
1. Installed the Qualcomm device driver properly
2. Followed the usage instructions properly.
BillGoss said:
Your MSM log doesn't show a connection to your phone. Attached are a screenshot and MSM log that you would get if you get a successful connection to the MSM Tool and do nothing else.
I suggest you go back to the MSM Tool thread and make sure you've:
1. Installed the Qualcomm device driver properly
2. Followed the usage instructions properly.
Click to expand...
Click to collapse
Hi thank you for your suggestion, I have solved this issue now.
I made sure, that I completely follow the guide and also downloaded the MSM on the official OP site and now it flashed on the first try.
So probably it was me who just didn´t follow the guide ;D
Thank you again for your help and have a nice day.