Hqnicolas

Ah ok, so, the uboot is fine, I don't know why it doesn't detect the root.img 🤔 Did you try to boot flashdrive?

I think by reading DTB from the kernel 4 that boot... You will find things like this

My god, that's good be a difference in voltage regulator 👀 It's a device with tcs4525 Or sti8070? This uboot from 8gb device don't like to boot from USB... I think we have somebody in this girl with SD card reader soldered on 8gb device

Thank you! Please use 0x0000c800 Flash the update again and do root on 0x0000c800 Please consider to rename this root partition to "recovery" on a second try rename it to "root"

some armbian builds https://disk.yandex.ru/d/Bt5wObnYekq8FQ not mine, i just found

it's Friday night! let's build another build H96MAX 8GB RK3566 UPDATE.img How to build V7 8G_Linux_Pack_Firmware.zip @mvpwar @Kenneth Hidalgo can you test it? Following the tutorial instead of set Address on 0x0000A000 You will set Address on 0x0000c800

Flash This UpdateV4.img file on EMMC and v0.5 on USB stick on port 3.0 Please post the LOG from TTL

for editing and include armbian kernel 6.2 on EMMC you will need to boot from usb

Can you use the linaro build image to boot from USB? On 8gb device? If you can... You can mount MMC and put the armbian inside, like this tutorial

😮‍💨 I'm about to buy an 8gb box just to make this image, but I already have a lot of hardware sitting here, including a radxa rock 3A 8gb ram 64gb mmc 1tb nvme, that don't accelerate GPU 😂 (drivers), hardware waiting for some use, tomorrow I'm going to make a socks5 Proxy over isolated docker L3 lan on it just to prevent it from being at the bottom of the drawer

You need to enable console tty over dtb command line So it will wait for interaction Since we use an original Android dtb on uboot.img No console enabled 😅

Sorry @mvpwar When I said v5 image It's about the v0.5 flash drive image that I have done... I'm not so good with instructions, For me It's hard to give instructions over a forum topic, be better when I have the device to debug. Flash the V5 update.IMG on device And v0.5 SD image on flash drive over USB 3.0

You need to mark write by address flag!!!!!

Balena etcher

please try to flash V5 image to an flash drive and put it on usb 3.0 port Release Version v0.5DEBIAN12 BETA Release Version v0.5ARMBIAN23 BETA

OK the V5 image address is 0x00010800 you will need to flash the root.img in this address please change it on the table

LOL! did you fix it? I'm at work now, can you recompile and test?

please get the DEV Partition from image v5 from the flashed device!!!! i have changed it 😨

what is the address that you flash the root.img partition on tutorial step 2? please try to flash V5 image to an flash drive and put it on usb 3.0 port Release Version v0.5DEBIAN12 BETA Release Version v0.5ARMBIAN23 BETA

te seller from china send it to @Kenneth Hidalgo unfortunately it was an kernel 4 linaro

Generating files again.... Result Update.img V4 execute step 1 with V4 update.img execute step 2 with root.img (from tutorial) set Address on 0x0000A000 set Name on root Update.img V5 execute step 1 with V5 update.img execute step 2 with root.img (from tutorial) set Address will be different value "0x00xxxx??????", you will need to seach for partition named root Please share this value if this image works For update.img V5 i used a different pattern for Linux Pack Firmware

Did it works? My files get corrupted

i did this with the imgutil on windows Download imgutil /x boot.img dtb Please test the V5 and V4 Before another different approach

just to bloat the file inside, it works on my 4gb device absolutly NOT, it's basically the same original android img file