Related
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Tiic said:
Hi Guys,
Im new to the forums so i hope this is the right place for this post
I have a hardbricked oneplus one 64GB.
I have read and followed mutiple guides here and on youtube on how ot unbrick it.
But in every guide i followed mine "failed" at the same step.
When i start the "oneplus one recovery tool" or Msm8974DownloadTool this happens; (cant seem to use a link so ill try to explain it).
It starts with one green bar, when that is finished it stops an i hear the disconnected device sound.
I am currently on Win 10 but i also tried it on WinXP since mutiple posts suggested hat it would work better, but that also didnt help.
I also tried diffrent drivers (oneplus driver from the color zip), google multi driver, qualcomm driver etc.
Hope someone can help
Click to expand...
Click to collapse
How your device got bricked?
Which recovery tool you tried?
Mr.Ak said:
How your device got bricked?
Which recovery tool you tried?
Click to expand...
Click to collapse
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Tiic said:
I don't have all the info since i got the phone from a "friend" who was about to throw it out, but ill do my best to provide accurate info
According to the privious owner the flashing of a custom rom or recovery went wrong and it ended up in it's current state.
The recovery tools i tried are;
- Oneplus one recovery tool by; Zyxxeil
- Oneplus one toolkit 1.5 by Manudroid19
- Msm8974DownloadTool
Click to expand...
Click to collapse
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Mr.Ak said:
Use the one with cm11s by Zyxxeil.Use Xp and use Qualcomm drivers,as this tool doesn't use fast boot/adb drivers and instead uses USB debugging port.
It need a few tries before device getting detected.
Make sure the device is getting recognized as "Qhs_bulk" or "Qualcomm diagnostics 9006" or some thing like that then install drivers manually.Also try different ports and refresh the toolkit. Open the toolkit with administrator rights.
Hope this helps
Click to expand...
Click to collapse
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Flashing 8974_msimage.mbn nin a loop.... you're not the only one with this problem. I couldn't find a solution to this problem so far. Have tried fresh installs of Windows XP and Windows 7 and drivers installed in Test Mode without success. Please report back once you could figure out what's wrong.
Tiic said:
I'm on windows xp now.
Made a clean install to be sure.
Phone is connected as Qualcomm HS-USB QDLoader 9008
The Zyxxeil tool recognizes it as a com port.
When i press start, it starts flashing 8974_msimage.mbn
When it finishes it just does the same. It looks like it's stuck on a loop at flashing 8974_msimage.mbn
I would post some pictures but i can't since im a new user
Edit; It is the same as this guy; youtube (dot) com/watch?v=TOw3-yX57jM
Click to expand...
Click to collapse
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Mr.Ak said:
Got it,it's because of a bad download or corrupt zip perhaps.Redownload the toolkit and also try with Color Os toolkit too.
If your device is recognized then there's no way you can't bring it back to life.
Click to expand...
Click to collapse
Just redownloaded the tools and tried again.
Still the same issue, i also tried the color os toolkit like you suggested.
I have the same issue too, keep installing 8974_msimage.mbn again and again.
I'm still open for sugestions since the issue is still there
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
kthejoker20 said:
Right click msm tool, and RUN AS ADMINISTRATOR.
Problem solved.
Click to expand...
Click to collapse
Although it is correct that you must run it as admin, this isn't the issue at all. There are phones that appear to be broken beyond the point where you can fix it with software.
MrBrainstorm said:
Although it is correct that you must run it as admin, this isn't the issue at all..
Click to expand...
Click to collapse
Yep, i always run tools like this as admin, the issue is something else in this case, but i wouldn't know what exactly
I may have found a solution/work-around to the problem described (in case anyone's still trying to unbrick a OPO after all this time). I must warn, however, that I really have no idea what I'm doing as I'm new to all of this, and have blundered through with no real understanding of what's going on, so pay heed at your own risk. It uses Qualcomm's QFIL program and Zyxxeil's OPO unbricking tool. I want give detail in describing the steps involved, so this will be fairly long.
***background***
My 64GB OPO has for the past couple of months almost always failed to get past the first 6-7 seconds of booting, and powered off before reaching the Cyanogen animation. It did the same when booting into fastboot and recovery, and at some point it stopped being able to access recovery at all. Very rarely it would boot, but pressing the power button while it was on would cause it to crash a few seconds later. I discovered that it would consistently boot properly if volume up were tapped while holding down the power button before it vibrates and the OnePlus logo appears, but this fix simply stopped working recently, and so it became impossible to turn the OPO on. Before giving up on it, I decided it would be worth trying the hard unbricking tool based on the ColorOS installer by Zyxxeil. However, I had the problem where the tool continually repeats the step of flashing 8974_msimage.mbn without progressing any further, to which nobody ever seemed to find a solution. I may have found a way to get around the problem, however.
Even though the procedure seems to have worked, the phone still shuts down after a few seconds as it did before (so I suspect my device has a hardware problem, possibly with the power button, and there's nothing that can be done for it). This means that I can't confirm that the fix actually works, but only that it appears to have worked. What it did was:
1) unbricked the phone - it probably wasn't even bricked before, but it definitely was after the installer hung on 8974_msimage.mbn ; it wouldn't respond to the power button at all afterwards. Applying the workaround allowed it to show signs of life again.
2) installed the COS11 fastboot. I'm not sure and can't tell whether the rest of the OS is there or intact, but the fastboot logo has changed from the newer small one to the bigger one from older versions.
***the problem***
The standard method for dealing with a hard-bricked OPO is to use the ColorOS tool as described in the "[GUIDE] [UNBRICK] Unbrick Oneplus One" thread and then flash Cyanogen, or to use Zyxxeil's tool which goes straight there. A common issue in both is that after pressing start, the tools repeat the step of flashing 8974_msimage.mbn , seemingly disconnecting the phone each time, and never progressing beyond that. This happened to me as well. This will happen if the tool is not run as an administrator, but for some people the same problem is seen even if it's run as an administrator. To the best of my knowledge, nobody has posted a solution to this problem, but some have suggested using alternative methods such as using QFIL (which I have gotten to work) or MiFlash.
***potential solution***
From what I understand, QFIL does the same thing as the unbricking tool, only not automatically. I directed it to use the files provided by Zyxxeil's tool, and it was then able to do something that unbricked the device as described above. This is what I did: (all on Windows 10, *not* using the original cable)
Required files:
1) Obtain the Qualcomm QDLoader driver. I used the the Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64 driver from Zyxxeil's tool's thread (page 5, #48).
2) Download Zyxxeil's tool. I used the 64GB version. Extract DRIVER.iso and run setup.exe as described. I'm not sure whether this actually did anything and presume manually installing the driver in 1) overrides this, but I'm including this for completeness.
3) Download QFIL version 1.0.0.2 . I originally used 2.0.0.5 , but this did not work (it produced the error "unable to read packet header. only read 0 bytes", to which the recommended solution was to use an older version). This can be run from the extracted folder. Open it once, and then close it again - it seems not to behave properly the first time it is run.
Preparation:
4) Create a new folder, for instance on the desktop, and give it a short name. Copy and paste (or just move) the contents of the "OnePlusRestoreTool" folder from Zyxxeil's tool into here. This step is because QFIL supposedly doesn't like long folder names or locations (I'm not sure whether this is true or not but there's no harm in making sure).
5) Install the QDloader driver: (the PC may need to be disconnected from the internet for this stage, I think Windows may try to automatically download and install incorrect drivers)
>Open device manager, then plug the OPO into the computer. It should come up after a few seconds under "Ports (COM & LPT)" as something like QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Mine originally showed up as "Quectel QDLoader 9008". If it comes up as a malfunctioned device ("Unknown USB Device") under "Universal Serial Bus controllers", try holding the power button on the OPO down for a few seconds, or holding it down for a few seconds at the same time as volume up. If it's still not recognised, try rebooting the PC and repeating this step.
>Right click on the device as it appears in device manager, select "Uninstall device", tick the box saying "Delete the driver software for this device", and click on "Uninstall".
>The OPO will disappear from device manager. Unplug and then replug it into the PC, and after a few seconds it should be recognised again, perhaps as "Unknown USB Device" again, requiring the same procedure as above. It should now show up as QHSUSB_BULK under "Ports (COM & LPT)"
>Right click on the device and select "Update driver", then "Browse my computer for driver software". Paste in the file path for the folder containing the driver as downloaded above, which will be called "20561190_ed08f7139a2028da454a6668162f44ac311facc0" if using the driver specified above. Ensure "Include subfolders" is ticked, and click on Next. This should install the driver, and because it's signed, it shouldn't present problems often encountered in this stage. Your device should now be called "Qualcomm HS-USB QDLoader 9008", with (COM#) after it.
Fix:
6) Restart the PC, leaving the phone plugged in. Open device manager again. At this point, if it is detected as a malfunctioned "Unknown USB Device", do not try to remedy it as described above - leave it as it is. This is exactly what happened in my case.
7) Run QFIL.exe as an administrator. I don't know whether this is actually necessary to run as an administrator, but seeing as problems arise in the normal methods from not doing so, it seems sensible. If the device is listed as "Unknown USB Device", then QFIL should say "No Port Available".
8) In QFIL, click on "Browse" in the "select programmer" section. Navigate to the folder where the contents of Zyxxeil's tool were copied/moved to, and open "prog_emmc_firehose_8979.mbn". Lower down, click on "Load XML", which should give you three files to choose from. As I couldn't fully boot my OPO afterwards I don't know which one is most appropriate, but I have tried the procedure with each and it worked for all of them. Perhaps start with rawprogram_unsparse.xml and if that doesn't work try the other two. Click Open, then select patch0.xml , then click Open again.
9) Paying attention to the QFIL window, hold down power+volume up until the text changes from "No Port Available" to "Qualcomm HS-USB QDLoader 9008 (COM#). Incidentally, this will also cause the device to change from "Unrecognised USB Device" to "Qualcomm HS-USB QDLoader 9008 (COM#)" in device manager. I believe that this step starts "Qualcomm's debugging mode" as explained in Zyxxeil's thread, and this is necessary for the process to work.
10) Click on "Download" (below "Load XML"). QFIL should do its thing, and if nothing has gone wrong the phone might be unbricked at the end of the process. Disconnect from the PC and see if it works.
In my experience, where this step did not work it gave one of two errors:
"unable to read packet header. only read 0 bytes" - this happens on the newer version of QFIL, which is why I used the older one.
"unable to download flash programmer using sahara protocol" - this was the troublesome one. I believe it means that the phone is not in Qualcomm's debugging mode. This would probably be the case if, for whatever reason, the PC recognised the phone immediately as Qualcomm HS-USB QDLoader 9008, and so it wasn't necessary to hold power+volume up for the PC to recognise it properly. In my case the program ran properly the first time but was interrupted because I hadn't transferred all of the right files to the target folder. After I had done this and tried again, it gave this error. I fixed this by holding down power+volume up, while the device was recognised, until the PC made a sound indicating something had been plugged in. The next attempt to download was successful.
If the procedure doesn't work properly, it might also be worth using one of the other two XML files mentioned in step 9.
*** ***
Anyway, after hours of searching and trial and error, this unbricked the phone, with it becoming responsive once more to button presses, despite still having the original problem of powering down during boot. It seems to have the CM11 fastboot as expected, and I was able to have my PC recognise it in the short time it stays on using fastboot devices. Other than that, I'm afraid I don't know how successful this was, or how successful it would be for other people. I hope this is useful nonetheless!
hi follow this guide https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.
I found this for you: https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/page1
@misslebulletttttt did you fix your Pixel. If yes, how did you do that?
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
Tacis said:
@misslebulletttttt did you fix your Pixel. If yes, how did you do that?
Click to expand...
Click to collapse
sadly, the files that download tool asked was far proprietary, I'm not able to peek it a bit
I'm not saying these will fix or even do anything but I found them and maybe they can help you there Qualcomm usb drivers. I apologize if these are of no use.
I will just post here in case someone has the same issue and might contribute with the files...
Basically an Android device has a few steps of initialization
- power on
- initialize cpu and memory
- load bootloader
- bootloader selects boot mode
- having the boot selected, the kernel and device tree are loaded
- drivers are loaded
- system is loaded
- userdata is decrypted
Ok... So knowing that, when we want to write some partition on the device, we use fastboot. But first, the fastboot must have oem unlocked in settings. Well when unlocking in settings, this write in a protected partition (don't remember which one) which is checked if the fastboot can run some commands.
Well the next step is... Where is fastboot located?
Well, fastboot is located inside the bootloader. So, what?
Imagine that there isn't anything written in the memory... What would the processor do? It would think... Well nothing there... But must access the memory. So the cpu opens a port which is known as the emergency download mode (EDL).
EDL mode can be triggered with adb command or by shorting test points (there's another way, but I won't say it here)
Anyway when in edl mode, the processor talks a defined protocol, which is known as firehose.
So the first file you mentioned:
prog_emmc_firehose_xxxx.mbn
Is the programmer for the specific chipset, in order to make a handshake and allow to write.
Then after the handshake, you need to define how the memory will be partitioned (remember... It is considering a raw memory, with nothing on it). This lead us to the second file:
rawprogram_XXX.xml
This is basically how the memory is partitioned and where the image address is.
Besides those files, you need the img files (which will probably be only the system.img non sparsed i think...) And patch.xml too, probably.
But remember... The programmer needs to be signed and for the chipset... So if anyone has any contact with google... Maybe we can get those in order to unbrick devices... Anyway...
I just wanted to have those files, in case i run into a bad update...
I think we have to contact the carrier according to the bootloader files
misslebulletttttt said:
I'm the lucky one to get this scarce BRICK problem, my pixel 2 occasionally run into this, can't boot up any more, no bootloader, recovery,
plug into the pc, it always tell qualcomm hs-usb qdloader 9008,
had searched out all the forum, need to use QFIL to flash correct, prog_emmc_firehose_xxxx.mbn, together with rawprogram_XXX.xml.
what is that ? anyone happen to know where to get it ?
any idea is pretty appreciated.
Click to expand...
Click to collapse
Hello friend! I have the same problem as you! (Hard bricked Pixel 2 and can't find firmware files for flashing device(via QFIL or QPST)). Do you have any progress on this issue ?
I don`t know where to go with this problem except for this forum
Hi, have you found a solution to this problem? I got a hard brick after the update (
Any update from anyone please?
bmw9651 said:
download > Tool all in one. Update it. update the drivers button at the bottom. now....... choose your phone. now choose flash factory image button.
it go to page where you pick the right firmware for you phone. press the download link. go back to Tool all in one and find the file you just download and then flash it with the button.
Click to expand...
Click to collapse
What does any of that mean? There is no download for a, tool all in one around here.
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
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
I have a hard bricked OP9 and have tried alot of different guides from here or other ressources.
The problem is somewhere in the process something is not supported and the how to dies there.
MSM download tool prompts that says "Packed image not exists!"
OP9 LE2113 version (EU Version i guess)
Phone is black screen and can not be detected through ADB or fastboot. Either through the Qualcomm HS-USB QDloader 9008 Drivers.
Before it bricked it was unlocked (bootloader) Not sure it is anymore
Can someone send me a link or guide that can guide me the right direction?
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Ill try that this evening, ill let u know ill turn out.
I typically run into sahara connection because i dont have connection through ADB of fastboot
#gorilla p
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Click to expand...
Click to collapse
i have used this link
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/ India version
And at the moment it is booting.
Unticked reboot and SHA check, This is indeed a good day !
Ive got a working phone again,
I will mark this thread as solved