Database Info

Photon Q not recognized by RSD lite in fastboot

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.

FASTBOOT problem

Running Windows 7 Home premium 64 bit
just upgraded from a Windows XP system to this, and now i cant get fastboot to work. ADB works no problem, but when i run fastboot devices, it doesnt do anything and goes back to having me type in a command
i.e
c:\dev\sdk\sdk\platform-tools>fastboot devices
c:\dev\sdk\sdk\platform-tools>
ive googled beyond belief, ive tried everything from the sdk to wugfresh toolkit and cannot for the life of me get it to work. Any ideas?

skeliton lord said:
Running Windows 7 Home premium 64 bit
just upgraded from a Windows XP system to this, and now i cant get fastboot to work. ADB works no problem, but when i run fastboot devices, it doesnt do anything and goes back to having me type in a command
i.e
c:\dev\sdk\sdk\platform-tools>fastboot devices
c:\dev\sdk\sdk\platform-tools>
ive googled beyond belief, ive tried everything from the sdk to wugfresh toolkit and cannot for the life of me get it to work. Any ideas?
Click to expand...
Click to collapse
This happened to me actually, and it turns out that I didn't hit "Allow" (or something to that effect) on the prompt while it's connected. It took me awhile to see that I'm not sure if that's your issue as well, though.

Remove all existing device drivers and the device itself from device manager then go to general > sticky thread and follow the adb and fastboot thread to install everything properly
Sent from my Nexus 5 using Tapatalk

rootSU said:
Remove all existing device drivers and the device itself from device manager then go to general > sticky thread and follow the adb and fastboot thread to install everything properly
I've done that as well and it still won't allow fastboot to work
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
MHousos said:
This happened to me actually, and it turns out that I didn't hit "Allow" (or something to that effect) on the prompt while it's connected. It took me awhile to see that I'm not sure if that's your issue as well, though.
Click to expand...
Click to collapse
I believe the prompt you are talking about is for 'ADB' since fastboot does not give you a prompt

I'm not talking about any prompts.
Sent from my Nexus 5 using Tapatalk

It's the USB Debugging prompt that comes up on the device. Looks like 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"
}
Sent from my Nexus 5 using XDA Free mobile app

MHousos said:
It's the USB Debugging prompt that comes up on the device. Looks like this
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
As the other guy said, that's for USB debugging which is an android only setting. . Only ADB works in android so this isnt relevant
Sent from my Nexus 5 using Tapatalk

Now that you mention it, that's correct. In that case, starting from scratch would probably be best, in my opinion.
Sent from my Nexus 5 using XDA Free mobile app

MHousos said:
Now that you mention it, that's correct. In that case, starting from scratch would probably be best, in my opinion.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I agree with that.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Yeah I agree with that.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
For some reason it didn't post my other part of the response where I said 'I tried the sticky and deleting all my drivers under the device manager and still a no go'
Not sure why it didn't post, apologies
Edit: actually it did post it, if you look at the quote for some reason it but it in the gray box
-_-

skeliton lord said:
For some reason it didn't post my other part of the response where I said 'I tried the sticky and deleting all my drivers under the device manager and still a no go'
Not sure why it didn't post, apologies
Edit: actually it did post it, if you look at the quote for some reason it but it in the gray box
-_-
Click to expand...
Click to collapse
Oh you wrote it in my quote.
Well once you've deleted the drivers (that's delete device AND drivers, not just device), ran the 15 minute adb and fastboot installed and reinstalled the naked USB driver. Come back to us with whatever errors you're getting now.
Don't forget to be in the bootloader when you do all that.
Sent from my Nexus 5 using Tapatalk

Tried and fastboot still does the same thing
It installs as 'android boot loader interface'
Here's a serious question, do the USB ports matter for fastboot? I have all USB 3.0 on my computer now
@rootSU

skeliton lord said:
Tried and fastboot still does the same thing
It installs as 'android boot loader interface'
Here's a serious question, do the USB ports matter for fastboot? I have all USB 3.0 on my computer now
@rootSU
Click to expand...
Click to collapse
You're really not giving me the feedback I require to help you so this is becoming difficult.
I do assume you know you MUST be booted into the bootloader for fastboot and fastboot drivers to work. please confirm you understand this.
Yes the port matters as does the cable. It must not be faulty, try changing it.
Are you following the links in my "adb and fastboot. what is it?" thread?
I am going to update it slightly, to make it more obvious.
Here is the thread:
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Please go through the install section fully. Ensure you do remove existing drivers as suggested. Your device should show up as "Google Nexus 4 bootloader interface" is you have installed drivers correctly AND you are booted into the bootloader.
If your drivers show as correct after this, please visit the troubleshooting connections thread that is also linked in my above thread.

