Develop Bugs

Help, Sprint Galaxy Nexus will not connect to PC...

I have browsed up and down both these forums and google. I am not a dev, but I am by no means a newb at this stuff.
Here is what is happening and what I have tried.
The Nexus will only recognize on the PC as INFT2 device and will try to install as a modem. I am not rooted. The problem with this seems to be that the only recurring theory that seems to be popping up is that I have Fastcharge enabled. Unless I am grossly mistaken, if I am using a stock kernel that not possible. And all signs (unless I'm just completely oblivious in looking this stuff up) point to my kernel being stock. Just for fun if anyone wants to direct me to a terminal emulator way to disable fast charge if my kernel is magically not stock, I'm all ears.
What I have attempted so far.
-Using the toolkit 7.8 installer
-Using the PDANET installer.
-Manually using the link provided in toolkit 7.8 to get it to recognize the device properly.
-Switching USB ports on my computer.
-Three different USB cables.
-Trying to force the device to recognize in Device manager (but since it isn't recognized as a usb device I don't know how that's possible.
For your dissection this is the kernel I have on my new phone.
3.0.8-00007-g785b3cc
[email protected] #1
SMP Preempt
Any help is greatly appreciated at this point.

When you connected the very first time your phone to PC, did it say your drivers could not be found? I presume you started after that the hole drivers saga. If I'm correct, Fastcharge would require a custom kernel and you are on stock, right? So why using it from the start... I own a GSM model from Google Play and my kernel is at 3.0.31 version.
Few rules for people running on Windows software: use the Windows Update drivers and original Google drivers for ADB, if you do not want to end with a pile of crap. I would start by removing all the crazy driver collection you have there and make sure they are gone. Run a cmd as Administrator and type:
Code:
set devmgr_show_nonpresent_devices=1
Then, in Device Manager enable the hidden devices (View > Show Hidden Devices) and hunt down all the drivers you installed, they will be grayed. You are in for a nice long workout... might as well re-install Windows.
Read this guide also: http://forum.xda-developers.com/showthread.php?t=1830108

Fastboot does not work but ADB does

Hey guys,
The power button on my phone stopped working this morning (without water damage). I'm preparing the phone to return to Samsung warranty, and in the process of reseting to stock and re-locking the OEM I noted that the phone does not respond to fastboot commands in the bootloader despite this working on the same system a week ago, no change in drivers or anything else. I installed PDAnet, still broken on Win 7 although I can reboot with adb.
I then tried this on OSX, again I can reboot with ADB, but the phone is unresponsive in fastboot.
I have three working hypotheses and I'm hoping someone can help me:
a) in some process of flashing my phone and being an uninformed n00b maybe I flashed something I shouldn't have or used some combination of partial fastboot flashes I shouldn't have. has this happened to anyone else?
b) whatever hardware damage knocked out the power button might have partially knocked out the bootloader
c) I just have really bad luck with driver set up and I just happened to mess up two different computer driver configurations but the phone is fine. to this end, I am setting up another Win 7 system fresh on a virtual drive as I'm typing, though I have little faith it will be different

update: fastboot commands didn't work on the other windows 7 virtual system, although adb reboot bootloader did
freaking a this is annoying.
i have a fully stock ROM and radio, anybody to know how to flash a new recovery image and lock the bootloader without accessing fastboot? Just have to get this ready to go back to Samsung so they can fix their own hardware mess ups.

they are 2 different drivers.

As much as I don't like using/recommending the Galaxy Nexus Toolkit (only because I feel it's better to actually learn everything you're doing), it's the easiest way I've found to get the Fastboot drivers installed.
http://forum.xda-developers.com/showthread.php?t=1392310

Thanks guys for your comments.
I've tried Android SDK drivers, PDANet, Universal Naked Driver, and now the one click toolkit mentioned above, some on three different operating systems (Win 7, Win 8, OSx) on 32 and 64 bit.
The wierdest part is that under device manager, no device shows up when the phone is in fastboot, no is there any noise or any recognition of the device being connected at all. It is completely, 100% silent. (again, ADB works when the phone is booted).
I recognize that this may not be possible, but does anyone know how to flash a recovery image without being in the bootloader mode?

