Unable to boot on HTC One S (htc-ville)

I started porting pmOS to htc-ville and compiling and flashing worked without fundamental problems. But the kernel is not able to boot up because it isn't finding the ram disk. The ramdisk offset was checked multiple times and matches twrp, cm-13.0 and los-14.1.

repo: https://github.com/escoand/pmaports/tree/htc-ville/device/linux-htc-ville

log: htc-ville.log

changed the description

By escoand on 2019-01-22T11:10:31

I assume that you are referring to this part:

[    1.887868] Warning: unable to open an initial console.
[    1.888081] RAMDISK: Couldn't find valid RAM disk image starting at 0.
[    1.888966] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6

How about unpacking the boot.img that pmbootstrap generated (get a convenient symlink with pmbootstrap export) and comparing it with an unpacked TWRP/CyanogenMod/LineageOS boot.img file?

If that doesn't help, I would try to boot a TWRP initramfs with a postmarketOS kernel and vice versa (TWRP kernel + postmarketOS initramfs) to narrow down the issue.

By Oliver Smith on 2019-01-24T06:41:31

Hi, thanks in advance. I'll give it a try asap.

I've already tried booting with TWRP kernel and pmOS initramfs. This seemed to boot (no restart) but I was unable to connect in any way.

By escoand on 2019-01-24T13:01:31

Yeah with the twrp kernel and initfs-hook.sh from htc-bravo I was able to boot and telnet into the initfs. So, obviously this is a kernel problem.

By escoand on 2019-01-24T22:09:22

I'm not an expert of htc devices, but couldn't you be interested into !175 (merged)? If they are half as thrifty as sony, just about everything but phone specific dts/camera and such should differ.

By mirh on 2019-01-25T12:59:49

mentioned in merge request !175 (merged)

By escoand on 2019-01-25T13:26:12

The complained issue is fixed now, so the next steps will go towards !177 (merged).

By escoand on 2019-01-26T15:07:01

closed

By escoand on 2019-01-26T15:07:01