H96 max plus 4+64 stuck on maskrom mode

[rolandow]

I tried that, but it still won't come out of maskrom mode. I guess the NAND could really be broken. Especially because the box just stopped working one day when I tried turning it on. It was just sitting there, turned off, and all of the sudden it wouldn't turn on again. So the error could not have been caused by a firmware upgrade or something like that, because I never upgraded it.

Eventually I gave up and just ordered a new one. Should have done that hours earlier. The new box has amlogic as well, so it will live a little longer than 7 months.

[JansleySouza]

My WiFi chip is SP6330 ZX190906..I tested 6 different firmware's and all works except WiFi. Button not open. The strange is i find firmware with SP 6330 chip but again not working..I don't know how to solve it. My device is new and is the second version

I have a rockchip box, with this WIFI chip SP6330. What firmware did you use? My Box is brick. Thanks

[tvBoxFreak]

Hi Everbody,

I'm still unable to resolve the maskrom issue that I've with my H96 Max+ device, however so far i've made progress. Details are posted below.

Q1. Could somebody please tell me why the sdcard despite being detected, after downloading bootloader, is not able to read or write? Is this a HW issue or can be fixed via SW tools or certain cmds?
Q2. What can be done to fix this, if at all it can be fixed?
Q3. Can this be fixed by booting into uboot and running the cmd "reboot loader", I found this cmd somewhere, where it's said that the loader can be rebooted with this cmd via uboot?
Q4. Is this a case of protected loader?

Thanks for reading this, please read along for observed outputs. Any help or suggestions are appreciated

1. I used to get excited and pretty optimitic on seeing positive results from rkdeveloptool, upgrade_tool and desktop tools as well, however that optimism was dashed when I saw the UART output

rkdeveloptool/upgrade_tool output - UART OUTPUT
1.1
Downloading firmware 0%....100%, erasing flash 0%...100%

SDC ERR: 0x20
SDMMC_CMD=0x20002759, SDMMC_RINISTS=0x114, SDMMC_STATUS=0x6906
mmc2:cmd25,20
SDM_Write error=b1e00 count=80 ret=1SDC ERR: 0x20
SDMMC_CMD=0x20002759, SDMMC_RINISTS=0x114, SDMMC_STATUS=0x6906
mmc2:cmd25,20
SDM_Write error=b1e00 count=80 ret=1

1.2 Boot
1.2.1 No output on the screen and a constant red light; discovered a Maskrom device (always)
1.2.2a UART output: Nothing until I do the db cmd from rkdeveloptool
1.2.2b

DDR version 1.13 20180428
ID:0xFFF
In
DDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB
ddrconfig:3
OUT
Boot1 Release Time: Sep 7 2018 15:48:25, version: 2.49
[B]SdmmcInit=0 NOT PRESENT[/B]
[B]mmc Ext_csd, ret=0 ,[/B]
Ext[226]=20, bootSize=2000,
Ext[215]=7, Ext[214]=47, Ext[213]=c0, Ext[212]=0,cap =747c000 REL=1f
[B]mmc2:cmd19,100[/B]
[B]SdmmcInit=2 0[/B]
BootCapSize=2000
UserCapSize=59640MB
[B]SDC ERR: 0x20[/B]
[B]SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
SDM_Read error=40 ret=20
FwPartOffset=2000 , 2000[/B]
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
SDM_Read error=1f80 ret=20
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
[B]SDM_Read error=1c00 ret=20[/B]
##############serialno_str = J?
UsbHook 712342
powerOn 712414

The above output is slightly different when I booted armbian from sdcard & usb drive. In that, mmc and mmc2 both are discovered

DDR version 1.13 20180428
ID:0xFFF
In
DDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB
ddrconfig:3
OUT
Boot1 Release Time: Feb 2 2018 15:41:39, version: 2.46
ChipType = 0x11, 141
[B]SdmmcInit=2 0
BootCapSize=2000
UserCapSize=59640MB
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x0, SDMMC_STATUS=0x6906[/B]
[B]SDM_Read error=40 ret=20[/B]
FwPartOffset=2000 , 2000
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x0, SDMMC_STATUS=0x6906
SDM_Read error=1f80 ret=20
[B]SdmmcInit=0 0
BootCapSize=0
UserCapSize=15103MB
FwPartOffset=2000 , 0
StorageInit ok = 41310[/B]
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xa3d00
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):f947c7e
NOTICE: BL31: Built : 12:09:31, Aug 30 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using rkfiq sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime serv?ces
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9


U-Boot 2017.09-armbian (Jun 28 2019 - 12:42:59 +0300)

Model: Firefly ROC-RK3328-CC
DRAM: 4 GiB
MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
*** Warning - bad CRC, using default environment

In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Firefly ROC-RK3328-CC
misc_init_r
cpuid=55524b54323530323300000000160d16
serial=d9503d4ca783446
Net: No ethernet found.
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: Core Release: 3.10a
USB3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler G3
Type: Removable Har? Disk
Capacity: 3824.0 MB = 3.7 GB (7831552 x 512)
... is now current device
Scanning usb 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
262 bytes read in 20 ms (12.7 KiB/s)
1: Armbian
Retrieving file: /uInitrd
reading /uInitrd
7794373 bytes read in 465 ms (16 MiB/s)
Retrieving file: /Image
reading /Image
18978824 bytes read in 1101 ms (16.4 MiB/s)
append: root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
Retrieving file: /dtb/rockchip/rk3328-t9.dtb
reading /dtb/rockchip/rk3328-t9.dtb
70290 bytes read in 105 ms (653.3 KiB/s)
## Loading init Ramdisk from Legacy Image at 04000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 7794309 Bytes = 7.4 MiB
Load Address: 00000000
Entry P?int: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to fc793000, end fcf01e85 ... OK
Loading Device Tree to 00000000fc77e000, end 00000000fc792291 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on phy?ical CPU 0x0

