Database Develop

Problem making pc to recognize phone.

Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.

rahbert said:
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
Click to expand...
Click to collapse
Have you tried with a different USB cable?

No because i connected succesfully my friends galaxy fit with it, so the cable is not the problem.

thry manualy installing galaxy s drivers on pc?

Uninstall and reinstall the drivers.
Try different drivers.
Make sure you're using a Samsung wrong with the Samsung drivers.
Use a different PC.
Keep trying!

I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.

rahbert said:
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
Click to expand...
Click to collapse
To try using different drivers you would need to uninstall the current driver.
And just to be sure, you didn't flash to CM7/MIUI recently, not realizing Samsung drivers won't recognize your phone anymore, right? Nexus S drivers for those ROMs.

Its on the original ROM i think. Recently bought it second hand, 1 year old.
I couldn't find different drivers...except 32 bit and 64bit, but they all are the same version. Maybe post a link or something. Mine are 1.4.4.
Firmware version: 2.3.3
Baseband version i9000XXJVO
Kernel Version: 2.6.35.7-i9000xwjvh - CL184813 [email protected] #Dark_core_2.4 Mon May 16 15:02:38 EEST 2011
Build Number: DarkyRom JVH v10.1

SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!

rahbert said:
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
Click to expand...
Click to collapse
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.

upichie said:
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
Click to expand...
Click to collapse
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx

rahbert said:
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347899

upichie said:
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.

rahbert said:
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
Click to expand...
Click to collapse
Throw it against the wall then. You ask us for help, disregard all of it, and then update us on what the service desk told you. If you will only listen to them, then don't ask us, kay? Appreciated.

Hi, there.
Actully, the rahbert's question is not bad. How can i use Mobile Odin if i can't root the device?
Or, how can I root without PC? Is it possible? I have exactly the same problem:
Nexus S (I9020), ICS 4.0.4(stock). When I plug the device: the error is reported(Code 43).
Should I try wipe data/factory reset? I really don't want to do this, because there is another good question: How can I fully backup my data(Titanium and so on) without root access? Can you suggest me something? Thanks.

Herman76 said:
Have you tried with a different USB cable?
Click to expand...
Click to collapse
Changing the USB cable worked for me. Thanks!!

drivers troubleshooting

Hi Team,
I feel like I'm pretty close to being able to root this thing. Never used ADB, telnet, or any of the other random things I've spent several days reading about, but I think I've got it lined up to give it a shot.
I wish I could do this on my mac, but it seems the MotoWpNoMo step requires a PC. I do have an old laptop running xp (sp3), so for that step I'll use it. Unfortunately I can't seem to get the drivers to work. I've installed the motorola device manager's newest incarnation and still no luck getting it to pick up my device.
Any advice on how to get windows XP to recognize my device?

motoxuser said:
Hi Team,
I feel like I'm pretty close to being able to root this thing. Never used ADB, telnet, or any of the other random things I've spent several days reading about, but I think I've got it lined up to give it a shot.
I wish I could do this on my mac, but it seems the MotoWpNoMo step requires a PC. I do have an old laptop running xp (sp3), so for that step I'll use it. Unfortunately I can't seem to get the drivers to work. I've installed the motorola device manager's newest incarnation and still no luck getting it to pick up my device.
Any advice on how to get windows XP to recognize my device?
Click to expand...
Click to collapse
what do you mean by your computer won't pick up your device.
like when you plug in your device nothing happens no driver's start to install or on your phone does it say USb debugging enabled or MTP.
or when you computer trys to install the drivers it fails.
if you not getting anything at all when you plug your phone in i would try a different USB port if still nothing then i would try a different USB cable
if you are having issues getting the drivers to install you can try downloading the Moto X toolkit, it has a option to download the drivers plus it also comes with ADB and everything else in the folder it installs to.(location is C:/Program Files/stillthisguy)
here is the link for the Toolkit for PC
http://forum.xda-developers.com/showthread.php?t=2477132
ToolKit for Mac
http://forum.xda-developers.com/showthread.php?t=2591875

hey that got it - the toolkits are great. thanks!:good:

motoxuser said:
hey that got it - the toolkits are great. thanks!:good:
Click to expand...
Click to collapse
no problem man glad it got it up and running

