Quote:
Originally Posted by rvcjew
The erasing step is what should be happening, […]. It should flash, erase, say updating system with a bar going across (this might only be OTAs) then boot like normal for like I'd say only 10 minutes max then be at the setup screen like when it was new.
|
OK, thx, so I shouldn't have any black screen
n.b.: just after the "erasing" under the circle, it looks like to reboot (really fast white screen), then I can see the picture of the bridge with "likebook starting up..." for ~1 or 2 seconds, then the black screen appears, so I guess it fails when it tries to read the kernel? or it succeed but with a wrong output screen?
I've seen in the parameter.txt "androidboot.console=ttyFIQ0" but it was "ttyS2" before trying to install android 8.1, like in my first post, but I guess that it is not the problem if the image works for others.
Quote:
|
Does it make a log saying what it flash from that img?
|
yes it does :
Code:
$ cat log/log2021-05-06.txt
14:18:14 Upgrade Tool ver 1.24
14:18:14 Test Device Start
14:18:14 Test Device Success
14:18:14 Check Chip Start
14:18:14 Check Chip Success
14:18:14 Get FlashInfo Start
14:18:14 <LAYER 1-1> INFO:FlashInfo: 0 0 CD 1 0 4 4 0 28 0 1
14:18:14 Get FlashInfo Success
14:18:14 Prepare IDB Start
14:18:14 <LAYER 1-1> INFO:CS(1) (14752MB) (SAMSUNG)
14:18:14 Prepare IDB Success
14:18:14 Download IDB Start
14:18:14 Download IDB Success
14:18:14 Reset Device Start
14:18:16 Reset Device Success
14:18:16 Wait For Loader Start
14:18:17 Wait For Loader Success
14:18:17 Test Device Start
14:18:17 Test Device Success
14:18:17 Download Firmware Start
14:18:17 <LAYER 1-1> INFO:Start to download trust,offset=0x4000,size= 4194304
14:18:18 <LAYER 1-1> INFO:Start to download uboot,offset=0x2000,size= 4194304
14:18:20 <LAYER 1-1> INFO:Start to download misc,offset=0x8000,size= 49152
14:18:20 <LAYER 1-1> INFO:Start to download resource,offset=0xa000,size= 251904
14:18:20 <LAYER 1-1> INFO:Start to download kernel,offset=0x12000,size= 21174292
14:18:27 <LAYER 1-1> INFO:Start to download boot,offset=0x22000,size= 22941696
14:18:35 <LAYER 1-1> INFO:Start to download recovery,offset=0x32000,size= 30859264
14:18:45 <LAYER 1-1> INFO:Start to download system,offset=0x18c000,size= 1345618164
14:26:20 <LAYER 1-1> INFO:Start to download vendor,offset=0x594000,size= 242786464
14:27:43 <LAYER 1-1> INFO:Start to download oem,offset=0x696000,size= 360596
14:35:25 Download Firmware Success
14:35:25 Reset Device Start
14:35:27 Reset Device Success
(n.b. for this one I used another version of upgrade_tool with the new update.img from below, but it was the same with the previous version (of software and image))
all .img that are in the update_xxx.img are seems to be correctly uploaded (according to the dump from imgRePackerRK) :
Code:
update-10456.img.dump/Image-rk3368# du -b *
22941696 boot.img
21174280 kernel.img
21174292 kernel.img.krnl
237902 MiniLoaderAll.bin
49152 misc.img
360596 oem.img
887 parameter.txt
899 parameter.txt.parm
30859264 recovery.img
251904 resource.img
1345618164 system.img
4194304 trust.img
4194304 uboot.img
242786464 vendor.img
Quote:
|
Looking at the link you sent about the tool it sounds like it only understands perhaps 4 of the like 10 img files it would be flashing that's is inside the main img. It might just be to OLD of an app perhaps. It does sound like it thinks it's doing its job though but might only be flashing some of the imgs.
|
if I try with a newer version of
update_tool, it stops and returns an error about the chip (and then rkflashtool that I use to be sure that the device is still responding froze and I have to remove battery and restart from begining) :
Code:
Linux_Upgrade_Tool_v1.57# ./upgrade_tool uf /tmp/update-10456.img
Program Data in /root/.config/upgrade_tool
Loading firmware...
Support Type:RK330A FW Ver:7.1.00 FW Time:2020-10-21 12:13:56
Loader ver:2.60 Loader Time:2019-03-13 23:09:52
Check Chip Fail
Linux_Upgrade_Tool_v1.57# rkflashtool p
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3368...
rkflashtool: info: interface claimed
^C
(froze here, so ^C)
with the following log :
Code:
15:39:29 Current process in Linux_Upgrade_Tool_v1.57
15:39:29 Using /root/.config/upgrade_tool/config.ini
15:39:29 Command Line: ./upgrade_tool uf /tmp/update-10456.img
15:39:29 Current Device Location ID:11
15:39:29 Test Device Start
15:39:29 Test Device Success
15:39:34 Error:RKU_Read_EX failed,err=-7
15:39:34 ERROR:ReadCapability-->RKU_ReadCapability failed,err(-4)
15:39:34 Check Chip Start
15:39:39 Error:RKU_Write failed,err=-7
15:39:39 ERROR:CheckChip-->RKU_ReadChipInfo failed,RetCode(-3)
15:39:39 Check Chip Fail
15:39:39 Command mode out
Quote:
|
Do you have over 50GB of space free on your own PC?
|
No I don't
Quote:
|
At least the Device is not bricked and I know for a fact can be fixed under the windows tool (maybe a friend has a laptop you can borrow for an hour or something?).
|
neither
Quote:
EDIT: I thought maybe your image could be bad but I don't think so as I could not find any other update img for this device and I know I Flashed mine with that one.
[…]
Which has this file link in it direct from Boyue.
https://mega.nz/file/PBpnDY5C#oD2LP-...q7daI5T9WK-xlE
My MD5 of the file extracted is: 0FB77268916C3C54DE7FA57E39DBDD2E
Use this file instead with your Update Tool.
|
OK, ty a lot.
same md5 here, and I used that image too with same results, so I guess that it is not a problem with the update img.
About options with upgrade_tool :
Code:
Linux_Upgrade_Tool_v1.24# ./upgrade_tool -h
---------------------Tool Usage ---------------------
Help: H
Quit: Q
Version: V
Clear Screen: CS
------------------Upgrade Command ------------------
ChooseDevice: CD
SwitchDevice: SD
UpgradeFirmware: UF <Firmware>
UpgradeLoader: UL <Loader>
DownloadImage: DI <-p|-b|-k|-s|-r|-m image> [parameter file]
DownloadBoot: DB <Loader>
EraseFlash: EF <Loader|firmware>
LowerFormat: LF
----------------Professional Command -----------------
TestDevice: TD
ResetDevice: RD [subcode]
ResetPipe: RP [pipe]
ReadFlashID: RID
ReadFlashInfo: RFI
ReadChipInfo: RCI
ReadSector: RS <BeginSec> <SectorLen> [-decode] [File]
WriteSector: WS <BeginSec> <File>
ReadLBA: RL <BeginSec> <SectorLen> [File]
WriteLBA: WL <BeginSec> <File>
EraseBlock: EB <CS> <BeginBlock> <BlokcLen> [--Force]
-------------------------------------------------------
According to
others the lf (low format) or even ef (erasing flash) options can be used when having errors. I'm really not sure about those options, but maybe erasing flash at first then upload the image like I did before could make all more clean? :/