Related
Hi,
I recently got to know, that my tab is using UBIFS as file system...what are the advantages compared to the normal ext2-ext4?
I thought about migrating to the ext filesystems, but if someone tells me that UBIFS is better, I'd stay on UBIFS...
Regards
Hi,
TheSSJ said:
Hi,
I recently got to know, that my tab is using UBIFS as file system...what are the advantages compared to the normal ext2-ext4?
I thought about migrating to the ext filesystems, but if someone tells me that UBIFS is better, I'd stay on UBIFS...
Regards
Click to expand...
Click to collapse
the problem running ext2/3/4 on flash is - sooner or later you will kill the flash. One might not notice it say, on a USB stick, when data is just copied from one place to another occasionally, but things look different if you use it as your root file system where things get written onto it all the time.
I am sure there are more of them around, I am only familiar wit JFFS2 and UBIFS, both are designed for flash media and implement wear leveling routines to make sure that the flash lasts longer.
JFFS2 is somewhat old now, UBIFS is newer and from what I know - better.
I use devices with UBIFS at work and it proved itself very robust, during development I often simply plug off mains without a clean shutdown and I still never ran into a file system corruption or anything like that. So, good to know that our tablets use it
Kind regards,
Jin
Thanks for the clarification. Another question:
Does any kernel support UBIFS or do I normally need to insmod the corresponding module?
TheSSJ said:
I recently got to know, that my tab is using UBIFS as file system...what are the advantages compared to the normal ext2-ext4?
I thought about migrating to the ext file systems, but if someone tells me that UBIFS is better, I'd stay on UBIFS...
Click to expand...
Click to collapse
Different things, different usages.
UBIFS, YAFFS2 etc are file systems for NAND flash devices. Those memories are not block devices.
EXT3, EXT4, VFAT etc are file systems for block devices, and can not use non block devices such as NAND flash devices.
To be able to use a block device file system on a NAND device, you'll need a Flash Translation Layer (FTL). In every USB memory stick, SSD, SDcard etc, you are viewing the NAND flash via such a translation integrated into the device itself, hence you are able to format is using an ordinary file system such as FAT or EXT4. In GNU/Linux (hence Android as well), you've got such a translation layer in the MTD device (look in /proc/mtd).
TheSSJ said:
Thanks for the clarification. Another question:
Does any kernel support UBIFS or do I normally need to insmod the corresponding module?
Click to expand...
Click to collapse
Theoretically it should be doable if you compile the ubifs modules for your kernel, I did not try that yet, when I was using it for some non tablet ARM9 boxes I simply compiled it into the kernel:
CONFIG_MTD_UBI=y
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
CONFIG_UBIFS_FS=y
CONFIG_UBIFS_FS_XATTR=y
kuisma said:
Different things, different usages.
UBIFS, YAFFS2 etc are file systems for NAND flash devices. Those memories are not block devices.
EXT3, EXT4, VFAT etc are file systems for block devices, and can not use non block devices such as NAND flash devices.
To be able to use a block device file system on a NAND device, you'll need a Flash Translation Layer (FTL). In every USB memory stick, SSD, SDcard etc, you are viewing the NAND flash via such a translation integrated into the device itself, hence you are able to format is using an ordinary file system such as FAT or EXT4. In GNU/Linux (hence Android as well), you've got such a translation layer in the MTD device (look in /proc/mtd).
Click to expand...
Click to collapse
It turned out that TrekStor Ventos 9.7 tablet uses ext4 file systems, does that mean that this is because of the way how they integrated the flash?
As far I know that for USB sticks / SDcards you can not get around the FTL, would be interesting if this is also the case for the Ventos tablet or if switching to UBIFS would be possible there. Main problem with FTL in my opinion is, that it is usually optimized for specific use cases and mostly those use cases do not include write patters that you have when the device is used as a root file system. That's where UBIFS does a much better job at preserving the flash.
Jin^eLD said:
It turned out that TrekStor Ventos 9.7 tablet uses ext4 file systems, does that mean that this is because of the way how they integrated the flash?
Click to expand...
Click to collapse
Somewhere you'll need the FTL. If using MMC technology, it's in the memory device itself.
Jin^eLD said:
As far I know that for USB sticks / SDcards you can not get around the FTL, would be interesting if this is also the case for the Ventos tablet or if switching to UBIFS would be possible there.
Click to expand...
Click to collapse
If FTL in software, such as in the MTD case, this would be possible, yes.
Jin^eLD said:
Main problem with FTL in my opinion is, that it is usually optimized for specific use cases and mostly those use cases do not include write patters that you have when the device is used as a root file system. That's where UBIFS does a much better job at preserving the flash.
Click to expand...
Click to collapse
Android places its root file system in RAM, not in flash.
The FTL is what differs the flash memory (SSDs, MMCs etc) vendors from each other. Some manufacturers priorities read speed, other write speed, and yet other random access etc. Some uses more spare chips extending the life of the device, at the cost of a more expensive unit. Other throttles the write speed to guarantee the functionality during the warranty period. Basically you'll get what you pay for.
kuisma said:
Android places its root file system in RAM, not in flash.
Click to expand...
Click to collapse
Oh.. OK, I did not know that, I'm still quite new to Android. So far I've been playing around with ARM9 devices, building root file systems with OpenEmbedded, but just starting with Android now.
kuisma said:
The FTL is what differs the flash memory (SSDs, MMCs etc) vendors from each other. Some manufacturers priorities read speed, other write speed, and yet other random access etc. Some uses more spare chips extending the life of the device, at the cost of a more expensive unit. Other throttles the write speed to guarantee the functionality during the warranty period. Basically you'll get what you pay for.
Click to expand...
Click to collapse
-> "Basically you'll get what you pay for."
That's what I fear I had very positive experiences with UBIFS so I'd rather rely on it doing the job than on an FTL, which I know nothing about, that is used in my el-cheapo tablet.
Jin^eLD said:
Oh.. OK, I did not know that, I'm still quite new to Android. So far I've been playing around with ARM9 devices, building root file systems with OpenEmbedded, but just starting with Android now.
Click to expand...
Click to collapse
Also, once booted, it remounts root as read-only, so I wouldn't worry too much about wear leveling.
Jin^eLD said:
-> "Basically you'll get what you pay for."
That's what I fear I had very positive experiences with UBIFS so I'd rather rely on it doing the job than on an FTL, which I know nothing about, that is used in my el-cheapo tablet.
Click to expand...
Click to collapse
Sure, if you know what you are doing, controlling the FTL, and you can optimize the performance for the particular task you are using the device for. Buying a ready-to-use device using an integrated FTL, and the manufacturer have no other choice than adjusting the FTL parameters for the average customer usage. Still, in most cases I would say this is good enough and the risk of manually creating an even worse profile is quite likely for a noob such as myself.
kuisma said:
Different things, different usages.
UBIFS, YAFFS2 etc are file systems for NAND flash devices. Those memories are not block devices.
Click to expand...
Click to collapse
Oh, this explains why I got a corrupted recovery by dumping /dev/block/mtdblock3 on my uImage/ubifs powered tab...It worked when I dumped /dev/mtd/mtd3 though...
Thanks for the explanation!
need help !!!!!!!!!!!!!!!!!!!!!!!!!!!
hey bro
how can i take backup of my ubifs rom
and flash ubifs rom on my mt6572 ( in case needed)
TheSSJ said:
Hi,
I recently got to know, that my tab is using UBIFS as file system...what are the advantages compared to the normal ext2-ext4?
I thought about migrating to the ext filesystems, but if someone tells me that UBIFS is better, I'd stay on UBIFS...
Regards
Click to expand...
Click to collapse
Hey bro, you said youll migrate to ext4 if it is better. How can you that? Ive been searching for a way to format my ubifs phone to ext4. I hope you can help me
My M9S-Pro finally arrived. It's a modest AmLogic S905 chip with a Mali-450, notably only because it has Ethernet, three USB ports, 3 GB of RAM and a 32 GB ROM.
My kids use the Nexus Player as a gaming device, but I am constantly running out of space even with Marshmallow's USB space reallocation (which does not work perfectly by any means). I bought this hoping to replace the Nexus Player which only has 8GB (+ whatever Marshmallow offers, and whatever some apps will allow transfer to external storage).
Right off the bat, it boots quickly and is stable. It included Kodi, some generic TV streamer with pay TV streams in foreign languages, a file manager, Antutu, various video players, and Netflix. The USB port puts out enough current to power an external 2.5" HDD.
Antutu score is 31,300 if that matters to you.
I found a version of TWRP that worked great and I rooted this by flashing the same beta-SuperSU as I used on my Nexus Player.
It uses an IR remote with shortcuts to different apps and a mouse function. It's slow but usable. I use it with an airmouse with a better experience.
I am running HAL Launcher which is just about the best experience you can hope for with a Chinese box. I also added the keylist for the Bluetooth controllers from the OUYA that I had years ago, and my kids use it for a gaming box.
It's a good value for me, but if you use Android TV boxes for streaming only you don't need the space and should probably get a cheaper box - maybe one running 6.0+ so it supports the latest version of Kodi.
Now that I have TWRP and root, I am looking for an AOSP experience.
Are these available for AmLogic systems? I've seen RemixOS for certain AmLogic boxes, but they're all a bit different and haven't tried experimenting with that yet.
How did you get this device rooted and how did you boot it into TWRP?
If rooted the Docooler, could I run a Long Term Release of Ubuntu or Mint on it. I've used Linux with our Brother MFC-J835DW and its simple to print from any Application. Android not good at all. 2nd is with Ubuntu I can set up multiple guest users in various Languages "English" " "Spanish" etc. so a guest can log on , browse, print, done.
On Android it seems to remember Users, not sure how to delete,
Very hard to print "share",
Doesn't appear to allow set up to multiple users so can only run as 1 language.
I really like that these boxes have separate monitors, keyboards, and appear not to require a fan as we are at the beach with a lot of salt air. All my connections require DiElectric Grease from Autozone so as not to corrode. Even better would be a sealed heat sink case.
Ken PlayaLindaHotel.com
root m9s-pro docooler amlogic s905 how
how root and install twrp in that model please tell me
Send me the links of software that must to download
hello, i have the m9s pro 32gb and i have slow speed in WiFi connection. Does anyone have the same problem and how can i solved? thanks in advance
Hello everyone, where can I get the original stock firmware? tnx
shdware said:
My M9S-Pro finally arrived. It's a modest AmLogic S905 chip with a Mali-450, notably only because it has Ethernet, three USB ports, 3 GB of RAM and a 32 GB ROM.
My kids use the Nexus Player as a gaming device, but I am constantly running out of space even with Marshmallow's USB space reallocation (which does not work perfectly by any means). I bought this hoping to replace the Nexus Player which only has 8GB (+ whatever Marshmallow offers, and whatever some apps will allow transfer to external storage).
Right off the bat, it boots quickly and is stable. It included Kodi, some generic TV streamer with pay TV streams in foreign languages, a file manager, Antutu, various video players, and Netflix. The USB port puts out enough current to power an external 2.5" HDD.
Antutu score is 31,300 if that matters to you.
I found a version of TWRP that worked great and I rooted this by flashing the same beta-SuperSU as I used on my Nexus Player.
It uses an IR remote with shortcuts to different apps and a mouse function. It's slow but usable. I use it with an airmouse with a better experience.
I am running HAL Launcher which is just about the best experience you can hope for with a Chinese box. I also added the keylist for the Bluetooth controllers from the OUYA that I had years ago, and my kids use it for a gaming box.
It's a good value for me, but if you use Android TV boxes for streaming only you don't need the space and should probably get a cheaper box - maybe one running 6.0+ so it supports the latest version of Kodi.
Click to expand...
Click to collapse
dow did you root the device?
@alexxdj,
You'll need to do two things.
First, download TWRP for AmLogic devices. The link is below for a whole bunch of them.
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/16228-twrp-for-amlogic-devices
I don't remember which one I used, but I believe it was for a Minix S905 device. As long as it's S905, they are similar enough that you should be okay. Make sure it is scaled properly when you use it.
Then you'll need to download ChainFire's SuperSU.
https://download.chainfire.eu/743/supersu
Copy both files to a SD card. TWRP will be bootable, but you will need to press/hold the button that's hidden in the audio out jack. I simply used a pin. So, unplug the unit, insert the SD card, insert the pin, then plug it back in and wait for it to boot to TWRP.
If all looks well, great. You will need a mouse for this part.
Flash SuperSU as normal. Reboot.
After I booted, I actually had to run the supersu APK to make it work properly. I used Root Explorer (since it opens files in zip files with ease) to do this.
I hope this helps.
thanks for your information but where is this hidden button? I cant find it!!!
It's in one of the audio jacks in the back of the unit. Open it up if you need to see it: it comes apart easy and goes back together easy.
Otherwise get a long pin or needle and poke in the jacks until you feel it click.
shdware said:
It's in one of the audio jacks in the back of the unit. Open it up if you need to see it: it comes apart easy and goes back together easy.
Otherwise get a long pin or needle and poke in the jacks until you feel it click.
Click to expand...
Click to collapse
i found it is the spdif jack thanks. do you remember if needs to rename the recovery? Because i downloaded the recovery for minix s905 but i cant boot it to twrp
Try naming it 'recovery.img'
The recovery should not be zipped. Extract the IMG file if it is.
yes i know that. maybe i tried wrong recovery. after 2 times failed to boot to recovery. when i release the button? when i show the android and starts to erase?
alexxdj said:
i found it is the spdif jack thanks. do you remember if needs to rename the recovery? Because i downloaded the recovery for minix s905 but i cant boot it to twrp
Click to expand...
Click to collapse
I press and hold it until the TWRP logo appears.
I think you have the wrong recovery. Try the MINIX MX one. AmLogic makes a lot of devices, and the S805, S812, S905, and S912 all require different recoveries.
You need to make sure it's for the S905. Google is your friend here.
After I successfully rooted, I ultimately decided to flash TWRP itself on my box.
i tried 50 recovery for s905 form yesterday but nothing. Cant boot to twrp!!
alexxdj said:
i tried 50 recovery for s905 form yesterday but nothing. Cant boot to twrp!!
Click to expand...
Click to collapse
Apologies, I didn't realize the URL to Freaktab was truncated. I've corrected it now.
TWRP for AmLogic Devices
Try a few of these. There are only 31, and over half of them can be discounted because they are not for the S905.
If I remember right, I used this one:
/TWRP_MiniMX.img
shdware said:
Apologies, I didn't realize the URL to Freaktab was truncated. I've corrected it now.
TWRP for AmLogic Devices
Try a few of these. There are only 31, and over half of them can be discounted because they are not for the S905.
If I remember right, I used this one:
/TWRP_MiniMX.img
Click to expand...
Click to collapse
You remember right!!!! this recovery was. thanks for your help friend.
@Gi3drius, @k_graham, @stilonas -
I've provided a tutorial. Read the comments and let me know if they help.
is there any update for this tx box?? and why do you want to install TWRP? I use it only fr install roms but I can´t find any for this model
By mistake, I installed REMIX OS on a full HD partition of 500GB...
Everything runs fine but would like to migrate to a smaller HD.
Is there a way either to:
- clone my HD on another smaller HD, or
- to reduce my installation size on this HD in order to be able to use some free space GB for Windows storage?
Thanks!
dsl25 said:
By mistake, I installed REMIX OS on a full HD partition of 500GB...
Everything runs fine but would like to migrate to a smaller HD.
Is there a way either to:
- clone my HD on another smaller HD, or
- to reduce my installation size on this HD in order to be able to use some free space GB for Windows storage?
Thanks!
Click to expand...
Click to collapse
You can run a live usb Linux, and resize the partition with tools like gparted.
vampirexhunter said:
You can run a live usb Linux, and resize the partition with tools like gparted.
Click to expand...
Click to collapse
Thanks for this but I'm not familiar with Linux...
Any further instructions welcome!
dsl25 said:
Thanks for this but I'm not familiar with Linux...
Any further instructions welcome!
Click to expand...
Click to collapse
Unfortunately, I only know how to do it with linux.
Personally, its the easiest way to do it without paying for additional software.
Best of Luck.
Yep, I understand but there are some portable free Windows applications for that also.
I only wonder whether I may use Windows programmes for doing this.
What sort of partition is usually Android installed on? FAT32?
dsl25 said:
Yep, I understand but there are some portable free Windows applications for that also.
I only wonder whether I may use Windows programmes for doing this.
What sort of partition is usually Android installed on? FAT32?
Click to expand...
Click to collapse
If you want the best compatibility, it should be installed on EXT4 partition.
vampirexhunter said:
If you want the best compatibility, it should be installed on EXT4 partition.
Click to expand...
Click to collapse
Yep, I finally managed to run the graphic mode of gparted (magic) and everything seems to be easier from there.
Many thanks for your patience and help!
What to do with "NFS support in custom kernel"? How to mount a NFS share on android?
We often see NFS support in custom kernels but is it really useful in mounting a NFS share on android? How do I go about it? I don't want app level buy system level access to NFS mounts so all the apps can't access them.
Running Lineage OS (PIE) with root. My kernel claims NFS support.
blazzer12 said:
We often see NFS support in custom kernels but is it really useful in mounting a NFS share on android? How do I go about it? I don't want app level buy system level access to NFS mounts so all the apps can't access them.
Running Lineage OS (PIE) with root. My kernel claims NFS support.
Click to expand...
Click to collapse
At best I've seen int the app store is SMB clients but that will not allow you to mount and re-map other apps to those shares. It would only persist for that one app session and unmount after closing. I'm currently looking into compiling the SMB/NFS modules for android but am a tad behind for experience in that area.
Once you have the support it should be as simple as using the mount command and fstab to permanently get things going.
Solace50 said:
At best I've seen int the app store is SMB clients but that will not allow you to mount and re-map other apps to those shares. It would only persist for that one app session and unmount after closing. I'm currently looking into compiling the SMB/NFS modules for android but am a tad behind for experience in that area.
Once you have the support it should be as simple as using the mount command and fstab to permanently get things going.
Click to expand...
Click to collapse
When searching I came across a github repository that claims to work on android. But some one with the know how needs to compile it.
libnfs
LIBNFS is a client library for accessing NFS shares over a network.
Android:- tested with NDK r10e - running on Android 4.4 (should work starting from 2.3.3)
Click to expand...
Click to collapse
Once you have the support it should be as simple as using the mount command and fstab to permanently get things going.
Click to expand...
Click to collapse
Being on Android means the device is mobile, it may or may not be able to connect to the server. NFS mounts might act weird if there is no connection. Something like autofs (that automatically mounts and dismounts according to context) might be required. Otherwise normal apps might have bad time.
Being a mobile device is just another device. Connectivity remans the same avenue whether its targeting internal or external addresses. Either way any issues would be solved after getting the base down which is any kernel modules and potentially busybox.
Where did you come across the repository what you mentioned?
Also you said the kernel supports NFS mounts did you check this under your supported filesystem's? So far no version of android I have touched natively supports the use of nfs or cifs/smb. Yet there are apps that provide the functionality but not persistent mounts. Cat /proc/filesystem to check.
Solace50 said:
Where did you come across the repository what you mentioned?.
Click to expand...
Click to collapse
Github repository link : https://github.com/sahlberg/libnfs
I was just searching for "android nfs" and came across it by chance.
Solace50 said:
Also you said the kernel supports NFS mounts did you check this under your supported filesystem's? So far no version of android I have touched natively supports the use of nfs or cifs/smb. Yet there are apps that provide the functionality but not persistent mounts. Cat /proc/filesystem to check.
Click to expand...
Click to collapse
It is a custom kernel so devs will try to throw in as many features as they can.
Code:
# cat /proc/filesystems | grep nfs
nodev nfs
nodev nfs4
nodev functionfs
I'm not sure why you would need to compile anything, all you need to do is mount the NFS. Perhaps try busybox to do so.
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
Q1 FIRMWARE #1
666.25 MB file on MEGA
mega.nz
Q1 FIRMWARE #2
683.48 MB file on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk, an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
##Edit## Updated 13/02/2021
Bertonumber1 said:
Hey guys and girls, so its a struggle to find firmware for these newer boxes anywhere. The Q1 X96MAX Plus is a revised version of the older model and contains a different WiFi radio set and Ethernet chip.
The old firmware from the other X96max plus on the web if flashed Will brick him but he has an automatic mask mode built in. If you brick him.. Leave him plugged into USB A to USB A and run the firmware below, he will automatically connect and accept this firmware version.
Hope this helps some people as there's not much on this Box in respect of development.
Basically the lack of development is due to the Chinese running scarce of Realtek chips and using whatever they could find to finish production. So many developer are faced with a lottery of trying to figure what firmware WiFi etcetera will work on which box as these models seem to vary so much from box to box instead of the usual one size fits all.
Here it is download, extract and flash with Amlogic UBT :
File on MEGA
mega.nz
Regards
Firmware link is courtesy of Vasily Schevchuk an amazing bloke check out his site here :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
Click to expand...
Click to collapse
The file you posted is no longer available. Could you post it again? Thanks a lot!
lchang.atsoft said:
The file you posted is no longer available. Could you post it again? Thanks a lot!
Click to expand...
Click to collapse
OP updated, 2 newer firmwares, also check out Vasily' site
Bertonumber1 said:
OP updated, 2 newer firmwares, also check out Vasily' site
Click to expand...
Click to collapse
Thank you for posting the files again. Do you know firmware for it that is rooted?
Will this firmware work on the older X96max Plus models?
delucai7 said:
Will this firmware work on the older X96max Plus models?
Click to expand...
Click to collapse
No there is a firmwares for that model. Search for vasily-ts vasikh shevchuk and slimhouse have great firmwares for amlogic boxes.
Regards
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
wonzay said:
Hi.
Is there any way to get rooted firmware for X96 Max+ Q1? Maybe someone know how to root it via twrp/magisk? I know that SuperSu may brick device causing bootloop.
Click to expand...
Click to collapse
Hello, I was talking to someone on YouTube about this earlier too.
There maybe a rooted firmware from Vasily Shevchuk :
https://www.evolutiontv-vs.com/uncategorized/блог-системных-файлов.html
scroll to near bottom of page.
I'm afraid TWRP only works via USB and won't give you root privileges on this System as Root device.
You're best bet is to install slimbox rom and patch magisk to boot. At least that way you will have a root and manager app to control it.
Here is a link to slimhouse slimbox firmwares :
project slimBOXtv
A project to create firmware for TV boxes and sticks with an Amlogic processor. Amlogic S905X, S905X2, S905X3, S912, S922, S905W, S905W4, S905Y2, S905L (Android 9) Amlogic S905X4, S905W2, S905Y4 (Android 11) slimBOXtv ATV and AOSP are two...
forum.xda-developers.com
You will also find more help and guidance in that amlogic thread with regards to what you want.
Regards
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
wonzay said:
Thanks for the info. I will try slimbox maybe, but something in stock rom is not clear for me. When I type "su" in console, there is no error message like "su not found", but something similar to "you have no rights to access this executable". I thought that I am be able to boot twrp, mount system as r/w and do some kind of "magic" via commands "chmod&chown". Maybe it's a little bit naive idea.
Sorry for language, it's not native for me.
Click to expand...
Click to collapse
Hmm I can't remember if it was this box that had the su file in the xbin folder but it needed chmod permissions to work.
By far the easiest way is to just connect via USB, get rid of stock rom an use slim, then patch the boot. Save yourself the headache
Regards
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
:/ $ ls -lh /system/xbin/su
-rwsr-x--- 1 root shell 16K 2008-12-31 17:00 /system/xbin/su
Click to expand...
Click to collapse
wonzay said:
I will try slimbox, but in the future. This is not my tv box, you know.
Found su here:
Click to expand...
Click to collapse
Ah.. So it was that box.. Then maybe change permissions and make it executable.
You may not have proper root but it should get you a root shell at least
Regards
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
wonzay said:
Which version of twrp should I use to do that? This is X96 Q1 4/64 box. I don't wanna brick it. I need root shell to change keyboard's config file ("enter" key in hardware bt keyboard doesn't work properly).
Click to expand...
Click to collapse
You'll only have twrp with a custom rom installed, stock firmware = stock recovery slimbox or one of vasilys roms and it will be a recovery.img via USB flash drive that boots from the update menu.
Have you tried installing a soft keyboard such as SwiftKey, Leanmey or some other that will change default settings?
I was using Leanmey without issues with a Rii mini USB keyboard/mouse.
Again, you're best bet is to flash the slimhouse firmware. These boxes are pretty indestructible and have a built in auto mask rom mode that kicks in after 5 minutes during brick and will accept stock firmware again regardless (so don't worry) .
Hope this helps
Regards
Do you mean in this way?
Bertonumber1 said:
I was using Leanmey without issues with a Rii mini USB keyboard/mouse
Click to expand...
Click to collapse
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
wonzay said:
Do you mean in this way?
I will try this. I have tried "simple keyboard", but no success. Enter key doesn't work properly when software keyboard is hidden, because "key 28" in the file "/vendor/usr/keylayout/Generic.kl" has wrong value "DPAD_CENTER" instead of "ENTER". No root = no fun, but at this moment I don't need slimbox, because everything works fine (bt, wifi, hw mouse&keyboard, even custom adw launcher/adaway/yt vanced), except this stupid enter.
Click to expand...
Click to collapse
Your box sounds identical to all my devices app wise ( you missed Newpipe for downloading though )
How did you get on with this? There is three options, you may try inserting the lines for the key into the file or you may try flashing another firmware... If that fails try another keyboard.
I don't know if you've done this already though
Regards
I have left this subject alone (for a time). "Enter" key works via AOSP stock software keyboard - it has option to set default key. The only disadvantage of this "method" is that the AOSP keyboard is visible on the screen.
Ok, I figured it out, enter key works properly on my hardware bt keyboard. X96 MAX+ Q1 gains superuser powers when is connected via adb (root) over wifi. I remounted "read-write" /vendor partition, went to file "/vendor/usr/keylayout/Generic.kl" (make a backup!) and changed the line "key 28 DPAD_CENTER" to "key 28 ENTER". Don't forget to mount back /vendor as "read-only". At the end reboot your box.
Useful commands:
adb:
Code:
adb root
adb connect [ip address of the box]
(backup Generic.kl)
adb pull /vendor/usr/keylayout/Generic.kl
adb shell
re-mount, read write & read only:
Code:
mount -o rw,remount /vendor
mount -o ro,remount /vendor
Shell text editor - only vi is avaliable on my box:
Code:
busybox vi /vendor/usr/keylayout/Generic.kl
On the other hand you can pull "Generic.kl" to your computer, edit it locally, then push to "/vendor/usr/keylayout/" and chmod it correctly. The funny thing is that the "Generic.kl" in "/system/usr/keylayout" has right value for the key 28, but "vendor" path has a higher priority (I think).
ADB can be run directly from the box too, just use app called "termux" (get the latest version from "fdroid") and install in it "android-tools" package via the command:
Code:
apt update && apt install android-tools
Bertonumber1 said:
you missed Newpipe for downloading though
Click to expand...
Click to collapse
Similar tool for this purpose is "youtube-dl". I use it in termux (requires python3), but works anywhere python is installed (linux, windows, macos and so on).