this is my first time asking a question here, as I just got my first android phone yesterday.
The phone is a UMI MAX. I went to reboot it today, and now its just forever showing the boot logo without starting.
I have already tried 'Recovery mode > Factory Reset > Wipe cache partition > Reboot', but that doesn't work.
I have tried flashing it back to the original ROM (from the official forums), but SP flash can't detect my phone, even after installing 'Preloader USB VCOM (Android)' driver. My phones battery cannot be removed so that may be a problem. I also disabled driver signature enforcement (I am on WIN 10)
Also, usb debugging is turned off, and I don't know how to turn it on
I just don't know what else to do
Search your mobile Drivers HERE
Kittey said:
this is my first time asking a question here, as I just got my first android phone yesterday.
The phone is a UMI MAX. I went to reboot it today, and now its just forever showing the boot logo without starting.
I have already tried 'Recovery mode > Factory Reset > Wipe cache partition > Reboot', but that doesn't work.
I have tried flashing it back to the original ROM (from the official forums), but SP flash can't detect my phone, even after installing 'Preloader USB VCOM (Android)' driver. My phones battery cannot be removed so that may be a problem. I also disabled driver signature enforcement (I am on WIN 10)
Also, usb debugging is turned off, and I don't know how to turn it on
I just don't know what else to do
Click to expand...
Click to collapse
flash official Rom From here
Related
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
A.R.Cante said:
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
Click to expand...
Click to collapse
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
abidifethi said:
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
Click to expand...
Click to collapse
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
A.R.Cante said:
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
Click to expand...
Click to collapse
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
abidifethi said:
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
Click to expand...
Click to collapse
I tried this now on my Desktop Computer and it worked fine. I didn't need to install drivers manually. It installed it by itself and therefore i was able to use odin!
I flashed the new recovery and put the omnirom and pa-gapps on my sd card (I also tried this on my notebook but my card reader is maybe broken)
so i installed teamwin recvovery over pc, put rom and gapps on my sd card and flashed them over recovery.
Now all works fine.
Thank you for your help.
But what I don't understand is my Win 7 OS (32 bit) is recently set up on my VM everything was fresh but it didnt recognized my device... Google says a lot of people are having this issues. I've tried everything whenever I found allegedly a solution for this problem. None of them worked. I simply switched the computer and everything is fine. This is ridiculous. One year ago, when I had running windows as main OS, there were no problems at all. If the problem was caused by a virtual machine I think that not many people would complain about this issue.
Kind regards
Why would old Win 7 recognize your device unless you install drivers .
JJEgan said:
Why would old Win 7 recognize your device unless you install drivers .
Click to expand...
Click to collapse
I don't really understand your comment. The Problem of this USB error has no root. When your Windows System says error code 10: device cannot start then you have a big problem because you don't know why and how to fix this. Try and Google this. You will find thousands of people complaining the same error. Everyone has other solutions for that. Some edit their registry, others simply do a soft-reset and try another USB-Port.
Samsung support can't help you at all because they don't know why this is happening. And the solving of this problem is really random. i tried for hours to solve this with no success (except switching to another computer).
Windows says on my laptop the device cannot start but it is perfectly connecting to my other computer. How can this happen? I don't know. Maybe the error code 10 is not that specific and there is something other wrong than my device.
Hi All,
I am having an issue with my S4 that when I plug them into my computer I get USB device not recognized. I have searched the forum for the past 2 days trying all kinds of different solutions the major one was changing my USB/charging port board on my phone.
I need to ODIN my device to an MJ7 image. At first I got the error and did a factory reset through safestrap recover. Still got the error so I did an advance wipe of every option. (Looking back shouldnt have done that) That took away my recovery, but I can get to download mode, but its not detected by my computer to use ODIN with. So I am stuck without a custom recovery without the ability to boot into anything.
Here is what I have tried so far:
1. Reinstall/uninstall drivers, reinstall/uninstall kies.
2. Changed USB ports on computer.
3. Changed USB cables
4. Changed computers from Win 8 x64 to Win 7 x64.
5. Changed computer to my MACbook using Heimdall.
6. Changed USB charging port board on my phone.
7. Tried everything again. *Still doesnt detect it*
Any ideas that I havent done already, or how to fix? I do have nandroid backup of my ROM, but dont have a custom recovery to flash it.
Cant ODIN back cause its not detected by my computer. Thanks in advance for your help.
Is USB debugging still checked on phone? You must use the USB cable provided with phone...
safestrap enabled, Hyperdrive driven
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
odlay75 said:
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
Click to expand...
Click to collapse
Tried Samsung Mobile phone drivers version 1.4.6.0 and still the same outcome "USB device not recognized". I went down to a local electronics store and bought two different brand microUSB data cables. Tried them both along with my original one from samsung, and still the same result. Any other ideas??
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
odlay75 said:
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
Click to expand...
Click to collapse
Go to Saferoot thread in dev forum...your answer may be there
safestrap enabled, Hyperdrive driven
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
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?
My Zenfone 4 Selfie(ZD553KL) is bootlooped, doesn't starts after the zenfone logo (restarts). I've tried adb sideload (it worked normally) the latest firmware, wiping all data including cache and nothing happenned. Asus FlashTool didn't recognize the smartphone in CSC fastboot mode. I guess it was because my USB debugging probably wasn't active. What can I do?
Firmware: 15.0400.1903.508
Not Rooted.
No Custom Recovery.
No OEM
EDIT: I managed to start the phone, but it keeps restarting a lot before proper start of the android (10min restarting until it starts). I've activated USB debbuging now, but still want to solve this.