Hey guys, I want to unroot my phone and lock the bootlodaer.
downloading the latest software from OnePlus's site and flashing with local upgrade in the system updates setting should be enough? (and of course locking the bootloader afterwards)
Or should i take more steps like uninstalling magisk and restoring images?
Thanks!
Doesnt MSMTools restore the phone to original settings?
orma1 said:
Hey guys, I want to unroot my phone and lock the bootlodaer.
downloading the latest software from OnePlus's site and flashing with local upgrade in the system updates setting should be enough? (and of course locking the bootloader afterwards)
Or should i take more steps like uninstalling magisk and restoring images?
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ <<< look at this thread and read carefully and do all this step correctly and your phone is unrooted and bootloader is also locked
GraveDigger176 said:
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ <<< look at this thread and read carefully and do all this step correctly and your phone is unrooted and bootloader is also locked
Click to expand...
Click to collapse
Quick question, the oos version listed there is older than what I have currently.
Can I just download the latest version from Oneplus's website and use that?
orma1 said:
Quick question, the oos version listed there is older than what I have currently.
Can I just download the latest version from Oneplus's website and use that?
Click to expand...
Click to collapse
Download the latest MSN tool flash it as it mentioned in the instructions and after it boots update via OTA to your latest OOS
Remember that you download the MSN tool for your phone
MSN tool can't seem to detect my phone any idea why?
It seems I triggered the edl mode as the pc detects qualcomm instead of oneplus as the device.
for now i booted the phone normally
Have tap the enrum button ? And your PC detected right in edl mode your phone should listed as Qualcomm 9008 when I remember right and in MSN tool should it shown as detected if not tap the enrum button in MSN tool
GraveDigger176 said:
Have tap the enrum button ? And your PC detected right in edl mode your phone should listed as Qualcomm 9008 when I remember right and in MSN tool should it shown as detected if not tap the enrum button in MSN tool
Click to expand...
Click to collapse
I did not tap the enum button as it said nothing about that in the tutorial.
The device was not detected as Qualcomm 9008 it was Qualcomm and a lot of letters and numbers.
I will try again with the enum button later when I don't need to use the phone
orma1 said:
I did not tap the enum button as it said nothing about that in the tutorial.
The device was not detected as Qualcomm 9008 it was Qualcomm and a lot of letters and numbers.
I will try again with the enum button later when I don't need to use the phone
Click to expand...
Click to collapse
You phone must be listed as
QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed. Look how is it listed if it not QDLOADER 9008 then drivers are missing
GraveDigger176 said:
You phone must be listed as
QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed. Look how is it listed if it not QDLOADER 9008 then drivers are missing
Click to expand...
Click to collapse
if it is listed as QHUSB_BULK how can I install the driver?
As i write before, read this >>>> https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ carefully and follow the instructions, all is inside in first post. You need the Qualmcomm drivers, the download is mentoined and linked in this thread.
GraveDigger176 said:
As i write before, read this >>>> https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ carefully and follow the instructions, all is inside in first post. You need the Qualmcomm drivers, the download is mentoined and linked in this thread.
Click to expand...
Click to collapse
installing the drivers like you said seemed to do the trick.
My phone is now working.
Thank you very much!
orma1 said:
installing the drivers like you said seemed to do the trick.
My phone is now working.
Thank you very much!
Click to expand...
Click to collapse
Glad you got it working you're welcome
Related
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.
maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc
If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.
Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!
No problem,glad to hear you solved the problem
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
Dear guys ，my phone crashed when i am playing the game,and then i can't reboot my phone even i use the hardware buttons. i installed the drivers and the QPST on the computer and it show Qualcomm HS-USB QDLoader 9008 (COM 10) in the Device manger when the phone connected computer via USB.
does any rom can save my phone?
and my phone has installed the PE+ 10 before it crashed
Liiiiii said:
and my phone has installed the PE+ 10 before it crashed
Click to expand...
Click to collapse
You can try a ruu flash to bring it back to full stock,, as long as you can get to download mode
hammered58 said:
You can try a ruu flash to bring it back to full stock,, as long as you can get to download mode
Click to expand...
Click to collapse
I think the mainboard is broken , it’s time to say goodbye to my U11.
Thank you
Make sure to delete all other drivers and then make sure you install the correct HTC drivers, any other driver that isn't the correct HTC can and will interfere with you trying to run ADB or fastboot commands.
Greetings to all
After flash rom on fastboot and rebooting the device, the device entered the recovery, but the recovery is not working just black screen
I have pressed the power button and volume down button for a long time but nothing works
Currently the device is completely damaged!!!
I want to get into the bootloader in any way
Power up and connect to a Windows PC, what does the device manager display?
ULTRAJC said:
Power up and connect to a Windows PC, what does the device manager display?
Click to expand...
Click to collapse
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
twuijri said:
I was trying to connect it to a Mac
It is now connected to a Windows device and the device recognizes it
""Qualcomm CDMA Technologies MSM QUSB_BULK_CID:0412_SN10E679A""
Click to expand...
Click to collapse
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
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.
Click to expand...
Click to collapse
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
OhioYJ said:
I'm not sure what your ROM installation process was, however at this point sounds like you need to use the MSM tool and recover your phone.
Unbrick tool to restore your device to OxygenOS <-- Use this thread.
Also from that thread:
Drivers are in that thread.
Screen will be blank / off during this process when you are in this mode (what you are seeing). At least that is what I believe you are describing / seeing.
Click to expand...
Click to collapse
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
twuijri said:
Thank you, the device has come back to life after using ""MsmDownloadTool Global_KB05AA"" my phone ""oneplus 8T KB2000""
After the device worked, I ran into another problem ""QUALCOMM CrashDump Mode""
Is there a MsmDownloadTool for China devices oneplus 8T KB2000?
I'm so sorry for the problems I'm raising but I need help
Thank you for your time and help in solving other people's problems
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
Thank you from the heart. I read the entire topic and tried all the methods. It took me 10 hours to work
I was so frustrated that I thought about buying a new device
Only 10 hours after knowing the solution of MsmDownloadTool There was a whole day after the device died
Thank you, thank you for everything you do to serve others
""All user from XDA ULTRAJC & OhioYJ""
The device has returned to work
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
UP. Any thoughts? Any suggestions? Please!
Svobodniy_ said:
UP. Any thoughts? Any suggestions? Please!
Click to expand...
Click to collapse
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
BillGoss said:
It might help if you shared what you've actually done (what you did that resulted in bricking and what you've done to try fixing things) in detail. Include versions of software and source.
Click to expand...
Click to collapse
It's complicated, because I tried a lot of ROMs from this forum and from other sources... The main problems, that MSM doesn't see my phone if I want to install ROM through MSM, and Fastboot give a lot of errors, if I want to install ROM through Fastboot...
How I brick my phone? I used file from OnePlus to unlock the bootloader (before it I unlock my phone from T-Mobile). After that all my data was wiped and I decided to change ROM from T-Mobile's to Global. I tried one of the ROM's (I don't remember which, but one from this forum). And my phone became a brick. (previously in my life I reinstalled a lot of ROMs on my Samsung Galaxy S2, Samsung Galaxy S4 - and have no issues, but this time...)
Use EDL to recover. You can get to fastboot, so you are not hard bricked. Make sure drivers are installed properly, try a different computer/cable
Svobodniy_ said:
OnePlus 8T+ 5G T-Mobile KB2007
My phone has become a brick. 3 days have been trying to restore it. Can't find the solution...
What issues I have:
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager
- MSM tool doesn't see my phone
- EDL mode doesn't load
- fastbootd doesn't load
- all fastboot roms show a lot of errors during installation
Works only usual fastboot.
What can you recommend me to try? Thank you!
Click to expand...
Click to collapse
It seems, on PC side of things you don't have drivers properly installed, otherwise you wouldn't have
- no "QHUSB_BULK" in Device Manager
- no "Qualcomm HS-USB QDLoader 9008" in Device Manager.
For the same reason, i presume MSM doesn't see your phone.