X10 Community Forum
X10 AirPad Android Tablet => AirPad General Discussions => Problems and Troubleshooting => Topic started by: Tesla on September 10, 2011, 04:08:40 PM
-
I don't seem to have root access on my AirPad. It has been posted that we would have root access to this machine.
Test 1:
Download "Terminal Emulator" from the Android Market and run it...
Once inside the Terminal type: su
If the terminal then jumps down a line and displays a # you have root...
- This test does something else.
Test 2:
Installed Titanium Backup (free) from the Android Market
- Reports "no root access"
... how do we get root access?
-
interesting, I'll look into this right away.
-
interesting, I'll look into this right away.
Any progress or news on this?
-
I'm also wondering if there's any more info or progress on this.
-
I'm also wondering if there's any more info or progress on this.
There is root access, but you're probably looking for 'su' and 'superuser.apk'. I will make a ROM with this and upload once I get back into the office Monday.
-
I'm also wondering if there's any more info or progress on this.
There is root access, but you're probably looking for 'su' and 'superuser.apk'. I will make a ROM with this and upload once I get back into the office Monday.
Support like this from the company is why I purchased the airpad try to get a Barnes & Noble tech to respond like this regarding a Nook, hah ! Thank you so much.
-
I will make a ROM with this and upload once I get back into the office Monday.
Just curious if there has been time to look at this.
-
Thanks kindly. >!
I've flashed many a firmware to many devices but I did actually have some troubles on this device when the first attempt failed.
Turns out the image file was corrupt and after downloading it and flashing it again, all was well.
The on-screen keyboard is much better. ;D
-
Turns out the image file was corrupt and after downloading it and flashing it again, all was well.
I might suggest zipping all the different files (even separately), just to act as a container. A .zip file can be tested, and an incomplete .zip file will complain.
Publishing the MD5 hash codes to the various files would be another option, but seems like zipping is easier.
-
I'm not sure exactly what happened, but with the first attempt the downloaded .img was 138MB and failed. The second was 159MB and flashed without issue.
The first attempt resulted in a boot loop, so I was worried for a few minutes... :'
-
I can't complain too much because I'm sure I'm outnumbered, but a Mac-friendly way of uploading ROMs would be helpful in the future. Especially if this is the preferred method of software updates or the eventual Ice Cream Sandwich release.
-
I can't complain too much because I'm sure I'm outnumbered, but a Mac-friendly way of uploading ROMs would be helpful in the future. Especially if this is the preferred method of software updates or the eventual Ice Cream Sandwich release.
Do note, your not the only one. I am a hard core mac/linux user. And I am X10 Staff so I account for many votes. rofl
-
I can' get the Rockusb driver installed. I'm on a Windows 7 Pro 32 bit, Core i7, laptop. I plugged the usb cable in while holding ESC and then released. A driver installed but it does not show up as RK29 Device in Device Manager.
I tried updating the driver from the Rockusb folder but when I navigate to the Unified Driver/Rocksub/x86/win7/ folder it says "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 32-bit systems."
-
I have tried 2 different computers. When I connect the usb to the AirPad while holding the Esc key, the Air Pad boots and the PC installs the usual mass storage drivers. Then the Rockchip Batch Tool cannot see the AirPad.
If I try to install the Rocksub drivers manually, by right c;icking and selecting Install, I get the message that "The INF file you selected does not support this method of installation".
I don't know what to do next. I've rooted Android devices before and I'm pretty familiar with the process. Please, any ideas what is wrong?
Thank you.
-
To update your ROM:
1. Download AirpadUpdater.zip and 110920_002_airpad_rooted.img. Unzip AirpadUpdater.zip. It contains driver files and a flash program.
2. Power off your tablet
3. Hold down the ESC button and then connect the USB cable from your tablet to your computer. Release the ESC button after the USB cable is connected.
4. If you have not already installed the Rockchip driver file, install the appropriate Windows driver from AirpadUpdater.zip. In device manager, if you choose 'View by Connection' and navigate through the list to find USB devices, the tablet needs to appear as 'RK29 Device'.
[/quote
This process does not work. When I Hold down the ESC button and then connect the USB cable from my tablet to my computer, the tablet boots and the computer installs the usual mas storage drivers.
What is wrong?
-
http://dl.dropbox.com/u/36442225/AirpadUpdater.zip
http://dl.dropbox.com/u/36442225/110902_001_airpad.img
http://dl.dropbox.com/u/36442225/110920_002_airpad_rooted.img
To update your ROM:
1. Download AirpadUpdater.zip and 110920_002_airpad_rooted.img. Unzip AirpadUpdater.zip. It contains driver files and a flash program.
2. Power off your tablet
3. Hold down the ESC button and then connect the USB cable from your tablet to your computer. Release the ESC button after the USB cable is connected.
4. If you have not already installed the Rockchip driver file, install the appropriate Windows driver from AirpadUpdater.zip. In device manager, if you choose 'View by Connection' and navigate through the list to find USB devices, the tablet needs to appear as 'RK29 Device'.
I'm really having a tough time with this. I don't own any Windows machines anymore, but I do have a Windows 2000 virtual machine on my Linux box. I can't seem to get the rockusb driver installed. Here's what I try:
0) Fire up my windows virtual machine. Unpack AirpadUpdater.zip. The result is an RK Batch Tool and a Unified Driver folder.
1) power off tablet (note --- I tried both real powered off (holding down power button and powering down) and "sleep")
2) hold down the ESC button (ON THE TABLET, the right side of the rocker button on the top of the airpad)
3) Plug in the tablet, and tell the virtual machine to connect the USB removable device to the VM.
4) Release the ESC button
Windows 2000 says it's detected new hardware, and calls it "rk2918 sdk" (if just in sleep mode... if I actually power down and do this., the only difference is that the airpad shows up as "USB Device" rather than "rk2918 sdk"). It prompts me for drivers, and I navigate to the Unified/Driver/Unified Driver/Rockusb/x86/2000 directory and choose the "rockusb" inf file (the only thing it'll let me choose). It then pauses for a second and announces "Windows was unable to locate a driver for this device." and graciously offers to let me try it all over again.
Has anyone tried the airpad update using Windows 2000 and actually gotten the driver to install properly? Has anyone done so in a Windows 2000 running under VMware in a virtual machine on Linux?
BTW, if I right-click the "rockusb.inf" file and choose "Install" I get absolutely nothing to happen. It doesn't appear to install anything, and gives me no error messages or dialogs at all.
It would be really wonderful to be able to update the airpad firmware on Linux without resorting to Losedows at all, but I guess that's a lot to ask for. I'll be watching the forums with bated breath hoping to see announcements that someone's figured it out.
-
http://dl.dropbox.com/u/36442225/AirpadUpdater.zip
http://dl.dropbox.com/u/36442225/110902_001_airpad.img
http://dl.dropbox.com/u/36442225/110920_002_airpad_rooted.img
To update your ROM:
1. Download AirpadUpdater.zip and 110920_002_airpad_rooted.img. Unzip AirpadUpdater.zip. It contains driver files and a flash program.
2. Power off your tablet
3. Hold down the ESC button and then connect the USB cable from your tablet to your computer. Release the ESC button after the USB cable is connected.
4. If you have not already installed the Rockchip driver file, install the appropriate Windows driver from AirpadUpdater.zip. In device manager, if you choose 'View by Connection' and navigate through the list to find USB devices, the tablet needs to appear as 'RK29 Device'.
I'm really having a tough time with this. I don't own any Windows machines anymore, but I do have a Windows 2000 virtual machine on my Linux box. I can't seem to get the rockusb driver installed. Here's what I try:
0) Fire up my windows virtual machine. Unpack AirpadUpdater.zip. The result is an RK Batch Tool and a Unified Driver folder.
1) power off tablet (note --- I tried both real powered off (holding down power button and powering down) and "sleep")
2) hold down the ESC button (ON THE TABLET, the right side of the rocker button on the top of the airpad)
3) Plug in the tablet, and tell the virtual machine to connect the USB removable device to the VM.
4) Release the ESC button
Windows 2000 says it's detected new hardware, and calls it "rk2918 sdk" (if just in sleep mode... if I actually power down and do this., the only difference is that the airpad shows up as "USB Device" rather than "rk2918 sdk").
[...]
Actually, I see that it is very important that this thing be turned OFF (really off, not sleeping). It shows up as a different vendor ID and Product ID. When I connect the airpad to W2K with the thing powered off and the esc button held down, it connects as VID 2207 and PID 290A, which matches what is in the INF file for the driver.
Unfortunately, it matters not one whit. Even with the device really powered off and connected with the expected VID/PID, W2K insists it can't find the driver even though I point right at the rockusb.inf file in the Rockusb/x86/2000 directory of the Unified Driver folder.
I'm still stumped. How in the world is this supposed to work?
GOT IT!
This was weird, but I managed, through tons of googling, to find another place where someone had posted rockusb drivers. I downloaded them, and did a Linux "diff" on the binary .sys file (it was identical) and the text .inf file --- the inf file for Windows 2000 was in fact different. When I modified the rockusb.inf file from the X10 Airpad.zip to match the other, it did indeed install correctly.
Here's what I had to do:
Way down toward the bottom of the .inf file was this stuff:
;--------- Manufacturer and Models Sections ----------------------------------
[Manufacturer]
%MfgName% = Rockchip,NTx86,NTamd64
; DisplayName Section DeviceId
[Rockchip.NTx86]
%RK29_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_290A
%RK281X_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_281A
%RK28_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3228
%RKCAYMAN_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_273A
%RK27_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3201
%RKCROWN_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_261A
%RKNANO_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3226
The other site's rockusb.inf had this:
;--------- Manufacturer and Models Sections ----------------------------------
[Manufacturer]
%MfgName% = Rockchip,NTx86,NTamd64
[Rockchip]
%RK29_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_290A
%RK281X_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_281A
%RK28_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3228
%RKCAYMAN_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_273A
%RK27_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3201
%RKCROWN_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_261A
%RKNANO_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3226
; DisplayName Section DeviceId
[Rockchip.NTx86]
%RK29_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_290A
%RK281X_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_281A
%RK28_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3228
%RKCAYMAN_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_273A
%RK27_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3201
%RKCROWN_DeviceDesc%=Rockusb_DDI, USB\VID_2207&PID_261A
%RKNANO_DeviceDesc%=Rockusb_DDI, USB\VID_071b&PID_3226
That is, the "Rockchip.NTx86" block was duplicated as a "Rockchip" block.
Duplicating that block in the Unified Driver/Rockusb/x86/2000/rockusb.inf file STOPPED the "Windows could not find a driver for this device" error, and replaced it with a "Windows has found a driver" --- and I was then able to flash the rooted firmware!
Woo Hoo.
I have no idea if this issue fixes things for other versions of Losedows, as I don't own any other version (and God willing, never will). But there you have it, this fixed it for me.
-
I am getting no help on this driver issue either. Windows 7 64bit, rockusb will not install correctly.
Same problem as RickM.
Please help X10
XP Machine installed driver, Rooted image now installed. Now what to do?
-
To those of you having problems updating the AirPad, here is what worked for me. I've started with the instructions earlier in this thread and added some clarifications. Thanks to those who tried to help.
The tools included below will completely reflash your Airpad. Do this with a plugged in, fully charged Airpad. I haven't experimented with what happens when this process fails and nor should you! Flashing the Airpad with a new ROM will erase all data and installed programs on your Airpad! After rebooting you will be able to log into the Android Market and redownload your purchased applications.
http://dl.dropbox.com/u/36442225/AirpadUpdater.zip
http://dl.dropbox.com/u/36442225/110902_001_airpad.img
http://dl.dropbox.com/u/36442225/110920_002_airpad_rooted.img
To update your ROM:
1. Download AirpadUpdater.zip and 110920_002_airpad_rooted.img. Unzip AirpadUpdater.zip. It contains driver files and a flash program.
2. Power off your tablet. Off, not sleeping.
3. Hold down the ESC button (the Back button on the Airpad) and then connect the USB cable from your tablet to your computer. Release the ESC button after the USB cable is connected.
4. If you have not already installed the Rockchip driver file, install the appropriate Windows driver from AirpadUpdater.zip.
If the driver did not install upon connecting the AirPad, press the Windows key. Right click Computer. Choose Properties. Click Device Manager. Find the RK29 device. It will probably be an Other or Unknown device. Right click the RK29 device and choose Update Driver. Choose Browse and navigate to the appropriate driver and install it.
In device manager, if you choose 'View by Connection' and navigate through the list to find USB devices, the tablet needs to appear as 'RK29 Device'.
5. Run RKBatchTool.exe. If you have installed the RK29 driver and successfully connected the Airpad in flash mode then the first box in the connected devices lists will appear green.
6. Select the “…” button in the top right hand corner of the window and choose 110920_002_airpad_rooted.img. You may have to navigate to the image files or copy them to the same directory as the RKBatchTool program.
7. Press Upgrade
8. It will take several minutes for the ROM to flash, for the Airpad to reboot and reinitialize, and then for the Airpad to reboot once more. Do not interrupt this process.
Good luck
-
Thanks for this information RickM.
:)
I am accustomed to rooting android devices, and have done so to a couple of phones for various reasons; tethering, changing ROMs, etc., but am wondering what is the purpose to rooting the X10 AP.
Can you briefly explain? If it is something to do with stopping the cell standby usage I am all over it.
-
The airpad is actually already rooted, the new ROM just adds the "su" command and SuperUser.apk" so you can actually do root commands from a terminal emulator.
AFAIK, no fix for the "Cell Standby" thing has been given yet --- but X10's battery usage tests were done even though the device claims a huge fraction of battery usage from "Cell Standby."
-
Any explanation why the rooted flash images were removed from circulation? The limitations on of the Airpad are frustrating.
Through substantial testing have discovered that wifi using WEP is unusable. Pad only works well with completely open APs.
Anyone else seeing similar symptoms?
Is there a list of supported USB-ethernet NIC devices?
-
Reading between the lines it appears that X-10 did not have permission / license agreement to be able to provide AP with Android Market / the Goggle Android Experience.
X-10 it seems does not want any direct connection between them and the earlier ROM images. They are availble if you do some exploring however.
My AP experience is that it works very well. Mine has ROM Ver. _001 the original early release one. I view NetFlix, stream movies from the Home Media Server over WiFi, do a little web surfing on it . Mine now has hundreds of hours of useage on it and no problems except the extremely short battery life which is closer to 2 1/4 Hr. than the 6 they claim.
FYI This same pad is sold under a different name for less cost if one looks hard enough.
-
Any news on this? I'd love to be able to root this. Are the ROM images available somewhere (they don't seem to be out there anymore).
Thanks,
Shawn
-
ncshawng clues to do this are found here if you look! ;)
As I tell most check my forum !
However I can't say for sure if the process will work with the newer Airpads.
The roms are still available.
-
To those of you having problems updating the AirPad, here is what worked for me. I've started with the instructions earlier in this thread and added some clarifications. Thanks to those who tried to help.
The tools included below will completely reflash your Airpad. Do this with a plugged in, fully charged Airpad. I haven't experimented with what happens when this process fails and nor should you! Flashing the Airpad with a new ROM will erase all data and installed programs on your Airpad! After rebooting you will be able to log into the Android Market and redownload your purchased applications.
http://dl.dropbox.com/u/36442225/AirpadUpdater.zip
http://dl.dropbox.com/u/36442225/110902_001_airpad.img
http://dl.dropbox.com/u/36442225/110920_002_airpad_rooted.img
To update your ROM:
1. Download AirpadUpdater.zip and 110920_002_airpad_rooted.img. Unzip AirpadUpdater.zip. It contains driver files and a flash program.
2. Power off your tablet. Off, not sleeping.
3. Hold down the ESC button (the Back button on the Airpad) and then connect the USB cable from your tablet to your computer. Release the ESC button after the USB cable is connected.
4. If you have not already installed the Rockchip driver file, install the appropriate Windows driver from AirpadUpdater.zip.
If the driver did not install upon connecting the AirPad, press the Windows key. Right click Computer. Choose Properties. Click Device Manager. Find the RK29 device. It will probably be an Other or Unknown device. Right click the RK29 device and choose Update Driver. Choose Browse and navigate to the appropriate driver and install it.
In device manager, if you choose 'View by Connection' and navigate through the list to find USB devices, the tablet needs to appear as 'RK29 Device'.
5. Run RKBatchTool.exe. If you have installed the RK29 driver and successfully connected the Airpad in flash mode then the first box in the connected devices lists will appear green.
6. Select the “…” button in the top right hand corner of the window and choose 110920_002_airpad_rooted.img. You may have to navigate to the image files or copy them to the same directory as the RKBatchTool program.
7. Press Upgrade
8. It will take several minutes for the ROM to flash, for the Airpad to reboot and reinitialize, and then for the Airpad to reboot once more. Do not interrupt this process.
Good luck
Has anybody got this to work with an Airpad-X? The button sequence must be different, since I can't get Windows 7 or XP to recognize the device as being a RK29 device or compatible with the Rockchip drivers.
-
Word is this won't work with the new 7 or 10 in. Airpads :'(
-
I just got my Airpad X a week ago, and while everything seems to work ok, there is no "su" or superuser.apk installed that I can find anywhere. Is there someone in development that can build a ROM with these installed, and make it available? PLEASE? I'd really appreciate it!
-
Looks like the 2 rom files vanished from drop box.
both files get 404 errors now. APv1 users should
be able to get root with rom 002,if it were there.
-
Looks like the 2 rom files vanished from drop box.
both files get 404 errors now. APv1 users should
be able to get root with rom 002,if it were there.
Actualy the files are still available on the net if one realy wants to look.
I' ve comented on this many times.
-
Right - I've seen them for the AP7 - don't think it's the same set of ROMs though, for the APX. ??
-
Right - I've seen them for the AP7 - don't think it's the same set of ROMs though, for the APX. ??
Correct these will not work with the AirPadX.
X10 hasn't released anything for them nor is there any rumor that they will anytime soon. :(
-
You are right Tuicemen.... the updater and ROM files 1, 2, and 4 are available and I found them this afternoon after checking your earlier comments. I have not tried the rooting yet but learned a long time ago (that's anything over 6 months in internet time) to get the files when you see 'em then figure it out later. Thanks! #:)
-
Hi all,
Merry Xmas
New to all this.
Can the rom on a new (12/08/2011) airpad 7p be set back to rom 1 or 2?
Tried directions posted earlier for Airpadupdater but program doesn't see the airpad?
thanks
GJF
-
Simple answer ,no.
The origianl X-10 7" AP ,the follow up 7 P which started shipping around mid. Oct and the 10" one all have different operating systems and require different ROMs.
There rreally should be different threads for each of these and all comments should be posted in or moved to the correct thread(s) as current state of mixed verisions in same threads is only leading to mass confusion.