I'm working on installing Ubuntu to my prime using the thread i linked below, but for part of that i need to go into my prime via desktop Ubuntu command line. The issue i'm having is that when i plug into my desktop using the USB cable, Ubuntu won't recognize my Prime and i can't move files back and forth.
The thread says to install the naked drivers (which i downloaded), but the instructions were only for windows machines. From what I can tell Ubuntu doesn't have a "Device Manager" where I could use to manually install drivers.
I've done Google searches, and searched XDA for the past week or so and I haven't come across anyone having this similar issue while using Ubuntu. If anyone can shed some light on my situation I'd greatly appreciate it.
Thanks!
How to install Ubuntu on transformer prime: http://forum.xda-developers.com/showthread.php?t=1603921
RailsRanger said:
I'm working on installing Ubuntu to my prime using the thread i linked below, but for part of that i need to go into my prime via desktop Ubuntu command line. The issue i'm having is that when i plug into my desktop using the USB cable, Ubuntu won't recognize my Prime and i can't move files back and forth.
The thread says to install the naked drivers (which i downloaded), but the instructions were only for windows machines. From what I can tell Ubuntu doesn't have a "Device Manager" where I could use to manually install drivers.
I've done Google searches, and searched XDA for the past week or so and I haven't come across anyone having this similar issue while using Ubuntu. If anyone can shed some light on my situation I'd greatly appreciate it.
Thanks!
How to install Ubuntu on transformer prime: http://forum.xda-developers.com/showthread.php?t=1603921
Click to expand...
Click to collapse
Try uninstalling the drivers from your machine then reinstalling the basic Asus drivers by plugging the Prime in. If that doesn't do it then I'll have to load up my Ubuntu parition and see if I can debug with you that way.
RailsRanger said:
I'm working on installing Ubuntu to my prime using the thread i linked below, but for part of that i need to go into my prime via desktop Ubuntu command line. The issue i'm having is that when i plug into my desktop using the USB cable, Ubuntu won't recognize my Prime and i can't move files back and forth.
The thread says to install the naked drivers (which i downloaded), but the instructions were only for windows machines. From what I can tell Ubuntu doesn't have a "Device Manager" where I could use to manually install drivers.
I've done Google searches, and searched XDA for the past week or so and I haven't come across anyone having this similar issue while using Ubuntu. If anyone can shed some light on my situation I'd greatly appreciate it.
Thanks!
How to install Ubuntu on transformer prime: http://forum.xda-developers.com/showthread.php?t=1603921
Click to expand...
Click to collapse
In my experience, you do not need to download any drivers to access your Prime from an Ubuntu PC -- the naked drivers are strictly a Windows thing from what I remember. You need to set up the 51-android.rules file in the /etc/udev/rules folder. And, you may or may not need to make an entry in adb_usb.ini (I believe this file is in a hidden folder) -- try it without first. If you do a little research on 51-android.rules, you will see that this is quite easy. And, the vendor and device numbers you need to plug into 51-android.rules can be obtained by typing lsusb at the terminal command line, with your Prime plugged into the PC. You also need to have debugging turn on under Developer Options in Settings. After you change the 51-android.rules file, you need to log off and log back on, so it gets run (there is another way to run it, but I do not remember how). I am away from my Prime and Ubuntu machine, but can get you further details later, if you cannot figure it out from the above information.
(P.S.) Giving you the path and file names from my memory. They are probably correct ... at least they are very close to being correct.
So, I wrote the 51-android.rules file like you suggested but I still can't access most files on my prime. When I tell it to connect as a camera i can view picutres, but when it connects as MTP I still get nothing.I looked in the /dev directory to see if i could find my SD card to continue on with the Ubuntu installation, but no luck there either.Your suggestions have been helping though, i'm getting closer. Thanks to both of you who replied so far.
RailsRanger said:
So, I wrote the 51-android.rules file like you suggested but I still can't access most files on my prime. When I tell it to connect as a camera i can view pictures, but when it connects as MTP I still get nothing.I looked in the /dev directory to see if i could find my SD card to continue on with the Ubuntu installation, but no luck there either.Your suggestions have been helping though, i'm getting closer. Thanks to both of you who replied so far.
Click to expand...
Click to collapse
51-android.rules is really for giving you access to your TFP with adb and other Linux commands in Terminal (Android Debugging must be enabled under Developer Options for this to work). 51-android.rules has nothing to do with PTP (camera) or MTP, as far as I know. I really do not know what you are trying to do, or at least how you are trying to do it, so it is difficult to suggest anything. If you are just trying to copy files to the TFP, you may have better luck with Windows than Linux. I'm pretty sure that most of the TFP's file system does not show up in the Linux File Browser, when plugged in to a USB port (only PTP & MTP work, as far as I know ... both are limited).
There are many users on this site who can help you, if you explain exactly what you are trying to do.
Related
Hey, I was wondering if anyone had a link to download the HTC Bootloader drivers. It fails when I try and load "something" in Windows.
Thanks.
p.s: This will lead to good things...
The only drivers that I am aware of are the ones that are in the Android SDK Toolbox and in the HTC Sync program. Correct me if I am wrong, but as far as I know, they aren't specific drivers ie "bootloader" drivers. They are just drivers to get your comp to recognize the phone when its attached.
I'm assuming this is something you're expirementing with to get root via the adb in recovery, if so, good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Hi crax0r,
The folks at Android (aka Google) provide these instructions for installing the drivers. It involves installing their SDK first, and installing Java for that, and an IDE called eclipse.... UGH.
The HTC "Sync" Application that hoovnick is referring to can be found here.
It has been so long ago that I installed drivers (on a WinXp x32 laptop) that I can't remember what order I did things in, whether or not the driver used by HTC sync is sufficient for fastboot but not adb (or vice versa), whether I did the SDK install first, etc etc etc. As a matter of fact, it's been so long ago that the computer that I did it on is now dead, and here I am using a Linux machine.
For all I know, the order you do things in affects the outcome - it sure seems like a lot of folks with Windows 7 complained about driver troubles.
One thing is for sure, though - setting up the entire Android SDK (+ Java + Eclipse + ...) in order to install a device driver has to be the worlds most roundabout way of doing a driver install.
If you are considering using the "fastboot" method to install Amon_RA's recovery boot, you might try just installing HTC Sync first, and see if that is sufficient for getting fastboot talking to the phone. That install is way, way easier than setting up the SDK to get a driver installed.
The other thing which is an option, if you are a little bit Linux-savvy, is to boot one of those "Live CDs" (Ubuntu, SuSe, etc) on your PC - there are no drivers to install in the case of Linux, you just need to be running as "root" on the Live (linux) CD to get fastboot to talk to the phone. The downloads (fastboot for Linux and the Amon_RA recovery image) are small, and they will both easily fit in the /tmp folder of the Linux (Live CD) boot on the PC.
Once you have Amon_RA on the phone, you won't need the SDK any longer, unless you want to start doing dev-like things; that's why a one-time boot into Linux would also work.
bftb0
I <3 Ubuntu. It's amazing!
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
crax0r said:
It's OK. I'm running Ubuntu now.
Click to expand...
Click to collapse
Excellent. Just remember to always run fastboot as root, and if using adb, then the first time after you boot (the PC), run adb as root.
The reason is that by default, Ubuntu won't let an unprivileged user access the USB.
Since I have adb and fastboot in my Ubuntu (regular user) PATH, I usually just do a
$ sudo `which adb` blah-blah-blah
or
$ sudo `which fastboot` blah-blah-blah
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
I don't know - I've already forgotten everything I did with the driver install in Windows, and I don't currently have a working Windows machine. Sorry I can't be of more help. As I said, the troubles people have been having seem to depend on which version of Windows (Xp/Vista/7), whether its x32 or x64, phase of the moon, etc. Seems like people run into snags on Win7 or x64 versions of Windows more than Xp-32, but I don't know why that is.
Keep plugging away at it. If you are looking for resources to help resolve the problem, I would go look at docs relating to Windows driver install troubleshooting - the driver install problem seems to be a Windows issue, not really anything to do with the SDK.
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
Sounds like what happened to me. i had to hit the icon at the top of my phone that showed the usb cable.. i had to switch charge only to disk drive "mount as disk drive"... folder popped right up on my windows machine asking how i wanted to open the file
I have the SDK running and my phone being recognized on my computer with Vista but I have another one running XP 32 bit and windows will NOT recognize the .inf? Any ideas? I deleted all previous HTC drivers and tried that approach but nothing seems to be working.
I cannot seem to get Novacom drivers installed for my Touchpad. I've tried rebooting both machine and touchpad, taken TP in and out of dev mode, tried every command line I could find for running the novacom installer, etc. I am at a loss, cannot get it to work at all. Tried searching but didn't come up with anything for novacom
I'm trying to do this while at work and am on a netbook with windows 7 starter.
Appreciate any help
OK sorry for sounding stupid but have you run the universal novacom installer? If so, what happened?
Sent from my HTC Desire S using xda premium
dan-fish said:
OK sorry for sounding stupid but have you run the universal novacom installer? If so, what happened?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Yes, I get a message that says it has been successfully installed, but when I plug in the TP it isn't recognized. Cannot mount as USB either
Doesn't sound like a novacom issue. Maybe someone else can spread some light here
Sent from my HTC Desire S using xda premium
Would be much appreciated.
FWIW, I did get it to be seen by quick install the very first time I plugged it in but it immediately dropped it and hasn't seen it since.
I got it to see it briefly on a different computer. Now when I put it in recovery mode it comes up as unknown device again. I want to throw this [email protected]#$& thing!
Please, can someone help me out here.
I have gotten it to the point that it is seen until I put it into recovery mode. Once I put it in recovery mode and plug it in, I get device not recognized.
In an effort to remedy that issue, I wiped everything touchpad related on my computer clean to start again. Now I'm back to square one. Device not recognized and cannot mount to USB Mass storage. What the F am I missing here. Why does it work one second and not the next?
In vein, I tried to install using my old iBook but even that didn't work(thanks Steve!)
I've also moved from the netbook I was trying to install from last night, to my normal win7 machine.
Would really appreciate it if anyone is willing to work with me to resolve this
Haha. I had this same issue. i wish it would be added to the tutorial's OP. Anyway, make sure you are putting acmeinstaller in the folder . Crogram Files, Palm, Inc where the actuall Novacom drivers are. Then enter the C prompt and you're good to go. If you don't have x64 put the ACMEInstaller file wherever your computer has Palm Inc and that is the directory you CD to.
i.e. for me it was cd c:/program files/ palm inc
Ended up using an XP machine to install. Took just a few minutes. Drivers were found right away unlike in 7.
blackwrx02 said:
Ended up using an XP machine to install. Took just a few minutes. Drivers were found right away unlike in 7.
Click to expand...
Click to collapse
My issue with Win7/64bit were the path/file location.
Even if you download the drivers and install them correctly, you still have to execute the novacom ext.
It's in the prog files\palm folder, as said.
Had a heck of a time myself until I realized this.
dajogejr said:
My issue with Win7/64bit were the path/file location.
Even if you download the drivers and install them correctly, you still have to execute the novacom ext.
It's in the prog files\palm folder, as said.
Had a heck of a time myself until I realized this.
Click to expand...
Click to collapse
For people searching for the answer.
I'm on win7 64 bit. The universal novacom install went fine. Plugged in touchpad and ran command, but novacom did not find device.
Moved usb connection to different usb port on my computer, magic.
Novacom commands worked and installed cyanogen 9.
If moving usb ports doesn't work. Disconnect usb cable, uninstall novacom via control panel, software removal. Then, reinstall novacom, and use 2nd usb port.
I seached the web, and none of these questions about novacom not finding device was answered. The above is the answer. Move usb ports.
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Good write up!
The procedure worked fine on my laptop. When I did it on on my home PC I forgot to disable auto-mount and the Nook installed itself as mass storage. I was able to right click -> un-install all the USB Mass Storage entries (with the Nook unplugged), disable auto-mount, plug the Nook back in, and have it show up correctly.
In short, I did not need to use "USBDeView" as I was able to remove the diveres manually. I suppose if you have more than a handful for USB devices (I just have a Mouse, Keyboard, and printer) "USBDeView" might be helpful to determine which drivers to un-install...
The device manager is enough for most people, but there is a somewhat large number of us that are having trouble still. Possibly because of other devices we have installed before. (I dont understand how all the drivers work and I wont pretend to)
Some people have go so far as putting a fresh install on Windows on a partition of a PC.
I had this problem with both my laptop and my desktop, which surprised me. This worked on both the laptop and PC, so hopefully it can help other people.
I cant wait to get my own tablet on the 12, I will take lot of pictures and make this process more user friendly.
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
mtelesha said:
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
Click to expand...
Click to collapse
Did you sort by last time plugged in and delete all of those too? Have you re-checked and then re-un-checked automount/usb debugging and such?
This is interesting, you'll have to come back and let me know if you ever get it working on your PC. Maybe its a good excuse for a nice healthy re-format and reinstall of windows?
l3ft3r1s said:
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
Click to expand...
Click to collapse
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
The_Joe said:
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
Click to expand...
Click to collapse
Yeap, that did the trick, thanks. Drives installed successfully this time, but adb devices still returns nothing.
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
adb error: device offline
This drove me nuts for at least a day. Turns out it is what happens when you are plugged into a USB 3.0 port on your PC side. Find out which USB is 2.0 (Front Panel for ZT Systems), use it and life suddenly gets really good.
The_Joe said:
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
Click to expand...
Click to collapse
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
l3ft3r1s said:
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
Click to expand...
Click to collapse
The problem is sdk uninstall and use ccleaner to clean your PC and registries. Use the drivers provided in this forum
Sent from XDA using one of my Android Toys
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
LadyPenley said:
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Click to expand...
Click to collapse
In the future don't delete your original, just post an edit with the fix. That way when someone else has a similar problem your post can help.
Sent from my BNTV250 using xda premium
mtelesha said:
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
Click to expand...
Click to collapse
Did you find a solution? Thats a problem I sadly dont know how to help with. I would start with:
-Check USBDeview and delete anything android/Nook/usb related. Delete just about everything.
-Restart the device
-Uncheck and recheck the USB Debugging boxes
-Recheck and uncheck the auto-mount box
-Test
-Try a different USB Port
-Try another PC
Thanks but didn't work.
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
The_Joe said:
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Click to expand...
Click to collapse
whitets said:
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
Click to expand...
Click to collapse
I had literally this exact same problem the 6th time I restored and flashed. IF im right, you just need to uncheck then recheck usb debugging.
Let me know if it works!
So, last night i tried to flash GtabComb to my 1.1 Gtab. After 3 unsuccessful installs (which I now believe are attributed to the system partition size of only 200 rather than 250 [help here would also be apprciated]) i downloaded the latest Rom Manager and updated ClockWork Mod. After the initial scare that my SD card had been totally formatted, i found that for some reason, this new CWM likes to use the second SD card... You know, the one with no backups or anything saved to it. For now, I am running a random ROM (Vegan Gingerbread) until i find out how to switch the SD card read by CMW. So any help guys? It's probably something really simple I'm over looking.. Help is appreciated greatly. Thanks
Edit: On a side note, I finally got GtabComb to load on my tablet! Seems I only needed a little bit of patience...
theshafe said:
So, last night i tried to flash GtabComb to my 1.1 Gtab. After 3 unsuccessful installs (which I now believe are attributed to the system partition size of only 200 rather than 250 [help here would also be apprciated]) i downloaded the latest Rom Manager and updated ClockWork Mod. After the initial scare that my SD card had been totally formatted, i found that for some reason, this new CWM likes to use the second SD card... You know, the one with no backups or anything saved to it. For now, I am running a random ROM (Vegan Gingerbread) until i find out how to switch the SD card read by CMW. So any help guys? It's probably something really simple I'm over looking.. Help is appreciated greatly. Thanks
Click to expand...
Click to collapse
The best way to install CWM is through NVflash. Rom manager is really designed for phones not this tablet. NVflash is simple and easy to use as long as you have a desktop or laptop using either windows or Linux. Here is the link to guide you through those steps. Helped me out when I was in a jam.
http://viewsonic-gtablet-for-dummies...om/nvflash.htm
Thanks for the advice! NVFlashing is a tad of a problem for me, however. I've actually commented on that particualr NVFlashing tutorial earlier today explaining how my computer won't recognize my tablet while it's in APX mode. I seem to have the worst luck with this kid of thing..
Would there another way to change which card is being read?
Do not use Rom Manager on the Gtablet it will mess things up. You can go to this link and download a .zip installable version of CWM for your bootloader. There are versions for installing from either the internal or external sdcard. If you are not installing from the external sdcard, it is best to remove it.
You could also check out this thread, and this one for more info.
It sure does mess things up! And that CWM.zip would be great had I not had another (worse) version already installed.. woe is me. I'll give those threads a read tomorrow and hope something turns up. Thanks for the links!
DaggerDave said:
Do not use Rom Manager on the Gtablet it will mess things up. You can go to this link and download a .zip installable version of CWM for your bootloader. There are versions for installing from either the internal or external sdcard. If you are not installing from the external sdcard, it is best to remove it.
You could also check out this thread, and this one for more info.
Click to expand...
Click to collapse
That would be the way to go but if you can't access the current CWM you cannot get it to install anything. The only other alternative would be to figure out why the computer won't recognize the tablet in APX mode. What OS are you trying it with?
Try this:
Download this .zip file and extract it to your Gtablet's sdcard.
Using a root file manager (ES, Root Explorer, etc.) mount /system as read-write (rw) and move the downloaded files in each folder to their proper locations (copy the system/etc/recovery folder into /system/etc and the files in system/bin into /system/bin) and make sure all the permissions are correct. The recovery images should be -rw-r--r--, the scripts inside of /bin should be -rwxr-xr-x and flash_image should be -rw-r--r--.
Open a terminal emulator and type 'su' (without quotes) and allow SuperUser when it asks. Your shell prompt should go from a '$' to a '#'. Now type 'cwmrecovery.sh' (without quotes) and enter. That should install cwm-08 for you, just exit when it finishes and try to reboot into recovery. You can use the 'fixrecovery.sh' script to flash the stock 1.1 recovery if you ever need to.
See the last thread I linked to in my last post for more info on this. Good luck!
DaggerDave said:
Try this:
Download this .zip file and extract it to your Gtablet's sdcard.
See the last thread I linked to in my last post for more info on this. Good luck!
Click to expand...
Click to collapse
Just extracted to the external SD that was being read from and updated from there with the new CWM and bam! .08 is on and working like a charm. Many thanks!
nobe1976 said:
Another alternative would be to figure out why the computer won't recognize the tablet in APX mode. What OS are you trying it with?
Click to expand...
Click to collapse
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck[/QUOTE]
The OS on the tablet doesn't matter since the APX mode is the tablets download mode. The OS on you computer is what might be the issue, or could even be just a bad USB port or even drivers being used. If the computer keeps promptings that software needs to be installed. Guied the it to install them from the extracted NVflash file and install the ones that are in the pack.
I would love to know why it doesn't. I was previously using a froyo tap'n'tap, but now I am running 3.0.1. Would OS make a difference? I always assumed it was my tablet/PC's/luck
Click to expand...
Click to collapse
As the post above said, the OS on your PC is probably your problem. Which OS are you using? WinXP, Win7? I can't for the life of me get Windows7 to recognize my ICS Gtablet but o'well!
If you are comfortable with using or trying Linux, you could try installing Knoppix on a USB drive and run that. I think Knoppix has everything set up for MTP & ADB already and is 'live' so no real configuration is needed to get it running (except for your wifi of course). Just use the Linux version included in most NvFlash packages. If you have a fairly powerful computer, you could also try running Linux in a VM, but Knoppix doesn't run in a VM very well.
My favorite is Arch Linux (not in a VM). Although you have to build and configure the system yourself from the ground up. Since I started using Linux I have really enjoyed it. It is much faster than Windows, more secure and gives me less problems than the Win PCs I deal with. Check out this site if you are interested in Linux.
DaggerDave said:
As the post above said, the OS on your PC is probably your problem. Which OS are you using? WinXP, Win7? I can't for the life of me get Windows7 to recognize my ICS Gtablet but o'well!
If you are comfortable with using or trying Linux, you could try installing Knoppix on a USB drive and run that. I think Knoppix has everything set up for MTP & ADB already and is 'live' so no real configuration is needed to get it running (except for your wifi of course). Just use the Linux version included in most NvFlash packages. If you have a fairly powerful computer, you could also try running Linux in a VM, but Knoppix doesn't run in a VM very well.
My favorite is Arch Linux (not in a VM). Although you have to build and configure the system yourself from the ground up. Since I started using Linux I have really enjoyed it. It is much faster than Windows, more secure and gives me less problems than the Win PCs I deal with. Check out this site if you are interested in Linux.
Click to expand...
Click to collapse
To top on this excellent information. If you decided to try a Linux disto I would recommend a version of Ubuntu, doesn't really matter which one they are all really user friendly and depending on you pc setup depends on which version of it you can use. I have 11.05 installed on a 2nd partition for doing my Droid stuff on a computer that is around 9 years old, runs smooth. Windows xp is the other alternative which I have used several times NVflashing stuff, but adb seems to run better through Linux in my opinion.
Ah, mind went blank there. Right now, all I have is a windows 7 laptop (my XP desktop and older Vista laptop are probably long gone) Ive attempted to flash before with the vista laptop to no avail. In both instances, I connect the tablet in APX and it was not even recognized as a connected device. I'm hesitant to run Linux, even from a flash drive. If I get the chance to soon, I may very well end up doing it, as it appears the ONLY option.. Thanks for your help guys. If you could think of anyway for Windows 7 to recognize my tablet, please let me know. You guys are a great help. Thanks again!
If you haven't already tried this maybe it will work for you.
- Put the tablet into APX mode, then plug in the USB. Windows7 will drag on then fail installing the drivers, as usual.
- Go to Control Panel->Hardware and Sound->Device Manager and find the '!' (unknown device)
- Right click and choose Properties, then Uninstall Driver (if it is an option)
- Next, click on Update Driver, then choose Browse My Computer ...
- Navigate to the NVFlash folder (the one you extracted from the nvflash .zip you downloaded)
- Open the folder inside called 'usbpcdriver' or similar, and select the .inf file (NvidiaUsb.inf) and choose to install it. Once it installs, it should recognize the tablet as a MTP device. If not turn off the tablet, unplug the USB, restart Windows and plug it back in when it is finished rebooting and start the tablet in APX mode again. If it still doesn't recognize it try the whole process over agian.
I can understand being hesitant toward running Linux but running from a flash drive or in a VM is pretty safe, as in if you mess up the OS you can always start over without damaging Windows. Done it many times! Try running Ubuntu in a virtual machine such as Virtual Box, it is almost as user friendly as windows and you can have the VM capture USB devices such as the Gtablet which Ubuntu should recognize. Probably won't run very fast on a laptop but if you have at least a dual core with 2 GB of ram it should be pretty smooth.
Not trying to push Linux on you or anything, just some suggestions. From what I hear most of the Gtab devs use Windows7 and it seems to work great for them!
Hi
I would like to connect my Yamaha digital piano to my Nook HD (I currently connect the paino to a PC via Midi IN/OUT to USB cable which works fine). I thought that rooting the Nook and running USB Host Check would provide the answer but the apps I have tried (Perfect Piano being the most appropriate) don't recognise a device as being connected.
I am sure there must be a way and would very much appreciate any help. Running a cable to my PC each time I want to record something is driving me crazy.
Maybe this could help: http://www.musicalandroid.com/1/pos...o-record-sound-with-your-audio-interface.html ?
According to this: http://www.mikrosonic.com/rd4-midi-android These kinds of things work best at least 4.1.x but 4.2+ would be better. Might need to try a custom rom as well then.
I've not had any experience with this stuff, just found some info for you. Hope it helps!
Connect Nook HD to Digital Piano
es0tericcha0s said:
Maybe this could help: ?
According to this:These kinds of things work best at least 4.1.x but 4.2+ would be better. Might need to try a custom rom as well then.
I've not had any experience with this stuff, just found some info for you. Hope it helps!
Click to expand...
Click to collapse
Thank you very much for the info - it all looked very promising.
USB Audio Recorder won't detect the piano when connected using the midi IN/OUT cable, it is looking for a sound card.
I am thinking that it may work if I connect it via the headphone socket.
Strangely enough if I don't have a Jack to USB cable to hand - but I have ordered one as it must be worth a try!!
Many thanks again for your help
No problem. Let us know if you figure it out in case someone else is looking for a similar solution.
Connect Nook HD to a digital piano
es0tericcha0s said:
No problem. Let us know if you figure it out in case someone else is looking for a similar solution.
Click to expand...
Click to collapse
Just to let you know that the cable didn't work! damn!
I have found USBHostSwitcher.apk on one of the forums here, which looked like it would do the trick.
I have downloaded it from a couple of locations but APK Installer comes back with an 'unable to parse' error message.
It either doesn't like my Nook, or the Android version, or ME!
The quest continues.
Thanks again for your help
https://dl.dropboxusercontent.com/u/9903887/Apps/USBHostSwitcher.apk
Found this on a Nook HD site and uploaded to my Dropbox and tested it. Installed fine for me. I don't have any use for the app, just tested to see if it installed correctly. If it still fails again, then you need to switch browsers or download on PC and transfer over.
Connect Nook HD to a digital piano
Found this on a Nook HD site and uploaded to my Dropbox and tested it. Installed fine for me. I don't have any use for the app, just tested to see if it installed correctly. If it still fails again, then you need to switch browsers or download on PC and transfer over.[/QUOTE]
Many thanks for your very quick reply.
I have downloaded the file from dropbox to my PC and copied it across to the Nook.
Unfortunately I still get an error message 'There is a problem parsing the package'.
I think it must be me that it doesn't like
Do you have adb set up so you can side load it?
Connect Nook HD to a digital piano
es0tericcha0s said:
Do you have adb set up so you can side load it?
Click to expand...
Click to collapse
I will find this and install.
I'll try the USBHostSwitcher again.
Thanks a lot
MiddleC said:
I will find this and install.
I'll try the USBHostSwitcher again.
Thanks a lot
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have the right drivers installed.
Plug in Nook with USB Debugging enabled
Put USBHostSwitcher.apk into the folder you unzipped with the files for adb.
Open CMD Prompt and change directories to the adb folder
Run:
adb install USBHostSwitcher.apk <enter>
Connect Nook HD to a digital piano
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have the right drivers installed.
Plug in Nook with USB Debugging enabled
Put USBHostSwitcher.apk into the folder you unzipped with the files for adb.
Open CMD Prompt and change directories to the adb folder
Run:
adb install USBHostSwitcher.apk <enter>
Click to expand...
Click to collapse
Installed Minimal ADB and Fastboot version 1.1.3.
Whilst I can access the Nook from the PC no problem, ADB can't find the device.
Other people seem to have had the same problem - none of the solutions seem to work.
In fact at least one of them caused problems with Windows reporting that there was a problem with the Nook connection.
I have had to restore my PC to a position a couple of days ago to undo the problem.
I have installed Minimal ADB and Fastboot again but it still can't find my device.
Are you running a custom rom like CM or just whatever comes on the Nook?
http://forum.xda-developers.com/showthread.php?t=2336088
This thread has a few different posts with what people had to do to get adb running.