Database Users

Win Error 43.. frustrated.

I've read through so many threads on so many forums trying to fix this, and I'm about to throw this thing through the wall.
I'm running CyanogenMod 7 nightly on 2.3.7
When I connect the phone to any PC (I've tried Win7 64/32 bit, XP SP3, XP SP2) I get a charging icon in my notification bar, but the USB Storage mode never opens to enable/disable. After about 10 seconds I see "USB Device Not Recognized." Happens the same on every PC. I can still access my internal storage via FTP, just not via USB. The device shows in my device manager as "Unknown USB Device."
Not sure if it's related, but when I boot into FastBoot it runs USB Control/USB Control init and then just freezes. Even after downloading a ROM update with ROM Manager it says "NO ROM FOUND"
This is what I've tried:
USBDeview to uninstall all Android-related drivers, reinstalled Samsung and Google SDK rev 4 drivers.
USB data wipe (for the hell of it, really.)
Multiple PC's with different OS and 3 different USB data cables, including the original.
At this point I'd like to try a factory reset. When I try to unroot with SuperOneClick the program just crashes. When I try a reset from the phone it fails to boot into recovery, and using the Factory data reset produces a "null" error.
I know just enough to be dangerous. If I'm missing something please let me know, and I appreciate any help.
--------------------------------------------------------------
Tried loading a CM9 rom from the SD card that I FTP'd over via ClockworkMod Recovery. It asks for data+cache wipe, then just boots into recovery. I get "NO IMG FOUND" and USB CONTROL INIT and USB CONTROL INIT END.

Try installing pdanet on your computer. Its what I did in order for my computer to recognize my phone. Hope it helps.

Should have mentioned earlier that I also installed PDANet after I wiped my drivers. It couldn't detect the phone being connected and did not completely install.

[Q] Yet another boot looped N4, tried all, need expert help to recover user files..

I have been using the stock 4.4.4 for a while with some occasional crashes and reboots in Skype. Then one day, when I turned on my device, the boot loop struck out of the blue! I had only installed some apps, nothing ROM related was changed.
I need some expert help with recovering my user files (some images in non standard folders, game saves etc..)
Symptoms:
*The device is stuck at the circle logo and won't boot up.
*The boot loader is unlocked, USB debugging is enabled and the device was rooted before with version 4.2, upgraded to stock after that at least twice and lost root.
*When connected to PC, auto driver loading fails with MTP but I hear a USB connection sound when I turn on and off the phone. Although, the device is not recognized in "My computer". I see an "Android Device" and/or "android bootloader interface" in Device Manager.
What I tried:
*Tried wugfresh's toolkit and re-installed all google drivers but when I run adb/fasboot commands from within the toolkit, my device is not listed in either list. I get a blank list of devices.
* I can get to the recovery mode in stock boot loader after the "No data" screen and tried wiping user cache, did no good.
What I would like to achieve:
* Ideally I would like to be able to boot into the system without losing any user data and run my backup app and/or connect via USB to backup files on PC.
* If above wouldn't be possible, accessing files externally would also do as a last resort.
Any help is appreciated!
Thanks

ozgurust said:
I have been using the stock 4.4.4 for a while with some occasional crashes and reboots in Skype. Then one day, when I turned on my device, the boot loop struck out of the blue! I had only installed some apps, nothing ROM related was changed.
I need some expert help with recovering my user files (some images in non standard folders, game saves etc..)
Symptoms:
*The device is stuck at the circle logo and won't boot up.
*The boot loader is unlocked, USB debugging is enabled and the device was rooted before with version 4.2, upgraded to stock after that at least twice and lost root.
*When connected to PC, auto driver loading fails with MTP but I hear a USB connection sound when I turn on and off the phone. Although, the device is not recognized in "My computer". I see an "Android Device" and/or "android bootloader interface" in Device Manager.
What I tried:
*Tried wugfresh's toolkit and re-installed all google drivers but when I run adb/fasboot commands from within the toolkit, my device is not listed in either list. I get a blank list of devices.
* I can get to the recovery mode in stock boot loader after the "No data" screen and tried wiping user cache, did no good.
What I would like to achieve:
* Ideally I would like to be able to boot into the system without losing any user data and run my backup app and/or connect via USB to backup files on PC.
* If above wouldn't be possible, accessing files externally would also do as a last resort.
Any help is appreciated!
Thanks
Click to expand...
Click to collapse
Do you have clockwork mod installed?
You might be able to pull the important stuff over ADB when the phones in recovery
If ADB on your computer recognizes and can connect to your phone you can probably pull off the files
Try this: http://www.xda-developers.com/android/all-in-one-guide-to-adb/

prasanth21 said:
Do you have clockwork mod installed?
You might be able to pull the important stuff over ADB when the phones in recovery
If ADB on your computer recognizes and can connect to your phone you can probably pull off the files
Try this: http://www.xda-developers.com/android/all-in-one-guide-to-adb/
Click to expand...
Click to collapse
Thanks for the suggestion. As a matter of fact, while waiting desperately for a reply here, I tried to flash TWRP recovery and managed to adb pull data and sdcard directories over to my PC. And then a factory reset brought my device back to life.
It's a bummer that all of my home screen settings and account settings are reset..
The question now is how to copy over the backup data back to the phone..

adb push will put them back, but your phone will probably mount normally and show up in 'My Computer' now so you could just do that.

ozgurust said:
Thanks for the suggestion. As a matter of fact, while waiting desperately for a reply here, I tried to flash TWRP recovery and managed to adb pull data and sdcard directories over to my PC. And then a factory reset brought my device back to life.
It's a bummer that all of my home screen settings and account settings are reset..
The question now is how to copy over the backup data back to the phone..
Click to expand...
Click to collapse
I'm glad you were able to pull off the files from the phone.
You can use the adb push command to put the data back into the phone
Try this : adb push /path/to/local/file /mnt/sdcard/path/to/file
or
adb -s [yourdeviceserialnumberhere] push /system/[whateverdirectory]
You can check out this too : http://forum.xda-developers.com/showthread.php?t=2167651
The post clearly explains multiple adb commands
Hope it helps!

How to retrieve data without debuggin mode activated and broken display

Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix). I do not consider my phone to be "bricked", just it has the display broken.
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ), maybe it's related to not having activated before the screen damage the debugging mode.
If I start the phone normally I can hear it when connecting it to computer and also it is shown in device manager, under "Portable device".
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,

