Develop Bugs

[Links Included] Android Eclair 2.1 Beta Releases on i8000 by Almar and his dev team

FROYO IS OUT NOW!!! SEE HERE
FEATURES
Supported features in latest public beta release:
HARDWARE
Display & Touch screen
Hardware keys
Internal & External storage
Vibrator
FM radio
Sound & Audio output via 3.5mm jack
Proximity and Light sensors
Orientation (Accelometer), Magnetic (Compass) and Temperature sensors
CONNECTIVITY
Phone & messaging
Wifi
GSM data (GPRS/2G/3G/..)
USB (ADB)
GPS
SOFTWARE
Android 2.1 (Eclair)
Android market
Rooting
2D/3D acceleration (libs are not included due to legal issues)
Open-source patches: I8000 B7610 M715&M8400
OTHER FEATURES
Battery driver/charging
Brightness control/backlight
COMPATIBILITY ON OTHER PHONES
Omnia pro (B7610): wifi not working
Omnia pro (B7610): hardware keyboard not working fixed
Omnia pro (B7610): some hardware buttons not working fixed
Omnia pro (B7610): vibration not working fixed
T*Omnia II (M715): not working when not connected to USB fixed
T*Omnia II (M715): headphone plug problem fixed
T*Omnia II (M715): some hardware buttons not working fixed
T*Omnia II (M715): phone not working (>rev??)
Show Omnia (M8400): wifi not working fixed
Show Omnia (M8400): USB/headphone plug/hardware buttons problems fixed
Verizon Omnia II (I920): not working
FEATURES UNDER ACTIVE DEVELOPMENT
Camera's
Proximity sensor (only kernel support yet)
Light sensor (only kernel support yet)
Bluetooth (only kernel support yet)
I920: Beta support
FEATURES UNDER DEVELOPMENT
Android 2.2 (Froyo) {sleep bug}
Android 2.3 (Gingerbread) {slooooow and some Eclair features broken}
POSSIBLE FUTURE FEATURES
Android kernel and image build from github.com
TV-Out
B7610: wifi driver
I920: CDMA phone part
___________________________________________________________________
TUTORIALS, MODS, ADD-ONS
BETA 1 INSTALLATION TUTORIAL By Me, l3ong91, XDA
1. Backup the files on your microSD first.
2. Go to Start>Settings>Memory Settings>Storage Card and click Format.
3. Download any one of the files provided on http://o2droid.phj.hu/index_en.php file section.(you can download either 512 partition image or 1GB partition image)
4. Extract the files and put it in My Storage. (Attention: Copy only "o2Beta" folder and default.txt, ext2.tar, haret.exe, log.txt, and zImage to the root of my Storage) Look at attachments.
5. Open "o2Beta" Folder and run haret.exe
6. Wait for it to load and until it say something like reboot, the device will auto reboot so just leave it there.
7. It will boot up Windows Mobile again.
8. Then go to My Storage and click on haret.exe
9. This time it will boot again and after awhile you will see Android logo on the bootscreen.
10. After the Android 2.1 was booted, hold on the "Lock" button for 3-4 sec and
turn off the device. (It will boot up Windows Mobile again, or sometimes you will have to do it manually to turn on the device)
10. Now download and copy http://rapidshare.com/#!download|482l33|443140910|o2bupdate.tar.gz|1480 and http://87.229.73.80/zImage file to root of My Storage and overwrite it.
11. Then run the haret.exe from My Storage (not inside o2Beta folder).
12. This time it will bootup faster than the first time.
13. Yes...Android's dream come true on Omnia i8000
BETA 2 INSTALLATION TUTORIAL By Kapica, MoDaCo
1. Clean SD card of beta1
a) Clean format with SD Formatter, or
Use EASEUS Partition Master and format the EXT2 partition on SD card
2. Rename o2b2filesys.tar.gz to ext2.tar.gz
3. Copy ext2.tar.gz and new zImage to My Storage and overwrite
4. Go to O2Beta directory and run haret.exe
And thats it, u get beta2 installed, rest as usual...
To add 2D/3D rename tar.gz to o2b2update as devs said...
If you experience reboots I think its to lack od 2d/3d, open the 2d/3d o2update.tar.gz and copy system directory into ext2.tar with Total Commander, save archive, copy to My Storage, and try to install now.
BETA 2 INSTALLATION TUTORIAL (EASY ALTERNATIVE) By Me, l3ong91, XDA
1. Download the latest installation package as of 11/2/2011
2. Format SD Card again using Samsung Settings>Format.
3. Delete all the Beta 1 Folder and Beta 1 files in My Storage.(if you have previously installed Beta 1 on your phone)
4. Extract and copy all the files in Beta2 installation package to My Storage.
5. Download one of the 2D/3D driver links below and rename as o2b2update.tar.gz
6. Put it in My Storage.
7. As usual, run haret.exe from o2Beta folder.
8.Then after reboot, run haret.exe from root of My Storage.
2D/3D DRIVER DOWNLOADS
For Beta1 Installation
Download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
For Beta2 Installation
Rename as o2b2update.tar.gz
http://rapidshare.com/#!download|482l3...ate.tar.gz|1480
http://www.filesonic.com/file/60103983/o2bupdate.tar.gz
TO ROOT BETA2 by turnado1979, MoDaCo
Download this and put it in root of My Storage
TO PREVENT PHONE FROM SLEEPING DEATH By slmz, MoDaCo
Settings>Wireless &network settings>Mobile networks> Tick "Use only 2G networks"
- 4% last for about 9 hs
BUTTON FIXES AND REMAPPING
Button fixes:
To wake up the phone with Hang up and Lock buttons only - by Rapid81
Menu button unlock policy fix - by ult_nrg
DUAL BOOT WIN-MO AND ANDROID ON OMNIA 2
1. Get Gen.Y DualBOOT from megaupload (http://www.megaupload.com/?d=HRPO9CC7)
2. Only use "Gen.Y DualBOOT WVGA v1.0.6.0 - Storage Card.cab" and delete other cabs.
3. Install cab on "Device Storage" (otherwise doesn't work)
4. Copy/move Haret.exe ,default.txt, zimage to root of SD card.
**If you want fastboot (no pushing OK in Haret) rename default.txt to startup.txt
GET LIVEWALLPAPER WORKING By Aafi-rocks, MoDaCo
1. Boot to windows and Connect your phone to PC in Mass Storage mode
2. Open ext2.tar.gz using 7-zip
3. Then go to below path ext2.tar.gz\ext2.tar\system\lib\
4.unzip the attached lib.zip file and copy all the 3 files here..
5.Then go to below path ext2.tar.gz\ext2.tar\system\app
6. Unzip the attached app.zip file and copy all the files here.. (you can also copy any other APK files for games and apps here, if you want to pre-install them)
7. Now close 7-zip and it will ask you if you want to update the archive.. click yes..
8. Now re-install Android..
Once Android is booted. On the home screen try changing the wallpaper and there you see the live Wallpaper option...Select the Live wallpaper of your choice and Njoy...!!
You can also do this without re-installing Android..
1. Explore your phone using Droid Explorer then navigate to system/lib and copy the files from the attached 'lib.zip' here..
2. Then using droid explorer install the APK files from the attached 'App.zip' file..
ADB INSTALLATION AND TUTORIAL By Rapid81, MoDaCo
1. First af all, you need to set the ports under Android.
To do that, write this to the phone: *#7284#
Then you need to select the followings:
UART -> Modem
USB -> PDA
After this, go to the Settings\Applications\Development and check the USB Debugging if it not checked already.
2. Download the Android SDK from here. Install (if you downloaded the installer) or unzip to a location where you'll easly found it. For example C:\android-sdk-windows.
3. Download Samsung KIES. Install it. It contains 2 of the 3 necessary drivers.
4. Download the SamsungADB.zip and unzip it somewhere, where you'll easly found it.
5. If the Android did not went to sleep after it started, then unplug from USB (if it plugged) and put to sleep with the Hangup button. After that, plug onto the USB. The Windows will install 2 of the 3 drivers automatically. The 3rd one will not be found. This will be the ADB driver. Go to the Device Manager and browse the driver (not just add the path to the search root, you need to select the driver yourself!!!) what you extracted from the SamsungADB.zip. Choose one of the followings:
Samsung Android Composite ADB Interface or ADB testing interface and install it.
If the Windows ask for a confirmation to install a not trusted driver, then say yes.
6. Press Windows+R and type into "cmd".
In the upcoming windows, navigate to the unzipped or installed Android SDK directory with the following command:
For example: "cd c:\android-sdk-windows"
In there, navigate to the "platform-tools" directory with this command:
"cd platform-tools"
7. This is where the party started.
Commands you can use:
adb devices -> If you see your device here, you did a good job.
adb shell -> console
In the console:
logcat -> List all android events/errors
cat /proc/kmsg -> kernel log
adb push filename folder -> Send file from Windows to android, to the specified folder
adb pull filename -> Receive file from Android to Windows
Backup all installed applications (rooting is necessary):
tar czvf /storage/App_backup.tzg /data/app* -> Backup
tar xzvf /storage/App_backup.tzg -> Restore
ADB Installation Guide on Omnia2Droid Google Source Code Page
http://code.google.com/p/omnia2droid/wiki/InstallAppsADB
___________________________________________________________________
EXTERNAL SITES, LINKS, AND PAGES
Beta Release Official Download Page: http://o2droid.phj.hu/index_en.php
Beta Release Source Code Page: http://o2droid.phj.hu/trac
Omnia2Droid Official Source Code Page: http://code.google.com/p/omnia2droid/
Almar's Twitter Account (INB2ENSECURITY): http://twitter.com/#!/INB2ENSECURITY
MoDaCo "Android on Omnia 2" Thread: http://www.modaco.com/content/i8000-omnia-ii-gsm-rom-discussion/322429/android-on-omnia-ii-i8000/
YouTube "Android 2.1 Eclair on Omnia 2" Video: http://www.youtube.com/watch?v=8khXDEOO96Y&feature=player_embedded
Source Code Repository Browser: http://o2droid.phj.hu/trac/browser
Omnia Pro B7610 Discussion Forum:http://www.modaco.com/content/b7610.../331432/android-tutorials-and-known-problems/
Verizon Omnia II(I920) Discussion Forum:http://www.modaco.com/index.php?showtopic=330325&view=getnewpost
___________________________________________________________________
LATEST NEWS & UPDATES
18/1/2011
Beta 1 (Minor Fix) Link: http://o2droid.phj.hu/index_en.php
19/1/2011
New Kernel (zImage) Sleep Issue Fixed Link: http://87.229.73.80/zImage
27/1/2011
Battery charge corrected, missing interface for redio signal level, powerstate,etc. was fixed. Put in root of My Storage and overwrite it. http://o2droid.phj.hu/o2droid.zip
30/1/2011
Script included for apps that needs ROOTED Android device: http://o2droid.phj.hu/suupdate.zip
31/1/2011
Working GSM data network. The o2droid.zip file contain the latest kernel,modules, patches and applications from Rapid and Voyteckst su correction.http://o2droid.phj.hu/o2droid.zip
9/2/2011
Sleep problem solved, Alarm function working, battery drain and percentage correction, upgrading from C4 to D1 the 6500 framework, more powerfull dalvik machine (Linpack 5.x) and all the usable corrections published. There are two version, a simple upgrade to the beta: o2bupdate.zip (just unzip to My Storage) and a new filesystem including all changes and rearranged file structure: o2b2filesys.zip (contains the filesystem as tar.gz and the kernel, must unpack and copy manually - no automatic install). The later one is the beta2 (this will be commiting to the SVN); there are some changes in the automatic updates when using the beta2 image to avoid the mistakes : the new automatic filenames are o2b2update.[tar.gz][sh]. Neither version contains the EGL libraries!http://o2droid.phj.hu/index_en.php
10/2/2011
Bugfix: the init dont allowed the GSM network to get DNS, dalvik vm problems. update it with o2b2update.tar.gz ( for beta2, if you use just the corrected beta, please rename it to o2bupdate.tar.gz). There is a strange error: within telephone conversation in approx.30 seconds the LCD blanks but also the sound muted - UNTIL NOT SOLVE, please use the Call Light application from Market!!!
11/2/2011
We have prepared Beta2 SD card installer (1024mb only). It includes latest update (2011-02-10). Download it http://87.229.73.80/beta2_1024.zip (it will wipe Your current installation). As always it doesn't contain 2D/3D libraries from Samsung (if You found them somewhere on the web put it before first boot to My Storage as o2b2update.tar.gz).
Note: There is still error, when within telephone conversation in approx.30 seconds the LCD blanks but also the sound muted - UNTIL NOT SOLVE, please use the Call Light application from Market!!!
3/3/2011
Updated kernel and modules with support for accelerometer, compass and light sensor, keylayout files for new kernel. Download it here . Install as always: replace zImage, put o2b2update.tar.gz, o2b2update.sh to My Storage. It will work on second boot (because old init.rc is executed first).
So now working things are:
Phone
WiFi
GPS
FM Radio
Market
Data connections (GPRS)
Sensors (only proximity sensor not yet)
2D/3D (Samsung not allowed to us to distribute the 2D/3D library binaries, so they are not included in the image).
Things which are working (low level tests), but without android support for now:
Bluetooth
Camera (there are some works to be done)
8/3/2011
To enable the automatic time update from the GSM there is a simple update script. The timeupdate.zip contains both o2update.sh and o2b2update.sh, copy the proper version (in the case of beta2 image: o2b2update.sh) to the root of the My Storage and haret... At first boot just updating the system database to use the telephone network time, so must reboot again to really use this setting and show the correct time.
9/3/2011
There was a rare condition when the SD card appeared sooner than the internal flash at boot - resulting the "No init found" error in kernel. The reason that the sdhci interfaces was not stricly assigned to an mmc device - the first sdhci was the mmc0. This is corrected now, so the s3c-sdhci.1 is the mmc0, .2 is the mmc1 and so on. The corresponding kernel ( svn version 100): zImage
19/3/2011
New kernel and modules (+ keylayout for those who didn't update it yet). Main changes are: fixes for SDHCI/MMC (ported from 2.6.32, external sd is much faster now), new battery profile (now percentage is more like in WM), compass calibration bugfix. Download here: kernel_19032011.zip.
___________________________________________________________________
UNOFFICIAL RELEASES
There is an ISO file, which was compiled by Mishatir, a MoDaCo member whom is dev team related, I think. I know this is a bit late....I'm sorry because I am unaware of this unofficial release too until recently read the comment on MoDaCo.
Alright to saves time, this is what it does. This ISO is a all-in-one package where it contains the updates and some modification (camera still not working yet though), but may or may not work with devices other than I8000, because currently I only tried out on my device.
From my experience, this ISO file is really amazing, no sleep of death issue, low battery consumption (dropped from 91% to 80% for 12+ hours) and pre-installed with few apps that you can try out.
Comment by MoDaCo member on the ISO
file
Short guide by Mishatir on ISO
Instructions:
1. Wipe out all Beta 1/2 files on your My Storage and format your SD card under Samsung Settings.
2. Download the ISO file here.
3. Unrar the files.
4. Connect your phone in WM mode and placed the "iso folder" under root of My Storage.
5. Run haret.exe in the ISO folder.
6. Android should bootup.
This ISO has few updates (kernel + modules.tar.gz) by Mishatir, if you want to update them,
- zImage --------> Replace zImage under ISO folder
- modules.tar.gz ----------> Rename to o2b2update.tar.gz and placed them under root of My Storage
To avoid Sleep of death , I use "Call End" key to lock and unlock the phone...Pressing" End key" seems to be easier and more responsive to unlock the screen.
Personally I don't recommend to update because since I update it I faced a few problems which eventually cause the Android not booting up....so try all this update at your own risk.
Anyway, this is a very nice and most stable release. Now I can use Android on my daily basis. For more questions, please leave a comment.
CREDITS
Credits to Almar and his dev team, I am not one of them. I'm here to spread this big news over XDA forum to inform every Omnia 2 users about this amazing breakthrough.

Just tried and its works great
Sent from my GT-I8000 using XDA App

problem
there is a problem when it is runing the linux help

Fantastic guys
Sent from my GT-I8000 using Tapatalk

killerkarara said:
there is a problem when it is runing the linux help
Click to expand...
Click to collapse
What problem you faced? Did you follow the instructions provided?

Here is some information for people who don't want to read the whole thread on Modaco.
Video of Beta on Omnia II by Rapid81:
http://www.youtube.com/watch?v=8khXDEOO96Y
Download beta release here:
http://o2droid.phj.hu/index_en.php
Download 2d/3d drivers and install here (you need these else above beta will freeze every 5 mins):
To install 2d/3d drivers download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
http://rapidshare.com/#!download|482l3...ate.tar.gz|1480
http://www.filesonic.com/file/60103983/o2bupdate.tar.gz
To manage ext2 partitions from Windows PC and to correctly format your SD card:
To delete ext2 from Windows PC I use EASEUS Partition Master 6.5.2 Home Edition. It is freeware, and seems to work well. Then to format the micro SD I turn on mass storage in samsung settings, connect to PC and use the SD formatting tool 3.0 from sdcard.org. It uses FAT (not FAT32) and 32kb cluster sizes. I do quick format...
For more information and to report bugs:
http://code.google.com/p/omnia2droid/
Almar's (one of the developers) twitter:
http://twitter.com/INB2ENSECURITY
Big thread on Modaco:
http://www.modaco.com/content/i8000-omnia-ii-gsm-rom-discussion/322429/android-on-omnia-ii-i8000/

ummh when installing the heret.exe for the second time it stops for some reason

killerkarara said:
ummh when installing the heret.exe for the second time it stops for some reason
Click to expand...
Click to collapse
I had similar problems, stuck on the linux part. It said it couldn't mount mmcblk0p5, wich is the SDcard. I solved it by reformating my SDCARD in fat32 and it worked.

ive done step by step on what to do but its stuck on the linux boot screen last line displayed is jumping to heart and it stays there. any help would be awesome. ive installed everything to the my storage section on my phone

First of all: INCREDIBLE WORK!!! CONGRATULATIONS!!!
I've tested and it is working, but unfortunately it is freezing time after time...
I have tried this:
bobzero said:
Download 2d/3d drivers and install here (you need these else above beta will freeze every 5 mins):
To install 2d/3d drivers download o2bupdate.tar.gz and place in "My Storage\o2bupdate.tar.gz" , this should stop the phone from freezing every 5 minutes:
Click to expand...
Click to collapse
... but no difference

is this done using harnet?

yes it uses haret.

bobzero, there's a new updated kernel release by Almar...have you tried that out?

Is there any plan for supporting Omnia Pro (B7610)? Most of components are equally identical.

yes, it's working even better! battery drains slower now.

Soul_Master said:
Is there any plan for supporting Omnia Pro (B7610)? Most of components are equally identical.
Click to expand...
Click to collapse
definitely agree with the sentence

B7610 currently not officially supported by Almar's android
maverick_endit81 said:
definitely agree with the sentence
Click to expand...
Click to collapse
Currently Almar and his team only focuses on omnia i8000, perhaps there maybe a tiny possibilities that they will release a android for other samsung phone...try checking out forums and google
Below link is maybe useful to B7610 users: http://www.modaco.com/content/b7610...-android-on-b7610-thnks-to-devs/#entry1566239

i noticed some b7610 users on the modaco thread saying that it works, but with some additional glitches... wifi doesnt work, no menu button mapped...
try it out

bobzero said:
Video of Beta on Omnia II by Rapid81:
http://www.youtube.com/watch?v=8khXDEOO96Y
Click to expand...
Click to collapse
"This video contains content from Believe and Sony Music Entertainment, one or more of whom have blocked it in your country on copyright grounds."
EDIT - Ah. Been a while since I've tried, but you can use an anonymising proxy (I used http://www.hidemyass.com) to get around the restriction on YouTube.

Thanx Almar and other devs team..~~
just to share my method to make android working in my omnia..
format SD card thru samsung setting.. download and combine 1gb 18jan android + 19jan zImage update + 2d/3d patch together. after that I copy that bunch of files into omnia 'My Storage' root. (It content o2beta, default, ext.tar, haret, zImage)
first, run the haret.exe from 'My Storage/o2beta' !! . after press RUN wait till it finish with the partition. more or less than 10minute to get this done. after that, ur phone will auto restart.
after restart, run haret.exe from 'My Storage' root. !! press RUN...
Kabbooom... new life begin
I installed pro launcher n make it my default home screen n it run smoothly..
angry bird is playable too.. to make it short, Am AMAZED with this 1st beta..
just my 2 cents..

[Guide] Eden Midas 8" Tablet

Moderators, please permit me to leave the tablet's Korean name (Eden Midas: 이든 마이다스) here so it shows up in google searches (if you don't have Korean fonts, it will probably show as garbage, but it really does say "Eden Midas" in Korean script).
This thread is intended as a place to collect together information about the Eden Midas tablet. It's quite possible that we will eventually find that the internals are the same as one of the Chinese tablets using the RK2918 chipset, in which case the thread may just turn into a pointer to that other thread.
What is the Eden Midas tablet?
In the form I have it, an 8" tablet based on the RK2918 chipset, with ICS 4.0.3 and kernel 3.0.8+ (whatever the plus may mean). It's quite nice, with a very clean 1024*768 screen. But like most RK2198 builds, severely locked down and marketed just as an entertainment station. At present, it seems to be only sold online in Korea. My build is V1.0.1.IMK74K.eng.root_20120508.165508_HW:1.0.0.0 (I wonder if the HW stands for huawei??).
Rooting[\B]
This is all I've done so far. Here's what I did:
On Linux
What's needed:
You may need to have root privileges on your linux system (you will need to mount some filesystems, and edit a udev rule file - depends on the linux system who is allowed to do these). You will also need rk2918tools ( https://github.com/lamegopinto/rk2918tools) - these are tools collected by lamegopinto, credits inside to the original authors; specifically, you will need ivop's rkflashtool.
In theory, this shouldn't remove your applications, data, and settings. In practice, on my machine, it did. So I'd back everything up first. And take out any external sd card so it's safe. Also, I better warn that I had a few scary moments getting to here, so please make sure you have really good backups. You will need (on your linux system) copies of su, Superuser.apk and busybox.
Connect the tablet by USB to your linux machine (real or virtual). Put the tablet into fastboot mode by holding down the whole +/- key, then pressing the start key for about 3 seconds. Keep holding the +/- key for up to ten seconds. If the system boots or goes into the boot screen (android open robot icon) you need to try again.
On the linux system, type lsusb (if you get an error, you probably need to install usbutils - how you do this depends on the linux system). If you see 2207:290a, you are OK. If you see 2077:0000, you missed fastboot mode and need to try again.
Tell linux about your device. You need to install udev rules.
Code:
cd /etc/udev/rules.d
sudo pico 61-android.rules
then create the content
Code:
# USB devices
SUBSYSTEM=="usb",ATTRS{idVendor}=="2207",ATTRS{idProduct}=="0000",MODE="0666",GROUP="users"
SUBSYSTEM=="usb",ATTRS{idVendor}=="2207",ATTRS{idProduct}=="290a",MODE="0666",GROUP="users"
This is for fedora 17. On current ubuntu the priority number (the 61 in the file name) probably needs to be different (maybe 51?). In earlier systems, the udev rule format is different, you're going to need to google this. The above rules also include one for adb mode, which will probably turn out useful. If you want adb mode, you will also need to do this:
Code:
pico ~/.android/adb_usb.ini
and create the content
Code:
0x2207
Create a directory called MIDAS inside the directory where you stored the rkflashtools. You need to have probably 2 times the capacity of your sdcard available (if you have an 8GB internal sdcard, I'd aim for 16GB+ free). Go into that directory.
Use ivop's rkflashtool to retrieve the first 2K blocks of memory:
Code:
../rkflashtool r 0x0 0x2000 > headers
This will create a file called headers. It's a binary file, but the important bit is readable. Try
Code:
more header
to read it, and carefully note down the partition locations (note that the order parameter order is the opposite to what rkflashtool uses. [email protected] means that the partition consists of X blocks starting at Y. Whereas for rkflashtool, you specify "rkflashtool (r or w) Y X (< or >) filename". The numbers X and Y are in hex notation (that's what the 0x at the start means). Note also that the MIDAS has a different layout to the tablet Ivop was discussing).
Now retrieve all the other partitions from the device, giving them descriptive names. For root, the only one you will actually need should be system.img. But get the rest just in case, as backups... Please note that there seem to be some funnies with this device, and rewriting partitions often causes it to reinitialise everything. It's probably doing some checksumming... Please keep these image files safe, and don't edit them! But you can gzip them to reduce the space they take up. Please note also that the last partition - usually the user partition - goes to the end of your card. So you need to convert your flash card size into a hex number (e.g. 8GB is 0x200000000 bytes, or 0x10000000 512B blocks). Suppose the user partition starts at 0x32A000. Then you need to put its length as 0x10000000 - 0x32A000 = CD6000 blocks (you may need a hex calculator for this).
Download su, Superuser.apk and busybox (these are all public domain) into your MIDAS directory
Code:
cp system.img system.new.img
mkdir mnt
sudo mount -t ext3 system.new.img mnt
Copy su into mnt/xbin, busybox into mnt/bin and Superuser.apk into mnt/app (simplest is to use a file manager to do this - or use linux commands). At this point, your image is complete!
Code:
umount mnt
../rkflashtool w (the system partition address and length for _your_ system image, which might be different from mine) < system.new.img
../rkflashtool b
Disconnect the USB cables
Your system should now reboot. If you're lucky (I wasn't) it will reboot as a rooted system with all your files intact. If you're semi-lucky, it will reboot as a rooted system, but without your files. Hope your backups were good... If you're really unlucky, it won't reboot. You may need to recreate all partitions from the copies you just made above, and try again. If the system seems completely bricked, the reset button (the tiny pinhole in the back, just above the external sd card door) is your friend. Pressing it and going into fastboot mode can allow you to reload all your partitions (you did make those backup copies of all partitions, didn't you)?
On Windows[\I]
Sorry, I have no idea. If someone drafts a guide, I'm happy to put it up. Alternatively, you can easily install a ubuntu virtual machine inside your windows box. It will probably be easier, and the linux experience won't go astray in working with android anyway.
[Tun Drivers and Openvpn]
For some reason known only to themselves, the manufacturers have removed the Tun drivers from the ics kernel build. The kernel doesn't have the ability to load modules. (This makes sense for phones, maybe, but I can't understand why anyone would remove the ability to load modules in a tablet. Perhaps the Chinese government doesn't want it to be too easy for people to set up vpns?) Anyway, you can install what appears to be a suitable Tun module using Tun.ko installer. It installs OK but when you try to use it, the system freezes for about 10 seconds, then reboots. If anyone finds a version of the 3.0.8+ kernel (maybe 3.0.8- kernel would be a better name), suitable for the Midas and with either a built-in tun driver, or the ability to load kernel modules, please let me know.
Complete Reflashes
Not sure if there are any that will work right now. If you're really stuck, the cyanogenmod version for Cube might work, but it sounds like it is still a work-in-progress.

Do you have the kernel of the tab?
- Oma -

Oma7144 said:
Do you have the kernel of the tab?
Click to expand...
Click to collapse
Sorry, no - and sorry for the delay in replying, I didn't get notification for the thread.

Dump the firmware and upload the files: http://forum.xda-developers.com/showpost.php?p=35298423&postcount=462
- Oma -

THBK1-10 thread: extend, root, hack !

Hello,
I'm the proud owner of an hybrid monster, called THBK1-10.
This is basically an affordable tablet, running both Windows 8 and Android 4.2.2.
10.1 display, running x86 Atom 4cores, 2Gb RAM, 32Gb eMMC, USB host enabled. It is shipped with an external keyboard/touchpad (no port, no battery, no extended storage on it). More informations: http://www.thomsoncomputing.eu/dualboot.html
Windows 8 comes in x86 flavor...
The boot process let you choose Windows or Android.
There is no play store. My main goal actually is:
- (ok) rooting Android part
- (ok) installing Play Store
- (ok) increasing space
- (nok) installing a recovery (CWM/TWRP) allowing you to flash non-signed updates
- (nok) running Linux from an external USB drive
Partition layout: http://forum.xda-developers.com/showpost.php?p=54095052&postcount=8
Rooting / play store guide: http://forum.xda-developers.com/showpost.php?p=55513404&postcount=23
Known clones: http://forum.xda-developers.com/showpost.php?p=54282229&postcount=10
Increasing space with external SD: http://forum.xda-developers.com/showpost.php?p=54914759&postcount=17
Timezone issue Android/Windows: http://forum.xda-developers.com/showpost.php?p=54945950&postcount=19
BIOS default (SlateDroid): http://www.slatedroid.com/topic/106594-thbk110-default-bios-values/
Have fun !

I know there are EXT2 drivers for Windows, and EXT3 is just EXT2 + Journaling (the journaling is an important feature, but it's not part of the security model). However, I'm not sure if any of those drivers can modify file permissions. Alternatively, one could of course hex-edit the Android partition and try to tweak the file permissions that way, but that would require much more understanding of the EXT filesystem than I have. The source code is all open, though...

Thank you. Here is what i did:
a) trying to handle EXT3 fs from Windows
-> with Ext2Fsd, i have accesses to all the partitions, including /system and /data, but unfortunatly, permissions are not correct
-> i trying with other tool (Explore2Fs) not luck
-> ltools seems to provide a lattr util that could do it, but i'm unable to see the files (certainly because of the GPT partition
b) trying to use VirtualBox with raw disk access for handling, with a linux guest, permissions:
-> up to partition 7, this seems correct
-> from partition 8 (/system), i can mount it in RO but it crashes in RW
c) trying to boot to any linux supporting EFI32 and GPT
-> thanks to paperwastage, i could achieve it (thread here: http://forum.xda-developers.com/showthread.php?t=2500078 )
-> i have strange troubles: the system only detect mmcblk0 to mmcblk7, and is throwing an error (error -110 + unknow command)
-> both, in clonezilla and ubuntu
d) tryed to use so android local tricks to force change mode, but once, i'm stuck with no eXecute flag. I dig around the local.prop or any stuff that would help me to achieve this goal. The recovery is not available (nor i found it) and the only thing i can do is factory reset.
It really seems only Windows got the proper drivers for this eMMC. This could explain why i had hard time to dump it (and, actually, i would not try to restore b/c i'm not sure everything is backuped correctly and don't want to brick my tablet), and why i could only write from Windows and why it cuts at partition7 (i have at least 12 partitions. NTFS windows main is the #11 iirc)
What i could try actually:
-> double check with newer ubuntu (when i started "install to disk", it seems it could detect the whole disk, have to look again)
-> double check with local THBK install (copy 3 apks bundled with the tablet, but perhaps a command script is available to be executed ?)
-> double check with virtual box & raw disk acces (i focused on /system, but perhaps /data is ok ?)
-> recompile Ext2Fsd to have different default properties
-> dig the hardware to see if a real recovery boot is not available, or change the recovery to something more usefull than factory reset
Thank you if you have more and more ideas

Quick notes:
- THBK1 does NOT connect to PC/MAC
- THBK1 does NOT have USB Debug activated. The micro-usb is aimed to put a (normal) cable, not an OTG one nor a charging cable. You can reach ADB only over Wireless.
-> Currently trying TowelRoot with different parameters, but for now not successfull. Basically this is a 4.2.2 kernel so i could expect a low resistance at exploits, it worths to be tested

Good news, i was able to boot from an USB stick (with EFI), and while the MMC is not accessible, i found a trick to change permissions.
I have now full R/W support on EXT3 partition.
But sadly SU is not enough to gain root accesses.... damn.
Anyone able to find doc or explain how root access is triggered ?

I found an update, and i'm now able to flash the whole system partition. Sadly, i could not flash another update.zip, so i guess this is signed (and sadly it is).
I have also tryed z4root, towelRoot exploits, not working.
Basically i could somehow bypass the sign system in applying myself the content of the update.zip (as long as it deals with /data and /system files & perms). I'll try that for at least google apps.
edit: ok i have now play store and the whole google suite is working after a big playstore update (talkback, vocal syntgetisis and so on). Only google+ is FCing but it should only be a matter of installation. I should remove it and reinstall it from the market.
Only thing missing is root
Status on Android forum side: http://forum.xda-developers.com/android/help/hacking-thbk1-10-getting-root-t2804631/post53896017

As today, the tablet is now rooted. It works flawlessly.
Next step is the handling of recovery to flash non-signed zip files. It would ease the process of installing GAPPS or rooting the tablet.
But i'll take a break before
TODO list, from top to crazy:
- recovery
- test and deploy various system tweaker sur as Xposed framework
- bugfix vibrator (only working when you hit Windows button, not in apps)
- new rom, new kernel

Here is the actual partition layout:
Code:
Model: MMC BIWIN (sd/mmc)
Disk /dev/mmcblk0: 30.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 269MB 268MB fat16 ANDROID!bootloader boot, hidden, legacy_boot
2 269MB 337MB 67.1MB ANDROID!panic
3 337MB 873MB 537MB ext4 ANDROID!factory
4 873MB 2484MB 1611MB ANDROID!fake
5 2484MB 2618MB 134MB ext4 ANDROID!config
6 2618MB 4229MB 1611MB ext4 ANDROID!cache
7 4229MB 5303MB 1074MB ext4 ANDROID!logs
8 5303MB 7450MB 2147MB ext4 ANDROID!system
9 7450MB 11.7GB 4295MB ext4 ANDROID!data
10 11.7GB 11.7GB 1049kB ANDROID!misc
11 11.7GB 11.8GB 33.6MB ANDROID!boot
12 11.8GB 11.9GB 134MB ANDROID!recovery
13 11.9GB 11.9GB 33.6MB ANDROID!droidboot
14 11.9GB 12.3GB 315MB ntfs Basic data partition diag
15 12.3GB 12.5GB 273MB fat32 EFI system partition boot
16 12.5GB 12.7GB 134MB Microsoft reserved partition msftres
17 12.7GB 30.9GB 18.3GB ntfs Basic data partition msftdata
I'm not able to read the partition w/o filesystem (2, 4, 10, 11, 12, 13).
I tryed with yaffs2, but i'm not able to see them (and since it is not MTD...)
I'm working on dd image of the 32Gb MMC.
In example, hexdump of partition 12 shows it is a kernel. Certainly the recovery kernel directly flash, i should dig this.

Guide: installing Google Apps and Rooting the tablet
THIS POST IS DEPRECATED. See http://forum.xda-developers.com/showpost.php?p=55513404&postcount=23
:good: /!\ Please click thanks or offer me a coffee with donate if it was usefull for you /!\ :good:
This is rather technical, but i can help if you are stuck. Thank you for your comments.
Here is how you could install Google App suite to the THBK1-10 and certainly many ones based on Inside H2O bios, board name: CARD_B (see above for detailled specs)
Basically, to install some stuff, the concept is to get rid of all the caveats (special MMC drivers, EFI 32 bits with GPT, etc...) through actual Windows 8.1 installation. Everything takes place through classic Windows desktop. For convenience, personnally worked with TeamViewer, doing this with the dock/touchpad is pain in the ass. You can void your warranty and break the android part of your tablet, so operate carefully, i'm not responsible of what you do !
This leads to 3 phases:
a) accessing EXT4 Android partitions
b) transfer files from Windows to Android
c) change permissions
a) Accessing EXT4. I used coLinux to access and handle Android EXT4 partitions:
- download and install coLinux http://sourceforge.net/projects/colinux/files/latest/download?source=files. At the 'Choose components' screen, uncheck 'Root filesystem image Download', and accept everything (including TAP drivers)
- download and unzip Debian Squeeze image in coLinux folder (c:\program files\colinux). Warning, this leads to a 2Gb file, ensure you have proper space. You could unzip it in your external SDcard, but you would have to change the path to rootfs and swap in above squeeze.conf
http://sourceforge.net/projects/col... 6.0 Squeeze/Debian-6.0.1-squeeze.7z/download
- test it: click on the squeeze.bat file into c:\program files\colinux (if you have an error co-slirp, simply close colinux and restart it). Once you have the 'debian login:' prompt simply type root then enter. You are now under coLinux.
First, install your local keyboard (if needed)
Code:
apt-get update
apt-get install console-setup locales console-data
In case you miss the point for the keyboard:
(choose select keyboard from full list / pc azerty or whatever...)
Code:
dpkg-reconfigure console-data
- you should now update your /etc/apt/sources.list file:
Code:
nano /etc/apt/sources.list
- fill with the following lines (remove all before)
Code:
deb http://ftp.fr.debian.org/debian/ squeeze main contrib non-free
deb http://security.debian.org/ squeeze/updates main contrib non-free
- update your apt repository:
Code:
apt-get update
- you would like to sync the clock from Linux with Windows: edit /etc/default/rcS and change UTC=yes to UTC=no
Code:
nano /etc/default/rcS
You can exit coLinux, we have things to tweak now.You can then download the attached Squeeze.conf, and put it into your colinux folder, replacing the old. Remember, if you have changed the path for rootfs and swap, you must change them to reflect your current installation.
Squeeze.conf:
Code:
kernel=vmlinux
cobd0="c:\program files\coLinux\rootfs_2gb.img"
cobd1="c:\program files\coLinux\\swap_128mb.img"
cofs0="C:\share"
cobd8=\Device\HarddiskVolume8
root=/dev/cobd0 ro
initrd=initrd.gz
mem=256
eth0=slirp
b) transfer files from Windows to coLinux
We would create a share folder at the root of C:\.
You must have C:\share folder.
- Create a directory in /mnt
Code:
mkdir /mnt/win
- then mount the folder into your coLinux
Code:
mount -t cofs cofs0 /mnt/win
FOLLOW THE ABOVE ONLY FOR GAPPS:
- You must now download the google apps files. The operation is done under Windows:
download Android 4.2.2 ones: http://goo.im/gapps/gapps-jb-20130812-signed.zip and extract all the file into C:\share
This folder must contains the whole gapps (you 'll see folders named: system, META-INF, optional...).
You must directly DELETE 3 files and 1 folder:
file system\app\GooglePlus.apk
file system\app\LatinImeDictionary.apk
file system\lib\libjni_latinime.so
fodler system\tts
If everything is ok, browsing /mnt/win/ from coLinux (not windows)
Code:
ls /mnt/win
should show the share directory content (META-INF,system,optional,...).
FOLLOW THIS ONLY IF ROOT:
- You must now copy su binary to your tablet: download attached files, unzip, copy it to your windows desktop shared folder
Nota: this file is extracted from Koush' superuser APK. This is the x86 su binary. Feel free to replace with newest version if available or if you fear something
FOLLOW THIS IF ROOT & GAPPS
c) access to Android partition
- create a system folder in /mnt
Code:
mkdir /mnt/system
- mount android to system
Code:
mount /dev/cobd8 /mnt/system
- check you are ok with
Code:
ls /mnt/system
You must see app, bin, usr, etc .... folders.
*** at this point, /mnt/system contains ALL your android system. NO MISTAKE ! ***
FOLLOW THIS ONLY IF GAPPS
- part 1: removing files. Browse to /mnt/system/app and CAREFULLY delete the 8 files (some could be missing, don't bother):
Code:
cd /mnt/system/app
rm Provider.apk
rm Provider.odex
rm QuickSearchBox.apk
rm QuickSearchBox.odex
rm SetupWizard.apk
rm SetupWizard.odex
- part2: copy. Copy the files from Windows to Android - it could take up to 2 minutes -
Code:
cp -rp /mnt/win/system/* /mnt/system
- then fix the permissions:
Code:
chmod -R 755 /mnt/system/addon.d
chmod 755 /mnt/system/app/*
sync
At this point, this is over. You can exit from colinux, reboot to Android, and come back to windows uninstalling coLinux, if anything is ok
The whole GAPPS are installed. Enjoy !
FOLLOW THIS ONLY IF ROOT
- copy attached x86 su binary to android
Code:
cp -p /mnt/win/su /mnt/system/bin
- then fix the permissions:
Code:
chmod 755 /mnt/system/bin/su
chmod u+s /mnt/system/bin/su
ln -s /mnt/system/bin/su /mnt/system/xbin/su
sync
At this point, this is over. Reboot, you can now download and install superuser https://f-droid.org/repository/browse/?fdfilter=superuser&fdid=com.koushikdutta.superuser
Your tablet is now rooted. Enjoy !

Know clones (feel free to help):
- Danew i1012 dual boot (strictly identical to Thbk1)
- VOYO A1 (Windows 8 only).
- Cube U100GT (Windows 8 only)
Certainly clones:
- Ramos i10 pro (dual boot)
- Pipo W1 / Work W1 (Windows 8 only)
- ColorFly i106 (Windows 8 only)
- Toshiba WT8-AT01G (Windows 8 only)

Graveen said:
Know clones (feel free to help):
- Danew i1012 dual boot (strictly identical to Thbk1)
- VOYO A1 (Windows 8 only).
- Cube U100GT (Windows 8 only)
Certainly clones:
- Ramos i10 pro (dual boot)
- Pipo W1 / Work W1 (Windows 8 only)
- ColorFly i106 (Windows 8 only)
- Toshiba WT8-AT01G (Windows 8 only)
Click to expand...
Click to collapse
Considering getting a voyo a1 or a pipo w2. But 99% of my interest in windows 8 tablets is running old windows games on them. What's your experience with win 8 and older games for windows? Touchscreen make anything unplayable? Thinking old command and conquer or Warcraft 1-3 etc. With some RPG thrown in.
I hate the idea of being limited to just windows, but I'm hesitant to spend too much on what might not work like I hope.

StridAst said:
Considering getting a voyo a1 or a pipo w2. But 99% of my interest in windows 8 tablets is running old windows games on them. What's your experience with win 8 and older games for windows? Touchscreen make anything unplayable? Thinking old command and conquer or Warcraft 1-3 etc. With some RPG thrown in.
I hate the idea of being limited to just windows, but I'm hesitant to spend too much on what might not work like I hope.
Click to expand...
Click to collapse
Honestly,i installed Steam and played some to test. But, alas, it is not successfull. If you can wire a BT pad, let's say it is ok, but else, generally, the touchpad is not suitable, really.
Of course some point'n clic games should work nicely. But except theses, you 'll be forced to add keyboard/mouse. Or, as i mentionned, a bluetooth gamepad, with some keyboard mapping, such as XPadder, could work fine.

Graveen said:
Honestly,i installed Steam and played some to test. But, alas, it is not successfull. If you can wire a BT pad, let's say it is ok, but else, generally, the touchpad is not suitable, really.
Of course some point'n clic games should work nicely. But except theses, you 'll be forced to add keyboard/mouse. Or, as i mentionned, a bluetooth gamepad, with some keyboard mapping, such as XPadder, could work fine.
Click to expand...
Click to collapse
So basicly, the hardware ran things OK, but the interface sucks, oh well. Probably not worth the headaches of dealing with windows again. I'd imagine it's a real PITA to fix things if it gets a virus.

StridAst said:
So basicly, the hardware ran things OK, but the interface sucks, oh well. Probably not worth the headaches of dealing with windows again. I'd imagine it's a real PITA to fix things if it gets a virus.
Click to expand...
Click to collapse
Like a windows. The 'dock' is allowing light computer use, and Office 2013 home is shipped for free with the tablet. But yeah, Windows legacy is the key when dealing with windows

Hey mate,
I have one of these - http://www.ebay.co.uk/itm/390900023783?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649
are you implying that I should be able to get it to dual boot Windows and Android following your guide?
Thanks
Karl

Hello Karl,
Yes it should be possible if strictly identical.

Increase data space with Link2SD
You can dedicate a part of external SD to increase /data size. Link2SD is ok for this, and will, in the free version, allows you to move APK to external partition.
Your tablet MUST be rooted !
1) ensure you have a FAT32 partition (primary, 1st position)
2) ensure you have an EXT2 or EXT4 partition (primary, 2nd position)
3) install Link2SD https://play.google.com/store/apps/details?id=com.buak.Link2SD
You can now use Link2SD which 'll create links and move your APKs to your new EXT partition.
Personnaly, i have a 32Gb SD with 24Gb FAT + 8Gb EXT4 partition.

Increase data space with Link2SD : Good news !!! You are the Boss. THNK1-10 is available at Carrefour (an another good news)

Time is changing between windows and Android
You can simply set timezone to GMT+0 and disable network time.
On Debian, you set UTC to YES, but need to seek where it takes place in Android.

bu3304 said:
Increase data space with Link2SD : Good news !!! You are the Boss. THNK1-10 is available at Carrefour (an another good news)
Click to expand...
Click to collapse
carrefour or conforama.
thomson carrefour and /danew in conforama.
even saw on internet that MSI is also having this tablet and just sticking there logo on it. atleast looked like this tablet.
---------- Post added at 12:05 AM ---------- Previous post was at 12:01 AM ----------
hum. i think i will go for the new asus transformer book t100 with atom z3775 processor.
i like the battery life of the asus.
but prefer the acer switch 10 in terms of look and the magnetic dock
but yeah choice of 11 hours of battery or 8. makes a difference
and the new 3775 or 3745. cpu

[WinApp][v2.4-Beta][+RemixOS] Android-x86 Installer UEFI Version

Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Description
This Installer will let you install Android x86 on your PC like any other application, no risk to Damage HDD Partitions, Boot Data or User Data. After installation you will got an option at boot to select Windows or Android.
This Installer is currently targets only Windows 8 / UEFI-Enabled Devices​
System Requirements
UEFI-Enabled x86 PC
Secure Boot Disabled
Bitlocker disabled on target drive
Windows 8/8.1/10
.Net Framework 4.5
Android System image with UEFI Support
Screenshot
{
"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"
}
Change log
v2.4
Update Detection of RemixOS image [Use RemixOS ver: B2016012301 or higher]
Fix UEFI Init Fail with Surface Pro devices
v2.3
Add support for RemixOS
v2.2
Fix reading large UEFI entries
Fix using img file from path with spaces
Trial period Removed
Add GPU Options to GRUB Bootlist
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS
v2.0
Initial Version
Features
Install/Uninstall Android directly from Windows
Support UEFI-Enabled devices
Support legacy BIOS devices [not available in Alpha version]
Install to Any FAT32/NTFS partitions
Instructions
Install
Download Android EFI Enabled img file from: [LINK]
Launch the Installer
Select the downloaded IMG file
Select "Data Size" for file which will be used to store downloaded Apps and User Settings
Select the partition which Android will be installed to.
Click Install and wait ... The installation will take about 5 min. or less, it is based on your hard drive speed.
How to Enter Android
Go to Windows power menu and Click on "Restart" while holding shift [Screenshot]
Select "Use a device"
Select "Android-OS"
Now your PC will reboot to Android
Uninstall
Launch the Installer
Select "Cleanup Android"
Under the hood
The installer will verify the system requirements on launch
directory: "<TargetPartition>AndroidOS" will be used for installation
Extract the IMG file
Create user data partition
Install grubx64 to UEFI partition
Install new UEFI boot entry for Android
Downloads:
For UEFI-Enabled PCs: [UEFIInstallerv24-5800.exe]
For Legacy-BIOS PCs: [Old Thread]
Important notes (Read it carefully)
This version for testers only, not for end users
Please don't redistribute this version of the installer
Please please report your device model and if installation was successful or not
Any bug/problem/issue reported shall have installer log (which can be found in your C: ) attached and a screenshot
you can read the log before sending it if you have any privacy concerns
The installer will not allow installation on non-UEFI Devices for now
Verify that you downloaded .IMG file not .ISO file
if you have found a bug inside Android you should contact android-x86 team not to post here
Your feedback is highly appreciated
XDA:DevDB Information
Android-x86 Installer for Windows, Tool/Utility for the Windows 8 General
Contributors
ExtremeGTX
Version Information
Status: Beta
Current Beta Version: V2.4
Beta Release Date: 2016-02-05
Created 2015-10-15
Last Updated 2016-02-13

Looks amazing, gonna try it for sure, thanks for this tool!
EDIT: Tried it (ASUS T100TAM, Windows 10 x86), installation failed unfourtunately. Adding log from installation:
================Installer Info================
Installer Directory:C:\Users\****\AppData\Local\Temp\droidinst_efi
Installer Version:2.0.5761.39882
Secure Boot ... Disabled
Manufacturer: ASUSTeK COMPUTER INC.
Model: T100TAM
Product: T100TAM
BIOS Version: T100TAM.204
Available GPU(s):
GPU: Intel(R) HD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
OS Type: ... fail
==========================================
====Install Started on 18.10.2015 10:52:53====
-ISO File: C:\Downloads\android-x86-4.4-r3.iso
-TargetDrive: C
-UserData: 1000k
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extract ISO
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exex C:\Downloads\android-x86-4.4-r3.iso "kernel" "ramdisk.img" "initrd.img" "system.sfs" -oC:\AndroidOS
-Extract SFS
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS
-Create Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=C:\AndroidOS\data.img ibs=1k count=1000k
-Initialize Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\Android\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Android Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
Folder is not empty.
-UEFI Init ... fail
-Cleaning up Android Directory ... Z:\EFI\Android\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
Click to expand...
Click to collapse

Check the New version
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS

ExtremeGTX said:
Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Click to expand...
Click to collapse
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel

ChrisJ951 said:
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel
Click to expand...
Click to collapse
it seems like bootloader can't access your Disk!
can you please post a screenshot of "Disk Management" :
- Open run and type: diskmgmt.msc then take screenshot like this [LINK]
- OR open start menu and type Disk Management

New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess

spenat said:
New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess
Click to expand...
Click to collapse
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader

ExtremeGTX said:
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader
Click to expand...
Click to collapse
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.

So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.

Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The biggest benefit is (obviously) that you don't need any flash drive for this - everything is done from your tablet's memory (basically a dualboot) and it's very, very easy to do this.

AFAIK, you can install the android x86 to via magic stick, although I haven't try it yet. I'm using it for Ubuntu. Did you use it daily? How about battery life and performance? Can't wait to try
Sent from my Nexus 5 using Tapatalk

Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now

spenat said:
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.
Click to expand...
Click to collapse
Thanks for posting the log.
My only concern with setting GRUB as default bootloader if GRUB has a problem running on the device the user may think that the device is bricked and no longer usable, anyway we will check back on that.
dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
exactly as @spenat told you.
the Advantage of this installer is you will not mess up anythings, no re-partitioning at all or corrupting the current installation of windows. All of the magic just live in <Drive:>\AndroidOS
and if you don't like it you can launch the installer and click on "Cleanup Android" you can check all installation steps in log if you have any concerns.
Thanks
spenat said:
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.
Click to expand...
Click to collapse
spenat said:
Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now
Click to expand...
Click to collapse
Thanks for your clear answers, appreciate your help

installing now. will I be able to change data size later?

dokie80 said:
installing now. will I be able to change data size later?
Click to expand...
Click to collapse
You can only change data size before you actually install the Android. If you wanna change it later, you need to remove Android and install it again with different data size, AFAIK.

working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:

dokie80 said:
working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:
Click to expand...
Click to collapse
Thanks for testing and posting the install log
Answers:
1. Check section "Under the hood" in the first post or check the installer log you have posted, it will give you an idea about the magic
2. This is an old request from a few users to allow reinstall/update android without removing userdata. Till now your workaround is valid, I think you will see message like this one [LINK] at the first boot after upgrade.
3. I 'm not sure right now.
4. here are 2 solutions to access Android:
a Shortcut on Desktop "Reboot to Android"
Set GRUB as default Bootloader, I can't do this right now as the app still in alpha stage and a lot of testing is needed. i don't want to mess up devices with something not ready yet, so currently i just add GRUB to UEFI Boot options but don't make it the default one.
Thanks for your feedback and questions

Just a quick tip to make dual-booting even easier:
Set the "Boot Option #1" in BIOS to Android-OS (instead of Windows Boot Manager), this way it will always boot to GRUB. Just one catch: You will need a keyboard to move in GRUB, or you will always boot to Android But, of course, you can anytime switch back to Windows Boot Manager as default, as long as you can access BIOS
Anyway, just tried this app on my brother's tablet (Lenovo Miix 3 10"), will add installation log ASAP.

[ROM][KERNEL][MOD] Debian 10 for Google Nexus Player (fugu)

This is a guide to install Debian Linux on your Nexus Player
NOTE: This guide is for advanced users
This is NOT VNC nor chroot nor Android X server nor anything else like that, but running Linux natively.​
D I S C L A I M E R
----------------------------------------------------------------------------
Use this at your OWN RISK. Experimental software may harm you, your device and others around you. I cannot be held responsible for any damage done. You have been warned!
Installing Linux will most likely VOID YOUR WARRANTY! (If warranty still applies to a five year old device...)
P R O L O G U E
----------------------------------------------------------------------------
I have adapted the Nexus Player's kernel to meet GNU/Linux, namely Debian 10, requirements so far that it has become quite stable by now.
Since the processor is Intel x86 compliant you can run a regular distribution, receive updates, load software, etc. etc. This makes the Nexus Player virtually a desktop PC.
You can install Debian onto a USB stick and dual boot along with Android OR you may install Debian to the device's internal storage (and speed up things significantly).
H A R D W A R E S U P P O R T
----------------------------------------------------------------------------
What is NOT working:
* Suspend/standby
* Screen off (DPMS off)
What is working:
* Hopefully anything else...
R E Q U I R E M E N T S
----------------------------------------------------------------------------
* Nexus Player (obviously) w/ unlocked bootloader
* USB OTG cable and mirco USB cable
* A USB Hub
* An empty USB stick (I suggest at least 16 GB of storage and 40 MB/s read and 20 MB/s write speed. 8 GB is the minimum requirement though.)
* Input devices (i.e. mouse, keyboard)
* Linux PC (or virtual machine)
* Basic Linux/ROM tinkering knowledge, some time and patience...
Ready?! Let's go!
S T E P 1: Install the Linux boot image
----------------------------------------------------------------------------
a) Unlock your Nexus Player's bootloader (there are guides online in case you don't know how to do that)
b) Reboot to bootloader, attach the Nexus Player to your PC and flash the device specific Linux boot image to the boot partition.
fastboot flash boot fugu_bootimage.img_EXTERNAL
Hint: This will be the only change to your Nexus Player.
Note: You may revert the changes by flashing the stock boot image.
S T E P 2: Prepare USB stick(done on the Linux PC)
----------------------------------------------------------------------------
a) Format the partition on the USB stick with the ext4 file system.
b) Manually mount the partition to e.g. /mnt
c) Download the attached root file system creator, untar it and change to the directory.
d) Create the rootfs (need to be root): ./fugu_rootfs_creator /mnt
Note: The process sometimes fail, you might have to try more than once.
Note: This will take a long time. To speed things up, you may create the rootfs into a disk image on your HDD and afterwards write the image to the USB stick.
d) Connect the USB stick to the Nexus Player/hub.
e) That's it, if you now boot your Nexus Player, it will actually boot into Linux.
S T E P 3 (optional): Install Linux to the internal storage
----------------------------------------------------------------------------
If you are keen enough to purge Android completely, you may read on:
a) Boot into Linux from the USB stick.
b) IMPORTANT: Make a backup (preferably a dd copy of the entire internal storage). Since you alter the partition table in the next step, this is very important in case you want to go back to Android
c) Use gparted to delete the following partitions: cache, system, data
d) Use the freed storage to create one "large" ext4 partition.
e) Flash the file system image to the new partition.
g) Flash the boot new image to the boot partition: fastboot flash boot fugu_bootimage.img_INTERNAL
h) Reboot.
P O S T I N S T A L L A T I O N A N D I S S U E S
----------------------------------------------------------------------------
a) Compositing
On fugu, Mate's window manager "Marco" is NOT hw accelerated. Compositing is slow. When watching Videos or browsing the internet, you may disable compositing (use mate-tweak) to increase performance.
If you need hw accelerated compositing you may use kwin-x11 but this takes up 1GB of disk space...
b) Chromium
Chromium is accelerated with X11/EGL, but buffer management does not work properly. When resizing the window you may need to restart Chromium, because the buffer allocation may fail.
Chromium does have support for WebGL.
c) Firefox
Firefox is not hw accelerated but still gives you decent performance when browsing or watching movies (tested Youtube FullHD and Netflix, works fine).
However when using WebGL, Chromium is much faster.
d) VLC media player
Video playback is hw acceleration is not supported. To achieve decent performance anyways do as follows:
I) Choose Tools --> Preferences --> Video
II) As "Output" choose "X11 video output (XCB)" and for "Fullscreen Video Device" select "hwcomposer" for best performance.
Q & A
----------------------------------------------------------------------------
Q: There is no text console shown during boot process, how can I get it?
A: Unfortunately the Nexus Player's bootloader appends "console=none" to the kernel command line, effectively disabling the console. If you want to have a console you need to rebuild the kernel and enable a built-in command line which cannot be overridden by the bootloader.
Q: Does graphics acceleration work?
A: Yes, OpenGL ES does work, however a lot of programs do depend on desktop OpenGL which is NOT supported. Graphics acceleration is achieved through libhybris which makes it possible to use Android graphics drivers in GNU/Linux.
Q: What is graphics performance like?
A: Depends. When a program supports OpenGL ES, you get decent performance (e.g. Kwin-X11 window manager, Chromium). Performance is sufficient to watch FullHD movies in Firefox or with VLC or browse the internet. Chromium supports accelerated WebGL.
Q: What is system performance like?
A: Depends. Bottle neck of system performance is the speed of the storage used. Using the internal storage gives huge speed improvements vs. an external USB storage (Nexus Player only has USB 2.0, so max ~ 30 MB/s). With internal storage simple tasks like file management, office applications etc. work fine. RAM is limited tough.
Q: Why? Why would you wanna turn your AndroidTV into a subpar desktop PC? Tell me why, I ask of thee!
A: Well... Linux on the Nexus Player is actually a by-product. I develop this for the Dell Venue 7040 which is basically - silicon wise - the same device. But the Nexus Player has the more recent software. So I did this to run Linux on the Dell. But I thought, hey, maybe someone is in to it...
S O U R C E C O D E
----------------------------------------------------------------------------
* Halium - https://github.com/halium
* Libhybris - https://github.com/NotKit/ and https://github.com/libhybris/
* Debian - https://www.debian.org/
* Kernel - https://android.googlesource.com/kernel/x86_64/+/refs/heads/android-x86_64-fugu-3.10-nougat-hwbinder , https://github.com/fcipaq/android_kernel_asus_fugu
* Lineage OS - https://github.com/lineageos
C R E D I T S
----------------------------------------------------------------------------
Special thanks goes to the Halium team, especially JBB and NotKit
And to Hybris, Debian and the LOS team
ROM OS Version: Debian 10
ROM Kernel: Linux 3.10.20
ROM Firmware Required: 8.0.0 (OPR2.170623.027, Nov 2017)
Graphics drivers based On: Lineage OS 14.1
Version Information
Status: Stable
Created 2020-01-30
Last Updated 2020-02-08

Updates:
2020-04-06
* Preserve temporary installation files by moving them from /tmp to /install
* Include wifi config file
2020-02-08
* Delete some unnecessary files from rootfs
* Fix issue with udev rule (which might prevent graphics from working properly)

A small demo on Youtube...

Is it possible to boot something like Batocera linux or Recalbox so we can use it as a retro console?

Well... that is an interesting idea! In theory you may run any Linux distro that still supports kernel 3.10. And maybe that applies to the two afore mentioned distro. I mean some of the Odroids (which might be supported) have a quite similar setup in terms of the drivers basis (Android drivers running via libhybris).
On the other hand this won't be plug and play or even installing, but one would rather have to put quite some work into it... If you are willing to get your hands dirty, I will try to offer some support.

PS: Batocera Linux seems to support Odroid XU4 which has OpenGL ES support (just like the Nexus Player), so there is a change that this could work.

trying to finish step 2 and get the following:
debootstrap
/home/bonnie/Downloads/fugu_mate_desktop/fugu_rootfs_creator: line 44: debootstrap: command not found
cp: cannot create regular file '/home/bonnie/Downloads/etc/network/': No such file or directory
cp: cannot create regular file '/home/bonnie/Downloads/etc/': Not a directory
cp: cannot stat 'rootfs/*': No such file or directory
Chroot...
mount: sys/: mount point does not exist.
mount: dev/: mount point does not exist.
mount: proc/: mount point does not exist.
chroot: failed to run command ‘bin/bash’: No such file or directory
umount: sys/: no mount point specified.
umount: dev/: no mount point specified.
umount: proc/: no mount point specified.
Exiting chroot
Done.

Try
sudo apt install deboostrap
Nephilim3883 said:
trying to finish step 2 and get the following:
debootstrap
/home/bonnie/Downloads/fugu_mate_desktop/fugu_rootfs_creator: line 44: debootstrap: command not found
cp: cannot create regular file '/home/bonnie/Downloads/etc/network/': No such file or directory
cp: cannot create regular file '/home/bonnie/Downloads/etc/': Not a directory
cp: cannot stat 'rootfs/*': No such file or directory
Chroot...
mount: sys/: mount point does not exist.
mount: dev/: mount point does not exist.
mount: proc/: mount point does not exist.
chroot: failed to run command ‘bin/bash’: No such file or directory
umount: sys/: no mount point specified.
umount: dev/: no mount point specified.
umount: proc/: no mount point specified.
Exiting chroot
Done.
Click to expand...
Click to collapse

That worked. But now the issue is during boot I get:
Waiting on root device /dev/sda1
I’ve tried using a USB flash drive and an external HDD. Wondering my maybe the OTG cable is crappy.
lunigma said:
Try
sudo apt install deboostrap
Click to expand...
Click to collapse

Run a file system check on your flash drive, it might be corrupted. A bad OTG cable could also be the culprit, try it on a phone with micro USB.
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
Has anyone gotten the WiFi to work?

It was definitely the OTG hub being a piece of junk. I’m reinstalling everything now and will try again when it’s done.
I did find out if you have installed everything to usb once already then all of the files and folders have already been downloaded to the system and you have to manually delete everything in /mnt and /media (not sure if you HAVE to delete everything in /media but that’s what I did).
Also, his video mentioned WiFi works. Not sure how to get it working if it doesn’t.
lunigma said:
Run a file system check on your flash drive, it might be corrupted. A bad OTG cable could also be the culprit, try it on a phone with micro USB.
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
Has anyone gotten the WiFi to work?
Click to expand...
Click to collapse

This is as far as I have gotten after getting a new OTG hub and rerunning the rootfs script for the USB flash drive:
{
"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"
}

Nephilim3883 said:
This is as far as I have gotten after getting a new OTG hub and rerunning the rootfs script for the USB flash drive:
Click to expand...
Click to collapse
Sorry for my delayed response. This usually happens if you got a corrupted root file system. That's why you get the
Code:
"devtmpfs: error mounting -2"
message. Good news is: your storage is properly detected and mounted, so most likely no hardware incompatibilities.
When creating to the file system be sure to a) either write it directly to the SD card (i.e. mount the SD card to e.g. /mnt) b) or first write to disk IMAGE (not directly to a directory). If you write the rootfs to a directory and then copy the directory over to a SD card might end up with a broken root file system.

Nephilim3883 said:
Also, his video mentioned WiFi works. Not sure how to get it working if it doesn’t.
Click to expand...
Click to collapse
Wifi should work out of the box.
Could you please get be the output of:
Code:
sudo ifconfig
and
Code:
dmesg | grep -i dhd

Could you please provide the method for writing to disk image? I am using Lubuntu to run the rootfs script. Thanks
lunigma said:
Run a file system check on your flash drive, it might be corrupted. A bad OTG cable could also be the culprit, try it on a phone with micro USB.
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
Has anyone gotten the WiFi to work?
Click to expand...
Click to collapse
fcipaq said:
Sorry for my delayed response. This usually happens if you got a corrupted root file system. That's why you get the
Code:
"devtmpfs: error mounting -2"
message. Good news is: your storage is properly detected and mounted, so most likely no hardware incompatibilities.
When creating to the file system be sure to a) either write it directly to the SD card (i.e. mount the SD card to e.g. /mnt) b) or first write to disk IMAGE (not directly to a directory). If you write the rootfs to a directory and then copy the directory over to a SD card might end up with a broken root file system.
Click to expand...
Click to collapse

Nephilim3883 said:
Could you please provide the method for writing to disk image? I am using Lubuntu to run the rootfs script. Thanks
Click to expand...
Click to collapse
That would be (executed from the rootfs creator's directory):
Code:
sudo su
mount /dev/sdX1 /mnt
./fugu_rootfs_creator /mnt YourUserName YourPassword
umount /mnt
Replace sdX1 with the proper device name and replace YourUsername and YourPassword with your desired user name and password respectively.
Btw: What version of Lubuntu are you using, 18.04? (because I tested with Ubuntu 18.04)

It is the latest version, 19.10
I will try create the image instead and see how it goes. Thank you for providing the information and for your work on this project.
fcipaq said:
That would be (executed from the rootfs creator's directory):
Code:
sudo su
mount /dev/sdX1 /mnt
./fugu_rootfs_creator /mnt YourUserName YourPassword
umount /mnt
Replace sdX1 with the proper device name and replace YourUsername and YourPassword with your desired user name and password respectively.
Btw: What version of Lubuntu are you using, 18.04? (because I tested with Ubuntu 18.04)
Click to expand...
Click to collapse

I got further this time. It acts as though it wants to go into Debian but I just get stuck on a blinking cursor using the EXTERNAL WCONSOLE boot image. If I use the EXTERNAL NOCONSOLE image it just stays on a white screen.
fcipaq said:
That would be (executed from the rootfs creator's directory):
Code:
sudo su
mount /dev/sdX1 /mnt
./fugu_rootfs_creator /mnt YourUserName YourPassword
umount /mnt
Replace sdX1 with the proper device name and replace YourUsername and YourPassword with your desired user name and password respectively.
Btw: What version of Lubuntu are you using, 18.04? (because I tested with Ubuntu 18.04)
Click to expand...
Click to collapse
Nephilim3883 said:
It is the latest version, 19.10
I will try create the image instead and see how it goes. Thank you for providing the information and for your work on this project.
Click to expand...
Click to collapse

Hm, odd... Maybe you could start over and upload the installation log.
Mark all the output of the installation of the Lubuntu console and copy and paste it to https://paste.ubuntu.com/
Just make sure your console has a line buffer large enough, because the log will be quite long.

FYI- I can get into tty1 by Alt+F1 which lets me login to the terminal. After that I have no idea what to do. I am thinking maybe there’s an issue with Xorg.conf
I forgot what command I used but I get: No Screens Found (EE)
fcipaq said:
Hm, odd... Maybe you could start over and upload the installation log.
Mark all the output of the installation of the Lubuntu console and copy and paste it to https://paste.ubuntu.com/
Just make sure your console has a line buffer large enough, because the log will be quite long.
Click to expand...
Click to collapse