Jump to content
New Wiki - User & Developer Guide ×

hisataro

Members
 View Profile  See their activity

  • Content Count

    24

  • Joined

  • Last visited

Posts posted by hisataro

  5. Posted

    hello @tooz,

    I don't see any error-like messages, and the last
    "create dtoverlay.imgmkfs.fat 4.1 (2017-01-24)"
    It seemed to fail at .
    ---
    create misc.img.... done.
    create uboot.img...
    create idbloader.img...done.
    create trust.img...
    create loader...
    create config.cfg...
    create baseparameter...done.
    Build dtbodone.
    create dtoverlay.imgmkfs.fat 4.1 (2017-01-24)
    Make image failed!
    ---

    The following file on Docker
    [CONTAINER-ID]:/source/rockdev/Image-WW_Tinker_Board_2/WW_Tinker_Board_2-raw.img ~/
    was not generated.
     

  7. Posted

    Hello, minami

    The manifest file seems to have changed, but the documentation has not been updated.

     

    I was able to get the repository by doing the following:

    $ repo init -u https://[access token]@github.com/TinkerBoard-Android/rockchip-android-manifest.git -b android11-rockchip -m tinker_board_2-android11-2.0.8.xml --config-name
     

  10. Posted

    In my case I created a launcher app in AndroidStudio and replaced it,  and called it in onPostCreate() as follows to call a target app at startup.

    private void launchApp() {
         String packageName = "com.mycompany.title";
         String className = "com.unity3d.player.UnityPlayerActivity";
         Intent intent = new Intent();
         intent.setAction(Intent.ACTION_VIEW);
         intent.setClassName(packageName, className);
         startActivity(intent);
    }

  13. Posted

    Hi @yi-hsin_hung

    It worked by using mraa-2.0.0.aar directly from Unity !

     

    // Put aar to Unity Plugin Folder

    UnityProjectFolder/Assets/Plugin/Android/mraa-2.0.0.aar

     

    // Gpio Instance
    AndroidJavaClass _TinkerBoard = new AndroidJavaClass("mraa.TinkerBoard");
    AndroidJavaObject _TINKERBOARD_PIN3 = _TinkerBoard.GetStatic<AndroidJavaObject>("TINKERBOARD_PIN3");
    int swigValue = _TINKERBOARD_PIN3.Call<int>("swigValue");
    AndroidJavaObject _Gpio = new AndroidJavaObject("mraa.Gpio", swigValue);

    // Dir instance
    AndroidJavaClass _Dir = new AndroidJavaClass("mraa.Dir");
    AndroidJavaObject _DIR_IN = _Dir.GetStatic<AndroidJavaObject>("DIR_IN");

    // Mode Instance
    AndroidJavaClass _Mode = new AndroidJavaClass("mraa.Mode");
    AndroidJavaObject _MODE_PULLUP = _Mode.GetStatic<AndroidJavaObject>("MODE_PULLUP");

    // Call Gpio.read()
    AndroidJavaObject resultDir = null;
    AndroidJavaObject resultMode = null;

    resultDir = _Gpio.Call<AndroidJavaObject>("dir", _DIR_IN);
    resultMode = _Gpio.Call<AndroidJavaObject>("mode", _MODE_PULLUP);
    int result = _Gpio.Call<int>("read");
     

    Tahnk you.

  16. Posted

    Thank you for your support. @tooz

    > once the flashing is done, please copy the boot image to the device. the boot.img file (TB2_Android11_v2.0.6_boot_img) is re-uploaded and can be downloaded
    > here:     https://www.asuswebstorage.com/navigate/a/#/s/50AF1C5364224C2BA8C8A5802DD779064

    I created a patch from this image with Magisk and flashed it, and it succeeded in rooting!

    I used the "RootCheker" app to see if it was rooted.

    Thank you really!!

  17. Posted

    Thank you for your support. @tooz

    > 9. Flash boot image patched by magisk in fastboot mode
    > 
    > adb reboot-bootloader

    After this, I couldn't find the device in [fastboot devices].
    But, Apply the <Android Bootloader Interface> driver from your PC's Device Manager.
    I could see the devices in [fastboot devices].


    > fastboot flash boot magisk_patched_[random_strings].img

    This also seems to be successful.

    > fastboot reboot

    This also seems to be successful.

    However, when TinkerBoard2 starts after this,
    the Android Recovery mode screen will be displayed.
    As I asked before, I don't know what to do in Android Recovery mode ...😥
     

  19. Posted

    Thank you for your support
    > I ran "fast boot flash boot", but it said "Waiting for device" and couldn't proceed.
    I did adb reboot fastboot on another PC and it went on.
    Tinkerboard2 became the Recovery screen after booting.
    I don't know what to do on the Recovery screen.

  21. Posted

    Thank you for your support.
    The boot.img you sent us was successfully patched.

    https://tinker-board.asus.com/forum/index.php?/topic/15098-how-to-root-android-on-tinkerboard-2/&tab=comments
    I'm following the steps in

    > 9. Flash boot image patched by magisk in fastboot mode
    >
    > adb reboot-bootloader
    >
    > fastboot flash boot magisk_patched_ [random_strings] .img
    >
    > fastboot reboot

    I ran "fast boot flash boot", but it said "Waiting for device" and couldn't proceed.
    The device was recognized as "Android download gadget" from the PC, so I tried to apply the following driver, but I could not install it.
    https://developer.android.com/studio/run/win-usb?hl=ja

    What should I do to do a "fast boot flash boot"?

  22. Posted

    Magisk fails, is the procedure wrong?

    Unzip Tinker_Board_2-Android11-v2.0.6-20220303.zip
    Renamed Tinker_Board_2-Android11-v2.0.6-20220303.img to boot.img.

    Magisk> Magisk Install> Select Patch a File> boot.img> Let's Go fails.

    It is the execution result of Magisk.
    -Device Platform: arm64-v8a
    -Installing: 24.3 (243000)
    --Copying image to cache
    --Unpacking boot image
    ! Unable to unpacl boot image
    ! Installation failed

×
×
  • Create New...