Database Develop

Q: Comp not recognizing hard bricked in download mode

My phone was hardbricked when i screwed up with the latest Serendipity install. It boot loops at the white AT&T world phone screen. I am unable to get it into download mode with out a jig. However, once i do have it in download mode, my computer will not recognize the phone. It keeps viewing it as an unknown device.
I dont know if this is related to it not showing up using Odin 3 one click downloader. Either way, i need to get it back to stock.
I have the drivers already, in fact ive reinstalled them once or twice trying to get this to work, any ideas?

That's not a hard brick. Search the already existing threads in the forums, of which there are many. No need to start another thread on it. Try a different USB port on your PC, make sure you're running Odin as an administrator before you put the phone in download mode and plug it into your PC.
Sent from my GT-I9000 using Tapatalk

Rhiannon224 said:
That's not a hard brick. Search the already existing threads in the forums, of which there are many. No need to start another thread on it. Try a different USB port on your PC, make sure you're running Odin as an administrator before you put the phone in download mode and plug it into your PC.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
sorry for not searching.
as for my problem. ive tried multiple ports and im running odin in admin mode. still no luck

icanhearpudding said:
sorry for not searching.
as for my problem. ive tried multiple ports and im running odin in admin mode. still no luck
Click to expand...
Click to collapse
Have you tried installing drivers and then reinstalling drivers manually from designgears thread in dev?
SIGNATURE : Life is like a box of captivates, you never know if your gps will work

so im pretty much able to get it into download mode any time i want. but i cannot get my computer to view it. No matter what USB port i use, it still says unknown/unrecognized device. I see you mentioned something about manually installing drivers, how would i do that?

Try a different PC. Although, it sounds like a driver issue. What version of windows are you on?
sent from my Gingerbread Cappy using Tapatalk from somewhere on AT&T's ****ty network.

I know others have had issues with i9000 ROMS not being recognized once their phone goes in download mode. Here is a whole thread about it.

yeah i checked through that whole thread, it wasnt any help.
My comp is 32 bit windows 7. ive tried to connect my phone to a 64 bit windows 7, and a mac, and still havnt gotten ****. Im getting really frustrated. What are my options when i simply cannot find a way to get Odin to view the phone? All it says is that my USB device has malfunctioned and it wont work.
EDIT1
okay. ive discovered that if i plug in my USB while the ATandT logo is looping, my computer will see it as an external storage device. THEN i jig it into download mode, and plug it into the same port, and it will no longer see the device as unknown, but instead calls it 'androidtest,' although it still doesnt show up in Odin3. hmmmmm could this be a lead into getting it to show up? Every other attempt ive done has ended up with it just calling it unknown device
EDIT2
Searching through the device manager shows that the phone no longer shows up under universal serial bus controllers, but instead 'libusb (WinUSB) devices', under the name Androidtest. But as i said before, still no luck getting it to show up with Odin, either the one click or the choose all the components version. Any thoughts?

icanhearpudding said:
yeah i checked through that whole thread, it wasnt any help.
My comp is 32 bit windows 7. ive tried to connect my phone to a 64 bit windows 7, and a mac, and still havnt gotten ****. Im getting really frustrated. What are my options when i simply cannot find a way to get Odin to view the phone? All it says is that my USB device has malfunctioned and it wont work.
Click to expand...
Click to collapse
It really sounds like a driver issue. Have u tried downloading I9000 drivers?

prbassplayer said:
It really sounds like a driver issue. Have u tried downloading I9000 drivers?
Click to expand...
Click to collapse
ive downloaded and uninstalled and redownloaded all sorts of different captivate drivers. it always still just said 'usb device malfunctioned.' i belive at this point, i have every driver uninstalled, hoping that windows itself would grab the right one. . ..
idea: ill reinstall captivate drivers. . . then ill do the usb while atandt is booting and THEN use the same usb port for the download mode. Without drivers, this is how i got to the 'androidtest' deal. perhaps with drivers installed, it will do something different.

icanhearpudding said:
ive downloaded and uninstalled and redownloaded all sorts of different captivate drivers. it always still just said 'usb device malfunctioned.' i belive at this point, i have every driver uninstalled, hoping that windows itself would grab the right one. . ..
idea: ill reinstall captivate drivers. . . then ill do the usb while atandt is booting and THEN use the same usb port for the download mode. Without drivers, this is how i got to the 'androidtest' deal. perhaps with drivers installed, it will do something different.
Click to expand...
Click to collapse
HOOOOOOOOOOOOOOOORAY. I did it! THis worked. I had to have the captivate drivers, installed, THEN plug it in during the at and t boot loop THEN plug it in after jigging download mode. Thanks so much for your help everybody!

