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.

OPO is Hardbrick and laptop doesnt recognize it what so ever... Please help!

Hi all,
I was in class today and put my phone in my bag. At the break when i looked at it it didnt respond to anything. I tried charging, plugging to my computer and nothing helped. I started reading online and there are a ton of guides that mainly use COLORS to recover from that situation.
My issue is that my laptops won't recognize OPO at all. I tried multiple times on both Win10 and Win7, plugging in and out, using the + button and all that. I get two errors. On the Win7 under device manager i see under Universal Serial Bus controllers - Unknown Device (with the yellow ! sign). On Win10 i see - unknown USB Device (device descriptor request failed).
I cannot even start using the color method before either computers recognize my device as HSUSB_BULK or Qualcomm HS-USB QDLoader 9008.
Please can you help? i dont know what to do next and i wasted like 6 hours today...
thanks in advance!

Ivy OPO has, a number of times, been working perfectly, had reasonable charge, and when I go to use, will not respond/wakeup. A few of these times the led was red, and plugging into power changed nothing.
I was able to get power back up normally, after holding both volume keys and pressing the power button and holding all three for about 8-15 seconds, after which the phone booted into the system.
I have no idea why it does this from time to time. Maybe 4 times now since January.

JeffDC said:
Ivy OPO has, a number of times, been working perfectly, had reasonable charge, and when I go to use, will not respond/wakeup. A few of these times the led was red, and plugging into power changed nothing.
I was able to get power back up normally, after holding both volume keys and pressing the power button and holding all three for about 8-15 seconds, after which the phone booted into the system.
I have no idea why it does this from time to time. Maybe 4 times now since January.
Click to expand...
Click to collapse
Thanks but that didnt do anything...

anyone else please?

i made some progress but now its just copying the same file over and over again:
{
"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"
}
Thoughts?

u can force the phone to boot in Qualcomm HS-USB QDLoader 9008 then flash it
i used this before for recovering
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 ( to install drivers because you know windows 10 has ****ty permission)
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 this to recover back to cm

chetan180 said:
u can force the phone to boot in Qualcomm HS-USB QDLoader 9008 then flash it
i used this before for recovering
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 ( to install drivers because you know windows 10 has ****ty permission)
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 this to recover back to cm
Click to expand...
Click to collapse
Plus that post!
It's a very very good thing you get the USB devices with the exclamation marks. On some USB3.0 ports etc it doesn't show up. Go for the windows 7 pc to recover as that was the thing that worked for me.
If you get the drivers sorted out you are in business. If it doesn't work try another USB port, preferably directly connected to the mainboard. Also take the original cable. I've had another broken cable last week, charge and sometimes data and this is something you do not want to happen during flashing
A lot of frustration and time loss, but when that is over you flash the device and you are set to go. Been there done that on the most difficult persons phone... my wife.

lukesan said:
Plus that post!
It's a very very good thing you get the USB devices with the exclamation marks. On some USB3.0 ports etc it doesn't show up. Go for the windows 7 pc to recover as that was the thing that worked for me.
If you get the drivers sorted out you are in business. If it doesn't work try another USB port, preferably directly connected to the mainboard. Also take the original cable. I've had another broken cable last week, charge and sometimes data and this is something you do not want to happen during flashing
A lot of frustration and time loss, but when that is over you flash the device and you are set to go. Been there done that on the most difficult persons phone... my wife.
Click to expand...
Click to collapse
chetan180 said:
u can force the phone to boot in Qualcomm HS-USB QDLoader 9008 then flash it
i used this before for recovering
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 ( to install drivers because you know windows 10 has ****ty permission)
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 this to recover back to cm
Click to expand...
Click to collapse
I tried this but still stuck on loop in Win10. in Win7 i get RELINK-...Qualcomm 9008 which is the modem only and not the phone itself. whenever I try to flash with the Oneplusrestore toolkit or the Mdm chinese toolkit on WIN 10, that wretched 8974_msimage_mbn just keeps on looping and looping over and over, it just disconnects and reconnect the usb. I'm already using admin rights, still the same. I followed the instructions step by step. Drivers are installed(the same drivers people who successfully unbricked their phones used).I need a solution for the loop.

