I recently purchased a 9 Pro T-Mobile edition. It was supposed to be a global edition, but this information was willfully obscured by the eBay seller. Whatever, I figured I could follow this guide to convert it to global firmware. I've rooted plenty of OnePlus phones before and am very comfortable with the process, as well as using MSM to fix things when they go wrong. However, things went even worse than normal. I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed. Now I cannot access fastboot or recovery, or do quite literally anything with it.
I figured I'd use MSM and fix it just like I did when things like this happened to my OnePlus 8. So I downloaded the T-Mobile MSM from this thread and ran it. When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."
I assumed that this error was due to the fact that some of the images that were successfully flashed are from the global image, while this MSM tool is for TMO specifically, so I tried to the global MSM tool from the same thread instead. It also fails Sahara communication with the exact same error. If I use Lite Firehose, it gives the error "Unsupported Target TMO."
At this point, I'm at a complete loss. I've tried to power off the phone via holding the power button + volume up button, but it never gives any response no matter how long I hold it. I'm not sure that the phone is able to turn on at all. My next guess would be to disconnect the battery and reconnect it, but I'm very hesitant to pull apart the phone without seeing if anyone has any better suggestions first. If I could access fastboot, I could have a download of a clean TMO firmware and could easily re-flash everything, but I can't get a single response out of the phone besides MSM errors. Any help would be much appreciated.
I just realized that that article is for the Oneplus 9 and NOT the Pro. That definitely explains why it broke in the first place, but doesn't help me get it back. The MSM Tools I'm using ARE for the Pro.
When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?
CZ Eddie said:
When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?
Click to expand...
Click to collapse
They're both using COM3
blindcat97 said:
They're both using COM3
Click to expand...
Click to collapse
Qualcomm.......9008?
TheGhost1951 said:
Qualcomm.......9008?
Click to expand...
Click to collapse
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)
blindcat97 said:
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.
TheGhost1951 said:
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.
Click to expand...
Click to collapse
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.
Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
CZ Eddie said:
Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
Click to expand...
Click to collapse
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.
blindcat97 said:
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.
Click to expand...
Click to collapse
I'm a little confused about how you got your phone to its current state.
Your first paragraph has some minutia in it.
" I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed."
What images did you download and how did you apply them to your phone?
I was following this guide to convert OP9 (not *pro*, which is where I messed up and I feel very stupid for not realizing that) from T-Mobile to Global firmware. It provided download links to a zip file full of img files, and a flash-all.bat which used fastboot commands to flash the individual files. Half of the files didn't flash because "Flashing critical partitions is not allowed", but some of them did flash successfully. There's no log file to tell me which ones did and did not work. Here's the chunk of the flash-all script that actually contains the fastboot commands:
Spoiler: flash-all excerpt
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash abl abl.img
fastboot flash bluetooth bluetooth.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot reboot fastboot
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
It got through the first reboot okay (despite booting to fastbootd and me having to manually redirect it back to fastboot), but when it reached the second reboot command, it just died and wouldn't turn on any more, and the third block of commands were never executed. So I'm guessing that something it flashed in that second block is what completely broke its ability to boot. I would flash the images from a clean copy of OP9Pro TMO firmware, but I can't get to fastboot at all.
blindcat97 said:
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.
Click to expand...
Click to collapse
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?
im not really that experienced with this stuff but this kind of happened to me today so i decided to make an account and try to help you. Basically what I did was I deleted everything on it, like I could only use fastboot mode. Then i used an msm tool from here. make sure you get the tmobile one because i tried global and it didn't work. after i used the msm tool it started working again. once again, i am not experienced in this stuff, so my advice may screw you over, but at this point you don't really have anything to lose.
TheGhost1951 said:
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?
Click to expand...
Click to collapse
From my original post: When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."
I've never run into the firehouse issue before.
But it's very common and is talked about in dozens of threads here.
But it looks like you've actually flashed some system files from a different phone.
I hope that doesn't mean MSM is rejecting you because it thinks you're a different phone.
Maybe try flashing a 9pro boot.img that would match the software you're supposed to be at right now?
Not sure if that'll mess you up more or not though.
Double-check that you've downloaded the correct MSM file
Research the SMT mode.
It's disabled for a reason - because it'll wipe your IMEI & other important things.
I don't know how to use it yet, but supposedly it'll fix unfixable things. When used properly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have no way of flashing. I can't get to fastboot, I can't get the phone to respond to quite literally anything other than MSM. Any combination of buttons does nothing. I'm not a professional with this stuff; if there's a way to flash to EDL without MSM, I don't know it. It looks like MSM rejecting because it thinks it's a different phone is exactly what's happening, and the only thing I can think to do would be essentially to mod it so that it thinks it's allowed to flash OP9 as well as 9Pro, or otherwise bypass the device check.
I'm certain I've got the right MSM tool. Doing some research into the SMT Download mode, it looks like it breaks core features, like the IMEI, and widevine. Is it possible to backup those partitions from EDL mode?
Basically, if my only way of recovering the device is to destroy critical sectors entirely, I might just send the device to OnePlus for repairs. My warranty was already voided by unlocking the bootloader.
blindcat97 said:
I can't get to fastboot
Click to expand...
Click to collapse
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.
CZ Eddie said:
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.
Click to expand...
Click to collapse
The phone is already off and cannot be turned on in any way, to any mode. Nothing happens when I hold that combination, nor any other. The phone is completely unresponsive.
Related
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?
craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?
U not able to flash boot the stock boot.img?
i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
You need to be in fastbootd,
Code:
fastboot reboot fastboot
craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)
@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse
djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support
djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked
Had an 11.2.3.3 Global rooted via Magisk OP9 Pro that I wanted to update via OTA to 11.2.4.4, which was offered via system update. I used Magisk to restore images before update, did the update, and then went back to install to inactive slot. Rebooted and it was still on 11.2.3.3 so I tried again. Upon trying again, my phone got to a Qualcomm debug/error mode. I experienced this before when on a different boot slot for some other diagnosis of another issue in the past so I switched boot slots.
The other boot slot is stuck in fastboot mode I come to find so I check what it shows if I reverted back to the other boot slot, which was the Qualcomm error. Now instead of a Qualcomm error, it shows language options, one of which is English, and then gives me "boot reason", "wipe data and cache" and "advanced". I believe this is the OnePlus recovery menu, which I have not needed to use before and in the past, used TWRP on other devices.
Can't I just reflash a whole system image for 11.2.4.4 (it'd have to be the European one right now since Global isn't available) via fastboot and it should be fixed, albeit unrooted and I can just re-root? I'd like to try this, but there's no "flash-all.bat" and I don't know the proper flash order for the Euro images within payload.bin as there's no xml file (I looked up a guide for directions on how to flash without flash-all.bat that I have used on other devices). Oh, and I tried to fastboot a known good boot.img and on one of the slots, it works fine, but still wont boot. The other gives error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". I'm stumped.
Wondering if this has been experienced by anyone else before. Wiping my device is the last resort and shall be avoided at all costs after how much I have configured it to my liking.
I saw the following on another guide:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
Followed this guide here after extracting the Europe full system image via Payload-dumper and it now boots somewhat, but after it looks like it's loading into OOS and boot is complete, I get a black screen instead of the lock screen. I get charging sounds when plugged into the computer, but just a black screen.
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Wondering if this has to do with the Europe 11.2.4.4 on my Global device. Going to try reverting to 11.2.2.2 Global full image now.
Geez, good luck
vibrantliker said:
Geez, good luck
Click to expand...
Click to collapse
Just tried flashing the older 11.2.2.2 images one at a time and now it's stuck in recovery...
The closest I can get it to full booting is with 11.2.4.4 Europe full image and I get a black screen only, after it boots up with the OnePlus logo. When plugged in, I get a charging sound every 10-20 seconds or so. Too bad there's no 11.2.4.4 full image for Global or I'd try that.
Also just tried fastboot boot 11.2.4.4_global_boot.img on this 11.2.4.4 Europe image and still no go. Boots and makes sounds, but black screen still.
Have you tried the MSM tool?
hadesflames said:
Have you tried the MSM tool?
Click to expand...
Click to collapse
I was considering it, but don't want to lose any data. Next step is to contact OnePlus technical support during normal hours and see if they can work with me to resolve this one. I believe I read here on XDA that people have contacted them and usually are able to resolve the issue. Trying to avoid clearing data as the device is fine as it boots, but I think the Europe image is conflicting somewhere and not allowing me into the system since it boots all the way to the lock screen, but I don't see a lock screen, just a blank screen with sounds after boot seemingly working, along with charging sounds (albeit, sounding every 10-20s like its periodically charging).
This is so odd though because I did everything as I should've and update seemingly occurred, but system version still showed 11.2.3.3. So I go back to system update and it said there was an issue and to restart again. Did that two times with magisk revert image and restore to inactive and it then stopped booting.
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
djsubterrain said:
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
Click to expand...
Click to collapse
Does stock recovery support ADB? At 8 pro you needed modified one..
pyry666 said:
Does stock recovery support ADB? At 8 pro you needed modified one..
Click to expand...
Click to collapse
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
Click to expand...
Click to collapse
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
pyry666 said:
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
Click to expand...
Click to collapse
Yeah I'm working at the moment so not on my own PC, can't really test it out
djsubterrain said:
Yeah I'm working at the moment so not on my own PC, can't really test it out
Click to expand...
Click to collapse
Just tried. ADB with stock recovery is "unauthorized"..So modified is needed if one wants to use stock recovery with adb
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
Click to expand...
Click to collapse
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
bulletbling said:
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
Click to expand...
Click to collapse
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
djsubterrain said:
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
Click to expand...
Click to collapse
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
Are there actual hw differences between AA and BA?
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
There's a pinned post at the top of the forum with all the available latest roms. Not sure they've added Global yet tho. Best going there or Oxygen Updater (when the phone is working) than the download page tbh, OnePlus ALWAYS takes ages to add builds there
pyry666 said:
Are there actual hw differences between AA and BA?
Click to expand...
Click to collapse
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
bulletbling said:
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
Click to expand...
Click to collapse
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
pyry666 said:
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
Click to expand...
Click to collapse
I wish I could go without my phone for weeks until they post the latest firmware to see if that even works, but I can't so I guess I'll have to use the msm tool and wipe all of my internal storage of documents, including taxes, and various files and downloads I've amassed over the past half decade. This really sucks. All because of a simple OTA that should've never caused this. They really should prevent this from being possible with the OTA update tool built-in to their system.
First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?
mbj731 said:
First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
Click to expand...
Click to collapse
Also, you need T-Mobile msm
oddlyspaced said:
In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?
Click to expand...
Click to collapse
I've tried that. Still no luck. Getting either "IMEI is incorrect" or "device doesnt match image" errors. Kind of odd getting different errors each time.
jamescable said:
Also, you need T-Mobile msm
Click to expand...
Click to collapse
I've tried them all just hoping one will work. Tmo-EU, Tmo, EU, Global etc etc
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
I use USB C to USB C 3.2 with no issues
Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)
BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?
mbj731 said:
BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?
Click to expand...
Click to collapse
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.
Shooter7889 said:
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.
Click to expand...
Click to collapse
Yes, I had been running on A13 for a few days. Got the itch to root but as I said, I couldnt unlock bootloader (kept saying to flash token) so I decided to start the whole process over, unlock the bootloader and try to manually flash A13 instead of doing a local upgrade. (hadnt hit OTA for me yet)
During the process, theres a point where you have to boot in to fastbootD to flash critical partitions that wont flash in regular fastboot.... using the commands "fastboot reboot fastboot" wouldnt get me to fastbootD as I read it's supposed to. I think during all that and scrolling through the bootloader menu, I hit "recovery mode" which was apparently wiped because I just went straight to a black screen and thats where it's been ever since. I did all the button combos etc thinking it would just go back to bootloader but to no avail.
I wish there was a way to do manual commands in EDL or something. Maybe bootloader is there just that it's not responding to the hardware keys?
Oh. When u tried to unlock BL did u try "fastboot oem unlock? Yeh usually, eben if I mess up with msm or flashing imgs, it will kind of get stuck in edl, and I have to hold all three hardware buttons for some time b4 it will finally respond
Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck
First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.
kjslabber said:
First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.
Click to expand...
Click to collapse
I taped all the buttons down and I'll watch it for a while and see if it boots up. I have tried holding them for a very good while with no luck already though
Shooter7889 said:
Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck
Click to expand...
Click to collapse
I've tried the IND MSM gives me an "unsuspected target TMO" error or something like that. So at least some tools are seeing it as TMo... Tmo tools say the device doesnt match! I'll have to find another computer or 2 to try.. I was supposed to ship off my oneplus 7t tomorrow for trade in on this 9 pro but now I'm using the 7t again as it's my only working device. this has been a headache. lol
thanks for the feedback. I'm trying everything I can think of and researching too
Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol
mbj731 said:
Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol
Click to expand...
Click to collapse
Every one of us that's been at this long enough has gone thru this or a similar experience. It's a lot more headache but you also learn a lot more for the next time or to help others. Congrats on getting it up
mbj731 said:
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)
Click to expand...
Click to collapse
You can use python3 to decrypt the .ops file, edit the first line parameters in the settings.ini, then python3 to encrypt the folder that was decrypted. Slow process but gives extra options.....
Hello everyone.
Wifes Redmi Note 8 Pro (begonia) is stuck in fastboot. I have tried to flashing stock rom (many different versions) using MiFlash (have tried two different versions of MiFlash) and phone still stuck in pure fastboot. When I restart it, then it go straight to fastboot.
I have tried to flash custom recovery - TWRP (many different versions), but can't boot into it. Commands like "fastboot reboot recovery" or "fastboot boot twrp.img" does nothing - it restart, but again go straight into fastboot.
Commands like "fastboot flash recovery twrp.img" success, but can't boot to recovery.
Phone is unlocked and all flashing ends with SUCCESS message.
Have also tried flashing using SP FlashTool as it's in this video
it also ends with SUCCESS message, but phone is still stuck in fastboot screen only. Tried to flash it with battery, without battery, but it had no difference.
This stuck happened, after official MIUI freezed and none of hardware buttons worked. Battery died, phone went off. Then I have powered it and then this pure fastboot happened.. I have checked hardware buttons, but they works correctly.
Spoiler: Some screenshots..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please if anyone know what to do with this except throwing it out from the window, I would appreciate it.
Thank you in advance!
Growicek said:
Hello everyone.
Wifes Redmi Note 8 Pro (begonia) is stuck in fastboot. I have tried to flashing stock rom (many different versions) using MiFlash (have tried two different versions of MiFlash) and phone still stuck in pure fastboot. When I restart it, then it go straight to fastboot.
I have tried to flash custom recovery - TWRP (many different versions), but can't boot into it. Commands like "fastboot reboot recovery" or "fastboot boot twrp.img" does nothing - it restart, but again go straight into fastboot.
Commands like "fastboot flash recovery twrp.img" success, but can't boot to recovery.
Phone is unlocked and all flashing ends with SUCCESS message.
Have also tried flashing using SP FlashTool as it's in this video
it also ends with SUCCESS message, but phone is still stuck in fastboot screen only. Tried to flash it with battery, without battery, but it had no difference.
This stuck happened, after official MIUI freezed and none of hardware buttons worked. Battery died, phone went off. Then I have powered it and then this pure fastboot happened.. I have checked hardware buttons, but they works correctly.
Spoiler: Some screenshots..
Please if anyone know what to do with this except throwing it out from the window, I would appreciate it.
Thank you in advance!
Click to expand...
Click to collapse
Try to press Volume down hard for 50 times. Then try to throw from high to the pilow/blanket many times. It's usually a hardware problem (Volume down got stuck). If they can't get help, you can try flash Engineer rom to test.
Kirasu2080 said:
Try to press Volume down hard for 50 times. Then try to throw from high to the pilow/blanket many times. It's usually a hardware problem (Volume down got stuck). If they can't get help, you can try flash Engineer rom to test.
Click to expand...
Click to collapse
I have tried to replace hardware buttons from another device. Problem is still here.
Made the experience that USB cables can be faulty. You can charge the phone with this cable. But you can't establish a working data connection with this cable. Sometimes it looks like it works, but it doesn't really ... you have weird behaviour. Therefore it is always a good idea to have many USB cables to switch.
Suggestion:
At first get Google's up-to-date ADB and fastboot: Linux or Windows.
Then get the latest TWRP recovery for begonia.
Then boot your device to bootloader mode.
Now try the boot-option within fastboot:
fastboot boot <twrp-recovery>.img
(Maybe try different USB-cables if this fails)
Now you can install/update TWRP within this booted TWRP instance
--> switch to install image and choose the recovery partition to install it.
HTH
shutdown-h_now said:
Made the experience that USB cables can be faulty. You can charge the phone with this cable. But you can't establish a working data connection with this cable. Sometimes it looks like it works, but it doesn't really ... you have weird behaviour. Therefore it is always a good idea to have many USB cables to switch.
Suggestion:
At first get Google's up-to-date ADB and fastboot: Linux or Windows.
Then get the latest TWRP recovery for begonia.
Then boot your device to bootloader mode.
Now try the boot-option within fastboot:
fastboot boot <twrp-recovery>.img
(Maybe try different USB-cables if this fails)
Now you can install/update TWRP within this booted TWRP instance
--> switch to install image and choose the recovery partition to install it.
HTH
Click to expand...
Click to collapse
Have tried two different cables. Fastboot boot recovery.img says success, but it loads back to fastboot.
Growicek said:
Have tried two different cables. Fastboot boot recovery.img says success, but it loads back to fastboot.
Click to expand...
Click to collapse
You really updated your fastboot?
Maybe try a different USB-port --> USB-ports on the back of your PC should works best.
The ones on the front plate of your PC are sometimes not satisfying!
And try another USB-cable (lend one from a friend).
shutdown-h_now said:
You really updated your fastboot?
Maybe try a different USB-port --> USB-ports on the back of your PC should works best.
The ones on the front plate of your PC are sometimes not satisfying!
And try another USB-cable (lend one from a friend).
Click to expand...
Click to collapse
Im using laptop. With same laptop, same cables I was able to restore few other phones in the past. Fastboot.exe is updated
Growicek said:
Im using laptop. With same laptop, same cables I was able to restore few other phones in the past. Fastboot.exe is updated
Click to expand...
Click to collapse
Have no ideas anymore.
Laptops / Notebooks are not my domain.
Maybe you should really try a PC of a friend ...
shutdown-h_now said:
Have no ideas anymore.
Laptops / Notebooks are not my domain.
Maybe you should really try a PC of a friend ...
Click to expand...
Click to collapse
I will give it a try
Original USB-C Cable from new Note 11 Pro 5G.
Have tried all of those with and also without battery.
mtkclient-gui for unlocking bootloader - SUCCESS
MiFlash 2020.3.14.0 flashing fastboot ROM - SUCCESS
Phone still in FASTBOOT mode.
____________________________________________________________________________
Latest ADB and Fastboot from your link
twrp-3.7.0_9-0-begonia.img
fastboot boot twrp-3.7.0_9-0-begonia.img - FAIL due to locked state
mtkclient-gui for unlocking bootloader - SUCCESS
Sending 'boot.img' (31380 KB) OKAY [ 0.688s]
Booting OKAY [ 0.062s]
Finished. Total time: 0.781s
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
ENGINEER ROM
Download Only - SUCCESS
Phone restarts normally!
____________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts normally to latest firmware.
Thank you very very very much for help. TIll today I didn't even know, that anything like ENGINEER ROM exists.
For everyone else, who whill have same problem. Try to flash ENGINEER ROM, then classic FIRMWARE.
Growicek said:
Original USB-C Cable from new Note 11 Pro 5G.
Have tried all of those with and also without battery.
mtkclient-gui for unlocking bootloader - SUCCESS
MiFlash 2020.3.14.0 flashing fastboot ROM - SUCCESS
Phone still in FASTBOOT mode.
____________________________________________________________________________
Latest ADB and Fastboot from your link
twrp-3.7.0_9-0-begonia.img
fastboot boot twrp-3.7.0_9-0-begonia.img - FAIL due to locked state
mtkclient-gui for unlocking bootloader - SUCCESS
Sending 'boot.img' (31380 KB) OKAY [ 0.688s]
Booting OKAY [ 0.062s]
Finished. Total time: 0.781s
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts back to FASTBOOT mode.
___________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
ENGINEER ROM
Download Only - SUCCESS
Phone restarts normally!
____________________________________________________________________________
mtkclient-gui for bypass SLA/DAA - SUCCESS
SP Flash Tool with: BegoniaDAfilesandAuthfile\MTK_AllInOne_DA_mt6765_mt6785.bin
BegoniaDAfilesandAuthfile\auth_sv5.auth
LATEST firmware
Download Only - SUCCESS
Phone restarts normally to latest firmware.
Thank you very very very much for help. TIll today I didn't even know, that anything like ENGINEER ROM exists.
For everyone else, who whill have same problem. Try to flash ENGINEER ROM, then classic FIRMWARE.
Click to expand...
Click to collapse
Good to know, saw some with these kind of problems. Some can get out by engineer rom and some not. You're one of the lucky guy
Are you still facing the issue ???
Sorry for my bad English!!
I'm a Mobile technician,and this method work for me!!
I have tried this with my Redmi k20 !!
It's a lengthy process !! But it will help you !!
1)- Extract the Fastboot rom
2)- copy adb files from your adb/ platform tools folder and copy it into the extracted Fastboot rom folder !
3)- open ' images ' folder from extracted rom
4)- connect your device
5) open cmd in images folder ( shift+ right click- open command window here)
6) type in cmd :-
fastboot devices
fastboot flash boot boot.img
fastboot flash system system.img
( Wait for some time - 5 min atleast )
fastboot flash vendor vendor.img
( Wait for 3-5 min )
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot reboot
7) your phone will automatically restart
( But still there will be no recovery or full rom..but it will just restart to miui- setup page )
8) again connect your phone in fastboot
9) open extracted Fastboot rom folder
10) run as administrator (or double tap ) the file -
" flash all.bat "
11) wait and watch --- it will take around 15 mins
12) your phone will automatically restarts
13) check the stock recovery is appeard or not ( it will definitely show the recovery )
14) done !! Enjoy
Hi there, I am encountering the following issue.
It is a hindi op9 pro
The situation:
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
Any ideas or advice? Plz help
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
it keeps on cycling back to 9008 so what you meant by xbl or abl is broken? Any solution ?
Renate said:
Can you locate the Firehose loader?
Click to expand...
Click to collapse
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
My msm tool from that
Renate said:
Have you tried various USB problem solving, different cables, different ports?
Click to expand...
Click to collapse
Yes I think it is no issues with my cable
Renate said:
If it keeps on cycling back to 9008 then xbl or abl is broken.
Can you locate the Firehose loader?
Can you try loading it manually using the Python EDL client.
Have you tried various USB problem solving, different cables, different ports?
Since you're on Windows you can also try my EDL client (although it uses a different Windows driver, not the V com port one, see insns).
Click to expand...
Click to collapse
FOR MORE DETAILS
I tried upgrading my device using fastboot firmware according to the following according to this article
How to Unbrick OnePlus 9/Pro via Fastboot Commands
In this comprehensive guide, we will show you the steps to unbrick the OnePlus 9 and 9 Pro devices via Fastboot Commands.
www.droidwin.com
when I reached to put commands in cmd and wrote
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
then reboot by
fastboot reboot fastboot
it gets stuck in edl mode and no anything showing just " Qualcomm HS-USB QDLoader 9008" showing in the device manager, appearing and disappearing about every five seconds
so the situation is
The screen is totally black
connecting to power supply - no reaction
holding only power (30 sec) - no reaction
holding + - loudness - no reaction
holding + + loudness - seems like a reboot, because windows is reacting to it "Qualcomm HS-USB QDLoader 9008 - Com4" work is disappearing and later on reappearing in the device manager
In the MSM Tool, it says:
1. Try to get PBL info
2. start downloading the firehose binary after 18sec.
3. Sahara communication failed....always
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Renate said:
I don't know, I don't care, I don't trust MSM tool.
You didn't say if any of the fastboot commands worked.
Click to expand...
Click to collapse
Fastboot commands already worked and I used them to upgrade my phone according to the article above, so when finished, I put a reboot command, and then it got stuck on EDL mod, so I tried to repair it using MSM tool it always says Sahara communication failed, any way to fix it plz my phone is new
Click to expand...
Click to collapse
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Renate said:
You flashed a bunch of stuff, but only a subset of important stuff.
Don't flash vbmeta_whatever without flashing the whatever.
Communication doesn't fail.
Either you can't write or can't read or you received garbage. Which is it?
That's why I don't care about tools that I don't know.
Since Sahara is in ROM it's not very susceptible to failure.
So what IS going on?
But another question is: why is it even going to EDL?
As I said, you can try the Python EDL client which won't necessitate swapping out the crappy Qualcomm Windows drivers.
Click to expand...
Click to collapse
thank you but is there a video explaining it bcz I am a noob in this stuff plz.
or you can contact my device using TeamViewer and try to fix it plz.
I don't know your partitions well enough.
If it wants a two stage reflash with 1/2 by (abl) fastboot and 1/2 by (recovery) fastbootd then you need a working recovery and I'm not sure that you have one.
The original post didn't indicate that you were able to reach/use fastboot.
I jumped on this because it seemed to be about USB/Sahara which I know something about.
We need the advice of somebody who knows more about your model.
Sorry
Can you tell how you ended up in this state? If you are a noob, why did you start wipe stuff from your phone without knowing how to what you are doing?
I would guess you thought a custom rom sounded nice but you don't have a clue what to do when things are starting to go south..
Edit: We, as a community always try to help out as much as we can but (and there is a BIG but) you have to understand the basics before you even start to do stuff or you will learn the hard and in some cases expensive way.
Read and do research at least for a few month, like reading most of the threads here and try to figure out how things work.
recovered my noodlep a week ago using this:
How to recover your device after flashing incorrect DDR xbl images
No matter how you are experienced or skilled in flashing ROM's, the things sometimes just happens. And you are here now... Even I was aware which DDR model was my device, yes.. I did it :D - flashed by mistake DDR4 xbl.img to my DDR5 noodlep...
forum.xda-developers.com
You may want to check it out....
Best luck. and don't worry. Just follow the steps and you'll recover your device.