O2X wont connect to pc as APX device (help needed please)

So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.

GhostRai said:
So I tried to root my phone, it worked, and I wanted to oc it. I used ROM Manager, and bricked my phone, since I installed a program (dont remember what its called) that turned my phone into EXT4, when it needs to run on EXT3 or something. So now its stuck at the LG/ LG with loading bar screen and cannot turn on. I'm trying the flash it with nvflash, but it wont work. I got my phone into APX Device mode once, but I failed and had to try again. But now, my computer won;t recognize my phone and I think I'm doing something wrong, because it wont show my phone as a APX Device. I'm obviously new to this so help would be appreciated.
Click to expand...
Click to collapse
Some people have reported that they have to try repeatedly before it will start in APX-mode. So try again and again before giving up, make sure battery is out and that you firmly press both volume-buttons while plugging it in.
If it absolutely, positively cannot enter APX-mode, then your last hope is Smartflash-mode. Does it start in Smartflash mode if you hold volume-down while plugging it in?
Oh, and make sure you're connected directly to a port on the motherboard.
EDIT: You can try deleting the APX-device from the PC too, to get it rediscovered and reinstalled. Unzip the attached archive and run the batch file in it. (It sets a parameter which allows the device-manager to display hidden and "ghost"-devices before starting it.) Select "Show Hidden Devices" from the View Menu, find the APX-device(s) ("NVIDIA USB Boot-recovery driver for Mobile devices") and delete it/them. Then try to reconnect in APX-mode again. (Have the driver ready.)

PLEASE HELP, Computer is not recognizing my Galaxy S

Just got my phone into download mode after using the jig, and i have been able to connect to my pc before i seriously F'd my phone by messing with a setting in cwm. I have downloaded and redownloaded drivers from samsungs website, along with installing Kies and that does not recognize my phone. (also i would like to add i am unable to access the phone since it wont turn on without the jig, without jig it just goes into a boot loop.)
THis is what happens when i plug my phone into the computer:
plug in usb (to computer and phone)
let it do its thing to recognize device...
pop-up stating "unknown device" so i click it.
then right-click the unknown device which opens up another window
from this menu it shows Install driver, Update driver and 3 other options.
when i press install driver and update driver, it tells me that the driver is already installed in "device unknown."
At this point i throw computer at wall after 2 days of trying to figure this out.

so messed around and the problem only happens when it is in download mode. but when it is not in download mode it shows up but no use to me because i am trying to flash it to stock. soo i dont know why the error 43 only shows up when in download mode. any help would be great.

sean.hunt said:
so messed around and the problem only happens when it is in download mode. but when it is not in download mode it shows up but no use to me because i am trying to flash it to stock. soo i dont know why the error 43 only shows up when in download mode. any help would be great.
Click to expand...
Click to collapse
Just follow this to update the drivers http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 , same thing as what you have done earlier but this time , when it searches for new drivers, you can do the selection for it.
But first reboot your PC after pulling out power cord ...and try the quick solutions first

