Posts by Ahmad alarjan

Ahmad alarjan · May 24th 2025

Code

System startup


Relocate Boot

Jump to C code


Fastboot 3.3.0 (zhangtq@define-ThinkStation-P300) (Dec 18 2020 - 17:51:12)

Fastboot:      Version 3.3.0
Build Date:    Dec 18 2020, 17:51:45
CPU:           Hi3798Mv200
Boot Media:    eMMC
DDR Size:      256MB

Found flash memory controller hifmc100.
no found nand device.

MMC/SD controller initialization.
MMC/SD Card:
    MID:         0x15
    Read Block:  512 Bytes
    Write Block: 512 Bytes
    Chip Size:   7456M Bytes (High Capacity)
    Name:        "8GTF4R"
    Chip Type:   MMC
    Version:     5.1
    Speed:       52000000Hz
    Mode:        DDR50
    Voltage:     3.3V
    Bus Width:   8bit
    Boot Addr:   0 Bytes
(Re)start USB...
USB0:   Register 1212 NbrPorts 2
USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
USB0:   Register 2000140 NbrPorts 2
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
reading bootargs.bin
bootargs.bin on device:usb:0:1 FOUND!
reading bootargs.bin from 0
...Net:   eth0 phymdio(31) invalid, use default:0
upWarning: failed to set MAC address
, downWarning: failed to set MAC address
, gmac0Warning: failed to set MAC address


Boot Env on eMMC
    Env Offset:          0x00100000
    Env Size:            0x00010000
    Env Range:           0x00010000
start download process.


SDK Version: HiSTBLinuxV100R005C00SPC052_20180124

keyled repeat init
MAC:D0:27:29:0F:A2:89
count=0
(Re)start USB...
USB0:   Register 1212 NbrPorts 2
USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
USB0:   Register 2000140 NbrPorts 2
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
(Re)start USB...
USB0:   Register 1212 NbrPorts 2
USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
USB0:   Register 2000140 NbrPorts 2
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
reading bootargs.bin
bootargs.bin on device:usb:0:1 FOUND!
reading bootargs.bin from 0
...reading apploader.bin
apploader.bin on device:usb:0:1 FOUND!
reading apploader.bin from 0
................................................................................                                                                                                                                                                                                                                             ................................................................................                                                                                                                                                                                                                                             ................................................................................                                                                                                                                                                                                                                             ................................................................................                                                                                                                                                                                                                                             ................................................................................                                                                                                                                                                                                                                             ................................................................................                                                                                                                                                                                                                                             ................................................................................                                                                                                                                                                                                                                             ................................................................................                                                                                                                                                                                                                                             .........................## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-4.4.35_hi3798mv2x
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    13631971 Bytes = 13 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
   Loading Kernel Image from 0x16777280 to 0x33554432 ... OK
OK
ATAGS [0x00000100 - 0x0000047C], 892Bytes

Starting kernel ...

Display More

Ahmad alarjan · May 24th 2025

Code

*** irq: data abort
data abort
pc : [<600001d3>]          lr : [<00c9991c>]
sp : 00bfffb8  ip : 00d4d134     fp : 00d4d780
r10: d0008d80  r9 : 00d4d6c0     r8 : 005fffe0
r7 : 00001387  r6 : d8529680     r5 : 029003e8  r4 : e64d03e8
r3 : 012cc0ec  r2 : 01293ed0     r1 : fed33f13  r0 : 012cc0ec
Flags: nzCV  IRQs off  FIQs on  Mode UK4_26
Resetting CPU ...

resetting ...
*** CPU will be re▒
Bootrom start
Boot Media: eMMC

Enter usb bootstrap by flash

Usb disk(1):
Decrypt auxiliary code ...OK
Enter boot auxiliary code

Auxiliary code - v1.00
DDR code - V1.1.2 20160205
Build: Nov 29 2017 - 19:57:41

Reg Version:  v1.6.0\
Reg Time:     2020/12/18 11:01:01
Reg Name:     hi3798mv2dma_hi3798mv200_DDR3-1866_1GB_16bitx2_2layers.reg

Boot auxiliary code success
Bootrom success


System startup


Relocate Boot

Jump to C code


Fastboot 3.3.0 (zhangtq@define-ThinkStation-P300) (Dec 18 2020 - 17:51:12)