If fastboot isnt working like it should, and you are sure it isnt user error, then take it for warranty.
Sent from my i9250

yeah fastboot + the power button (which was defunk in clockwork mod) are back online again, dunno for how long. agreed seems like a hardware/warranty issue.

Recoveries can be flashed with ROM Manager assuming you have SuperUser permissions, but otherwise you or the toolkit need fastboot working.
Sent from my Galaxy Nexus using xda app-developers app

Trying to backup phone using Gnex Toolkit

Hello
My Galaxy Nexus's USB port seems to be broken, I have to wiggle to get it to load the battery or connect to a PC. I'm planning on sending it in.
But before sending it in, I want to do a full backup (NANDroid backup is what I want, right?). So I wiggled and connected my phone to my PC (Gnex Toolkit and drivers installed), and tried to back it up.
Now: whenever the toolkit needs to use fastboot mode it displays < waiting for device >. My phone however displays:
FASTBOOT MODE
PRODUCT NAME - tuna
etc.
SIGNING - production
LOCK STATE - UNLOCKED
Nothing happens.

lynguist said:
Hello
My Galaxy Nexus's USB port seems to be broken, I have to wiggle to get it to load the battery or connect to a PC. I'm planning on sending it in.
But before sending it in, I want to do a full backup (NANDroid backup is what I want, right?). So I wiggled and connected my phone to my PC (Gnex Toolkit and drivers installed), and tried to back it up.
Now: whenever the toolkit needs to use fastboot mode it displays < waiting for device >. My phone however displays:
FASTBOOT MODE
PRODUCT NAME - tuna
etc.
SIGNING - production
LOCK STATE - UNLOCKED
Nothing happens.
Click to expand...
Click to collapse
I use mybackup pro to save all my files and data, also you should look into repairing your usb flex cable yourself like i did, The part is cheap and it really is a simple process pulling your phon apart with the correct tools..just be careful not to break your volume flex cables! Heres a link to rpairing it http://www.ifixit.com/Guide/Repairing-Samsung-Galaxy-Nexus-Micro-USB-Charge-Port/9641/1 and here is a link for the part http://www.ebay.com.au/itm/Replacem...AU_MobilePhoneAccessories&hash=item2c6a1fa3b9 goodluck mate.

@n-0-s: Thank you very much for your reply, but I don't like tinkering with my phone. I'm still under guarantee, so I could send it in.
@the developer of Gnex Toolkit: I found the culprit. The Android 1.0 drivers could not be installed under Windows 8 64-bit. I used Windows XP in a virtual machine and it worked.

Possible Hardware Fault

Hey guys, been a long time since i last created a thread so here goes... I think my galaxy nexus has developed a possible hardware fault, the syptoms include;
1 charger not always being detected (mains or usb), sometimes does more often doesnt get detected
2 phone speaker wont always work (will for android system sounds not mp3s or video etc user stuff), sometimes does play my stuff
3 the times the charger is detected the speaker works correctly for user stuff
4 just a reboot will make the charger not be detected without removing it, on boot not being detected
5 off line charger mode is in some kind of bootloop (charges for a few seconds, reboots to battery icon, charges for a sec, repeat)
6 pc wont recognise the device get malfunction report (adb and fastboot mode) windows 7 ultimate 32 bit
So sounds like the usb port is screwed right? But what about the times it works and then my speaker works again? Possible mother board problem? Iv had this for about 4/5 days, some days are worse than others but my phone is no longer reliable as its my pride andjoy and need it for work and social life etc
Any ideas about a fix or a better answer as to whats broken and how to get back to stock for warrenty without usb?
Specs as follows;
minco v6
franco 361
192-1228mhz
row schedular
default hardcoded kernel voltages
hw vers 9
jellybean europe radio

