擦除Flash屡次"准备IDB失败" [已解决]
本帖最后由 饿客登门 于 2017-3-25 13:04 编辑之前用TTL2USB板查看Android环境下都有什么，结果糊里糊涂的就执行了跳转到Linux环境下的某个脚本（想不起来是哪个了），然后就弄不回去了。
然后尝试用AndroidTool 2.38（还有其它瑞芯微的工具也试了）刷3月18号出的固件，
因为新接触，单独刷分区的没敢弄，只尝试刷update.img的方式，但屡次"准备IDB失败"！
把Log贴上，麻烦版大看看，究竟该怎么办才好，如果把整个emmc空间置零，这样算擦除IDB吗？
20:57:17 294 Android开发工具 v2.3.8.0 start run
20:57:46 994 Layer<7-2>:测试设备开始
20:57:46 999 Layer<7-2>:测试设备成功
20:57:47 001 Layer<7-2>:获取FlashInfo开始
20:57:47 003 <LAYER 7-2> INFO:FlashInfo: 00 E0 A3 03 00 04 04 00 28 00 01
20:57:47 004 <LAYER 7-2> INFO:GetFlashInfo-->Emmc storage.
20:57:47 007 Layer<7-2>:获取FlashInfo成功
20:57:47 010 Layer<7-2>:准备IDB开始
20:57:47 011 <LAYER 7-2> INFO:CS(1) (29820MB) (SAMSUNG)
20:57:47 013 Error:RKU_Read-->ReadFile failed,bRet=0,err=31,size=2112,read=0
20:57:49 015 INFO:RKU_ResetPipe-->DeviceIoControl OK
20:57:54 017 Error:RKU_Read-->ReadFile failed,bRet=1,err=0,size=2112,read=0
20:57:54 018 <LAYER 7-2> ERROR:FindIDBlock-->RKU_ReadSector failed,RetCode(-4)
20:57:54 019 <LAYER 7-2> ERROR:PrepareIDB-->FindAllIDB failed
20:57:54 021 Error:Layer<7-2>:准备IDB失败
最后按照版主的思路解决了问题，确实只要进入MaskRom模式就可以做任何事，但我这边的情况之前是把USB线插在延长线上了（受物理条件所限），所以AndroidTool总是报错，后来把线直接插在机箱后IO面板上才一切正常，所以这里总结：一定不能把USB线插在转接线或延长线上！
新人，本着尝试各种方法刷，结果现在真的刷出问题了，所以急需能"擦除Flash"的方法。
用TTL2USB转接板，查看Log，如下：
DDR Version 1.07 20161103
In
Channel 0: DDR3, 666MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: DDR3, 666MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg = 0x3AA17AA1, stride = 0xD
OUT
Boot1: 2016-07-29, version: 1.05
CPUId = 0x0
ChipType = 10 1847
SdmmcInit=2 0
BootCapSize=100000
UserCapSize=29820MB
FwPartOffset=2000 , 100000
SdmmcInit=0 0
BootCapSize=0
UserCapSize=14804MB
FwPartOffset=2000 , 0
StorageInit ok = 65867
LoadTrustBL
No find bl30.bin
No find bl32.bin
theLoader 200000 139639
LoaderFlag2: 0x0
NOTICE:BL31: v1.2(debug):e1a1ee4
NOTICE:BL31: Built : 14:38:26, Sep 29 2016
INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO: plat_rockchip_pmu_init(1202): pd status 3e
INFO: BL31: Initializing runtime services
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2014.10-RK3399-10 (Mar 16 2017 - 17:31:00)
CPU: rk3399
CPU's clock information:
aplll = 816000000HZ
apllb = 24000000HZ
gpll = 594000000HZ
aclk_periph_h = 148500000HZ, hclk_periph_h = 74250000HZ, pclk_periph_h = 37125000HZ
aclk_periph_l0 = 99000000HZ, hclk_periph_l0 = 99000000HZ, pclk_periph_l0 = 49500000HZ
hclk_periph_l1 = 99000000HZ, pclk_periph_l1 = 49500000HZ
cpll = 800000000HZ
dpll = 660000000HZ
vpll = 24000000HZ
npll = 24000000HZ
ppll = 676000000HZ
Board: Rockchip platform Board
Uboot as second level loader
DRAM:Found dram banks: 1
Adding bank:0000000000200000(00000000ffe00000)
128 MiB
SdmmcInit = 0 0
SDCard Update.
storage init OK!
Using default environment
GetParam
remotectl v0.1
pwm freq=0xb8320
pwm_freq_nstime=0x52d
Load FDT from boot image.
power key: bank-0 pin-5
usb bc: can find node by path: /dwc-control-usb/usb_bc
pmic:rk808
can't find dts node for pwm1
set pwm voltage ok,pwm_id =2 vol=1000000,pwm_value=33
SecureBootEn = 0, SecureBootLock = 0
#Boot ver: 0000-00-00#0.00
empty serial no.
normal boot.
no fuel gauge found
no fuel gauge found
read logo on state from dts
rk fb dt: can't find node '/display-timings'
no fuel gauge found
'recovery' does not seem to be a partition nor an address
Unable to boot:recovery
try to start backup
ERROR: : bootrk: bad boot or kernel image
Unable to boot:backup
try to start rockusb
强行进入 MaskRom可以前行清空EMMC，需要硬件操作，有一定风险，因此仅在设备进入不了 Loader 模式、SD 卡启动也失效的情况下，方可尝试 MaskRom 模式。
进入MaskRom模式的方法：
Firefly-RK3399 MaskRom模式：
http://wiki.t-firefly.com/index.php/Firefly-RK3399/MaskRom
Firefly-RK3288 MaskRom模式：
http://wiki.t-firefly.com/index.php/Firefly-RK3288 /MaskRom
FirePrime MaskRom模式：
http://wiki.t-firefly.com/index.php/FirePrime /MaskRom 另外，还有个问题，从SD启动，有什么条件吗？如何操作？ HDMI也不能接，接上也会出现IDB失败
页:
[1]