Tablet rk2906 after flash it never tablet does not work
Rum used in the flashing device belonging arnova 2g
Then the tablet never works and can not connect to a computer via USB
The computer sees as an unknown device
Hi,
I have TAB264 Yarvik. Only thing I need is to connect it to the RasPI and make USB tether. I test it on Arch Linux on my notebook. I can plug my phone with usb tethering allowed and than I am able to connect to the internet.
However, there is no such option on my TAB264. There is original ROM (4.2.2). I have installed some USB tether apps but nothing worked.
Do I need root or even new ROM? Or is it hardware dependent?
Thank you.
P.S. I can see the tablet in ADB if it helps.
The tablet was uploaded rom not of this tablet. The computer does not detect it. Sometimes supposedly it installs the driver, but says unknown device.
From what I found out it was an attempt to upload it Ainol AX10t-2014032425
The computer does not detect the tablet
The tablet does not turn.
Help
tablet is rooted
tablet has busybox
have iunstalled zt-180 adhoc.....wont see adhoc
have insalled adhoc wifi enabler...wont see adhoc
can anyone help me
im close to tossing the tablet out into the lake...it is useless to me if i cant connect to adhoc wifi
thank you
Calling all A95X MAX owners!
Has anyone successfully connected this TV box to a PC in order to send ADB commands?
I installed the S905X2 USB drivers that come with the S905X2_USB_Burning_Tool. With USB debugging on, I put the A95X MAX into bootloader and connected it to my PC with a male-to-male type-a USB cable, but there was no reaction in the PC's device manager, where you'd expect to see the Android USB driver appear when a connection is made. (I did get power throught the cable, for when I unplugged the power to the A95X MAX it remained on with the USB cable plugged in.)
Is there something I don't know about or has no-one here tried to connect the box to a PC via USB?
It would be useful to send ADB & fastboot commands to this TV box.
I feel your pain
doktorspin said:
Calling all A95X MAX owners!
I also have tried to connect via usb to the a95x max us and MANY other amlogic manufactured tv boxes without success.
You would think some expert person from this forum would respond to this issue once and for all... GRRRR....but noooooooo, no such expert person seems to want to answer the bell here or in any other related tech forum I have gone to. Is it possible no one on the planet knows the answer to this?
Attempting tech support at both gearbox and geekbuying websites, places where one typically purchases such tv boxes have yielded nonsensical/completely useless/incompetent answers so no point going there for any such related support.
Anyway. From what have been able to observe, the burning tool driver shown as "libusb-win32 usb devices" known strangely as the "world cup" driver, "only works for the burning process app as far as the box being recognized by the burning tool app via a USB connection but it seems it has nothing to do with the device being recognized by the ADB.EXE PC side app when using the USB connection.
For that you need an "android composite ADB interface driver". Unfortunately, none of the google or Microsoft or any "universal" ADB USB drivers I have tried, seem to work for these amlogic tv boxes which throws you back to having to go to the amlogic manufacturer to download their drivers from there.
Although this makes almost too much sense, you won't find any downloadable drivers at their site, "amlogicdot com, so we all are back to step one...GRRRRR.
So, until a forum expert from this xda-developers site finally decides to help with this issue....if in fact that will ever happen, we are all pretty much stuck in the mud here as far as the needed USB connection. Until that happens, here is a work around I developed which will let you communicate with these boxes without the need for any USB drivers as long as such amlogic boxes come rooted.
The TCPIP wireless or wired connection trick:
What many folks don't know is that if the box is unrooted you will ALWAYS need to have an initial USB connection before one can switch over to a tcpip connection ("ADB tcpip 5555" command after you have FIRST established a USB connection), but if the box is rooted you do NOT have to have an initial successful USB connection!!!
The secret is to switch over to tcpip at the Android device FIRST by using one of many apps on the android device that activates this such as "WIFI ADB" or "ADB WIFI reborn" app etc. Don't bother with the ones that say no root or any other app that says you need to connect a USB cable first since that defeats the whole point of this post right?...smile.
The app typically will give the IP address of your device along with the command needed on the PC side such as "ADB connect 192.168.1.3:5555" (the device IP address along with its port number ) which allows you to connect your PC to the android device via tcpip WITHOUT ever connecting to any USB cable and having to worry about non functioning USB drivers.
In closing, although I think I have provided a life saver solution for those that cannot get the USB connection to work to still be able to connect to their android device regardless of a non-working USB connection, there are cases where windows apps relying on ADB won't work even with a rooted device because these developers at program entry, STUBBORNLY just look for a USB connection instead of looking and USING A-N-Y valid and working connection as should be the case regardless if it’s thru USB or tcpip.
If any other forum member can help us figure out how to force these win apps to use ANY available valid working connection and not just a usb connection this post would then have a COMPLETE solution to this issue.
Hopefully the explained tcpip work around in this post can help those stuck with a non-working usb connection.
Cheers Ed Ray;
Click to expand...
Click to collapse
Ed,
Thanks for your response. I've been trying another approach to deal with my basic problem of being able to flash a system image (a ROM) onto the A95X MAX. It mainly involved trying to get TWRP running and get it to flash the image. That seemed to be unsurmountable. So now I'm looking into the possibility of putting the system image into a zip file with a little glue and using stock recovery to flash it from the SD card.
In the process I found instructions as to how to get ADB up & running over ethernet here:
https://stackoverflow.com/questions/2604727/how-can-i-connect-to-android-with-adb-over-tcp
Sounds like it should work, but I'm drained on this system into a zip file thing.
Cheers.