01-20-2018, 06:53 AM
Hello everybody,
I'm trying to flash my 64GB eMMC with the latest Android TV build from ayufan: https://github.com/ayufan-rock64/android...3-r115.zip
I've been following this guide: http://files.pine64.org/doc/rock64/guide...o_eMMC.pdf
I'm running Arch Linux. I also tried the exact same steps on a Ubuntu 17.10 machine and I got the exact same behaviour.
Here's the output of the rkinstall script:
Please note the "Error: 'mtdparts' not found in command line" lines.
This is the output of rkflashtool n:
I have tried to boot my ROCK64 and flash the image in all the following modes:
- Loader Mode, as suggested in ayufan's guide (hold Recovery, press Reset, release Recovery after 3 seconds) and also as suggested in the SADIE script (hold Reset, hold Recovery, release Reset, release Recovery after 3 seconds). Please note that I'm NOT actualy running the SADIE script.
- Normal boot (by simply pressing the Power button)
- MASKROM boot (by pressing the Power button after short-circuiting the eMMC PINS with a jumper)
(Acually I really have no idea how to verify which mode my ROCK64 is actually booting into... Does anybody know a way? Maybe using UART?)
Regardless of what mode I'm trying to use, I ALWAYS get the same ouput for all commands (including the MASK ROM MODE line!).
Unfortunately I do not have a eMMC -> USB adapter (after reading the guides I concluded that it was not strictly necessary anymore so I did not purchase it) so I'm stuck to flashing directly on the board.
So in the end I'm stuck right now. Any help would be really appreciated.
I'm trying to flash my 64GB eMMC with the latest Android TV build from ayufan: https://github.com/ayufan-rock64/android...3-r115.zip
I've been following this guide: http://files.pine64.org/doc/rock64/guide...o_eMMC.pdf
I'm running Arch Linux. I also tried the exact same steps on a Ubuntu 17.10 machine and I got the exact same behaviour.
Here's the output of the rkinstall script:
Code:
+ rkflashtool P
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: writing flash memory at offset 0x00001c00... Done!
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w uboot
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: uboot
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w trust
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: trust
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w misc
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: misc
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w kernel
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: kernel
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w boot
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: boot
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w recovery
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: recovery
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ for i in uboot trust misc kernel boot recovery system
+ rkflashtool w system
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: working with partition: system
rkflashtool: info: Error: 'mtdparts' not found in command line.
+ rkflashtool b
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: rebooting device...Please note the "Error: 'mtdparts' not found in command line" lines.
This is the output of rkflashtool n:
Code:
rkflashtool: info: rkflashtool v5.2
rkflashtool: info: Detected RK3328...
rkflashtool: info: interface claimed
rkflashtool: info: MASK ROM MODE
rkflashtool: info: Flash ID: 00 00 00 00 00
rkflashtool: info: Flash Info:
Manufacturer: Samsung (0)
Flash Size: 0MB
Block Size: 0KB
Page Size: 0KB
ECC Bits: 0
Access Time: 0
Flash CS:I have tried to boot my ROCK64 and flash the image in all the following modes:
- Loader Mode, as suggested in ayufan's guide (hold Recovery, press Reset, release Recovery after 3 seconds) and also as suggested in the SADIE script (hold Reset, hold Recovery, release Reset, release Recovery after 3 seconds). Please note that I'm NOT actualy running the SADIE script.
- Normal boot (by simply pressing the Power button)
- MASKROM boot (by pressing the Power button after short-circuiting the eMMC PINS with a jumper)
(Acually I really have no idea how to verify which mode my ROCK64 is actually booting into... Does anybody know a way? Maybe using UART?)
Regardless of what mode I'm trying to use, I ALWAYS get the same ouput for all commands (including the MASK ROM MODE line!).
Unfortunately I do not have a eMMC -> USB adapter (after reading the guides I concluded that it was not strictly necessary anymore so I did not purchase it) so I'm stuck to flashing directly on the board.
So in the end I'm stuck right now. Any help would be really appreciated.
