I was doing some filework on my A7+ and thought "Wouldn't it be so much better if I could just plug this damn thing directly into my computer?" So I put it in device mode, rebooted, and used a male-to-male USB cable to connect it to my PC. It didn't work, as expected, but what I did find out was the filesystem or driver system that it uses. Windows XP was trying to find drivers for a "UT-PB1" device. It couldn't, of course, so I went to the internet. I literally searched "UT PB1 USB drivers" and I got this article:
http://thetechjournal.com/electroni...raboo-ut-pb1-e-book-tablet-now-official.xhtml
(Other source: http://techcrunch.com/2011/07/22/raboo-panasonic-japan-to-launch-android-e-book-readertablet-video/ )
Look closely at the bevel, the camera and light sensor positions, and the three soft keys. (I know that the menu key is rotated 90 degrees) This weird tablet has most of the same specs as the A7+.
7-inch 1024×600 color touchscreen
Dual Core CPU (the article says that the actual chip is unknown, but I bet that it's Tegra 2)
1.3Mpix Camera
Wifi (BGN), Bluetooth
USB port (but no HDMI)
It seems that this Panasonic tablet was never released in the US. Maybe StreamTV bought a factory off of this Chinese company, and used the same basic hardware.
Just a thought. Maybe someone can do something with this, I don't know.
I ran into similar results in Win 7, however it did display a generic drive icon for the device.
I think I had USB debugging and allow mock connections on at the time for experimentation.
From what I could tell the two devices were talking to each other however I couldn't access the tablet's file system.
Do you have root setup? I do not.
---------- Post added at 12:34 AM ---------- Previous post was at 12:17 AM ----------
Here is a short output from ADB:
$ adb -d devices
List of devices attached
???????????? no permissions
adb -d bugreport
error: insufficient permissions for device
As far as I can tell from this, the hardware works....
Upon further review, I think I had the USB permissions incorrect in my: /etc/udev/rules.d/51-android.rules
But after rebuilding my desktop environment for the Nth time recently, ADB is able to poll the device.
$ adb devices
List of devices attached
037c708542c0e097 device
The "$ adb -d bugreport" also works but has far too much info to post here.
Related
Maybe I'm missing something exceedingly obvious, but what's the best/easiest way to transfer files onto the 10.1v?
I plug the USB cable into my computer, and it doesn't give me the option to mount it as a hard drive (like I could previously).
I tried the SMB module for ASTRO, but that crashes. I may look at some more SFTP/SMB apps.
What are you guys using?
I dont think it supports USB file system.
It should be MTP, media transfer protocol like in Xoom.
That is the one for Android Honeycomb.
Not sure though, but likely.
What's yous OS?
Try to get MTP driver perhaps?
Or browse to the Xoom forum.
There are a couple of Apps like Android WiFi manager that work pretty well.
However, I have been plugging the data cable into Windows 7 machines and it gets identified as USB mass storage and I've been able to transfer files without problems.
Interesting!
I'm on Ubuntu... maybe that is the issue? But that is strange, as I've never had a problem with Android phones before.
Aaaah. It looks like it is MTP -
http://forum.xda-developers.com/showthread.php?t=981774
Thanks for the heads up, I will continue down this road, and maybe the SMB route as well.
I could not get this working under 10.04.... tried for 3 hours... gave up... thought, the nag screen for 10.10 seemed a little more enticing now... so i upgraded Ubuntu...
Plugged the tab in and voila! It worked without even having to type anything else as it was already entered before when i was playing around with 10.04...
Anyway... the only thing i changed from the above link is in the udev rules, you need to put the right vendor ID in there.... Obviously this is not a Xoom... Replace their lines in the /etc/udev/rules.d/51-android.rules with the following...
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
I dont know what the code is for bootloader or anything, i just got this info from lsusb command. I only added this one line for now, as the other line is pointless unless you need to use bootloader... which im am guessing we will need soon enough
I've been reading various threads and tech posts for hours and feel like I'm going in circles and getting absolutely nowhere, so I'm really hopeful someone can help me out.
I broke the screen and digitizer on my AT&T SGH-I337 Galaxy S4 with stock Android 4.2.2 and ROM, though it is rooted. I was trying to control it via the computer with 'Ultimate Touchscreen Control for Android' or Screencast, but they require ADB which I'm pretty sure is not enabled. I did enable USB debugging before the screen broke, though I can't say with 100% certainty that I didn't later disable it, so I'm not entirely sure what the status of that is. I've been reading about sideloading a kernel with ADB enabled through recovery, or using CWM with Odin to enable it, but I have been absolutely unable to figure out how to do it with a broken screen. It doesn't help that it's been 3.5 years since I really messed with stuff like CWM and custom ROMs, and I've never used Odin, and my knowledge on this stuff is not great. Any help would be greatly appreciated.
I think you're pretty much sol. You say you're on 4.2.2, do you know what bootloader you're on. Mdb, mdl or mf3. If you're on mf3 you won't be able to flash a kennel. Do you have a custom recovery, and if so, which one?
When booted into recovery and adb installed on your pc in a Windows command window type
adb devices
If you're devices serial number shows up you have adb debugging enabled. If it just shows waiting for device, you don't.
Your best bet is to get the screen/digitizer replaced.
Sent from my Nexus 5 using XDA Free mobile app
Not sure what bootloader, but I got the device only a month or two after the S4 came out and immediately rooted it with Motochopper and it hasn't had any updates since, so it has to be an earlier one, probably the first.
After several attempts, 'adb devices' gave me:
"List of devices attached
da916528 unauthorized"
The first several times it would just say "List of devices attached" with nothing following.
'adb shell' resulted in "error: device unauthorized. Please check the confirmation dialog on your device."
Shortly after it does list the phone, the phone shows up in Windows, so I'm thinking it's not going into recovery. My timing must be off because I can't see the screen to know when to release the buttons.
vertigo_2_20 said:
Not sure what bootloader, but I got the device only a month or two after the S4 came out and immediately rooted it with Motochopper and it hasn't had any updates since, so it has to be an earlier one, probably the first.
After several attempts, 'adb devices' gave me:
"List of devices attached
da916528 unauthorized"
The first several times it would just say "List of devices attached" with nothing following.
'adb shell' resulted in "error: device unauthorized. Please check the confirmation dialog on your device."
Shortly after it does list the phone, the phone shows up in Windows, so I'm thinking it's not going into recovery. My timing must be off because I can't see the screen to know when to release the buttons.
Click to expand...
Click to collapse
You're close but unfortunately no cigar. You have usb debugging enabled but it's waiting for you to authorize the device by clicking accept on the touch screen. Which you obviously can't do. If you used motochopper you are on mdb or mdl bootloader which means you could flash a kernel but you'd have to do it in a custom recovery and use the touch screen. I don't have an i337 so I'm not going to be much more help. Sorry.
Sent from my Nexus 9 using XDA Free mobile app
Kinda figured it was something like that. Thanks anyways, at least I know exactly where I stand now. I'm going to try using an MHL and OTG adapter to see if I can click it that way. In the meantime, hopefully somebody with the same phone as me will come along and be able to provide further guidance.
So I was finally able to gain remote access with some crazy wiring and a lot of patience. I'm putting this here so others in my situation might have an easier time at doing it.
First I installed TeamViewer QuickSupport (TVQS) via the Play Store online, then connected a PS/2 mouse to the phone through a OTC cable and a USB to PS/2 adapter (only USB mouse I have is wireless, but good to know you can use such an adapter for this). I blindly swiped the screen to unlock the phone, then connected it to my TV with an MHL adapter and the 5 to 11 pin Samsung-specific adapter. I long-pressed the menu button to activate voice search and said "launch TeamViewer QuickSupport," then when the app opened it showed me the ID to connect to the phone which I entered into my desktop TeamViewer application. I then had to switch back to the mouse to do some more blind clicking to authorize the connection, then again to authorize the remote control, which took several frustrating minutes of switching back and forth between the mouse and the TV. One mistake I made was not installing the remote addon at first, so after I first authorized the connection, I didn't have that option, so I had to install it again through the Play Store online then close and relaunch TeamViewer on the phone and reauthorize the connection before I could start a remote session. Once I was FINALLY in I had full control and was able to get the Ultimate Touchscreen (UTCA) program authorized (which in retrospect would have required the same thing only it would have been significantly easier, since I would have only had to do one blind click) and Mobizen (which I'm currently using to control it as it's the best and fastest of the three, and oddly it's faster through the web interface than the desktop program).
In the end, what would have made this significantly easier (in fact, very easy), would have been to use a combination OTG/MHL adapter that would allow using the mouse and TV at the same time, or possibly a micro-USB OTG Y-cable so I could plug one connector into the phone and one into a power supply, then plugged the MHL Samsung adapter into that so it could get power that way, allowing me to plug the mouse in to it instead of a USB cable for power. Not sure if that would actually work, but it seems like it would. Hopefully somebody finds this info helpful. From now on, I'll be installing and authorizing TVQS, Mobizen, and UTCA on my phones when I get them.
I have the same problem. I cannot access ADB in anyway, even in in Clockworkmod recovery. USB Debugging is off. I am on the original firmware that came with the device, (Pre Knox) and the device is rooted.
My lock screen is just the simple lock, with no password required, but I have an app installed that switches the USB mode to Mass Storage for the external SD only so I cannot see internal storage.
MHL does work, but the touchscreen is not working, so all I can see is the lock screen.
When in recovery, ADB Devices shows the device as unauthorized. If i go to option # 3, (which apparently is Factory Reset) the status changes to "Sideload." But I still cannot do anything.
If no one has any suggestions. I think i'm going to have to purchase one of the Samsung Smart Docks.
I can't post links or pictures until I get 10 posts, but this works;
goo.gl/PR7TCK
Other than getting the dock, the only other way to do it that I know of is how I described above, switching back and forth between video and mouse, which sucks because you're flying blind. It requires a lot of patience.
I managed to get into developer mode on my new NGP, there's no more "build number" as I've seen in several blog posts with the latest update you click on the Nook icon on the About page it takes you to Developer mode. I've been able to install a few apps, but here's what I'd like to do.
I'd like to plug in a USB keyboard and use it to SSH into another machine through my WiFi hotspot to do some HTML/JS/CSS text editing while I'm outdoors (at the pool, the park, etc) as my other laptops/tablets aren't visible at all outdoors with glare. This would be a nice portable solution if I could get it to work, even editing locally on the device through some editor and sending via SFTP would be just fine.
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
JohnnyFriendly said:
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
Click to expand...
Click to collapse
As a workaround I put a VNC client on it so I can access my other devices and do the typing from there, that way I can use my RPI3 as the system with a keyboard on battery power and do some Python (Django)/NodeJS/ReactJS from the NGP using it as a monitor outdoors, but if I issue the following commands via adb to rotate into landscape mode I lose input on the NGP and have to reboot:
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1
Any ideas?
I believe I looked at this once.
At least one of the problems is that the ID pin on the micro USB connector is not connected through to the processor.
B&N has never shown any interest in putting Bluetooth in a Nook.
We'll have to see if the latest "Nook Glowlight 3" will have either OTG or BT.
Hi guys,
might be someone can share good knowledge and experience for my very specific issue...
I'm a big fan of Fire HD tablets, currently we do have 4 of 'em in house, one HD 10 and three HD 8 (2016 & 2018). Three tables successfully rooted, debloatwared, tweaked and 100% allset for my family (and my) needs. But one of the Fire HD 8 has a trouble. This is a tablet of my 4 yo little princess; people with kids already know how small kids usually unplug USB connector - I don't need to explain So, the USB connector become unusable and non-working right before root for Fire HD 8 was achieved (or I found this hack on xda ), doesn't really matter. But I don't like to waste good and sophisticated items, even they costs me just a $40-50 - I'm not greedy but respect human mind and technology heights. So, I asked my friend, very experienced electronics engineer, to fix the tablet (already bought a new USB connector for HD8 on eBay). My friend fixed the tablet (it's not an easy: you need a good soldering station, zoom and experience - assembly is too small). but... He is an Apple guy; he fixed USB power but forgot to check (and solder) data connection He did this work for me for free, and I can't ask him again to redo the work.
So, this tablet has a perfect power but no USB data connection (i.e. it's invisible for desktop adb). My question is: is it possible to root Fire HD 8 without USB cable? Technically (as far as I understand), I should find a way to set "execute" attribute to mtk-su program. I googled a lot, and it looks impossible but... Might be, someone knows "the hack"? Theoretically, if desktop adb can set this attribute, why some android app can not do the same?
Please, if you don't know and don't have enough experience, do not reply - I know how to use google, search at xda-dev & stack overflow.
P.S. To prevents this "USB issue" in the future, I've bought that stuff on aliexpress. It's not an advertising and I'm not related to the seller (there are bunch of similar items on ali!). But this magnetic cable is must have feature for any micro-USB device, and my children simple loves these cables and connectors (it's also funny)!
You can obtain a root shell using mtk-su with a terminal emulator e.g. Terminal Emulator or Termux. Instructions are here. If it is a 6th or 7th gen. you can then install SuperSU: see here. If it is an 8th gen. the method is here.
---------- Post added at 01:06 PM ---------- Previous post was at 12:53 PM ----------
To add, if it is an 8th gen. unit the data connection is needed to install the bootrom exploit and unlock the bootloader, so it won't work.
There is a root method for Fire OS6 that was developed for the Fire 7, 9th gen. before the bootloader unlock was available: see here. This will most likely work on the Fire HD8, 8th gen. too and does not require ADB.
Thanks for good tip! But I have an issue with Termux: 64-bit mtk-su can't execute 'cause of error "CANNOT LINK EXECUTABLE DEPENDENCIES: "libz.so" is 32-bit instead of 64-bit. 32-bit mtk-su is running fine and telling me what I'm root, but ./mtk-su -c mount -o remount -rw /system didn't remount, actually, Fire HD8 /system to read/write mode. It looks like 32-bit mtk-su made me root... just for Termux (or I don't know).
I haven't tried "Terminal Emulator" 'cause I don't know where to copy "rooting" files (mtk-su and the rest).
UPDATE: Tried with "Terminal Emulator" (copied files to internal storage to /data/data/<emu_package_name>) and everything works like a charm! Installed "WiFi ADB" from store, and I'm allset
I made the mistake of buying this tablet, so -thanks- Walmart for the unexpected, unwelcome headaches.
I got it for reading ebooks, because of the slightly larger screen compared to my phone. I saw it was limited when I got it home and turned it on, but I was still able to install a couple of book-reader apps so I thought it would be OK for my purposes. But when I plug it into my Windows 11 laptop with the USB cable the tablet doesn't show up on the computer. I have books on the laptop to transfer over.
Is there any way I can force the USB to be a data transfer connection instead of only a battery charger? There is no "use USB for" option when it's plugged in, like there is on my phone. Is there maybe a third party app I could install that will enable this -usually- normal function? Thanks, any advice and help is appreciated!
Hi @Lookstwice
Enable MTP:
Settings > Connected devices > USB > File transfer
Enable ADB:
Settings > About Tablet > Build number (7 x tap)
Settings > System > Advanced > USB debugging
Some people like Calibre on their desktop for organizing books. I believe that understands MTP.
Me, I use my adbsync.exe (in my sig) to synchronize directories. It uses ADB (duh).
Also check out this thread on the 8" which has some info that may be applicable:
https://forum.xda-developers.com/t/new-generation-3-onn-tablets-are-now-available.4464147/
Hello Renate and thanks for the advice!
I did find the developer mode and turned on USB debugging. Also, I selected File Transfer under Default USB Configuration.
Under Settings > Connected devices there is no USB on my tablet, only +Pair New Device and Connection preferences, Bluetooth.
The tablet still doesn't show up at all, when I connect via USB to my laptop.
Is there anything else I should try? Under System > Developer options maybe? How about OEM Unlocking? Disable adb authorization timeout? Thanks!
Are you sure that you have a data cable? Cheesy ones only supply power.
If you're connected to Windows enabling/disabling USB debugging should make it "bong".
To check out if I am using an inferior cable, I switched to my cellphone cable. It works fine on my cell, but no luck with this tablet. I know it makes no sense!
Thanks for your help anyway. I'm open to any ideas.
Lookstwice said:
I'm open to any ideas.
Click to expand...
Click to collapse
Sorry, I missed your response.
These devices come up in the MTK preloader whenever they reboot.
You don't actually need to load a loader or do anything.
Connect the USB. I presume you're using Windows? Does it "bong"?
Use the regular Android reboot option on the power menu.
Does it do a bunch of bong-ing and Windows flashes popups complaining about devices?
You may have a hardware problem and you need to return the device.
Wow, Renate, you've got some serious skills. Pretty impressive to turn such a low-end device into a custom machine...
I'm having trouble pulling the boot.img from this device... If anyone was willing to share the stock boot.img for the 100071481 that would be SUPER appreciated...
otherwise I'm just going to keep trying to get this MTK client thing to work although nothing seems to get the device to be visible...
Joined the forum to post this message though I hope to contribute in the future! Thanks!
@oneiromon Yes, try the (Python) MTK client
I've had problems getting that to run under Windows. I finally used a Raspberry Pi with Linux.
I was working on writing a native Windows MTK client but I haven't got that working yet.
After successfully writing a native Windows EDL (Qualcomm) client it was a bit disheartening to dive into the MediaTek gobble-dee-gook.
FWIW: I've not had luck with fastboot boot whatever.img
It works fine with fastboot flash boot whatever.img, then fastboot reset
@Renate - THANKS! for all your help with this onn tablet . Sorry I've not been keeping current on responses. I use the tablet to read books on while getting medical treatments and I was able to upload the files to my Google drive and then download to the tablet.
I'm on a Windows 11 laptop and it doesn't "bong" when I attach the tablet. I'll try the reboot option and let y'all know .
@oneiromon - I totally agree with this statement: "Wow, Renate, you've got some serious skills."
@Lookstwice I haven't got up to Windows 11, so maybe it's hiding some stuff from you.
It could also be that the 7" has some differences to the 8"
The USB/VID of my 8" is 0e8d/201c (MediaTek)
Try using UsbView.exe
See if anything appears/disappears as you plug in. For sanity, check against a known working device.
Oh, and if you're thinking reading, you really ought to consider Eink devices.
Yeah, a lot of them are annoying and underpowered, but see if you like the concept first.
I like the Onyx Poke3, but buttons/no buttons is contentious and personal.
I use no buttons but a tiny Bluetooth clicker. I love it!