[gefattern]

Hi Everbody,

I'm still unable to resolve the maskrom issue that I've with my H96 Max+ device, however so far i've made progress. Details are posted below.

Q1. Could somebody please tell me why the sdcard despite being detected, after downloading bootloader, is not able to read or write? Is this a HW issue or can be fixed via SW tools or certain cmds?
Q2. What can be done to fix this, if at all it can be fixed?
Q3. Can this be fixed by booting into uboot and running the cmd "reboot loader", I found this cmd somewhere, where it's said that the loader can be rebooted with this cmd via uboot?
Q4. Is this a case of protected loader?

Thanks for reading this, please read along for observed outputs. Any help or suggestions are appreciated

1. I used to get excited and pretty optimitic on seeing positive results from rkdeveloptool, upgrade_tool and desktop tools as well, however that optimism was dashed when I saw the UART output

rkdeveloptool/upgrade_tool output - UART OUTPUT
1.1
Downloading firmware 0%....100%, erasing flash 0%...100%

SDC ERR: 0x20
SDMMC_CMD=0x20002759, SDMMC_RINISTS=0x114, SDMMC_STATUS=0x6906
mmc2:cmd25,20
SDM_Write error=b1e00 count=80 ret=1SDC ERR: 0x20
SDMMC_CMD=0x20002759, SDMMC_RINISTS=0x114, SDMMC_STATUS=0x6906
mmc2:cmd25,20
SDM_Write error=b1e00 count=80 ret=1

1.2 Boot
1.2.1 No output on the screen and a constant red light; discovered a Maskrom device (always)
1.2.2a UART output: Nothing until I do the db cmd from rkdeveloptool
1.2.2b

DDR version 1.13 20180428
ID:0xFFF
In
DDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB
ddrconfig:3
OUT
Boot1 Release Time: Sep 7 2018 15:48:25, version: 2.49
[B]SdmmcInit=0 NOT PRESENT[/B]
[B]mmc Ext_csd, ret=0 ,[/B]
Ext[226]=20, bootSize=2000,
Ext[215]=7, Ext[214]=47, Ext[213]=c0, Ext[212]=0,cap =747c000 REL=1f
[B]mmc2:cmd19,100[/B]
[B]SdmmcInit=2 0[/B]
BootCapSize=2000
UserCapSize=59640MB
[B]SDC ERR: 0x20[/B]
[B]SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
SDM_Read error=40 ret=20
FwPartOffset=2000 , 2000[/B]
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
SDM_Read error=1f80 ret=20
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
[B]SDM_Read error=1c00 ret=20[/B]
##############serialno_str = J?
UsbHook 712342
powerOn 712414

The above output is slightly different when I booted armbian from sdcard & usb drive. In that, mmc and mmc2 both are discovered

DDR version 1.13 20180428
ID:0xFFF
In
DDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB
ddrconfig:3
OUT
Boot1 Release Time: Feb 2 2018 15:41:39, version: 2.46
ChipType = 0x11, 141
[B]SdmmcInit=2 0
BootCapSize=2000
UserCapSize=59640MB
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x0, SDMMC_STATUS=0x6906[/B]
[B]SDM_Read error=40 ret=20[/B]
FwPartOffset=2000 , 2000
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x0, SDMMC_STATUS=0x6906
SDM_Read error=1f80 ret=20
[B]SdmmcInit=0 0
BootCapSize=0
UserCapSize=15103MB
FwPartOffset=2000 , 0
StorageInit ok = 41310[/B]
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xa3d00
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):f947c7e
NOTICE: BL31: Built : 12:09:31, Aug 30 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using rkfiq sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime serv?ces
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9


U-Boot 2017.09-armbian (Jun 28 2019 - 12:42:59 +0300)

Model: Firefly ROC-RK3328-CC
DRAM: 4 GiB
MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
*** Warning - bad CRC, using default environment

In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Firefly ROC-RK3328-CC
misc_init_r
cpuid=55524b54323530323300000000160d16
serial=d9503d4ca783446
Net: No ethernet found.
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: Core Release: 3.10a
USB3: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Device 0: Vendor: Kingston Rev: 1.00 Prod: DataTraveler G3
Type: Removable Har? Disk
Capacity: 3824.0 MB = 3.7 GB (7831552 x 512)
... is now current device
Scanning usb 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
262 bytes read in 20 ms (12.7 KiB/s)
1: Armbian
Retrieving file: /uInitrd
reading /uInitrd
7794373 bytes read in 465 ms (16 MiB/s)
Retrieving file: /Image
reading /Image
18978824 bytes read in 1101 ms (16.4 MiB/s)
append: root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
Retrieving file: /dtb/rockchip/rk3328-t9.dtb
reading /dtb/rockchip/rk3328-t9.dtb
70290 bytes read in 105 ms (653.3 KiB/s)
## Loading init Ramdisk from Legacy Image at 04000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 7794309 Bytes = 7.4 MiB
Load Address: 00000000
Entry P?int: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to fc793000, end fcf01e85 ... OK
Loading Device Tree to 00000000fc77e000, end 00000000fc792291 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on phy?ical CPU 0x0

