Database Users

[Q] USB only working on bootloader ?

Hi all.
First of all, Win7, 32bit.
Second, I must be doing something really stupid ... here goes:
I'm trying to upgrade my Qtek S200 (AKA HTC Prophet) G4.
I've tried the Prophet_Upgrade_2.6.5 (that I got from this forum), following the instructions from thread 534707 (can't paste links yet ..)
But... the tool gives me an error ( Warning: no device connected. Waiting for a device to connect...), so I figured out I did something wrong and decided to start again from scratch, but this time I would hardSPL the thing first, using the "Upgrade_SPL_G4" batch that I found somewhere in this forum.
That's when I discovered that Win7 doesn't recognize the phone anymore: when I connect it to the USB port, windows doesn't even "beep" and there's no device on the device manager. BUT. If I start the phone in bootloader mode, windows DOES recognize it ...
I've already hard-reset the phone, done a system restore on windows to a previous date, the works ... but windows still refuses to "see" the phone after it booted normally ...
Any hints ?
./J

install proper drivers for win7/vista first.
Read Prophet Upgrade thread or Claudyfa thread about installing drivers...

what condition of your phone now...?!
if it's entering 3 color screen when booting, better find XP PC n' use nvid rom to back to wm5 first.
then update in Win7/Win Vista with driver installed (like bikertibi told)

@Bikertibi: The question is "what" proper drivers if when I plug the phone via USB on it's "normal" condition (working) it isn't recognized by windows, not even as an "unknown device" ?
The only way to make it "appear" under the windows device manager is booting the phone into the "bootloader" (3 color screen) mode ... and even in that situation, windows tells me it has the latest drivers...
I've even tried to uninstall and reinstall "Windows Mobile Device Center" (that carries some 'new' drivers with it) with no success ...
@hd.herlambang: phone is working ok. I can boot it normally, I can hard and soft reset it and I can boot it into the "bootloader" mode, but when booting it normally it is NOT recognized by windows, not even as an "unknown device". As I've said earlier, it's only visible to windows when booted into the "bootloader" mode.
./J

***bump*** ?

I have the exact same problem with my HD2. I've asked HTC, but they haven't given me an answer so far...

Help!! My L7 is not working,black screen, no charges, QHSUSB_DLOAD what to do?

So I have bought a L7 and when I have it the phone is not working, the seller doesnt want to take my money back so I need help with this :S!
No appears to do anything when connected to charger
No led
No vibrates
No emergency mode
When I connect it to my PC it recognizes it as QHSUSB_DLOAD, but neither KDZ or LG update program recognize it :S!!
Someone know how to reinstall OS I think is software issue but I dont know how fix it
Thanks!

