Hi, i was at work today and the PC is running XP. I connected the TP for the first time and it would not recognize. It was connected and running but i could not eject or see the Touchpad or any files. I had to pull the plug without ejecting, did this 2 times.
Now i am at home and when i plug it into my Windows 7 PC it is asking me if i want to format the disc.
When i close the box out it states this-
E:/is not accessible
"The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted." It keeps on asking me to format the disk.
Please help!
I had this same problem and found that if I restarted my machine opened Windows Explorer or my computer then plugged in the touchpad only while in a vertical position it worked. I think the connector or cable on mine is a little screwy.. I have also heard to make sure you are using the usb cable that came with it...
mayhem69 said:
asking me to format
Click to expand...
Click to collapse
its a trappp!!!!
You must have the novacom drivers installed on your pc for it to recognize the touchpad. DO NOT FORMAT. If you format the tp under windows, you will have a nice paperweight to add to your desktop. Google novacom. Get the drivers for the pc and everything will work as it should.
Sent from my Touchpad using Tapatalk
Moshe5368 said:
You must have the novacom drivers installed on your pc for it to recognize the touchpad. DO NOT FORMAT. If you format the tp under windows, you will have a nice paperweight to add to your desktop. Google novacom. Get the drivers for the pc and everything will work as it should.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
I had the right Novacom drivers already installed. The system files got corrupted from pulling the plug earlier in the day. I talked to an HP tech through chat and he told me to format. I did, it doesn't format the whole file system, just the temp. files.
It was working and seemed to be back to regular, but then started acting up again. Pretty soon i was getting the palm.com/rom error code.
After the negative feedback i gave the previous rep. i received a phone call from a US rep. later that night. She is going to send me another TP, i am giving $150 for them to hold til i send mine back.
This thing is too damn buggy, i am selling it on CL. Sold already for $200, getting a Transformer Prime.
This thing is ****! I guess you get what you pay for.
Tilde88 said:
its a trappp!!!!
Click to expand...
Click to collapse
thanks for the help, GEEK!
I have the same problem.. did you fix this by any chance?
Try it on another computer first, make sure you are using the cable that came with it. Try after a fresh reboot of your pc... I know it seems strange but I can only get mine to work after a fresh reboot with the stock cable and the touchpad in a verticle position but it works...
Related
I've had my AT&T galaxy S2 for a week now, upgraded from the Captivate. Mildly impressed, but very very disappointed that i can't even connect it to my laptop for file transfers--because I have win 7 x64. Even my captivate connected to it!
I talked to samsung, they don't have a win7 x64 driver for it yet. They recommended the Kies Air application, which i tried, and is so antiquated and SLOWWW that it is unbearable to use. For example, transferring photos must be done max 20 at a time, and at a very slow transfer rate--when it works. Other times upon tranfer it says "Error: Network error occurred"
Oh and then Samsung's next piece of advice was to just reinstall my OS to the 32 bit version. WHAT!??!
If i can't transfer music and movies from computer to my phone, and i can't transfer my pictures from my pictures from the phone to my computer... i've actually downgraded from my captivate.
Anyone have any solutions? Or do i return this new phone, which i anxiously awaited and purchased the day it came out...?
Uninstall ANY and ALL drivers that have to do with Kies or a Samsung phone. Reboot ur computer and phone. Install Kies and see what happens. I had that problem when I had a couple droid phones but uninstalling and reinstalling everything seems to fix it.
Works fine on my Win7 64 laptop and desktop.
entropism -- what drivers are you using, the 32 bit ones?
Have you tried alternate USB ports on your computer? Does it show anything or give you any indication that a connection is being made?
Oh and I'm on W7 x64 myself and haven't had any issues but installed Kies before I did anything.
it shows the battery charging, phone beeps when plugged in... OS says "installing device driver..." and then shortly says "(X) Driver was not successfully installed." and that is the end of story so far.
.. and you guys that say you are successfully connected, is this for full USB download mode (like my captivate where it just sees it basically like flash drive on your computer)? or is it via the kies interface? thanks for all responses.
innerfear said:
entropism -- what drivers are you using, the 32 bit ones?
Click to expand...
Click to collapse
The drivers on the Samsung site for the GS2. It was working fine without them, but I installed for the heck of it. I'm not using KIES to connect, just enabling USB storage on the phone when I connect.
innerfear said:
.. and you guys that say you are successfully connected, is this for full USB download mode (like my captivate where it just sees it basically like flash drive on your computer)? or is it via the kies interface? thanks for all responses.
Click to expand...
Click to collapse
Mine is for full USB mode so I can see my sdcard contents, etc. It also works fine with Kies.
Also try a NEW data cable, after a while they get flaky.
Sent from my SAMSUNG-SGH-I777 using xda premium
There are two USB modes on AT&T GS2: the default MTP mode and the Mass Storage mode. To enable Mass Storage mode, you will have to go to Setting->Wireless settings and network->USB utilities.
I have no problem on two of my 64-bit Win7. Drivers automatically downloaded and installed.
Looks like your Win64 install has some issues.
Well guys, i've tried uninstalling all KIES and samsung drivers/softwares, rebooting, then reinstalling the sg2 driver from samsung's site, new data cable, still no luck.
How do I enable USB storage on the SG2? I guess it was automatically enabled on the captivate. I'm a computer guy, it seems like i'm being slow on this, or this is really not user friendly. Thank you guys for the responses and help so far.
AH HA
AH HA! Finally.
Using the googles and the internets, i found this link -- and using "Method 2" as described, i got my sg2 connected in USB download mode... and it worked just like i needed it to.
So glad to have answered my own question here, but also appreciate the help and responses! Hopefully this link will help someone else out.
innerfear said:
AH HA! Finally.
Using the googles and the internets, i found this link -- and using "Method 2" as described, i got my sg2 connected in USB download mode... and it worked just like i needed it to.
So glad to have answered my own question here, but also appreciate the help and responses! Hopefully this link will help someone else out.
Click to expand...
Click to collapse
Didn't I already give you the instruction above?
foxbat121 said:
Didn't I already give you the instruction above?
Click to expand...
Click to collapse
I thought you did. I did not have any problems and thought it was pretty easy. Win 64 as well
Sent from my SAMSUNG-SGH-I777 using XDA App
Worked fine for me. I transferred 800 pics pretty quick.
Sent from my SAMSUNG-SGH-I777 using xda premium
Love my phone, but I can't get it to mount to my pc. Before the latest update I was able to use easy tether and access my sd card to transfer files. After the update neither the PC nor the phone do anything when plugged in, other than charge the phone. I've only found one computer that I can mount my phone to. Has anyone else had this problem and found a solution? I've tried multiple USB cords and even HTC's support line. They seem to think Verizon's media manager is to blame, but I think it would happen with all of us if that were true.
BTW phone is completely stock.
I have the same issue.
http://forum.xda-developers.com/showthread.php?t=1546598
Not Quite The Same
My computer doesn't recognize my phone at all. My DINC worked fine on every computer I tried it on, too bad I can't get used to the smaller screen and the 3G speeds again.
What does your computer say under device manager? Might have to update drivers, or delete them and reinstall them.
Sent from my ADR6425LVW using Tapatalk
Just one entry has a problem, but my coworkers Samsung Captivate works in this PC. The other computer doesn't have any issues in Device Manager. When I try to update it the Hardware Update Wizard says that it could not find a better match for my hardware. I can't post the image yet, 8 more posts to go.
http:
//i43.tinypic.com
/2ymdeaa.jpg
I would try uninstalling and reinstalling the HTC drivers. You may also try a different USB port, if you haven't already.
CaliDerb said:
Love my phone, but I can't get it to mount to my pc. Before the latest update I was able to use easy tether and access my sd card to transfer files. After the update neither the PC nor the phone do anything when plugged in, other than charge the phone. I've only found one computer that I can mount my phone to. Has anyone else had this problem and found a solution? I've tried multiple USB cords and even HTC's support line. They seem to think Verizon's media manager is to blame, but I think it would happen with all of us if that were true.
BTW phone is completely stock.
Click to expand...
Click to collapse
Yeah I think it has to do with the Verizon bloat. My Dad's work computer won't see his phone but it sees mine just fine. We both have Rezounds, but mine obviously isn't stock like his.
Tempted to hard reset
I'm so fed up with this that I am tempted to let Verizon do a factory reset. Either it works or they'll send a refurbished phone and hopefully that will one will work. Either way one way or another its going to cost them man hours or phones. I'm fed up with the bloat and the problems it causes.
I'm posting from my Windows 7 i7 gaming rig. My Rezy is usb connected to my rig. I can navigate both my internal memory file system as well as my SD card file system from Win7.
My Rezy is locked and stock, btw. I love this phone.
I just got this tablet a week ago after upgrading from my acer iconia a500 (good tablet, wanted more specs) and i puchased it used from someone. When I plugged it into my computer it would say usb device not recognized when I plug it into my usb 2.0 port, but when I plug it into my usb 3.0 port it would say unknown device. I've looked everywhere for this problem and I still cant find a solution. I tried installing the drivers manually but it would say;
"The inf file you selected does not support this installation"
or when i choose have disk it would say
'the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems
Ive tried installing asus sync and tried plugging it into my old windows xp computer and still doesnt work.
I have unlocked the bootloader with Asus's tool and my device firmware is 9.4.2.28.. and its not rooted (ics 4.0.3)
I thought this tablet would be amazing, its driving me crazy instead
Did you try the universal drivers pack...??
I did, nothing works
Sounds like a PC issue rather than a TP issue.....you tried on another machine?
Sent from my GT-I9300 using xda premium
I had the same issue, turned out to be a faulty usb cable, bought a new one and everything worked right away. Hope that helps.
sj010489 said:
I had the same issue, turned out to be a faulty usb cable, bought a new one and everything worked right away. Hope that helps.
Click to expand...
Click to collapse
Oh ****... Well, have the same issue here too now. It doesn't even make the "plug in" sound on my computer but still can load my tablet with the cable.
Maybe I'll buy a new one too. They are not that expensive.
Was on Bonsai rom and was running fine. Noticed the phone acting kind of weird the last couple days and thought it may be related to Xposed or some of it's modules so I deleted all of them. That didn't fix the problem. The problem being that the battery icon in the the notification bar would randomly flicker and with it so would the touch keys. I'm pretty sure this only happened when I was attempting to charge my phone (in my car.)
Instead of getting the usual phone charging indication in the status bar I either got nothing or it would say that the phone was connected to the dock (WTF?) I ended up restoring a nandroid of an older Bonsai rom and for a few hours there were no problems but then it started happening again. At times I would get a reboot from just plugging in the USB cable to charge the phone (car or wall) Other times the phone would just freeze up.
I then did a full wipe and tried MAXIMUS rom. I plugged in the USB cable and attempted to sync the phone to my PC as I have done countless times just days ago but I was now getting a message that my USB device is not recognized. I did another clean flash and tried Steve's Odexed rom. Same story more or less. If I attempt to sync the phone to the PC I get the same not recognized message.
Here are the steps I have taken:
- tried numerous USB cables
- tried numerous charging ports (wall/car/PC)
- tried numerous roms (none will let my PC see the phone)
- reinstalled the Samsung USB drivers
I'm at the point where I'm thinking this is a hardware issue and I probably have to return this phone. However, before I jump the gun I wanted to see if anyone has input on this. I appreciate any advice u guys may have.
My initial thought s maybe a cheap car charger, then a bad USB cable, but you've already eliminated those options. When you backup /restore your backups, are you including the efs.? I also remember the option in Wanam to keep old efs, was that option checked while it was installed?
Sent from my SM-N900P using Tapatalk
blackcanopy said:
My initial thought s maybe a cheap car charger, then a bad USB cable, but you've already eliminated those options. When you backup /restore your backups, are you including the efs.? I also remember the option in Wanam to keep old efs, was that option checked while it was installed?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that when I backup and restore I have all the boxes check off. However, I not only used backups. I did clean flashes on two separate roms but both had the same issue. I'm still on the fence as to whether this is software or hardware
SantinoInc said:
I'm pretty sure that when I backup and restore I have all the boxes check off. However, I not only used backups. I did clean flashes on two separate roms but both had the same issue. I'm still on the fence as to whether this is software or hardware
Click to expand...
Click to collapse
Have you tried flashing the MJ4 firmware to see if that straightens things out?
I would suggest to odin the stock rom found here if you can get your computer to recognize your device in download mode..
[ROM][TAR][ODIN] Full Restore (Return To Stock) N900PVPUBMJ4 TAR
http://forum.xda-developers.com/showthread.php?t=2549035
[ROM][TAR][ODIN] Full Restore (Return To Stock) N900PVPUBMJ4 TAR
Sent from my SM-N900P using Tapatalk
I may try that as a last resort. My fear is that I won't even be able to access Odin mode because the PC won't recognize my phone. We'll see...
Sent from my SM-N900P using XDA Premium 4 mobile app
SantinoInc said:
I may try that as a last resort. My fear is that I won't even be able to access Odin mode because the PC won't recognize my phone. We'll see...
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hopefully somebody can come up with a solution for you.
If it fails to recognize your device in Odin mode, you should be able to remove the battery, reinsert it and reboot to your system. No harm, no fowl.
Sent from my SM-N900P using Tapatalk
---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------
One more thing before I resign for the night... Maybe try those things you have already tried with your SD card removed. I'm hearing here and there about sd cards going bad causing issues you wouldn't normally think were related.
Sent from my SM-N900P using Tapatalk
SantinoInc said:
I may try that as a last resort. My fear is that I won't even be able to access Odin mode because the PC won't recognize my phone. We'll see...
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like a Windows driver issue. Could be unrelated to your phone.
What Version of Windows are you running? What do you see when you plug in your device when you go into Windows device manager?
Have you installed any new Android devices of the Nexus variety on your computer?
Alright, I'll assume that you're asleep. I agree, you may not want to do PC Odin if your computer isn't recognizing your device.
Go into device manager (right click on My Computer, select Manage, go to device manager from there). Do you see your device? Do you see any Android device? If so, do either have a yellow question mark adjacent the device name? Either way, delete the device if present, then reboot your PC.
Now plug your phone into your computer using a different USB port on the machine (cable we'll assume is fine). Your computer should automatically recognize the phone. If yes, profit.
Also check that USB debugging is set to on. If recognized and the phone is plugged in, deselect MTP device and choose the photo option. Then select MTP again.
If the above doesn't work, you can try rolling back drivers and reinstalling.
Let me know if this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Sounds like a Windows driver issue. Could be unrelated to your phone.
What Version of Windows are you running? What do you see when you plug in your device when you go into Windows device manager?
Have you installed any new Android devices of the Nexus variety on your computer?
Alright, I'll assume that you're asleep. I agree, you may not want to do PC Odin if your computer isn't recognizing your device.
Go into device manager (right click on My Computer, select Manage, go to device manager from there). Do you see your device? Do you see any Android device? If so, do either have a yellow question mark adjacent the device name? Either way, delete the device if present, then reboot your PC.
Now plug your phone into your computer using a different USB port on the machine (cable we'll assume is fine). Your computer should automatically recognize the phone. If yes, profit.
Also check that USB debugging is set to on. If recognized and the phone is plugged in, deselect MTP device and choose the photo option. Then select MTP again.
If the above doesn't work, you can try rolling back drivers and reinstalling.
Let me know if this helps.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Mic, thanks for taking the time for taking a look at this Q&A. I'm on Windows 7. Under DEVICE MANAGER it says UNKNOWN DEVICE with a yellow triangle with a exclamation point inside. When I click on that icon this is what I get for device status: Windows has stopped this device because it has reported problems. (Code 43)
I went through all your steps but it hasn't worked. I get the same message in DEVICE MANAGER before and after doing your steps.
As far as the phone is concerned (running Steve's Odexed) it indicates that the phone is charging but it doesn't have the usual MTP message in the status bar. Simply indicates that it's charging.
Is it safe to assume this is a hardware problem with the phone? The only thing I can think of that could have caused this is the other day my car charger (part that goes in the phone) fell in some water that accumulated on the rubber car mat. I dried it off with a napkin and plugged it back into my phone. These problems happened a day or two after this incident. Not sure if it's the reason. I was leaning towards blaming it on Xposed modules that got updated.
Nope, Not Safe to Assume...
SantinoInc said:
Mic, thanks for taking the time for taking a look at this Q&A. I'm on Windows 7. Under DEVICE MANAGER it says UNKNOWN DEVICE with a yellow triangle with a exclamation point inside. When I click on that icon this is what I get for device status: Windows has stopped this device because it has reported problems. (Code 43)
I went through all your steps but it hasn't worked. I get the same message in DEVICE MANAGER before and after doing your steps.
As far as the phone is concerned (running Steve's Odexed) it indicates that the phone is charging but it doesn't have the usual MTP message in the status bar. Simply indicates that it's charging.
Is it safe to assume this is a hardware problem with the phone? The only thing I can think of that could have caused this is the other day my car charger (part that goes in the phone) fell in some water that accumulated on the rubber car mat. I dried it off with a napkin and plugged it back into my phone. These problems happened a day or two after this incident. Not sure if it's the reason. I was leaning towards blaming it on Xposed modules that got updated.
Click to expand...
Click to collapse
Hi, SantinoInc, let us hope that the car charger issue and your Code 43 is a cum hoc ergo propter hoc (with this, therefore because of this) fallacy, or a non-correlated set of phenomena that, though happening contemporaneously, does not mean (though one is enticed to infer) causality.
The Code 43 error is a Windows issue, and if you are using a laptop (I hope), turn off the computer, take out the battery, let it discharge for 10 minutes, slap your laptop battery back in, boot up, plug in the phone, it's alive (I'm hoping). The USB controller on your computer actually holds a small amount of charge for rapid use when the computer is started, which can corrupt the port and driver. Draining the charge and pulling the battery is required to get rid of the problem.
Report back and let us know if this works for you.
unfortunately my computer I've been using is a desktop. However, I do have an old laptop laying around somewhere and will try that. This is driving me nuts already. I wish I knew for sure what the issue is.
Sent from my SM-N900P using XDA Premium 4 mobile app
Google...
SantinoInc said:
unfortunately my computer I've been using is a desktop. However, I do have an old laptop laying around somewhere and will try that. This is driving me nuts already. I wish I knew for sure what the issue is.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Google the error code you flipped me. You'll find that it most certainly looks like a USB controller issue. Tom's Hardware and Microsoft look to have the info you need, bro.
SantinoInc said:
unfortunately my computer I've been using is a desktop. However, I do have an old laptop laying around somewhere and will try that. This is driving me nuts already. I wish I knew for sure what the issue is.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had this issue as well, not with the same phone symptoms, but in windows.
Remove the driver, go to samsung's site, download and re-install the latest driver. Also make sure you are connecting directly to the ports on your motherboard and not on the front of the PC or a USB hub on something like your monitor. Also make sure you are using the cable provided by samsung if possible. 3rd party cables for some reason can cause issues. (Thank god for standards to specifications
If you are still on MI5, use the thread I created here for help in getting to MJ4:
http://forum.xda-developers.com/showthread.php?t=2580731
I have tried all of your suggestions (including Windows error code 43 in Google and trying those recommendations) nothing has worked. Of course I can't find either of the two laptops I own to test this POS phone out. If I get the same error another PC I'm going to take the phone to Sprint to get it replaced. I'm really feeling that this is hardware related considering I have not installed any new phone drivers to my PC at all and have made no significant changes to the PC.
Agreed...
SantinoInc said:
I have tried all of your suggestions (including Windows error code 43 in Google and trying those recommendations) nothing has worked. Of course I can't find either of the two laptops I own to test this POS phone out. If I get the same error another PC I'm going to take the phone to Sprint to get it replaced. I'm really feeling that this is hardware related considering I have not installed any new phone drivers to my PC at all and have made no significant changes to the PC.
Click to expand...
Click to collapse
Agreed; any PC would be suffice to determine if it is phone related. I'd almost be inclined to hop in the car and hit a Best Buy store and be done with it, like now....
Best of luck.
This device is EOL I realize but I would like to root it. Problem is I can't get any pc's to even acknowledge it is plugged in. Can I get this thing rooted again without ADB???
My bootloader is unlocked from when I first got the device.
EDIT: So it was the USB port that was bad. Ordered a daughter board from E-Bay and now I have working ADB. I'm going to leave this thread open in case someone does figure out a way to get root without adb...
andyroidking said:
This device is EOL I realize but I would like to root it. Problem is I can't get any pc's to even acknowledge it is plugged in. Can I get this thing rooted again without ADB???
My bootloader is unlocked from when I first got the device.
Click to expand...
Click to collapse
If you can't get the drivers set up, try Wug's NRT toolkit. He has a walk-through on setting up/removing/reinstalling drivers. You don't need ADB to root, but you do need to boot into a custom recovery to install a root program (I use SuperSu). You can boot a recovery via CMD from fastboot as long as the recovery is in your adb/fastboot data folder.
FWIW, NRT can do all.
Sent from my Nexus 9 using Tapatalk
ritchea said:
If you can't get the drivers set up, try Wug's NRT toolkit. He has a walk-through on setting up/removing/reinstalling drivers. You don't need ADB to root, but you do need to boot into a custom recovery to install a root program (I use SuperSu). You can boot a recovery via CMD from fastboot as long as the recovery is in your adb/fastboot data folder.
FWIW, NRT can do all.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I'm really thinking it is my connector. Sometimes it doesn't even charge. I guess I could try to boot one of my pc's into a live Linux distro. I never had issues when I ran Arch. Actually I could try it on my server. It is an Odroid XU4 though but it runs Arch... Thanks.
Cables are most often the cause.
ritchea said:
Cables are most often the cause.
Click to expand...
Click to collapse
Linux doesn't recognize it either. I assume it is the port/cable. The original cable is long gone but I have many brand new Anker and other brands but none work for connecting... Guess I'm screwed. Really wanted root because I'm having issues with battery drain again and the screen not coming on. I wanted to get a custom kernel running... Oh well.
I use off-brand cable exclusively. Have you tried uninstalling all Android USB connections then allowing an auto re-install? I've had to do that with my N9 at times. A few times, the driver showed up in device hardware but nothing further (connection). I right-clicked and updated driver-just went through the process with no new driver just basically re-install. Once, it was the cable but all others worked.
ritchea said:
I use off-brand cable exclusively. Have you tried uninstalling all Android USB connections then allowing an auto re-install? I've had to do that with my N9 at times. A few times, the driver showed up in device hardware but nothing further (connection). I right-clicked and updated driver-just went through the process with no new driver just basically re-install. Once, it was the cable but all others worked.
Click to expand...
Click to collapse
I tried removing everything. It never even acknowledges it is even plugged in. I also tried on 1 brand new Windows system. Same deal. I did a live boot of Linux and nothing. I tried on my Odroid and nothing. I'm not new to this and have many PC's and other devices but none work.
Only thing I noticed is under developer options it comes up as ptp or mtp but if I try changing it I will always say charging no matter what I pick.... So I never even get a USB permission dialog...
As this isn't new territory, you know some cables don't have pin config for data transfer.
Are you able to get recognition of your device with ADB devices command?--recognized but unauthorized?
[C:\Program Files (x86)\Android\sdk\platform-tools>adb devices
List of devices attached
007667324ccb229b unauthorized]
ritchea said:
As this isn't new territory, you know some cables don't have pin config for data transfer. Have you done a factory reset? That may be the only way to get proper permissions for PC again.
Click to expand...
Click to collapse
Yup... And I'm doing it again now. This time both in Android then from the bootloader (pwr+dn).
Also apparently when I flash stock back on this a year ago for my son to use I never flashed the recovery image, or not correctly because there is no recovery at all. Just hboot... When I select recovery I get the dead Android..
I altered my previous response. Andy lying on his back is the stock recovery portal. You have to hold power button then push/release vol+. It can be tricky, but pretty sure that's the sequence. I'll flash stock recovery to double check if needed.
ritchea said:
I altered my previous response. Andy lying on his back is the stock recovery portal. You have to hold power button then push/release vol+. It can be tricky, but pretty sure that's the sequence. I'll flash stock recovery to double check if needed.
Click to expand...
Click to collapse
I have to go do some other stuff right now... I think he had the triangle exclamation in his chest though... I'll try some more later. Thanks!
When you have time https://youtu.be/DuuSTnbQSlM
ritchea said:
When you have time https://youtu.be/DuuSTnbQSlM
Click to expand...
Click to collapse
Doh! I'm so spoiled with rooted devices and twrp I forget you have to jump through hoops to get into some recoveries... So, I did the Android reset, Hboot reset and stock recovery hard reset. And no changes. Still only charges. Oh, well. Thanks again.
Quick update... Ordered a usb daughter board from e-bay. Last $10 I'll spend on this device...
andyroidking said:
Quick update... Ordered a usb daughter board from e-bay. Last $10 I'll spend on this device...
Click to expand...
Click to collapse
My USB started acting up on mine too. Watching a movie with a USB otg and it just stopped. I then discovered the only way for it to work was to jiggle it then hold it in a certain angle. I'm guessing something is loose. I haven't opened her up yet. I'd like to grab a new USB port for mine. Is it soldered to the daughterboard? Seems like changing the daughterboard will be easier.
madbat99 said:
My USB started acting up on mine too. Watching a movie with a USB otg and it just stopped. I then discovered the only way for it to work was to jiggle it then hold it in a certain angle. I'm guessing something is loose. I haven't opened her up yet. I'd like to grab a new USB port for mine. Is it soldered to the daughterboard? Seems like changing the daughterboard will be easier.
Click to expand...
Click to collapse
A few screws... I had to fix my camera because I pulled the back off wrong trying to disconnect the battery a while ago. Just gotta be careful. When the part comes in I'll update.
Video:
https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
eBay store:
http://www.ebay.com/itm/For-Google-...e=STRK:MEBIDX:IT&_trksid=p2057872.m2749.l2649
andyroidking said:
A few screws... I had to fix my camera because I pulled the back off wrong trying to disconnect the battery a while ago. Just gotta be careful. When the part comes in I'll update.
Video:
https://www.ifixit.com/Guide/Nexus+9+USB+Daughterboard+Replacement/43021
eBay store:
http://www.ebay.com/itm/For-Google-...e=STRK:MEBIDX:IT&_trksid=p2057872.m2749.l2649
Click to expand...
Click to collapse
I looked it up and saw it. I noticed the rear camera was attached. Thanks for the info. I changed the screen on my n7 2013, but never thought to change the port on this one. D'oh.
@madbat99 @ritchea
Got the daughter board from China. About 25 minutes to install (I'm getting real good at taking this device apart now...lol). Powered up and connected to my Windows machine. And... It is recognized now! Can't believe I fought so long thinking it was a driver/windows issue.
After taking it out I can see why it would wear out/break. Cheap plastic and it has such a large opening on the outside my son probably tried all the time to plug it in wrong...
@ritchea thanks for your help!
@andyroidking,
I did nothing but super glad you were able to fix it!...and share it with the community.
andyroidking said:
@[email protected]
Got the daughter board from China. About 25 minutes to install (I'm getting real good at taking this device apart now...lol). Powered up and connected to my Windows machine. And... It is recognized now! Can't believe I fought so long thinking it was a driver/windows issue.
After taking it out I can see why it would wear out/break. Cheap plastic and it has such a large opening on the outside my son probably tried all the time to plug it in wrong...
@ritchea thanks for your help!
Click to expand...
Click to collapse
I ordered one from the link you provided. Coming from China so I hope it doesn't take too long. Can't wait. The port is waaaay to big, too much room to jiggle around. Hope this fixed my problem too.