The Gingerbread Man said:
Hey guys, been a long time since i last created a thread so here goes... I think my galaxy nexus has developed a possible hardware fault, the syptoms include;
1 charger not always being detected (mains or usb), sometimes does more often doesnt get detected
2 phone speaker wont always work (will for android system sounds not mp3s or video etc user stuff), sometimes does play my stuff
3 the times the charger is detected the speaker works correctly for user stuff
4 just a reboot will make the charger not be detected without removing it, on boot not being detected
5 off line charger mode is in some kind of bootloop (charges for a few seconds, reboots to battery icon, charges for a sec, repeat)
6 pc wont recognise the device get malfunction report (adb and fastboot mode) windows 7 ultimate 32 bit
So sounds like the usb port is screwed right? But what about the times it works and then my speaker works again? Possible mother board problem? Iv had this for about 4/5 days, some days are worse than others but my phone is no longer reliable as its my pride andjoy and need it for work and social life etc
Any ideas about a fix or a better answer as to whats broken and how to get back to stock for warrenty without usb?
Specs as follows;
minco v6
franco 361
192-1228mhz
row schedular
default hardcoded kernel voltages
hw vers 9
jellybean europe radio
Click to expand...
Click to collapse
It sounds like a usb problem compltley anf about speakers maybe a connectionnis loose or something but when youbget it to charge it connects properly I dont know naything about hardware so im just guessing!
Sent from my LT30a using xda premium

mcsqwizzys98 said:
It sounds like a usb problem compltley anf about speakers maybe a connectionnis loose or something but when youbget it to charge it connects properly I dont know naything about hardware so im just guessing!
Sent from my LT30a using xda premium
Click to expand...
Click to collapse
Well I'll pretty sure the USB port is ****ed but the speaker does always work, just not for my stuff. Like, phone will ring, alarm goes off, get notifications of stuff, turning up ring volume make the sound but things like music don't play out the speaker. That's what I meant by android systems sound works but not my stuff like music and video or games, Gatsby anything not belonging directly to android os won't play over the speaker so loose connection for speaker is ruled out
Sent from my Galaxy Nexus

CWM Back up..
Flash JB Stock Firmware..
Test..
It's knowing that undervolts n downgrade freqs to 192 min could cause that hardware fails n will do funny restarts ..
I think thats why franco use mins at 384 by default..
Howeber.. I had experimented some problems with audio in last kernel 361, dont know if it has being caused by audio boost like in past versions but franco turn off this option in this new 361.. (he said)
Dont know what its happen but I have the same problems today.. I had to call my mother 3 times this evening cause I keep loosing sound..
I have watched that smartreflex is off by default in this new version, and its draining my battery 2 fast..
I'll change tomorrow for the last one i had installed r348.. was good.. not too misses sound calls but was going well at well..
Sorry my english mate..
Paranoid 2.99b9 + franco r361..
All by default and testing since yesterday..

Vessina said:
CWM Back up..
Flash JB Stock Firmware..
Test..
It's knowing that undervolts n downgrade freqs to 192 min could cause that hardware fails n will do funny restarts ..
I think thats why franco use mins at 384 by default..
Howeber.. I had experimented some problems with audio in last kernel 361, dont know if it has being caused by audio boost like in past versions but franco turn off this option in this new 361.. (he said)
Dont know what its happen but I have the same problems today.. I had to call my mother 3 times this evening cause I keep loosing sound..
I have watched that smartreflex is off by default in this new version, and its draining my battery 2 fast..
I'll change tomorrow for the last one i had installed r348.. was good.. not too misses sound calls but was going well at well..
Sorry my english mate..
Paranoid 2.99b9 + franco r361..
All by default and testing since yesterday..
Click to expand...
Click to collapse
This isn't cause of any audio mod or anything and Franco removed those patches from 361 and I was able to repeat it in several different kernels from Franco and I know it's not his code or the 192mhz slot, and about flashing back to stock, not so easy when my PC reports a malfunction with my nexus in fast boot mode and adb mode, if it were that simple I'd of been able to flash back to stock by now. My phone is having problems in offline charge mode, fast boot mode and booted up to OS
Sent from my Galaxy Nexus

Maybe usb cable.. another cable?
If not.. usb port.. sure.. you will probably have some pin ****ed..
The audio may not be affected because it will have its own output pin port in this connector..
Have in ebay.. Change it..
http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=150713366355

My old x10 needed slight pressure pushing up on the USB cable to recognise it. So if a new cable doesn't fix it ^^ try resting the cable on a book while your phone hangs of it. Try to find the sweet spot so the pins connect properly.
Just another option to rule out.
Good luck
Sent from my GT-I9300 using xda premium