rootSU said:
You're really not giving me the feedback I require to help you so this is becoming difficult.
I do assume you know you MUST be booted into the bootloader for fastboot and fastboot drivers to work. please confirm you understand this.
Yes the port matters as does the cable. It must not be faulty, try changing it.
Are you following the links in my "adb and fastboot. what is it?" thread?
I am going to update it slightly, to make it more obvious.
Here is the thread:
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Please go through the install section fully. Ensure you do remove existing drivers as suggested. Your device should show up as "Google Nexus 4 bootloader interface" is you have installed drivers correctly AND you are booted into the bootloader.
If your drivers show as correct after this, please visit the troubleshooting connections thread that is also linked in my above thread.
Click to expand...
Click to collapse
I followed the exact thread that you provided, I deleted every and all devices and drives related to google or android, I then rebooted the computer, installed the drivers and adb is still working just fine, but when I boot my phone into boot loader mode, it does not work, when I type in 'fastboot devices' it does not show me the words 'list of attached devices' like it normally would regardless if I was in boot loader mode or not, BC if I wasn't a device just wouldn't show up
Like I said, I had all of this working on my windows XP computer but cannot for the life of me vet the fastboot commands to work at all on windows 7. And just for trial and error purposed, I use virtual box to boot into ubunutu and build Roms, and fastboot DOES work in Ubuntu but it does NOT work in windows 7

Then I already told you what thread to read next. Good luck
By the way, "adb devices" shows "list of attached dwvices", even if no devices connected but does not list a device. "Fastboot devices" lists a BLANK line if no devices is connected, as you can clearly see from my thread
Just trying to prevent you chasing a red herring. The fact fastboot doesn't say "list of attached devices" is entirely normal. The only issue is it doesn't see your device attached. Change ports, change cables, but its probably your windows OS at fault. Read the troubleshooting thread
Sent from my Nexus 5 using Tapatalk

I think I killed my brand new phone

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

[REQ] Unihertz Titan Stuck in Bootloop

Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif&notif_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&notif_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?

Need help with hard bricked oneplus 8T

Hi everyone,
So, I just picked up a oneplus 8T, unlocked the bootloader, loaded TWRP, backed up my stock rom, and attempted to flash the vanilla version of the arrow rom. Everything was fine until TWRP said that something in the flash failed towrds the end of the flashing. I went back into TWRP, tried to wipe everything except internal storage and try again. The wipe also said that it failed. When I clicked reboot in TWRP, it got stuck in a soft boot loop.
I got the phone to boot back into recovery mode, and used the platform tools to get it back into fastboot. Somehow, I lost the stock recovery that I stored on the internal storage. I found this link, which had a one-click flash-all to bring an 8T back to stock OS.
Unbrick OnePlus 8T from a Hard-Bricked State using MSMDownload Tool
A complete guide on how to unbrick the OnePlus 8T from a hard-bricked state using the MSMDownload Tool and restore stock OxygenOS software.
www.thecustomdroid.com
My 8T is an unlocked carrier version, so I chose the global version labeled kebab_15_O.12_201110.zip
Once I unzipped it and clicked the flash all exe, it opened a terminal window, connected to the phone, and seemed to be flashing properly. When it finished, the phone rebooted, but never really rebooted. It is stuck on a black screen, which I believe is EDL mode.
The only sign of life now is when plugging in the USB cable, I can see the phone in device manager under OTHER DEVICES and it is labeled QUSB_BULK_CID:0412. I found another thread which explained this means the USB driver has been corrupted. I downloaded and tried to install the qualcomm drivers from this link
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
but the installation fails right at the end 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"
}
Is there any way to unbrick this oneplus 8T, or did I just destroy it forever? I really feel like it should be able to be reflashed and fixed, I just can't figure it out. My next step today is going to be to call oneplus support, explain the situation, and hopefully they have some sort of insight for me, or at least a tool to get the proper USB drivers back into the phone so that I can access fastboot again.
Any help you guys could give me would be greatly appreciated.
-Vr4Mike

vr4mike said:
Hi everyone,
So, I just picked up a oneplus 8T, unlocked the bootloader, loaded TWRP, backed up my stock rom, and attempted to flash the vanilla version of the arrow rom. Everything was fine until TWRP said that something in the flash failed towrds the end of the flashing. I went back into TWRP, tried to wipe everything except internal storage and try again. The wipe also said that it failed. When I clicked reboot in TWRP, it got stuck in a soft boot loop.
I got the phone to boot back into recovery mode, and used the platform tools to get it back into fastboot. Somehow, I lost the stock recovery that I stored on the internal storage. I found this link, which had a one-click flash-all to bring an 8T back to stock OS.
Unbrick OnePlus 8T from a Hard-Bricked State using MSMDownload Tool
A complete guide on how to unbrick the OnePlus 8T from a hard-bricked state using the MSMDownload Tool and restore stock OxygenOS software.
www.thecustomdroid.com
My 8T is an unlocked carrier version, so I chose the global version labeled kebab_15_O.12_201110.zip
Once I unzipped it and clicked the flash all exe, it opened a terminal window, connected to the phone, and seemed to be flashing properly. When it finished, the phone rebooted, but never really rebooted. It is stuck on a black screen, which I believe is EDL mode.
The only sign of life now is when plugging in the USB cable, I can see the phone in device manager under OTHER DEVICES and it is labeled QUSB_BULK_CID:0412. I found another thread which explained this means the USB driver has been corrupted. I downloaded and tried to install the qualcomm drivers from this link
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
but the installation fails right at the end saying View attachment 5563423
Is there any way to unbrick this oneplus 8T, or did I just destroy it forever? I really feel like it should be able to be reflashed and fixed, I just can't figure it out. My next step today is going to be to call oneplus support, explain the situation, and hopefully they have some sort of insight for me, or at least a tool to get the proper USB drivers back into the phone so that I can access fastboot again.
Any help you guys could give me would be greatly appreciated.
-Vr4Mike
Click to expand...
Click to collapse
Fun Fact: THIS IS NOT WHERE YOU POST STUFF LIKE THIS this szection is for ROMS kernels and recoveries

GbnrVR said:
Fun Fact: THIS IS NOT WHERE YOU POST STUFF LIKE THIS this szection is for ROMS kernels and recoveries
Click to expand...
Click to collapse
well I tried to install a rom from this section, and need some form of recovery, so I figured the people here would likely be able to help. I will gladly post in another section if I have to...

Hey, ah, I assume it is done yet recommend disabling DSE (Driver Signature Enforcement) in Windows & then install the driver.
To do so, open CMD with admin privilege > type: bcdedit /set TESTSIGNING OFF and then try installing the driver. Because drivers don't usually failed to install or run properly. I understand the severity of the device's condition and also I'm glad you chose not giving up that's great, again I'll say install proper drivers after disabling DSE and then flash the original stock software. If it boots in EDL means its recoverable. Happened with me many times but the device was of different vendor/oem. Great luck.

psi.singh03 said:
Hey, ah, I assume it is done yet recommend disabling DSE (Driver Signature Enforcement) in Windows & then install the driver.
To do so, open CMD with admin privilege > type: bcdedit /set TESTSIGNING OFF and then try installing the driver. Because drivers don't usually failed to install or run properly. I understand the severity of the device's condition and also I'm glad you chose not giving up that's great, again I'll say install proper drivers after disabling DSE and then flash the original stock software. If it boots in EDL means its recoverable. Happened with me many times but the device was of different vendor/oem. Great luck.
Click to expand...
Click to collapse
I just searched qualcomm hs-usb, and found a download for the computer. After installing it, I rebooted my computer, and device installer now finds the phone listed as Qualcomm HS-USB QDLoader 9008 and assigned it to COM3. I have not had luck yet finding a working version of the MSM Download Tool. Every version I find and download says "packed image does not exist"

Can somebody give me the msm download tool? I have downloaded 4.0 from a few places and can not get it to work. Most downloads say package does not exist as the above screenshot shows. Others seem to work, and give a message that msm tool is running, but no windows ever pop up to log in or anything.
Am I doing something wrong trying to use the tool?

Try with this
MsmDownload_Tool_v5.0.15
MsmDownload_Tool_v5.0.15.zip - Devdrive - File Hosting For Publishers
Download file - MsmDownload_Tool_v5.0.15.zip
cutt.ly

