Hello,
I'm owning a Acer Iconia A200 and I found a Version of Ubuntu Touch, that was ported to the Iconia A500 (the A200 and the A500 are similar) so I downloaded it and tried to flash it. After some testing, i found out, how i have to modify the .zip file to flash it on my tablet. When I booted into System, the was no output except of the bootloader (acer logo). So I got the sourcecode of the native linux kernel for a500 and started compiling and added the zImage to the boot.img of the .zip file. After I flashed this .zip, i got a output of Linux kernel. The System still doesn't boot, because it cant mount the root partition. Does anybody have an Idea, why?
Native Linux Kernel:
http://forum.xda-developers.com/showthread.php?t=1158260
ubuntu touch for the a500:
http://forum.xda-developers.com/showthread.php?p=38428344#post38428344
Thanks in Advance
EDIT:
I've watched the kernel output.
It says something about
[7.50705] fs_mgr: cannot mount filesystem on /dev/block/mmcblk03 at /system
the folowing errors are resulting of that (accessing files at /system)
Related
I want to install a linux distribution on the newly rooted Archos 101 xs.
Howerver, it needs a kernel that supports loop device.
Apparently, the kernel of the 101 xs does not.
I'm stuck with the error:
Error: Unable to mount the loop device!
Do you know a method to support loop device on this tablet (keeping the root) or to install a linux distribution on it?
cajl said:
I want to install a linux distribution on the newly rooted Archos 101 xs.
Howerver, it needs a kernel that supports loop device.
Apparently, the kernel of the 101 xs does not.
I'm stuck with the error:
Error: Unable to mount the loop device!
Do you know a method to support loop device on this tablet (keeping the root) or to install a linux distribution on it?
Click to expand...
Click to collapse
I think, like for the previous generations, you won't get a distro running, the same way that other Android devices do (loopback device - linux mounted in Android). It'll have to be a seperate ROM, running seperately.
Has progressed to this point one. There is already a Linux with dual boot on the 101xs?
I need help I saw this bloghttp://bcmon.blogspot.com/2012/10/new-firmware-for-bcm4329.html
And I was wondering how do I get this to work, I downloaded the file they said to download (in attachments). I don't know what to do with it. Thanks for reading.
Most likely its to flash in recovery (only if rooted). HOWEVER, unzip it first and check to make sure theres an "updater-script" file in there somewhere
Those files are used to patch the Linux Kernel when you're booted into the Backtrack 5 mobile ARM virtual enviroment.
The changes are not done to the ROM on the phone but Linux image on the SD card.
The patch has an install script run setup.sh from the directory in a terminal in bt5.
Then reboot and modprobe the new wireless module.
Hi all,
I successfully installed MultiROM on my Nexus 7 (2013), and I can boot CyanogenMod.
Therefore, I followed the excellent article "Multi-Booting the Nexus 7 Tablet" that was published in the Linux Journal:
http://www.linuxjournal.com/content/multi-booting-nexus-7-tablet?page=0,0
Unfortunately, booting Ubuntu Touch does not work. The error message is:
"Error. Kexec-hardboot support required to boot this ROM. Use kernel with kexec-hardboot support."
However, for the installation I chose a patched kernel that includes the kexec-hardboot patch as described here:
http://forum.xda-developers.com/showthread.php?t=2457063
The link contains the following advice:
Installing MultiROM
"Now that your bootloader is unlocked, you can proceed to the trickiest part of this process—installing MultiROM. Grab a copy of it from the XDA-Developers MultiROM thread (the link is in the Resources section of this article; currently the filename is multirom_v10_n7-signed.zip). You'll also need to get the modified TWRP install file (TWRP_multirom_n7_20130404.img) and a patched kernel (kernel_kexec_422.zip). Rename the TWRP install file to recovery.img, then hook your tablet back up to your computer, and place these files in the root of its filesystem (keep the .zip files zipped—don't unzip them). "
This is what I did, I used:
kernel_kexec_flo_443.zip
and
multirom-20140511-v24-flo.zip
Any ideas how to get Ubuntu Touch running?
Hi there! I'm trying to build CM-12 for GT-I8160 based on TeamCanjica's CM-11. Actually, it has been compiled successfully with some hacks (I skipped imgdiff). But it bricked my phone after I flashed it via CWM. :crying:
I've unbricked my phone by flashing my backup of stock boot partition (mmcblk0p15) to "Kernel" partition via Heimdall. Then, my phone showed CM boot animation for a long time. (bootloop I think, maybe because of stock boot partition isn't compatible with it). And I use stock firmware for now.
I found that type of the boot partition (mmcblk0p15) of the stock differ with boot.img I've built.
Code:
$ file mmcblk0p15-boot (my backup of stock boot partition)
mmcblk0p15-boot: Linux kernel ARM boot executable zImage (little-endian)
$ file boot.img (boot.img I've extracted from cm-12-20141217-UNOFFICIAL-codina.zip)
boot.img: Android bootimg, kernel (0x40008000), ramdisk (0x41000000), page size: 4096
So, what are "Linux kernel ARM boot executable zImage" and "Android bootimg"? Where is the root partition (ramdisk) stored?
Is it okay to skip imgdiff? I think imgdiff is just for creation of OTA package. Am I correct?
I also found boot.img in out/target/product/codina (not in the zip file) which type is Linux kernel ARM boot executable zImage.
Is it the correct boot.img? I found that the content of that file is same with kernel file I found in the same folder. I'm afraid that the ramdisk is not included in it.
Sorry for my English n thank you very much.
Oh. All people wants to have cm12, but still 0 replies here.
I'm sorry, I can't help in this too... /
S.AMU said:
Oh. All people wants to have cm12, but still 0 replies here.
I'm sorry, I can't help in this too... /
Click to expand...
Click to collapse
Hi! It's okay, I've flashed out/target/product/codina/boot.img + gapps. It booted to CM-12 , freezed at the welcome screen n refused to boot again after I force-rebooted it :crying:. Unfortunately, ADB & recovery didn't work, so I didn't know much why it got freezed. Maybe I have to figure out how to compile a nice kernel with working ADB & recovery. Hahaha...
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