CM 12.1 on Note 3: Usb is now disconnected

Hi to everyone, I'm having bad time finding a solution to my problem, but for now nothing helped me.
I've CM 12.1 installed on my Note 3. Since I installed it to my phone, I've never be able to connect my phone to the computer.
When I click on settings-->storage-->usb computer connection, it says:
"USB is now disconnected".
This doesn't allow me to set the usb connection, and so my pc doesn't recognize my phone.
On my pc, it says: "Unknown device, code 43" (looks like it doesn't have drivers).
I've tried everything:
1) different cable, pc, usb connected directly to main board;
2) reboot phone;
3) all the steps about enabling and disabling developer option:
**********************************************************************************************
To see the USB computer connection options:
1. Developer>Disable USB debugging.
2. Reboot.
3. Connect to PC.
4. Settings>Storage, press the overflow button (three dots).
If that does not do it, then:
1. Disable developer options.
2. Reboot.
3. Connect to PC.
4. Settings>Storage, press the overflow button (three dots).
5. Re enable developer options. (About Phone>Build Number-6x)
**********************************************************************************************
But, apparently, nothing changed.
I want to solve this situation becasue I need to install stock firmware now.
Another problem is that I've tryed to install twrp recovery (using flashify), but this made my phone go in recovery bootloop, and so now, It seems I can't access no custom recovery.
If there is no solution to the problem above, at least help me to install the right twrp recovery (if compatible with cyanogen mod 12.1), so I can try a stock firmware flashing using it.
Thanks for answering, hope someone can help me.
Note: I've installed 12.1-20151120-NIGHTLY-hlte version, and, if I search update it says that there are some updates, but I cannot upgrade my system.

Have you installed the drivers on the PC ??

Usb cable is damaged or lack of driver on PC.

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.