I was trying to upgrade my device and then my PC stop working and reboot. Now My Qtek 2020 is showing Serial v1.02 (if not in cradle) and USB v1.02 (if in cradle) and I cannot perform an upgrade because HimaUpgradeUt doesn't detect the device. How can I revert this situation, is it possible?
More info needed:
Did you already begin to update your QteK? Did your PC say "updating" with a red progress bar and a percentage amount? If so, I think you would need to try and get that cable working again. Perhaps redownload the ROM (the installer may have become corrupted) and make sure that ActiveSync is switched OFF. Perhaps even reinstall ActiveSync if nothing else works. THe cable may also not be getting enough power. Try plugging it into the USB on the back of your computer if it is plugged into a USB Bus or the front USB port. THe back port will give you the most power. Also, make sure it is plugged in to the AC adapter while you upgrade just to make sure your phone doesn't go flat.
If you had not started upgrading it, try reseting your phone using the reset button with the stylus.
unbrick xda II
Hi, I've got the same issue................
Any hope?????????????
Related
From a noobie:
Question 1: My original problem is on soft reset my HTC xv6800 hangs at tricolor with "Serial" at the bottom of screen unless the usb cable is plugged in. It will boot to wm6.1 if I plug in the usb cable at soft reset. Then I get no USB connections in WM61, and my PC does not detect the phone at all at the usb port. I'm stuck with inability to do any sync on the phone.
I am hoping if I install a newer radio ROM it might fix the hang at tricolor with Serial, and usb connection problem. Is this reasonable or do these symptoms indicate something more grave?
Can you recommend any next steps?
Have you tried relocking the phone and flashing back to stock rom? Once you have it back to stock, see if it boots normal. If it does, go thru the steps flashing it back to custom and see if the problem comes back.
BTC
Since I've had the same stock OS ROM and verizon authorized radio ROM for several months, I assumed the ROMs were not the problem. The problem just began last week or so. What I have done is installed neuSPL2.47 wnd reflashed radio ROM and flashed TitanReloaded1.3.2.
I've checked the cable using a different device and it gets recognized by WinXP. I am now syncing with Activesync in bluetooth, and I've flashed both the OS and radio ROMs... With these steps above, is it apparent or feasible that I have a hardware usb issue on the phone?
The only issues I have are that I cannot power up the phone without a usb cable in the phone - it goes to bootloader without the cable plugged in, and I must sync via bluetooth, which is not a huge issue unless I really want to use usb for connection to PC.
Do you still think the ROMs could be the culprit?
Any ideas on why it would go to bootloader with "Serial" at the bottom unless an active usb cables is plugged in? Does anuyone know what the "Serial" message means?
What happens if you plug in the USB cable after the bootloader comes up, does it change to USB or does it keep saying serial.
It does sound like maybe your USB port is bad, if you get it booted up normally, does it see activesync in windows, does your headset work, etc?
Basically, if you use the cable trick to get it to boot, does the USB port seem completely normal then?
BTC
Flash it using your microsd
BillThyCat said:
What happens if you plug in the USB cable after the bootloader comes up, does it change to USB or does it keep saying serial.
It does sound like maybe your USB port is bad, if you get it booted up normally, does it see activesync in windows, does your headset work, etc?
Basically, if you use the cable trick to get it to boot, does the USB port seem completely normal then?
BTC
Click to expand...
Click to collapse
The port seems dead after bootup, once it gets past the bootloader. It never says USB in the bootloader. Should I see that if USB is confirmed functional? What does "Serial" mean? Activesync does not see the Titan whatsoever when using USB connection after it boots. I sometimes get an error popup at the taskbar in WinXP Pro that says the usb device has a problem...
Hi guys.
I am hoping to get some help. I flashed a custom rom about 3 weeks ago from my favourite chef as there was a newer version released. After flashing said Rom I could no longer connect my phone via USB to PC. I would get a message on PC saying USB device not recognised or failed. Tried uninstalled Device centre, different USB and PC, but nothing, still the same error. So after all that tried hard reset and Task29. I then copyied the previously used Rom to my SDcard and installed from HSPL bootloader, but still the same.
I have noticed over the last week or so, that when using WinMo instead of Android, my battery will last 3-4 hours from a full charge, with Android I get 7-8 if I am lucky.
The last problem I have is when using WinMo and I want to lock the screen, it will lock and then come back on within 1 seconds time.
Can anyone help?
Thanx
Seg
P.S: I am not blaming the Chef of the ROM for this.
Here's what I would do:
1) run task29 (SD)
2) flash 2.15.50 radio
3) Flash a ROM you KNOW works (NRG, dutty, etc...) from SD
4) Hard-reset right after flash
try to hook up your USB and see if it works.
Go into Bootloader Mode and only then connect the USB cable. Does the 'Serial' change to 'USB'?
Have you tried another USB cable?
Have you tried connecting the USB calbe to the rear USB sockets on the computer?
fred_up Go into Bootloader Mode and only then connect the USB cable. Does the 'Serial' change to 'USB'?
Have you tried another USB cable?
Have you tried connecting the USB calbe to the rear USB sockets on the computer?
I have tried all this Fred, to no avail. Different cable, different usb sockets, different pc. Still nothing.
Bootloader mode doesn't change connection type when connected.
orangekid said:
Here's what I would do:
1) run task29 (SD)
2) flash 2.15.50 radio
3) Flash a ROM you KNOW works (NRG, dutty, etc...) from SD
4) Hard-reset right after flash
try to hook up your USB and see if it works.
Click to expand...
Click to collapse
Tried all this previously mate, and still nothing. Trying again with a different ROM. I'll post back results.
Thanx guys
Seg
Still no joy, tried just about everything now.
The only way the screen will stay off is when it is plugged into charger, other than that it just dims after 10 seconds then brightens back up after 2 seconds.
Looks like the insurance will be gettinga call then.
Damn, this means I will have to use the spare Blackbery Curve we have, gutted.
Seg
Hi all... i got my V for a month and now it is not charging anymore. neither from the ac adapter nor my computer usb..and my computer couldnt detect my phone is plug to the USB port....just nothing pops out. The debugging mode status icon, and the storage icon is not shown on my phone.
basically... i tried everything i found on Google...
reboot my phone, pop out the battery, change cable[from other optimus V], changed battery, different ports on my computer, different computer, different AC adapter, different SD card, format my SD card, factory reset, and the last thing i tried is to rooted my phone and flash with a I.H.O CM7.1 ROM.
no hope at all; however, when i plugged to the usb port or the ac adapter, then i take out the battery.. the phone does power up and say required battery....
so, if anyone had this problem before and solved it.. please help me out. between, i cant return the phone anymore.. it is over a month.
forgot to mention... it is the second time this charging issue happened. the first time, it fixed itself after i plugged into the PC, windows recognized it, and installed the drivers. [well, i already installed the driver before this happened, because i was doing some coding and debugging]
this time.... windows is doing nothing, no message pop out, no new driver found.. just nothing. and my phone doesn't shows the debugging icon on the status bar even thought i ticked the debugged mode On, and connected to the usb.
sorry for my bad grammar =[
maybe see if your pc recognizes it while rebooted into recovery.
you could also try removing all the lg and Android drivers in device manager (select show hidden devices to get at them) and then plugging the phone into the pc again.
or use a Ubuntu "live cd" to check the connectability... micro$oftware is uppity, my kid's windoze computer doesn't like my v, although it used to see it fine.
I've also read that toggling debugging, disconnecting and reconnecting the cable, then toggling usb debugging again can help.
also, froyo roms are supposed to go to a charge mode when turned off but still plugged in.
I have been running on Cooks I777UCMD8 rom for about 2 months now and have had multiple powering issues. Have tried all the basic trouble shooting, not sure if its the Rom causing the issues or the AJK noswap Kernel, but nothing has been tweaked, running as is. The booting issue is when connecting a USB cable while the phone is powered off, if you try to turn the phone on while the USB cable is still attached you get a POWER RESET OR UNKNOWN UPLOAD MODE error message, only way to avoid it is to remove the usb cable and hold power button then it powers up normally.
now the problem with the USB cable, and i feel these two are possibly related, my phone no longer recognizes when its attached to a computer usb hub, it charges, but dose not enter into mass storage mode, nor does the computer recognize that the phone is attached, i have tried on multiple computers with same results, and yes all drivers are downloaded on computers. Further information; Before this problem began accruing, I would get error messages after attaching the phone to a pc VIA usb cable saying ( ONE OF THE USB DEVICES ATTACHED TO THIS COMPUTER HAVE MALFUNCTIONED, AND WINDOWS DOES NOT RECOGNIZE IT ) also, after plugging in the usb cable and windows attempted to download the drivers this error also appeared ( DEVICE SOFTWARE WAS NOT SUCCESSFULLY INSTALLED, CONSULT WITH YOUR DEVICE MANUFACTURER FOR ASSISTANCE ) it later resolved itself for a short time ( couple days ) but now when i connect the phone, nothing happens... i'm hoping somebody has had similar USB problems after flashing a new rom and knows whats going on.
additional information:
- i have two Galaxy S2 phones both running cooks-i777ucmd8 rom and both phones have had the exact same issues.
- previous problems also include boot looping, and frozen lock screen upon powering up the phone. has not happen in a while.
Hi, I have the Chinese smartphone Uhappy UP920, android kitkat.
I tried to root my phone with kingoroot and all other root software before one week, without success, kingo always said "connection with servers failed, try again", I tried it two days from different libraries & I tried some software for upgrade, just to see if it is possible to upgrade to the android 5 & 6, the upgrade was refused because developer didn't make such possibility.
I don't remember from all this software if I used any software for flashing device, but here is the problem:
in one moment after trying all these software, I saw that phone battery dropped from 10% to 1% and the USB cable didn't work any more, I tried OTG cable also but the phone didn't recognize my USB device, when battery was gone/spent, I tried to use USB cable to charge the phone with my computer, but no success. I don't have ac adapter (charger), I think it would not work in any case because OTG cable is not working, not only USB cable.
battery is gone, I can't charge it with USB cable, I tried to make restart with "down volume button" and "home button", but it didn't work.
when I press Power On button, display become something like blue for a second and it is dark again. I can't start the phone.
my theory is that some software destroyed possibility for android kitkat to recognize smartphone microUSB port (for USB cable, you can see that port on the photo: https://img.fasttechcdn.com/231/2314500/2314500-9.jpg). So, maybe it is software problem, maybe hardware problem...
anyone had similar problem? anyone has a solution?
p.s. before battery was gone, USB debugging option was checked, that's requirement when I tried to root the phone, in theory I could try ADB to do something with the phone, but I don't know how to use ADB, I tried to list devices but I got everything black in the terminal, I didn't get listed my device. if you recommend ADB, please tell me what commands to use.