Try following the instruction I got from a website.
What is 'qhsusb_dolad' ?It is the situation when you can't boot into your phone,recovery mode and any other visible interface. When you connected your phone to the PC, the LED will flash and your PC will show that they were searching for the drivers needed(win7/8) but they couldn't find .......If it is commom for you to remove the battery when the phone did not shutdown completely or when you ran into 'No-Response' , as time goes by ,it will be inevitable that you come across the 'QHSUSB_DLOAD' situation .
But from now on ,you needn't worry about that for I have found a way out.
Tools needed:
Hardware: A PC running XP and higher (win7/8 recommended) and your usb cable
Software : MIflash and MIAssistent and a certain mi update rom(It is a *.exe file---fastboot file)
Steps :
1. Install the first two softwares described above(Run as administrator) in your PC (You need to disable the enforcement of digital signature while on win8 in the advanced startup (press 7 or F7)
2.Boot into fastboot mode(you just need to do with your two buttons and usually you cann't see the interface for your screen just won't show in this situation) before connecting to PC
3.Connect you MI2/S to your PC via the usb cable and the pc will recongnise it in the device manager panel(if not, update its driver in the unknown device---qhsusb_dload)
4.Open the miflash and click fresh to load your phone's serial number
5.Flash the update rom(the self-extracted-to folder) into your phone and reboot .
Explanations:
Miassistant contains the 'qhsusb_dload' driver for any phone and it enables the PC(Miflash) to recongnise your CPU serial which is the key part of updating by wire.
Tips:
Try this with your other phone, I believe it will work ,too.
I'm supposed to just copy/paste the link.. but the protocol won't let me since I still don't have more than 10 posts. I just want to help. Try this

XT320 setup wizard issue after flashing

Hi everyone,
I have a big issue after having flashed my XT320 : when it starts, I have a setup wizard failure (com.android.setupwizard) asking me to force closing it... and it does it again without ending (error message, close, error message, close..). The consequence is that I can't use my phone anymore (the weird thing is I see the incoming sms, but that's all).
The problem is that my phone is not detected by RSDlite anymore (and even by Motorola device manager). ADB isn't working when I try to connect when the phone is in USB mass storage mode (device not found), which could be normal as I can't enable USB debugging mode. The only thing I can do is power on the phone in recovery mode, then plug it to the PC, then use the terminal to make fastboot recovery (I used a custom recovery.img taken from xda). Thus, I might be able to reflash the phone with another ROM, but I am not sure... I figured I also could enable USB debugging mode with ADB, but I can't use ADB
Anyway, this is what I've done before I was stucked :
- enable fastboot (it wasn't)
- root my phone (ok)
- install CWM
- backup my data
- install CyanogenMod 7.2.zip and corresponding google apps on my SD card
- restart in recovery
- wipe data & cache
- choose install from sdcard option
- run cyanogenmod 7.2 and google apps
- reboot
If you have a genious idea, please tell me, I will be REALLY grateful !
Thanks
EDIT:
I have also installed Motorola Device Manager (and I am under windows 8). I was wondering if there was an issue with the drivers, but I tried to reinstall, reboot, with no changes... I also tried to force windows using the drivers in Motorola folder, but windows says the device won't work properly. I am quite sure there is a driver issue too (I've just tried to use Android root software, but the phone is not detected).

[Q] Galaxy S-5360 No Download Mode, but Recovery Mode Works

I am new to posting, but I have followed XDA for a long time and used it to install custom ROM's on other phones. However, I now have a problem with my wife's Samsung Galaxy GT-S5360L. I have searched for hours, but can not find a solution.
The phone is stuck in a boot loop. I can enter stock recovery mode. When I try to perform a factory reset, I get the following message:
E:format folume: rfs format failed on /dev/stl11
formatting /cache
Data wipe complete
After wiping the cache partition, the phone continues to be stuck in the same boot loop after reboot (Samsung logo appears on screen, followed by animation, back to Samsung logo).
The phone will not enter into download mode. When I press power+volume down+home, I see a white screen, followed by a black sreen, followed by another white screen. the suggested method of removing the battery, SIM, and SD card, and plugging into the computer while holding both volume buttons does not work. Odin will not recognize that the phone is connected.
I tried to connect the phone to two different computers. One runs Linux mint with Windows XP on a VM. This computer has always worked for flashing ROM's to other phones. Odin would not recognize the phone, and I received messages that the device was not properly installed.
I then tried to connect the phone to another computer with Windows Vista. This PC has Kies installed and Samsung drivers. Kies would not connect to the phone, and I also received messages that the device was not properly installed. Odin would not recognize the phone. I should note that the phone has interfaced with this computer sucessfully before.
This phone has never had a custom recovery or ROMs installed. It only has the original stock ROM. Is the phone's hardware defective, or can it somehow be fixed? Please post any links to threads that I may have missed. Thanks.