First thing I'd do is uninstall my android device drivers. They're hidden though because they're non-present (device isn't connected) so here's a trick for that in Windows 7.
Start menu -> Right click Computer, Properties -> Advanced System Settings -> Environment Variables...
Under User variables -> New... -> name: devmgr_show_nonpresent_devices -> value: 1
Reboot. Go to Device Manager in Control Panel. View menu -> Show hidden devices.
Now you can see everything that was ever installed. Uninstall all the Android ones.
Then I would boot into CWM/TWRP and try connecting using a different cable than the one you were using before, preferably one you know works. Reinstall the adb drivers for Universal Naked Driver for Android devices (version 0.72 currently, I believe). If you get that going, then adb reboot-bootloader and install the Naked drivers for fastboot if it doesn't do it itself. If you get that going, then I'd fastboot oem lock my bootloader, then flash the entire Galaxy Nexus Factory Image as follows:
fastboot devices
fastboot oem unlock
fastboot reboot-bootloader
fastboot flash bootloader <bootloader>.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
Then maybe fastboot oem lock and fastboot oem unlock one more time just to make sure things are nice and squeaky clean. And then reboot and see if things work?
P.S. for adb and fastboot you don't need the Android SDK or anything, they work standalone, and you can get them attached to the OP here:
http://forum.xda-developers.com/showthread.php?t=1626895

I'm having the exact same charging issue for the last 2 days.
Took the phone apart today, took EVERYTHING out and sprayed everything with alcohol and cleaned all the connectors, connected it all back up and it's still the same.
Mine registers the charger after A LOT of attempts but the strange thing is, it will register charge from a PC with fast charge on, Much easier than it will from the wall charger. I've tried a few chargers too so it's not a cable or anything.
Sent from my Galaxy Nexus using xda premium

