Can't detect busybox - Githubissues

jensstein / oandbackup

backup manager for android

Other

543 stars 194 forks source link

Can't detect busybox #210

Closed swan11jf closed 6 years ago

swan11jf commented 6 years ago

On startup, error shows this: couldn't find busybox, please check error log

error log shows this: sh: [1]: toybox: not found [busybox

Recently changed from Lineage (7.1.2) to AOSP Extended (8.1). It was working fine on Lineage

ildar commented 6 years ago

toybox or busybox required for oandbackup. Could you please check which of the two you have?

ointeractive-depot commented 6 years ago

Busybox or Toybox are required, but Android have it from the box by default. Before Marshmallow (will be, I don't remember the version) it using Busybox, and after - Toybox. But OAB execute commands with Busybox and Toybox together, so at least one of them WILL working, so seems this message is only a warning, not error. So does OAB makes backups or not for you? In this situation it will on any case.

ildar commented 6 years ago

Anton, you are wrong. Every Android has toolbox, but CM/LA/derivatives have bb/toybox bundled. @swan11jf , plz just check and answer.

ointeractive-depot commented 6 years ago

@ildar please refers the OAB sources: https://github.com/jensstein/oandbackup/blob/master/src/dk/jens/backup/ShellCommands.java line 369:

android 6 has moved to toybox which doesn't include [ or [[

ildar commented 6 years ago

Right. I am wrong. Toybox came into AOSP in 2014.

ointeractive-depot commented 6 years ago

Don't worry about it ;) We all mistaken.

swan11jf commented 6 years ago

Is there anyway of transferring backups manually then?

ointeractive-depot commented 6 years ago

Where do you want to tranfser it? You could made it, but can't apply it after?

swan11jf commented 6 years ago

The backup was made on Android 7. I changed to a new ROM, so had to wipe my device. I've upgraded to android 8 now, so as oandbackup doesn't seem to be working for me, i want to restore this backup to the same device

ointeractive-depot commented 6 years ago

I'm so sorry for forgot to answer you. If you have backups, you can restore it manually. You need a filemanager which can set chmods (like Solid Explorer, it's really cool), put your backups folder to /data/data folder (e. g. /data/data/your.app.name) and set 777 chmods to all of it.

jensstein commented 6 years ago

it seems like your device doesn't have toybox or has a non-standard installation of some *box. could you please see if running toybox in a terminal emulator on your device or via adb shell gives a result (it should list the included commands). and could you post the output of running ls -l /system/bin/

also, remember checking if you have a value set for busybox under "custom paths" in the preferences. if it's set, the old value may not be valid for your new system.

(by the way, i'm in the process of making a replacement for {toy,busy}box, which will ship with oab)

swan11jf commented 6 years ago

Ok, here's the link to the output

https://file.io/KVniGn

EDIT: I set a custom path for busybox and it is now detected! Thanks for your help

jensstein commented 6 years ago

great :) your link gives me 404 but i'm glad you got it to work

simongcc commented 1 year ago

I am using a legacy Samsung tablet with Android 4.1.2, it mentions this error when backup data and apk. Is it possible to add those tools in 4.1.2?

ildar commented 1 year ago

find out if you have busybox or toybox
if not, get a Busybox Installer. F-Droid Archive should have one for your vintage system !!! surely root required.