Firefly Open Source Community

[Issue] Stock Recovery RK3399 & ADB not function.

113

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
113
Posted at 4/4/2017 08:35:16     
When going into the Stock recovery on the Firefly-RK3399, ADB functions do not work.
Reply

Use props Report

591

Credits

0

Prestige

0

Contribution

advanced

Rank: 4

Credits
591
Posted at 4/5/2017 10:40:33     
try to link a sh for adb in recovery.
out/target/product/rk3399_firefly_box/recovery/root/
ln -sf /sbin/sh  system/bin/
rebuild recovery.img and flash it , retry
Reply

Use props Report

113

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
113
Posted at 4/6/2017 01:28:20     
ok, so I extract recovery.img, then extract ramdisk.gz, now I symlink system/bin/sh to /sbin/sh ?
Reply

Use props Report

591

Credits

0

Prestige

0

Contribution

advanced

Rank: 4

Credits
591
Posted at 4/6/2017 09:58:52     
BiatuAutMiahn Posted at 4/6/2017 01:28
ok, so I extract recovery.img, then extract ramdisk.gz, now I symlink system/bin/sh to /sbin/sh ?

It maybe work, I sugguest you do it under the SDK .
Reply

Use props Report

113

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
113
Posted at 4/6/2017 11:55:00     
ok, thank you
Reply

Use props Report

22

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
22
Posted at 6/25/2018 17:33:26     
Hello!

I did this ("ln -sf /sbin/sh  system/bin/ " in "out/target/product/rk3399_firefly_aio_box/recovery/root/" under SDK, then recompile and reflash recovery.img)
But ADB in recovery mode still doesn't work. I can't see any usb devices on my PC for AIO on recovery mode (I'm using linux PC and I'm sure 100%)
What should I do next?
Reply

Use props Report

591

Credits

0

Prestige

0

Contribution

advanced

Rank: 4

Credits
591
Posted at 6/27/2018 10:47:28     
sol Posted at 6/25/2018 17:33
Hello!

I did this ("ln -sf /sbin/sh  system/bin/ " in "out/target/product/rk3399_firefly_aio_box/ ...

No need to complie , just pack it up after complie the whole SDK.
Run ./mkimage.sh and get the recovery.img .
Flash recovery.img and it will be work.
Reply

Use props Report

22

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
22
Posted at 6/28/2018 19:51:42     
leung先森 Posted at 6/27/2018 10:47
No need to complie , just pack it up after complie the whole SDK.
Run ./mkimage.sh and get the re ...

Ok, to check everything I did all from scratch:
1. Download fresh SDK (Firefly-RK3399_Android7.1.2_git_20180126.7z)
2. Unzip it, updated it (git pull gitlab firefly-rk3399:firefly-rk3399 - everything up to date)
3. Compiled it with ./FFTools/make.sh -j8  -l rk3399_firefly_aio_box-userdebug
4. Ru "ln -sf /sbin/sh  system/bin/ " in "out/target/product/rk3399_firefly_aio_box/recovery/root/"
5. Run "/mkimage.sh", new recovery.img was made
6. Flashed this new recovery.img with rkflashkit to recovery partition
6. After board boot, run "adb reboot recovery" on my PC
7. When board boots into recovery, I can see that this recovery image is new (date and time is written at the top of menu).

But result of "adb devices" on my PC is empty! I can't run "adb sideload" or anything else.
And there no unknown devices in "lsusb" output on my PC.

Also, if I select "Apply update from ADB" from recovery menu - I see error "Failed to open driver control: No such file or directory"

So, in recovery mode ADB not working with or without selecting "Apply update from ADB" in recovery menu.
This is a screenshot from /cache/recovery/last.kmsg:

https://www.dropbox.com/s/m4ya7h ... 628_144740.jpg?dl=0

It shows "init: avc: denied {set} for property=sys.usb.ffd.ready" before "init: Starting service adbd", maybe this is the reason why ADB doesn't work?

Please help!
Reply

Use props Report

591

Credits

0

Prestige

0

Contribution

advanced

Rank: 4

Credits
591
Posted at 6/29/2018 09:27:13     
sol Posted at 6/28/2018 19:51
Ok, to check everything I did all from scratch:
1. Download fresh SDK (Firefly-RK3399_Android7.1. ...

You need to make sure that when you run ./mkimage.sh is "lunch rk3399_firefly_aio_box" .
As I kown , if you do not lunch by hand , it default lunch rk3399_firefly_box insteal of  rk3399_firefly_aio_box.
Reply

Use props Report

22

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
22
Posted at 6/29/2018 17:35:52     
leung先森 Posted at 6/29/2018 09:27
You need to make sure that when you run ./mkimage.sh is "lunch rk3399_firefly_aio_box" .
As I kow ...

Yes, I did lunch by hand with "lunch rk3399_firefly_aio_box"
My recovery image title is "rockchip/rk3399_firefly_aio_box/rk3399_firefly_aio_box 7.1.2/NHG47K/...", so it's for firefly_aio_box

But ADB USB connection is not working in this revovery mode (with "ln -sf /sbin/sh  system/bin/")

Maybe you can post your recovery.img with working ADB for firefly_aio_box somewhere (i.e. on your gitlab)?

Your advice "ln -sf /sbin/sh  system/bin/ " doesn't affect ADB functionality in recovery mode.
Please help.

P.S. Also I  can't use "Apply update from SD card" from recovery menu, it gives "E:failed to map file"
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list