RK3229 wait for loader fail

7,758 views
Skip to first unread message

Michel Dubois

unread,
Apr 18, 2017, 10:31:37 AM4/18/17
to linux-rockchip
Hi,

I've a MXQ 4K RK3229 android TV box
Due network
I tried to downgrade From Android Lolipop to Android Kit Kat. I used this procedure :
http://www.hotmcu.com/wiki/Flashing_Firmware_Image_Files_Using_The_Rockchip_Tool#Using_Linux_Upgrade_Tool_to_flash_update.img

During the work I've god this log :

15:24:18 771    AndroidTool MarsBoard v2.1.0.0 start run
15:26:12 998    Layer<1-2>:Test Device Start
15:26:13 005    Layer<1-2>:Test Device Success
15:26:13 012    Layer<1-2>:Check Chip Start
15:26:13 020    Layer<1-2>: Check Chip Success
15:26:13 027    Layer<1-2>:Get FlashInfo Start
15:26:13 032    <LAYER 1-2> INFO:FlashInfo: 00 00 08 01 00 20 20 28 20 02 01
15:26:13 038    Layer<1-2>:Get FlashInfo Success
15:26:13 044    Layer<1-2>:Prepare IDB Start
15:26:13 050    <LAYER 1-2> INFO:CS(1)        (8448MB)        (HYNIX)
15:26:13 061    Layer<1-2>:Prepare IDB Success
15:26:13 067    Layer<1-2>:Download IDB Start
15:26:14 881    Layer<1-2>:Download IDB Success
15:26:14 904    Layer<1-2>:Reset Device Start
15:26:15 922    Layer<1-2>:Reset Device Success
15:26:15 955    Layer<1-2>:Wait For Loader Start
15:26:46 024    Error:Layer<1-2>:Wait For Loader Fail

I can not connect to the device anymore

Any idea how to restore the system?

Thanks in advance.


Omegamoon

unread,
Apr 18, 2017, 1:00:38 PM4/18/17
to Michel Dubois, linux-rockchip
Hi,

I guess you flashed the wrong image... at least it looks like it. If the device can no longer be flashed in a normal way (by pressing reset and then powering the device on), you soft-bricked it, and you have no other option then trying to get the device into mask mode. To do so, find the NAND chip on the device board. Looking at the log you sent, this is a Hynix chip. Power off the device, shorten pins 7+8 on the board using a paper clip or something similar, and while shortened, power on the device. Remove the paper clip after a second or 2-3, making sure not to drop it, or shorten anything else. The device should show up in mask mode after that, and you should be able to flash it. This time make sure to use a known working image ;-)

Good luck!

Regards,
Omegamoon

--
You received this message because you are subscribed to the Google Groups "linux-rockchip" group.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-rockchip+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/linux-rockchip.
For more options, visit https://groups.google.com/d/optout.

Jay Reilly

unread,
May 3, 2017, 12:05:23 AM5/3/17
to linux-rockchip, dubois...@gmail.com
I have never been able to get the RK3399 ready to flash by pressing reset and then powering on.  The only way I got it to work was by following the directions on the "bootloader" page at http://wiki.t-firefly.com/index.php/Firefly-RK3399/Boot_mode/en :

If device still can not be found after pressing "RESET", then try this: long press "PWRKEY" after short pressing of "RESET", before finally releasing "RECOVERY".

I wish that Firefly either had a better, more navigable/searchable forum or that part of it's site would be in a wiki form that trusted users could edit. Omegamoon, if you're from Firefly, you should really consider this idea.  I really like the RK3399 so far and I'd even like to push Google to support it with a dedicated developer if I could (since it and the Nvidia boards are the only two developer boards I know of that should be capable of encoding Webm).

At least there's this Google group though, which is good.

Andres Novoa

unread,
Dec 13, 2017, 7:51:58 AM12/13/17
to linux-rockchip
Do you solve it??? I have the same problem. Could you help me please.
To unsubscribe from this group and stop receiving emails from it, send an email to linux-rockchi...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages