Database Info

I really need urgent help!!!

i made a huge mistake guys i was trying to flash twrp recovery and then it didn't work and the phone bricked so i tried to download all in one tool and then by mistake i locked the bootloader and then i downloaded the msm tool and its not working my windows is in test mode and every time it says sahara communication failed :crying: :crying:

AssyrianHero said:
i made a huge mistake guys i was trying to flash twrp recovery and then it didn't work and the phone bricked so i tried to download all in one tool and then by mistake i locked the bootloader and then i downloaded the msm tool and its not working my windows is in test mode and every time it says sahara communication failed :crying: :crying:
Click to expand...
Click to collapse
"sahara error" is a known problem in various tools (qfil,qpst,msm etc) and is related to device-pc connection almost always
_disable driver signature (ignore it if you already have..)
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
_Install the latest “net Framework” for your Windows.
_try to Install correct "Qualcomm HS-USB QDLoader 9008" last version drivers, according to your Windows type (x64 or x86)- (update manually, from windows device manager)
_press vol (+) vol (-) and connect the phone to the pc
_try another port usb (as a last solution)
Read here : https://forum.xda-developers.com/showpost.php?p=80052763&postcount=2
and here : https://forum.xda-developers.com/showpost.php?p=80021106&postcount=21
(use google search for more Info about "sahara error")

daitalos said:
"sahara error" is a known problem in various tools (qfil,qpst,msm etc) and is related to device-pc connection almost always
_disable driver signature (ignore it if you already have..)
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
_Install the latest “net Framework” for your Windows.
_try to Install correct "Qualcomm HS-USB QDLoader 9008" last version drivers, according to your Windows type (x64 or x86)- (update manually, from windows device manager)
_press vol (+) vol (-) and connect the phone to the pc
_try another port usb (as a last solution)
Read here : https://forum.xda-developers.com/showpost.php?p=80052763&postcount=2
and here : https://forum.xda-developers.com/showpost.php?p=80021106&postcount=21
(use google search for more Info about "sahara error")
Click to expand...
Click to collapse
I tried everything i used different computer and it's still saying connected and N/A and then sahara error???? Why please help, maybe because i locked the bootloader and the phone is bricked ?

AssyrianHero said:
I tried everything i used different computer and it's still saying connected and N/A and then sahara error???? Why please help, maybe because i locked the bootloader and the phone is bricked ?
Click to expand...
Click to collapse
First of all you don't need to panic... Panic is the worst advisor and it doesn't solve no one problem
Of course if you had an unlocked Bootloader the device could be restored in various ways,that are now excluded
Your device is "T-Mobile" or is it locked maybe to a provider? What device you have? For example is GM-1900,GM1910,GM1911 etc? The device only enters in Fastboot mode?
What version windows10 you have ? (home,pro,Pro N etc)...

daitalos said:
First of all you don't need to panic... Panic is the worst advisor and it doesn't solve no one problem
Of course if you had an unlocked Bootloader the device could be restored in various ways,that are now excluded
Your device is "T-Mobile" or is it locked maybe to a provider? What device you have? For example is GM-1900,GM1910,GM1911 etc? The device only enters in Fastboot mode?
What version windows10 you have ? (home,pro,Pro N etc)...
Click to expand...
Click to collapse
Gm1900 Windows 10 pro and the device entering only in fastboot mode .

daitalos said:
First of all you don't need to panic... Panic is the worst advisor and it doesn't solve no one problem
Of course if you had an unlocked Bootloader the device could be restored in various ways,that are now excluded
Your device is "T-Mobile" or is it locked maybe to a provider? What device you have? For example is GM-1900,GM1910,GM1911 etc? The device only enters in Fastboot mode?
What version windows10 you have ? (home,pro,Pro N etc)...
Click to expand...
Click to collapse
Its not American its Chinese version it was bought from Amazon and its unlocked it's not locked to any carrier.