Fastboot:      Version 3.3.0
Build Date:    Dec 18 2020, 17:51:45
CPU:           Hi3798Mv200
Boot Media:    eMMC
DDR Size:      256MB

Found flash memory controller hifmc100.
no found nand device.

MMC/SD controller initialization.
MMC/SD Card:
    MID:         0x15
    Read Block:  512 Bytes
    Write Block: 512 Bytes
    Chip Size:   7456M Bytes (High Capacity)
    Name:        "8GTF4R"
    Chip Type:   MMC
    Version:     5.1
    Speed:       52000000Hz
    Mode:        DDR50
    Voltage:     3.3V
    Bus Width:   8bit
    Boot Addr:   0 Bytes
(Re)start USB...
USB0:   Register 1212 NbrPorts 2
USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
USB0:   Register 2000140 NbrPorts 2
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
reading bootargs.bin
bootargs.bin on device:usb:0:1 FOUND!
reading bootargs.bin from 0
...Net:   eth0 phymdio(31) invalid, use default:0
upWarning: failed to set MAC address
, downWarning: failed to set MAC address
, gmac0Warning: failed to set MAC address


Boot Env on eMMC
    Env Offset:          0x00100000
    Env Size:            0x00010000
    Env Range:           0x00010000
start download process.


SDK Version: HiSTBLinuxV100R005C00SPC052_20180124

keyled repeat init
MAC:D0:27:29:0F:A2:89
count=4
Call [HI_Flash_OpenByName] return [0x00A00122]
reading STARTUP_ONCE
reading STARTUP
STARTUP: boot emmcflash0.linuxkernel1 'root=/dev/mmcblk0p16 rootsubdir=linuxrootfs1 rootfstype=ext4 kernel=/dev/mmcblk0p12 userdataroot=/dev/mmcblk0p16 userdatasubdir=userdata1 blkdevparts=mmcblk0:1M(boot),1M(bootargs),1M(bootoptions),3M(baseparam),4M(pqparam),4M(logo),4M(deviceinfo),4M(softwareinfo),4M(loaderdb),32M(loader),8M(trustedcore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata)'

Error Code: [0x00A00119]
Call [loaderPartitionRead] return [0x00A00119]
LOADING KERNEL(linuxkernel1) fail
Reserve Memory
    Start Addr:          0xFFFE000
    Bound Addr:          0x8D85000
    Free  Addr:          0xEE45000
    Alloc Block:  Addr         Size
                  0xFBFD000   0x400000
                  0xF8FC000   0x300000
                  0xF8F9000   0x2000
                  0xF878000   0x80000
                  0xF7D5000   0xA2000
                  0xEFEB000   0x7E9000
                  0xEFE7000   0x3000
                  0xEE51000   0x195000
                  0xEE47000   0x9000
                  0xEE45000   0x1000

Press Ctrl+C to stop autoboot

MMC read: dev # 0, block # 135168, count 65536 ... 65536 blocks read: OK

88467517 Bytes/s
Wrong Image Format for bootm command
ERROR: can't get kernel image!
fastboot# *** irq: data abort
Unknown command '***' - try 'help'
fastboot# data abort
Unknown command 'data' - try 'help'
fastboot# pc :       lrp : d780
Unknown command 'pc' - try 'help'
fastboot# r10:08d89 :d852    : 03e8 : e63e8
Unknown command 'r10:08d89' - try 'help'
fastboot# : 01ec   0RQs o FIQ   UK4_eset C..
Unknown command ':' - try 'help'
fastboot#
fastboot# rting
Unknown command 'rting' - try 'help'
fastboot# *btraniy ci 0
Unknown command '*btraniy' - try 'help'
fastboot# D-0e 101
Unknown command 'D-0e' - try 'help'
fastboot# m8iauxile
Unknown command 'm8iauxile' - try 'help'
fastboot# rom s
Unknown command 'rom' - try 'help'
fastboot# zhan   Vet  DeC    odia: 56MB
Unknown command 'zhan' - try 'help'
fastboot#
fastboot# ytrtionCCa
Unknown command 'ytrtionCCa' - try 'help'
fastboot#  k:  ecity R"
Unknown command 'k:' - try 'help'
fastboot#  :eoDa B8 r(tSe1
Unknown command ':eoDa' - try 'help'
fastboot# 0
Unknown command '0' - try 'help'
fastboot# i i
ir - IR command:

Usage:
ir ir read @cnt @timeout: get RC key pressed, read @cnt keys.
     and each key can wait @timeout ms.
ir start: open ir module.
ir stop: close ir module.
ir set up @0|1: set ir driver report up event or not.
     @0: do not report. @1: report up event.
ir set hold @0|1 : set ir driver report hold event or not.
     @0: do not report. @1: report hold.
ir set hi @time: set the HOLD event report interval time. unit ms
ir reset : reset ir module, which will clear buffers, restart ir IP.
ir enable @protocol_name: enable protocol specified by @protocol_name.
ir disable @protocol_name: disable protocol specified by @protocol_name.
ir status @protcol_name: display the enable/disable status of @protocol_name.
fastboot# i4r,)e)'
Unknown command 'i4r,)e)' - try 'help'
fastboot#  NELuRve ry
Unknown command 'NELuRve' - try 'help'
fastboot# :   xAddr   05    cck:d    z        F0  0
Unknown command ':' - try 'help'
fastboot#        x20    878 000    D50
Unknown command 'x20' - try 'help'
fastboot#      00
Unknown command '00' - try 'help'
fastboot#    0
Unknown command '0' - try 'help'
fastboot#    r d t eOK
Unknown command 'r' - try 'help'
fastboot#
fastboot# bootm 0x1000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
fastboot#

Display More

Ahmad alarjan · May 23rd 2025

Quote from kitte888

the box have 3 slots for images

have you install more images , slot 1 or slot 2

"Actually, I performed the full 'Ears All' process using the HiTool software, which completely wiped the device. Now I’m looking for the essential files needed to get the device working again. I’ve flashed several firmware images via HiTool, but the device only reaches the 'Boot' screen and doesn’t load the image."

Ahmad alarjan · May 23rd 2025

Quote from kitte888

Do you have other images installed in the slot? Can you still access the box with Putty? You can copy the boot slot to boot a different image.

how?

Ahmad alarjan · May 23rd 2025

I need these files

Ahmad alarjan · May 23rd 2025

Quote from Hannibal_Lecter

all written here klick me

I have already completed all the steps, but I was unsuccessful in flashing the device's firmware. I tried using USB drives of 2GB, 4GB, and 8GB capacities, but the process still failed. What I need are the specific files for the device to flash it using the HiTool software, but I have not been able to find these files.

Ahmad alarjan · May 23rd 2025

????

Ahmad alarjan · May 22nd 2025

؟؟

Ahmad alarjan · May 22nd 2025

The process was unsuccessful using USB drives of 2GB, 4GB, and 8GB—the device gets stuck on the 'boot' screen and does not start. As for the HiTool software, it does recognize the device, but I need the specific repair file for this device. I have tried all available files without success. I need a dedicated file specifically for this device

Quote from kegnkiwi

Just out of interest have you tried the recovery menu option but having removed all sata and usb drives?

Ahmad alarjan · May 22nd 2025

؟؟؟؟؟؟؟؟؟؟؟؟

Ahmad alarjan · May 22nd 2025

Hello, my friends. I am in urgent need of a recovery file to be used with the HiTools software. I’ve searched extensively online but haven’t been able to find it. My device has been stuck on the "boot" screen for over a year, and I haven’t been able to locate the proper recovery files. I kindly ask you to provide me with the required recovery file so I can repair the device using HiTools. Your help would be greatly appreciated.

Ahmad alarjan · Sep 10th 2023

This method did not work for all images

Ahmad alarjan · Sep 10th 2023

??????

Ahmad alarjan · Sep 10th 2023

Please help me

Ahmad alarjan · Sep 10th 2023

I want to help my device is standing on the word Bot please help it does not accept any image

2023-09-10_085727.png

2023-09-10_085748.png

Posts by Ahmad alarjan

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

Recovery Gigablue Trio UHD using HiTool

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

I need the recovery file for the Gigablue UHD Trio 4K device via the Hirools software

Help for me fix receiver stop for boot

Help for me fix receiver stop for boot

Help for me fix receiver stop for boot

Help for me fix receiver stop for boot