Jump to content

Recommended Posts

Posted

Can anyone please share dts/dtb that working for HK1 RBOX R2 - kernel 6 (or 5.15) ?  I don't have enough knowledge to do patching dtb/dts
I tried the dtb from @hotnikq (thank you!), and it booted to os successfully, however, no ethernet (no usb 2.0, no hdmi but it's fine for me) 😁

I'm also looking for a way to build uboot and recreate sdcard for booting. I did it myself before but now I can't remember 😅 I'm using kernel 4.19 
Please give me some advice, any help would be highly appreciated. Thanks

kernel-4.19.log kernel 6.2.log

Posted
2 hours ago, ewww said:

no ethernet (no usb 2.0, no hdmi but it's fine for me)

 

it's worse than when I started my thread back in 2022


if you have the patience to test and compile the adaptations we will create a topic efforts to develop firmware for HK1 RBOX R2 4gb 64gb ap6398s

Posted (edited)
14 hours ago, Kenneth Hidalgo said:
hello everyone, I have not been able to install the hotnikq image yet, after the first step it is in MASKROM, and I have not been able to do anything else.

You will need to create a update.img to your device,

since the factory change the BOM list to build your device you can search for @SteeMan topics about that

You can read more about this here
.................
Everything you need is described on this topic.
start from page 1
...................
Try flash uboot and loader from your Android image

.........................
If you can, please send a readable board photo upside and downside

Edited by hotnikq
Posted

great, as soon as I have some time I'll try it out, I have a cp21xx ttl serial converter, soon I'll be posting the board's log output.

Posted (edited)
On 6/20/2023 at 1:15 AM, Kenneth Hidalgo said:

hello everyone, I have not been able to install the hotnikq image yet, after the first step it is in MASKROM, and I have not been able to do anything else.

I made the changes to work on your device see there in the topic I created for your device
@Kenneth Hidalgo

 

 

Edited by hotnikq
Posted (edited)
2 hours ago, Kenneth Hidalgo said:

The problem is that I can't do the second step, he pressed the reset button and connected the USB and it appears in MASKROM mode

Can you share a image that actually works on your device?

Can be Android or Linux

i think you already test this https://drive.google.com/file/d/1FTOKB0pgqkLCJedyJrBq-qdONQ9KTM3-/view?usp=sharing

please confirm

Edited by hotnikq
Posted
10 hours ago, Kenneth Hidalgo said:

Hotnikq, It is correct, that is the firmware that my box has installed, the only problem I have is that the root partition is very small (6GB)

today I will work in that image....

Posted (edited)
On 6/26/2023 at 12:39 AM, Kenneth Hidalgo said:

Hotnikq, It is correct, that is the firmware that my box has installed,


since this image works with your H96 MAX
I create an update.img file based on your image....
 

Edited by hotnikq
Posted (edited)
On 6/28/2023 at 5:47 PM, hotnikq said:

This is a new Update.img file for you to test

After  update.img  in MASKROM mode, debug message as below

U-Boot SPL board init
U-Boot SPL 2017.09-gc613b7ea04-210315 #zzz (Mar 15 2021 - 18:08:14)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
MMC error: The cmd index is 1, ret is -110
Card did not respond to voltage select!
mmc_init: -95, time 10
spl: mmc init failed with error: -95
Trying to boot from MMC1
SPL: A/B-slot: _a, successful: 0, tries-remain: 6
Not fit magic
Trying fit image at 0x5000 sector
Not fit magic
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
# Reset the board to bootrom #

 

Edited by mvpwar
Posted (edited)
Quote

Kenneth Hidalgo

Posted Monday at 05:39 AM

Hotnikq, It is correct, that is the firmware that my box has installed, the only problem I have is that the root partition is very small (6GB)

 

I fixed the issue on a different firmware by running the following command: 

resize2fs /dev/mmcblk2p6

 

My main partition changed from 6GB to 56GB.

Edited by wootje
Posted (edited)

when the box in MASKROM mode, I checked the "loader" with the MiniLoaderAll.bin path, and click the "Run" button to "Download Image" the Debug message as below

Boot1 Release Time: Mar  5 2021 15:51:33, version: 1.05
support nand flash type: slc
...nandc_flash_init enter...
No.1 FLASH ID:ff ff ff ff ff ff
sfc nor id: ff ff ff
sfc_nand id: ff ff ff
SD IO init 0
Set SD Clk: 200, 5
Set SD Clk: 200, 5
 SDC_BusRequest:  CMD=8  SDC_RESP_TIMEOUT 1747
 mmc0:cmd8,20
 SDC_BusRequest:  CMD=5  SDC_RESP_TIMEOUT 1747
 mmc0:cmd5,20
 SDC_BusRequest:  CMD=55  SDC_RESP_TIMEOUT 1747
 mmc0:cmd55,20
 SDC_BusRequest:  CMD=1  SDC_RESP_TIMEOUT 1747
 mmc0:cmd1,20
Set SD Clk: 200, 5
 SDC_BusRequest:  CMD=8  SDC_RESP_TIMEOUT 1747
 mmc0:cmd8,20
 SDC_BusRequest:  CMD=5  SDC_RESP_TIMEOUT 1747
 mmc0:cmd5,20
 SDC_BusRequest:  CMD=55  SDC_RESP_TIMEOUT 1747
 mmc0:cmd55,20
 SDC_BusRequest:  CMD=1  SDC_RESP_TIMEOUT 1747
 mmc0:cmd1,20
Set SD Clk: 200, 5
 SDC_BusRequest:  CMD=8  SDC_RESP_TIMEOUT 1747
 mmc0:cmd8,20
 SDC_BusRequest:  CMD=5  SDC_RESP_TIMEOUT 1747
 mmc0:cmd5,20
 SDC_BusRequest:  CMD=55  SDC_RESP_TIMEOUT 1747
 mmc0:cmd55,20
 SDC_BusRequest:  CMD=1  SDC_RESP_TIMEOUT 1747
 mmc0:cmd1,20
SdmmcInit=0 1
Emmc IO init.
Emmc IO init.
mmc_set_bus_width: 1
SetEmmcClk: 375000, 5
SetEmmcClk: 375000, 5
mmc_set_bus_width: 8
SetEmmcClk: 200000000, 1
Enable PHY CLK: 200000000
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=59640MB
FwPartOffset=2000 , 100000
##############serialno_str = 4DA57NB8JI
UsbBoot ...110226

 

the box cant be tested successfully this time, and follow the step2 to flashed the root.img by Address "0x0000A000", after reboot the debug message as below

 

U-Boot SPL board init
U-Boot SPL 2017.09-gc613b7ea04-210315 #zzz (Mar 15 2021 - 18:08:14)
unknown raw ID phN
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
MMC error: The cmd index is 1, ret is -110
Card did not respond to voltage select!
mmc_init: -95, time 10
spl: mmc init failed with error: -95
Trying to boot from MMC1
SPL: A/B-slot: _a, successful: 0, tries-remain: 6
Not fit magic
Trying fit image at 0x5000 sector
Not fit magic
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
# Reset the board to bootrom #

 

Trying to reset the box , and it still dosen't works , help me , THX... @hotnikq

Edited by mvpwar
Posted (edited)
13 hours ago, mvpwar said:

Trying to reset the box , and it still dosen't works , help me , THX...

 

 

The bootloader is incompatible with you board, you will need to go back to android image. https://androidtvbox.eu/firmware-rk3566-h96-max-for-android-11-tv-box-update-20210810/
or try the linaro from @Kenneth Hidalgo  https://drive.google.com/file/d/1FTOKB0pgqkLCJedyJrBq-qdONQ9KTM3-/view?usp=drive_link

 

Since my Uboot + Miniloaderall.bin don't detect your board 
you will have to adapt uboot and miniloaderall.bin somehow

 

 

if you can't flash this images
you will need to short the CLK + GND with tweezers to enable maskrom mode  
these two pins are exactly opposite the emmc side of the board

short it, conect the USB male to male USB
release the short
flash the regular ROM

 

PIN.jpg.702a6482d977dcd7fb801f239fd938df.jpg

https://roc-rk3328-cc.readthedocs.io/en/latest/flash_emmc.html#maskrom-mode

 

 

h96maxF.thumb.jpg.eaf6465c45d497d03bd7cddc455cabb5.jpg

 

Edited by hotnikq
Posted
On 7/2/2023 at 10:01 PM, hotnikq said:

The bootloader is incompatible with you board, you will need to go back to android image. https://androidtvbox.eu/firmware-rk3566-h96-max-for-android-11-tv-box-update-20210810/
or try the linaro from @Kenneth Hidalgo  https://drive.google.com/file/d/1FTOKB0pgqkLCJedyJrBq-qdONQ9KTM3-/view?usp=drive_link

 

Since my Uboot + Miniloaderall.bin don't detect your board 
you will have to adapt uboot and miniloaderall.bin somehow

 

 

if you can't flash this images
you will need to short the CLK + GND with tweezers to enable maskrom mode  
these two pins are exactly opposite the emmc side of the board

short it, conect the USB male to male USB
release the short
flash the regular ROM

 

1142.jpg.955d607cbc2f3b82169d786868d08b38.jpg

https://roc-rk3328-cc.readthedocs.io/en/latest/flash_emmc.html#maskrom-mode

 

114.thumb.jpg.43ae8bbca4209c02c38c0db29e30c28e.jpg

 

 

 

Posted (edited)

Recently acquired an H96 Max v56 Rk3566 (Android 12) 8GB DDR4/64GB eMMC, and like the idea of using it for Linux and Android development.
 

I can get it into both 'Loader' mode, with the reset switch, and into MaskROM mode, by shorting the eMMC Clock signal to ground.

 

Unfortunately, that's where my expertise falls short, and I became stumped. I tried to extract the firmware in both modes, with a confirmed working M2M USB cable, with both rkdumper_1.1.1.0, and with the rkflashkit. No such luck. rkdumper_1.1.1.0 finds the device, but can't reset or upload from it, whilst the rkflaskit doesn't see it in either mode, despite the USB device appearing after an lsusb command.

 

What are the tools and methods for firmware extraction, and flashing? I imagine, though I haven't tried it, that I can flash alternate firmware with the Rockchip-AndroidTool_Release_v2.84, but that's not what I'm trying to do. I'm wanting a full backup, before I find that the manufacturer's firmware on their website isn't suitable or enough to get me out of trouble.

 

Any links, info or advice for this device, greatly appreciated.

 

T.

Edited by Guest

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines