魔百盒cm101s和unt400b 求资源
我看了不少UNT400B的刷机帖子,之前刷了一个芒果Q的固件,前几天突然停在中国移动LOGO界面,使用CPU短接和两个孔短接都进入不了机器人。不知道是不是能否用TTL救? 因为这个机顶盒坏了,所以回家拿了一个移动的cm101s emmc 8223的,看了教程,安装了当贝市场和桌面,也提高权限和开机启动,然后有个问题,因为换了网络,一直再显示下发数据,就算当贝桌面启动之后,也启动不了程序。这种情况是不是要烧录?然而论坛的固件很多,我不知道哪个才能用,怕刷成砖头了。UNT400B救砖 要么就是你说的 强刷救砖,要么就是用烧录文件进行救砖
CM101s 8223 板子拍照然后ttl下跑马看看内存芯片是NAND还是emmc的 才能判断 hao501802766 发表于 2018-3-26 10:40
UNT400B救砖 要么就是你说的 强刷救砖,要么就是用烧录文件进行救砖
CM101s 8223 板子拍照然后ttl下跑马 ...
谢谢超版,交流群里有人说过 我是因为刷机包不对才导致unt400b没有提示机器人,我在论坛的安装教程下载了固件,中午再回家试试~~不行估计要TTL烧录了,cm101s 8223 我昨晚ttl连接了 显示emmc的内存,请问在哪里有固件 版主,图片在此 hao501802766 发表于 2018-3-26 10:40
UNT400B救砖 要么就是你说的 强刷救砖,要么就是用烧录文件进行救砖
CM101s 8223 板子拍照然后ttl下跑马 ...
版主,我拍照了,麻烦您看一下 hao501802766 发表于 2018-3-26 10:40
UNT400B救砖 要么就是你说的 强刷救砖,要么就是用烧录文件进行救砖
CM101s 8223 板子拍照然后ttl下跑马 ...
Bootrom start
Boot from eMMC
Starting fastboot ...
System startup
DDRS
Reg Version:v1.1.0
Reg Time: 2016/7/6 15:22:53
Reg Name: hi3798mdmo1g_hi3798mv100_ddr3_1gbyte_16bitx2_4layers_8Q40E_emmc.re
g
Jump to DDR
Fastboot 3.3.0 (liuyunlei@server180) (Jul 06 2016 - 15:37:08)
Fastboot: Version 3.3.0
Build Date: Jul6 2016, 15:38:08
CPU: Hi3798Mv100
Boot Media: eMMC
DDR Size: 1GB
Check nand flash controller v610. found
Special NAND id table Version 1.36
Nand ID: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
No NAND device found!!!
MMC/SD controller initialization.
MMC/SD Card:
MID: 0x70
Read Block:512 Bytes
Write Block: 512 Bytes
Chip Size: 7296M Bytes (High Capacity)
Name: "M7280"
Chip Type: MMC
Version: 4.0
Speed: 52000000Hz
Bus Width: 8bit
Boot Addr: 0 Bytes
HI_OTP_LockIdWord,327: ID_WORD have already been locked
SDK Version: HiSTBAndroidV600R001C00SPC064_v2016060803
begin
begin
partition addr :
BaseAddress:0x200000, DataSize:0x100000, offset:0x0, b
ytes:0xb10
cksum , ptable->checksum
data at 0xd1ec is ok
BaseAddress:0x300000, DataSize:0x100000, offset:0x0, b
ytes:0xb10
cksum , ptable->checksum
0 fastboot 0x000000000 0x000200000
0 partition 0x000200000 0x000200000
0 recovery 0x000400000 0x001000000
0 deviceinfo 0x001400000 0x000200000
0 baseparam 0x001600000 0x000800000
0 pqparam 0x001E00000 0x000800000
0 logo 0x002600000 0x000800000
0 fastplay 0x002E00000 0x002800000
0 boot 0x005600000 0x001000000
0 misc 0x006600000 0x000200000
0 userapi 0x006800000 0x000800000
0 hibdrv 0x007000000 0x000800000
0 qbflag 0x007800000 0x000800000
0 qbdata 0x008000000 0x012C00000
0 system 0x01AC00000 0x027000000
0 cache 0x041C00000 0x019000000
0 swdb 0x05AC00000 0x003000000
0 userdata 0x05DC00000 0x149C00000
ptable info:2M(fastboot),2M(partition),16M(recovery),2M(deviceinfo),8M(baseparam
),8M(pqparam),8M(logo),40M
(fastplay),16M(boot),2M(misc),8M(userapi),8M(hibdrv),8
M(qbflag),300M(qbdata),624M(system),400M(cache),48M
(swdb),5276M(userdata)
ok
begin
deviceinfo addr :
BaseAddress:0x1400000, DataSize:0x100000, offset:0x0,
bytes:0x514
start...
ok,checksum:0x9482
data at 0x001400000 is ok
count: name: value:
count: name: value:
count: name: value:
count: name: value:
ok
BaseAddress:0x5600000, DataSize:0x100000, offset:0x0,
bytes:0x2000
tmp_cmdline:mem=1Gconsole=ttyAMA0,115200 lpj=974848 quiet blkdevparts=mmcblk0
:
use boot cmdline,enable serial, cmdline:[mem=1Gconsole=ttyAMA0,115200 lpj=9748
48 quiet
blkdevparts=mmcblk0:]
get standard swstandard:1080p_50Hz g_auto_adp:0
bootargs:[mem=1Gconsole=ttyAMA0,115200 lpj=974848 quiet blkdevparts=mmcblk0:2M
(fastboot),2M
(partition),16M(recovery),2M(deviceinfo),8M(baseparam),8M(pqparam),
8M(logo),40M(fastplay),16M(boot),2M
(misc),8M(userapi),8M(hibdrv),8M(qbflag),300M
(qbdata),624M(system),400M(cache),48M(swdb),5276M(userdata)
androidboot.force_op
en_console=none androidboot.mac=60:31:3B:29:D1:59 androidboot.standard=1080p_50H
z
androidboot.serialno=005001FF0001181001A460313B29D159]
sw_ir_detect_recovery begin500 count
sw_ir_detect_recovery ok
BaseAddress:0x6600000, DataSize:0x100000, offset:0x0,
bytes:0x10000
boot normal!!!
bootimg now: mmc read 0 0x1FFFFC0 2b000 8000;bootimg 0x1FFFFC0
ok
SDK Version: HiSTBAndroidV600R001C00SPC064_v2016060803
Reserve Memory
Start Addr: 0xFFFE000
Bound Addr: 0x8D4A000
FreeAddr: 0xF14D000
Alloc Block:Addr Size
0xFBFD000 4194304
0xF8FC000 3145728
0xF8F9000 8192
0xF8C4000 212992
0xF7C3000 1048576
0xF7BF000 12288
0xF5FC000 1843200
0xF466000 1658880
0xF2A3000 1843200
0xF150000 1384448
0xF14D000 8192
Hibernate!! drvphyaddr 0xFC00000
Hibernate!! user api phyaddr 0xF900000
Hibernate!! userapistart 0x6800000, size 0x800000
Hibernate!! drvstart 0x7000000, size 0x800000
Hibernate!! flag start 0x7800000, size 0x800000
Hibernate!! data start 0x8000000, size 0x12C00000
begin
open loader keyed
Press Ctrl+C to stop autoboot
MMC read: dev # 0, block # 176128, count 32768 ... 32768 blocks read: OK
87274664 Bytes/s
kernel@ 3e08000 (7887464 bytes)
ramdisk @ 4e00000 (650555 bytes)
page size @ 2048 bytes
initrd rd_start = 4e00000,rd_end = 4e9ed3b
## Booting kernel from Legacy Image at 020007c0 ...
Image Name: Linux-3.10.0_s40
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 7887400 Bytes = 7.5 MiB
Load Address: 02000000
Entry Point:02000000
XIP Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 1.265485] libphy: PHY himii:1f not found
[ 1.515241] >>>init /autoci02/home/projects/ANDROID-Hi3798M-SPC060-EMMC-kk-
4.4/device/hisilicon/bigfish/sdk/source/kernel/linux-3.10.y/drivers/usb/usbir/us
b-ir.cusb_usbir_init
[ 2.078326] init: /init.rc: 65: invalid command '//mkdir'
[ 2.083898] init: /init.rc: 171: invalid command '//mount'
[ 2.089507] init: /init.rc: 235: invalid command '//chown'
[ 2.095039] init: /init.rc: 236: invalid command '//chmod'
[ 2.101928] init: /init.bigfish.rc: 80: invalid option 'sdcard_r'
[ 2.211240] init: /dev/hw_random not found
[ 2.215776] init: cannot open '/initlogo.rle'
[ 2.310493] init: e2fsck /dev/block/platform/hi_mci.1/by-name/userdata
[ 2.525308] init: e2fsck /dev/block/platform/hi_mci.1/by-name/swdb
[ 2.544817] init: e2fsck /dev/block/platform/hi_mci.1/by-name/cache
[ 2.572552] init: /dev/hw_random not found
[ 2.585649] init: type = 0x5
[ 2.588638] init: reg_value = 0x5
[ 2.639509] init: name:serialno,value:005001FF000
1181001A460313B29D159init:
name:mac,value:60:31:3B:2
9:D1:59init:
name:standard,value:1080p_50Hzinit: [se
t_devinfo_properties,660]name:secureline,value:1001[ 2.670424]
healthd: No ch
arger supplies found
[ 2.673537] init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
[ 2.674041] init: cannot find '/system/etc/install-recovery.sh', disabling 'f
lash_recovery'
[ 2.676854] init: cannot find '/system/bin/mtkbt', disabling 'blueangel'
[ 2.679622] init: cannot find '/system/bin/dtvserver', disabling 'dtvserver'
[ 2.679666] init: cannot find '/system/bin/gpio-led', disabling 'gpio-led'
[ 2.680146] init: cannot find '/system/bin/usb-driver', disabling 'usb-driver
'
[ 2.682303] init: property 'sys.powerctl' doesn't exist while expanding '${sy
s.powerctl}'
[ 2.682313] init: powerctl: cannot expand '${sys.powerctl}'
[ 2.682329] init: property 'sys.sysctl.extra_free_kbytes' doesn't exist while
expanding
'${sys.sysctl.extra_free_kbytes}'
[ 2.682337] init: cannot expand '${sys.sysctl.extra_free_kbytes}' while writi
ng to
'/proc/sys/vm/extra_free_kbytes'
init: cannot find '/system/bin/rild', disabling 'ril-daemon'
root@Hi3798MV100:/ # [ 16.368026] init: untracked pid 3012 exited
[ 16.446082] init: untracked pid 3018 exited
[ 16.507804] init: sys_prop: permission denied uid:1014name:net.default.stat
us
[ 16.516006] init: sys_prop: permission denied uid:1014name:net.default.auth
[ 19.095647] init: sys_prop: permission denied uid:1014name:net.default.stat
us
[ 19.103313] init: sys_prop: permission denied uid:1014name:net.default.auth
[ 29.988945] init: untracked pid 3217 exited
[ 30.047651] init: untracked pid 3224 exited
[ 31.500650] init: sys_prop: permission denied uid:1000name:java.net.preferI
Pv4Stack
[ 31.509317] init: sys_prop: permission denied uid:1000name:java.net.preferI
Pv6Addresses
[ 49.059744] init: untracked pid 3640 exited
[ 74.409663] init: untracked pid 1659 exited
init: untracked pid 4203 exited
init: untracked pid 3643 exited
TTL连接后的数据 hao501802766 发表于 2018-3-26 10:40
UNT400B救砖 要么就是你说的 强刷救砖,要么就是用烧录文件进行救砖
CM101s 8223 板子拍照然后ttl下跑马 ...
cm101s的问题不大,已经自行解决,连续两晚到这个时间,unt400b基本知道原因,还是fastboot丢失了,给你一个图看看,现在的问题是TTL线乱码,都无法识别,不知道版主有何高招 可怕了图片成这样 我有个同样的CM101s,WIFI一直不能使用,刷过好多版本的固件都不行,请问楼主刷的是什么版本的 whc78 发表于 2018-3-27 15:39
我有个同样的CM101s,WIFI一直不能使用,刷过好多版本的固件都不行,请问楼主刷的是什么版本的 ...
用龙猫tv
页:
[1]
2