Hi ,

follow the Guide of User Haizenberg , it is sticky in the RK3288 Section i think ,

this is the only working Solution that i know for this Bug ,

good luck / gefattern

[freddy]

1. Its hidden in partition maybe...

Try this maybe

You will need Stock Firmware in OTA format image.

Use big G and search
C gadgets review...etc
Probs 8.1 version was original or 9.0

Forget the PC for a minute

Was armbian on the USB thumb drive?

You made a bootable sd card

On a USB thumb drive that has been cleaned and formatted f32
Send OTA file for H96 Max plus .../Copy to/drag drop
Make sure you do not unzip

Boot to recovery/uboot and try cmd OTA update

[tvBoxFreak]

There's a tool called Chinese Miracle 2, CM2 RKT is for rockchip devices sadly, it needs a dongle to work & there seems to be no "usable" version for it. If somebody knows what cmds/ways it uses to access the device, that may be of some help.

Hi ,

follow the Guide of User Haizenberg , it is sticky in the RK3288 Section i think ,

this is the only working Solution that i know for this Bug ,

good luck / gefattern

Hi gefattern, Thanks for replying. I'm sorry I couldn't find the sticky post you were referring to? Is the following solution the one you'd referred, from thread "[HOWTO] Enable Maskrom-Mode / perhaps UnBrick your device"?

To fix your IDB failure, you have to be in maskrom first and Look for the letters (GND and CLX) inside the board and try to connect them for 2 seconds while pressing upgrade button.

I tried, this however it didn't work infact my issue is with sd mmc communication, if you'd look at the uart o/p that I'd posted in my previous post it shows sd write error 0xxxx & sd read error 0xxxx. Now, i'm wondering if it's the issue of a loose solder, since the cpu is placed right next to the emmc on H96 max+ board, I doubt the solder may have loosened up because of cpu's heating. I'm referring this from my memory of the box dying, it was quite unresponsive when it was last working.

But anyway, I know for sure that the problem is 1. Bootloader 2. SDMMC read/write operations, no cmd is able to write to emmc because of rw errors
Also, when I download bootloader, I can query chip info and flash info successfully but I can't read/write anything.
Queried flash info:
Flash Info:
Manufacturer: SAMSUNG,value=00
Flash Size: 59640MB
Block Size: 512KB
Page Size: 2KB
ECC Bits: 0
Access Time: 40
Flash CS: Flash<0>

Please let me know your thoughts on this and hopefully any solutions/ways that I may test? Thanks

1. Its hidden in partition maybe...

Try this maybe

You will need Stock Firmware in OTA format image.

Use big G and search
C gadgets review...etc
Probs 8.1 version was original or 9.0

Forget the PC for a minute

Was armbian on the USB thumb drive?

You made a bootable sd card

On a USB thumb drive that has been cleaned and formatted f32
Send OTA file for H96 Max plus .../Copy to/drag drop
Make sure you do not unzip

Boot to recovery/uboot and try cmd OTA update

Hi freddy, thanks for replying.

About armbian boot: I wrote the img file with win32diskimager to both sdcard, usb drive & then I booted the device & it worked flawlessly.

I did try the OTA option with usb drive(FAT32) however it doesn't look up anything on the drive when I choose the option to apply update via sdcard.

I could't find the cmd for ota update via uboot, I tried do_ota, reboot ota however those cmds didn't exist (refer the end of uart o/p)

Can you think of a way by which I can access the emmc & write the image directly there(other than de/soldering), because when I try to write to emmc via rockchip board it gives me sdmmc read/write errors or is there a way to fix sdmmc rw errors? or de/soldering is the last straw? or maybe this is the case of a short connection on the board?

Please share your thoughts on this. Thanks.

The following is the UART output when I booted the device with a stock img written sd card
UART Log excerpt

[ 1.631464] mmc2: card has unknown MMCA version 6
[ 1.631481] mmc2: error -22 whilst initialising MMC card
[ 1.632784] Freeing unused kernel memory: 768K
[ 1.637652] init: init first stage started!
[ 1.637698] init: First stage mount skipped (recovery mode)
[ 1.637893] init: Using Android DT directory /proc/device-tree/firmware/android/
[ 1.643105] mmc_host mmc2: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0)
[ 1.673059] usb 1-1: new high-speed USB device number 2 using dwc2
[ 1.693147] mmc2: card has unknown MMCA version 6
[ 1.693175] mmc2: error -22 whilst initialising MMC card

UART Complete log

DDR version 1.13 20180428
ID:0xFFF
In
DDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=4096MB
ddrconfig:3
OUT
Boot1 Release Time: Sep 7 2018 15:49:55, version: 2.49
ChipType = 0x11, 194
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=59640MB
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
SDM_Read error=40 ret=20
FwPartOffset=2000 , 2000
SDC ERR: 0x20
SDMMC_CMD=0x20002352, SDMMC_RINISTS=0x104, SDMMC_STATUS=0x6906
mmc2:cmd18,20
SDM_Read error=1f80 ret=20
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=15103MB
FwPartOffset=2000 , 0
run on sd0
StorageInit ok = 41993
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
GPT 0x337a9e0 signature is wrong
LoadTrust Addr:0x4000
No find bl30.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xc12fc
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):0eba775
NOTICE: BL31: Built : 12:11:32, Nov 23 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-194-g646eecc5 #61 Wed Dec 5 06:31:51 UTC 2018 aarch64)

INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.4

INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9


U-Boot 2017.09 (Apr 27 2019 - 23:48:59 +0800)

Model: Rockchip RK3328 EVB
DRAM: 4 GiB
Relocation Offset is: fcc05000
Using default environment

rksdmmc@ff500000: 1, rksdmmc@ff520000: 0
switch to partitions #0, OK
mmc1 is current device
do_rkimg_test found IDB in SDcard
Boot from SDcard
Load FDT from recovery part
DTB: rk-kernel.dtb
ANDROID: fdt overlay OK
Using kernel dtb
pwm-regulator(vdd-center): init 1250000 uV
vcc_arm 1250000 uV
pwm-regulator(vdd-log): init 1100000 uV
vcc_log 1100000 uV
start get public phy
inno hdmi phy init success, save it
In: serial
Out: serial
Err: serial
Model: Rockchip RK3328 box
enter Recovery mode!
Rockchip UBOOT DRM driver version: v1.0.1
display_panel_prepare: failed to find panel prepare funcs
display_panel_enable: failed to find panel enable funcs
CLK: apll 400000000 Hz
dpll 664000000 Hz
cpll 1200000000 Hz
gpll 491009999 Hz
npll 600000000 Hz
armclk 600000000 Hz
aclk_bus 150000000 Hz
hclk_bus 75000000 Hz
pclk_bus 75000000 Hz
aclk_peri 150000000 Hz
hclk_peri 75000000 Hz
pclk_peri 75000000 Hz
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
ca head not found
ANDROID: reboot reason: "recovery"
get share memory, arg0=0x0 arg1=0x9e08000 arg2=0x3f8000 arg3=0x1
read_is_device_unlocked() ops returned that device is UNLOCKED
avb_ab_flow.c:30: ERROR: Magic is incorrect.
avb_ab_flow.c:106: ERROR: Error validating A/B metadata from disk. Resetting and writing new A/B metadata to disk.
avb_slot_verify.c:637: ERROR: vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED
get share memory, arg0=0x0 arg1=0x9e08000 arg2=0x3f8000 arg3=0x1
Booting kernel at 0x207f800 with fdt at 1f00000...


## Booting Android Image at 0x0207f800 ...
Kernel load addr 0x02080000 size 19005 KiB
RAM disk load addr 0x11000000 size 10099 KiB
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
XIP Kernel Image ... OK
'reserved-memory' ramoops@68000000: addr=110000 size=f0000
Loading Ramdisk to 07823000, end 081ffae5 ... OK
Loading Device Tree to 000000000780d000, end 000000000782210d ... OK
Adding bank: 0x00200000 - 0x08400000 (size: 0x08200000)
Adding bank: 0x0a200000 - 0xff000000 (size: 0xf4e00000)

Starting kernel ...


[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Initializing cgroup subsys schedtune
[ 0.000000] Linux version 4.4.159 (user@ubuntu) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05) ) #1 SMP PREEMPT Sat Apr 27 23:50:50 CST 2019
[ 0.000000] Boot CPU: AArch64 Processor [410fd034]
[ 0.000000] earlycon: Early serial console at MMIO32 0xff130000 (options '')
[ 0.000000] bootconsole [uart0] enabled
[ 0.000000] Reserved memory: failed to reserve memory for node 'secure-memory@20000000': base 0x0000000020000000, size 0 MiB
[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000fac00000, size 32 MiB
[ 0.000000] Reserved memory: initialized node linux,cma, compatible id shared-dma-pool
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.0 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS migration not required
[ 0.000000] PERCPU: Embedded 21 pages/cpu @ffffffc0fef31000 s45528 r8192 d32296 u86016
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: enabling workaround for ARM erratum 845719
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1019976
[ 0.000000] Kernel command line: androidboot.mode=normal androidboot.dtbo_idx=0 root=PARTUUID=af01642c-9b84-11e8-9b2a-234eb5e198a0 androidboot.verifiedbootstate=orange androidboot.slot_suffix= androidboot.serialno=d9503d4ca7834461 console=ttyFIQ0 androidboot.baseband=N/A androidboot.selinux=permissive androidboot.wificountrycode=US androidboot.veritymode=enforcing androidboot.hardware=rk30board androidboot.console=ttyFIQ0 firmware_class.path=/vendor/etc/firmware init=/init root=PARTUUID=af01642c-9b84-11e8-9b2a-234eb5e198a0 earlycon=uart8250,mmio32,0xff130000 swiotlb=1 kpti=0
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.000000] software IO TLB [mem 0xfeee9000-0xfef29000] (0MB) mapped at [ffffffc0feee9000-ffffffc0fef28fff]
[ 0.000000] Memory: 4002520K/4145152K available (11134K kernel code, 1724K rwdata, 5348K rodata, 768K init, 2406K bss, 109864K reserved, 32768K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 1.238436] rk_gmac-dwmac ff550000.ethernet: clock input or output? (output).
[ 1.238499] rk_gmac-dwmac ff550000.ethernet: Can not read property: tx_delay.
[ 1.238517] rk_gmac-dwmac ff550000.ethernet: set tx_delay to 0x30
[ 1.238535] rk_gmac-dwmac ff550000.ethernet: Can not read property: rx_delay.
[ 1.238565] rk_gmac-dwmac ff550000.ethernet: set rx_delay to 0x10
[ 1.238619] rk_gmac-dwmac ff550000.ethernet: integrated PHY? (yes).
[ 1.238817] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_refout
[ 1.238846] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_speed
[ 1.243965] rk_gmac-dwmac ff550000.ethernet: init for RMII
[ 1.276501] stmmac - user ID: 0x10, Synopsys ID: 0x35
[ 1.855893] init: Unable to set property 'ro.adb.secure' to '0' in property file '/prop.default': Read-only property was already set
[ 1.855971] init: Unable to set property 'ro.boot.wificountrycode' to 'CN' in property file '/prop.default': Read-only property was already set
[ 1.856425] init: Unable to set property 'ro.product.first_api_level' to '28' in property file '/prop.default': Read-only property was already set
[ 1.856712] init: Unable to set property 'ro.board.platform' to 'rk3328' in property file '/prop.default': Read-only property was already set
[ 1.856939] init: Unable to set property 'ro.audio.monitorOrientation' to 'true' in property file '/prop.default': Read-only property was already set
[ 1.857013] init: Unable to set property 'ro.tether.denied' to 'false' in property file '/prop.default': Read-only property was already set
[ 1.857064] init: Unable to set property 'ro.product.usbfactory' to 'rockchip_usb' in property file '/prop.default': Read-only property was already set
[ 1.857565] init: Unable to set property 'ro.rk.screenoff_time' to '2147483647' in property file '/prop.default': Read-only property was already set
[ 1.857741] init: Unable to set property 'ro.rk.screenshot_enable' to 'true' in property file '/prop.default': Read-only property was already set
[ 1.857797] init: Unable to set property 'ro.target.product' to 'box' in property file '/prop.default': Read-only property was already set
[ 1.857897] init: Unable to set property 'ro.setupwizard.mode' to 'OPTIONAL' in property file '/prop.default': Read-only property was already set
[ 1.858114] init: Couldn't load property file '/product/build.prop': open() failed: No such file or directory: No such file or directory
[ 1.858161] init: Couldn't load property file '/odm/default.prop': open() failed: No such file or directory: No such file or directory
[ 1.858197] init: Couldn't load property file '/vendor/default.prop': open() failed: No such file or directory: No such file or directory
[ 1.858786] init: Created socket '/dev/socket/property_service', mode 666, user 0, group 0
[ 1.859451] init: Forked subcontext for 'u:r:vendor_init:s0' with pid 200
[ 1.860252] init: Forked subcontext for 'u:r:vendor_init:s0' with pid 201
[ 1.860431] init: Parsing file /init.rc...
[ 1.860654] init: Added '/init.recovery.rk30board.rc' to import list
[ 1.860731] init: Added '/init.rk30board.usb.rc' to import list
[ 1.860763] init: Added '/init.usb.configfs.rc' to import list
[ 1.860965] random: init: uninitialized urandom read (40 bytes read, 18 bits of entropy available)
[ 1.861342] init: Parsing file /init.recovery.rk30board.rc...
[ 1.861441] random: init: uninitialized urandom read (40 bytes read, 18 bits ?f entropy available)
[ 1.861447] init: Unable to read config file '/init.recovery.rk30board.rc': open() failed: No such file or directory
[ 1.861471] init: /init.rc: 1: Could not import file '/init.recovery.rk30board.rc': No such file or directory
[ 1.861502] init: Parsing file /init.rk30board.usb.rc...
[ 1.861962] init: Parsing file /init.usb.configfs.rc...
[ 1.862774] init: Parsing file /system/etc/init...
[ 1.862871] init: Unable to read config file '/system/etc/init': open() failed: No such file or directory
[ 1.862925] init: Parsing file /product/etc/init...
[ 1.862970] init: Unable to read config file '/product/etc/init': open() failed: No such file or directory
[ 1.863088] init: Parsing file /odm/etc/init...
[ 1.863154] init: Unable to read config file '/odm/etc/init': open() failed: No such file or directory
[ 1.863189] init: Parsing file /vendor/etc/init...
[ 1.863224] init: Unable to read config file '/vendor/etc/init': open() failed: No such file or directory
[ 1.863308] init: processing action (early-init) from (/init.rc:5)
[ 1.863454] init: starting service 'ueventd'...
[ 1.864301] audit: type=1400 audit(1514808000.743:3): avc: denied { write } for pid=1 comm="init" path="/acct/uid_0/pid_202/cgroup.procs" dev="rootfs" ino=2218 scontext=u:r:init:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=1
[ 1.864633] init: processing action (wait_for_coldboot_done) from (<Builtin Action>:0)
[ 1.865778] random: ueventd: uninitialized urandom read (40 bytes read, 18 bits of entropy available)
[ 1.868952] ueventd: ueven[ 1.986387] dwmmc_rockchip ff510000.dwmmc: Successfully tuned phase to 161
[ 1.987635] mmc1: new ultra high speed SDR50 SDIO card at address 0001
[ 2.045961] ueventd: Coldboot took 0.172 seconds
[ 2.046948] init: wait for '/dev/.coldboot_done' took 182ms
[ 2.047084] init: Command 'wait_for_coldboot_done' action=wait_for_coldboot_done (<Builtin Action>:0) took 182ms and succeeded
[ 2.047131] init: processing action (MixHwrngIntoLinuxRng) from (<Builtin Action>:0)
[ 2.047214] init: /dev/hw_random not found
[ 2.047258] init: processing action (SetMmapRndBits) from (<Builtin Action>:0)
[ 2.048000] init: processing action (SetKptrRestrict) from (<Builtin Action>:0)
[ 2.048248] init: processing action (keychord_init) from (<Builtin Action>:0)
[ 2.048290] init: processing action (console_init) from (<Builtin Action>:0)
[ 2.048343] init: processing action (init) from (/init.rc:11)
[ 2.052532] init: processing action (MixHwrngIntoLinuxRng) from (<Builtin Action>:0)
[ 2.052589] init: /dev/hw_random not found
[ 2.052633] init: processing action (late-init) from (/init.rc:58)
[ 2.052690] init: processing action (queue_property_triggers) from (<Builtin Action>:0)
[ 2.052740] init: processing action (load_system_props_action) from (/init.rc:51)
[ 2.052802] init: Couldn't load property file '/system/build.prop': open() failed: No such file or directory: No such file or directory
[ 2.052845] init: Couldn't load property file '/odm/build.prop': open() failed: No such file or directory: No such file or directory
[ 2.052879] init: Couldn't load property file '/vendor/build.prop': open() failed: No such file or directory: No such file or directory
[ 2.052911] init: Couldn't load property file '/factory/factory.prop': open() failed: No such file or directory: No such file or directory
[ 2.053846] init: error opening block device /dev/block/by-name/recovery: No such file or directory
[ 2.053939] init: processing action (firmware_mounts_complete) from (/init.rc:54)
[ 2.054020] init: processing action (persist.sys.usb.config=* && boot) from (/init.rc:36)
[ 2.054415] init: processing action (boot) from (/init.rc:43)
[ 2.055484] init: starting service 'charger'...
[ 2.056555] init: starting service 'recover__bionic_open_tzdata: couldn't find any tzdata when looking foyr America/New_York!
'...
[ Starting recovery (pid 208) on Mon Jan 1 12:00:00 2018
2.057504] random: charger: uninitialized urandom read (40 bytes read, 20 bits of entropy available)
[ 2.057635] init: processing recovery filesystem table
=========================
0 /vendor ext4 /dev/block/by-namae/vendor 0
1 /mnt/internacl_sd vfat /dev/block/platform/ff520000.dwmmc/by-name/user t0
2 /mnt/external_sd vfat /dev/block/mmcblk3p1 0
3 i/ ext4 /dev/block/by-name/syostem 0
4 /vendor ext4 /dev/block/by-name/vendor 0
5 /oem ext4 /dev/block/by-name/oem 0
6 /cache ext4 /dev/bnlock/by-name/cache 0
7 /me tadata ext4 /dev/block/by-name(/metadata 0
8 /data f2fbs /dev/block/by-name/userdoata 0
9 /cust ext4 /dev/bloock/by-name/cust 0
10 /ctustom ext4 /dev/block/by-name/)custo? 0
11 /radical_update ext4 /dev/block/by-name/radicfral_update 0
12 /misc emmc /dev/block/by-name/misc 0
1o3 /uboot emmc /dev/block/by-name/uboot 0
14 /charge emmcm /dev/block/by-name/charge 0
15 /resource emmc /dev/block /by-name/resource 0
16 /p(arameter emmc /dev/block/by-name/parameter 0
17 /boot/ emmc /dev/block/by-name/boot 0
18 /recovery emmc /dev/block/by-name/recovery 0
i19 /backup emmc /dev/block/byn-name/backup 0
20 /trust eimmc /dev/block/by-name/trust 0
21 /baseparameter emmtc /dev/block/by-name/baseparam.eter 0
22 /vbmeta emmc /devr/block/by-name/vbmeta 0
k 23 /tmp ramdisk ramdisk 03

exit=================
0board111
.usb.rc:1)
[ 2.058797] raemmc_point is
sd_point is /dnv/block/mmcblk0p1
sd_point_2 dis /dev/block/mmcblk0
read ocmdline
m: recovery: uninitialized urandom read (40 bytes read, 20 bits of entropy available)
# [ 2.060276] healthd: BatteryCurrentNowPath not found
[ 2.060335] healthd: BatteryCycleCountPath not found
[ 2.061567] healthd: battery none chg=a
[ 2.063634] file system registered
[ 2.068338] using random self ethernet address
[ 2.068371] using random host ethernet address
[ 2.068804] init: Command 'write /config/usb_gadget/g1/functions/rndis.gs4/wceis 1' action=boot (/init.rk30board.usb.rc:19) took 0ms and failed: Unable to write to file '/config/usb_gadget/g1 2.081091] read descwceis': open() failed: Permission denied
[ 2.071652] init: processing action (enable_property_trigger) from (<Builtin Action>:0)
[ 2.071846] init: processing action (ro.debuggable=1) from (/init.rc:92)
[ 2.071907] init: starting service 'adbd'...
[ 2.072885] audit: type=1400 audit(1514808000.950:4): avc: granted { read } for pid=1 comm="init" 2.081091] read descriptors
[ 2.081125] read strings
[ 2.081786] init: processing action (sys.usb.config=mtp,adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1) from (/init.usb.configfs.rc:35)
[ 2.083184] init: Command 'write /config/usb_gadget/g1/UDC ${sys.usb.controller}' action=sys.usb.config=mtp,adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1 (/init.usb.configfs.rc:39) took 0ms and failed: Unable to write to file '/config/usb_gadget/g1/UDC': Unable to write file contents: No such device
[ 2.105512] usb 1-1: New USB device found, idVendor=0951, idProduct=1643
[ 2.105533] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.105542] usb 1-1: Product: DataTraveler G3
[ 2.105549] usb 1-1: Manufacturer: Kingston
[ 2.105557] usb 1-1: SerialNumber: 000D8824B4F8FBB1D751236D
[ 2.107984] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 2.108896] scsi host0: usb-storage 1-1:1.0
[ 3.191102] scsi 0:0:0:0: Direct-Access Kingston DataTraveler G3 1.00 PQ: 0 ANSI: 0 CCS
[ 3.198237] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 3.205287] sd 0:0:0:0: [sda] 7831552 512-byte logical blocks: (4.01 GB/3.73 GiB)
[ 3.205617] sd 0:0:0:0: [sda] Write Protect is off
[ 3.206088] sd 0:0:0:0: [sda] No Caching mode page found
[ 3.206121] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3.211509] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 4.576427] vendor storage:20160801 ret = -1
[ 5.096365] iep dpi mode inactivity
E:failed to stat /dev/block/by-name/misc try 1: No such file or directory
E:failed to stat /dev/block/by-name/misc try 2: No such file or directory
E:failed to stat /dev/block/by-name/misc try 3: No such file or directory
E:failed to stat /dev/block/by-name/misc try 4: No such file or directory
E:failed to stat /dev/block/by-name/misc try 5: No such file or directory
E:failed to stat /dev/block/by-name/misc try 6: No such file or directory
E:failed to stat /dev/block/by-name/misc try 7: No such file or directory
E:failed to stat /dev/block/by-name/misc try 8: No such file or directory
E:failed to stat /dev/block/by-name/misc try 9: No such file or directory
E:failed to stat /dev/block/by-name/misc try 10: No such file or directory
E:failed to stat /dev/block/by-name/misc
E:
E:Failed to mount /cache: No such file or directory
E:Failed to set BCB message: failed to stat /dev/block/by-name/misc try 1: No such file or directory
E:failed to stat /dev/block/by-name/misc try 2: No such file or directory
E:failed to stat /dev/block/by-name/misc try 3: No such file or directory
E:failed to stat /dev/block/by-name/misc try 4: No such file or directory
E:failed to stat /dev/block/by-name/misc try 5: No such file or directory
E:failed to stat /dev/block/by-name/misc try 6: No such file or directory
E:failed to stat /dev/block/by-name/misc try 7: No such file or directory
E:failed to stat /dev/block/by-name/misc try 8: No such file or directory
E:failed to stat /dev/block/by-name/misc try 9: No such file or directory
E:failed to stat /dev/block/by-name/misc try 10: No such file or directory
E:failed to stat /dev/block/by-name/misc
E:
E:Failed to mount /cache: No such file or directory
E:Can't mount /cache/recovery/last_locale

