search

maemo-leste / bugtracker

Issue tracking repository
63 stars 3 forks source link

bionic: failed flash boot.img #713

Open carlosgonz0 opened 1 year ago

carlosgonz0 commented 1 year ago

carlosgonz@-B75-Pro3-M:~/Descargas/bionic-clown-boot-master$ ls allow-mbmloader-flashing-mbm.bin boot.img install.sh kexecboot README root root404.sh scripts

carlosgonz@B75-Pro3-M:~/Descargas/bionic-clown-boot-master$ fastboot flash boot boot.img fastboot flash boot boot.img Sending 'boot' (8192 KB) OKAY [ 0.396s] Writing 'boot' (bootloader) Preflash validation failure FAILED (remote: '') fastboot: error: Command failed

IMbackK commented 1 year ago

The bootloader dident like your boot.img. boot.img is signed, if there is any corruption this will happen.

What is also possible is that your cdt.bin is to old, altho i dont think the bionic signatures where ever changed, what version of android do you have on this bionic?

Also note that there are several verizon devices that contain "bionic" in the name, but only the model xt875 is supported, trying to flash a xt875 boot.img on a different device would also cause exactly this failure

carlosgonz0 commented 1 year ago

It is Android Jelly bean, so i used iRoot to get Root access because qemu not get working i just not expert on qemu however i spend a lot time to get root from qemu but seems i doing something wrong i guess. To be honest i got confused to follow the both instruct files to install Maemo on android 4.0 and 4.1 because seems incomplete for 4.1 So at the moment the bionic can not boot android either.

Edit: My Device Bionic XT875

Thanks any help

IMbackK commented 1 year ago

the sha256sum of the boot.img should be 0eea1a727249db0827de809ae18fd70afc617912d704838fe5d50e9016644b1d

IMbackK commented 1 year ago

to abort the install you have to flash the system.img of the android version you have installed, then android will work again and you can start over.

carlosgonz0 commented 1 year ago

carlosgonz@B75-Pro3-M:~/Descargas$ md5sum boot.img 0e79a534a77f55c6443c3c3a40c93afa boot.img

where to find your boot.img? also system.img to recovery?

carlosgonz0 commented 1 year ago

the sha256sum of the boot.img should be 0eea1a727249db0827de809ae18fd70afc617912d704838fe5d50e9016644b1d

Also this is for android 4.0 or 4.1 ?

IMbackK commented 1 year ago

its the boot.img in the clownboot repo. your boot.img is corrupt, its md5sum should be 7090c80ff4ae49ab0738675adc1ce63d, as the devices bootloader was already telling you.

You can get system.img by downloading the .zip file of you revision of android from here: https://firmware.center/firmware/Motorola/XT875%20Droid%20Bionic/Stock/

anyhow if you just reclone or git fsck your clone you and flash a non-corrupted boot.img kexecboot should work on your deivce

The boot.img from the clown-boot repo is universal, its the one from 4.0 because the kexec modules are built against this version, but you can flash it on a 4.1 device just the same.

carlosgonz0 commented 1 year ago

Thanks i will come back here in 5 days. Huge thanks for the support. uvos - bionic

carlosgonz0 commented 1 year ago

I got boot Maemo on Bionic but with this output... Just boot Maemo without sim, with sim card inserted just not boot. Chimaera-devel is enabled.

carlosgonz@B75-Pro3-M:~/Descargas/bionic-clown-boot-master$ sudo ./install.sh installing kexec to kexecboot scripts/kexebootstart.sh: 1 file pushe...kipped. 0.3 MB/s (575 bytes in 0.002s) kexecboot/: 7 files pushed, 0 skipped. 5.7 MB/s (6348537 bytes in 1.065s) root/busybox: 1 file pushed, 0 skipped. 5.8 MB/s (1867568 bytes in 0.309s) cp: /system/xbin/true: No such file or directory failed on '/system/bin/logwrapper' - No such file or directory

carlosgonz0 commented 1 year ago

Well it booting Randomly with SIM /Modem, but for some reason do not get connection, because 3G shutdown, however i like Bionic because Texas Instrument.