Ok sen, so i tried to install the driver manually but i am stuck at the part where i have to install something on my phone to allow it to sync with the computer, since my phone will not even boot up. I am starting to think my dear Capi is going to be a paper weight =(

Softbricked HTC One "Qualcomm HS-USB QDLoader 9008"

Hi, i need help on this phone.
So the issue is this phone went into a bootloop but i can still go to recovery or hboot. When I tried doing adb the phone cant be found. Having no idea on how to go about messing with HTC phones, I brought it to a technician. This phone has a locked bootloader, he was able to unlock it and then install TWRP but he failed to load rom on this device and gave up. Thinking since it got TWRP i can go ahead and try to fix it myself since the technician already gave up and i was not charged for the "repair". When I went home the phone wont boot, when I charge it the led wont turn on and the phone wont respond to any button combinations, tried to shine a light on the sensors too while booting up and trying the button combinations but it didnt work. I was getting these errors (attached) before I went to get the phone fixed. It says that data it failed to mount /data. When I connect the phone to my laptop i can see in device manager that the phone is read as Qualcomm HS-USB QDLoader 9008. Is there still a way to fix this or is this hardware related already? Cause if its hardware related then I would stop trying to fix this phone and maybe just sell it for its parts. Any help would be greatly appreciated, thanks.

Kcube989 said:
Hi, i need help on this phone.
So the issue is this phone went into a bootloop but i can still go to recovery or hboot. When I tried doing adb the phone cant be found. Having no idea on how to go about messing with HTC phones, I brought it to a technician. This phone has a locked bootloader, he was able to unlock it and then install TWRP but he failed to load rom on this device and gave up. Thinking since it got TWRP i can go ahead and try to fix it myself since the technician already gave up and i was not charged for the "repair". When I went home the phone wont boot, when I charge it the led wont turn on and the phone wont respond to any button combinations, tried to shine a light on the sensors too while booting up and trying the button combinations but it didnt work. I was getting these errors (attached) before I went to get the phone fixed. It says that data it failed to mount /data. When I connect the phone to my laptop i can see in device manager that the phone is read as Qualcomm HS-USB QDLoader 9008. Is there still a way to fix this or is this hardware related already? Cause if its hardware related then I would stop trying to fix this phone and maybe just sell it for its parts. Any help would be greatly appreciated, thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56198279&postcount=2
Sorry
Sent from my HTC One using XDA Labs

Phone bricked, need help :c

Hey, Ive tried to install xiaomi.eu rom but didnt realize that i needed the chinese rom and that the global didnt work for this, after ive installed using TWRP the rom, ive rebooted and it just went black, not recovery, not fastboot.
BT was unlocked.
I also see my phone as qualcomm...qloader 9008 when connecting to my pc
Any help?

after having a few heartattacks, ive installed a good Miflsah and a good fastboot rom, and managed to restore my phone to its former glory
no need for further help, but i have a few advices
dont be stupid like me, and listen to directions like theyre the word of god, when they say change from chinese rom to a non official rom, YOU NEED CHINESE, global wont work
and if you're having problems with miflash giving errors, try a bunch of downloads, old, new, everything.

Hi, yet another brick here!
I had an AOSP ROM but I had problems with it. I entered TWRP, downloaded a MIUI official ROM for recovery, wiped the phone from TWRP and decrypting it (there was an option for that). Then I did try to flash the ROM and... black screen. No signs of life.
However, when I connect it to the computer it detects it as the famous Qualcom xxx 9008 (COM10) device. But fastboot is not working, when I type "fastboot devices" it doesn't return anything. ADB doesn't recognize the phone either. Everywhere I saw that I should use MiFlash to recover it, but I took a look at the scripts and are using fastboot to perform the process. But since fastboot doesn't recognize the device, it won't work. I get stuck all the time at "Failed to receive the hello packet".
Fastboot doesn't detect my phone either on Linux or Windows. I tried Linux, virtual Windows 10 (x64) and at last I'm trying on a Windows 10 (x64) computer (no virtualization). No matter what I do, it always stays at the same point. I also used several MiFlash versions (from old builds from last year to the most up-to-date version of XiaomiMiFlash). But since fastboot is not detecting the phone I think there's no point in switching MiFlash versions.
So... what can I do? Should I use the pin short-circuit /deepflash cable method? As of I understand, that is what you use to get into EDL, but if my device is showing 9008 in device manager doesn't it mean that I'm already in EDL? I'm not really sure because all the threads I saw in several forums are a bit messy.
I'll appreciate any help. I don't have phone since 3 days ago and I can survive without it but I need it for my work.
Thank you in advance!
EDIT:
Forgot to say, if I try to power off and power on it doesn't do anything BUT when I plug and unplug from the charger it does show a battery icon with the charged percentage. That's the only sign of life from the phone, aside from being recognized as a 9008 device, but that actually happens when I try to (blindly) get in fastboot mode.

FIXED!!! After four hours testing out several options I found the solution: Open up the phone, unplug the battery cable, plug it again, and voilà. The phone automatically got recognized (again) as Qualcomm 9008 device but this time the flash went on flawlessly. It took less than 5 minutes, once succeeded I powered on the device and it ran into MIUI 8 in less than 5 minutes.
So, if you find issues with the command "fastboot devices", unplug the battery and try it again before troubling yourself with deepcables or shortcircuits ;-D
NOTE: Taking out the back cover is very easy, search on youtube, I bought the thing you need for 1$ at the store next to my home (sorry I don't know what it's called).