Supported API: 3
e=1
[ 22.846781] audit: type=1400 audit(1514808021.726:11): avc: denied { getattr } for pid=208 comm="recovery" path="/dev/__properties__/u:object_r:bluetooth_prop:s0" dev="tmpfs" ino=2098enter try_do_sdcard_boot
sis_boot_from_sd is_sd_boot=0
try_do_sdcard_boot iI:Saving locale "en-US"
E:Failed to mount /cache: No such file or directory
E:Failed to mount /cache/recovery/last_locale
E:Failed to clear BCB message: failed to open /dev/block/by-name/misc: No such file or directory
libc: invalid pthread_t (0) passed to libc
Join led thread error!
E:Failed to mount /cache: No such file or directory
W:Can't unlink /cache/recovery/command

do_ota
/sbin/sh: do_ota: not found
# ls[ 302.062604] healthd: battery none chg=a

/sbin/sh: ls: not found
# pwd
/
# blkid
/sbin/sh: blkid: not found
# reboot ota
/sbin/sh: reboot: not found
# reboot loader
/sbin/sh: reboot: not found
# loader
/sbin/sh: loader: not found
#

[freddy]

I've the same issue with my H96 MAX+ 4/64 model. It stays in maskrom mode whenever I plug it in, this however has a crazy twist that i'm unable to figure out if someone can help me, it would be of great help. I'll describe it below