daitalos said:
first of all you don't need to panic... Panic is the worst advisor and it doesn't solve no one problem
of course if you had an unlocked bootloader the device could be restored in various ways,that are now excluded
your device is "t-mobile" or is it locked maybe to a provider? What device you have? For example is gm-1900,gm1910,gm1911 etc? The device only enters in fastboot mode?
What version windows10 you have ? (home,pro,pro n etc)...
Click to expand...
Click to collapse
**update** i fixed the phone with msm tool but the problem is, The apps are chinese now i need to download gm-1900 stock recovery which is gm57aa

AssyrianHero said:
Its not American its Chinese version it was bought from Amazon and its unlocked it's not locked to any carrier.
Click to expand...
Click to collapse
I know you have a locked bootloader & this make the situation more difficult but you must to try..."Sahara error" is communication problem between device-pc...
_From the beginning_
First,uninstall any Qualcomm driver from pc > Reboot your pc!
*disable driver signature (you said you did that-Ignore it)
enabled "developer mode" on pc - close any antivirus temporarily
*[download minimal adb & fastboot on pc : https://forum.xda-developers.com/showthread.php?t=2317790
Read here how to add adb and fastboot to the windows PATH : https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/ ]
If you press "windows button" + R > type > msconfig > advanced options, make sure "debug port" says "USB"
Download & Install these Qualcomm HS-USB QD Loader 9008 (x64) drivers: https://mega.nz/#!ouYngKTQ!tt-qm_574qopWljVdOQACKHWvwm8aNbbmv1dCVJ3epI
Go to device manager on pc > View + Show hidden devices + Ports (com & LPT)...If you see "Qualcomm hs-USB qdloader 9008 (com3 for example) on windows device manager,follow this Quide from the third step & after ...Now,press vol (+) vol (-) and connect the phone to the pc(if this step succeeds,the MSM Tool will work)
*_After the update drivers manually step,if there is a persistent problem with edl mode,as a last solution go and Install this file "fastboot_edl" : https://mega.nz/#!piRDTKyY!veODfIu3YSxBUYwfZy7eDzNr1BFDPy4aemmb_LDfEPs (extract it and run it, even with locked bootloader)
Follow these steps in this Quide : https://forum.xda-developers.com/showpost.php?p=80021106&postcount=21
For Qualcomm drivers : https://www.androidjungles.com/qualcomm-hs-usb-qdloader-9008-driver/
MSM Tool : https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
FAQ msm tool: https://forum.xda-developers.com/showpost.php?p=80011568&postcount=2
[This is Unbrick tool for OnePlus 7 - Hydrogen Version : https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
and this you can use,and after you can easily go to OOS with official Updater app....Thread Repo of OOS Builds OP7 : https://forum.xda-developers.com/oneplus-7/how-to/oneplus-7-repo-oxygen-os-builds-t3937152
sorry for english & GL
---------- Post added at 04:15 ---------- Previous post was at 04:10 ----------
[/COLOR]
AssyrianHero said:
**update** i fixed the phone with msm tool but the problem is, The apps are chinese now i need to download gm-1900 stock recovery which is gm57aa
Click to expand...
Click to collapse
Great news
Just,read my last post for "Thread Repos of OOS Builds OP7" : https://forum.xda-developers.com/oneplus-7/how-to/oneplus-7-repo-oxygen-os-builds-t3937152
you can do it with various ways...
* _You can ask any question in this Thread: https://forum.xda-developers.com/oneplus-7/help/help-thread-question-noob-friendly-t3954564

msm tool unroot- stuck on waiting for device

I am trying to use the msm tool to unroot my OnePlus 8t tmobile variant. Using the MSM tool I have run into a few different problems.
1. Drivers. When my phone is in edl mode plugged in to my computer, device manager recognizes it as usb_bulk. I tried using the provided .cab file to update windows Qualcomm drivers but windows could not ever find the files when updating. I found on another forum a automatic installer.
2. Although it now says Qualcomm 9008 windows says that driver digital signature is not recognized or corrupted. However the MSM tool does finally show COM 5 and when I plug in my device is stuck at waiting for device.
I'm pretty stuck right now and any information to help me out would be appreciated.

You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com

Rootk1t said:
You need to disable driver signature verification in windows to successfully install drivers.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue

mreese14 said:
thank you I tried this and it still didnt work eventually i went into the registry and deleted lowerfilter, and now the drivers work however,
I am faced with another issue. The MSM tool says ddr not automatically detected and wont continue so we are now trying solve this issue
Click to expand...
Click to collapse
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.

gforceriders said:
I have encountered this error and what I found was that there are some people, me being one where you need to disable your network and change your PC date to December 2018 and then open msm and proceed.
Click to expand...
Click to collapse
Worked for me, thank you!

Bricked My phone, cant get into FastbootD to fix it

So i recently wanted to root my OOS 12 oneplus nord, and i bricked it..
i cant get into fastbootD, Recovery, or anything at all except fastboot, the device is detected as Android bootloader interface in device manager, i have tried using: msm tool, flashing normal rom (error: partition not found and Flashing is not allowed for critical partition)

As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Azeld said:
As a last resort, this worked for me : [OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Click to expand...
Click to collapse
As I said, msm didn’t work for me

Hafted said:
As I said, msm didn’t work for me
Click to expand...
Click to collapse
may be need to reinstall drivers? should be displayed differently in the device manager than Android bootloader interface.

gorro8 said:
may be need to reinstall drivers?
Click to expand...
Click to collapse
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there

Hafted said:
Nope, I can’t get it into edl mode, I did manage once but I got the you need to restart error and I couldn’t get it back there
Click to expand...
Click to collapse
what do you do to enter the edl mode?
what cable are you using?

gorro8 said:
what do you do to enter the edl mode?
what cable are you using?
Click to expand...
Click to collapse
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys

I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com

download the correct drivers and replace them in the device manager

gorro8 said:
I found a problem similar to yours. they say it's the wrong driver
[Bricked] OP8 : FASTBOOT rom : 'Flashing is not allowed for Critical Partitions
I messed up trying to install TWRP on c.17 OOS12 Now the mobile is bricked. 1. I tried the MSM tool, it shows the COM PORT but doesnt do anything. Just stuck at waiting for device. 2. I tried the ALL IN ON TOOL, but getting "UNHANDLED...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I’ll try that and give you an update, Ty!

worth trying another USB port too, even if they are supposed to be the exact same. Same thing happened with my laptop, tried another (presumably identical) USB port and it works first time, every time

Hafted said:
Using official one plus cable, I hold bot volume keys for about 40 seconds, then connect the cable and only then I let my hands go off the keys
Click to expand...
Click to collapse
1st, u really should find the exact drivers. But also very important to remember booting your PC into Test Mode with Driver Signature Enforcement OFF - BEFORE installing the EDL 9008 Drivers for your device.
Besides, after you press and hold both Vol buttons, u should plug the device in IMMEDIATELY, not waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.

Hey, so after some time (I got a new phone by now) I managed to fix it, turns out that i had to instantly put in the cable, just like how LinhBT Said
LinhBT said:
waiting for 40 seconds, since each time the device boots into EDL mode, if there's no connection is established in 5 seconds , the device will automatically out of EDL mode.
Click to expand...
Click to collapse

Here is something that might work for unbricking and/or getting in to EDL-mode:
Unable to reinstall Oxygen OS from custom ROM. FAILED (remote: Flashing is not allowed for Critical Partitions ). Need assistance, details below.
Hello, friends. So I am here following this exact tutorial : https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ I currently am stuck there @pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$...
forum.xda-developers.com

OnePlus 8T Kona stuck in fastboot

Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.

Arunraj90 said:
Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.
Click to expand...
Click to collapse
Does it connects to a PC?
If it does type fastboot reboot edl

It connects to PC thats why its returning this error na, and in port it shows qualcom 9008. All drivers were installed corretly . If kona oneplus8T fastboot vailable can someone share.

Arunraj90 said:
Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.
Click to expand...
Click to collapse
The OnePlus 8T code name is kebab, but you won't find that name on the phone itself. But it's used in LineageOS and in custom rom/recovery builds.
The SoC of the 8T is called kona and you'll see this on the bootloader screen and in some system properties like ro.product.board.
The 8T has a Snapdragon 865 5G chipset.
Earlier versions of the 8T used DDR4 storage, newer ones use DDR5.
I've found that l often have to reinstall drivers for the 8T on my PC when things go wrong. So if your PC isn't properly recognising your phone, it may be helpful to reinstall the appropriate driver.
And one more point: don't post the same question in multiple places. See rule "5. Create a thread topic or post a message only once" in https://forum.xda-developers.com/t/xda-developers-forum-rules.4200559/

Device name in ports shows correctly. Msmdownloader also detecting after preprocessing returns with "Device not match image". Tried EU IN O2 roms, but same error occurs. o if anyone knows the exact problem kindly help. And also kindly share working driver for one plus 8T for msm downloader, so that i can check again.

Arunraj90 said:
Hi all,
My OP8T got stuck at fastboot screen ,i tried several ways from msm tool finally found that all fastboot file available in the net was for kebab and mine is kona. So the msm tool returns "param preload" with "device not match image" error.While searching more about the difference found that kebab comes with 855qc and lpdram4 but kona comes with 865qc and lpdram5. Im now stuck n fastboot screen more than a week. Can anyone guide me or point me for this device fasboot rom??? Or else how to recover fom this? Need urgent help.
Click to expand...
Click to collapse
Change the data cable and install drivers manually again L2 drivers try on different USB port

jahanzaiblohani said:
Change the data cable and install drivers manually again L2 drivers try on different USB port
Click to expand...
Click to collapse
Tried original cable, Ambrane brand cable, Samsung cable. Can you share me the drivers? What is L2 drivers?

jahanzaiblohani said:
Change the data cable and install drivers manually again L2 drivers try on different USB port
Click to expand...
Click to collapse
Tried original cable , samsung cable, and one 3rd party branded cable no use. Can you share me the driver? What is L2 drivers?

Here is the log file of msmdownloader. This is the latest one. Can anyone find what's the problem?

Arunraj90 said:
Tried original cable , samsung cable, and one 3rd party branded cable no use. Can you share me the driver? What is L2 drivers?
Click to expand...
Click to collapse
I got the QCOM driver I use from here: https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
And the one I downloaded is shown in the attached screenshot. I used that one because it's newer than the bottom one and is for 64-bit Windows.

Question [HELP!] Needing to flash OP9 back to stock, but I have some issues...

Trying to flash my friend's phone back to stock but having some issues, you might have seen twixyfig's post in the OnePlus 9 Pro threads, but it's a regular OP9 and not the Pro.
Anyways, I have been trying to flash to working condition but MSM won't help. It keeps saying "No valid trg ID" and "Param preload" for a while now. This happened because we tried to root the phone but failed. The bootloader is unlocked, and fastboot works too.
TIA.

Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.

shadabkiani said:
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
Click to expand...
Click to collapse
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "

twixyfig said:
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
Click to expand...
Click to collapse
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.

shadabkiani said:
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
Click to expand...
Click to collapse
Thanks! Im gonna try this today and give you an update when something happens

twixyfig said:
Thanks! Im gonna try this today and give you an update when something happens
Click to expand...
Click to collapse
I think you were trying Indian MSM Tool. That might be the problem.
When your open MSM Tool, choose Others as login.

Write me in dm and I will help you, I think I can solve your problem

you can download OP9PRO India MSM tool(OnePlus_9_Pro_India_OxygenOS_11.2.4.4) and
1.unzip OP9Pro India ROM and download to your phone(select the firhose chebox)
2.if you success to download it,your phone will restart to the OOS.
3.Login your Google account and unlock OEM,then reboot your phone
4. install "Oxygen Updater", VERSION 5.7.3，you can find it on github.
5.download OOS for OP9 , archive name is "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip"
6.enter the oxygen updater,and flash "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip" to your phone
7.reboot and fixed!
PS: my english is so suck,try to read it!
good luck!