All Activity
This stream auto-updates
- Last week
-
Hello @tooz, The problem is it should be rk3399pro-tinker_edge_r.img instead of tinker_edge_r and also there are errors compiling scripts/dtc/dtc-lexer.lex.c_shipped because of multiple definitions of yyalloc on main branch
-
hello @sri, did you do step 4). which is to create defconfig?
-
5). make ARCH=arm64 tinker_edge_r.img CROSS_COMPILE=/media/edger/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu- -j32 I get an error no rule to make tinker_edge_r this did u mean Image?
-
sri joined the community
-
SPARKRU changed their profile photo
-
Firmware provided by (denchakapon) - https://tinker-board.asus.com/forum/index.php?/profile/259-denchakapon/ This post contains links to downloading firmware, obtaining ROOT super user rights, and instructions for installing Google Play Market. Android 8.1 - https://drive.google.com/file/d/1yfR_UXxI7Sd_vm2h87BHwsqajJVRVGT2/view?usp=drive_link The firmware has ROOT and Google Play Market. All interfaces and communications are working. The storage memory is completely visible. Android 11 - https://drive.google.com/file/d/1SywUn62XJk9Pmv0ixdnPvAvBKlONMLcv/view?usp=drive_link Wi-Fi doesn't work... I figured out getting root rights and it works. I also figured out the installation of PlayMarket, it works. Android 12 - https://drive.google.com/file/d/17JokXhaBzw3aK3lOoS4j0YTw4Z6UcveG/view?usp=drive_link Wi-Fi doesn't work... I figured out getting root rights and it works. I also figured out the installation of PlayMarket, it works. I've encountered a problem. I use microSD 32Gb and 64Gb. Android 12 does not see the full microSD capacity. I tried doing a factory reset, but it didn't help. I tried different programs for recording the image - balenaEtcher, win32diskimager, USB Image Tool. Obtaining super user rights - ROOT. How to get ROOT super user rights - https://tinker-board.asus.com/forum/index.php?/topic/15098-how-to-root-android-on-tinkerboard-2/ If it’s not clear or you have questions, you can contact me and I’ll explain. A little more detail - how to get super user ROOT rights. For Android 11 and 12, install the Magisk application - https://magisk.me/apk/ (Alternative link download) on Tinkerboard, then open the firmware image, for example, in Windows, using the archiver - 7zip, copy the boot.img file from the open firmware image to a location convenient for you. Then copy the boot.img file to Tinkerboard, run Magisk on Tinkerboard, select Magisk mode - installation, patch boot - image. Naturally, select the pre-copied boot.img image. The patched boot.img image will be saved to the Download folder on Tinkerboard with the approximate name - magisk_patched-27000_TmRXH.img. Next, copy the patched image to your computer. Next you need to copy the patched image to Tinkerboard in fastboot mode via ADB. How to install ADB kitchen (Android SDK Platform Tools) (Alternative link download) for Windows (there are a lot of letters, but everything is simpler than it seems) - https://droidwin.com/how-to-add-adb-to-path-in-windows-11/ Instructions for copying patched boot.img via ADB (see point - 😎 - https://droidwin.com/root-android-11-magisk-patched-boot-img/ A little difficult, but everything is simpler than it seems. If it’s not clear or you have questions, you can contact me and I’ll explain. Regarding the installation of Google Play Market. After obtaining ROOT super user rights through Magisk, You need to download the LiteGapps package with Google services, including our coveted Google Play Market - repository https://sourceforge.net/projects/litegapps/files/litegapps/arm/30/pixel/2024-02-23/ Link to the package we need (MAKSU-LiteGapps) - https://sourceforge.net/projects/litegapps/files/litegapps/arm/30/pixel/2024-02-23/MAKSU-LiteGapps-pixel-arm-11.0-20240223-official.zip/download (Alternative link download) Next, copy the downloaded file MAKSU-LiteGapps-pixel-arm-11.0-20240223-official.zip to any folder convenient for you on Tinkerboard. Launch Magisk, select Modules at the bottom of the line, install from the storage, and select a pre-downloaded file for installation -MAKSU-LiteGapps-pixel-arm-11.0-20240223-official.zip After unpacking and installing the modules, click in the lower right corner - reboot. Good luck with the firmware, obtaining super user rights and installing Google services! I look forward to your criticism, questions and suggestions - (I’m more looking forward to suggestions for solving problems that have arisen)... The most questions and solutions await - (denchakapon) - https://tinker-board.asus.com/forum/index.php?/profile/259-denchakapon/
-
All links for downloading the firmware in this topic are not working. If possible, please update.
-
jackie_yu changed their profile photo
-
Wi-Fi doesn't work... I've encountered a problem. I use microSD 32Gb and 64Gb. Android 12 does not see the full microSD capacity. I tried doing a factory reset, but it didn't help. I tried different programs for recording the image - balenaEtcher, win32diskimager, USB Image Tool. Wi-Fi не работает... Я столкнулся с проблемой. Использую microSD 32Гб и 64Гб. Android 12 не видит всю емкость microSD. Пробовал сделать сброс к заводским настройкам, не помогло. Пробовал разные программы для записи изображения - balenaEtcher, win32diskimager, USB Image Tool.
-
android 11 [Release] Android 11 Tinkerboard (not R2.0)
SPARKRU replied to denchakapon's topic in Android
Wi-Fi doesn't work... I figured out getting root rights and it works. I also figured out the installation of PlayMarket, it works. Не паботает Wi-Fi... С получением рут прав разобрался, работат. С установкой PlayMarket тоже разобрался, работает. -
android 11 [Release] Android 11 Tinkerboard (not R2.0)
denchakapon replied to denchakapon's topic in Android
Sorry, here is the working link: Download Android 11 ROM Tinkerboard (not R2.0) -
Hi guys. Let me share Android 12 for Tinkerboard / Tinkerboard S 1-st revision (not R2.0) which Asus marked as outdated/legacy. You can find download link below: Download Android 12 ROM Tinkerboard (not R2.0) Bug reporting are welcome. Release is based on official Asus firmware for Tinkerboard S R2.0.
- 1 reply
-
- 1
-
-
- android 12
- tinkerboard-s
- (and 1 more)
-
denchakapon changed their profile photo
- Earlier
-
I can, just to know the behaviour, but in production we deliver it to customer without the SD Card with the OS on the eMMC 😞
-
android 11 [Release] Android 11 Tinkerboard (not R2.0)
SPARKRU replied to denchakapon's topic in Android
Please provide a working link to download the firmware. The link in the topic header is not relevant, there is no file to download. Thank you in advance. -
hello @Jovan, thanks for letting me know. also, could you try use flash a sd card with v.1.0.17, and see if the first tinker board 3n can boot from sd and then flash emmc? Tinker Board 3N Debian 11 (Kernel 5.10) V1.0.17
-
I just got and tried a new, second one (same model, Tinker Board 3N). Removed the jumper cap, plugged into the mac and it immediately recognized and works like a charm. Looks like the first one needs to be RMA. Thanks
-
kali joined the community
-
Thanks for all the great feedback. There is always an option it's a faulty one.
-
hello @Jovan, given the clues i can only suggest to 1. restart the windows pc 2. change the type a - type c cable tinker board 3n should be recognised in device manager, as same as tinker board 2s (the quickest way to debug the environment is to plug a usb drive to the same port of the windows pc and see if it's working)
-
I'm not sure I understand the last question, but I've never "used" the board in term of booting the OS. As soon as I plug in the power supply, red led turns on. It was on also before I've removed the mask2 jumper. So, it's always on when I connect the power supply, no matter if USB cable is connected or not.
-
hello @Jovan, was the led (led1) on while using? please check if you're able to use the adb with mask2 cap on while booting?
-
I've attached the latest setup photo for reference. Red light is there, USB-C -> USB-A, but nothing detected by Win, and nothing in device manager.
-
I've done all that, both jumper caps removed, except Macbook does not have USB-A port, so have to use USB hub for that. Also tried on Windows, which now does not recognize anything at all 😞
-
hello @Jovan, 1. the connection should be type c port (tinker board 3n) to type a port (macbook) 2. both the jumper caps need to be removed 3. no need to adjust mask1 dip switch
-
Thanks for really fast answers. Unfortunatelly... still nothing. So, I've removed jumper from Mask2 pins. What about the Recovery pins, should I have the jumper there ON or no)? And also the Mask1 dip-switch?
-
hello @Jovan, please remove the yellow jumper cap, and re-do the procedure (connecting tinker board 3n to the computer) again booting without the jumper cap attached so the tinker board 3n can start on uboot and the board should be in ums mode
-
Thanks for the feedback. On Mac I had to use USB Hub to get USB-A port. Tried two without any success. Result is the same. Then I tried on the Windows machine and it got recognized, but not as a storage device, but as "Unknown Device", which then was not available for flashing in BalenaEther as it's not recognized as a storage device. Any further help please? Is there any drivers I should install on Win? Thanks again
-
hello @Jovan, the cc logic controllers between tinker board 2s and tinker board 3n are different -- for tinker board 3n, if both the ports connected are type c port, the controller will not be able to recognise which port should be in host mode and which port should be in device mode. for tinker board 3n i would recommend to connect type c port from tinker board 3n to type a (macbook)
-
After successfully using TinkerBoard 2S in production, we wanted to evaluate TinkerBoard 3N and bought it. However, using the same setup (macOS and USB-C <-> USB-C cable directly connected to the mac laptop), we cannot get it to be recognized as a storage device. We're following the same procedure as we do with the TinkerBoard 2S (unplug everything from TinkerBoard, connect the USB-C cable to board and laptop using the OTG port and then connecting the power supply. But nothing happens when we connect the board... Can you suggest what can we try to resolve the issue? Photo of the board itself is attached if that helps in any way... Thanks
