[Q] Zopo 9520 Usb driver, recovery problem - Android Q&A, Help & Troubleshooting

Hello!
I can't install USB driver, and also can't get into recovery. Phone is working, but... When I connect the phone to computer the device manager shows nothing. With battery plugged in it shows 9520, but that is not helpfull in any way... Also when I'm trying to get into recovery mode, it's showing the loading android and after few seconds there is android laying with a red triangle with exclamation mark in it. I have flashed the official ROM with SP Flashtool but nothing changed. Is there any possibility to install the driver manually, not through the device manager? And how do I get the recovery to work again?

Related

[Q] MOTOROLA XT615 MOTOLUX flashing help needed

I have a problem with my xt615,
it started out with the bootloop problem.
after that i managed to get into flash mode (redscreen) installed the pc drivers
and tried to flash 2-3 different stock roms, and a recovery via RSD LITE version 6.
at the beginning the phone was recognized as a zeus flash device, but i changed that driver to a motorola usb device.
somehow i manage to get the phone connected in the FLASH MSM7227 but still no program can recognize it so i can flash...
since i tried to flash the recovery i cannot enter the Flash mode (red screen) and earlier, when i was trying to turn on the devices from 50power attempts 2 times it was the moto bootloop logo...
now i cannot do that...
any suggestions how to get this device flashed!?or get it into flash mode?!
all the time its blackscreen and as i enter the usb it connects to the pc depends on which mode...when i hold the powerbutton and connect it it will connect as flash device msm7227 but still...i cannot do anything via RSD LITE , also tried via adb to get it recognized. but no luck...
Help desperatly needed

[Q] Help flashing Alcatel C7 that boots automatically when plugging the USB

Hello,
During the past days I've been trying to flash my C7 with no success. When pressing power button, it turns on and displays the Alcatel logo but stays there, it does not load the OS.
I have tried to use SPtools to flash it, I have the mtk drivers installed in my PC. When I plug the switched-off phone to the computer it turns on and couple seconds after my PC detects it (I can see the preloader mtk loaded on the device manager); however, one second right after it is detected, it is disconnected as it keeps booting to show the logo and stay there. Obviously, if the phone is not detected I cannot use SPtools to flash it.
Any suggestion will be highly appreciated.
PS: I have also tried to connect to it with adb, and dump a ROM using sideload with no sucess, the PC recognizes it from the recovery but after copying the image nothing new happens on reboot.

Homtom HT3 stuck on boot logo

Hi guys, I recently purchased a Homtom HT3 for my mother, when it arrived to me I charged it and checked it out a bit just to make sure everything was fine which it was.
She collected it from me the next day and told me she'd start to use it the day after, she calls me up the next day and tells me there's some problems with it and a few people at her workplace tried to fix it for her to no avail. I pick the phone back up and I notice that everytime I power it on, it gets stuck on the "homtom" logo.
As I don't know too much about fixing phones I only took the following steps before asking for advice here; I went into recovery mode by holding up volume and power button, the android guy with the red triangle appeared so I tapped up + power button to get into the recovery(?) menu. I wiped the phone to factory settings and deleted the cache in there but it hasn't fixed the problem.
I assume I need to flash a firmware or something to potentially fix this, but I'm unable to find an official firmware from doogee/homtom's site for the HT3. I've found a firmware that I downloaded from "chinagadgetsreviews" but I'm a bit weary to try and flash with that rom because it isn't from the manufacturer. (even if I knew how to - the only experience I have is rooting my own phone but that's when I actually had access to a working phone, not one thats stuck on a boot logo).
Sorry for the long post but could anyone guide me in the right direction here? TIA
I'm not opposed to not using official firmware, I think I use cyanogen mod(?) on my own phone. I'd just like the problem fixed in the easiest way possible.
Trying to fix it myself by flashing a rom via SP flash tools but I've ran into another problem which is stopping any kind of progress - the phone isn't detected in Windows, I can't enable usb debugging because I can't get passed the boot loop, I've tried installing the ADB driver manually which didn't seem to work (just said it didn't install correctly and left me with a yellow exclamation mark) and I tried to install it automatically via ADB driver installer but it just throws up an error that the device isn't detected.
Any help would be greatly appreciated.
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Same here - any solution for this problem?
Kleos89 said:
Hello. I bought a Homtom HT3 and next day a done an update with sp flash tool. all gone ok, but phone now wont to turn on. I contact homtom and got all drivers and room to fix it. Now i have a problem , i hit download on flash tool , take off battery + pres volume down + conect phone on usb cable. My computer detect it as USB MTK PORT sp flash tool load only the first red line but not detecting phone info, then after 1 minute i get
s_ft_da_no_response(4001) da didn't send response data to flash tool.
I changed drivers port even to MTK preloader, but i get same error.
NOTE....... All drivers and rom i got original from HOMTOM.
Thanks to all who can help me.
I can show a screenshot if need.
Click to expand...
Click to collapse

Hisense c20 bricked after root.

Hello all.
I have hit a problem with my Hisense c20. I rooted using kingoroot and everything seemed to work fine. SuperUser was installed and working as it should. The phone then ran flat so I plugged it in and booted but it just hung on the SMART powered by android screen. So I restarted again into recovery mode and cleared system cache. Rebooted again but same thing. So tried again but with the wipe user data option. Still just hangs there. I then decided to try flash a stock rom via needrom. I followed the instructions but cannot seem to get the phone to be visible as a com port on Windows 7 64 bit. I have tried different cables and USB ports and reinstalled drivers countless times. Please could anyone assist me on getting this phone to be seen as a com port so I can flash it with QFIL.
Kind regards
Ryan
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Need a file *qcn. or backup NV backup ?
Who has the opportunity to give?
[email protected]
[email protected]
RuanRex said:
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Click to expand...
Click to collapse
Hi Ruan. You haven't found a custom recovery?

Need help with softbrick!

Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.

Categories

Resources