mortazanabin said:
Try with this
MsmDownload_Tool_v5.0.15
MsmDownload_Tool_v5.0.15.zip - Devdrive - File Hosting For Publishers
Download file - MsmDownload_Tool_v5.0.15.zip
cutt.ly
Click to expand...
Click to collapse
Same thing. I keep getting this message when I try to open it. I tried double clicking the exe and also tried right click/run as administrator. Both give the same result.

try this patched version...
6T_MsmDownloadTool_v4.0.58_patched.rar | by OvrDriVE for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if antivirus detected as virus then turn it off....

mortazanabin said:
try this patched version...
6T_MsmDownloadTool_v4.0.58_patched.rar | by OvrDriVE for OnePlus 6T
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
if antivirus detected as virus then turn it off....
Click to expand...
Click to collapse
It did not detect as a virus, but how do I run/install a .rar file?

Are you able to get into fastboot? Did you check fastboot devices command and see your device listed? Then let me know there are ways to restore

kirankowshik said:
Are you able to get into fastboot? Did you check fastboot devices command and see your device listed? Then let me know there are ways to restore
Click to expand...
Click to collapse
I can not get into fastboot. I believe the phone is stuck in EDL mode. I have gotten MSM Download tool to open, but it will not flash to device. The tool knows that my phone is connected to COM3, but the MSM tool says waiting for device after clicking start, and never goes any further.
If anyone has experience with the MSM Downloading Tool and can help out, please chime in.
Thanks for the help everyone. I'm slowly getting there.

So, I noticed the caution label on the device in device installer...which usually indicates a driver problem. I reinstalled the qualcomm driver, and it says that it is installed properly. Is there an updated driver or something that I am missing?

try this method...
i thik this will help you to unbrick your device...

mortazanabin said:
try this method...
i thik this will help you to unbrick your device...
Click to expand...
Click to collapse
I can follow that exactly. The problem comes down to when connecting to USB cable and pressing start, the tool always says waiting for device, as if my device is not in EDL mode. I really think the issue is coming down to drivers for the phone to communicate with the tool. I do not think there should not be a caution symbol in device installer (as noted above) when the driver is properly installed. (even tho windows says I have the latest qualcomm driver for the device)
Does anyone have an updated driver in case I have an incorrect version? I am using the below. It says from 2014, so Im not sure that it is the correct driver. I got the link from a oneplus 8T post somewhere. I do not recall exactly which post it was.

your windows version? windows 10 or 11?

mortazanabin said:
your windows version? windows 10 or 11?
Click to expand...
Click to collapse
windows 10
I uninstalled and tried reinstalling the drivers, and now I can't get any of them to install. Device installer is back to saying QUSB_BULK for the device.

Disable windows dirver signature enforcement check
=========
Try this driver
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
=========
Try this msm tool
QDLoader HS-USB Driver_64bit_Setup.zip
drive.google.com
thanks me later if successful....

vr4mike said:
So, I noticed the caution label on the device in device installer...which usually indicates a driver problem. I reinstalled the qualcomm driver, and it says that it is installed properly. Is there an updated driver or something that I am missing?
View attachment 5563605
Click to expand...
Click to collapse
You have a yellow triangle there disable the driver signature in windows the MSN tool should be work properly

I got it to work!!!!
It was the driver signature enforcement.
However, that was not the only issue. After disabling the signature enforement, it was connecting to the device, but still not working. The stsus in the configuration panel started to connect, but then failed in red. I tried it a few times with the same result. I tried holding the 2 volume buttons while plugging in the USB, that didn't change anything either.
What ended up working was holding all 3 buttons while the tool was connected. It caused the device to momentarily disconnect and reconnect to the USB (via disappearing and reappearing in device installer, as well as the laptop making the disconnected and connected sounds) As soon as it reconnected and the laptop made the sound, the tool instantly started transmitting data and functioning.
My phone boots up as it did stock now, and does not even tell me that the bootloader is locked anymore upon first power up. It is 100% functioning just as it came out of the box!!!
I CAN NOT THANK THIS FORUM ENOUGH!!!!!
I have been using information here for years since I rooted my first Galaxy S3. This is the first time I have had to make an account and post.
You guys are the best, and were my only saving grace. Oneplus doesn't even have a working phone number anymore. All support must go thru email.
THANK YOU ALL SO MUCH!!!
I hope this information helps somebody else.