It's an ainol Novo7 Venus, 7" tablet.
According to Windoiws ADB, the vendor id is 10D6, and the product code is 0C02.
I've successfully flashed Android version 4.2.2 onto the device (from 4.1) using Windows.
My main develoment machine runs Ubuntu 12.10, but ADB on this machine won't recognise the Anal (ainol) tablet.
lsusb identifies the device as 10d6:0c02 from Action Industries Ltd, so it's almost a dead cert that the vendor id is correct.
I've set up udev rules to try and get it recognised, but it just won't have it.
Any ideas?
Thanks.
Geoff.
Related
This is for if you have flashed a rom and it boot loops and when you try and restore and it stays in a bootloop,
I had this issue during the week and freaked out but thanks to termleech who created this http://forum.xda-developers.com/showthread.php?t=1699535 rom I was able to get my tablet back in working order.
This Tutorial is for Ubuntu/Linux (ill try and get one for windows but I wasnt able to do this through windows) for this im also guessing that you have a custom recovery flashed.
Step one:
go to http://source.android.com/source/initializing.html and go down to the section that says configure usb access the file will be saved in this location in /etc/udev/rules.d/51-android.rules
follow that section for all the lines that say "<username>" replace <username> with the account name that you are using,
in my case each of those it was changed to "aaron".
Step two:
Open terminal and type sudo lsusb this will display everything that is connected through usb. you should get something looking like this
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0c45:641d Microdia 1.3 MPixel Integrated Webcam
Bus 002 Device 003: ID 0b05:4d03 ASUSTek Computer, Inc.
Bus 002 Device 004: ID 0bda:0159 Realtek Semiconductor Corp. Digital Media Card Reader
Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 002 Device 006: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 002 Device 007: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 002 Device 008: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Now in the File you created from step one create a new line and replace the values with the values you just got from lsusb
so the line for me looked like this when I pasted it back into the file.
# usbboot protocol on asus (Asus Transformer TF300T)
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", ATTR{idProduct}=="4d03", MODE="0600", OWNER="Aaron"
Step three:
Setting up the Android SDK
This is where I had the most trouble.
So you need to open the market place on Ubunto and download openJDK7, let that install then go to the android site and download the the android tools
http://dl.google.com/android/android-sdk_r20-linux.tgz
extract that to your desktop.
Then in terminal navigate to the folder called tools in the sdk and open it.
then type sudo ./android
that will install the tools and open android sdk manager.
when that opens all you will need to do is tick the tools box and it will install everything you need.
Once that is installed you will need to navigate to the platform-tools folder in the root of that folder.
What I did was also copy the rom that I wanted to flash into the folder just to make it easier on myself.
On your tablet boot it into the custom recovery but by powering the tablet it on and holding the volume down and power button then pressing the volume up.
YOu can leave you tablet in the home screen for the recovery for the next bit.
Step four:
Copying the rom to the tablet.
On terminal you will need to navigate back to the platform-tools folder.
and copy the rom you want to use into it (for this i will call the rom fix.zip this is just for this tutorial)
make sure your tablet is connected now and in the recovery sceen not{/B] fastboot!!!!!
on terminal type sudo ./adb push fix.zip /sdcard
It will look like its doing nothing that pop up saying that it copied it 33 seconds.
Step five:
factory reset x3
then wipe cache and dalvik
then flash + gapps (if not included with rom)
then wipe cache + davlik again
then reboot, on first boot it can take between 2-5minutes to start.
Now you have a working tablet again
Hope this helps those who are stuck! ill try get a guide together for windows and maybe a video if many people end up using this.
if you need to get in touch fast im always on twitter @d_crossfader
I am not responsible if anything goes wrong
How do you give root to a user in ubuntu? Thanks for the help by the way have ubuntu installed made rule but cant transfer because im not root user?
Sent from my HTCEVOV4G using xda premium
lukethepainter said:
How do you give root to a user in ubuntu? Thanks for the help by the way have ubuntu installed made rule but cant transfer because im not root user?
Sent from my HTCEVOV4G using xda premium
Click to expand...
Click to collapse
Just use sudo. There is no root user in Ubuntu-based distros.
almost got it
i followed all steps and when i go to push the rom i get
[email protected]:/media/sdk/platform-tools$ ls
aapt adb.vol03+04.par2 aidl fix.zip source.properties
adb adb.vol07+08.par2 api lib
adb.par2 adb.vol15+16.par2 dexdump llvm-rs-cc
adb.vol00+01.par2 adb.vol31+32.par2 dx NOTICE.txt
adb.vol01+02.par2 adb.vol63+35.par2 fastboot renderscript
[email protected]:/media/sdk/platform-tools$ sudo ./adb push fix.zip /sdcard
sudo: ./adb: command not found
[email protected]:/media/sdk/platform-tools$
any suggestions?
Hey could you enable root by following these steps https://help.ubuntu.com/community/RootSudo then try again as su
Sent from my Transformer Pad TF300T using XDA Premium HD app
On vacation this week will try it when I get home and thank you for helping me your the best
Sent from my HTCEVOV4G using xda premium
No worries, when it happened to me last week I freaked out
Sent from my Transformer Pad TF300T using XDA Premium HD app
I am using the mac version of the SDK and can see the tablet in the mac System Information. It shows:
TP10A:
Product ID: 0x0010
Vendor ID: 0x2207 (Fuzhou Rockchip Electronics Co., Ltd.)
Version: 2.22
Serial Number: 0123456789ABCDEF
Speed: Up to 480 Mb/sec
Manufacturer: unknown
The AGPtek brand, model TP10A is a generic 7 inch tablet running Android 4.0.4, Kernel 3.0.8+, [email protected] #85, build number = rockchip IMM76D.
I have USB debugging turned on. My problem is there are no adb functions that work. For example adb devices reports a blank. adb shell or adb usb reports that no device is present.
I can turn on sharing files across USB from the tablet and read files on it from the mac OS.
Can anyone help me root this? Ultimately I want to turn on wi-fi adhoc mode but just getting adb to talk to it would be a great start - thank you!
RockChip 2906 tablet
I am having the same problem with an inexpensive tablet I bought on amazon. Tried multiple different USB drivers for MOMO9 and Allwinner tablets but the PC (either Win7 or XP) will only see tablet as USB mass storage. ADB Devices returns a blank list. I have asked the seller to see if they can provide USB drivers specific to the model they sent me but no reply as of yet. The specs for my tablet are below:
Model Number - RK702
Android Version - 4.0.4
Kernel Version - 3.0.8+ [email protected] #156
Build Number - Rockchip 2906
I am trying to root. Any help is appreciated.
jcdela said:
I am having the same problem with an inexpensive tablet I bought on amazon. Tried multiple different USB drivers for MOMO9 and Allwinner tablets but the PC (either Win7 or XP) will only see tablet as USB mass storage. ADB Devices returns a blank list. I have asked the seller to see if they can provide USB drivers specific to the model they sent me but no reply as of yet. The specs for my tablet are below:
Model Number - RK702
Android Version - 4.0.4
Kernel Version - 3.0.8+ [email protected] #156
Build Number - Rockchip 2906
I am trying to root. Any help is appreciated.
Click to expand...
Click to collapse
Hi
i have bought an inexpensive tablet too. The Omega OT107.
I can already use adb on that mashine, but i have no luck to get root or even break the bootloader. ( if someone could help me , it would be great)
if you are interrested how to make adb working just drop me some lines and i will give you the details. You will need linux or ( if i find the link again than) windows 7
BR
Gergo
Add unknown device to adb
These are on Linux, so if you're using Windows, it sucks to be you
Add the device in udev like so (my vendor ID in a TP10A GBD is 18d1, My Ampe 10A is 2207), in the file
/etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="18da", MODE="0660", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", MODE="0660", GROUP="plugdev
restart udev: sudo udevadm control --reload-rule
Then add the VID in your $HOME/.android/adb_usb.ini like so:
0x18d1
0x2207
Then restart the server adb kill-server
adb start-server
Works for all the devices that don't show up with adb devices.
Cheers.
Hi,
In fastboot mode my linux distro (Debian testing) can see and reboot the device:
Output of lsusb:
Bus 003 Device 011: ID 0502:33a5 Acer, Inc.
but with ./adb devices, I cannot see anything:
No trace in lsusb, debug usb is on, udev rules are ok, adb_usb.ini is ok and with ADB_TRACE="all", everything is ok except that there is no device in adb...
Any clue?
Thanks.
Ps: I did google around...
There seem to be a problem with fastboot for intel devices on linux. I am running Ubuntu 14.04 and I have an Asus Zenfone 5 a501cg. Adb works fine. I have updated the udev rules. When I try fastboot, the device is not even detected. I see the device connected in lsusb. But fastboot devices shows me nothing. And I have inserted the new device ID when the fastboot mode into the udev rules.
I mean when I installed Intel android drivers in windows, everything works fine. I have used fastboot in windows and it works. But when I use it in ubuntu, it does not work. I have tried searching around. And it seems that intel devices have a problem with fastboot in linux. There are similar questions in forums asked for lenovo phone with intel chip in the intel developer zone and the intel guys are telling why don't you update your udev rules blah blah blah..
Do you guys have same problem??????
Do you guys have a solution???????
Hi, all.
I went through the forums here and googled, but I can't find one working solution.
I have the tablet in subject (Acer Iconia B1-750).
I'd like to root it using guide I found on this forum and with modification for Ubuntu from here.
I can see my device in adb no problem.
When I run lsusb, I see device
Code:
Bus 003 Device 030: ID 0502:367b Acer, Inc.
So far so good.
When I do
Code:
adb reboot-bootloader
the device restarts to something called DROIDBOOT PROVISION OS.
When I type
Code:
lsusb
I can still see the device as
Code:
Bus 003 Device 031: ID 0502:3680 Acer, Inc.
So far so good.
However, when I do
Code:
sudo fastboot devices
I see no device connected.
I tried the -i 0x0502 switch for fastboot, did not help.
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
I tried to modify the ~/.android/adb_usb.ini, no help.
I also ensured I have correct permissions for plugdev on the device using udev rules and I do.
Does anyone have any advice how to force fastboot binary to "see" the device?
@sancho_sk Which Ubuntu version are you using?
Sent From my SM-G928F via Tapa
As I wrote:
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
Nobody? Seriously nobody works with Ubuntu?