can not run RECOVERY on RK3288

syuchan

I use Firefly RK3288.

I have trouble.

RECOVERY program not work.

I try RESET+RECOVERY. but, not work.

I want to re-initialize to Factory defaults.

What do I?

zhansb

[size=11.8181819915771px]you can go into settings->Backup&reset, and select Factory data reset.

[size=11.8181819915771px]or run this command in adb or uart debug：

[size=11.8181819915771px]am broadcast -a   android.intent.action.MASTER_CLEAR

syuchan

Thanks for zhansb.

But can not start ANDROID-SYSTEM too.

May be, I have erased bootloader and system on eMMC  by operation-miss.

I tryed,

1. PowerOn

2. OTG USB cable connected to PC. (and startup AndroidTools on PC.)

3.  RESET-button and RECOVERY button pushed.

4. release RESET button.

5. release RECOVERY button.

"But AndroidTools is not connected. all time.

And before "operation-miss", could connect by AndroidTools.

May be not work "Loader Mode".

How can I use "MaskRom Mode"?

zhansb

try keep pushing RECOVERY and then power on,keep pushing 3-5sec

or could you show the message on debug uart when power on.

naobsd

hi syuchan,

it seems you mixed 2 different mode.

"press & hold RECOVERY key when reset/power-on" is "loader mode". it is used for flashing firmware from PC. (btw flashing firmware will erase data as like as factory reset)

"recovery mode" / "recovery program" is self factory-reset/update program flashed on Firefly board. you can start factory-reset by recovery program by "settings -> backup & reset" on Android. in this case you can see droid picture on TV.

just FYI.

EDIT: "loader mode" should run even if Android cannot boot anymore. if you cannot go into "loader mode", see debug uart output as zhansb said...

syuchan

Thanks all.

I was resolved on myself.

I done reboot "My-PC(Windows7)".

And  execute RESET+RECOVERY button sequence, again.

AndroidTools can connect to FireFly-Board !!

I'm sorry for all...

Thank you.

adamo.a60

It is same for me. I followed the "wiki.t-firefly.com/index.php/Firefly-RK3288/Build_Ubuntu_rfs/en" procedure and loaded misc.img and running miniroot successfully. The procedure failed because not enough space in /dev/mmcblk0p1. I tried with an SD card mounted on /dev/mmcblk1p1, but this was unsuccesfully.
Now I want to try the recovery procedure, but this is not possible. The debug rs232 monitor displays, after the boot,  "rockusb key pressed" and stops for 4-5 seconds awaiting for OTG-USB to be connected, then go ahead starting the kernel and stops with a miniroot shell. The OTG-USB cable is connected and the program is running. I tried both Windows and Linux programs and pcs, but it seems that the otg-usb it is not recognized.
What can I do to fix this? I spent a lot of time looking at forums in search of a suggestion, but I didn't find a solution.
Please, help me.

pacopad

Hi Adamo i already have such as problem, i had to format the flash to enter boot loader mode again

http://developer.t-firefly.com/en/viewt ... 8f48#p1084

Let me Know if it help you.

Pacopad

adamo.a60

Sorru, but the link "http://developer.t-firefly.com/en/viewt", as appears in your mail, is not correct...

Please, rewrite it the full link.

adamo.a60

Hi pacopad.

I found the full link: http://developer.t-firefly.com/en/viewt ... 8e4aeddf#p

I discovered some days ago the Ian Morrison wiki. I was trying to flash an SD card with Ubuntu, but that was unsuccessful, I didn't understand why.

The problem, now, is that Morrison says: "To be able to dual boot (i.e. boot directly from the device or from an SD card), you will first need to update the bootloader on your device. Either use 'AndroidTool v2.3' on Windows or 'upgrade_tool' on Linux to flash just the 'Loader' with the 'RK3288Loader_uboot_V2.17.02.bin' file." I'm no more able to enter Loader Mode, not at all.
I should go over this point enad resume the native working mode of the board.

adamo.a60