Dear XDA developers,
recently I've bought an Android TV Box, you can read a techincal datashet of it at this link:
telcominstrument . com
on the left menu select: Box Android Internet TV FULL-HD 1080p - Android 4.0 TV Box Full-HD Wireless
technical specification:
•Sistema Operativo Android 4.0;
•Microprocessore CPU BOXCHIP A10 frequenza 1.2GHz;
•Memoria RAM DD3 1GB, Flash 4GB;
•Uscita Video HDMI 1.4, Full HD 1080P, con decoder hardware;
•Connessione Wi-Fi a velocità massima 300mbps;
•Antenna Wifi Omnidirezionale;
•supporto Videochiamate Skype;
•Compatibile HDD formattati in FAT, FAT32, NTFS, EXT2, EXT3;
•Risoluzione Alta Definizione Full HD 1080p, max. 1920x1280px;
Principally I've one problem, It's impossible to write on an external usb disk, a permission denied message appears at all attempt.
I've tryied some different format for the device FAT,FAT32 and NTFS but no one allow me to write on the device.
So I've search some solution on internet and I've found this one:
"To enable USB host API support you should add a file named
android.hardware.usb.host.xml and containing the following lines:
<permissions>
<feature name="android.hardware.usb.host"/>
</permissions>into folder
/system/etc/permissionsin that folder find file named
handheld_core_hardware.xml or tablet_core_hardware.xml and add
<feature name="android.hardware.usb.host">
into <permissions> sectionReboot your device. Usb host api should work.
Tested on CUBE U30GT with android 4."
Unfortunatelly I haven't the access to modify the system /etc/permision folder, so I think that I must root my Android Box, but How?
Can You halp me with the USB and Root issue?
Thanks at all,
Related
Hi everyone, is there a way to root the 1&1 SmartPad and to use a custom ROM?
Kind regards
PaulyTally
The problem seems to be that you cant enable the usb debugging mode as it is not available in the menu.
Maybe some technical details help:
* Display: 7″ LED-Touch-Display (Resoultion 800 x 480)
* Processor: 500 MHz ARM11
* Memory: 256 MB DDR RAM
* Internal memory: 1 GB Flash
* Interfaces: WLAN IEEE 802.11b/g/n, USB 2.0, SD-Card-Slot, Infrared-Sender, Micro USB (Power Supply), 3,5mm Audiooutput, System-Connector(Docking-Station)
* Akku: 2.500 mAh Lithium-Ionen
* Size: 196,6 x 130 x 22 Millimeter
* Weight: ca. 470 Gramms
* Audio: MP3, AAC, WAV
* Video: H.264, MPEG4 (XVID), ASF, AVI, MP4, MOV, MKV
* Picture: JPG, GIF, PNG, BMP
Kind regards
PaulyTally
We try to hack the pad. A small Board called ump2002 in German.
Search for a way to read and write a Custom Rom. We have found some Information on the net and wait now for the smarpads to test some things.
sorry for my english
i have a smart pad with android not realy good
i hope for a way to make win mobile on it that was fine
the quest is " run win mobile on smart pad "
Root 1&1 Smartpad
Here is a way to root 1&1 Smartpad running on Android 2.2 (Froyo).
Many thanks to 'Kjeldor' @ tablet-user.de for the original German content.
The following apps are needed:
Superuser.apk
AnyCut.apk
z4root.apk
U may download the zip file from rapidshare (h**p://rapidshare.com/files/451128664/Root-Kit.zip) or attached below.
1. Copy the above mentioned APKs to the memory card
2. Go to Settings > Applications and enable 'Unknown Sources'
3. Install a file manager from the 1&1 Store (I installed Dual File Manager)
4. Now go to the SD card using the file manager and install 'Superuser.apk' and then 'AnyCut.apk'.
5. Start 'Anycut' and click 'New Shortcut'. Select 'Activity' then 'Development', and create a new short cut. This new short-cut named 'Development' (default name) will give you the access to 'Enable USB Debugging' option which is otherwise not visible from 'Settings > Applications'
6. Activate the 'USB-Debugging' from the new short-cut
7. Install and run 'Z4root.apk' application. Once it's up, click 'Permanent Root'. Make sure your Smartpad has enough battery and be patient (unless you want to brick your device !) till it reboots.
More info and pictures on Z4 root is here (w*w*w*.dkszone.net/root-galaxy-s-samsung-android-2-2-froyo-samsung-galaxy-tab-root)
8. Congrats, now you have root access !!!
Once again many thanks to 'Kjeldor' @ tablet-user.de forum for the original German content.
*Refreshing
Is there no custom rom for this smartpad ??
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Smartpad 810c custom roms/development/faq/ecc
http://www.androidiani.com/forum/mediacom-smartpad-810c/
Sorry, only Italian language forum
This is some of the info that I have put together and I figured it may help some of you also. Let me know if I need to add anything. Looking forward to working with this device. Hopefully the Devs will take an interest in it also. With these hardware specs I feel like they will. Anyway, carry on............
Dev/Config/Soft/Tools
CyanogenMod team Touchpad port
HP Site
SDK - Multiple Platforms Instructions
Command line tools
Java - WIndows 32 and 64 Bit Instructions
****Note - Be sure to add the Java Bin path to your Environment Variables PATH
Java - Linux
Bluetooth with Non-WebOS device
Enabling Developer Mode (Rooting)
How To: Connect TP to network sharesHW
Exploded and PCB
Quick sum up/start up guide Thanks KameoRE
Bill of Materials
Specs 16GB
Specs 32 GB
Repair Manual / Teardown
Comparisons
Extra info
Enabling Developer Mode (Rooting)
In general, simply installing the Palm SDK gives you everything you need for full access to the Linux operating system on any webOS device. There is no special "rooting" or "jailbreaking" process. Simply installing the SDK provides you with unlimited access to the Linux operating system.
Download & install the Palm SDK for Linux, OS X or Windows.
Enable developer mode on the HP Touchpad:
Launch Device Info and tap its top-left menu.
Select "Custom Application..." and type in: ##3386633#
In the application, move the Developer Mode slider to the On position.
Tap Reset the Device.
When reset is complete, Developer mode is enabled.
Plug the device into the computer via the USB cable, and just close out the USB storage mode thing.
The next step varies:
Mac OS X / Linux: Type novaterm into terminal to directly access the Linux command line for the HP Touchpad.
Windows: you will need to download and install a novaterm program.
On Windows 32-bit, download novacom-win-32.tgz and install novacom with NovacomInstaller_x86.msi.
On Windows 64-bit, download novacom-win-64.tgz and install novacom with NovacomInstaller_x64.msi.
Then, just like the Mac and Linux users you can just type novaterm.
At this point you will have a window with a prompt that says [email protected]: or something similar.
You are now logged in as root on your webOS device and can do anything you would normally do on a Linux device.
DISCLAIMER: We cannot be held liable for any loss of data, damage, bricking, or other malfunctions of the device. We solely provide the information needed to achieve root access.
This quick sum up/start up guide might come handy:
http://forums.precentral.net/hp-touchpad/293028-new-touchpad-heres-your-get-started-guide.html
[Q] What is wrong with my touchpad?
RESET: Hold Power Button & Home Button until the tablet resets.
Doing the above solved the below issue.
My touchpad won't turn on I used it until it had about 30 % battery last night, but didn't put it to charge. When I woke up this morning, it was at 28% battery. I used it to check facebook and xda, locked it and put it down to watch the price is right but when I went to use it again, none of the buttons unlocked it. I plugged it into mulitple outlets and held the power button for about 30 seconds each time, but nothing is happening I don't know what to do. Can anybody help?
Click to expand...
Click to collapse
solution #2
this happened twice:
plug it in to pc
open webos quick install
tools - command line
type "reboot" and hit enter
Bill of Materials
$318 Bill of Materials
Comparisons
Comparisons
Exploded and PCB
Exploded and PCB
First non-webOS phone to be fully tetherd with HP TouchPad
First non-webOS phone to be fully tetherd with HP TouchPad
Worked for me, I had to fool with it a couple of times to get it to work. My screenshot is attached
The messaging does not work but the phone calls do.
How To: Connect TP to network shares
How To: Connect TP to network shares
spud101
Member
Join Date: Jun 2004
Location: Netherlands
Posts: 574
Likes: 34
Thanks: 43
Thanked 69 Times in 34 Posts
Updated (Sep 7th 2011):
Rewritten to include a method for stock kernel, make shares usable for KalemSoft Media Player & automount at (re)boot. Thx to everybody who contributed to this thread! (Under construction, finished later)
Updated (Aug 9th 2011): processed some comments from this thread and the fact that uberkernel now also supports CIFS (& NFS).
Prerequisites:
- HP Touchpad, webOS 3.0.2 or later.
- One of the following Kernels:
---- Stock kernel
---- Uberkernel 3.0.2-52 or later (Next to support for CIFS & NFS this kernel also supports UTF-8. More info here: WebOS Internals Uber-Kernel
---- F15C,.. (completed later)
- Terminal access to your TP, either via webOS Quick Install or Xecutah + Xserver + Xterm (install from preware)
- Internalz Pro with show hidden files set to yes
Three parts:
This guide has three parts:
Basic Mounting
Mounting with shares visible in apps like Kalemsoft Media Player
"Sticky" mounting: Auto mount at (re)boot
Definitions:
hostIP = IP address of the computer or NAS you want to connect to. You can use hostnames too, but need to also edit /etc/hosts then.
sharename = The share name you want to connect to as configured on your computer/NAS
mountpoint-path = as discussed above, e.g. /mnt/nas
cifs = type of filesystem to mount (cifs is better version of smbfs, I've been told)
auto (or can also be noauto) auto/noauto determines if the share is mounted automatically at startup.
username & password = share login credentials. There are probably safer ways to do this instead of having this plain text on your device, anyone can tell me how to do that?
rw = access mode, in this case read & write, other possibilities exist too
The numbers have someting to do with filesystem check at boot.
1a: Basic Mounting (without fstab)
- Create a mountpoint, a path where the share will be accessible, e.g. /mnt/nas or /mnt/media/internal/nas I used Internalz Pro in master mode for this.
- In a terminal type:
mount.cifs //<hostIP>/<sharename> <mountpoint-path> -o username=<username>,password=<password>
Example: mount.cifs //10.0.1.26/DataVolume /mnt/Shared -o username=foo,password=bar
1b: Basic Mounting (with fstab, not supported by stock kernel)
To be finished later
2: Mounting with shares visible in apps like Kalemsoft Media Player
To be finished later
For now please refer to:
Road to Success - How to allow NAS to show up under /media/internal on Touchpad Apps?
How To: Connect TP to network shares
How To: Connect TP to network shares
3: "Sticky" mounting: Auto mount at (re)boot
To be finished later
For now please refer to:
Road to Success - Mounting SAMBA/CIFS Permanently on Touchpad
-------------------------------
Original post:
In short: The stock kernel on a webOS 3.0.2 Touchpad does not support CIFS. Or at least I didn't get it to work just the same way I do get it to work out of the box on a 1.4.5 Pre-.
Then I saw this thread: F15B & F15C test kernels
It says CIFS support! So I hesitantly installed this experimental F15C kernel, quickly ran Govnah to set max speed to 1.5 GHz (I don't want no real overclocking beyond this speed). But, YES, it does work, I now can access my NAS!
After I initially posted this thread webosinternals also added support for CIFS (& NFS) to the uberkernel (as of version 3.0.2-36). Thanks a lot for that guys!!
So how to go about:
- Install the F15C kernel from the testing kernel feed
The rest is standard linux stuff for mounting Samba shares:
- Create a mountpoint, a path where the share will be accessible, e.g. /mnt/nas or /mnt/media/internal/nas I used Internalz Pro in master mode for this.
- Open /etc/fstab again you can use Internalz Pro in master mode for this
Add a line:
//<hostIP>/<sharename> <mountpoint-path> cifs auto,username=<username>,password=<password>,rw 0 0
hostIP = IP address of the computer or NAS you want to connect to. You can use hostnames too, but need to also edit /etc/hosts then.
sharename = The share name you want to connect to as configured on your computer/NAS
mountpoint-path = as discussed above, e.g. /mnt/nas
cifs = type of filesystem to mount (cifs is better version of smbfs, I've been told)
auto (or can also be noauto) auto/noauto determines if the share is mounted automatically at startup.
username & password = share login credentials. There are probably safer ways to do this instead of having this plain text on your device, anyone can tell me how to do that?
rw = access mode, in this case read & write, other possibilities exist too
The numbers have someting to do with filesystem check at boot.
- Save the file
- Open a terminal
- type in this command:
mount -t cifs //<hostIP>/<sharename> <mountpoint-path> -o username=<username>,password=<password>
No idea whether all the -o options are still needed, as they are in the fstab line already as well.
Apparently mount -a should also mount your shares inside fstab. But for me that didn't work, maybe because I have it set to noauto.
This should do it.
Unmounting as follows:
umount <mountpoint-path> e.g. umount /mnt/nas
Note: as soon as you have a kernel running that supports CIFS, you can also use the xt tools. See this thread and the threads referenced inside it. samba filesharing - install/support thread
The xt tools will take over all the fstab editing and directory creation.
I agree this is still cumbersome. On an Android phone for example this is buildin in every decent filemanager. So I really, really hope that either or both Gemini and Internals HD will have some easy solution for this (both configuring and the actual mounting/unmounting). Or a solution straight from HP, this is also aimed at enterprise market after all!
Last edited by spud101; 09/08/2011 at 07:41 PM.
Thanked by 60milesmile, cookie_42, El_Titi, flyers333, ichi2k, Major Payne, mivoligo, Nightburn, obarthelemy, PF Graham, phil71, pre101, RickNeff, runner77, sf3000, sjp770, sps_2k1, tabaloos, teng_lin, thomaz, timjhenry, tlaswell
Weird shortcut to USB mode
Has anybody else seen this?
While connected to PC in "just charging" mode I reached out and accidentally hit the Volume Down and Power buttons at the same time. The TouchPad instantly switched to USB Storage mode.
Interesting behavior and I couldn't seem to find any mention of it anywhere.
PreCentral had it as a tip on their web site about a week ago and I spotted it there - http://www.precentral.net/access-usb-mode-touchpad.
Quite a few other useful titbits crop up on there - it is worth following. I use the webOS News app from the App Catalog. That gives heads-up on the free software codes as well.
dmarchant said:
PreCentral had it as a tip on their web site about a week ago and I spotted it there - http://www.precentral.net/access-usb-mode-touchpad.
Quite a few other useful titbits crop up on there - it is worth following. I use the webOS News app from the App Catalog. That gives heads-up on the free software codes as well.
Click to expand...
Click to collapse
LOL, I think you mean "TIDBITS."
Too bad there is no reverse version of this.
Okay so I didnt really come across alot of central material on how to do this with Nook or if it even could. Since storage capacity is an issue most HD content is probably not going to be getting stored on most users tablets. I would guess that alot of users already have lots of content on their personal computers. If you have a decent wireless router configured correctly it shouldnt be a problem to be able to stream this content to the nook. The nook tablet has a decent amount of ram and the cortex a9 is more than sufficient to stream, so i was bored and figured id give it go.
What you will need to do this
Rooted Nook Tablet 8gb or 16gb shouldnt matter - for documentations sake im running aokp milestone
Personal Computer with somewhat organized media structure
Hanewin NFS Server Easy to setup in windows
BusyBox Installer Latest version of BusyBox - BusyBox Installer is what we used
MX Player seems to be the best android video player ive come across
Neon Codec is compatible with our processor and is necessary for decoding files with dts audio
Its important to organize your movies into a single folder if possible to decrease on mountpoints. If you must use different folders, try and name them movies1 movies2 movies3, etc
After organizing download and install hanewin. Make sure UPnP is enabled on your router it saves you from having to fwd ports later on.
Open Hanewin in the general tab uncheck UDP and check version 2 and 3, and check TCP.
On the server tab, Check "allow mount of remote devices", check "Reset innode table", check "convert windows drive letters", and check "utf-8 charset"
On Exports Tab, click on edit exports file. You need to setup like this:
Code:
my\path\towindows\folder -name:movies
my\path\to\someother\windows\folder -name:movies2
once you have entered all of your shares, save the file as exports.
now click restart server button on the right hand side.
you should see your mounts show up in the box.
Now download and install busyboxinstaller on your nook
type in mount script in busybox installer on the scripts tab by clicking the plus sign in the top right
name the script whatever you want
then in the command section type the following: You do not have to put the extra /sdcard/movies2 or so on if you are only mounting 1 folder
Code:
mkdir -p /sdcard/movies /sdcard/movies2 /sdcard/movies3 /sdcard/movies4
busybox mount -o nolock,tcp,hard,intr my.pc.ip.address:/myfoldermnt /sdcard/movies
the -p option on mkdir will check to see if the directory exists, if not it will create it
the mount command must be formatted exactly the same swapping out mypcipaddress for your local lan ip, and myfoldermnt for whatever you called your nfs share in your exports file, then mounting on the directory /sdcard/movies
once finished save the script and run it, then use root explorer to check and make sure /sdcard/movies exists and has your nfs content inside
you can set this script to run at boot also, if you are not at home no worries it will just error out and continue booting without you noticing
Setting up the Nook
Download Neon Codec
extract the neon folder to the root of either your internal or external sdcard
Download and install MX Player
Once installed configure it. Your movies may show up in the folder, dont attempt to play them yet.
click on settings and goto decoder
Make sure "Use h/w+ decoder" "h/w decoder local" "correct aspect ratio" are checked and nothing else
Now scroll to the bottom and you should see "custom codec" click it
navigate to the sdcard where neon folder is located. click on neon then click ok once the folder contents are displayed
MX Player is now setup, completely exit out of it
This next step is important because without it the h/w decoder buggers out and you are stuck with software decoder
navigate to main settings for tablet, enable developer options
scroll almost to the bottom and check "disable hw overlays"
now would be a good time to set your custom mount script in busybox installer to run at boot
now restart your nook
Open MX Player and you might not see your content, click the refresh symbol at top right and it should appear
select your movie of choice and go
enjoy full hd movies on your tablet!!!
I've seen a couple of older posts, but I haven't been able to get it worked out.
Is it possible to mount Network share so that I can watch various movies, etc off my of a home server? I have a small server in my basement running unraid with a samba share.
I have a rooted Nexus 10 with Cyanogenmod 10 installed on it.
Any help would be greatly appreciated.
ptmuldoon said:
I've seen a couple of older posts, but I haven't been able to get it worked out.
Is it possible to mount Network share so that I can watch various movies, etc off my of a home server? I have a small server in my basement running unraid with a samba share.
I have a rooted Nexus 10 with Cyanogenmod 10 installed on it.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I use CIFS manager or ES File Explorer to mount network shares.
Also you may want to post in the relevant device section, this is samsung galaxy tab 10.1 , not nexus 10.
CIFS natural mount needed - howto?
My device is:
Samsung Galaxy Tab V2 10.1 P5100 (P5100XXDLL2 baseband)
Kernel 3.0.31 - 1069185
JZO54K.P5100XXDMC3 buildnumber
Android 4.1.2
PS: This was the oficially suported French/German/... update version to Android 4.1.2 for P5100 with WiFi, GPS and 3G
----------
I need realy CIFS / Samba mount on this device. Realy i mean, that the shares on Samba servers mounted here will be available for each application running on that Samsung tablet as if it would be an drive/directory on his internal flash. I mean, this is the the standard operating principle on Windows / Linux computers. I do not need especialy managers with CIFS uspport, i need CIFS support naturaly for the whole Android system.
I readed tonns of postings and tested to load cifs.ko, nls_utf8.ko, md4.ko, dns_resolver.ko modules via MountManager and similar other applications, but without success. The Mount Manager & Co. tell me always, the modules cannot be loaded, because the version numer of my build is not compatible withe the versionsnumber of this modules.
If you can me help, pls tell me, what to do, that i can activate CIFS access in the Android:
- need to flash a new kernel?
- need to get the *.KO modules for my Adroid/Kernel version? Were? Till this time found nothing!
- what is the easiest way?
I do not need any especialy features, because except Samba mount i have all, what i need. The Samsung is properly rooted, it can see via the USB adapter each partition/file on external USB harddrive (on 2 TB too, its nice) and can play movie from them, ... and so far.
Help me if you can pls.
Thx,
Feri
100% solved mounting of network shares Samba/CIFS on Galaxy
I solved my SAMBA / CIFS on Samsung Galaxy Tab 10.1 V2
Infos to my device (important, because other CIFS.KO and Co. do not work with them!!!) You must have the right modules for you firmware version. Otherwise it will do not work!
SAMSUNG GALAXY TAB 10.1 V2
Modelversion: GT-P5100
Basebandversion: P5100XXDLL2
Kernel: 3.0.31-1069185
[email protected] #1
SMP PREEMPT Fri Mar 29 18:55:40 KST 2013
Buildnumber: JZO54K.P5100XXDMC3
Android version: 4.1.2
(This was the oficial German/French/... version for Europe for unbranded devices)
Module files i found here: http://forum.xda-developers.com/showthread.php?t=2088515&page=2
Direct links to the files: http://forum.xda-developers.com/attachment.php?attachmentid=1710219&d=1360209542
Configuration and HOW TO:
- Files loaded from above link into: system/lib/modules
- Changed the file attributes to 755 (i do not know if it was usefull, but i does it)
- Installed Cifs Manager
- Made directory: storage/sdcard0/cifs/nas2
- Turned my NAS server on (address 10.0.0.251 local)
- In the CIFS MANAGER settings:
cifs module load: yes
load per insmod: yes
path to cifs.ko: system/lib/modules/cifs.ko -> other modules may be added, ':' will be used to separe the modules
- In the CFS MANAGER - add share (or edit existing share - long tap on share name)
share path: 10.0.0.251/raidz2_main
mount point: storage/sdcard0/cifs/nas2
name: set your Samba access name
password: set your Samba access pasword
options: (nothing to set)
Then do short tap on the share in the CIFS MANAGER and it should be green! Long tap for edit (if not mounted). If mounted short tap for file manager over this share.
If cannot be mounted, controll all - look in the INFO from CIFS MANAGER, if the modules are loaded. Do not give SLASH or BACKSLAH character on begin or end of the parameters, like "/10.0.0.251/raidz2_main/" !!! both slash on begin and at the end are to be removed!
If nothing helps, may be, your *.ko modules don't have the apropriate version to your tablet firmware. You must looking around for in the internet. Sorry - may be someone can help you
PS: MOUNT MANAGER was instable - many crashes, if i trying to mount my NAS server. I know, they are thousend big files on it, but the settings made like described before working wery well, so i think it is better to use CIFS MANAGER! The MOUNT MANAGER give me other error to see - if i try to select the share from the names list, they give me bad address to see and told me, cannot find this share. Only manual entry of the address was ok. But one good thing is if you use MOUNT MANAGER - they have logging - and in the logs you can see, what of setting or *.ko module are not loaded and why!
Best regards, i hope this help someone to solve problems.
Feri
PS: I have tested it on Seagate Wireless Plus WiFi external harddisk drive with firmware from http://hackseagatesatellite.com/ It works fine, may be a little bit slow, but it works! In this drive i had changed the 1TB HDD against 128 SSD, so i have more battery lifetime and no problems with mechanical crashes.
The settings for this drive are here:
- Made directory: storage/sdcard0/cifs/plus
- Turned my Seagate wireless Plus on (address 172.25.0.1 - it is the default for this drive with Hackersatellite firm local)
- In the CFS MANAGER - add share (or edit existing share - long tap on share name)
share path: 172.25.0.1/seagate
mount point: storage/sdcard0/cifs/plus
name: set your Samba access name for this drive
password: set your Samba access pasword for this drive
... all others leave set like above. And it works! For details go here:
http://hackseagatesatellite.com/privateforum/viewtopic.php?f=13&t=1444&p=7558#p7558
Hello guys, I have a problem with this box: the system partition was tempered with (they tried to remove root) and I want to flash a new rom to fix it.
I opened it to check the hardware but the manufacturer have shielded the wifi chipset so I can't read the numbers on it.
Dmesg says:
Code:
dhd_conf_set_chiprev: chip=0x4334, chiprev=3
And I found these files in etc/wifi/
p2p_supplicant_overlay.conf
wpa_supplicant.conf
Folder 40183
config.txt
fw_bcm40183b2.bin
fw_bcm40183b2_apsta.bin
fw_bcm40183b2_p2p.bin
fw_bcm4334b1_ag.bin
fw_bcm4334b1_ag_apsta.bin
fw_bcm4334b1_apsta.bin
fw_bcm4334b1_p2p.bin
nvram.txt
So it's a broadcom4334, right? Too bad I haven't found any rom that clearly states bcm 4334 or 40183 and s905x, except this
Full specification as read from the amazon page @ https://www.amazon.it/gp/product/B0788MX52X/
OS: Android 7.1.2
Bluetooth: 4.0
CPU: AmlogicS905X Quad Core Cortex A53 a 1.5 GHz 64 bit
GPU: Penta-core Mali-450MP
RAM: 2 GB DDR
ROM: 16 GB EMMC
Wifi: IEEE 802.11 a / b / g / n, Dual-Band 2.4G/5G
LAN: 10 / 100M, standard RJ-45
The Motherboard (Aida says it's p212) doesn't have an hidden button, unlike other boxes, but I can boot into recovery using a terminal emulator
Of course I tried reaching to goobangdoo but they haven't replied.
Edit: typos
Edit: updates
I want at least root the box, I found
deamonsu, su, su.bak in system/xbin
su in sbin
Rootchecker says root is not installed properly.
I have the UPDATE&BACKUP and I used it to install:
UPDATE-unSU-signed.zip > deletes nothing
SuperSU-v2.82-201705271822 > bad recovery error
Magisk-v16.0 > failed to find meta-inf/com/android/metadata in update package
Everything failed and I tried from recovery, same thing.
I can still return the box so I'm trying not to install twrp since I don't have the stock recovery.
I'm stuck.