[Help][xperia f3113][dead]

Hello, excuse my bad english I'm using google translate.
The problem I have is that my xperia xa is dead.
the reason of it, was that I wanted to flash the rom of my cell to remove the applications that come with the mobile company.
when I realized my error, was that I did the following, in the flash tool, in the rom selection, I made the error, not selecting the following settings:
-APPS_LOG
-DIAG
-QNOVO
-USERDATA
-CUST-RESET
as shown in the following image:
{
"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 the flash operation ended, the cell phone did not want to turn it on, the only function it had and has so far, is that it does not vibrate, it does not turn on, it does not go into flash or fastboot mode, it's dead, it just turns on the red led.
when I try to perform the flash operation again, I simply get the following message when I connect the device.
in the windows device manager, recognizes the phone as "usb serial device (com)".
I searched the net, and I did not find the solution to this problem, I appreciate your attention, and I expect some help.
PD: I already tried the connection with pc companion, and even the function from system symbol of windows with the tool fastboot to flash the boot, with the img.
the problem is that the device does not go into any mode

1990macsfull said:
Hello, excuse my bad english I'm using google translate.
The problem I have is that my xperia xa is dead.
the reason of it, was that I wanted to flash the rom of my cell to remove the applications that come with the mobile company.
when I realized my error, was that I did the following, in the flash tool, in the rom selection, I made the error, not selecting the following settings:
-APPS_LOG
-DIAG
-QNOVO
-USERDATA
-CUST-RESET
as shown in the following image:
when the flash operation ended, the cell phone did not want to turn it on, the only function it had and has so far, is that it does not vibrate, it does not turn on, it does not go into flash or fastboot mode, it's dead, it just turns on the red led.
when I try to perform the flash operation again, I simply get the following message when I connect the device.
in the windows device manager, recognizes the phone as "usb serial device (com)".
I searched the net, and I did not find the solution to this problem, I appreciate your attention, and I expect some help.
PD: I already tried the connection with pc companion, and even the function from system symbol of windows with the tool fastboot to flash the boot, with the img.
the problem is that the device does not go into any mode
Click to expand...
Click to collapse
2 times so far, my XA died the same way after trying to flash a mod. Both times I was eventually able to resurrect it by holding down various combinations of buttons while plugging and unplugging, trying different cables, etc. The second time, it wouldn't do anything until the next day, and then it suddenly came to life when using a different cable and plugging into the wall while holding power and volume down. I would try it. I'm not too familiar with flashtool on XA. I have used it for 3 years with my Z1c and never hard bricked a phone with it. Seems like X series have a little bit different rules, but I don't see why your phone would hard-brick just because you didn't wipe a few partitions... Also good idea to check in with FT thread.

If the computer does recognize it, maybe you need to reinstall your usb drivers. If its not, then u have a big problem with it, before making anything you need to see if there is a way to connect it by Fastboot, and install his custom TWRP. if u are able to do that, there is a sollution for you.
Remember always to install your usb flash drivers, and the fastboot drivers too.

Same problem my XA F3113 is dead. The LOG says everything was ok but after disconnect it from PC the phone dies.
Look like exist a way to get it back to life but we need the SCATTERED FILE.
Can somebody share us the SCATTERED FILE of this Model?

Really appreciate this guy....
Awesome person. He had recover my dead XA ultra through online. Just with 500 INR.
wrundawan said:
Whats app me +918147499618 I can help you to fix your dead phone.
Click to expand...
Click to collapse

i have a same problem
please help. my phone f3113 is dead after downgrade

wrundawan said:
Whats app me +918147499618 I can help you to fix your dead phone.
Click to expand...
Click to collapse
Be careful this guy is a cheater he cheated $30 from me

Who the hell has cheated you?
Check your paypal with your open eyes since you had raised claim on your money inside paypal your money was refunded by them. And I am helpless as I didn't got your money.
mballe francois said:
Be careful this guy is a cheater he cheated $30 from me
Click to expand...
Click to collapse

mtk scatter

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?