Related
I am trying to flash my vibrant to stock, but my laptop says usb unrecognized.This causes Odin not to detect my vibrant in download mode. I have downloaded all drivers including nexus drivers, but still same error usb unrecognized. I have then start on switching data cables including the stock data cables but the errors remain the same. I have tried on different computers and different windows, nothing working its the same errors on all computers. I have messed up by formatting everything in the Vibrant, now it boot loops to Vibrant logo. I can get into download mode normal but I cant get into CWM or any recovery mode, its probably because I have formatted the whole phone. When the phone is off, I plugged in the micro USB to the phone from the laptop, all it shows is the white lines that are in circler motions and then freezes. Weird my laptop still detects it as a USB unrecognized. As the phone is plugged in to the laptop I try taking the battery out and my phone is still on with the frozen screen of those white lines in circler Motions. Can anyone help me, or at least explain to me what the problem may be? My thoughts is that it may be a hardware problem. If so can anyone provide me some schematics on the USB portion? I hope we can bring some light on this problem. Giving it to T-Mobile is not an option. I have dealt with many problems and solved it, but this is one problem that keeps me stomp in my own tracks.
You can give a man a fish and he will eat for a day, but if you teach a man to fish, he will be able to eat for a lifetime!
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Woodrube said:
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Click to expand...
Click to collapse
I agree with you, it may be a HW issue. I have tried connecting other phones to my laptop and it reads it just fine, but for my vibrant no success. Im gonna go ahead and actally open it up and check on some componets, i have a feeling that it may have burnt one of the componets due to over charge. Ill get back with you on my findings. Keep me updated on your progress.
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Woodrube said:
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Click to expand...
Click to collapse
yes i've tried. I used a Q-tip and some alcohol, still same problems.
Update: Nothing!! How about you?
I have tried un/reinstalling the drivers, Odin v1.8, 1.3 and 1.0, about 4-5 cables and all 3 ports. I have cleaned the USB with alcohol and at this point am at a slight loss. The phone boots into DLmode and charges fine, so I don't think it is a faulty USB port. I cannot get into any recovery or ROM boot. All I have is DLmode and the GB bl screen. No kernel or ROM splash.
Gasp! I'm in a similar boat guys. My phone charges fine, and all my drivers are working and up to date...I can get into DL mode and all that jazz...phone even boots up and works! (fortunately)...but no dice on it being recognized by my or any computer. Glancing into the port, it looks like there may be some corrosion on the left hand side of the port, or some sort of damage...can't really tell without a proper magnifying glass. but it does look damaged or at least irregular. I've been reading around, and cleaning sounds like a potential solution...I've no idea how you guys are cleaning with giant q-tips lol but hopefully I can figure that one out also and give it a whirl xD But in the mean time, I sure hope somebody can come to the rescue
I don't know if this can help you guys, but this is how i hard bricked my vibrant few months ago. I get into download mode trying to get back to stock from ICS and my computer didn't recognize my phone....after a couple of hours my phone was completely dead and after a few days of research i brought it back to life using the unbrickable mod. What i'm thinking now is to use the Unbrickable Resurrector but you will need Linux...it always worked for me but i'm not sure if you need the unbrickable mod already applied. However i think if you have Linux installed you can have a try. Here is the link for the unbrickable resurrector http://forum.xda-developers.com/showthread.php?p=17135277#post17135277
Hi all,
I am experiencing intermittent USB host (OTG cable) connection on Samsung Galaxy S2, Android 4.0.3 (stock unrooted but exotic brand).
I've spotted this when trying out Helicon Remote app with a Nikon D90 camera. Connects and shows live image from the camera and other signs of operation for a few seconds, then disconnects, connects again, disconnects etc, then the app complains over connectivity and suggests to restart the camera...
Similarly, flashdrives are first mounted, then unmounted unexpectedly, then reported as damaged (though still fine on a PC and chkdsk finds nothing).
I believe it is not cable-related because I've tested 3 different OTG cables for the S2, two of them new, and one of them had once worked fine with flashdrives. But that was with Android 2.3.6 before upgrade to ICS, and I also had to replace the USB&MIC board in the phone due to a charging problem (both rev.2.2) in between.
USB Host Diagnostics says GT-I9100, IML74K/XWLPD, verdict Yes/Full. But the test is not long enough I guess.
Normal USB storage connection to PC still works fine (normal cable not OTG for this one).
Should I try another USB&MIC board, or is this more likely a software issue? I've managed to google up a couple of similar case with flashdrives, with no solution, maybe didn't use good keywords. Any suggestions?
_sem_ said:
Hi all,
I am experiencing intermittent USB host (OTG cable) connection on Samsung Galaxy S2, Android 4.0.3 (stock unrooted but exotic brand).
I've spotted this when trying out Helicon Remote app with a Nikon D90 camera. Connects and shows live image from the camera and other signs of operation for a few seconds, then disconnects, connects again, disconnects etc, then the app complains over connectivity and suggests to restart the camera...
Similarly, flashdrives are first mounted, then unmounted unexpectedly, then reported as damaged (though still fine on a PC and chkdsk finds nothing).
I believe it is not cable-related because I've tested 3 different OTG cables for the S2, two of them new, and one of them had once worked fine with flashdrives. But that was with Android 2.3.6 before upgrade to ICS, and I also had to replace the USB&MIC board in the phone due to a charging problem (both rev.2.2) in between.
USB Host Diagnostics says GT-I9100, IML74K/XWLPD, verdict Yes/Full. But the test is not long enough I guess.
Normal USB storage connection to PC still works fine (normal cable not OTG for this one).
Should I try another USB&MIC board, or is this more likely a software issue? I've managed to google up a couple of similar case with flashdrives, with no solution, maybe didn't use good keywords. Any suggestions?
Click to expand...
Click to collapse
As you have tried with 3 different cables I guess it's a software issue, most probably the usb host driver's settings must be corrupted , try a factory reset, and if that doesn't work flash with a stock firmware, try upgrading to Jelly Bean or if you like ICS getting the same firmware and re flashing ain't a bad idea, also since you are rooted try flashing through Mobile Odin if you don't want to go through the hassle of flashing through the computer.
Edit : I don't think it could be a hardware problem as the device when it becomes a slave device works normally and is only having this issue when it becomes master device, only after trying above things you need to think about a replacement.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
As you have tried with 3 different cables I guess it's a software issue, most probably the usb host driver's settings must be corrupted , try a factory reset, and if that doesn't work flash with a stock firmware, try upgrading to Jelly Bean or if you like ICS getting the same firmware and re flashing ain't a bad idea, also since you are rooted try flashing through Mobile Odin if you don't want to go through the hassle of flashing through the computer.
Edit : I don't think it could be a hardware problem as the device when it becomes a slave device works normally and is only having this issue when it becomes master device, only after trying above things you need to think about a replacement.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Tnx. I thought that'd be one way to start. But I'm not so proficient in this flashing business. I think the ICS update brought me less good than hassle, I've wasted a couple of days fixing things. I'm not rooted yet and I was also considering warranty service, but that'd mean trips to the centre and a week without the phone, and I'd want a thorough backup first and that'd require rooting and unrooting AFAIK... ugh. They're probably better for flashing than me, but I guess they might have not tried OTG in their lives
I was wandering if somebody here knows something about the cause of such specific issue, where a working connection drops after a few seconds.
_sem_ said:
Tnx. I thought that'd be one way to start. But I'm not so proficient in this flashing business. I think the ICS update brought me less good than hassle, I've wasted a couple of days fixing things. I'm not rooted yet and I was also considering warranty service, but that'd mean trips to the centre and a week without the phone, and I'd want a thorough backup first and that'd require rooting and unrooting AFAIK... ugh. They're probably better for flashing than me, but I guess they might have not tried OTG in their lives
I was wandering if somebody here knows something about the cause of such specific issue, where a working connection drops after a few seconds.
Click to expand...
Click to collapse
Flashing a stock rom of the same region of your device won't actually void your warranty, you don't need root for that if you are doing it via PC Odin, but since you're not sure I won't recommend it, and I had something similar with my Galaxy Tab 7 plus with stock honeycomb, the connection flickers the first few attempts (I have tried more than 10 time's), first time connected and BAM suddenly some weird error, then it always on connection showed device corrupted, then after some time BAM!! Connected, then normal use, my God!! I also had to face the write_media_storage permission problem too, but all in all I upgraded, then flashed and flashed and finally reached JB aah smoothness bonanza USB OTG works like a charm.
Edit : and for the record Galaxy Tab 7 Plus is S2 with a large ugly screen.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
Flashing a stock rom of the same region of your device won't actually void your warranty, you don't need root for that if you are doing it via PC Odin, but since you're not sure I won't recommend it, and I had something similar with my Galaxy Tab 7 plus with stock honeycomb, the connection flickers the first few attempts (I have tried more than 10 time's), first time connected and BAM suddenly some weird error, then it always on connection showed device corrupted, then after some time BAM!! Connected, then normal use, my God!! I also had to face the write_media_storage permission problem too, but all in all I upgraded, then flashed and flashed and finally reached JB aah smoothness bonanza USB OTG works like a charm.
Edit : and for the record Galaxy Tab 7 Plus is S2 with a large ugly screen.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if stock JB is ready at my operator. I've had second thoughts about updating via cable when the USB port is under suspicion. And I hear about nasty developments from Google in recent updates. Since which version is the write_media_storage permission issue?
Btw I've just read in another thread someone found root was required for USB OTG in stock JB?
Is it possible that some odd permission thing would kill USB host comm only after a few seconds?
_sem_ said:
I'm not sure if stock JB is ready at my operator. I've had second thoughts about updating via cable when the USB port is under suspicion. And I hear about nasty developments from Google in recent updates. Since which version is the write_media_storage permission issue?
Btw I've just read in another thread someone found root was required for USB OTG in stock JB?
Is it possible that some odd permission thing would kill USB host comm only after a few seconds?
Click to expand...
Click to collapse
No, you don't need root for USB OTG in S2, in some devices yes but S2 no... Because it was one of the widely announced feature during it's release and you don't need to concern about the permission issue.. it's honeycomb only lol.
Edit : I mentioned the permission issue just to show you that I had to go through a lot of trouble connecting OTG with my Tab and on upgrading it with JB everything became smooth as butter. The S2 has never had or never will have this problem.
Sent from my GT-P6200 using xda app-developers app
---------- Post added at 02:48 AM ---------- Previous post was at 02:31 AM ----------
Since you're reluctant to flash via a micro usb port under suspicion I have an idea to flash without touching the computer.. It's actually safe I guess in comparison. It's actually like this :
1.Root device using Exynos Abuse App(I guess you will trigger the counter though)
2 .Install Mobile Odin App
3.Flash your stock firmware via Mobile Odin.
4.Done and Done.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
No, you don't need root for USB OTG in S2, in some devices yes but S2 no... Because it was one of the widely announced feature during it's release and you don't need to concern about the permission issue.. it's honeycomb only lol.
Edit : I mentioned the permission issue just to show you that I had to go through a lot of trouble connecting OTG with my Tab and on upgrading it with JB everything became smooth as butter. The S2 has never had or never will have this problem.
Click to expand...
Click to collapse
I see that was actually an S2 plus (minus?) :laugh:
I'd assume the phone would first check permission, then start talking. This here looks so weird, like it starts normally, then does some periodic check and kills it, reminds me of one piracy protection scheme
_sem_ said:
I see that was actually an S2 plus (minus?) :laugh:
I'd assume the phone would first check permission, then start talking. This here looks so weird, like it starts normally, then does some periodic check and kills it, reminds me of one piracy protection scheme
Click to expand...
Click to collapse
Ah lol now I understand what you're referring to about that root requirements I saw your other post, in JB one thing was removed that is not USB OTG the thing that needs root is UMS or USB Mass Storage, ie if you have tried connecting to a computer in GB or ICS you can either connect via MTP or UMS for file transfer Samsung removed USB storage mode in JB update.
Sent from my GT-P6200 using xda app-developers app
I tried a couple more things, without changing anything.
The USB Host Controller app. I'm not sure if it is supposed to work correctly without root. On the Info tab it says
S3C USB host driver NOT found
Root hub present, USB host mode is active.
On the USB tab it does shoe the Nikon D90 camera when connected.
I've also tried an USB mouse but it doesn't show it, nor does the mouse light up, nor there is any mouse cursor.
Googling around I understand the mouse does not show up because of a Samsung "whitelist" blocking it. I gather more USB devices used to work earlier but the whitelist leaving only flashdrives mainly came with 4.0.3 update? I could only find hearsay, is there an official Samsung policy regarding this?
And there was a reference to a Siyah kernel which should restore this... or there are perhaps other popular ones that fix this?
And, since the mouse doesn't show up at all, I assume this whitelist has probably nothing to do with my original problem?
_sem_ said:
I tried a couple more things, without changing anything.
The USB Host Controller app. I'm not sure if it is supposed to work correctly without root. On the Info tab it says
S3C USB host driver NOT found
Root hub present, USB host mode is active.
On the USB tab it does shoe the Nikon D90 camera when connected.
I've also tried an USB mouse but it doesn't show it, nor does the mouse light up, nor there is any mouse cursor.
Googling around I understand the mouse does not show up because of a Samsung "whitelist" blocking it. I gather more USB devices used to work earlier but the whitelist leaving only flashdrives mainly came with 4.0.3 update? I could only find hearsay, is there an official Samsung policy regarding this?
And there was a reference to a Siyah kernel which should restore this... or there are perhaps other popular ones that fix this?
And, since the mouse doesn't show up at all, I assume this whitelist has probably nothing to do with my original problem?
Click to expand...
Click to collapse
Typing this using a mouse in stock rom.
Edit :As you can see that above statement is written using a mouse in pure stock JB, so I don't think Samsung has blacklisted anything and and the mouse used is some unknown weird brand. Since your mouse didn't even light up, I'll say it may be something other than host driver issue, because the host device will always provide the power, you may possibly be facing a hardware issue, the only thing that can assure that it's not a software issue is a flash using a stock rom, or try cm9 stable I recall that OTG worked perfectly in it. Since you're afraid of flashing via a computer, I'll tell you certain steps which will help you flash without using a cable or a computer :
1.Root using Exynos Abuse App (preferably chain fire's app) (search, read and download)
2 . Install Mobile Odin and set it up.
3.Download a stock rom or custom rom(you must read very carefully) , preferably JB.
4.Flash via mobile Odin.
5.make sure you read all related threads several times.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
Typing this using a mouse in stock rom.
Edit :As you can see that above statement is written using a mouse in pure stock JB, so I don't think Samsung has blacklisted anything and and the mouse used is some unknown weird brand. ....
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
So you think these are nonsense?
http://forum.xda-developers.com/showthread.php?t=1768119
http://poke64738.iphpbb3.com/forum/...-galaxy-s2-gt-i9100-usb-hid-support-t105.html
http://techblog.goelite.org/kernel-modifications-for-usb-client-devices-of-samsung-galaxy-i9100-s2/
http://forum.xda-developers.com/showthread.php?t=1246116
Notice it is SGS2 specific, not Samsung or ICS general. You are using a Galaxy Tab I gather?
I've tried three Logitech mice and one Labtec.
Not that I'd want to use a mouse (a keyboard might be more useful), just want to see what's going on with USB host.
_sem_ said:
So you think these are nonsense?
http://forum.xda-developers.com/showthread.php?t=1768119
http://poke64738.iphpbb3.com/forum/...-galaxy-s2-gt-i9100-usb-hid-support-t105.html
http://techblog.goelite.org/kernel-modifications-for-usb-client-devices-of-samsung-galaxy-i9100-s2/
http://forum.xda-developers.com/showthread.php?t=1246116
Notice it is SGS2 specific, not Samsung or ICS general. You are using a Galaxy Tab I gather?
I've tried three Logitech mice and one Labtec.
Not that I'd want to use a mouse (a keyboard might be more useful), just want to see what's going on with USB host.
Click to expand...
Click to collapse
Lol friend, I use a s2 also but also have galaxy tab 7+ which is just like a galaxy s2 but with a huge screen, like I was saying, Samsung may have created a whitelist with ics, but not in JB as I clearly used a mouse in JB, in my s2 I am using a custom kernel so I am not sure about stock in s2 but since now stock JB in my tab support it then stock JB in s2 should also support it. I am suggesting that Samsung must have removed the whitelist limitation in JB.
I am saying this whitelist thingy might be ics specific because in GB stock mouse used to work in my s2, I would have tested it out for you if it weren't ics, ics 4.0.4 stock kernel contains a dangerous brick bug and I don't wanna go anywhere near an ics stock kernel (even though there are other version's which are said to be safe, my heart ain't strong enough to take a risk with stock kernels)
Sent from my GT-I9100 using xda app-developers app
Hi all. I couldn't find a specific forum for my SII HD LTE (Bell Canada version - i757m) so I'm posting in here with hopes that someone can help me out.
My USB port appears to be toast. The phone will charge, but it not recognized by any computer I plug it in to. I've tested in with Odin on two machines with several cables in download mode, USB debugging mode with the SDK, and mass storage mode. The fact that it won't even get detected in download mode leads me to believe that it's a hardware issue. Is this common?
Edit: Tried to post a link but I'm too much of an XDA posting noob to do so (<10 posts)
Is this the same device / would it be compatible? It's only 10 bucks but I'd like to know if there is anything else I can try or any known issues / fixes for this problem.
Any advice would be great!
Thanks.
Have you tried to clean the port. That's a problem. Or mobile Odin if you want to flash some thing. Have you tried dif version of Odin?
That's a problem too.
andrewwright said:
Have you tried to clean the port. That's a problem. Or mobile Odin if you want to flash some thing. Have you tried dif version of Odin?
That's a problem too.
Click to expand...
Click to collapse
I've tried cleaning the port with a clean dry toothbrush as suggested for some other models without any luck. I've also used a version of Odin that I know worked on the phone a month or so ago so there's definitely something wrong on the phone's end of things. Since it's failing to get detected in download mode (before anything is really loaded) I'm almost positive it's a hardware problem - unless there is some obscure software issue that may be causing this.
I'm not using any custom ROMs at the moment and it just stopped working out of the blue.
Fairly certain I'm going to have to replace the actual hardware piece. I looked in it with a flashlight and everything looks clear / contacts are all in-place so I'm guessing something may have fried on the pcb that it's attached to. Possibly a short or something?
I've run into the identical problem.
It's quite an issue actually, because the stock experience is becoming really unbearable, and I can't find a way to root or install a custom Rom without USB.
Any solution?
I actually sourced the part for about 10 bucks on Ebay. Just arrived a few days ago. It includes the whole circuit board, ribbon cable, and USB plug. There's gonna be some disassembly required (obviously) but after testing every software solution in the book, cleaning the ever living crap out of it, and trying four different cables on multiple PCs, I'm positive the USB port / attached hardware bit the dust.
I'll post my results when I get around to putting the thing in.
i have a sgs3 i9300. i recently flashed the stock MJ9 android 4.3 firmware to it and it was working fine till 3 days ago when it started to show driving mode sign and then i flashed the rom again 2 or 3 times i wiped user data and now the driving mode sign is gone but i cannot connect the phone to the computer, when i connect it nothing happens, on mobile or computer. nothing. (no usb charging or mass storage or any sounds or anything) however i can charge it using usb charger that came with it and strangely i can even use the phone in download mode with computer to flash it using odin. i read somewhere that its not a hardware issue so im really looking forward to some help here. thanks
Many similar threads, lots of possible reasons. Best search for the most likely causes, which will include your pc, leads, phone hardware etc.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Many similar threads, lots of possible reasons. Best search for the most likely causes, which will include your pc, leads, phone hardware etc.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
tested it on different computer still the same. phone hardware should not be the issue since i am able to use it in download mode and charge it using the charger. so hardware port cannot be the problem.
codetoeternity said:
tested it on different computer still the same. phone hardware should not be the issue since i am able to use it in download mode and charge it using the charger. so hardware port cannot be the problem.
Click to expand...
Click to collapse
Search = the cable
JJEgan said:
Search = the cable
Click to expand...
Click to collapse
changed the cable. still the same. i saw another post about the same issue (quite old though and had no replies) and he was talking about some code like *#7280# (or similar code that opens up a hidden menu that allows to do something to fix it) but i opened that menu and those options werent there.
searched all over xda. tried all the things suggested (including the recovery firmware). still things remain the same. i still can flash it in download mode. but i cant charge it or anything. im sure its a software problem not a hardware problem. some serious help is required here
codetoeternity said:
searched all over xda. tried all the things suggested (including the recovery firmware). still things remain the same. i still can flash it in download mode. but i cant charge it or anything. im sure its a software problem not a hardware problem. some serious help is required here
Click to expand...
Click to collapse
Would suggest you uninstall Kies if you have it then download the new version (Kies for non Android 4.3 or Kies 3 for Android 4.3) from here Kies this will re-install the new drivers, re-boot your PC then plug your phone into your PC and you should get the message installing drivers.
Don't let Kies run at the same time as Odin otherwise it wont work but I guess you probably know that.
ag4751 said:
Would suggest you uninstall Kies if you have it then download the new version (Kies for non Android 4.3 or Kies 3 for Android 4.3) from here Kies this will re-install the new drivers, re-boot your PC then plug your phone into your PC and you should get the message installing drivers.
Don't let Kies run at the same time as Odin otherwise it wont work but I guess you probably know that.
Click to expand...
Click to collapse
done. still no use. since the device isnt even noticed by the computer. its like nothing is attached. however in download mode i get a lot of devices in device manager. im unable to charge my phone or connect as mtp thats the problem. i dont think the port is faulty coz the download mode works just fine.
USB port on the phone faulty or motherboard .
JJEgan said:
USB port on the phone faulty or motherboard .
Click to expand...
Click to collapse
in that case the phone shudnt work in download mode. i think.
codetoeternity said:
in that case the phone shudnt work in download mode. i think.
Click to expand...
Click to collapse
Have you tried different USB ports on the PC, there have been reports before that for some reason the port people normally use stops working and by switching to another USB port it works
Forgot to say if not already tried, turn off the phone pull the battery leave for a minute or two, replace the battery and reboot then try to connect it.
ag4751 said:
Have you tried different USB ports on the PC, there have been reports before that for some reason the port people normally use stops working and by switching to another USB port it works
Forgot to say if not already tried, turn off the phone pull the battery leave for a minute or two, replace the battery and reboot then try to connect it.
Click to expand...
Click to collapse
have tried different ports and different computers different cables etc and the battery was out all day still no use
codetoeternity said:
have tried different ports and different computers different cables etc and the battery was out all day still no use
Click to expand...
Click to collapse
Not having much luck are you, one last thing I have read before is using a pin or cocktail stick (you may need a magnifying glass as well) to gently clean the USB port on the phone and the cable, remove the battery first, but be careful you don't actually damage anything, that's why you need to be gentle with it.
Can you flash via ODIN successfully but phone not recognised by Windows??? Sounds like not all pins connecting properly. Clean connector VERY carefully...
Sent from my GT-I9300 using Tapatalk
ag4751 said:
Not having much luck are you, one last thing I have read before is using a pin or cocktail stick (you may need a magnifying glass as well) to gently clean the USB port on the phone and the cable, remove the battery first, but be careful you don't actually damage anything, that's why you need to be gentle with it.
Click to expand...
Click to collapse
i used a very sharp pin to clean the port on phone. did clean a bit, and had a bit of success. i cud charge my phone with the connector connected at a certain angle. if i wud touch it it would stop charging. but that went on for like 40 minutes and then it stopped working any ideas on how can i clean it? if i open the phone will i be able to clean it easily?
codetoeternity said:
i used a very sharp pin to clean the port on phone. did clean a bit, and had a bit of success. i cud charge my phone with the connector connected at a certain angle. if i wud touch it it would stop charging. but that went on for like 40 minutes and then it stopped working any ideas on how can i clean it? if i open the phone will i be able to clean it easily?
Click to expand...
Click to collapse
Never actually had to do it, only read what others have done, maybe an old dry toothbrush would do it as ling as you remember the gentle bit, if the pin did help then this could solve the problem for you it may simply be dust or dirt on the connections.
Would do both the phone and the cable end, not easy but worth a try as its free.
My N9 seems to have an issue with it's port as it can charge but I cannot get a pc to recognize it via adb or fastboot. All my other devices work fine on that pc. I don't even get the prompt to choose what mode to use when hooked to the PC nor does my PC recognize anything is connected. Anyway I'm running Slimrom currently but am ready to get rid of this tablet. Is there a way to revert to stock without having pc access? I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader. Does the N9 have that? I couldn't find any info so I'm assuming not. I have TWRP/Magisk so I could just sell/pass it on rooted running a rom too. Just thought stock would be better.
henderjr said:
My N9 seems to have an issue with it's port as it can charge but I cannot get a pc to recognize it via adb or fastboot. All my other devices work fine on that pc. I don't even get the prompt to choose what mode to use when hooked to the PC nor does my PC recognize anything is connected. Anyway I'm running Slimrom currently but am ready to get rid of this tablet. Is there a way to revert to stock without having pc access? I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader. Does the N9 have that? I couldn't find any info so I'm assuming not. I have TWRP/Magisk so I could just sell/pass it on rooted running a rom too. Just thought stock would be better.
Click to expand...
Click to collapse
Have you tried different USB cables and/or different USB ports on your PC? I've had problems in the past myself, with fastboot/ADB connections, and changing the cable or port has sometimes resolved such issues - might be worth a shot, if you haven't already tried it.
Hi, henderjr...
This method...
henderjr said:
...I know some HTC devices used to be able to flash a rom by putting it in the root folder and renaming the file something specific (model number) and then boot into bootloader...
Click to expand...
Click to collapse
...only works for 'true' OEM HTC devices, and whilst the Nexus 9 is manufactured by HTC, it's ostensibly a Google device, built by HTC under license from Google. And only Google make factory stock images for it...
Nexus 9 - WiFi
https://developers.google.com/android/images#volantis
Nexus 9 - WiFi/LTE
https://developers.google.com/android/images#volantisg
The method you refer to, was applicable on my old HTC One M8, and apparently it works for other OEM HTC devices too, but with the Nexus 9 - a Google device - there are no such factory stock images that can be 'placed on the root' for the bootloader to auto-flash.
There is only one way of reflashing the N9 back to factory stock, and that's via fastboot (or with toolkits that use fastboot).
The only other possible way, and I suspect it to be fairly unlikely you'll be able to do... is if you have TWRP installed as your Custom Recovery, and a previously created Nandroid (bare-bones) backup of factory stock stored somewhere on the internal storage of your N9. And then it'd be a relatively simple matter of performing a Nandroid restore. But, as I say, I very much doubt you'll likely have a Nandroid backup floating around somewhere on the device, given the size of such things.
Other than that, I can only suggest you tinker around with different cables/ports, and see if you can get a response from your PC, or maybe even try another PC, if you have access to one.
Hope this helps, and best of luck
Rgrds,
Ged.
GedBlake said:
Have you tried different USB cables and/or different USB ports on your PC? I've had problems in the past myself, with fastboot/ADB connections, and changing the cable or port has sometimes resolved such issues - might be worth a shot, if you haven't already tried it.
Hi, henderjr...
This method...
...only works for 'true' OEM HTC devices, and whilst the Nexus 9 is manufactured by HTC, it's ostensibly a Google device, built by HTC under license from Google. And only Google make available factory stock images for it...
Nexus 9 - WiFi
https://developers.google.com/android/images#volantis
Nexus 9 - WiFi/LTE
https://developers.google.com/android/images#volantisg
The method you refer to, was applicable on my old HTC One M8, and apparently it works for other OEM HTC devices too, but with the Nexus 9 - a Google device - there are no such factory stock images that can be 'placed on the root' for the bootloader to auto-flash.
There is only one way of reflashing the N9 back to factory stock, and that's with Google's factory stock images, which can only be flashed with fastboot (or with toolkits that use fastboot).
The only other possible way, and I suspect it to be fairly unlikely you'll be able to do... is if you have TWRP installed as your Custom Recovery, and a previously created Nandroid (bare-bones) backup of factory stock stored somewhere on the internal storage of your N9. And then it'd be a relatively simple matter of performing a Nandroid restore. But, as I say, I very much doubt you'll likely have a Nandroid backup floating around somewhere on the device, given the size of such things.
Other than that, I can only suggest you tinker around with different cables/ports, and see if you can get a response from your PC, or maybe even try another PC, if you have access to one.
Hope this helps, and best of luck
Rgrds,
Ged.
Click to expand...
Click to collapse
Wow long reply! Thanks for that. I've tried various cables and pcs (2). I have a handful of android devices and my N9 is the only one I can't get to work anymore. I might dig around and try a couple more cables just to be sure. It used to work a year or so ago on this same PC (my work laptop). It was temperamental then as I couldn't touch it at all or it'd disconnect. I kind of figured the HTC autoflash method (I had a EVO, M8, and M10) wouldn't work on it since I couldn't find anything when searching but thought I'd ask since I knew it was made by HTC. I'll likely wipe in TWRP and put one of the available ROMs on it with root and sell/give to one of my somewhat android capable friends. Thanks!
henderjr said:
Wow long reply! Thanks for that. I've tried various cables and pcs (2). I have a handful of android devices and my N9 is the only one I can't get to work anymore. I might dig around and try a couple more cables just to be sure. It used to work a year or so ago on this same PC (my work laptop). It was temperamental then as I couldn't touch it at all or it'd disconnect. I kind of figured the HTC autoflash method (I had a EVO, M8, and M10) wouldn't work on it since I couldn't find anything when searching but thought I'd ask since I knew it was made by HTC. I'll likely wipe in TWRP and put one of the available ROMs on it with root and sell/give to one of my somewhat android capable friends. Thanks!
Click to expand...
Click to collapse
You can get a new usb daughterboard for like $10 us on eBay. It took me about 15-20 minutes to change, and I've never done it before. Couple screws and ribbon cables.
If that's your issue. Pretty easy. Daughterboard has the USB port on it.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/202105962464
madbat99 said:
You can get a new usb daughterboard for like $10 us on eBay. It took me about 15-20 minutes to change, and I've never done it before. Couple screws and ribbon cables.
If that's your issue. Pretty easy. Daughterboard has the USB port on it.
https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/202105962464
Click to expand...
Click to collapse
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
henderjr said:
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
Click to expand...
Click to collapse
Hope it helps your issue. Be careful around the rear camera when you take the back off, it sticks to the cover a little. The little silvery pieces of tape are a little troublesome too. I've replaced the board on 2 Nexus 9s now. They even charge a little better too
madbat99 said:
Hope it helps your issue. Be careful around the rear camera when you take the back off, it sticks to the cover a little. The little silvery pieces of tape are a little troublesome too. I've replaced the board on 2 Nexus 9s now. They even charge a little better too
Click to expand...
Click to collapse
Thanks I read about the camera and how it likes to stick to the back. I ended up getting a cheap Fire tablet (HD 8") just to have something but would be nice to be able to wipe this thing and see if I can get it running ok. Currently on Slim it freezes and needs to be rebooted frequently.
henderjr said:
Thanks I read about the camera and how it likes to stick to the back. I ended up getting a cheap Fire tablet (HD 8") just to have something but would be nice to be able to wipe this thing and see if I can get it running ok. Currently on Slim it freezes and needs to be rebooted frequently.
Click to expand...
Click to collapse
You certainly do have to be careful with the camera assembly, when removing the back.
Around 3 years ago, I removed the back of my Nexus 9, and not being aware of the camera 'sticking-in-the-hole' problem, I accidently ripped the camera assembly wires/connector from its socket. No real damage was caused, but reconnecting it would have required the removal of a circuit board in order to access the socket and reconnect it. In the end I decided it was more trouble than it was worth, so I've been running my N9 since then, without a working/connected camera. It's not something I've missed to be honest, but yeah... caution is required when removing the back.
Ged.
Sent from my moto g(6) using XDA Labs
GedBlake said:
You certainly do have to be careful with the camera assembly, when removing the back.
Around 3 years ago, I removed the back of my Nexus 9, and not being aware of the camera 'sticking-in-the-hole' problem, I accidently ripped the camera assembly wires/connector from its socket. No real damage was caused, but reconnecting it would have required the removal of a circuit board in order to access the socket and reconnect it. In the end I decided it was more trouble than it was worth, so I've been running my N9 since then, without a working/connected camera. It's not something I've missed to be honest, but yeah... caution is required when removing the back.
Ged.
Sent from my moto g(6) using XDA Labs
Click to expand...
Click to collapse
I don't think I've ever used my N9 camera either. Regardless I'll take my time
Indeed. Once you've gone around all of the edges (I used my fingernail) to prise/detach the back, I would suggest some light finger pressure on the camera to 'pop' it out of its hole, before lifting the back away.
Sent from my moto g(6) using XDA Labs
henderjr said:
Awesome! I ordered one. Even found a little guide to help, https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
Click to expand...
Click to collapse
I ordered mine from there and they sent a toolkit with it too.