Related
Hi Community-
I'm having USB connection issues & was hoping for a little guidance.
Although I've read through multiple USB problem threads, I thought I'd start my own rather than hijack another member's thread.
In an effort to best help, I'll try to be thorough.
When I connect my Vibrant to PC, I get the "USB Device Not Recognized" and "Error Code 43" notifications & "Unknown Device" designation in Device Manager. Also, when I set updates to automatic, I get an "Drivers failed to install" notification (paraphrased).
I am running EDT's Project V with one of the Bullet 1.2/1.42 kernels. While I DO NOT believe the ROM or Kernel are causing issue, I will likely change both soon to confirm.
To solve the issue, I have attempted the following in USB Debugging and Mass Storage modes:
1. Plugged into 3 different PCs (2 running XP, 1 running W7).
a. Multiple usb ports in each.
2. Used 4 different micro USB cables (two are original Samsung cables).
3. Allowed windows to autdetect & install drivers (fails).
4. Installed 32 bit drivers & 64 bit drivers from multiple sources using the included setup files (uninstalled between).
5. Manually directed Windows to 32 bit and 64 bit drivers using Device Manager.
6. Attempted to connect to Kies Mini in Kies mode (uninstalled program after failure).
*As a side note, I successfully connected a Captivate & Fascinate (neither mine) to one of the PCs using one of the same Samsung cables I have tried.
*And another: I have not tried to connect the Vibrant recently, but have successfully connected the phone to multiple PCs in the past.
To this point, I have not tried:
1. Manually installing I9000 drivers.
2. Installing a new Froyo kernel and/or ROM.
3. Reverting to a previous Froyo nandroid that connected in the past.
4. Flashing an Eclair kernel then reverting to a stock Eclair nandroid.
Those will likely be the next steps, but if any users have had success using additional methods, any advice would be greatly appreciated.
Thanks!
Try this from Unlockr.com (was for HTC drivers but you can clear remaining Samsung drivers if any)
1. Download USBDeview
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
2. While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the Samsung drivers and delete them all.
3. Once all have been deleted, unplug the phone from the USB cable and plug it back in.
4. The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
suchavibrantthang said:
4. The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
Click to expand...
Click to collapse
Downloaded USBDeview from the provided link. Program confirmed that I have already deleted all Samsung drivers.
When I left program running and plugged Vibrant back in, I got:
1. Same error notification (device has malfunctioned).
2. Windows did not try to download drivers (despite permission in Windows Update).
3. USBDeview did not recognize that a USB device had been plugged in (checked "Display devices without drivers" under Options & refreshed).
Thanks for the reply & a new method to attempt though! Something's gotta work eventually.
"device has malfunctioned"
"Drivers failed to install" notification"
edit: just letting you know my experiences with those failure notices. for me it had nothing to do with drivers and such. it was faulty hardware.
Ive had this problem with one of my MS Bluetrak mouses. The USB dongle fried and burned and messed up one of my usb2.0 ports on my laptop, leaving me with only one. Might be your usb port in your phone that's malfunctioned. My two vibrants have loose connections now because of the way it pulled left or right while charging. so it's either your usb port on pc or the phone has a bent chip or massive dust...idk
sorry i cant help. another alternative is to replace your usb part on your phone.
suchavibrantthang said:
"device has malfunctioned"
"Drivers failed to install" notification"
phone has a bent chip or massive dust...idk
another alternative is to replace your usb part on your phone.
Click to expand...
Click to collapse
Yeah, looking that way, huh?
Anyway, thanks again.
I had a similar situation. I had 4 micro usb cables, two samsung stock ones (captivate/vibrant), 1 blackberry, 1 which I forgot where I got it from. Long story short, the blackberry one which coincidentally was the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
mrlazyone said:
the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
Click to expand...
Click to collapse
Haha, tried my thickest cable for 15 min again just to see.
Unfortunately, I'm getting close to giving up.
So:
1. No smartphone for a while ... Boo!
2. Or no Odin ever ... Double boo!!
Sent from my SGH-T959 using XDA App
mrlazyone said:
I had a similar situation. I had 4 micro usb cables, two samsung stock ones (captivate/vibrant), 1 blackberry, 1 which I forgot where I got it from. Long story short, the blackberry one which coincidentally was the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
Click to expand...
Click to collapse
THANK YOU!!!! I tried using my wife's cable and it did the trick! It sucks because I saw your comment a few days ago but it didn't register but this morning I am sleepless so decided to give it a shot again and voila!!! Thank you boss.
I have been working through this for a while as well. As far as I can tell, the problem is isolated to only my machine, even though there are a couple of different USB controllers within. Both cables I have and the CM7.1-nightly (various attempted) Vibrant I am using will connect to my laptop and my other desktop, but not to my Asus P8Z68-V Pro (either directly or through a hub, through the USB3 controller and USB3 + hub). I have also tried a separate stock Vibrant, same results. All I get on my uber-rig is charging
one thing that HAS worked (in a limited fashion) is using the hub built in to my Razer Tarantula keyboard, however its USB 1.1 and cant supply the proper voltage. So code 43 becomes code 10 (This Device Cannot Start [USB Hub Power Exceeded]), still no functionality.
fortunately my mobo has a built in bluetooth module and I can just push things around with that. slowly... Will be keeping an eye out for bios and chipset updates to see if they resolve, and in the future may try an add-in USB2 card
Hi!
Well, after few weeks with my nice S3, yesterday I finally had time to try to root and mod my phone, but things seems to be worst in advance, so I woul like to ask for some help...
1) At first, I never plug my phone on my pc since I bought it, since I put all my stuff on sd card with an textternal usb reader/w and put in and everything works nice.... however when I yesterday try to put my phone in usb download mode, I found that it was NOT recognized in usb in any way (no MTP, no usb device and not usb Download Mode) by my vista windows install on my laptop (I use more kubuntu but keep the original vista install that came with my machine for the rare times that I need to run something on windows).
Ok, so, I then read post, search and follow sugestions about remove drivers, reinstall Kies, remove kies, reinstall, then install only the drivers for T-mobile version, and also uninstall everything and reinstall again with the ToolKit 4.0... but again NO results and S3 not recognized on my machine...also tested with others micro usb cable (1 generic and one oem motorola)...
2) Again and follow posts... I borrow anotehr laptop with a Win7 install that NEVER had installed Samsung drivers or Kies... so I installed Kies, and drivers only for try to at least get my S3 recognized by Kies by USB cables... same NO successs...
3) So, then I came to my Kubuntu install and try at first a flash of recovery with Heimdall... so It was recognized and completed the flash of recovery, But I found that I use a STOCK recovery file... son when I try to acces recovery, I get it but again it was the same stock recovery....
4) Here is the weird part... after this first Heimdall flash, the Flash counter appears with 1 count, BUT now Heimdall also dont recongnizes my S3 with this error:
Initialising connection...
Detecting device...
Failed to detect compatible download-mode device.
I wonder if after first count may the Stock S3 may be block the usb connection for dwonload mode until some sort of stock software, that may reset usb and allow it to enter in download mode again... also wonder if may be some hidden menu optioon for reset/test thet usb port or for change it form MTP to USB storage mode thatmay NOT requiere ROOT since I not see by now a way to get root withouth usb access detected in pc.
So, by now, I am still lucky in that my phone is booting fine on stock android and charges and everything seems normal, except that there is no way to make it recognized in usb connection of any type, none Linux, vista o win7...
5) I then try at a last resort to try to get root, to try to use STOCK recovery to try to flash a zip with CWM recovery inside, but give a error of validation and no flash nothing...
6) By now I wonder how could be reset or wake up the usb since seems a common issue with S3 but almost everything that I found refers to solution when the phone is already rooted, and if not rooted all I found is the same suggestions about uninstall/reinstall drivers/kies but nothing else...
So, I remember that when I used a Moto XT720, one of the ways to make it custom roms, was a zip that was proper prepared by a dev, that include a version of CWM zipped inside a file named update.zip that could be flashed temporaly by Stock recovery "flash update" option of stock recovery menu, and then it Boots to CWM recovery that finnally allows to flash custom roms properly inside the phone and WITHOUT usb access... so I wonder if somebody may know/help with a similar solution for S3 that dont get USB access for get flased roms or root...
So, as I post above, by now I fell enough lucky to have my phone booting-up normal and charging, but feels that I caged since I not see a way to get root or custom roms other that have an usb fully recognized by pc and seems that this could be an issue of the stock firmware that may be happen... so I would like to ask for help suggestions and proece with extremely care before doing any other attemps to root since I would like to solve how to maintain a reliable usb connection open and recognized status and/or a way that may be possible to install CWM recoveery with an update.zip file form stock recovery, and from there the advance may be safer....
Thanks for read and any help/suggestion will be very appreciated.
Best regards to all.
Well... Really worry now...
And by now I test several attemps of the same tricks plus a suggestion on other post, about reset factory, fully charge S3 (somebody talks that in their case the S3 refuse to connect if battery level is under certain 85% level and the USB connect in Battery Charge mode only and above level of charge allow MTP connection), and also a suggestion about factory reset and a leaving the phone without battery by a while ( I leave mine by 12 hours...)....
Still no way to connection trough usb...
So any help or suggestion for reset USB operation mode (in order to get my S3 detected in PC) or to get Root access from Stock recovery "apply update from external Card", may seems the possible solutions.
Please if could be some help, no answer/posts by now, so hope tha this could not be a BUMP... :-/
Thanks for read and if please some help...
Best regards!
Standard reply
One not using Samsung USB cable
Two Not using drainboard USB port .
Three try turn on or off USB debugging .
jje
JJEgan said:
Standard reply
One not using Samsung USB cable
Two Not using drainboard USB port .
Three try turn on or off USB debugging .
jje
Click to expand...
Click to collapse
Hi!
Ok, first of all thanks for reply...
1) I already try with an Motorola OEM cable from a Droid 3 and with a generic micro-usb no brand (As I found by now seems that is S3 have a new usb pinout with 11 pins port) so may be need a new cable with 11pins or may believe that a standard micro-usb cable (like mine Droid 3 oem cable) may be better for debug this issue.
2) Please excuse my dumb question, but what is a drainboard USB port? (by now all my tests are directly to the usb ports of my laptop that are working fine in any of the 3 that it have and recognizes other phones, usb memories and other usb devices in any of them), so I wonder about what is a drainboard USB port and if it may be a clue to try to fix this...
3) Ok, by now I did my testing try to turn on/off usb debugging in several of the tests without any sign of change in usb port status of my S3, may be possible some additional setting in stock rom that may affect usb port status aprt of Debugging On/Off?
Thanks again for take tiem for answer and any additional help will be very gartefull
P.D. Today I still did some testing try same about kies on/off, turn on/off laptop with phone connected/unconected, etc, and still usb port still in charging mode only... Thanks again.
Hi!
Well, I finally got my usb work and was due a combination of wipe and original cable (and combination of this factoirs in my previous attemps...so I would like to thanks again to JJEgan since with their "standard reply" kick me to start a new round of tests and I found some details that would like that would like to share if may help somebody else that may look in this thread....
As many other people post previously thet Samsung original cable that came with S3 is really faulty (as many others friends found and post before), but I didnt found in previous posts if somebody look why this (simple after fix didnt look more about), so I was curious and checked it, and at least to my sight (that not may be the 20/20 but close, and I checked with a magnifying glass...), so these are some details that appears to my eyes:
1) The Samsung S3 usb conector seems that have somewhat more tiny contacts plate that other phones (including samsung as I checked with my Captivate Glide), so the contact with a cable seems to be somewhat loose in many cases...
2) In my case the diference was with a Droid 3 oem cable that when is checked carefully against the Samsung S3 original cable and Samsung Glide original cable, the Moto oem seems that have the internal wire contacts inside the micro usb conector of the usb cable, more "curved" to the center of the slot of the micro usb cable conector that the Samsung ones (in fact the Samsung seems almost planes in comparison). So I believe that my previous attemps with Moto cable may fail because I didnt full wipe my S3 at that time of test with moto cable.
3) I also receive and tested today an HDTV Adapter TIP (5 to 11 Pin Converter-Samsung EPL-FU10BEBSTA) and I gald to confirm that It works wonderfully with my Glide HDTV adapter (Skiva MHL (Micro USB) to Female HDMI Adapter (1080p Supported)), so it seems a fine piece, BUT the curious detail is that this HDTV Adapter TIP have a really visible longer metalic connector (more than 1mm more) that the metalic connector in the S3 original cable, and when the HDTV Adapter TIP is inserted in S3 it goes fully inside (so apart of somewhat tiny internal plate, seems that the connector is in fact more deep inside S3 than other phones).
4) I also tested the moto cable with HDTV Adapter TIP and it didnt work to make a data transfer connection but make charging of S3 so the connectio is made but not recognized through the HDTV Adapter TIP for data access (but again HDTV siganl of the Skiva adapter works fine).
5) So, my resume for people that may have this issue is:
a- Find a usb cable that may have more curved wire contacts inside prefer oem cables that may have better quality.
b- Test on a windows machine with the LAST AVAILABLE version of KIES and allokies to download their last driver version that may it install.
c- When everything is set, if possible test usb cable and port in copmpuetr with another phone and better if could be another samsung model so You could check that kies is working fine.
d- First plug usb cable in computer and then in S3 and if nothing happen try to move VERY GENTLY AND SOFTLY the micro usb plug connected in S3 in order to try that the really tiny wires of the plug may reach god contact, or try several times to plug and unplu micro usb connector in S3 port (try counting to 10 between plug-unplug).
e- if the above didnt works I may suggest try on another coputer that may have win 7 in order to test better.
In my case the diferences was made with step d of the above comment.
So, by now thanks to people that read this post and best regards to all.
I also have problem with flash SGS3 (GT-I9300) via heimdall 1.3.2 under Ubuntu Precise.
Phone was recognized by Linux but flash was failed.
I haven't any Windows computer to test.
heimdall flash --recovery recovery.img --verbose
.....
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Failed to initialise protocol!
PS
I use USB cable supplied with phone
So i have a motorola razr xt910 and i was running the jellywiz rom before this thing happened. So what i did was, boot into bmm recovery, restored cid, did a full wipe and immediately tried to flash the mokee rom. When it was done, i rebooted and got a FASTBOOT FLASH FAILURE. Later, i tried to use RSD lite to fastboot it back to europe ics but the com did not detect the phone. I tried lots of stuff
1. Tried another pc
2. Reinstalling the drivers
3. Tried different cables even the motorola OEM one
4. Spent money to replace the micro usb port on my phone
5. Factory resetting my phone a few times
6. I tried with my friend's razr on a pc with all the appropriate drivers, the pc could detect my friend's phone but not mine
But all of them did'nt work, it is still stuck in fastboot flash failure for 3 weeks now. Any solutions? Thanks in advance
http://forum.xda-developers.com/showthread.php?t=2431617
I had a very similar problem- the proper cable was necessary for my computer to recognize the phone. I uninstalled all of my USB drivers, and let windows reinstall them. This has helped with my SGS3 for recognizing the device. I used RSD 5.7, and having adequate power is imperative.
EDIT
When I say I reinstalled the drivers, I don't mean the Moto drivers. I uninstalled my USB device drivers in Control Panel> Device Manager, and then I reinstalled the motorola device manager, which reinstalled the motorola drivers. However, if your computer doesn't even recognize an unknown USB device connected, then it sounds like either A) a USB cable issue, or B) a USB A port issue.
LuckiestNut419 said:
http://forum.xda-developers.com/showthread.php?t=2431617
I had a very similar problem- the proper cable was necessary for my computer to recognize the phone. I uninstalled all of my USB drivers, and let windows reinstall them. This has helped with my SGS3 for recognizing the device. I used RSD 5.7, and having adequate power is imperative.
EDIT
When I say I reinstalled the drivers, I don't mean the Moto drivers. I uninstalled my USB device drivers in Control Panel> Device Manager, and then I reinstalled the motorola device manager, which reinstalled the motorola drivers. However, if your computer doesn't even recognize an unknown USB device connected, then it sounds like either A) a USB cable issue, or B) a USB A port issue.
Click to expand...
Click to collapse
Sorry for the late reply and thanks for trying to help. Okay so I tried what you said, I uninstalled the USB device drivers and let windows reinstall them rebooted my pc then reinstalled motorola device manager. When i plugged in my phone, the pc still did not detect it although i was using a motorola oem cable fresh from the box. It is definitely not a USB port issue as I tried pluggin in my mouse and omy thumbdrive into the other ports and it could detect them and install the drivers. So any solutions? I'm starting to miss her.
Do you have access to the fastboot menu at all? Any of the options, aside from AP fastboot? What is the battery status?
LuckiestNut419 said:
Do you have access to the fastboot menu at all? Any of the options, aside from AP fastboot? What is the battery status?
Click to expand...
Click to collapse
I have access to the fastboot menu all the options available and the battery is OK. Its just that when i plug it in to the pc it does not detect the phone.
Will the PC recognize the phone under any of the other boot options? (BP Tools, diag, BP SBF flash, Recovery, etc.) When I got to the point where my power source was adequate, and all I had trouble with was PC-Phone recognition, I purchased an OEM Moto charger from Verizon with a cable that said "factory data" on it. I wish I could be of more help, but that was the last step to fix my problem. It recognized immediately, and I successfully flashed. It sounds like you've covered all your bases on the PC end. Let us know if you find a solution!
LuckiestNut419 said:
Will the PC recognize the phone under any of the other boot options? (BP Tools, diag, BP SBF flash, Recovery, etc.) When I got to the point where my power source was adequate, and all I had trouble with was PC-Phone recognition, I purchased an OEM Moto charger from Verizon with a cable that said "factory data" on it. I wish I could be of more help, but that was the last step to fix my problem. It recognized immediately, and I successfully flashed. It sounds like you've covered all your bases on the PC end. Let us know if you find a solution!
Click to expand...
Click to collapse
Thanks for your concern. The pc did not detect the phone in an of the other options so the last resort is using that cable. Is it the same as the factory cable, can i make one myself cause i have a soldering iron at home. Or ordering one online would be better?
I would say go ahead and make one. Just beware, a lot of USB cables (most) have either rubber or hot glue molded around, so it is difficult to expose the contacts on the Micro B connection. There is a great tutorial by MotoCache1, located HERE, that will give you the rundown. It's worth a shot. My only concern is that the idea of the factory data cable is to trick the phone into thinking there is a good power source (without a battery/dead battery). I would think that finding the right USB cable would effectively solve your problem, but go for it, and let us know how it works. You can order the cable (if TeamBlackHat has them... or you can find one sold out of Cali on Ebay, I've heard), and that may be the ticket. Good luck.
LuckiestNut419 said:
I would say go ahead and make one. Just beware, a lot of USB cables (most) have either rubber or hot glue molded around, so it is difficult to expose the contacts on the Micro B connection. There is a great tutorial by MotoCache1, located HERE, that will give you the rundown. It's worth a shot. My only concern is that the idea of the factory data cable is to trick the phone into thinking there is a good power source (without a battery/dead battery). I would think that finding the right USB cable would effectively solve your problem, but go for it, and let us know how it works. You can order the cable (if TeamBlackHat has them... or you can find one sold out of Cali on Ebay, I've heard), and that may be the ticket. Good luck.
Click to expand...
Click to collapse
Thanks for the tip. I will give it a shot when I have the time. However I was wondering why my phone would run into such a problem. Before that when i flashed roms and soft bricked it, i could still recover it using rsd lite and fastboot files. Secondly, my usb cable was woking fine until just before i landed into this mess. The phone could not be detected by the pc in usb storage mode so i resorted to using google drive instead of actually solving the problem.
By the way, could i have the model number of the motorola oem factory data cable you bought. I dont live in the US so i may need to buy it from another shop. Thanks!
You may very well have a hardware problem, if you were having connection problems before the fastboot errors. Could be the contacts on the micro female in your phone. It sounds like you definitely have a data transfer problem if you couldn't mount for mass storage.
The only number I could locate is SKN6430A.
Sent from my XT912 using xda app-developers app
LuckiestNut419 said:
You may very well have a hardware problem, if you were having connection problems before the fastboot errors. Could be the contacts on the micro female in your phone. It sounds like you definitely have a data transfer problem if you couldn't mount for mass storage.
The only number I could locate is SKN6430A.
Sent from my XT912 using xda app-developers app
Click to expand...
Click to collapse
I already replaced the micro usb port on my phone after i bricked it but it still did not work. How to solve a data transfer problem? Thanks.
Appropriate USB cable, unfortunately. Motorolas are very picky. Even if you weren't having problems with a particular cable before, like me (fastboot flash would start, but not finish, first time I encountered a problem), the right cable solved my it. OEM Motorola data cable.
Sent from my XT912
LuckiestNut419 said:
Appropriate USB cable, unfortunately. Motorolas are very picky. Even if you weren't having problems with a particular cable before, like me (fastboot flash would start, but not finish, first time I encountered a problem), the right cable solved my it. OEM Motorola data cable.
Sent from my XT912
Click to expand...
Click to collapse
Okay I guess it all goes down to the cable. I've got a SKN6378A from motorola but it doesn't work. So what is the appropriate cable i should get or should i just send my phone to the motorola service centre and ask them to help me solve it?
I'm certain they can diagnose the problem, though I couldn't say for certain what the cost would be. You may have better luck purchasing a used phone on eBay. I can understand your frustration, to an extent, though you're problem is turning out to be more complicated than mine! Motorola tech support may also be able to help, remotely.
But But Were
LuckiestNut419 said:
I'm certain they can diagnose the problem, though I couldn't say for certain what the cost would be. You may have better luck purchasing a used phone on eBay. I can understand your frustration, to an extent, though you're problem is turning out to be more complicated than mine! Motorola tech support may also be able to help, remotely.
Click to expand...
Click to collapse
Hey I Know You Said You Already Tried Using A Different Computer But Were They Different Operating Systems? I Had A Similar Problem RSDlite Wouldn't Recognize My Phone On Windows 8 But Connected Just Fine On Windows 7.
fastboot not detected
while the PC recognize the phone under any of the other boot options BP, Tools, diag (here the phone goes black), BP SBF flash, Recovery, why the fastboot is not recognized? im on a xt910, i have no system.. and i remember that previosly, he wasnt able to be recognized even as an mass storage... so weird.. then i messed up, and i cant do nothing because all the do able thing is via fastboot.. is there any chance to do something via recovery stock without getting operation aborted?.. oh, another hint, i mess a little with the entry of the female usb on the xt910, and now i have an "unknown device" maybe is broken.. and if i disarm it, and i cut a cable, and green and white should be data, maybe ill be able to flash something via rsd.. damn is so weird that the bp is recognized in rsd but fasboot not.. and i cant buy nothing, i just have a knife, two cables(i cutted one to put the negative positive directly to the battery) and wi fi. thanks in advances, and yes i know that is an old thread, but i dont know what else to do. /And sorry for my english, i dont speak it.
Hi guys, can someone explain me why I can't restore original firmware? I've tried a lot of cables and a lot of PCs. I've also tried to reinstall drivers but nothing happens. Every time I connect the phone to the pc I get "Usb not recognized" error. Could it be the connector? Because I'm able to repair it if this is the problem.
Thanks a lot.
did you install Kies?
Yes I did. I'll change the USB board. I hope to solve this problem.
I've changed the USB board and the PC initially has recognize my phone, but once I pressed START in Odin, the PC didn't respond more to the commands, also the phone didn't display the download status bar. Now, I've seen there are many version of the USB board. The one that was in my phone was the 0.8 version, and the one that I bought was the 0.6. My last test will be to buy the newest version, hoping to restore my phone.
Hi guys
I've just received Tanix TX9S android box and I'm trying to flash a custom rom but my computer doesn't detect the box. I'm using Win 10 Pro 64bit and I've tried reinstalling the burning tool, installing with driver signature off, restarting, changing usb ports on both the pc and the box but it just doesn't work. I'm using this cable: https://www.aliexpress.com/item/4000574237363.html
Any ideas?
kalehrl said:
Hi guys
I've just received Tanix TX9S android box and I'm trying to flash a custom rom but my computer doesn't detect the box. I'm using Win 10 Pro 64bit and I've tried reinstalling the burning tool, installing with driver signature off, restarting, changing usb ports on both the pc and the box but it just doesn't work. I'm using this cable: https://www.aliexpress.com/item/4000574237363.html
Any ideas?
Click to expand...
Click to collapse
Cable Looks Quite Thin, It Says IUts A Data Cable So Should Work Just Might Not Provide Enough Power, Try Connecting Power At Same Time, that may help, or you might have to use mask rom mode to force your box to be detected
I tried connecting power but to no avail. I don't think I will be opening the box so I'll have to live with stock ROM
kalehrl said:
I tried connecting power but to no avail. I don't think I will be opening the box so I'll have to live with stock ROM
Click to expand...
Click to collapse
Aww, something you should try, when you eventually upgrade and it becomes a spare device
Maybe I can try with an sd card.
I also have some logs in amlogic folder.
I've noticed 'NoDeviceConnected' error and sometimes 'Other device'.
kalehrl said:
Maybe I can try with an sd card.
I also have some logs in amlogic folder.
I've noticed 'NoDeviceConnected' error and sometimes 'Other device'.
Click to expand...
Click to collapse
Yhea SD Card Is Another Option, i Just Generally don't recommend This Method as if you flash a incompatible firmware and your device wont turn on then USB Burn Tool Will Be needed To Fix And Flash From a "Bricked" State
I managed to flash my box.
I used the latest burning tool v3.1.0. During the installation, I plugged my box into the computer and saw that it not only installed world cup drivers, but additional ones as well which was a good sign. I also had to use the power supply because usb didn't output enough power.
kalehrl said:
I managed to flash my box.
I used the latest burning tool v3.1.0. During the installation, I plugged my box into the computer and saw that it not only installed world cup drivers, but additional ones as well which was a good sign. I also had to use the power supply because usb didn't output enough power.
Click to expand...
Click to collapse
I have the same issues. At the moment that you plugged in your box with usb cable was your box already on power? en did you have to use the reset by toothpick reset at the time you plugged in?
BUZZTV XRS4900
Yes, already on power and I used a toothpick.
But flashing is hit and miss with amlogic burning tool.
Sometimes it works, sometimes doesn't.
Try a different computer because for one of my boxes I had to use a Windows 7 machine.
kalehrl said:
Yes, already on power and I used a toothpick.
But flashing is hit and miss with amlogic burning tool.
Sometimes it works, sometimes doesn't.
Try a different computer because for one of my boxes I had to use a Windows 7 machine.
Click to expand...
Click to collapse
Thank you.. I tried several options and cables and pc's.
When on power the toothpick doesn't work because it is already operational i guess
I try the mask rom method. Hope that will do the job
kalehrl said:
I managed to flash my box.
I used the latest burning tool v3.1.0. During the installation, I plugged my box into the computer and saw that it not only installed world cup drivers, but additional ones as well which was a good sign. I also had to use the power supply because usb didn't output enough power.
Click to expand...
Click to collapse
this doesn't sound like a good sign to me... world cup drivers !!??
I've yet to flash my box and I'm really put off by the fact that guides mention to ignore virus warnings and just to click OK. I haven't yet seen it uploaded onto xda either which makes me confident.
Try older versions of the Amlogic USB Burning Tool, newer versions might not work with older boxes.
You can find most of the versions here: Amlogic USB Burning Tool - All Versions
The problem was the cable. The Chinese one I bought first didn't work properly. The cheapest one from Amazon worked fine.
Same here mine to does not detect but i have noticed in device manager it appears an unknown device
Reinstall the driver.
EdT586 said:
Try older versions of the Amlogic USB Burning Tool, newer versions might not work with older boxes.
You can find most of the versions here: Amlogic USB Burning Tool - All Versions
Click to expand...
Click to collapse
thxy men, i tried use the latest version and don't work, after saw ur comment i can revive my tv boxes