[HELP NEEDED] ROM Development for Duo - Microsoft Surface Duo Guides, News, & Discussion

Hello Everyone!
I have gone down the rabbit hole in developing ROMs for the Surface Duo. Since we have root, and the ability to unlock the bootloader, I wanted to see what I could do for ROM development. Unfortunately, I've ran into two problems: creating a device tree for the Surface Duo and unzipping the system image.
First, the device tree for OS builds was not released.
Second, the system image is formatted as an EXT2 file, NOT an EXT4 file, and not as an Android system file that sim2img desires.
I found the system image through two methods:
Finding the payload.bin OTA file and extracting the images there.
Rooting the phone, copying the super.img, and extracting the images.
In both situations, the filetype of the system image is Linux rev 1.0 ext2 image. All the guides I found say the image should be an EXT4 file type.
This is for both A and B Partitions. I can't mount ext2 images onto my linux OS (I'm on Kali OS) via mount loop.
Code:
wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
If anyone can help me out, that would be great!

JengaMasterG said:
Hello Everyone!
I have gone down the rabbit hole in developing ROMs for the Surface Duo. Since we have root, and the ability to unlock the bootloader, I wanted to see what I could do for ROM development. Unfortunately, I've ran into two problems: creating a device tree for the Surface Duo and unzipping the system image.
First, the device tree for OS builds was not released.
Second, the system image is formatted as an EXT2 file, NOT an EXT4 file, and not as an Android system file that sim2img desires.
I found the system image through two methods:
Finding the payload.bin OTA file and extracting the images there.
Rooting the phone, copying the super.img, and extracting the images.
In both situations, the filetype of the system image is Linux rev 1.0 ext2 image. All the guides I found say the image should be an EXT4 file type.
This is for both A and B Partitions. I can't mount ext2 images onto my linux OS (I'm on Kali OS) via mount loop.
Code:
wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
If anyone can help me out, that would be great!
Click to expand...
Click to collapse
If my memory serves me right it should be mount -t ext2 <blah>

pibleck said:
If my memory serves me right it should be mount -t ext2 <blah>
Click to expand...
Click to collapse
Sadly, I've tried that. I get the same loop error as posted above.

JengaMasterG said:
大家好!
我已经在为Surface Duo开发ROM时陷入了兔子洞。由于我们有root,并且能够解锁引导加载程序,我想看看我能为ROM开发做些什么。不幸的是,我遇到了两个问题:为Surface Duo创建设备树和解压缩系统映像。
首先,未发布操作系统版本的设备树。
其次,系统映像被格式化为 EXT2 文件,而不是 EXT4 文件,也不是 sim2img 所需的 Android 系统文件。
我通过两种方法找到了系统映像:
查找有效负载.bin OTA 文件并在那里提取图像。
生根手机,复制super.img,然后提取图像。
在这两种情况下,系统映像的文件类型都是 Linux rev 1.0 ext2 映像。我找到的所有指南都说图像应该是EXT4文件类型。
这适用于 A 和 B 分区。我无法通过挂载循环将 ext2 映像挂载到我的 linux 操作系统(我在 Kali OS 上)。我无法将 ext2 映像挂载到我的 linux 操作系统上。
Code:
错误的 fs 类型、错误的选项、/dev/loop0 上的错误超级块、缺少代码页或帮助程序或其他错误。[/代码]
如果有人能帮助我,那就太好了!
[/QUOTE]
https://surface.downloads.prss.microsoft.com/dbazure/ota_b1-11-customer_gen_2022.517.57.zip?t=5bc2c2bd-751e-4bf4-8e32-3dcce783f7e7&e=1658523817&h=2253dc7d607ba51f842aa6e1e761a0646f372348b15d6cea075105797ed6682a
Click to expand...
Click to collapse

可以下载的链接。

Surface 恢复映像下载 - Microsoft 支持
support.microsoft.com
JengaMasterG said:
Hello Everyone!
I have gone down the rabbit hole in developing ROMs for the Surface Duo. Since we have root, and the ability to unlock the bootloader, I wanted to see what I could do for ROM development. Unfortunately, I've ran into two problems: creating a device tree for the Surface Duo and unzipping the system image.
First, the device tree for OS builds was not released.
Second, the system image is formatted as an EXT2 file, NOT an EXT4 file, and not as an Android system file that sim2img desires.
I found the system image through two methods:
Finding the payload.bin OTA file and extracting the images there.
Rooting the phone, copying the super.img, and extracting the images.
In both situations, the filetype of the system image is Linux rev 1.0 ext2 image. All the guides I found say the image should be an EXT4 file type.
This is for both A and B Partitions. I can't mount ext2 images onto my linux OS (I'm on Kali OS) via mount loop.
Code:
wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.
If anyone can help me out, that would be great!
Click to expand...
Click to collapse
Surface 恢复映像下载 - Microsoft 支持
support.microsoft.com

Related

[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 -

[Q] Linux on TAb 3 7.0

Hello . every one :laugh:. May i ask support for running linux natively on tab 3 7.0.?
Currently i could run Kali ,Ubuntu and Debian in my tablet,,, but only in chroot method , another is i am also able to install the image file (kali.img) in the 2nd partition of my ext sdcard to give it more space,,,, .
The only method that i couldnt make is to run it natively on this tab,,,, I hope there is solution to this ,,,,
How did you get the chroot method to work? I can't get it to
Sent from my 831C using XDA Free mobile app
reinaldistic said:
How did you get the chroot method to work? I can't get it to
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
just download the complete linux installer ,allow superuser permission
then go to /data/data/com.zpwebsites.linuxonandroid/files
you will see a bootscript.sh file .Edit it using a text editor you prefered and find this line
"mount -t ext2 /dev/block/loop255 /data/local/mnt"
and edit it as
"mount -t ext4 /dev/block/loop255 /data/local/mnt"
save the file. and boot linux now via complete linux installer.
You must have terminal emulator and vnc (if you want to see the GUI).
:good:
stuff to DO
anvil_10 said:
Hello . every one :laugh:. May i ask support for running linux natively on tab 3 7.0.?
Currently i could run Kali ,Ubuntu and Debian in my tablet,,, but only in chroot method , another is i am also able to install the image file (kali.img) in the 2nd partition of my ext sdcard to give it more space,,,, .
The only method that i couldnt make is to run it natively on this tab,,,, I hope there is solution to this ,,,,
Click to expand...
Click to collapse
anvil,
working on p5210 towards this end.
you need
1 an arm-linux distro set to /boot /root and/or /system and /home on seperate partitions and then an .img of those partitions
to correspond to the limitations of your devices mmcblk setup.
2 rebuild your kernel to work with the above - mountpoints dev etc.
3 put up with android for a while because figuring out the above is going to take a WHILE.
if i figure out anything i will post.
m
an afterthought- most of it's already here in a lesser form i think it's mostly
unhooking from one userspace setup into another.
moonbutt74 said:
anvil,
working on p5210 towards this end.
you need
1 an arm-linux distro set to /boot /root and/or /system and /home on seperate partitions and then an .img of those partitions
to correspond to the limitations of your devices mmcblk setup.
2 rebuild your kernel to work with the above - mountpoints dev etc.
3 put up with android for a while because figuring out the above is going to take a WHILE.
if i figure out anything i will post.
m
an afterthought- most of it's already here in a lesser form i think it's mostly
unhooking from one userspace setup into another.
Click to expand...
Click to collapse
yeah i saw many post on other forum your procedure, but unfortunately i dont have any idea how to do it, like making the custom kernel to boot the linux distro instead of android,
init process and initramfs
anvil,
i was reading on another site that the linux kernel since 2.6 [i think] has a default behaviour of searching
for an init process in alternate locations when it can't find the first one, there's also an option
during configuration that allows you to specify an specific location of/for the ramdisk.
meaning if i understand it correctly, the kernel itself is bound to your boot/kernel mmcblk
by the bootloader BUT you could locate your init/ramdisk "off-world" by setting a different / location in kernel cmdline
you can also specify support for different compression methods for initramfs/initrd but i'm not sure if that actually builds in
or if you need a module [*.ko].
m
kali linux
How to get kali linux on tab 3 7.0?? Plz tell me . Tell what all things needed and how to??

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

[SOLVED] Missing proprietary blobs on m7

I'm currently running a home build of the 13.0 branch on my HTC One m7, and I'm now trying to build 14.1 for it. When extracting the proprietary blobs, extract-files.sh reports that it can't find the following files:
Code:
/system/etc/firmware/widevine.b00
/system/etc/firmware/widevine.b01
/system/etc/firmware/widevine.b02
/system/etc/firmware/widevine.b03
/system/etc/firmware/widevine.mdt
/system/vendor/lib/libuiblur.so
A quick ls /system/etc/firmware as root from the terminal on my phone reveals that, indeed, there are no files named "widevine.*" in that directory. I also do not have libuiblur.so.
If I stubbornly continue with brunch anyway, the build fails immediately because those files are missing. I figure there must be some way to obtain those files without flashing an existing 14.1 build, and indeed it looks like extract-files.sh is capable of grabbing them from an expanded ROM, so I downloaded and unpacked the latest official nightly. I figure system.new.dat is the system image, but I'm unable to mount it; dmesg reports
Code:
EXT4-fs (loop0): bad geometry: block count 475135 exceeds size of device (168078 blocks)
So basically, I'm still more or less at a loss on how to get those proprietary blobs, bar the overkill solution of flashing an existing build. Any help would be greatly appreciated!
Thanks in advance.
EDIT: after some more digging, I discovered that the system image is not something you can just mount right away; instead you can use sdat2img to convert it into a proper disk image that can be mounted. extract-files.sh can then grab the files from the mount point (note that you have to name the mount point 'system' and pass its parent directory to the script).
I wonder what you end up doing to fix it and if you ended using CM13 blobs for 14.1? Your answer will be appreciated to test some things in order to restart official support.

Bliss Android x86 OS won't boot from the hard drive

Hello all,
I love Bliss OS. Unfortunately, I can't get Android-x86 to boot from my X64 machine. I've researched and tried a number of options but nothing seems to work. I installed it on my single NTFS drive in my laptop busing the Androidx86-Installv26.0003 executable. All seem to go fine. However, when I select the Android entry in UEFI, I get a permanent and repeating "Detecting Android ......" output. Here is some info which may help with troubleshooting.
1. Android in installed on my C:\ drive in a folder called "AndroidOS". The size of the folder is 60.7 GB and holds the following files ...
android.boot - 16 B
data.img - 60.1 GB
initrd.img - 1.3 MB
kernel - 6.4 MB
ramdisk.img - 1.7 MB
system.sfs - 690 MB
2. The EFI entry for AndroidOS in my system partition is ....
Description:Android-OS
GPT partition GUID:{0001208F-8310-EE75-9BD4-D73B1E410200}
Partition number:2
Partition starting sector:999804928
Partition ending sector:1000214527
File path:\EFI\boot\grubx64.efi
3. The cfg file in EFI has the syntax shown in my picture attachment.
I know I'm missing something small or an error in syntax, please review and offer any suggestions you might have.
Thank you in advance
try to make sure your bios has secure boot and bitlocker disabled. if so, try a build using a different kernel
I have the same problem.
sbaloch said:
Hello all,
I love Bliss OS. Unfortunately, I can't get Android-x86 to boot from my X64 machine. I've researched and tried a number of options but nothing seems to work. I installed it on my single NTFS drive in my laptop busing the Androidx86-Installv26.0003 executable. All seem to go fine. However, when I select the Android entry in UEFI, I get a permanent and repeating "Detecting Android ......" output. Here is some info which may help with troubleshooting.
1. Android in installed on my C:\ drive in a folder called "AndroidOS". The size of the folder is 60.7 GB and holds the following files ...
android.boot - 16 B
data.img - 60.1 GB
initrd.img - 1.3 MB
kernel - 6.4 MB
ramdisk.img - 1.7 MB
system.sfs - 690 MB
2. The EFI entry for AndroidOS in my system partition is ....
Description:Android-OS
GPT partition GUID:{0001208F-8310-EE75-9BD4-D73B1E410200}
Partition number:2
Partition starting sector:999804928
Partition ending sector:1000214527
File path:\EFI\boot\grubx64.efi
3. The cfg file in EFI has the syntax shown in my picture attachment.
I know I'm missing something small or an error in syntax, please review and offer any suggestions you might have.
Thank you in advance
Click to expand...
Click to collapse
@electrikjesus is he missing androidboot.hardware=android_x86_64
??
ElfinJNoty said:
@electrikjesus is he missing androidboot.hardware=android_x86_64
??
Click to expand...
Click to collapse
Yes he is missing that
i same problem
how to fix this problem
please help me,,,

Categories

Resources