Download mode is only effected by a change in bootloader normally by Flashing incompatible firmware or a hardware fault
For flashing via odin kies is not required - its useless as it's not compaitable with the galaxy y for this purpose
You just need the Samsung USB drivers available from my firmware thread (links in signature)
It maybe possible to still flash the device
Once USB drivers installed
Enter download mode
Connect USB to pc
When the white screen appears push Vol up
Wait a few seconds
Open odin
Put the 3 firmware files in their places & flash
If it doesn't flash you will either need to flash a new bootloader via a jtag (repair shop) Or replace the motherboard - either way unless you can get it done very cheap it's more economical to buy a new phone

Thank you marcussmith2626 for your sound advice. The phone is working again. I will share the problems I solved in order to flash the stock ROM. Hopefully this will help anyone else that may have a similar problem.
The Samsung USB drivers had been previously installed on my PC running windows vista. I installed the drivers so that I did not have to use the bloated Kies software. However, when I tried to connect the corrupted phone to the PC via USB, it was not recognized, even though the correct drivers were installed. Below is the procedure I had to follow in order to connect the phone:
1. I connected the phone to the computer via USB. The phone had the battery installed and was powered off. After connecting to the computer, the phone started charging (battery icon on screen). Connecting in download mode at this point did not work. The phone must be powered off.
2. When the "found new hardware" notification box appeared, I had to make a note of each device that had been discovered.
3. I then had to open Device Manager from the control panel and find each device (the name in Device Manager matched the name in the new hardware notification).
4. I right clicked on each unknown device and selected "update driver software"
5. In the next menu, I selected "Browse my computer for driver software"
6. In the following menu, I selected "Let me pick from a list of drivers on my computer"
7. This brought up a list currently installed drivers. I selected the Samsung phone driver.
8. The driver then installed for the selected device..
9. Steps 2 through 9 were repeated for each new device discovered by Windows (each device listed in the "found new hardware" dialog).
10. I started the phone in boot mode (power+home+volume down, phone still connected to PC). I saw only a white screen. However, when I pressed the volume up button, the phone connected to the PC. Odin recoginized the phone and the stock ROM was flashed.
So, even if you only see a white screen, download mode can still be active. In my case, the drivers on the PC were not working correctly, probably due to the corruption of the original stock ROM. The drivers can only be added on my PC using the above method. The option to choose from a list of currently installed drivers was not available from the found new hardware wizzard.
Also, I will also say for reference that in the USA, the stock ROM from Brazil is the one that should be used so that the phone broadcasts on the proper GSM frequencies.

ADB phone access via Windows 10 (broken screen)

Unfortunately I broke the screen of my beloved 6P today and have spent the last 8 hours trying to figure out how to recover everything from it. It's still working as I can hear notifications and phone calls but the screen is blank.
After searching everywhere (xda, stackoverflow etc.), I'm a bit stuck and was wondering if anyone can help. Here's my plan/what I know:
1) I want to emulate the phone screen on my PC via USB using Android Control
2) I need USB debugging mode to access the phone via ADB
3) I need the correct (Google) USB drivers installed on my PC to access ADB
I have downloaded several tools/drivers and this is how far I got:
1) Windows sees/recognizes the phone under Devices and in Device Manager (as It does normally) - I am unable to access the phone because it's not in file transfer mode
2) When I run adb devices, the list is empty
3) I tried to update the driver to the latest Google USB driver but Windows 10 won't let me (windows has determined the best drivers etc. etc.)
I can't be sure what is blocking access via ADB. I'm sure I enabled USB debugging when I first got the phone but it was a long time ago. I read that I might need to disable Windows Driver Signing to install the latest Google driver but I haven't tried it yet.
My question is, how can I tell if it's USB debugging or the Driver? Any help would be greatly appreciated!

If you have your bootloader open, then this should be easy. You can install (if not already installed) TWRP recovery with "fastboot flash recovery file.img". When you then boot blindly into the recovery (its always the same amount of button presses in bootloader) then you can access the storage of your phone.
Other cheap solution: Get a phone with bootloop issue and use that screen from it. Then you have again a fully working phone.