[FAQ] Asus T100: Installing custom OS (android/ubuntu/*nix/Windows 7/Windows 8 x64)

[FAQ] Asus T100: Installing custom OS (android/ubuntu/*nix/Windows 7/Windows 8 x64) - Windows 8 Development and Hacking

[4 April 2014]I haven't had time to play with my device or update fully the info in this post
Jhong2 has an updated post on how to get ubuntu working on the Asus T100
http://forum.xda-developers.com/showpost.php?p=51291244&postcount=181
http://www.jfwhome.com/2014/03/07/perfect-ubuntu-or-other-linux-on-the-asus-transformer-book-t100/
(do search for the specific topic headers to jump to them)
Post 1: Global Info
UEFI:
Bootloader auto-detection path:
Secure Boot
Partition Table for Live USB sticks:
How to boot from USB stick
Info for various operating systems:
Hardware info:/cpu/cpuinfo:
Post 2: <backup/ archived infomation>
Post 3: Files
grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32
---------------------------------------------------------------------------------------
Global information
for BIOS 214 (2013.09.25), version loaded on retail T100 units
UEFI:
Bootloader auto-detection path:
(bootloader is only 32-bit compatible)
/efi/BOOT/bootia32.efi
WILL NOT pick up the x64 location /efi/BOOT/bootx64.efi
Secure Boot
You should disable Secure Boot in UEFI/Setup-Utility-Menu-> Security tab-> Secure Boot Menu -> Disable
Partition Table for Live USB sticks:
GPT or MBR works
Use Rufus (works for Windows/Unix ISOs) or Windows 7 USB Download Tool (works for Windows 7 / Windows 8)
How to boot from USB stick
NOTE:
If you don't see the USB drive on the boot list or the UEFI/Setup-utility, this means you have a badly prepped USB live drive, or the boot-list/UEFI/Setup-utility was loaded before the USB drive was read.
If you are on the boot list, boot into UEFI/Setup-utility. Then, go to the last tab, save changes and restart while holding F2 (to force the next reboot to go back into UEFI/Setup-utility). If you still don't see the USB drive after doing this multiple times, then you have a badly prepped USB drive.
I find using Rufus (GPT for UEFI + FAT + 64 kb+ bootable disk using ISO Image) to consistently get a working bootable USB drive
Option 1a) Boot to UEFI USB drive from Windows (works only if your USB is correctly prepped)
Boot into Windows
Swipe from right, click on settings.
Click on Power. Press and hold the shift key, and then click on Restart
A Blue menu should show up. Click on Use a device->click on the device name (might not show up if USB isn't prepped properly)
Device should reboot into the USB
Option 1b) Boot to UEFI/Setup-Utility-menu from Windows (easiest, and almost no way to screw it up)
Boot into Windows
Swipe from right, click on settings.
Click on Power. Press and hold the shift key, and then click on Restart
A Blue menu should show up. Click on Troubleshoot-> Advanced Options-> UEFI Firmware Settings
Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive
NOTE:
For options 2a and 2b, if you see the ASUS logo and circle loading icon, you either:
Pressed button (ESCAPE/F2) too late. Solution: Reboot and try again
Have Fast startup enabled, and did the steps with the device in shutdown mode. Windows will cache the kernel/other stuff, and you might not be able to get to UEFI. Solution: Reboot from Windows and try again(reboot does not trigger caching). Or disable Fast Startup
Option 2a) Boot to UEFI/Setup-Utility-menu
Inside Windows, restart system. Press and hold the F2 key
You should get into the Aptio Setup Utility screen
Inside UEFI/Setup-Utility-menu, go to the last tab, and select the USB Drive
Option 2b) Boot Menu
Inside Windows, restart system. When screen goes blank, press and hold the ESCAPE key (if you press it too early, Windows might interpret you as cancelling the restart process)
You should get a list of bootable devices
If you see the ASUS logo, you've pressed the ESCAPE key too late. Restart and retry
Info for various operating systems:
You should backup the recovery partition to a separate USB key. Alternatively, you can do it with this ASUS utility Backtracker that HatesForums pointed me to
Windows:
Windows 8.1
x86: (Status: Works but missing drivers)
Used Windows 7 USB Download Tool or Rufus to create bootable USB. Using en_windows_8_1_x86_dvd_2707392 from MSDN (x86 8.1 Regular & Pro ISO), able to install W8.1 x86 and boot to it (missing a few drivers, eg touch screen doesn't work, no sound). Windows is automatically activated without need for key. First boot had 25.7GB free out of 33.6GB.
x64: (Status: Not yet working)
Used Windows 7 USB Download Tool or Rufus to create bootable USB. ISO does not contain bootia32.efi. Copied that file from the x86 ISO to USB, able to boot, but the installer complains that the processor isn't 64-bit compatible
Windows 7
x86: (Status: unknown)
ISO does not contain efi
x64: (Status: unknown
ISO only contains x64 efi
Unix:
Ubuntu:
You need an EFI-compatible distro. For ubuntu, x64 EFI is enabled since 12.04-2. However, we'll need to include x86 EFI because our bootloader only reads x86 EFIs
13.04 x64 desktop- (Status: boots to GUI using fbdev)
Used Rufus(GPT for UEFI + FAT + 64 kb+ raring x64 as bootable disk using ISO Image) to create bootable USB. Copied over the bootia32 to /efi/boot/
there is a bug in VESA where it queries for a BIOS-only command and crashes. Forcing xserver to use fbdev fixes this problem
13.10 x64 desktop- (Status: boots to GUI using fbdev
Same problems as 13.04 x64 plus one addition efifb problem
see post for more details - touchscreen works, but no wifi
Android:
android-ia - (Status: No x86 UEFI bootloader)
Generic UEFI Installer android-4.2.2_r1-ia3 does not come with x86 UEFI bootloader. it does not use grub, so can't just use ubuntu's x86 grub2 efi. Need to compile it from source
android-x86 - (Status: Bootable but slow)
Uses grub, can piggy-back on the ubuntu x64 13.10 bootia.efi grub. Some workarounds needed, see this post
external/efitools/Android.mk
# TODO: support ia32 prebuilt
ifeq ($(TARGET_KERNEL_ARCH),x86_64)
arch_name := x86_64
Click to expand...
Click to collapse
/cpu/cpuinfo:
taken from a x64 13.04 live USB
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 55
model name : Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz
stepping : 3
microcode : 0x312
cpu MHz : 1333.387
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms
bogomips : 2666.77
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
Hardware info:
The microUSB slot is USB-HOST-capable (i.e. with a USB OTG cable or Y cable, you can connect a USB flash drive to the microUSB slot
Amazon.de and Asus.de posted a T100 version with 500GB drive on the keyboard base. No pictures yet
Internal eMMC, 108MB/s 44MB/s read/write on sequential. CrystalDiskMark here
External microSD(HC/XC) reader is NOT UHS-1 compatible. Someone over at liliputing comments posted his atto benchmark
64GB Samsung microSDXC card came in the mail today, I did some ATTO disk tests using the T100's built-in microSD reader and a USB 3.0 reader from Transcend.
Unfortunately, it looks like the built-in reader is connected via USB 2.0. It maxed out at 23.8 MB/s read and 17.2 MB/s write, while the USB 3.0 reader maxed out at 71.3 MB/s read and 21.3 MB/s write. The card is rated at 70 MB/s read and 20 MB/s write.

<backup/ archived infomation>

Files:
grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32
LINK | MIRROR | Instructions on compiling from source

<reserved 3>

paperWastage said:
ISO does not contain bootia32.efi. Copied that file from the x86 ISO, able to boot, but the installer complains that the processor isn't 64-bit compatible
Android:
Click to expand...
Click to collapse
odd: http://ark.intel.com/products/76759/
shouldnt be erroring about 64 bit, unless the 8.1 installer is checking the CPU ID, isn't recognising it (no idea why) and then presuming a lack of 64 bit support.

SixSixSevenSeven said:
odd: http://ark.intel.com/products/76759/
shouldnt be erroring about 64 bit, unless the 8.1 installer is checking the CPU ID, isn't recognising it (no idea why) and then presuming a lack of 64 bit support.
Click to expand...
Click to collapse
Perhaps the 32bit bootloader sends that the device is only booting in 32bit.
Seeing that I can boot to Ubuntu x64, the chip should be 64bit like how the Intel ark site says. I'll check the cpuinfo in Ubuntu to see what extensions it supports
Will also try to download WinPE and get the efi bootloader from there instead. Windows 7 x64 has efi x64 bootloader, but x86 doesn't have any efi bootloader

Compiling grub2-efi-ia32 (x86)
NOTE:
The instructions below are for raring 12.04.
The same instructions should work for other versions/sources/distros of grub2 as well.
The resulting binary should work with any *nix distros that use grub2
The resulting bootia32.efi should be placed on your USB drive at /EFI/BOOT/bootia32.efi
The grub-mkimage instruction basically packages the grub-efi AND the *.mod you specified into that bootia32.efi. You may need to tweak the list of *.mod that you include. You don't need to copy the *.mod onto the USB drive
-p /boot/grub tells grub-efi to look for the grub.cfg at /boot/grub/grub.conf (location that ubuntu uses). Other distros may use a different location.
Either recompile grub2-efi-ia32 with the right "-p" flag
Or copy your distro's grub.conf to /boot/grub/grub.cfg
Download grub2 sources for raring
https://launchpad.net/ubuntu/+source/grub2/2.00-13ubuntu3
apt-get install gcc bison flex
./configure --with-platform=efi --target=i386
make
#make GRUB EFI binary and mods
cd grub-core
../grub-mkimage -d . -o bootia32.efi -O i386-efi -p /boot/grub ntfs hfs appleldr boot cat efi_gop efi_uga elf fat hfsplus iso9660 linux keylayouts memdisk minicmd part_apple ext2 extcmd xfs xnu part_bsd part_gpt search search_fs_file chain btrfs loadbios loadenv lvm minix minix2 reiserfs memrw mmap msdospart scsi loopback
cp bootia32.efi to <USB DRIVE>/EFI/BOOT/
# might be missing some modules... but if i tried to compile all *.mod, I get an invalid stack frame during grub boot
Click to expand...
Click to collapse
Files:
grub2 2.00-13ubuntu3 (13.04 raring sources) compiled for grub-efi-ia32 (x86) - bootia32
LINK | MIRROR | Instructions on compiling from source

tried using that bootia32.efi to load Ubuntu 13.10 x64 ... (13.10 & 13.04 seem to use the same grub2-2.00 sources)
the grub menu shows up, but after selecting "Try Ubuntu", it flashes, menu continues showing up, nothing happens
then my Windows 8.1 OS got corrupted or something.... either boots to Windows message "Windows unable to start up properly", or it boots to login screen, then the screen goes haywire and popup boxes saying "illegal exception" or something
going to reinstall W8.1 x86 cleanly from a MSDN ISO/USB flash drive
got the logs from the semi-successful 13.04 x64 boot... will look through them and post them soon

ubuntu x64 13.04, debuging x-server issues
[ 36.591] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 36.597] (II) Module fbdev: vendor="X.Org Foundation"
[ 36.597] compiled for 1.12.99.902, module version = 0.4.3
[ 36.597] Module class: X.Org Video Driver
[ 36.597] ABI class: X.Org Video Driver, version 13.0
[ 36.597] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
Haswell Server (GT2+), Haswell SDV Desktop (GT1),
Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
Haswell ULT Server (GT1), Haswell ULT Server (GT2),
Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
ValleyView PO board
...
[ 36.762] (II) VESA(0): initializing int10
[ 36.763] (EE) VESA(0): V_BIOS address 0x0 out of rangefrom
http://www.redhat.com/archives/rhl-devel-list/2009-December/msg00372.html
looks like 13.04 is able to recognize and load the necessary drivers, but crashes because our UEFI-only computer doesn't have a BIOS portion... or maybe 13.04 is using older stuff
EDIT: or does that error even matter? trying to force x to configure itself
EDIT2: it matters because VESA is configured to be the default/fallback driver. With the V_BIOS issue, it won't work. Tried to force it to use fbdev driver, but no luck (it loads, but nothing shows up)

I deleted the vesa_drv.so from /usr/lib/xorg/modules/drivers/ , forced it to start using fbdev... works, very slowly of course
will try the intel driver later
(it's definitely the vesa BIOS bug that's stopping it from working on 13.04... will debug 13.10 later)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

<instructions below should be complete
got ubuntu 13.10 to boot to command prompt (with bootia32.efi and grub.cfg fixes below)
Rufus (GPT for UEFI + FAT + 64 kb+ 13.10 desktop x64 as bootable disk using ISO Image)
Note:
Good behavior:
After you select "Try Ubuntu" in grub, screen goes to blank, (?might appear as well) usb light disappears... wait < 30s, the screen should then show the logs and then cmd line)Bad Behavior:
After you select "Try Ubuntu" in grub, screen goes to blank, then the grub menu reappears (but nothing happens when you press arrow keys). (?might appear as well) usb light stays lighted. if you wait >5 minutes, nothing happens. just force reboot machine (hold power button), and reboot into windows, then UEFI and try again
/boot/grub/grub.cfg - replace with the text below
Code:
if loadfont /boot/grub/font.pf2 ; then
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
menuentry "Try Ubuntu without installing" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper text noacpi nomodeset --
initrd /casper/initrd.lz
}
menuentry "Install Ubuntu" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --
initrd /casper/initrd.lz
}
menuentry "OEM install (for manufacturers)" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true --
initrd /casper/initrd.lz
}
menuentry "Check disc for defects" {
set gfxpayload=keep
linux /casper/vmlinuz.efi boot=casper integrity-check quiet splash --
initrd /casper/initrd.lz
}
(changes in grub is to disable efifb which causes screen flickering/corruption - video=vesa: off doesn't work, probably because vesa IS the fallback driver)
then boot. After you get to command line, remove the vesa_drv.so module from /usr/lib/xorg/modules/drivers/, type startx
touchscreen works on x64 13.10. still haven't had time to make x86 ISO work with bootia32.efi GRUB

For Android-x86 without EFI support, I wonder if this method courtesy of Tyler Swindell on Youtube would work. This is what he used to get Android-x86 booting on the Surface.
Alright guys, this is the Surface Pro running Android-x86. It was something we all saw coming. Past 2
nights, I have been trying hard to get Android-x86 to run on my Surface Pro since I saw how amazing it
ran on my desktop PC. If it would just boot, I could see just how great Android is on the Surface Pro. So
I got it to boot, and it was just as great as I expected it to be.
So why didn't it boot? I had Secure Boot off. Ubuntu boots, Windows 7 boots. Well what do all these
operating systems have in common? Their installers all include both BIOS and EFI boot loaders. What is
interesting about the Surface Pro is the UEFI chip was designed without legacy BIOS support. There is
no way to boot a BIOS-based boot loader.
I thought about it and how Ubuntu boots. I checked the files and I saw a EFI-based Grub boot loader.
All I had to do was drop in Android's files into an Android directory and add the boot entries. This
worked and Android booted thanks to the EFI-based Grub boot loader.
Everything works except no connectivity, no Wi-Fi or Bluetooth. Also the buttons could have better
functions such as the Windows button or the power button which just brings up a power menu. Overall
it's a great start, it's booting, and the drivers are there for mostly everything. It's fantastic.
This tutorial can be drastically simplified and improved. Keep in mind it was just to get it to work.
1. Download Android-x86 ISO and Ubuntu 12.10 x64 ISO.
2. Format a USB flash drive.
3. Using LiLil USB Creator, copy Ubuntu ISO to flash drive.
4. Create Android directory in flash drive. Extract Android ISO, copy initrd.img, kernel, ramdisk.img,
system.sfs to the Android directory.
5. Modify boot/grub/grub.cfg to add these entries:
submenu "Android" {
menuentry "Android" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=android_x86 quiet video=1920x1080
dpi=145 i915downclock=1 i915.powersave=1 usbcore.autosuspend=2 SRC=/android/
initrd /android/initrd.img
}
menuentry "Android text output" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=android_x86 video=1920x1080 dpi=145
i915downclock=1 i915.powersave=1 usbcore.autosuspend=2 SRC=/android/
initrd /android/initrd.img
}
menuentry "Android debug mode" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=android_x86 video=1920x1080 dpi=145
i915downclock=1 i915.powersave=1 usbcore.autosuspend=2 SRC=/android/ DEBUG=1
initrd /android/initrd.img
}
}
6. Turn off Secure Boot and boot Android. Enjoy.
Click to expand...
Click to collapse
Sent from my DROID BIONIC using Tapatalk

spunker88 said:
For Android-x86 without EFI support, I wonder if this method courtesy of Tyler Swindell on Youtube would work. This is what he used to get Android-x86 booting on the Surface.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
that might work, forcing android-x86 to boot via grub.. thanks
been using android-ia, which doesn't use grub... uses another efitool, need to play with both android-x86 and android-ia later tonight

paperWastage said:
that might work, forcing android-x86 to boot via grub.. thanks
been using android-ia, which doesn't use grub... uses another efitool, need to play with both android-x86 and android-ia later tonight
Click to expand...
Click to collapse
Picking up on our conversation from SlickDeals.. I actually ended up buying one of these things and I was able to get an external hard drive recognized just by plugged into my usb OTG cable -- in windows. I even tried a USB mouse which worked perfectly.

Deltido said:
Picking up on our conversation from SlickDeals.. I actually ended up buying one of these things and I was able to get an external hard drive recognized just by plugged into my usb OTG cable -- in windows. I even tried a USB mouse which worked perfectly.
Click to expand...
Click to collapse
yeah, my usb otg cable works now in windows (detects flash drive). no idea why it didn;t work before (maybe I unpluged it too early while it was detecting/installing the usb driver?)

got android to boot up, but uglily
need 2 flash drives, and a USB-OTG cable(to be able to connect using the microUSB port)... a USB-hub should work too
(basically, you're piggying back off the ubuntu grub2 bootloader, to load the android kernel and other stuff)
used my (existing & currently working) ubuntu 13.10 x64 bootable USB (made via Rufus, GPT partition with bootia32.efi fix)
copied the contents of android-x86-4.3-20130725.iso into the USB:/android/
modified contents of grub.cfg as per the post by spunker88 with some changes to the resolution
second flash drive had dd if=android-x86-4.3-20130725.iso of=/dev/sdb1
without this second flash drive, the android boot sequence stops at "Detecting Android-x86" and "VFS: could not find a valid V7 on sda1". probably something to do with android/kernel not liking the first drive having FAT instead of ext2/3/4
grub.cfg - add to the end, and select this during grub
Code:
submenu "Android" {
menuentry "Android" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=x86 video=1366x768 DEBUG=1 SRC=/android/
initrd /android/initrd.img
}
}
boot into USB, then grub, then select android.
android crashes to command line. forcing it to start (type exit twice), leads to the default android start screen, and eventually this
it is SUPER LAGGY. not usable

paperWastage said:
got android to boot up, but uglily
need 2 flash drives, and a USB-OTG cable(to be able to connect using the microUSB port)... a USB-hub should work too
(basically, you're piggying back off the ubuntu grub2 bootloader, to load the android kernel and other stuff)
used my (existing & currently working) ubuntu 13.10 x64 bootable USB (made via Rufus, GPT partition with bootia32.efi fix)
copied the contents of android-x86-4.3-20130725.iso into the USB:/android/
modified contents of grub.cfg as per the post by spunker88 with some changes to the resolution
second flash drive had dd if=android-x86-4.3-20130725.iso of=/dev/sdb1
without this second flash drive, the android boot sequence stops at "Detecting Android-x86" and "VFS: could not find a valid V7 on sda1". probably something to do with android/kernel not liking the first drive having FAT instead of ext2/3/4
grub.cfg - add to the end, and select this during grub
Code:
submenu "Android" {
menuentry "Android" --class android --class linux --class os {
linux /android/kernel root=/dev/ram0 androidboot.hardware=x86 video=1366x768 DEBUG=1 SRC=/android/
initrd /android/initrd.img
}
}
boot into USB, then grub, then select android.
android crashes to command line. forcing it to start (type exit twice), leads to the default android start screen, and eventually this
it is SUPER LAGGY. not usable
Click to expand...
Click to collapse
Progress!!
Although its unusable, it's nice to see android on this device. So what do you think needs to be done to get android usable on this?

costcutter said:
Progress!!
Although its unusable, it's nice to see android on this device. So what do you think needs to be done to get android usable on this?
Click to expand...
Click to collapse
for both ubuntu/android, first steps (since it's booting) is to get the graphics driver working. right now, ubuntu is using fbdev and android is (i think) using efifb... both are running at 800x600 and laggy....
either I fix the VESA bug, or find the correct intel driver for the new Bay Trail IGP and use it
then, install ubuntu/android properly on the device, and then debug the rest (instead of through a live USB where changes would not persist from every reboot)

I'm trying with Fedora 20 alpha, but not much luck so far.
Got the grub2-efi to work with your tutorial (and some digging), but once I start installing Fedora, it seems to freeze.
Gonna try ubuntu over the weekend.

probably the vesa bug as well (if you are trying to install via gui)
attempting to fully install ubuntu on system and boot from it.... the bootia32.efi / bootx64.efi / grubx64.efi is making a mess here...
managed to get Windows Bootloader AND ubuntu grub listed as boot options... grub has problems though, dumps me into grub shell
EDIT: Think it;s easiest for me to try installing EFI Shell, and tinker from there
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Efi-shell
EDIT2: For Windows 8 64-bit, the error is "This 64-bit application couldn't load because your PC doesn't have a 64-bit processor"
Looks like we need to enable Virtualization in the UEFI/BIOS... but there isn't such an option (the cpu Z3740 does support VT-x)

Related

OSLoader failed

Hi All,
I am using the OsLoader-1.5.6 to backup my original ROM of my PDA (Medion MD 40600) that runs WM2003.
The error message is:
Contents of virtual address and physical address don't match. ?x80000000] =0xA0000000 ?x48000000] =0xE3A000D3
After that:
An error occured while saving 0x00400000 bytes of flash at address 0x00000000 to file flash_00000000.bin.
Do you wish to continue?
It saves the first 4MB with no contents, then later continues with the 2nd chunk and this is 4MB also 3rd etc. So, only the 1st chunk of 4MB is a mismatch in addressing.
What can I do ?
Is it related to the CID unlock? Shall I use the program "lokiwiz" to unlock it ?
Pls help me. Thanks !
Best Regards,
Jocafi

My PDA uses the Intel PXA255 chip with 32Mb size. I am trying to repair the device.
I am using a Jtag Cable with H-JTAG and it recognizes the device as :
PXA25X
0x69264013
I know that the Chip MD3831 from M-Systems is also inside of it.
I used openwince Jtag 0.5.1 under Kubuntu and the output using the JTag connected to the parallel port (LPT1) was:
Code:
JTAG Tools 0.5.1
Copyright (C) 2002, 2003 ETC s.r.o.
JTAG Tools is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
There is absolutely no warranty for JTAG Tools.
Warning: JTAG Tools may damage your hardware! Type "quit" to exit!
Type "help" for help.
jtag> cable parallel port at 0x378 TRITON
Initializing Ka-Ro TRITON Starterkit II (PXA255/250) JTAG Cable on parallel port at 0x378
jtag> detect
IR length: 5
Chain length: 1
Device Id: 01101001001001100100000000010011
Manufacturer: Intel
Part: PXA250
Stepping: PXA255A0
Filename: /usr/share/jtag/intel/pxa250/pxa250c0
jtag> print
No. Manufacturer Part Stepping Instruction Register
---------------------------------------------------------------------------------------------
0 Intel PXA250 PXA255A0 BYPASS BR
Active bus:
*0: Intel PXA2x0 compatible bus driver via BSR (JTAG part No. 0)
start: 0x00000000, length: 0x04000000, data width: 32 bit, (Static Chip Select 0)
start: 0x48000000, length: 0x04000000, data width: 32 bit, (Memory Mapped registers (Memory Ctl))
jtag> detectflash
buswidth: 32
CFI query: 00000154, 98
CFI query: 000002a8, 98
CFI query: 00000550, 98
err: -4
jedec_detect: mid d3, did e3a0
Flash not found!

PPC 200 or MIO 339
hello
did u resolve problem?
same to me .erased boot and jtag not recognize flash.
inside is same MD3831-D32 flash
Dark

into the trash
I threw everything into the trash !
No way to repair the device. Sorry!

[ICS][DEV] Tegra Hardware and Feature Implementation [UPDATE 3/22]


I wanted to start a fresh thread to focus purely on Tegra hardware possibilities and how we implement the use of hardware into ICS. I have moved some resources from other threads here as well to consolidate this development concept.
THIS THREAD IS STRICTLY FOCUSED ON ADVANCING THE DEVELOPMENT OF THE KERNEL, BINARIES, FRAMEWORK, ETC. BEFORE POSTING HERE, ASK YOURSELF THIS... "HOW DOES MY POST ATTEMPT TO FORWARD DEVELOPMENT AS THE THREAD TITLE DESCRIBES?" IF YOU CAN'T CLEARLY ANSWER THAT, THEN PLEASE DO NOT POST HERE. THIS THREAD IS MEANT TO BE TECHNICAL IN NATURE. THIS THREAD IS NOT A Q&A THREAD. PLEASE RESPECT THE GUIDELINES SET FORTH. THANK YOU.That being said, let's take a look at some tools to get us started. Development Overlay
Bash 4.1 system shell
Nano and vim text editors
-- Init.d scripts --
Dropbear setup script and service initialization
Modprobe modules on boot
pittpatt symlinker for more system storage
BT5 support scripts
-- extra binaries --
7z, file, inadyn, irssi, iwmulticall ( i'll up a kernel with wireless extentions soon, even though wext is depricated ), scp, tcpdump, unrar, zipalign script
Revision 4 -- combined overlay with latest module pack for simplification. Tiamat Xoom 3.0.9 kernel updated 3/22. -- Moved modules and some bins to /data/local then symlink to system. This leaves tons of system storage. -- Of course, all needed monitor mode, injection patches for Backtrack. TDR's adhoc kernel patch in the event I actually come up with a solution -- included WifiDirectDemo.apk so we can get some WifiDirect dev going on. On your EOS build, enable advanced wifi direct settings in development settings.
DOWNLOAD DEVELOPMENT OVERLAY REVISION 4Facial Recognition Binary Symlinker
Facial recognition binaries consume about 25 MB of system storage. Even though system storage is not relevant for day to day use, it becomes a concern when doing things like adding theming or extra kernel modules where more system storage is required. This tool moves the "pittpatt" facial recognition binaries from /system/vendor/pittpatt to /data/pittpatt and creates a shortcut ( in Linux we say "symlink" ) to them. This frees an additional 25 MB of system storage. DOWNLOAD FACIAL RECOGNITION BINARY SYMLINKERDrivers Galore!ALL SORTS OF GOOD STUFF
This build is built from the Tiamat 3.0.9 base. But this build includes an insane amount of driver modules to support a variety of hardware. There are several groups of modules for different hardware, primarily using a USB Host cable as the interface. Some groups include USB Wireless Dongles, USB Ethernet Dongles, 3G and 4G GSM and CDMA/LTE Dongles, serial port modules, networking modules such as rndis_host to support tethering from a phone to the xoom, and other miscelaneous hardware.USB Wireless Dongles
All USB Wireless dongles that depend on the mac80211 wireless subsystem are monitor mode capable. Perfect for pentesting, security analysis, or going to Federal Prison for hacking your neighbors WiFi.
Linux Wireless Catalog Of Supported USB Wireless Dongles
at76c50x_usb 30409 0 - Live 0xbf085000
rtl8192cu 84308 0 - Live 0xbf397000
rtlwifi 58705 1 rtl8192cu, Live 0xbf380000
rtl8192c_common 49260 1 rtl8192cu, Live 0xbf34e000
rtl8187 48197 0 - Live 0xbf33b000
eeprom_93cx6 1127 1 rtl8187, Live 0xbf0df000
rt73usb 21310 0 - Live 0xbf325000
rt2800usb 9831 0 - Live 0xbf31b000
rt2800lib 36395 1 rt2800usb, Live 0xbf30b000
rt2500usb 16115 0 - Live 0xbf301000
rt2x00usb 7451 3 rt73usb,rt2800usb,rt2500usb, Live 0xbf2f9000
rt2x00lib 29250 5 rt73usb,rt2800usb,rt2800lib,rt2500usb,rt2x00usb, Live 0xbf2e8000
rndis_wlan 23105 0 - Live 0xbf2d1000
zd1211rw 47819 0 - Live 0xbf462000
zd1201 17003 0 - Live 0xbf457000
mac80211 201396 8 zd1211rw,rtl8192cu,rtlwifi,rtl8187,rt2800lib,rt2x00usb,rt2x00lib,at76c50x_usb, Live 0xbf040000
( Included but likely not used )
lib80211_crypt_wep 2538 0 - Live 0xbf240000
lib80211_crypt_tkip 7837 0 - Live 0xbf239000
lib80211_crypt_ccmp 4635 0 - Live 0xbf232000
michael_mic 1756 0 - Live 0xbf262000
hostap 96172 0 - Live 0xbf1b7000
lib80211 3564 4 lib80211_crypt_wep,lib80211_crypt_tkip,lib80211_crypt_ccmp,hostap, Live 0xbf1b0000USB Serial Drivers
USB Serial Drivers to interface with all sorts of devices.
pl2303 10705 0 - Live 0xbf2b4000
ftdi_sio 28048 0 - Live 0xbf0e5000
cypress_m8 14665 0 - Live 0xbf0ae000
ipw 3034 0 - Live 0xbf20d000
iuu_phoenix 14989 0 - Live 0xbf213000
mos7840 27187 0 - Live 0xbf272000
mos7720 15798 0 - Live 0xbf268000
spcp8x5 5050 0 - Live 0xbf3f7000
sierra 8457 0 - Live 0xbf3c8000
ti_usb_3410_5052 19435 0 - Live 0xbf404000
option 13380 0 - Live 0xbf29b000
USB Ethernet Drivers
These drivers support a large array of dongles
dm9601 5696 0 - Live 0xbf0b8000
cx82310_eth 2901 0 - Live 0xbf0a8000
rndis_host 5213 1 rndis_wlan, Live 0xbf2ca000
kaweth 9695 0 - Live 0xbf223000
pegasus 17228 0 - Live 0xbf2a8000
rtl8150 8803 0 - Live 0xbf332000
smsc95xx 11437 0 - Live 0xbf3e2000
smsc75xx 13416 0 - Live 0xbf3d8000
net1080 3055 0 - Live 0xbf27f000
plusb 926 0 - Live 0xbf2bd000
mcs7830 5117 0 - Live 0xbf25b000
zaurus 2190 0 - Live 0xbf451000
hso 28083 0 - Live 0xbf1d9000
int51x1 2491 0 - Live 0xbf1f2000
ipheth 5297 0 - Live 0xbf1fe000
sierra_net 6399 0 - Live 0xbf3d1000
lg_vl600 2763 0 - Live 0xbf22c000USB Mobile Data Drivers
USB Wireless WAN is a generic driver that supports an array of congles
usb_wwan 8789 1 option, Live 0xbf292000USB Multimedia
These drivers support a wide array of USB webcams, digital video capture, and drivers for userspace controls. As of now, we have no implementation of these drivers, and will be one heck of a science project to make work.
dvb_core 80709 0 - Live 0xbf0c0000
uvcvideo 58311 0 - Live 0xbf423000
gspca_zc3xx 36191 0 - Live 0xbf178000
gspca_spca561 7905 0 - Live 0xbf170000
gspca_spca508 6464 0 - Live 0xbf169000
gspca_spca506 7602 0 - Live 0xbf162000
gspca_spca505 4139 0 - Live 0xbf15b000
gspca_spca501 13107 0 - Live 0xbf152000
gspca_spca500 9825 0 - Live 0xbf14a000
gspca_spca1528 5914 0 - Live 0xbf143000
gspca_sn9c20x 23657 0 - Live 0xbf137000
gspca_ov534_9 8884 0 - Live 0xbf12f000
gspca_ov534 9395 0 - Live 0xbf127000
gspca_ov519 33377 0 - Live 0xbf118000
gspca_main 22079 12 gspca_zc3xx,gspca_spca561,gspca_spca508,gspca_spca506,gspca_spca505,gspca_spca501,gspca_spca500,gspca_spca1528,gspca_sn9c20x,gspca_ov534_9,gspca_ov534,gspca_ov519, Live 0xbf10c000Joystick and Game Controllers
zhenhua 1620 0 - Live 0xbf477000
warrior 2039 0 - Live 0xbf43a000
twidjoy 1984 0 - Live 0xbf41d000
trancevibrator 1498 0 - Live 0xbf417000
tmdc 4237 0 - Live 0xbf410000
stinger 1672 0 - Live 0xbf3fe000
spaceorb 2528 0 - Live 0xbf3f1000
spaceball 2876 0 - Live 0xbf3eb000
sidewinder 9351 0 - Live 0xbf3c0000
serport 2389 0 - Live 0xbf3ba000
magellan 1872 0 - Live 0xbf255000
joydump 2090 0 - Live 0xbf21d000
interact 3125 0 - Live 0xbf1f8000
iforce 14117 0 - Live 0xbf1e8000
guillemot 3040 0 - Live 0xbf188000
grip_mp 5403 0 - Live 0xbf105000
grip 4589 0 - Live 0xbf0fe000
gf2k 4210 0 - Live 0xbf0f7000
cobra 3192 0 - Live 0xbf09c000
analog 7464 0 - Live 0xbf024000
adi 6890 0 - Live 0xbf016000
a3d 4374 0 - Live 0xbf00f000
serio 9848 8 zhenhua,warrior,twidjoy,stinger,spaceorb,spaceball,serport,magellan, Live 0xbf24c000
gameport 6942 12 tmdc,sidewinder,joydump,interact,guillemot,grip_mp,grip,gf2k,cobra,analog,adi,a3d, Live 0xbf007000IPSec VPN
Credit to saturn_de from the TFP board for the idea
xfrm_user 19993 0 - Live 0xbf446000
xfrm4_mode_tunnel 1462 0 - Live 0xbf440000
ipip 7627 0 - Live 0xbf205000
ah4 4354 0 - Live 0xbf01d000Miscalaneous
scsi_wait_scan makes sure all system buses are online before proceding with boot. ppp_synctty is a network driver needed from Cisco VPN and other uses.
scsi_wait_scan 482 0 - Live 0xbf2d1000
ppp_synctty 5417 0 - Live 0xbf1e0000

Module ManagementLet's talk about what modules are.
Simply put, a kernel is a big blob of drivers in a single image. Modules are those same drivers but compiled to be "built out" of the primary zImage. There are a few reasons why modules are useful. Most devices have very limited boot partition. That means that the kernel, which is inside the boot image, must be limited in size as well. So when you need extra drivers, modules do the trick. Also, modules allow you to control what drivers are installed at what time. For example, if you want to run a USB Wireless Dongle, you may wish to remove the Android Wifi driver ( bcmdhd.ko ) so that Android Wireless services are disabled. Using modules, in conjunction with a USB Host Cable, and a Motorola Xoom ( running Eos preferable ;D ), we now have an extraordinarily powerful mobile device.How do I know what modules I need? There's too many!
That all depends on the piece of hardware you want to use or some feature you wish to utilize. You need to know what "chipset" your hardware has. I will begin cataloging what modules work with different hardware. IT IS HIGHLY ADVISED THAT YOU ONLY LOAD THE MODULE STACKS YOU NEED! IT IS LIKELY YOU DON'T HAVE ENOUGH ROOM ON THE SYSTEM PARTITION TO LOAD ALL THESE! Later, I'll work out a scheme to efficiently load modules from the Data partition.
Module Stacks
Often, the driver you wish to use is dependent on other modules. So how do you know what modules you need to complete your driver stack? When the kernel is compiled, the Makefile determines what other modules you need based on the drivers you have selected. Let's look at an example using the USB Wireless Dongle group.
Code:
adb shell
lsmod
rndis_wlan 23105 0 - Live 0xbf1ee000
zd1211rw 47819 0 - Live 0xbf33b000
zd1201 17003 0 - Live 0xbf330000
zaurus 2190 0 - Live 0xbf32a000
rtl8192cu 84308 0 - Live 0xbf2b4000
rtlwifi 58705 1 rtl8192cu, Live 0xbf29d000
rtl8192c_common 49260 1 rtl8192cu, Live 0xbf26b000
rtl8187 48197 0 - Live 0xbf258000
eeprom_93cx6 1127 1 rtl8187, Live 0xbf0af000
rtl8150 8803 0 - Live 0xbf24f000
rt2800usb 9831 0 - Live 0xbf238000
rt2800lib 36395 1 rt2800usb, Live 0xbf228000
rt2500usb 16115 0 - Live 0xbf21e000
rt2x00usb 7451 3 rt73usb,rt2800usb,rt2500usb, Live 0xbf216000
rt2x00lib 29250 5 rt73usb,rt2800usb,rt2800lib,rt2500usb,rt2x00usb, Live 0xbf205000
mac80211 201396 8 zd1211rw,rtl8192cu,rtlwifi,rtl8187,rt2800lib,rt2x00usb,rt2x00lib,at76c50x_usb, Live 0xbf00f000
You can use the shell command "lsmod" to display all loaded module stacks.
The bottom row is the full USB Wireless Stack, all modules dependent on the mac80211 wireless subsystem. I'll use the driver rtl8192cu as an example in the following dependency stack.
Code:
rtl8192cu ----> rtlwifi ----> mac80211 ----> ( inside kernel ) cfg80211
|
|
|
|----> rtl8192c_common
So, in this case, you will need your driver, rtl8192cu, along with rtl8192c_common, rtlwifi and mac80211. Remember, only load the modules you need.
How To Install Modules
The easiest way to install modules is to uses an init.d script so the modules load on boot. Such a script is included in the Development Overlay in the tools section in the first post. It looks like this
Code:
#!/system/bin/sh
#
# Load any extra modules
MODPATH=/system/lib/modules/
for i in `ls $MODPATH`
do
modprobe `basename $i .ko` >/dev/null 2>&1
done
exit 0
Or you can load them manually one by one thru a shell. I'll use rtl8187 as an example.
Code:
cd /system/lib/modules
modprobe rtl8187
"modprobe" is the command that loads modules. Modprobe is the prefered method over "insmod" as modprobe will load the driver and automatically load any dependencies the driver has.

Scripts, Tips, Tricks, How-ToHow to preview a USB Webcam
1. Install the Development Overlay Revision 2
2. Install Tiamat 3.0.5 Kernel Module Pack Revision 4. For starters, load the entire USB Multimedia stack until you figure out specifically which driver you need for your webcam.
3. Install SimpleWebCam.apk DOWNLOAD HERE.
NOTE: All credit for SimpleWebCam.apk goes to neuralassembly and his source code can be found HERE.
And credit to xda user Dilligaf_ for the email pointing me to these resources.
4. Attach your webcam to your USB Host cable then insert host cable into your xoom.
5. Launch SimpleWebCam and you should see your webcam stream on the screen.
NOTE: At this time, we can only preview. So no still shots or video recording as of yet. This is mostly proof-of-concept but that's what this threads about

I read the other day about a Kernel that allows to adjust the colors on the display. Any word on that one?

Wow. We waiting for this. Hope something cool come to our xoom

Outstanding...
This kind of effort brings real value to the Xoom. Thanks for all the hard work you do as the activity in this forum brought me to the Xoom, despite of Motorola's poor market performance.
I haven't seen another tablet that has dual band wifi, have you?

Module Request: USB ETHERNET QF9700 : idVendor=0fe6, idProduct=9700
I hope it is appropriate to post this here. I'm seeking a module for the above usb eth adapter. I've seen it referenced in other threads as qf9700. I believe it is a very common (cheap) adapter; I did try and get a more "supported" dm9601 but couldn't find one anywhere (not helped by suppliers reluctance to specify chipset).
dmesg:
Code:
[ 130.277339] usb 2-1: USB disconnect, device number 2
[ 130.560150] usb 2-1: new full speed USB device number 3 using tegra-ehci
[ 130.989906] usb 2-1: New USB device found, idVendor=0fe6, idProduct=9700
[ 130.990408] usb 2-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 130.990674] usb 2-1: Product: USB 2.0 10/100M Ethernet Adaptor
# uname -r
# 2.6.39.4-Tiamat-g1360200
I have little/no experience in linux kernel/module compilation and it would also be handy to get some pointers to learning materials (I'm not being lazy but; I'm 45, have a fulltime job in IT services and wouldn't have time to learn Android/Linux from the ground up. The ability to understand/write/adapt modules would, however, be a useful skill to have)
I'm attaching the supplied "Android" drivers which I'm not even sure are correct. They may be of some use to someone.
Many thanks in advance

3g usb key
First of all, thanks for the great work done on EOS and modules.
I'm really happy to have my USB Ethernet working great
Now I'm trying to make my USB 3g donggle working.
I've loaded the USB_wwan and option module without any problem (my USB key is a k3760) but now I'm a bit lost to where I can configure my connexion (apn pin code ..)
Can you please help me?
Thanks a lot
Note: I'm on EOS nightly build 75
On the rev4 the USB_wwan module is missing !

usb audio
Another question
Is there a way to have USB speaker working? I have a Logitech USB one. When plugged, here's the dmesg result :
<6>[ 625.589256] usb 2-1: New USB device found, idVendor=046d, idProduct=0a10
<6>[ 625.589552] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 625.590037] usb 2-1: Product: Logitech Speaker
<6>[ 625.590294] usb 2-1: Manufacturer: Logitech
<6>[ 625.701138] input: Logitech Logitech Speaker as /devices/platform/tegra-ehci.0/usb2/2-1/2-1:1.2/input/input8
<6>[ 625.702528] using input dev Logitech Logitech Speaker for key reset
<6>[ 625.703102] keychord: using input dev Logitech Logitech Speaker for fevent
<6>[ 625.703860] generic-usb 0003:046D:0A10.0001: input,hidraw0: USB HID v1.00 Device [ Logitech Logitech Speaker] on usb-tegra-ehci.0-1/input2
Just the volume buttons on the speakers are working but audio is only on the Xoom.
Thanks a lot

Thank you bigrushdog for such a hard work.
My question is can I install 'DEVELOPMENT OVERLAY REVISION 2' and 'DEVELOPMENT OVERLAY REVISION 2' by clockworkmod recovery? and if so how can I make the module work.. Sorry I am kinda confused
------
Somehow I flashed both by CWM recovery, and yes my system partition used space has been increased by 16 mb (i.e, I install your goodies in system partition successfully as I think ) but I sense nothing has changed; I have the same logitech USB headphone as thdj has, but as same only recognizes the volume up and down button that was recognized by the system initially even before flashing...
Any help???

I just installed the Rev 4 Kernel mod pack because I saw the IPSEC VPN addition. My only question is how to access it as I seem to still have the same choices and none of them come with the Group Name option enabled.
I am sure it is something silly I am over looking....

Help Please
Let me start off by saying, thank you so much for your hard work and interest in our technology needs/wants! Now...please guide me- the Multimedia, and joystick goodies are in which DL Pack? Development Overlay -Revision2 is designed for video only? I tried to make sense of it all but got caught up in it's glory! Just now coming down from my KERNEL HIGH and things are foggy.

IS there any hope to allow the Xoom to mount to a Windows PC as a logical drive, or is MTP the only way to go?

Hy bigrushdog,
...in the changelog from today i see a update to kernel 3.06 and the implement of usb ethernet. So i do not need your package anymore?
Craxx
Send from my MZ601 eos ICS with Tapatalk

some threads should be a sticky, this is one of them.
thanks

There seems to be a problem with the Tiamat 3.0.5 Kernel Driver Module Pack rev 4. (or maybe rev 2 too)
The zip has a lot of modules, but when installed only a few get installed?
ex. usb_wwan.ko, option.ko etc. are missing.
EDIT:
Now i installed the Module pack rev 2. on a fresh 78 wingray nightly. Installed gapps, and development overlay rev2. And it has only the first 31 modules from the zip installed(sorted alphabetically).
On the 2nd flash all missing modules got installed. (there were warrnings/errors when flashing the zip the 1st time AFAIK).
I'm also missing the chat or chat-ril binary for the pppd.
Would also suggest adding usb_modeswitch to the dev. overlay.

zerox981 said:
There seems to be a problem with the Tiamat 3.0.5 Kernel Driver Module Pack rev 4. (or maybe rev 2 too)
The zip has a lot of modules, but when installed only a few get installed?
ex. usb_wwan.ko, option.ko etc. are missing.
EDIT:
Now i installed the Module pack rev 2. on a fresh 78 wingray nightly. Installed gapps, and development overlay rev2. And it has only the first 31 modules from the zip installed(sorted alphabetically).
On the 2nd flash all missing modules got installed. (there were warrnings/errors when flashing the zip the 1st time AFAIK).
I'm also missing the chat or chat-ril binary for the pppd.
Would also suggest adding usb_modeswitch to the dev. overlay.
Click to expand...
Click to collapse
I had the same issues, 2 flashes for everything to get in place, but no errors when flashing.

Guys I think I'm making a rookie mistake. When I try to modprobe I get an error chdir /lib/modules no such file or directory. I can insmod a module just fine.
I'm also not seeing all the modules. What is the recommended flash order?

The overlay contains the pittpatt symlinker that makes 25mb free space. Since its an init.d script, you have to flash overlay then reboot. Then go back to recovery and flash the modules. However, nobody on Earth needs all the modules so you should hand pick only the stacks you need anyway.

I also have some issues with modprobe. I can not add or remove modules. The message I am getting is always
Code:
modprobe: chdir(2.6.39.4-Tiamat-g2523b85-dirty): No such file or directory.
Although the startup script that loads modules seems to work, because all the modules are loaded (checked it with lsusb).
But insmod seems to work ...
EDIT
Any chance of adding usbserial.ko?

[TOOL] rkDumper (utility for backup firmware of RockChip's devices)

rkDumper
Utility for backup firmware of RockChip's devices
Version 1.1.1.0 Windows
1. Makes dump of NAND by partitions according "parameter" information (RKFW/RKAF formats)
2. Creates config.cfg for RKAndroidTool (1.xx, 2.xx)
Notes:
1. All drivers must be installed
2. Administrator rights are required
Known bugs:
-
Old versions:
View attachment rkDumper_091.zip
View attachment rkDumper_092.zip
View attachment rkDumper_093.zip (604)
View attachment rkDumper_094.zip (1810)
View attachment rkDumper_095.zip (226)
View attachment rkDumper_100.zip (1480)
View attachment rkDumper_101.zip (716)
View attachment rkDumper_102.zip (4400)
View attachment rkDumper_103.zip (792)
View attachment rkDumper_104.zip (2630)
View attachment rkDumper_105.zip (3812)
View attachment rkDumper_106.zip (8948)
View attachment rkDumper_107.zip (426)
View attachment rkDumper_108.zip
View attachment rkDumper_1.1.0.0.zip

Tested on:
WinXP (32), WinVista (32), Win7 (32/64), Win10 (64)
0bb4:2910 MSC device (USB debug off)
0bb4:0c02 MSC device (USB debug on)
2207:0000 MSC device (USB debug off)
2207:0010 MSC device (USB debug on)
2207:350A RK3566 x88 Pro
2207:330D RK3308/RK3326/RK3388/PX30 Evoo EV-A-81-8-1
2207:330C RK3399/PX6 CSA96
2207:330A RK3368/PX5 Artway X6/HCT MTCD (Car head unit) SOM
2207:320C RK3318/RK3328/PX4 A5X Plus mini
2207:320B RK3229 MXQ 4K
2207:320A RK3288 Jesurun T034
2207:310D RK3126 Proscan PLT9650G
2207:310C RK3128 CS918-rk3128
2207:310B RK3188/PX3 PIPO Max M9 Pro
2207:301A RK3036 Wecast E8
2207:300B RK3168 Starmobile Engage7+
2207:300A RK3066/PX2 UG802
2207:292C RK3026/RK3028 ONYX BOOX C67SML COLUMBUS/?
2207:292A RK2928 Lexibook Tablet Master 2
2207:290A RK2906 TeXeT TB-138
2207:281A RK2818 ChinaLeap M3
If you have another Rockchip SoC send me result of "rkDumper scan" and name of device. I'II send you personal version for test

rkDumper
Utility for backup firmware of RockChip's devices
New version (0.92 Windows) ready
! pre-Release #2;
~ "4GB" bug fixed;
+ support of "USB debug on" mode added;
+ support of RK3026 added;
+ support of RK2906 added;
+ support of VID=0bb4 (HTC? Rockchip devices) added.

Hello,
I have run your utility, but the file sizes of the output differ compared to when I use rktool 2.1 (with finless instructions).
Here's the scan..
Code:
C:\temp\1>rkDumper.exe scan
rkDumper (version 0.92)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices emumerating --
Devices table (found 8 USB devices):
1 Device #0: USB Root Hub
2 Device #1: USB Root Hub
3 Device #2: USB Root Hub
4 Device #3: USB Root Hub
4.1 Device #4: BT-253
VID = 0x0b05, PID = 0xb700
5 Device #5: USB Root Hub
5.2 Device #6: USB Composite Device
VID = 0x2207, PID = 0x0010
Disk #1
5.8 Device #7: USB Composite Device
VID = 0x04f2, PID = 0xb071
==========================[ STOP ]==========================
Thank you.

nevoz said:
I have run your utility, but the file sizes of the output differ compared to when I use rktool 2.1 (with finless instructions).
Click to expand...
Click to collapse
Some types of files have own length in header. This information used for cutting (real size, not whole partition)

here's is mine.
C:\RKDumper>rkdumper scan
rkDumper (version 0.92)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices emumerating --
Devices table (found 7 USB devices):
1 Device #0: USB Root Hub
1.1 Device #1: USB Hub
VID = 0x8087, PID = 0x0024
1.1.1 Device #2: XBOX 360 Controller For Windows
VID = 0x045e, PID = 0x028e
1.1.2 Device #3: Rockusb Device
VID = 0x2207, PID = 0x300b
1.1.4 Device #4: USB Composite Device
VID = 0x09da, PID = 0x90a0
2 Device #5: USB Root Hub
2.1 Device #6: USB Hub
VID = 0x8087, PID = 0x0024
==========================[ STOP ]==========================

wertzPH said:
here's is mine
Click to expand...
Click to collapse
Please tell me the name of the device and the name of SoC

RedScorpioXDA said:
Please tell me the name of the device and the name of SoC
Click to expand...
Click to collapse
thanks for the reply
Starmobile Engage7+, its advertised as RK3066 based on cpu-z, but the loader is rk3168.

wertzPH said:
Starmobile Engage7+, its advertised as RK3066 based on cpu-z, but the loader is rk3168.
Click to expand...
Click to collapse
You can find link to personal version in "Private Messages". I'll wait your report

rkDumper
Utility for backup firmware of RockChip's devices
New version (0.93 Windows) ready
! pre-Release #3;
+ support of RK3168 added;
+ administrator's rights checking added.

rkDumper (version 0.93)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices enumerating --
Devices table (found 10 USB devices):
1 Device #0: USB Root Hub
1.1 Device #1: USB Composite Device
VID = 0x045e, PID = 0x00db
1.2 Device #2: USB Input Device
VID = 0x046d, PID = 0xc05a
2 Device #3: USB Root Hub
3 Device #4: USB Root Hub
3.5 Device #5: Rockusb Device
VID = 0x2207, PID = 0x292c
4 Device #6: USB Root Hub
5 Device #7: USB Root Hub
6 Device #8: USB Root Hub
7 Device #9: USB Root Hub
==========================[ STOP ]==========================
this is mine, and when I try to do "dump" I get:
rkDumper (version 0.93)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
--- Firmware dumping ---
The utility requires administrator rights
==========================[ STOP ]==========================
I am an administrator, and the device is a RK3026
also, is there a way to dump the loader of these tablets?
Thanks

niabi said:
I am an administrator, and the device is a RK3026
Click to expand...
Click to collapse
Do you run tool as administrator (Ctrl+Shift+Enter on cmd string)? Try to use /admin key
niabi said:
also, is there a way to dump the loader of these tablets?
Click to expand...
Click to collapse
No. But sometime you can found loader in backup.img partition (use imgRePackerRK)

Kudos to RedScorpio!
Great work RedScorpio!
It never hasn't be that easy to create a dump for rockchip devices!
But I still see some room for improvements and also have some questions:
Can I create a full dump of a device including the user partition? I appreciate to create full dumps - so I can play with my devicesm flash different firmwares and finally I'm able to restore everything to the former state - in case it's not possible to create a full dump at the moment it would be great if you could add it!
Another great addition would be if you could simplify the installation of the drivers in windows 8.1 - please take a look at this post: http://forum.xda-developers.com/showpost.php?p=55529498&postcount=56
Basically Microsoft decided to change the behaviour of the usb stack in windows 8.1 and so it's not possible to install the rockchip driver that easily - you need to figure out 3 details of your device and create an exception-rule in the windows registry so your device is handled as it has been with the previous usb stack.
To create this registry key you'll need VID, PID and REV from the usb device - maybe you can display REV also in your output of 'scan' ? (windows device manager don't even display those details...)
Finally it would be great if you could create this registry key automatically (or with another command) in case you notice that the os is windows 8.1 and the device isn't recognized properly - in my case I'll get the following output when I connect my rockchip device without the registry entry:
C:\Users\roland\Desktop\Rockchip Tools\rkDumper_093>rkDumper.exe scan
rkDumper (version 0.93)
Utility for Rockchip's firmware backup
(c) RedScorpio, Moscow, 2014
[email protected]
==========================[ START ]==========================
-- Devices enumerating --
Devices table (found 11 USB devices):
1 Device #0: USB Root Hub
1.1 Device #1: USB Hub
VID = 0x8087, PID = 0x8009
2 Device #2: USB Root Hub
2.4 Device #3: USB Hub
VID = 0x0424, PID = 0x2514
2.4.1 Device #4: USB-Eingabegerät
VID = 0x1bcf, PID = 0x0005
2.4.2 Device #5: USB-Verbundgerät
VID = 0x045e, PID = 0x00db
2.11 Device #6: Unbekanntes USB-Gerät (Fehler beim Anfordern einer Gerätebeschreibung.)
VID = 0x2207, PID = 0x290a
2.14 Device #7: USB-Verbundgerät
VID = 0x041e, PID = 0x30df
2.15 Device #8:
3 Device #9: USB Root Hub
3.1 Device #10: USB Hub
VID = 0x8087, PID = 0x8001
==========================[ STOP ]==========================
I've also attached my debug-log so you can check how to identify a blocked device - the hardware id is displayed as 'USB\DEVICE_DESCRIPTOR_FAILURE' in device manager in windows.
After creating the registry key as explained in the linked post above everything is working fine in windows 8.1, the drivers get installed and I can create a dump with your tool :good:
Finally it would great if you could add an automatic request for administrative permissions in your application - I think this would simplify the execution a little bit more.
Keep up the good work!

nalor said:
Can I create a full dump of a device including the user partition?
Click to expand...
Click to collapse
I still can't find a simple method of determining the full size of the NAND (it need to count user partition size)
nalor said:
To create this registry key you'll need VID, PID and REV from the usb device - maybe you can display REV also in your output of 'scan' ?
Click to expand...
Click to collapse
I have used USB_DEVICE_DESCRIPTOR for detection VID and PID:
Code:
typedef struct _USB_DEVICE_DESCRIPTOR {
UCHAR bLength;
UCHAR bDescriptorType;
USHORT bcdUSB;
UCHAR bDeviceClass;
UCHAR bDeviceSubClass;
UCHAR bDeviceProtocol;
UCHAR bMaxPacketSize0;
USHORT idVendor;
USHORT idProduct;
USHORT bcdDevice;
UCHAR iManufacturer;
UCHAR iProduct;
UCHAR iSerialNumber;
UCHAR bNumConfigurations;
} USB_DEVICE_DESCRIPTOR, *PUSB_DEVICE_DESCRIPTOR;
So what is revision in this structure?
nalor said:
Finally it would great if you could add an automatic request for administrative permissions in your application
Click to expand...
Click to collapse
Sorry, I'm not a programmer. I can't find example for C (CodeBlocks + gcc)

RedScorpioXDA said:
So what is revision in this structure?
Click to expand...
Click to collapse
Solved. Revision detection will be added into new version

rkDumper
Utility for backup firmware of RockChip's devices
New version (0.94 Windows) ready
! pre-Release #4;
+ support of RK3288 added;
+ manifest file added;
+ detection of device revision added;
~ administrator's rights checking algorithm changed.

rkDumper
Utility for backup firmware of RockChip's devices
New version (0.95 Windows) ready
! pre-Release #5;
+ support of RK3128 added;
+ /user key added;
+ ROM size/vendor/ID determinetion added ("info" command);
~ bug of incorrect determination of disks in multi-CD systems fixed.

Just thank you !

rkDumper
Utility for backup firmware of RockChip's devices
New version (1.00 Windows) ready
! Release;
+ /incl key added;
+ /excl key added;
~ some algorithms improved.

Hello, one question, is possible to use this tool with Rockchip/Intel sofia platform? Thanks in advance

Installing Kali on SM-T113

I'm trying to install Kali with Linux Deploy form the play store. I understand that my SD card may need to be partitioned, but I'm not sure how exactly. I also know that my device needs to support device looping, which I don't think it does. Is there a Kernel or ROM I can install to enable that?
I have a (Kingoroot) rooted Android Galaxy Tab 3 (SM-T113) running Android 4.4.4
Current kernel version 3.10.17-1114920
[email protected] #2
Linux Deploy gives me this output on status.
[16:03:06] >>> status
[16:03:06] Architecture:
[16:03:06] Kernel:
[16:03:06] Memory: / MB
[16:03:06] Swap: / MB
[16:03:06] SELinux: yes
[16:03:06] Loop devices: no
[16:03:06] Support binfmt_misc: no
[16:03:06] Supported FS:
[16:03:06] Installed system: unknown
[16:03:06] Status of components:
[16:03:06] Mounted parts:
[16:03:06] ...nothing mounted
[16:03:06] Available mount points:
[16:03:06] ...no mount points
[16:03:06] Available partitions:
[16:03:07] ...no available partitions
[16:03:07] <<< status

Kali is a Debian based Linux. Which makes it reliable and stable. But Kali Linux has grown so much. Now you can install it on almost anything. Once you iron out the kinks it can installed on most any device. Kali's distributions are already built to work on many things. Such as Live Boot USB, ARMs, Virtual Machines, Containers, Windows, The Cloud, and some Mobile Devices with Kali AKA Nethunter.
Kali Distributions https://www.kali.org/get-kali/
NetHunter https://stats.nethunter.com/
If you feel like learning how easy or hard it is. Most of the work has already been done. Just follow the path and you can create builds for smart watches or so I've heard
README.md · master · Kali Linux / NetHunter / build-scripts / kali-nethunter-devices · GitLab
Devices https://stats.nethunter.com/ https://nethunter.kali.org/
gitlab.com

Successful Bliss OS Installation does not finish booting

I have installed the latest Bliss OS 10.0 beta to my computer using the android-x86 installer from the developers. After it finished it said that the installation was successful. When I try to boot into Bliss OS though it stops after
"detecting Android_x86 . . . found on /dev/sda4
Android-x86_64:/# "
it allows me to type some minimal commands but will not boot to Bliss OS. I have no idea what to do. Here are some specs of my laptop.
Machine name: DESKTOP-T1R6H4T
Machine Id: {CB81229F-8457-413F-A7A3-679CEB484FCF}
Operating System: Windows 10 Home 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
System Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
System Model: 305E4A/305E5A/305E7A
BIOS: 00TL.MI22.20120511.SKK
Processor: AMD A6-3420M APU with Radeon(tm) HD Graphics (4 CPUs), ~1.5GHz
Memory: 4096MB RAM
Available OS Memory: 3564MB RAM
Page File: 2317MB used, 2590MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.16299.0015 64bit Unicode
Card name: AMD Radeon HD 6520G
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x9647)
DAC type: Internal DAC(400MHz)
Device Type: Full Device
Device Key: Enum\PCI\VEN_1002&DEV_9647&SUBSYS_C624144D&REV_00
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 2035 MB
Dedicated Memory: 499 MB
Shared Memory: 1536 MB
Current Mode: 1366 x 768 (32 bit) (60Hz)
HDR Support: Not Supported

I'm having the same problem. Did you ever get it to work?

Same problem
I have some problem.
My laptop is Lenovo 110-14ast AMD A9 wtih 4gb ram.
I was installed android x86, remix os, and now Bliss os but all os cant boot to android , stuck on logo (remix) or terminal before logo. ~androidx86#
Also i was installed on virtual machine gnu/linux but cant boot..
Very2 sadly with this..:crying::crying:

these are usually issues related to the kernel. try a build with a different kernel

Develop Bugs

welcome