The Gingerbread Man said:
Hey guys, been a long time since i last created a thread so here goes... I think my galaxy nexus has developed a possible hardware fault, the syptoms include;
...
6 pc wont recognise the device get malfunction report (adb and fastboot mode) windows 7 ultimate 32 bit
...
Any ideas about a fix or a better answer as to whats broken and how to get back to stock for warrenty without usb?
...
Click to expand...
Click to collapse
I think the only way is the warranty repair, but, as you said, PC does not recognize the device and you cannot flash back to stock... In Gnex toolkit you need some 5 minutes to do it, maybe you have to try to communicate using different cables, drivers etc and if you ever get the connection, use it immediately to flash...
To connect my phone to PC I use FTPserver, but I doubt it `ll fit to flash the device...

Thanks for the tips guys, will try some of these later, fire now I'm about to start 9 hour work shift
Sent from my Galaxy Nexus

osm0sis said:
First thing I'd do is uninstall my android device drivers. They're hidden though because they're non-present (device isn't connected) so here's a trick for that in Windows 7.
Start menu -> Right click Computer, Properties -> Advanced System Settings -> Environment Variables...
Under User variables -> New... -> name: devmgr_show_nonpresent_devices -> value: 1
Reboot. Go to Device Manager in Control Panel. View menu -> Show hidden devices.
Now you can see everything that was ever installed. Uninstall all the Android ones.
Then I would boot into CWM/TWRP and try connecting using a different cable than the one you were using before, preferably one you know works. Reinstall the adb drivers for Universal Naked Driver for Android devices (version 0.72 currently, I believe). If you get that going, then adb reboot-bootloader and install the Naked drivers for fastboot if it doesn't do it itself. If you get that going, then I'd fastboot oem lock my bootloader, then flash the entire Galaxy Nexus Factory Image as follows:
fastboot devices
fastboot oem unlock
fastboot reboot-bootloader
fastboot flash bootloader .img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
Then maybe fastboot oem lock and fastboot oem unlock one more time just to make sure things are nice and squeaky clean. And then reboot and see if things work?
P.S. for adb and fastboot you don't need the Android SDK or anything, they work standalone, and you can get them attached to the OP here:
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Can also use usbdeview ..to uninstall the drives.
http://m.download.cnet.com/USBDeview/3000-2094_4-10614190.html
Sent from my Galaxy Nexus using xda premium

Tito2007 said:
Can also use usbdeview ..to uninstall the drives.
http://m.download.cnet.com/USBDeview/3000-2094_4-10614190.html
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I followed what osmosis said and my phone charged up fine last night, while transferring stuff to / from the PC via USB it sometimes decided to stop be recognised half way through. I'm back on stock rom and using Franco kernel with it at least till I can get my USB port repaired
Sent from my Galaxy Nexus

DesireZ can't connect via USB

Hey guys!
I got my hands on an HTC Desire Z just yesterday and I keep trying to figure out how to connect it to my PC, since it won't pop-up in neither Windws7, Windows8 nor Ubuntu 12.04.
I have tried google drivers, HTC Sync, ADB won't recognize the device. I tried on a freshly installed windows7 - the only device that actually gets installed in Device Manager is "Quallcomm Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.30)" - meaning... ?!?!?! What?!? I can't make anything out of this.
The device is S-OFF-ed here is what HBOOT says:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 8 2010,15:56:38
System Info Output:
SN-SH16DRT00073
LCD-SO
TOUCH PANEL-AMTECL12_20aaY
Commit-adbd7a75
OS Ver.-1.34.405.5
IMEI-*********************
CID-111111111111
eMMC-Sandisk 2223MB 4554751sectors
It has installed CWM recovery. mounting the USB storage from CWM however doesn't work :S
So I can flash a ROM through it, but even a freshly installed ROM wouldn't connect via USB when booted, so I have to run an FTP app to exchange files between my phone and my PC. USB debugging doesn't make any difference.
Besides, I think my phone not being visible in HBOOT by ADB is a big-enough problem by itself.
Does any1 have any suggestions? I tried searching (both by hand and using the forum search engine), but didn't see any1 with a problem similar to mine.
P.S. The phone does charge via the USB cable(tried the original one AND 3 others) when connected to the computer.
I have another Android phone that ADB sees as a valid device etc. ... so I am kinda thinking it maybe even a hardware issue?
There's been some development​
I am now pretty sure it's a software issue. Connecting the device to an older PC running Windows XP works like a charm. Sadly anything that's Core i -based doesn't seem to recognize the device.
Could anyone pull his HBOOT, radio, RCdata, etc. and give it to me so I could try flashing something, that is surely known to be working software?

May have a bad pin in USB port, but if any driver at all tries to install then I'm thinking hardware is okay
Go to any guide explaining how to root and there should be links to the proper drivers.
You may need to uninstall any driver that is associated to your phone and then manually choose what driver you need.
http://forum.xda-developers.com/showthread.php?p=27796375
See third post for a small tutorial
Sent from my Nexus 4 using xda premium

Hmmm.... the correct DRIVERS don't seem to be working on Win8.
Will try on windows7 in a while and write back with results. BTW is there a particular device I should be looking for in the Windows' "Device Manager" ?

Windows 8 and 8.1 have issues, a few Google searchs should show you how to do it. If you can't find what driver in device manager to change there is a free windows program called USB driver search (something like that) which tells you all drivers on PC.
If you go to xda university (the xda thread for it) I have a more comprehensive fastboot guide there with directions for Linux install too
Sent from my Nexus 4 using xda premium

I think (and correct me if I'm wrong) that it's really not a driver issue.
The Drivers I re-linked above had no success on Windows7
I don't get unrecognized device connected to my PC. I don't get any devices connected to my PC (after I uninstalled the Quallcomm Atheros... mentioned before).
Now - again - correct me if I am wrong, but isn't the phone USB driver inside the Radio? if yes - maybe a wrong radio is flashed? Given the fact that I have a working CWM - is it possible to get a fix through it?
@ demkantor
I will do some reading on the subject you said and then test things out tomorrow morning after a clean neat Win7 installation on my PC. I'll post back results.

Ok, so - here are the results:
I re-installed my Windows OS on my PC, installed all the MoBo drivers - a clean slate.
I then installed the HTC Drivers (mentioned above), HTC Sync, platform-tools.
Connected the phone - computer made the tingling sound of a connected device, but in the device manager - nothing.
Is there a way to flash the bootloader/radio/anything, aside from a new ROM through CWM? That's all I got now :S

Flashing firmware should be done in fastboot, if your USB port is broken you can make a flashable zip and flash in recovery but it is less safe. A slightly better option is creating a pc10img.zip
What do you need to flash right now?
Sent from my Nexus 4 using xda premium

demkantor said:
Flashing firmware should be done in fastboot, if your USB port is broken you can make a flashable zip and flash in recovery but it is less safe. A slightly better option is creating a pc10img.zip
What do you need to flash right now?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well I tried flashing different radio through pc10img.zip file, but it had no effect. Windows still plays the tingling sound and no device is recognized.
I'm seeing this HBoot version - PC101000
I noted mine is a tad different - PC1011000, although my HBoot is 0.84.2000 (Which If I understand correctly is the engineering one and should be working properly). Should I be concerned about the number difference and can I flash HBoot through a PC10IMG.zip file?
P.S. I really know I should be flashing through fastboot - the point is - I can't get my DZ connected
P.P.S. Would you advise me to revert to stock (BL, Recovery, Radio, ROM) through PC10IMG.zip (if possible) ?

I know, it was just a general statement
http://forum.xda-developers.com/showthread.php?p=27796375
In the 30th post you will find a link to a pc10img I made that 'may' help, but yes you can return to stock with a pc10img.zip, nipqer made a good guide, just search it out
Sent from my Nexus 4 using xda premium

demkantor said:
I know, it was just a general statement
http://forum.xda-developers.com/showthread.php?p=27796375
In the 30th post you will find a link to a pc10img I made that 'may' help, but yes you can return to stock with a pc10img.zip, nipqer made a good guide, just search it out
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Flashed the DZ_PC10IMG.zip file you posted - sadly there was no effect on the USB connection. I think I'm pretty convinced it's a hardware issue. At this point I think the soldering iron would be my only salvation.
Thank you very much for your time and knowledge!

Sorry for the bump-up, but I have some recent information on the matter - in the first post.

That's very strange, but again it must be a driver issue I would assume. I've had issues before with some PCs and had to use a program called USBDeview to locate all drivers associated with said phone and then force windows to install the proper ones.
All that firmware you requested can be found in the link I sent earlier in the 30th post
Sent from my Nexus 4 using Tapatalk 2

With all due respect I still think it's the phone's software issue. I tried installing Windows7 from the same DVD on both computers. Both PCs run fine, but one of them doesn't recognize the phone. Only difference is the hardware platform.
I tried running linux and OSX (Hackintosh) on the PC that doesn't recognize the phone - no effect on any of the OSes.
PC that recognizes the phone under both WindowsXP and Windows7 has no trouble recognizing it when running live linux (Ubuntu distro)
One other strange thing that I noticed is when I connect the phone to my car charger it asks me whether to mount the SD card or not... I'm no expert but I'm guessing that shouldn't be happening.
That is why I'm hoping that someone could pull their HBOOT, radio, rcdata, recovery, etc... and post them here so I can try flashing a known-to-be-working software and see if it helps.
P.S. (note that the phone doesn't recognize it's plugged into a PC either - it's just charging as if it was plugged into a charger)
One other thing. When I plug the phone in the PC that's not working and I reboot the phone it offers me to mount the SD card and share it with the PC, but the PC won't see there's a USB storage device. It only sees the Atheros gigabit adapter mentioned in my first post. OS clearly doesn't matter.

Again all the firmware you requested in that link on the 30th post, you can unzip it and flash each image on its own if you want, same firmware as on both my g2s and neither have issues
If you're for sure its not a driver issue than its either the USB cable or port (is the new computer USB 3.0?) I feel the phones firmware is unlikely the cause but feel free to test.
But I will say its strange that when plugged into car charger it asks for SD mount, makes me go back to my original thought of a pin on the phones USB port is bad and certain cables trigger effects not wanted
Sent from my Nexus 7 using Tapatalk 2

Well I think I can rule the pin on the phone USB port out, since it's working fine with more than one computer.... sadly it's just not working with the computer I need it to work :S
I'm re-flashing the PC10IMG you posted previously (as it appears I flashed something else last time o.0 )
I'll post results and see if I can order a usb port replacement for my DZ unit.
Once again - Thank you for your time and patience with me!
Cheers