After installing UrukDroid, how can I access/call USB Serial to use it to communicate to an Arduino? (I haven't installed it yet, but was wondering about the possibilities after I did.)
Also, since the tablet has some usb host support, shouldn't the code for it be somewhere in the system? I could probably access that, but it would require root, leaving me back with UrukDroid anyway...
I'm used to playing around on my phone (Droid X2) and if I do anything wrong on there, I know that I can simply SBF. Is there something similar with the Archos101?
Device Info:
Archos 101 IT
2.4.82 firmware
A101IT-V6 board
Thank you for your help.
Related
First, let me say that I've searched and searched and looked for all the info I can find about people having similar problems. I've yet to find anything that works for me, and I'm at my wit's end on this...
A few days ago I tried [unsuccessfully] to update CWM on a GTab. I can't get into recovery at all now (it just hangs), but this problem predates that.
The problem I have is that I cannot get any PC to recognize the GTab - in any mode - and I've tried 4 computers with various operating systems. I've tried Fedora, Ubuntu, Windows XP and Windows 7 and none of them will see the GTab at all. They won't see it with debugging on, with it off, in APX mode or anything.
I have gone through half a dozen cables and tried every USB port I've got. It just simply will not recognize the tablet in any way.
I'm toying with the possibility that the port might be damaged, but I can't think of a good reason why that would be the case. The tablet has been well taken care of, and all the other ports work just fine (audio, USB storage, SD).
So, has anybody else run into this issue and found a fix for it?
N0ctrnl said:
I'm toying with the possibility that the port might be damaged, but I can't think of a good reason why that would be the case. The tablet has been well taken care of, and all the other ports work just fine (audio, USB storage, SD).
So, has anybody else run into this issue and found a fix for it?
Click to expand...
Click to collapse
Read: Only ClockWork recovery on boot
Check dmesg to see if tablet is detected: A self inflicted wound
Also: [Q] (really) bricked g-tab.
If you can't boot the tablet at all--into either ROM or recovery--, then there's nothing you can do if your USB isn't working. If you can boot into one of them, then there's hope.
I managed to get CWM installed (was my bad on trying to flash the wrong one to upgrade it anyway). It's always booted just fine into the ROM, and everything works but the USB connection to PC.
I am actually a Linux admin by trade, so I kept an eye on all pertinent system logs and outputs when I tried it on the Linux box. No dice.
N0ctrnl said:
I am actually a Linux admin by trade, so I kept an eye on all pertinent system logs and outputs when I tried it on the Linux box. No dice.
Click to expand...
Click to collapse
Well, you have to be careful about these things. APX mode, for instance, only "connects" to the host PC once, so if you unplug and replug hoping to see USB device recognition messages from the Linux kernel, then you will be disappointed.
What about on the gTablet? Does the kernel print anything pertinent when the cable is connected to the host PC (enable USB debugging first)? Are there any other error messages or diagnostics?
That's the troubling part. I'm finding absolutely nothing. Nothing at all to indicate there's any kind of issue. My guess at this point is that the USB port must be physically broken. I can't see any other way to make sense of it.
Here's one final suggestion: Open the gtab up and disconnect the battery. Wait 1 minute then reconnect the cable.
See if it helps. (It's for people who can't even boot the tablet into APX mode, but, try it before concluding that it is a HW problem).
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
flumpster said:
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
Click to expand...
Click to collapse
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
ichihaifu said:
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
Click to expand...
Click to collapse
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
flumpster said:
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
Click to expand...
Click to collapse
Hmm, alright. Just because I havent really roughed up the cable at all and everything worked fine until the said date.
But for now theres no way to try another cable, I'l look for new one next week.
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
I gained root on 4.1.x via twrp and supersu, just after unlocking it. I am not shure if reinstalling 4.1.was really useful...but I did.
Hi all,
I am a noob and a have a question: I try to install to Pi****u to a small TV Box with rk3188 chip.
I fiddled around with different stuff, nothing worked so far. But I broke one thing: it is not recognized any longer on the USB. Instead of 0x2207, 0x310b it now announces as 0x2207, 0x0010. Does somebody know how I can correct this. I'm not sure but it seems that this also happened after I rooted the device.
Any hints?
Jan
Hi,
Are there any guides for how to dump/backup/image the NAND/eMMC of a brand new, never-been-booted-up Android device? I want to create an image file of the entire/complete NAND before powering on a new phone for the first time.
Maybe that would be achieved by connecting the phone to a PC via USB and using SoC vendor-specific software to dump the NAND. I have done that on an Archos GamePad before. The GamePad has a RockChip RK3066 SoC, and (from memory, it was a while ago) I used rkflashtool to do that.
I read some guides for MTK-based phones, but they require doing stuff after the phone has booted up, for example enabling USB debugging. Is there any way to determine the NAND size and read it without having to do that? Maybe connecting a brand-new phone over USB I could enable some kind of factory-use mode?
And are there any guides for doing that for Qualcomm-based devices (Snapdragon 410)?
Hi there. I’m still kinda new as this is the second post I’ve ever made. Last one was many years ago.
As the title states, I’m trying to root my Android tv box. It’s a MyGica ATV 1900 Pro with AMlogic S905 chipset running Android 5.1.1. So I’ve tried the obvious routes. From Framaroot to Towelroot to Kingoroot to Baidu Root to One Click Root and everything in between. Whether it be the APKs or PC alternatives. I found one that looked promising but it was for a different device that required the running of a .bat file from my laptop while connected to the box via Ethernet cable. I know I know, useless attempt as it was not made for my device but I was desperate. So that didn’t work obviously. I have also tried connecting the box to my laptop using a male to male usb cable but they don’t see each other. Maybe the cable is old or maybe the box was just never meant to be connected to a pc that way. Who knows
The MyGica support site says they have an Android 7 beta update with superuser support but most comments on that thread have people crying from having their boxes bricked and I don’t want to risk it. I’ve had varying levels of success with rooting my previous devices in the past(each device needing a different app etc) but I’ve always succeeded in the end. But this box has me utterly stumped. I do not know what other options I have.
Any advice is welcome and thanks in advance
P.S The reason I want to root has to do with the fact that my box has lost its WiFi ability it seems. WiFi won’t turn on. So was wanting to delete the wpa suplicant files to see if that resolved the matter but can’t get in system folder without root