I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.
In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting
viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem
whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.
whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"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"
}
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port
Related
Ive flashed many photon Q's before using RSD lite but for some reason now they wont even show up in AP Fastboot. IM not sure why but im wondering if it has anything to do with installing PDAnet a few weeks ago for htc drivers. RSD does however recognize my photon q booted normally. I can choose the file to flash and hit start, but where RSD used to reboot the phone into fastboot and start flashing, it says "The phone failed to switch to fastboot mode". Any help would be appreciated. I used to use RSD 6.1.4 and now use 6.1.5. This is happening with both versions. ive updated drivers, uninstalled and reinstalled drivers, uninstalled PDAnet.....
Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader
arrrghhh said:
Have you tried forcing the device into fastboot mode yourself?
Code:
adb reboot bootloader
Click to expand...
Click to collapse
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.
wbbjason said:
the phone goes into fastboot mode. I can get it by holding vol up and down and power. The problem is that when in fastboot, it isnt recognized by RSD. where in the past it has been. it just stopped one day. the drivers fail and i go to device manager and cant find a driver that needs updating to get the phone to connect. if you know of a driver i need to install manually please let me know what it is cause nothing is jumping out as needing updating. thank you.
Click to expand...
Click to collapse
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
already had that. most recent version. uninstalled and reinstalled that as well. i have no idea why none of the photon Qs will connect now.
Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com
arrrghhh said:
Hm, I think the Motorola Device Manager was all I needed on my Windows machine.
Click to expand...
Click to collapse
rbeavers said:
Try usbdeview uninstall and delete! all moto drivers and reinstall.
Photon Q &/or Note 3 on ting.com
Click to expand...
Click to collapse
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
Did you try the Moto Device Manager? That's all I recall needing for Windows.
wbbjason said:
Thanks for the help guys. So problem still unsolved but today I went back at it and noticed that the phone was showing up in device manager as "Samsung mobile device". So i uninstalled that driver, put it back into AP fastboot and plugged it in. now under "other devices" i have "Fastboot ASANTI_C S" and it needs to be updated. i want to make sure i update it with the correct file. if anyone knows where i can find this on my computer or the internet please let me know. it would be greatly appreciated.
Click to expand...
Click to collapse
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.
arrrghhh said:
Did you try the Moto Device Manager? That's all I recall needing for Windows.
Click to expand...
Click to collapse
KoolBurnX8 said:
If you haven't already, you can try putting the USB cable into a different USB slot. I didn't notice it before, but I had mine plugged in to a USB 3.0 slot. It worked for ADB, FASTBOOT and file transfers, so I thought nothing of it. Still the damn thing wouldn't be recognized in RSD Lite 6.5
I just switched it over to another usb slot(USB 2.0 port) and voila, works like a champ every time. You've probably already done this, but I thought I would just throw it out there.
Click to expand...
Click to collapse
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?
wbbjason said:
yeah i tried the device manager. uninstalled and reinstalled. and changing ports doesnt work. i have motorola drivers. like ADB QC Diag that i can install but im not sure its the right one. does anyone know the name of the driver that shows up in device manager when you plug in a photon q in AP fastboot?
Click to expand...
Click to collapse
Not sure if this will help you, but here's a screenshot of Device Manager when I rebooted to bootloader (fastboot) mode.
{
"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"
}
When I was having trouble, i've also read that RSDLite can be picky about the USB cable you use sometimes. If you have extras or have the one your phone came with, you might wanna give it a shot.
I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.
Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"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"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.
I have same thing did it work
I am just wondering if u managed to fix it.
I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?
mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)
mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/
Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.
install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers
Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif¬if_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!
DorkyDev said:
Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif¬if_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!
Click to expand...
Click to collapse
Are you needing help or you solved the bootloop?
I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.
DorkyDev said:
I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.
Click to expand...
Click to collapse
platform-tools-latest | drivers USB OEM | MTK USB driver
Obviusly you only need flash stock recovery.img as your device has A9.
For Custom Recovery like TWRP maybe I can ask my friend to help you. If - you still TWRP want?!
Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.
{
"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"
}
DorkyDev said:
Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.View attachment 5518101
Click to expand...
Click to collapse
Search in the internet How install MTK drivers, specially in the Win7. Better in Win10 and if you as that so the drivers [link] is much better, You can try installing that file but need reboot your computer. After try flash with SPFT.
Don't choose FORMAT+ALL or any option with FORMAT+........
Win7 need more effort to start drivers for Mediatek devices!
You can try pressing constantly the VOL - button when put USB for SPFT work.
The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.
DorkyDev said:
The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.
Click to expand...
Click to collapse
We often don't realize that certain errors are normal on our machine. So the question is to test in others computers.
But there are possibilities of company blocks or even something that has happened on the phone without it really should happen.
Some interesting cases:
1- I noticed with the image you showed about trying to flash all the firmware.
** So even if you have tried the Download only or Firmware Upgrade options, the question remains if you tried to flash only the recovery.img file? Obviously you can have the same error in SPFT?!
2- Cases of hardware vs software that match the use and characteristics found such as restarting the PC and trying to flash in a different USB port. Same problem?!: Drivers are resolved?!
The biggest case of suggesting something or thinking that this or that is a problem wastes precious time. Confirm the main steps!:
1- Driver correctly installed and working;
2- Driver works: Different USB PORT tested;
3- SPFT version must be tested. Mainly previous versions to confirm the error message that persists or may disappear;
4- Phone particularities: pressing the VOL buttons for a while can trigger the preloader that is responsible for the connection between the SPFT and your phone on the computer. Switching to VOL+ or Power or VOL- with VOL+ or VOL+ VOL - and Power may solve or confirm the non-solution.
Best way: Win10 with driver updates. Find the way to disable unsigned driver installations. But you can use this driver and you must restart your computer for it to take effect.
Make sure the USB port has a speed feature for the flashing process. Example: All USB ports are 2.0 only and SPFT asks for a USB 3.0 port to make the connection.
With everything confirmed the rest is something to question in relation to having the correct firmware file or the device itself having blocked the installation process due to a drastic change in the preloader or something that has changed and is blocking it.
Look previous posts about that so all depends on what you have and how you use it.
Unfortunately everyone (including me) who went through bad times like the one you have now, has a headache because it's a simple process and doesn't know what to do. But on the other hand, it's a huge learning experience when we solve it.
But there is still a choice without a headache: take it to a technical assistance and pay for it!
No on drivers when it goes to do the typical windows installation with the installation boxes in the upper left corner, I keep getting red x's.
I'm letting it charge some more and tomorrow trying again on my windows 7 laptop, as I think I'm also getting hung up on disabling driver signatures on windows 10 laptop. IDK if it's cause I'm dual booting JingOS 0.9 and that cancels out F7 or what the hang up is on that part.
In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.
shivadow said:
In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.
Click to expand...
Click to collapse
Would that also be done in SP Flash Tool or another software? I've also got these MTK tools.
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.
DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.
Click to expand...
Click to collapse
If you have more drivers for others phones like samsumg, motorola, lg, etc so remove that's and reboot computer. Install again MTK Drivers, UAC permissions and reboot computer. Test SPFT.
But here a good video to see and may be can fix - confirm driver issue in Win7:
Drivers: https://drive.google.com/file/d/1V2FducGB4pNpbkJWVmk2sfRJpf4Q5Bth/view
DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
Click to expand...
Click to collapse
Maybe corrupted zip file?
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
MacroWolf said:
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
Click to expand...
Click to collapse
Update drivers on PC
For the Sahara error, open MSM Tool, click use lite firehose, and click Start. Then do the key combo to get the phone in EDL. When you plug it in, the software will already be preparing to connect to the phone and it should work. If it doesn't, try another port, another cable, etc. Sometimes it's temperamental but usually what's happening is that you're not plugging in and starting the process fast enough as it only stays in EDL mode for a few seconds waiting for a connection.
EtherealRemnant said:
For the Sahara error, open MSM Tool, click use lite firehose, and click Start. Then do the key combo to get the phone in EDL. When you plug it in, the software will already be preparing to connect to the phone and it should work. If it doesn't, try another port, another cable, etc. Sometimes it's temperamental but usually what's happening is that you're not plugging in and starting the process fast enough as it only stays in EDL mode for a few seconds waiting for a connection.
Click to expand...
Click to collapse
Thanks for the advice. Checking the "Use Lite Firehose" has progressed it a bit further. I'm still getting an issue where it's failing at "Param Preload" were it states the error is "Device not match image"
I'll keep looking to see if I can find some more information about this. Thanks for the help!
MacroWolf said:
Thanks for the advice. Checking the "Use Lite Firehose" has progressed it a bit further. I'm still getting an issue where it's failing at "Param Preload" were it states the error is "Device not match image"
I'll keep looking to see if I can find some more information about this. Thanks for the help!
Click to expand...
Click to collapse
Unfortunately when that happens things get a lot more complicated which is why I personally think we should not encourage people to try to flash with fastboot, it messes up more often than it works, and now the device isn't recognized by the MSM.
Go download the Indian 9 Pro MSM Tool and flash that. Then download the global 11.2.10.10 full update from the pinned post and flash that from the local upgrade menu to get a working phone. From there you can either unlock the bootloader and go to a custom ROM or you can continue on to flash the global OOS 12 update.
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Qualcomm drivers.7z
drive.google.com
JonasHS said:
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Click to expand...
Click to collapse
The error OP has is because his device was corrupted by the fastboot flash attempt and the MSM Tool doesn't recognize it as a compatible model anymore. He needs to use the Indian 9 Pro MSM because it doesn't perform this check and then he has to local upgrade to the regular global OP9 software to get back to a stock state. I went through the same crap myself. Fastboot scripts cause more problems and people should just use the MSM Tool.
JonasHS said:
You use wrong driver. Don't use thirdparty driver to MSM. Use this driver it's work, trust me I have the same problem as you. Remove old driver.
Your phone can't shutdown and really .
I know it.
If this not work, so use you wrong firmware, and you are need to go to OnePlus community website and unbrick tools.
Click to expand...
Click to collapse
This didn't work. I had these drivers installed and when I switched to the ones you provided it simply did the same thing.
EtherealRemnant said:
The error OP has is because his device was corrupted by the fastboot flash attempt and the MSM Tool doesn't recognize it as a compatible model anymore. He needs to use the Indian 9 Pro MSM because it doesn't perform this check and then he has to local upgrade to the regular global OP9 software to get back to a stock state. I went through the same crap myself. Fastboot scripts cause more problems and people should just use the MSM Tool.
Click to expand...
Click to collapse
Ok, I think I understand some of what I need to do.
1. Download the Indian version of the MSM Tools for the OnePlus 9 Pro?
--> https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
2. Run the MSM Tools with the same method you recommended in your initial post
3. Local upgrade to the global stock rom.
I'm not sure what you mean by local upgrade the ROM. Does this mean using the Global version of the MSM Tools to flash, using fastboot to flash, or will the phone recognize the region disconnect and recommend it update the ROM? Sorry about this. I very much appreciate your help.
MacroWolf said:
This didn't work. I had these drivers installed and when I switched to the ones you provided it simply did the same thing.
Ok, I think I understand some of what I need to do.
1. Download the Indian version of the MSM Tools for the OnePlus 9 Pro?
--> https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
2. Run the MSM Tools with the same method you recommended in your initial post
3. Local upgrade to the global stock rom.
I'm not sure what you mean by local upgrade the ROM. Does this mean using the Global version of the MSM Tools to flash, using fastboot to flash, or will the phone recognize the region disconnect and recommend it update the ROM? Sorry about this. I very much appreciate your help.
Click to expand...
Click to collapse
Local upgrade means download the zip and place in the root of the storage. Go to Settings --> System --> System Updates and then bring up the menu and there's a local upgrade option.
Download the full OTA zip from https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
I had problems with the zip file disappearing if I downloaded it on my desktop and copied it over directly so either download it on the phone, make sure it's got a zip extension, and move it to the root of storage or enable developer options as well as USB debugging, connect to PC, and adb push the zip to /sdcard/ which worked every time I tried it (I have had a hell of a time with this device and bricking and I have it down to a science now lol).
EtherealRemnant said:
Local upgrade means download the zip and place in the root of the storage. Go to Settings --> System --> System Updates and then bring up the menu and there's a local upgrade option.
Download the full OTA zip from https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/
I had problems with the zip file disappearing if I downloaded it on my desktop and copied it over directly so either download it on the phone, make sure it's got a zip extension, and move it to the root of storage or enable developer options as well as USB debugging, connect to PC, and adb push the zip to /sdcard/ which worked every time I tried it (I have had a hell of a time with this device and bricking and I have it down to a science now lol).
Click to expand...
Click to collapse
Thanks for all the help. I am still running into an error with MSM Tools. I get the message "Unsupported Target O2"
Are there any good post I can use to read up on more of these error? The tool looks great, but trying to search references to each error has been less than fruitful.
Edit: Never mind. Apparently I needed to restart my computer cause it was looking to the incorrect target. It seems like it is currently working.
MacroWolf said:
Thanks for all the help. I am still running into an error with MSM Tools. I get the message "Unsupported Target O2"
Are there any good post I can use to read up on more of these error? The tool looks great, but trying to search references to each error has been less than fruitful.
Edit: Never mind. Apparently I needed to restart my computer cause it was looking to the incorrect target. It seems like it is currently working.
Click to expand...
Click to collapse
Did it work for you? It's strange that you got that error with the Indian 9 Pro MSM.
EtherealRemnant said:
Did it work for you? It's strange that you got that error with the Indian 9 Pro MSM.
Click to expand...
Click to collapse
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
MacroWolf said:
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
Click to expand...
Click to collapse
Awesome, glad that you got it sorted.
MacroWolf said:
Hi. I'm here asking for some advice from anyone who may have ran into this problem before or may have an idea on how I can fix this. I was following the guide post here https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/ to flash my rom back to stock and it failed to reboot into fastboot. This has left my screen blank. I don't get anything when trying to power on or off. I see that the driver pick up and that Windows 10 recognizes it is connected.
I've been trying to fix this using MSM Tools to flash the stock ROM, but am running into issues. I cannot tell if I'm in EDL mode and keep getting a "Sahara Communication Failed" error when trying to run the program.
Click to expand...
Click to collapse
I'm having a similar issue. Black screen. I can get it to start the process in the MSM tool (after some trial and error) but it now tells me "Device not match image". I've downloaded the Global tool ( and my device is a OnePlus 9 5G LE2115). OnePlus wants me to send in the device. I'd rather not if I don't have to.
MacroWolf said:
Yup, it worked. I don't know why I got that error but after a restart it's all good. Just got to do the local upgrade and it's done.
I really appreciate all the help you gave!
Click to expand...
Click to collapse
It's from not restarting after installing drivers
EtherealRemnant said:
Awesome, glad that you got it sorted.
Click to expand...
Click to collapse
I've seen you around while searching for my issue with MSM tool. Can you help?
Backstory: My device (OP9) has no os and no recovery. I managed to get fastboot back after an incident and as far as I can tell, I have EDL mode. However, MSM tools I've tried all get stuck on "waiting for device" after plugging in
Here's a pic of what EDL looks like on Windows device manager:
{
"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"
}
Does that look right?
Also as far as I can tell I have all the proper drivers. Windows seems to agree when trying to update them in device manager.
What is it I'm missing? Any advice would be amazing.
shadowofdeth said:
I've seen you around while searching for my issue with MSM tool. Can you help?
Backstory: My device (OP9) has no os and no recovery. I managed to get fastboot back after an incident and as far as I can tell, I have EDL mode. However, MSM tools I've tried all get stuck on "waiting for device" after plugging in
Here's a pic of what EDL looks like on Windows device manager:
View attachment 5634873
Does that look right?
What is it I'm missing? Any advice would be amazing.
Click to expand...
Click to collapse
Update the driver.
Unbrick OnePlus 9, 9 Pro Using EDL Firmware With MSM Download Tool
OnePlus has finally launched its OnePlus 8 series successor known as OnePlus 9 and 9 Pro with a much-upgraded camera, processor, display, refresh rate,
www.getdroidtips.com
Mate. Where were you the other day!
I'm actually embarrassed it was that easy. All day I've been on this. All. Day.
I swear I installed those drivers the first time as well. Windows confirmed everything was legit too but failed anyway.
Seriously thank you.
Glad that you got it fixed now. I have bricked my phone enough times messing with custom ROMs that I have the whole restoration process to a refined science at this point lol.
I was try to, unlock my phone from t-mobile (https://forum.xda-developers.com/t/convert-t-mobile-oneplus-9-to-global-or-other-firmware.4277169/), everything was fine.
i unlock my bootloader and SIM, but when i use the "flash_all.bat" and that finish, i have to Reboot into recovery and wipe everything, but the phone don't turn on.
This never happened to me, so i don't know what to do.
Nothing appears, any logo or battery icon.
when i conect the phone to the pc i heard the sound but seconds later is disconected
OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool
Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862
forum.xda-developers.com
Run the tool as other and click start before hooking up the phone while holding both volume buttons.
AtoZ0to9 said:
OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool
Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862
forum.xda-developers.com
Run the tool as other and click start before hooking up the phone while holding both volume buttons.
Click to expand...
Click to collapse
{
"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"
}
Idk if im doing something wrong but nothing happens
Ok, so if the MSM tool never shows any indication that it has seen the phone in EDL mode, doesn't start the flashing, etc, but you hear the computer noise when you plug it in, you should investigate your drivers.
Open up the Device Manager and then plug the phone up in EDL mode. EDL mode is achieved by holding both volume buttons while plugging in the phone. Look in the device manager and see what comes up. Somewhere around here are the correct drivers. Look at all of the unbrick / msm threads and one of them will have a driver download for you.
It sounds like a brick, and you are only getting into EDL mode, the mode used to flash back to stock with the MSM tool. So. Drivers. Check them out, and get that sorted and I believe you will be able to revive it.
AtoZ0to9 said:
Ok, so if the MSM tool never shows any indication that it has seen the phone in EDL mode, doesn't start the flashing, etc, but you hear the computer noise when you plug it in, you should investigate your drivers.
Open up the Device Manager and then plug the phone up in EDL mode. EDL mode is achieved by holding both volume buttons while plugging in the phone. Look in the device manager and see what comes up. Somewhere around here are the correct drivers. Look at all of the unbrick / msm threads and one of them will have a driver download for you.
It sounds like a brick, and you are only getting into EDL mode, the mode used to flash back to stock with the MSM tool. So. Drivers. Check them out, and get that sorted and I believe you will be able to revive it.
Click to expand...
Click to collapse
My computer detects my iphone, but when i connect the oneplus phone in my order pc is detectect like this
Delete that driver (check the box to permanently delete) and install this one:
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
Try the process again.
Loshim said:
View attachment 5655997
My computer detects my iphone, but when i connect the oneplus phone in my order pc is detectect like this
Click to expand...
Click to collapse
The TMobile msm might work but most likely won't if it doesn't use the OnePlus 9 pro msm and you need to install the driver that @AtoZ0to9 has mentioned
AtoZ0to9 said:
Delete that driver (check the box to permanently delete) and install this one:
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
Try the process again.
Click to expand...
Click to collapse
i did, i unnistall everything and install again, is the same, i connect my moms phone and is detecting my iphone to, idk what to do
Loshim said:
i did, i unnistall everything and install again, is the same, i connect my moms phone and is detecting my iphone to, idk what to do
Click to expand...
Click to collapse
Does it connect to the msm now also calm down same thing was happening to my phone and it's working fine now you'll be fine
I remember that I did something with the drivers in the process, since the abd bootloader was not detecting it for me, I really do not know if it influences.
this is the driver "android_winusb.inf"
Loshim said:
I remember that I did something with the drivers in the process, since the abd bootloader was not detecting it for me, I really do not know if it influences.
this is the driver "android_winusb.inf"
Click to expand...
Click to collapse
Did you install the driver that @AtoZ0to9 linked
stez827 said:
Does it connect to the msm now also calm down same thing was happening to my phone and it's working fine now you'll be fine
Click to expand...
Click to collapse
When you connected it did you just connect it and try or did you put in edl mode
stez827 said:
Did you install the driver that @AtoZ0to9 linked
Click to expand...
Click to collapse
yes i did
stez827 said:
When you connected it did you just connect it and try or did you put in edl mode
Click to expand...
Click to collapse
i put with edl mode
Ok well you need to download the OnePlus 9 pro msm tool
I still feel like this is possibly an issue with drivers / USB ports etc. Don't worry about other peoples phones, theirs is working. You are working on one thing and one thing only. The connection between YOUR phone and the computer. Have the device manager open ALL the time. Hook up the phone and whatever pops up, click it, hit the delete button on the keyboard, check the box to delete the driver. Download the drivers I linked, and unzip them and run the file. Hook up the phone again to a different USB port. See what comes up. It will most likely be the correct driver, if you followed the steps correctly. Run the MSM tool again and click the start button. If it drops the connection before you hit start, unhook it, hit start again, and hook it back up in EDL to a different USB port. Just gotta keep playing with it man. Mines weird too. I have to use one port for fastboot stuff, and one port for EDL stuff, and sometimes they aren't the same port it was previously. These are temperamental phones. Stay strong, be focused, use your training, we believe in you.
stez827 said:
Ok well you need to download the OnePlus 9 pro msm tool
Click to expand...
Click to collapse
Also 100% download this. Be prepared for everything.
AtoZ0to9 said:
I still feel like this is possibly an issue with drivers / USB ports etc. Don't worry about other peoples phones, theirs is working. You are working on one thing and one thing only. The connection between YOUR phone and the computer. Have the device manager open ALL the time. Hook up the phone and whatever pops up, click it, hit the delete button on the keyboard, check the box to delete the driver. Download the drivers I linked, and unzip them and run the file. Hook up the phone again to a different USB port. See what comes up. It will most likely be the correct driver, if you followed the steps correctly. Run the MSM tool again and click the start button. If it drops the connection before you hit start, unhook it, hit start again, and hook it back up in EDL to a different USB port. Just gotta keep playing with it man. Mines weird too. I have to use one port for fastboot stuff, and one port for EDL stuff, and sometimes they aren't the same port it was previously. These are temperamental phones. Stay strong, be focused, use your training, we believe in you.
Click to expand...
Click to collapse
Dude the TMobile msm is absolute dog**** and when I bricked my phone using the same guide he did I had to use the India OnePlus 9 pro msm tool as it was the only msm that worked so no it's not a problem with USB ports or drivers I had literally the same exact error and I ****ed my phone the same exact way so while there may be a extremely small chance that this fixes it it's still extremely unlikely that it will fix it
AtoZ0to9 said:
I still feel like this is possibly an issue with drivers / USB ports etc. Don't worry about other peoples phones, theirs is working. You are working on one thing and one thing only. The connection between YOUR phone and the computer. Have the device manager open ALL the time. Hook up the phone and whatever pops up, click it, hit the delete button on the keyboard, check the box to delete the driver. Download the drivers I linked, and unzip them and run the file. Hook up the phone again to a different USB port. See what comes up. It will most likely be the correct driver, if you followed the steps correctly. Run the MSM tool again and click the start button. If it drops the connection before you hit start, unhook it, hit start again, and hook it back up in EDL to a different USB port. Just gotta keep playing with it man. Mines weird too. I have to use one port for fastboot stuff, and one port for EDL stuff, and sometimes they aren't the same port it was previously. These are temperamental phones. Stay strong, be focused, use your training, we believe in you.
Click to expand...
Click to collapse
so, i connect the phone with edl and without edl, but in the devices manager nothings happens nothings appears, i heard the sound but i dont see nothing
you guys recommend me using another computer?
stez827 said:
Dude the TMobile msm is absolute dog**** and when I bricked my phone using the same guide he did I had to use the India OnePlus 9 pro msm tool as it was the only msm that worked so no it's not a problem with USB ports or drivers I had literally the same exact error and I ****ed my phone the same exact way so while there may be a extremely small chance that this fixes it it's still extremely unlikely that it will fix it
Click to expand...
Click to collapse
Kinda makes sense since the service is too. Thanks for the clarification, that the conversion guide does weird **** sometimes that makes the regular MSM not work?
I'm lucky to have the NA model which isn't as much dog ****, or just a smaller dog anyways. Seems the carrier variants suck more.