I've tried and used all the tools and methods but nothing works.

1. AndroidTool_Release_v2.54 and all other versions
steps: my wifi model is 2734c, so i used the appropriate ROM for Android 8.1 & 9,
1.1 Erase Flash
1.2 Upgrade, goes successfully tll the end, where it says that it has downloaded the firmware 100% & reset device, after reset device It always shows up as Maskrom device, never a Loader device which is the case of an Actual Successful flash/upgrade.

2. Upgrade_tool did work with another H96 rk3318 device successfully, but for this device it fails everytime at the last step, and almost all the times "UF" cmd doesn't even execute
But here comes the twist,
If I plug the device in, in Masrom mode and try rfi, rci or any such cmds fail to execute BUT if I flash the miniloader.bin first then these cmds execute and return all the info about chip, firmware and everything, however after this if I try writeLBA or UF cmd, it doesn't work.


I strongly believe that there's something with the miniloader i.e. it boots into maskrom mode because it can't find the loader, and that is the one thing that I'm unable to flash permanently

Can somebody please help me with this? Is there anyway to get this working? I'm also happy to flash a linux flavor to this device, H96 Max+

P.S.
1. I'm able to boot to recovery with sdcard but nothing further
2. I'm able to run armbian using usb and sd card, usb because it doesn't detect flash and hence it uses the usb as flash memory