[Q]ADB/Device Manager Issues, help please!

Hello all, first time poster, but I have been lurking for a few days absorbing what I can. I just recently got my first Android phone, the Droid Turbo. So far I love it. I am trying to use the awesome Debloater tool I found elsewhere, but I have a problem. When ever I connect my Droid Turbo to a computer in my house (desktop or laptop), I get an error in device manager. Neither the standard Google ADB driver, or the Universal ADB drivers seem to be working. I am not stupid when it comes to computers, but am I missing something? I have uninstalled, restarted and reinstalled both drivers a few times, I even tried using the SDK to install Google's drivers as well. USB debugging is turned on. I can't seem to find any USB drivers for the Droid Turbo at the Motorola site listed with Google. The phone is new, running 4.4.4 KitKat. I am running Windows 7 x64 on my PC, a fairly fresh install. I'm really at a loss to figure out what is going on, any help or a point in the right direction would be greatly appreciated . I have already searched most of the relevant information and videos on this sight, but perhaps I missed something.
Please keep up the good work! My phone is just begging for a root/unlocked bootloader with a clean Android install, But I will settle for no bloatware for now.
I was going to include a screenshot of what I see with my phone plugged in, but I don't have enough posts yet. None of the options of "Update Driver" result in it working, its as if it sees my Droid Turbo there, but I just don't have correct the drivers for it, and I cant find the right ones.

Install drivers from motorola and select driver manualy, dont work with Windows XP

matheus_sc said:
Install drivers from motorola and select driver manualy, dont work with Windows XP
Click to expand...
Click to collapse
at this link:
Motorola Device Manger/USB drivers.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481

Awesome!
Awesome! That link is what I was missing. Thanks a lot to both of you!

Help on htc one (M7)(GSM) revive from hard bricked state

