Join GitHub today
HTC Wildfire status report #1203
I made some initial efforts to port HTC Wildfire (aka as Buzz) and would like to document it (not ready for a PR as booting is not working): https://github.com/feinerer/pmbootstrap/commit/a966d8472daeded6b583a1990903b5841d20ecda
Kernel is from the
There is also the LineageOS Device repository for HTC Buzz but I could not extract relevant information out of it.
Boot image offsets
I tried to use
Flashing the kernel and system image do not work at the moment (
Modify boot image
I also tried to modify an existing working CyanogenMod boot image as described here: #99 (comment)
Increasing the bootsize was necessary as the pmOS initramfs is huge compared to the original one (i.e., more than 1 MB difference). Using this new boot image shows the the same symptoms as described above.
Any ideas or pointer are highly appreciated. Thank you!
Welcome to postmarketOS and thanks for all the work you have put into both porting the device and for the detailed write-up here!
What happens, when you try to run the known working kernel with the postmarketOS initramfs, does that at least give you a network device?
I merged a CyanogenMod 7.2 kernel with the postmarketOS initramfs as follows:
Now the device is not stuck any more but reboots after a few seconds (and then boots into the installed Android).
No (never so far for all investigated combinations).
Maybe another interesting data point: Based on http://tjworld.net/wiki/Android/HTC/Vision/HackingNotes I managed to set up serial-over-USB which shows some boot messages from
Some more ideas:
Yes, that works fine.
IMHO, there are not many alternatives left as https://github.com/arco/htc-kernel-msm7225 seems the be the only useful kernel source. There are several forks (https://github.com/arco/htc-kernel-msm7225/network/members) but these are more or less the same codebase. For completeness, I tried to build https://github.com/ErwinP/htc-kernel-msm7225 but it makes no difference.
Just to exclude all edge cases I wanted to mention the two following warnings (with
Thanks for reporting those, but these messages appear with all other kernels as well, so they should not cause any problems.
Yes, it really sounds like the kernel is broken.
If I understand this right, then you should get some useful output, when you flash one of the
My guess is, that by following this approach
Thanks for collecting all the data so far, this is very useful!
The output of
I tried a different kernel (https://github.com/kylon/Buzz-kernel) which seems to be similar/identical to the kernel from an official HTC Froyo image: no success, same behaviour. I wrote an init hook for blinking the green LED; although installed it does not work. The same script in a CyanogenMod works and the green LED blinks (in a loop).
I am going to close this issue soon. Guess I am out of luck; I have no further ideas for this device.
Sure. Stock CM 7.2
The boot log is identical to the one posted in #1203 (comment) (the
Unfortunately I am not able to test the two combinations:
as the generated boot images are too big for flashing (the pmOS initramfs is about 1 MB whereas the CM initramfs is just about 150 KB). The observed limit for the
Unfortunately I'm also out of ideas for now.
@drebrez: when you have time, any clue?
@feinerer: Anyhow, you have provided lots of useful data points here, and it wouldn't be the first time that someone started a port and another person came later and finished it based on that initial work. So we might see a port eventually
I think I have found out why the device does not (and cannot) boot:
So it looks like due to the lack of a matching architecture (in Alpine and pmOS) this device cannot be supported.
Oh, that sounds logical.
The only way to support that device would be bootstrapping a new architecture on Alpine. That is possible (run the bootstrap script from Alpine's aports folder, then compile all packages from scratch), but not feasible for us at this point, maybe this makes sense in the far future.
Thanks for reporting back and all the effort you have put into this port!
Just in case you want to try out postmarketOS on another device, but don't have one available, it could be possible that someone sends you their device.
Just for the records, hoping nobody is bothered by advertising of other free software, I think Arch/Debian/Slackware should all still retain support for armel (not sure if soft or softfp though).
Then from there, I guess like if one wants to specifically tinker with this phone (say, for mainlining), everything should still be doable.