Unable to flash Android TV on eMMC: rkflashtool error
#1
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:

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.
  Reply
#2
here are some threads that may help,
https://forum.pine64.org/archive/index.p...-5359.html
https://forum.pine64.org/showthread.php?...4#pid29074
https://forum.pine64.org/showthread.php?tid=4924
  Reply
#3
Those threads seem to provide no solution for this particular problem (the first thread reports the same problem but there is no real solution, only inconvenient workarounds).

In the end I used a Windows PC and flashed the eMMC by following the Windows section of the same guide. That worked flawlessly.

So it might be a bug in rkflashtool. Unfortunately it's much more convenient for me to flash under Linux, so it would be nice to have the problem solved in the future. Maybe I'll try with rkdeveloptool instead.
  Reply
#4
(01-20-2018, 06:53 AM)fbossi Wrote: 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:

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.

I am in the same exact situation (output identical), however I followed the PDF first and then did actually try SADIE as well.  No Dice!
  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Receiving errors about eMMC (?) acasta 11 1,742 09-24-2019, 10:26 PM
Last Post: ridgarou
  USB -> eMMC is now available. Luke 15 6,916 07-27-2019, 04:27 PM
Last Post: tllim
  Unable to boot from SPI stevefan1999 4 752 05-01-2019, 04:47 PM
Last Post: rhens1
  Rock 64 network error as soon as I try to write or read. georgegohl888 1 142 03-12-2019, 09:35 AM
Last Post: georgegohl888
Brick How to Write an Image to the eMMC Module Tutorial MarkHaysHarris777 55 24,332 02-06-2019, 04:02 PM
Last Post: tllim
  flash image to sd/emmc through ethernet LMM 0 206 02-04-2019, 07:36 AM
Last Post: LMM
  No Boot, Red Green and White flash at 1 sec intervals wesleykonrad 2 285 01-28-2019, 11:54 PM
Last Post: wesleykonrad
  How to get UHD 4k working (with Android TV 7) Hotkey 7 842 09-18-2018, 09:39 AM
Last Post: Trash_Can_Man
  Card emmc Auggoncalves 2 359 06-25-2018, 03:20 AM
Last Post: Auggoncalves
  AOSP Build Steps Using github.com/ayufan-rock64/android-7.1 birender.s 15 5,039 05-09-2018, 01:20 AM
Last Post: burram

Forum Jump:


Users browsing this thread: 1 Guest(s)