my htc one (M7) (GSM) got hard bricked on its own (i never rooted it or anything), it shows up as QHSUSBDLOAD or something in the device manager in windows 8.1
i found this link to revive my phone: http://forum.xda-developers.com/showthread.php?t=2770684
I am a total noob and i know nothing about rooting or flashing roms or anything for that matter (i just think my phone is hard bricked because someone told me if it comes up as QHSUSBDLOAD in the dev manager, it means it is hard bricked). There is no response if i hold the power button, or the power and volume buttons under a bright light or not under a bright light, i tried charging it continuously for 5 days, nothing happened, LED is not flashing. Only when i connect it to windows via a usb cable, it recognised it as an unknown device, when i updated the driver, it showed QHSUSBDLOAD.
This link (same as above): http://forum.xda-developers.com/showthread.php?t=2770684
worked for many people. i'm a noob so can anyone please elaborate and give me a full detailed process on how to go about it. Again, i never ever rooted my phone.
And its out of the warranty period, and i dont really know what a jtag box is, but i heard it involves opening up your phone, and i really dont wanna do that. But, if theres a method of using jtag via a usb cable and reviving my phone without opening it up, then plz tell me that too.
otherwise, just elaborate on the same link ( http://forum.xda-developers.com/showthread.php?t=2770684)
and explain it to me like u would to a noob.
THANK YOU!!!!
Any help is appreciated.

Hi,
Thanks for using XDA Assist Please Standby When we move your post here HTC One Help and Troubleshooting
Good Luck !

ari4788 said:
my htc one (M7) (GSM) got hard bricked on its own (i never rooted it or anything), it shows up as QHSUSBDLOAD or something in the device manager in windows 8.1
i found this link to revive my phone: http://forum.xda-developers.com/showthread.php?t=2770684
I am a total noob and i know nothing about rooting or flashing roms or anything for that matter (i just think my phone is hard bricked because someone told me if it comes up as QHSUSBDLOAD in the dev manager, it means it is hard bricked). There is no response if i hold the power button, or the power and volume buttons under a bright light or not under a bright light, i tried charging it continuously for 5 days, nothing happened, LED is not flashing. Only when i connect it to windows via a usb cable, it recognised it as an unknown device, when i updated the driver, it showed QHSUSBDLOAD.
This link (same as above): http://forum.xda-developers.com/showthread.php?t=2770684
worked for many people. i'm a noob so can anyone please elaborate and give me a full detailed process on how to go about it. Again, i never ever rooted my phone.
And its out of the warranty period, and i dont really know what a jtag box is, but i heard it involves opening up your phone, and i really dont wanna do that. But, if theres a method of using jtag via a usb cable and reviving my phone without opening it up, then plz tell me that too.
otherwise, just elaborate on the same link ( http://forum.xda-developers.com/showthread.php?t=2770684)
and explain it to me like u would to a noob.
THANK YOU!!!!
Any help is appreciated.
Click to expand...
Click to collapse
First line of the guide:
This will fix devices which were bricked due to firmware incompatibility. This can be caused with the way HTC handles the firmware updates in it's m7's OTAs. If you've been flashing from a 3.x firmware to a 5.x firmware via OTA, or manually, you most likely have a device stuck in QHSUSB_DLOAD. This tool is for you
Click to expand...
Click to collapse
Doesnt apply to your situation:
my htc one (M7) (GSM) got hard bricked on its own(i never rooted it or anything),
Click to expand...
Click to collapse
Device entering QHSUSB DLOAD mode by themselves are usually devices with hardware problem and this guide won't fix anything. You'll probably have to replace the motherboard of your phone. You should however give this guide a try just to confirm its indeed an hardware problem. Just follow steps by steps and ask questions when you are stuck.

alray said:
First line of the guide:
Doesnt apply to your situation:
Device entering QHSUSB DLOAD mode by themselves are usually devices with hardware problem and this guide won't fix anything. You'll probably have to replace the motherboard of your phone. You should however give this guide a try just to confirm its indeed an hardware problem. Just follow steps by steps and ask questions when you are stuck.
Click to expand...
Click to collapse
thanks for the reply.
First of all, i don't know what all this is:
the appropriate package for the device
fastboot
distro utils: md5sum, strings, tail, grep, unzip ( all included in most linux distros)
some basic linux experience
root access on a linux machine
I've never touched Linux EVER. Only thing i know is that it's an operating system.
IF you have the time, can u please tell me:
1) ''which version'' of Linux i should install (is it 64 bit and 32 bit too?)
2) from where should i install it
3) how should i install it
4) what Ubuntu is. is it some form of linux. Can it be used in this case? If yes, then how?
5) what fastboot, distro utils, root access on linux means.
6) can linux be installed side by side on my windows pc along with the windows i already have? then how?
7) what all this means-
Boot the linux box and download the appropriate package for the device.
Remove the sim card from the phone. Do not connect yet
Extract the package in your working directory
Open up a terminal and cd to that directory
Run revive.sh as root and connect the device
Code:
sudo ./revive.sh
( i mean, i know how to remove the sim card, but whats a linux box?, how do you extract the package?, how to open u a terminal, what is a terminal?, how to open up a cd to that directory, which cd? how to "run revive .sh as root", what the code sudo ./revive.sh means and how and where do i use it?)
Thank You.
BTW, is there any way to tell for sure whether my problem is in the hardware or in the software?

reflashing entire system, bootloader, recovery, all of it

So I really messed up. Somehow my l90 manged to get a corrupted bootloader and recovery, I believe. It will not turn on, nor boot into recovery. It is quite literally, a very fancy brick at the moment. I do believe it is soft-brick though, as it will show up on my windows computers, and my linux (running debian) Long story short, can someone guide me to reflashing the entire system again? If linux is the way to go, great, I already have the ADB and Fastboot tools installed, if there is a program to do this on windows, great. The phone shows up on windows as QHSUSB__BULK, the same as on linux, but the linux machine recognizes the processor manufacturer, as "Qualcomm CDMA Technologies MSM" Any help is appreciated, as I currently have a windows phone, (If there ideas on changing that operating system to android, please tell) and it is... nicely put a disappointment.

Follow this tutorial and skip step one
http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429

MrCampust said:
Follow this tutorial and skip step one
http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429
Click to expand...
Click to collapse
Thanks, I have done that, but on the check, it fails and says check pmic and I can't get anywhere from there. It also seems no one has gotten that error either, though I will ask for assistance on that thread.