-
Upcoming Events
-
-
Volunteering positions
-
Code reviewer
Position: Framework maintainerNumber of places: UnlimitedApplicants: 9
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
197
Armbian for H313 X96-Q LPDDR3 TV-Box
Actually in that post it was about downloading the boot_a partition. Then extracting the dts.. you can skip the dts extraction part for now. We need your boot_a partition. also that’s not the android dts you posted. It has some info but not all of it. -
197
Armbian for H313 X96-Q LPDDR3 TV-Box
Oh, so it is the devicetree of Linux we want. My bad. Here it is: devicetree.txt FYI I was able to use binwalk -e on the boot partition dump, nice to see there is another way. Thanks for all the help -
197
Armbian for H313 X96-Q LPDDR3 TV-Box
This post should help extracting your boot.img from android. That’s if your box is already rooted. -
197
Armbian for H313 X96-Q LPDDR3 TV-Box
/sunxi-fw info -v fulldisk.img @ 0: mbr: DOS MBR protective MBR, GPT used GPT version 00010000 usable disk size: 7419 MB number of partition entries: 17 @ 16: toc0: signed boot image 2 items size: 98304 bytes @ 321: toc0: signed boot image 2 items size: 98304 bytes @26812: fit: U-Boot FIT image fit:__overlay__: "<no description>" fit:__overlay__: "<no description>" fit:fragment@2: "<no description>" So I never dumped just boot0 (and no firmware update available), but I have full emmc dump named fulldisk.img. I would assume it is the toc0? Trying to extract does not work , however: (maybe because there are two?) /sunxi-fw extract -v -n toc0 -o uboot0 /home/Tr/fulldisk.img unknown image file extracting the mbr works fine though. -
197
Armbian for H313 X96-Q LPDDR3 TV-Box
Wait, that was the Linux kernel, not uboot. I'll get that
-
-
Member Statistics