TL;DR: I am looking for some info from developers on which Xoom tablets running which tablets *fully* support Android USB Host API and whether I can reflash a EU-shipped device with the these img's.
Can a kernel be patched to fully support USB Host API?
--
I have a Motorola Xoom tablet that was originally shipped with MZ601 software (EU). I am trying to get it to work with a USB HID device. My code works well until I want to transfer data using controlTransfer - it then returns -1 as if there was no device connected (although the USB device was detected before by my code, using Host API).
I did some research and it turns out that US-shipped Xooms support Host API and that there was a guy who flashed the device to US MZ604. I did the same but the software img provided by Motorola was Android 3.0 which doesn't support Host API by default. I then tried to update this to 3.1 and 3.2 but it didn't work (tried with many copies, hazard triangle appears in the middle of installation process). Tried with rooted device.
I am now looking for any other software/ROM that proved to support USB Host API.
I would also like to know if in general Xoom tablets have hardware USB OTG support (meaning: whether flashing my device with a specific ROM should work).
Here you can find list of Android devices that was checked if they support USB Host API:
usbhost.chainfire.eu (based on USB Device Info app that lets you submit info after checking for Host API support). Most of Xoom devices are fully supporting Host API.
Thank you very much for taking on this project. Looking forward to the first release.
Sent from my Galaxy Nexus
ews said:
TL;DR: I am looking for some info from developers on which Xoom tablets running which tablets *fully* support Android USB Host API and whether I can reflash a EU-shipped device with the these img's.
Can a kernel be patched to fully support USB Host API?
--
I have a Motorola Xoom tablet that was originally shipped with MZ601 software (EU). I am trying to get it to work with a USB HID device. My code works well until I want to transfer data using controlTransfer - it then returns -1 as if there was no device connected (although the USB device was detected before by my code, using Host API).
I did some research and it turns out that US-shipped Xooms support Host API and that there was a guy who flashed the device to US MZ604. I did the same but the software img provided by Motorola was Android 3.0 which doesn't support Host API by default. I then tried to update this to 3.1 and 3.2 but it didn't work (tried with many copies, hazard triangle appears in the middle of installation process). Tried with rooted device.
I am now looking for any other software/ROM that proved to support USB Host API.
I would also like to know if in general Xoom tablets have hardware USB OTG support (meaning: whether flashing my device with a specific ROM should work).
Here you can find list of Android devices that was checked if they support USB Host API:
usbhost.chainfire.eu (based on USB Device Info app that lets you submit info after checking for Host API support). Most of Xoom devices are fully supporting Host API.
Click to expand...
Click to collapse
Look in the Development section and you should find a number of possibilities. If you look in my signature you will see the configuration that I'm running with success and I have full USB host capabilities (must use proven OTG cable, usually need a third party app like Drive Mount to successfully mount my HDD, but thumb drives mount just fine automatically on the EOS roms). Check out the long and rambling guide in my sig. as there is a bit of info on why you kept getting the error when in process of flashing recovery...
Thank you. In the meantime I've found an easy solution which works just fine. AFAIK the best choice if you want to have USB Host API support is to install the original MZ604 Android Honeycomb 3.0 software (downloaded from Motodev) and then update it to ICS. Then root the device (after applying few software updates).
Related
i want to know if there any rom supported usb host on sensation through
otg cable
i make otg cable and connected to external usb power and connect flash disk
and nothing happened
i use rcmix 7.1 gb rom
does ics rom supported usb host on senstion
ics rom should have usb host function because ics roms run on the tablet
No usb host in ics yet
The device is surely capable but we need a kernel maker to make it happens..
I hope, when source will be released, to see that feature in our phone
Hi all
Wondering if anybody else has noticed that OTG/usb host is not detecting devices in the latest CM nightly. "USB Host Diagnostics" app reports:
Android Api:
-Claims support: yes
-Classes found: yes
-Device detected: no
Rooted API:
-Claims support: N/A
Device detected: N/A
Kernel:
-Claims support: yes
-Device detected: no
Verdict:
-OS support: no
3rd party apps: no
I am currently running cm-10.1-20130713-NIGHTLY-evita.zip (kernel 3.4.10-g1cfaa2d). Do I need to install something else? I tried "USB OTG Helper" and "Stickdroid" but no joy.
I was using cm-10.1-20130304-EXPERIMENTAL-evita-M2.zip (kernel 3.0) last week and OTG was working just fine, but there were other issues that I was hoping would be fixed in the nightly. Also, i noticed that logcat does not appear to be written to at all. I installed aLogcat app and all it contains is:
---------beginning of /dev/log/main
W/InputEventReceiver(18566): Attempted to finish an input event but the input event receiver has already been disposed
I really like CyanogenMod, but am finding a number of issues with the 10.1 builds (I realise that they are unstable):
OTG not working in latest nightly
device encryption not working (apparently broken on all ROMs for now)
USB mount dialog window shows even when screen pin locked and allows full sdcard access
media player (winamp/apollo) works fine in foreground, dies within a few seconds of going background
My evita is hboot 2.14, S-Off, SuperCID, TWRP 2.3.0.0
Cheers,
Coffman
Sorry, just realised I posted this in the wrong forum. If a mod could move it to Q&A I would be most grateful.
Thanks and sorry for the slip-up.
I create bootable USB flash drives based on Fedora Linux or UEFI that have special purpose applications on them. I am able to use these flash drives on Windows 8 tablets that have the capability to select USB as the boot device. Thus allowing the tablet to be booted from this USB flash drive.
I have a Samsung Tab 3 10.1, the device model is GT-P5210 with 4.2.2 OS. My thought is I could connect the micro USB to a USB hub that has one of my bootable flash drives plugged in and boot the tablet from the flash drive.
However, I have searched the forums and wiki for posts on this or related to it but I have not see any.
Can someone point to a post that addresses this?
metaylor said:
I create bootable USB flash drives based on Fedora Linux or UEFI that have special purpose applications on them. I am able to use these flash drives on Windows 8 tablets that have the capability to select USB as the boot device. Thus allowing the tablet to be booted from this USB flash drive.
I have a Samsung Tab 3 10.1, the device model is GT-P5210 with 4.2.2 OS. My thought is I could connect the micro USB to a USB hub that has one of my bootable flash drives plugged in and boot the tablet from the flash drive.
However, I have searched the forums and wiki for posts on this or related to it but I have not see any.
Can someone point to a post that addresses this?
Click to expand...
Click to collapse
The generic boot-loader (*which resides on the chip-set) has no knowledge of USB etc, as the lk (Little Kernel) is more concerned about trapping keystrokes in order to chain-load into recovery or to boot directly into Android environment (When holding Vol+Down key in this instance) - in pseudo-code (this is from the context/aspect of lk, and also, the memory addresses pertaining to how to read the partitions are hard-coded into this lk so it will know how to process the logic!)
The lk kernel is the de-facto standard by Qualcomm for MSM chipsets (Snapdragon) and adopted by manufacturers such as Sony, Motorola, LG, Samsung and can be found in the AOSP source under bootable/bootloader.
if (Is Volume Down key pressed?) then
chain-load kernel from /recovery partition into particular address in memory and jump to it and start execution, in bringing up the recovery environment
else
chain-load kernel from /system partition into particular address in memory and jump to it and start execution in bringing up the Android environment.
end if.
As the kernel within lk is pretty limited, considering that the binary image of the kernel is burned into the chip and therefore no way of modifying it. And also should be mentioned that lk contains the fastboot protocol in preparation for flashing /boot, /recovery, /system and /data partitions. There are two sequences to boot, primary boot and secondary boot as it is:
Primary Boot -> lk (depending on outcome of logic)
Go into Secondary Boot -> /boot or /recovery
Side note: Samsung is fond of the PBL/SBL (Which is Primary Boot Loader and Secondary Boot Loader respectively) in their jargon when it comes to modding. Thing about Samsung, is that, in some handsets, PBL and SBL may be encrypted (Samsung Wave GT-S8500 is one such example, where porting Android to it was nearly impossible to do because of the DRM within the boot loaders which was a nightmare to deal with and made modding it extremely difficult, nonetheless, it is sort of working via an exploit in the FOTA code!)
This is why there are no extra facilities such as OTG functionality or anything else such as serial communications, reading from SDCard, graphics etc as it would make the lk kernel bigger than is intended. In other words, it is the smallest possible size of kernel that is designated to do just the above pseudo-code happen.
Also, another way of looking at it is this, and this is dependent on the Android version - the USB OTG functionality is fully brought up within the Android environment, i.e when the familiar home screen appears, then OTG's functionality is enabled. Unfortunately not the case when looking at it from lk's perspective.
If you're curious, here's the Qualcomm entry on the above lk which is a part of the tiny C source that has ARM assembly included and found in JellyBean's AOSP source in bootable/bootloader/legacy/usbloader/main.c
Source
Hi guys.
I have been working on a project to port NetHunter to Jiayu S3 (advanced for me , MT6752 platform) , working okay so far.
The rom contains two parts: Patched Kernel & NetHunter Files.
Kernel is modified and patched based on LoliTeam's project on Github.
mac80211 patched with script provided by Offensive-Security , HID manually patched regarding "Kernel-3.10-Nexus9.patch". Not exactly the same yet similar.
Additional Package of NetHunter is built under construction of [email protected]
Tested on
CM13 UNOFFICIAL for JIAYU S3a MT6752 (recommend)
AICP 6.0 UNOFFICIAL for JIAYU S3a MT6752
( Should work on JIAYU S3 basic too I guess. Never tried )
Progress:
OTG: Fix the 5V Power Supply for OTG so we can mount more than a USBdisk , like Mouse/Keyboard/JoyStick/WirelessAdapter , all avaliable now.
DuckHunter HID attack: working. Tho simple HID attack item didnt work , no idea why.
BadUSB MITM: RNDIS enabled. Capable to redirect the traffic of the computer you connected through your phone. (DHCPD on phone required, do it manually)
WiFi MITM: built-in wireless adapter does not support Monitor Mode so built-in Nethunter WiFi MITM does not work either. But we can do it manually , with a external USB via an OTG cable
Kali Chroot: Working
USBkeyboard(as HID device): Working
cSploit: Working
Shodan: Working
OpenVPN for Android: Working
VNC: Working
MSF: Working
RF Analyzer: Working
SDR softwares: Working
Not working:
aircrack-ng toolkit: seldom working. But can be replaced by manually command.
War Driving: not working normally , because aircrack-ng. Not planning a fix.
Router Keygen: Only support built-in adapter. Giving it up.
Problems:
Battery Power is consumed faster.
Easier to heat up.
I think they are bearable.
Installation Instructions:
To manually install , there is a long way to go.
Download ManuallyFlashImage.zip and unzip.
1. get a SP_FlashTool with a stock 5.1.1 RC5 firmware.
I have done most of the job.
Replace recovery.img with a TWRP one.
Modify scatter.txt to enlarge the partition of boot , recovery and system (I enlarged them * 2 , * 2, * 1.5)
You just need to select "download only" to "Format all and Download"
2.Get the roms ready in sdcard. I got [ cm13 , opengapps-mini , supersu , nethunter, xposed-framework ]
Vol-Up + Power
Vol-Up to select recovery and Vol-Down to confirm.
Wipe everything EXCEPT micro sdcard.
Install the roms in order.
CM13 - reboot to system - reboot to recovery - opengapps-mini - supersu - xposed - nethunter .
Screenshots (AICP)
Credits:
M.A.D.
DKingCN
LoliTeam
Offensive-Security
Download Link:
ManuallyFlashImage.zip
Keep track or commit:
@ https://github.com/offensive-security/kali-nethunter
@ https://github.com/DKingCN/nethunter-devices
@ https://github.com/DKingCN/android_kernel_jiayu_s3_h560
@ https://github.com/DKingCN/android-keyboard-gadget
i like that otg feature where you can plug in more than one. i hope that can be implemented in nougat too.
first time i hear about this nethunter, is that some kinda like linuxdeploy? where you can launch a desktop distros?
ak0ztik said:
i like that otg feature where you can plug in more than one. i hope that can be implemented in nougat too.
first time i hear about this nethunter, is that some kinda like linuxdeploy? where you can launch a desktop distros?
Click to expand...
Click to collapse
OTG might be avaliable on nougat , too.
I havent seen the source code of 7.0 kernel so I cant say for sure but most likely there should be OTG configuration.
Nethunter is a professional security package for android where you can do penetration test.
check NetHunter
Simplely it can be seen as Kali Linux on android.
And yes , local VNC server is avaiable so you can access local chroot kali desktop. Seems like gnome2.
I'm missing something
So you used kernel repo, that is a clone from mad repo, yet where's the credits?
Call me a jackass but this is the exactly reason why there's no much development on this devices.
Ever since M.A.D. released their GPL (and more non-GPL repos like device &vendor trees)
People had been using ( and good) and making kernels & semi-compiled cm builds forgetting the ones that had the heavy work on making those trees & releasing repos to the public ( that was an huge headache )...
Well done
As the project itself , looks cool
superdragonpt said:
I'm missing something
So you used kernel repo, that is a clone from mad repo, yet where's the credits?
Call me a jackass but this is the exactly reason why there's no much development on this devices.
Ever since M.A.D. released their GPL (and more non-GPL repos like device &vendor trees)
People had been using ( and good) and making kernels & semi-compiled cm builds forgetting the ones that had the heavy work on making those trees & releasing repos to the public ( that was an huge headache )...
Well done
As the project itself , looks cool
Click to expand...
Click to collapse
I forked the kernel from LoliTeam where the project can be found no link between MAD.
I am not a historian but I checked the commits and decide that MAD should be the origin of the copy of kernel so the credit is added.
Can be used kali linux from framebuffer in this project ?
(Request) help
Using magisk we can install universal full kali net hunter on miui or any other custom android rom
Which works almost perfectly
But
to do advanced stuff like wifi related stuff we need a external adapter i already has a fully supported wifi adapter
But the problem is to use a external adapter through otg we need a kernel which support wireless adapter, adapter driver built in
(Like most of the official device oneplus nexus lg samsung has "Any kernel" its a kernel available for nexus devices fully supports nethunter has wifi adapter driver built in)
Even the net hunter detects the adapter (cheked using "lsusb" command, it shows apater name chipset) but we cant do anything on off nothing because of that kernel compablity
So is there any kernel has this type of functionility available for note 5 pro whyred
If answer is no
Then im requesting Devs to make or port one
Since there is both stock and nethunter kernel source available in internet
So it will be not that difficult to port
(even previous year note 4 note 3 has a ported kernel which fully functional with net hunter)
So why not for our star
So plz its an request
A rom for net hunter will be great but
A kernel which support wireless adapter and other functionality is enough
Thanks in advance
[email protected] said:
Using magisk we can install universal full kali net hunter on miui or any other custom android rom
Which works almost perfectly
But
to do advanced stuff like wifi related stuff we need a external adapter i already has a fully supported wifi adapter
But the problem is to use a external adapter through otg we need a kernel which support wireless adapter, adapter driver built in
(Like most of the official device oneplus nexus lg samsung has "Any kernel" its a kernel available for nexus devices fully supports nethunter has wifi adapter driver built in)
Even the net hunter detects the adapter (cheked using "lsusb" command, it shows apater name chipset) but we cant do anything on off nothing because of that kernel compablity
So is there any kernel has this type of functionility available for note 5 pro whyred
If answer is no
Then im requesting Devs to make or port one
Since there is both stock and nethunter kernel source available in internet
So it will be not that difficult to port
(even previous year note 4 note 3 has a ported kernel which fully functional with net hunter)
So why not for our star
So plz its an request
A rom for net hunter will be great but
A kernel which support wireless adapter and other functionality is enough
Thanks in advance
Click to expand...
Click to collapse
Android kernel is device-specific. You cant flash one kernel to another device.
Hi,
i have a Huawei Mediapad M5 Lite (was a stock Android 8) where i installed a custom AOSP Android 10 rom from here (tried some of there):
Flashing Successfully any GSI to Mediapad M5 Lite 10 [UPDATED]
Requirements: 1. Unlocked Bootloader 2. You need ramdisk of current version. a) Install this program from this link (you need the program installed in order to download the files) https://github.com/ProfessorJTJ/HISuite-Proxy/releases/...
forum.xda-developers.com
The issue is that if i try to install this app: USB AUDIO PLAYER PRO, it seems not be not compatible with those roms. Seems that USB OTG is not working.
So i installed this app: USB OTG CHECKER, it says that USB HOST is not working.
The last rom i installed have root privileges the i created the file android.hardware.usb.host.xml in /system/etc/privilege that was missing.
But issue is not fixed. Please could you help me?
The reason i need to use USB AUDIO PLAYER PRO is the only app to have hi-res audio streaming. Can bypass Android 16 Bit 44.1 KHz limit and go up to 24 bit 192 KHz.
Thank you.
How USB / USB-OTG is implemented is hardware specific, the related drivers are NOT part of Android OS itself, they are provided by OEM.
jwoegerbauer said:
How USB / USB-OTG is implemented is hardware specific, the related drivers are NOT part of Android OS itself, they are provided by OEM.
Click to expand...
Click to collapse
so fot you the only way to have it is to restore stock rom from Huawei?
USB OTG CHECKER app you ran told you the USB-hardware build into phone doesn't support USB-OTG. So what should be the reason to re-flash phone's stock ROM?
jwoegerbauer said:
USB OTG CHECKER app you ran told you the USB-hardware build into phone doesn't support USB-OTG. So what should be the reason to re-flash phone's stock ROM?
Click to expand...
Click to collapse
Sorry but i put stock Huawei android 8 and now USB OST CHECKER app say that is compatible.
And also now i can install USB AUDIO PLAYER PRO app.