Anyone have one or know anything about it or rooting the unit?
Android™
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
thanks
b.g.
I saw this go on sale on eBay. I'd like to know as well.
Info base
Got one works great, heavy. No info yet. Like the 500gb system memory. no usb debugging option, only via ethernet, have not yet accessed it. No root, super su , nor busybox will install. haven't looked into bootloader or recovery yet.
b.g.
things I think I know
Had to use ethernet cable, setting address to 192.168.42.10 as the asus will put a hard address of 192.168.42.1 255.255.255.0. Able to adb by "adb connect 192.168.42.1" pinged it first to make sure network setting ok. Standard ethernet cable from asus directly to pc. Prob need binaries from intel system, either from a linux based machine or tablet/phone intel based. was able to adb reboot into either recovery (e3) or bootloader (droidboot), could not get fastboot to give commands to the asus, always "waiting for device", it would still ping however. Droid explorer crashes when attempting access, suspect it tries via usb.
Need someone smarter than me to jump in.
b.g.
thanks for the small info, would like to know about full root as well.
tablet
if I could find a screen protection and case for it, I could put those ipads to shame, when I go out.
b.g.
hehe, you surely would get a workout as a benefit!
more little things
Still no progress, except in bootloader, only open port is 1234, that being said. still cannot connect with fastboot; however, when I "adb connect" to this tcpip;port in the bootloader and adb devices comes back as "192.168.42.1:1234 offline".
I'm thinking I'm at the end or there maybe another bootloader type program on sdcard to access, as droidboot appears to looking for an update on drive "e".
b.g.
a littl off topic, but does anyone know how to open and install more memory ram? what kinda ram does it take?
sodimm?
Ram
geminihc said:
a littl off topic, but does anyone know how to open and install more memory ram? what kinda ram does it take?
sodimm?
Click to expand...
Click to collapse
No ram access panels at all. Do not even see in storage all HD. see screenshot
unknown command 'CNXN'
In the bootloader, when i issue "adb connect 192.168.42.1:1234" i get the following response from the aa3 "unknown command 'CNXN'"
b.g.
whgarner said:
No ram access panels at all. Do not even see in storage all HD. see screenshot
Click to expand...
Click to collapse
interesting, i ask because here: http://us.acer.com/ac/en/US/content/model/DQ.STPAA.001 (press full datasheet and search for 8gb) it seems to indicate there is one slot that you can install up to 8gb of ram. "SDRAM"
geminihc said:
interesting, i ask because here: http://us.acer.com/ac/en/US/content/model/DQ.STPAA.001 (press full datasheet and search for 8gb) it seems to indicate there is one slot that you can install up to 8gb of ram. "SDRAM"
Click to expand...
Click to collapse
i opened up the back to see what was inside. the 500gb hard-drive is definately easily replacable with SSD (the problem is seeing if it'll boot). most things were covered and the only thing exposed is some unknown PCB board. it does have some places where you can plug things in it seems like...
https://plus.google.com/photos/1132...s/6093720382613628977?authkey=CK3xwte3qpiv2QE
Bootloader(droidboot)
The bootloader is definitely looking at the ext sd slot for its command when it boots up. It says "no valid installer found" on the "E" drive. If I put a file named "installer.cmd" in the root directory of the sdcard then I get a valid installer found. Tried placing "fastboot reboot" into installer.cmd with and without quotes, but no reboot. Need to find how to script installer.cmd to accept a command.
ps-nice pictures, good to see people interested
b.g.
this might be a stupid question but is the bootloader phyiscally located in the 500gb hard-drive or else where? i was wondering what happens if we swap out the drive with say, a drive that is loaded with windows. what happens when you power on? i believe all of the components on this has drivers and everything already recognized by windows 8.
Pulling hd
geminihc said:
this might be a stupid question but is the bootloader phyiscally located in the 500gb hard-drive or else where? i was wondering what happens if we swap out the drive with say, a drive that is loaded with windows. what happens when you power on? i believe all of the components on this has drivers and everything already recognized by windows 8.
Click to expand...
Click to collapse
Might be a problem booting without proper bootloader in firmware, no bios or efi access, probably wouldn't hurt it. Wondering if pulling hd and accessing in linux or osx would allow you to place correct binaries for root? Thanks for idea.
b.g.
Still trying to root
Thought I was close, but not close enough.
So far, removed hard drive from unit and was able to see and access files on drive via linux. I was able to install busybox and SU (x86 from Supersu zip, x64 was not a binary) into both bin and xbin, installed supersu into /system/app, fine so far. Upon reboot all works fine. Starting supersu says binaries need to be updated-fails, cannot update. In terminal attempted su command I get "permission denial broadcast asks to run as user" and about 10 other lines. Stuck now, tired of looking. Anybody with ideas are welcome.
ps was able to chmod 777 xbin and system on linux, but system reverted to 755 on reboot, locking me out, i suspect, from supersu updating binaries.
bill g.
I don't have one of these but am seriously considering one. I hope you get this all figured out!
willing to try almost anything
I'm going to try a few more times and things, but practically speaking I'm done. Love the unit though.
B.g.
not sure if this is helpful, but there is another intel baytrail android device that someone seem to be able to install windows 8.1 on to successfully:
http://cngadget.info/2014/06/11/windows-8-1-firmware-for-teclast-x98-3g-instructions/
also, quite sure you did this already, but have you tried connecting a USB male to male from PC to the android ? what happens?
Related
I am new to the Android platform so please excuse any silliness on my part…
Below are the steps I took to successfully allow my Vizio Tablet (VTAB108) to connect via USB using the generic Google ADB driver as Vizio does not include ADB access for the tablet.
History:
I am trying to Root my tablet and from what I read throughout the forum, the easiest steps to root a tablet is using the SuperOneClick method.
Since SuperOneClick requires ADB access and the Vizio does not include the ADB driver (and the generic Google) do not work out of the box I was at a loss to how I would run SuperOne Click.
This article are the steps I took to get ADB access working with Windows 7 x64 and the Vizio Tablet.
I am hoping my steps here can further lead to root access for this tablet.
As an FYI, I was still unsuccessful in getting SuperOneclick to completely run after following these steps, but maybe someone has an alternate method of rooting now that ADB access is available? /me crosses fingers
It would stop at Step #6 at which time I would disconnect and reconnect the tablet. It would contine to step #8 but then finally fail. If anyone has an alternative to SuperOneClick, I would gladly try it.
IMPORTANT:
The instructions below assume you have already put your Tablet into USB debugging mode.
The instructions below assume you are running Windows 7 x64. If you are running x32 versions of your OS, modify the below settings as apporopriate for your OS[/B].
1. Download and install the Google Android SDK.
(Being this is my first post, I cannot post a URL so google the following topic exactly and click the first link):
what-is-adb-and-how-to-install-it-android
2. When you get to the USB driver install you will have to manually modify your android_winusb.inf settings file to allow Windows to recognize your Vizio Tablet using the generic Google ADB-USB driver.
3. Find the "usb_driver" folder in your sdk directory. (Mine was: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver).
4. Right-click "android_winusb.inf" and open it with notepad or your favorite text editor.
Under the [Google.NTamd64] section, paste the following:
Code:
;Vizio Tablet
%SingleAdbInterface% = USB_Install, USB\VID_0489&PID_E040&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0489&PID_E040&REV_0227&MI_01
then, open a command prompt and type the following:
Code:
echo 0x489 >> "%USERPROFILE%\.android\adb_usb.ini"
5. Right-Click the unknown device in Windows Device Manager (Under Other devices) and manually install the driver for your Tablet.
NOTE: Originally my tablet connected to the computer and installed the regular Windows 7 Mass Storage driver. I had to remove this driver before I could see the device listed under "Other Devices". Follow these instructions if you need to remove your generic Mass Storage driver:
Code:
A. Unplug all removable devices (USB drives, Thumb Drives, SD Cards, Etc...) but leave the Android phone plugged in.
B. Open Windows Device Manager.
C. Select "Universal Serial Bus Controllers"
D. Select USB Mass Storage Device.
IMPORTANT: Click on the details tab and select "Compatible Ids" under the Property drop-down. You should see three items listed under Value. If not, you are looking at the wrong Mass Storage Controller.
E. Select Uninstall Driver
F. Close the window.
G. Right-Click your computer name at the top of device manager and select "Scan for Hardware Changes".
H. Your new "Android Phone USB device" with a Yellow Exlamation mark! will appear under Other Devices.
I. Click on the "Android Phone USB device"
J. Select "Update driver software"
J. Select "Browse my computer for driver doftware"
K. Browse for the location that you have unzipped the android_usb_windows ( Mine is: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver )
6. Now test to make sure you can access your device in USB Debug mode:
Type the following from a command prompt:
adb kill-server
adb devices
You should see your device serial number at the command prompt and in Windows Device Manager if everything worked.
drivers
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
USB Drivers Not Installing
[email protected] said:
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
Click to expand...
Click to collapse
I grabbed those drivers a couple of days ago and could not get Win7 or WinXP to install them with the vtab1008.
I can use adb to interface with the vtab008 (using Linux and Win7), but GingerBreak and SimpleOneClick (which uses GingerBreak) are unable to root the vtab1008.
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Agreed
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
This is my thinking EXACTLY!
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
Yes, I agree. If there's no root, the tablet is not worth it.
The drivers worked for me.
I downloaded the drivers from the Vizio site and when I plugged the VTAB into my computer I manually installed the driver. I just used adb to grab a bunch of screenshots.
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
You can get to recovery mode by holding down both volume buttons and the power button. Details
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Mark0266 said:
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Click to expand...
Click to collapse
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
marvin02 said:
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
Click to expand...
Click to collapse
Thats the problem the prompt never comes up. Running Windows 7
Well I got the driver for adb to install but it still will not show up when I do adb devices
Bootloader?
the.joeba said:
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
Click to expand...
Click to collapse
Did you actually get into the bootloader? adb reboot bootloader simply reboots the device for me.
So whats with gingerbreak? No love with it? I thought this thing was rooted already prior to shipping? Hmmm. My bro just ordered one for me and I am curious about getting it rooted. Lets get this thing rooted and overclocked and get it some love. Also, whats the word on honeycomb on this beast? anything?....
Mark0266 said:
Well I got the driver for adb to install but it still will not show up when I do adb devices
Click to expand...
Click to collapse
Same here.
Rooting help
I have some coding knowledge, but have never worked on rooting a device. I did not pay for mine, so if anyone has references to some info I can look at about obtaining root then I will work on mine without fear of bricking it.
I have been at this for weeks, to no avail.. tried changing params in Gingerbreak, tried running it under every condition possible, and the only thing I haven't tried is changing how GingerBreak is using the /sdcard/ mount point, as that's where the internal memory is mounted to.. It's a pretty odd move to make, and I don't like having my true sdcard in /sdcard/external. what a crock :/
This tablet has to have a way to be rooted, I tried an older version of gingerbreak 1.1 just kept running, never failed, but didn't root the tablet just kept running, like it was gonna root the tablet, kinda weird, I do know that the bootloader is not locked down, my wife works for vizio, the company gave there employees a tablet for free
(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 since cm7 is so close, I decided to try the flashable cwm from indirect. Unfortunately, after that all that happens is my nook tries to boot, I see the white screen with the package, and then it turns off. If I have it plugged in, it will just loop.
I have partitioned a 4gb sandisk with a 50mb FAT 32 partition as the primary, and have given it the lba and boot flags in gparted from my ubuntu laptop. I never could get it to boot off the sd card.
So now I must ask, where do I go from here. I've searched and crawled this forum, but with the boot loop and not being able to boot off of SD, I am unsure where to go next.
Any tips? To me, it looks like it just keeps trying to boot from the recovery. N + Power yields same results as above. Could really use some help with this head scratcher
So you cant access to CWM at all, if not somehow you must make the sdcard method to work in order to apply the fix posted by Indirect, that is the only way im afraid.
~ Veronica
http://forum.xda-developers.com/showthread.php?p=21785424 there's a link to indirects fix for broken recovery.
_______sig starts here______
Even you were a beginner once
If this post helped click the thanks button!
remember QTIP - Quit Taking It Personal
Okay, I get that. I have two questions though,
1: Does this mean I have to do the recovery method vs the bootable sd card?
2: How am I supposed to run commands to a device that keeps rebooting and doesn't give windows time to communicate with it, or will it send commands to it even though its rebooting?
cleverghost said:
Okay, I get that. I have two questions though,
1: Does this mean I have to do the recovery method vs the bootable sd card?
2: How am I supposed to run commands to a device that keeps rebooting and doesn't give windows time to communicate with it, or will it send commands to it even though its rebooting?
Click to expand...
Click to collapse
To apply Indirect's fix first you need to use Goncezilla's CWM sdcard method to boot into CWM once in CWM basically you use adb tools to fix it, use the link posted below by @dodgepot and read the OP carefully to understand the process.
~ Veronica
Thank you for the replies....
So I've gone through and tried once again to get my nook to boot from SD, and still I can't get it to boot. There is a way to do it using DISKPART in windows, I've made the 50mb fat partition, and set it to active. Have there been any other issues with getting it to work?
Poked around the CM7 thread again, apparently CelticWebSolutions was having a problem booting from an sd card.
Anyone know what he did exactly?
It works! Installing android sdk now
cleverghost said:
It works! Installing android sdk now
Click to expand...
Click to collapse
If you are on windows there is no need of SDK it will just give you troubles with the drivers, you should already have the drivers and adb if you rooted your nook tablet before. The adb drivers came in the zip provided for root and should be in C:\ntroot folder.
~ Veronica
I had access to a xp laptop when I did it on before. Using a win 7 64 bit right now, and indirect's batch file stops part of the way through. I had problems in 64 bit before, using the usb drivers from snowball's mod. Guess its a 64 bit problem. (have used usbdeview and I have verified it sets up as an android composite device.)
cleverghost said:
I had access to a xp laptop when I did it on before. Using a win 7 64 bit right now, and indirect's batch file stops part of the way through. I had problems in 64 bit before, using the usb drivers from snowball's mod. Guess its a 64 bit problem. (have used usbdeview and I have verified it sets up as an android composite device.)
Click to expand...
Click to collapse
i have a windows x64 bits too and when i rooted did not have any problem, do not install sdk it is not necessary, run the runmefirst.bat the one that comes in the .zip with the root files not the one that comes in the drivers.zip from Indirect's root. Snowball uses the same drivers as Indirect.
~ Veronica
I did everything stated above ... still a no go.
I tried indirect's driver half a dozen times and can never seem to get it working on x64. I decided to format my laptop and put xp on it. Like I said, last time I used XP, no problems at all.
Edit: Okay, so I tried it on another x64 machine, and I still run into the same issue!
1. run runmefirst.bat
2. Plug in nook
3. Right click nook device with /!\ and update drivers from c:\ntroot
4. Open up bat from indirect's thread
5. Y, Enter
6. Program starts abd..... locks up right after it states it, I waited a good 10 mins for results.
7. Use USBDeview and delete all references to usb mass storage, nook, and android devices. Unplug nook.
8. Plug in nook and repeat 3-6
9. Bang head against wall lol.
It's probably something stupid I overlooked. Feel free to flame away, I'll take it like a man XD. I started with a nook color, but this is pretty much my first tablet experience. You guys have a lot of experience, and I just want to make sure I am not missing something obvious. (I guess I just don't want to seem like a noob, more like a half noob )
Truth be told, I don't know if this is an issue... but I am runing W7x64 Ultimate N
Alright, so adb devices lists my device as "recovery".
I run the script and it still seems to just stop.
Uhmmm the steps you've done are right, I run a windows professional no N edition but that shouldn't be a problem. Maybe try disabling firewall, antivirus if any also Use ccleaner to clean your registries and cache of your machine, reboot and then try again, I want to repeat do not install SDK (just making sure).
~ Veronica
Sent from XDA premium using my Nook Tablet
okay great! Then I do understand the steps.
Yep, no SDK.
Edit: Going to crash now, ill wake up in a bit and take another crack at it. Thanks for your help so far
Alrighty. I woke up again and decided to give it a try from step one. Still a no go. Going to try wiping my drivers again. I've also disabled all antivirus/antimalware....
Looks like its going to be a fun day heh.
ok keep us updated on how you doing.
~ Veronica
Should I see the nook and sd drives mounting in Windows? Right now, I see the drives, but I can't access them. I don't know if that matters or not.....
Also, when I do an adb devices, mine shows as:
Code:
<String of numbers> recovery
Thats correct?
I also took a look at the batch file and might try to run the first few commands to see if I can find where the problem is manually. I have a feeling it's stopping at:
Code:
adb wait-for-device
We'll see though.
EDIT: Unless when you run the command it's supposed to not do anything, then yes. It's hanging.
Alright. Here is what I've found out.
I've done some forum crawling, and I happened upon a post by Loglug where he says to run the following commands:
Code:
adb shell mount -t vfat /dev/block/mmcblk0p6 /data
adb shell dd if=/dev/zero of=/data/BCB bs=1 count=1088
adb shell dd if=/dev/zero of=/data/BootCnt bs=1 count=1
adb reboot
All of the commands work except the second one. It basically echos back and tells me how to use the command. Now, I read a little further into his post and it says that if you do not get the BN recovery after 8 reboots, your recovery partition might be messed up. Could this be what is preventing me from recovering?
EDIT: NEVERMIND! I am up. Sorry, I feel pretty stupid now lol. I just ran the second command wrong -_-. Sorry, my answer was in the forums, just couldn't find it!
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!
Hello All,
So there is very little documentation on the PX102 online as of yet, let alone AOCOS products in general (at least on english sites which I have scoured). First off, I'm currently using OSX 10.6.8 and have the current Android developer tools package that was downloaded from their site about three hours ago (just to be clear). The PX102 is running 4.1.1 and the tablet is a fresh restore (I had a number of apps downloaded but considered that some may have been interfering...).
I will be attempting to root via psneuter exploit from SuperOneClick v2.3.3, however in the terminal when I execute "adb devices" it returns "List of devices attached" with blank space underneath...
I have tried to kill/restart server, run "adb usb", and a couple other small things to no avail.
Yes, usb debugging mode is enabled as well.
I would really like to attempt/execute this all via OSX, however name an OS and I have it at my disposal...
I admit- I am a noob in various ways, especially to android as this is my first android device. Hoever, I also consider myself to be rather self sufficient in terms of sourcing knowledge and troubleshooting, which is why I humbly ask for guidance in this endeavor.
Also, feel free to ask me any questions about the PX102 (via PM only please! I dislike threads being fuddled with asides...).
I'm not seeing too many people claiming to have these tablets though there is quite a bit of interest in them.
Anyone?
For windows you can try rkbatchtool v1.5 to get the correct drivers
Rooted mine
I rooted mine, wasn't easy though.
First problem, you need a adb driver that works on this rockchip tablet that doesn't have a built in ADB driver. Also I didn't have much luck on the chinese language AOCOS forum.
The only way I found to get one is:
1) download and install the morborobo phone manager software from moborobo.com. Yes this is a risk to your pc. God knows what else it did to my pc.
2) let IT find a driver. It will download and install two unsigned drivers.
3) those drivers aren't enough. You need to generate adb_usb.ini in c:/Users/%username%/.android/adb_usb.ini (if you're on windows 7)
Installing the SDK does that automatically otherwise you need to run "android update adb" or something to generate it
4) put the vendor id at the end of adb_usb.ini in the case of AOCOS the vendor is 0x2207
I tried using a premade adb_usb.ini with all of the vendor ids. That didn't work. It worked when I put the right on only.
NOTE, that vendor ID exists nowhere online. I had to find it by reading it directly from the device using USBVIEW from http://digital.ni.com/public.nsf/allkb/335A90747734097886257070006415B9
5) Now you should have a working adb driver. Plug the machine in and type "adb devices". It should see yours
6) now comes the rooting.
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1886460
The script is here: http://uploaded.net/file/0fpyh5c5
the videos showing how are here http://forum.xda-developers.com/showthread.php?p=33470626#post33470626
Note there IS a hacked adb driver that doesn't need a vendor ID, BUT it doesn't work for rooting, it's too old to have the restore feature you need for a jelly bean root.
The PX102 is cool, but mine has some problems:
1) the keyboard charge connector is bad, I have to send it back
2) the battery sucks... I'm sending back the tablet too, hopefully that will fix it
3) never drop one of these, mine only fell a couple feet and it's flaky now. :/
4) the camera is fake. It's not the 2mega pixels it says. It's super low quality and maybe vga. They put in bull**** fractal interpolation software to try to fake higher res
The keyboard is no where near as nice as a transformer, the tablet only rests on the keyboard and can fall off.
Still it's a nice machine. I have my memory cards formatted ext2 (from a previous tablet). I can mount them but the machine won't boot with an ext2 card plugged in. I have to take the card out, boot the machine, then plug it in and mount it.
I even managed to install GNU Gcc/ gnu tools
You can also try this: http://www.androidtablets.net/forum/rockchip-rk3066-tablets/46964-root-your-rockchip-3066-a.html
Or this: http://valentijn.sessink.nl/?p=382