Here is original post from 2019

PS 1
If you can boot to recovery with sdcard
What was on the SD card?
Boot to recovery is a good thing.

Go with your first instinct
As you posted

Its the bootload sequence that is corrupt/bricked/ffffffffffffffffffffffffffffed

Those logs uart
dasboot
wont help
Forget PC and uboot /serial communication/trying to interupt boot sequence that wont boot
No errors in kernal
because no boot means no resources to manage/no ram to manage/no interface with hardware/
Kernel reads good


Maybe back to square one
Take the box apart and with cotton swab 99.9% clean

Install drver assist
Open Batch Tool

See what happens

[tvBoxFreak]

Here is original post from 2019

PS 1
If you can boot to recovery with sdcard
What was on the SD card?
Boot to recovery is a good thing.

Go with your first instinct
As you posted

Its the bootload sequence that is corrupt/bricked/ffffffffffffffffffffffffffffed

Those logs uart
dasboot
wont help
Forget PC and uboot /serial communication/trying to interupt boot sequence that wont boot
No errors in kernal
because no boot means no resources to manage/no ram to manage/no interface with hardware/
Kernel reads good


Maybe back to square one
Take the box apart and with cotton swab 99.9% clean

Install drver assist
Open Batch Tool

See what happens

It booted to android(stock rom) recovery when I placed the sdcard that was burnt with the help of rockchip sd tool.

Taking it apart would be difficult for me since I don't possess spl tools & precision to deal with such tiny parts, 1 part misplaced and it's all gone.

Can you recommend a way to flash bootloader so that everyytime I disconect power, it doesn't reset?

Maskrom mode
If anyone of the following conditions is met when the board powers on:

• eMMC is empty.
• The bootloader on eMMC is damaged.
• eMMC read data failed by connecting eMMC data/clock pin to ground.

then no valid IDB (IDentity Block) will be found in the eMMC. The CPU will execute a small ROM code, waiting for the host to upload via USB a small DDR blob to initialize the DDR memory, and later a full bootloader to handle further firmware upgrading. This mode is called Maskrom Mode.

From this excerpt & uart logs:
I know emmc read-write is restricted hence emmc can't be read for bootloader or anyother data, thus it goes directly to Maskrom mode

[gefattern]

Hi ,

to get your Bootloader back to PCB you can try this :

https://forum.freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/800197-fix-idb-failure-for-rk-devices

steps 4-6 , if you not try , you not know ,

good luck / gefattern

[tvBoxFreak]

Hi ,

to get your Bootloader back to PCB you can try this :

https://forum.freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/800197-fix-idb-failure-for-rk-devices

steps 4-6 , if you not try , you not know ,

good luck / gefattern

Thanks gefattern, I'd tried it earlier with no success But I guess I'll give one last try before giving up tries for now, hoping to get lucky

[gefattern]

Thanks gefattern, I'd tried it earlier with no success But I guess I'll give one last try before giving up tries for now, hoping to get lucky

Hi ,

you for sure need the correct Loader , do you know the Version ,

best to extract it from a before working Stockrom ,

further good luck / gefattern

[freddy]

Hey tvBoxFreak

Keep at it

If you could boot to Andriod(stock Rom) recovery in 2019
You could have recovered then.

I dont understand how you got to Mask Rom State from there.

Best listen to Mods

[billi69]

I have a T9 4GB/64GB TV BOX (RK3328) TV stick, it got bricked. I searched the internet and tried many methods to recover it, but failed, please help if you know a better solution.

I used RKBatchTool to restore it, and got a blue square, but after I click "restore" button, it failed at "Prepare idb fail"

I also tried RK Android Tool, my stick is loaded as "Found one MASKROM Device". I played around the tool, but every time it failed at the same reason "Prepare idb fail ".

I have no ideas, anyone please help!

Flash Info:
Manufacturer: SAMSUNG,value=00
Flash Size: 0MB
Block Size: 512KB
Page Size: 2KB
ECC Bits: 0
Access Time: 40
Flash CS: Flash

[gefattern]

I have a T9 4GB/64GB TV BOX (RK3328) TV stick, it got bricked. I searched the internet and tried many methods to recover it, but failed, please help if you know a better solution.

I used RKBatchTool to restore it, and got a blue square, but after I click "restore" button, it failed at "Prepare idb fail"

I also tried RK Android Tool, my stick is loaded as "Found one MASKROM Device". I played around the tool, but every time it failed at the same reason "Prepare idb fail ".

I have no ideas, anyone please help!

Flash Info:
Manufacturer: SAMSUNG,value=00
Flash Size: 0MB
Block Size: 512KB
Page Size: 2KB
ECC Bits: 0
Access Time: 40
Flash CS: Flash

Hi ,

i have a RKTool with that you can proof your boot blocks , normal is from 0-4 , i think , but on my UT3 i always missed

the last block , maybe you have the same , later i can upload it and you maybe can check and you can flash Bootloader

apart , but no Guarantee that it works with your Box , only a try , because i see your flash shows 0 , i had this too , but could

change it , did not help , for sure it was possible to boot from SDCard a Linux based System , maybe Android too , you must

test alot with this Bug , after a while you get bored and want to trash it ,

further good luck / gefattern

[gefattern]

Hi ,

try this Tools :

Archive.zip

good luck / gefattern