I have the device mentioned in http://forum.xda-developers.com/showthread.php?t=1738650 (I can't post there yet) based on Telechips TCC8925.
Telechips releases the kernel source and it builds fine.
However, the kernel does not seem to be a in a partition with a file system.
I could find kernel strings in /dev/block/mtdblock0. This 10 MB block device starts with "4e41 5244" which seems related to fastboot.
Is there a way to somehow mount this type of partition and update the kernel? Thanks.
cnxsoft said:
I have the device mentioned in http://forum.xda-developers.com/showthread.php?t=1738650 (I can't post there yet) based on Telechips TCC8925.
Telechips releases the kernel source and it builds fine.
However, the kernel does not seem to be a in a partition with a file system.
I could find kernel strings in /dev/block/mtdblock0. This 10 MB block device starts with "4e41 5244" which seems related to fastboot.
Is there a way to somehow mount this type of partition and update the kernel? Thanks.
Click to expand...
Click to collapse
That's apparently standard for Android. I could use split_bootimg.pl script to extract it. I documented this step and a few others to modify the ROM at http://www.cnx-software.com/2012/08/22/how-to-create-a-custom-android-firmware-for-cx-01/
I think i am going to sell me CX-01 with tweaks on it let me know if you are interest
I think i am going to sell me CX-01 with tweaks on it let me know if you are interested
I really don't use it because i am usually not home so i don't have time for Movies
Does XS has a cifs.ko in stock rom to use samba shares? If not, as I assume, is there a way to get this module for an rooted XS? Or are there any custom kernels with cifs support, which I can use on a stock rom?
stm999999999 said:
Does XS has a cifs.ko in stock rom to use samba shares? If not, as I assume, is there a way to get this module for an rooted XS? Or are there any custom kernels with cifs support, which I can use on a stock rom?
Click to expand...
Click to collapse
If you gain root access to your XPERIA S(LT26i) you should be fine.
You can then use CIFS Manager and Samba Fileshaing as is your want.
I chose to use RaymanFX' ELiTE V2 Kernel on my XPERIA S in case that is a factor in making CIFS and Samba share operational, but I don't think it's required.
I'm using CIFS and Samba file sharing without any problems, no *.ko downloads required.
CIFSManager is only a manager, it needs cifs support in kernel.
But I will have a closer look at your kernel, at first sight it looks interesting.
I'm am using an SXAS and I've been looking into this, tool.
After some trying with different kernel modules I downloaded the kernel sources from Sony's developer webpage. And then it became very clear:
Theoretically our 6.2.B.0.200 firmware's kernel has integrated cifs support. The kernel config says so.
So I connected with adb and tried to mount via command line and looked at dmesg. It says: "CIFS VFS: Connecting to DFS root not implemented yet". This means: The kernel should be able to handle cifs, but there is a bug. Either it is the mount utility from the busybox I've installed or it is a bug in the kernel. Since our firmware uses a 3.4.0 Linux kernel and due to some googleing, I assume this to be a kernel bug.
You can find some source code patches in the internet. Maybe I'am patient enough to try building my own kernel.
stm999999999 said:
CIFSManager is only a manager, it needs cifs support in kernel.
But I will have a closer look at your kernel, at first sight it looks interesting.
Click to expand...
Click to collapse
mattes13 said:
Maybe I'am patient enough to try building my own kernel.
Click to expand...
Click to collapse
I did build the kernel with the applied patch, but it didn't solve the problem. I guess I have to do some more research within the kernel forums. So no cifs yet.
mattes13 said:
I'm am using an SXAS and I've been looking into this, tool.
After some trying with different kernel modules I downloaded the kernel sources from Sony's developer webpage. And then it became very clear:
Theoretically our 6.2.B.0.200 firmware's kernel has integrated cifs support. The kernel config says so.
So I connected with adb and tried to mount via command line and looked at dmesg. It says: "CIFS VFS: Connecting to DFS root not implemented yet". This means: The kernel should be able to handle cifs, but there is a bug. Either it is the mount utility from the busybox I've installed or it is a bug in the kernel. Since our firmware uses a 3.4.0 Linux kernel and due to some googleing, I assume this to be a kernel bug.
Click to expand...
Click to collapse
Okay, for anybody, who is interested: I have not tried the following using the stock kernel of .200 or .211 since I'm on Forzaferrarileo's JB kernel at the moment. However, after a lot of internet research I found out how to configure the cifs manager app to mount Samba shares again.
Share Path: //<ip>/<share>
Mount Point as you like it
Username as needed
Password as needed
Options: sec=ntlm,iocharset=utf8,unc=\\\\<ip>\\<share>
It appears that the Samba developers changed their mounting syntax. Although the app states to start the share path with the ip, you need the double slash. And although the share path is already defined, they want it again in the options with the unc option. There you need to double all backslashes. If you have spaces in the unc path, use double quotation marks around your path.
Additional info: currently, I'm using busybox version 1.20.2.
Cifs is enabled and the module is built in kernel . Need only right use of cifs manager
Sent from my LT26i using xda app-developers app
Forzaferrarileo said:
Cifs is enabled and the module is built in kernel . Need only right use of cifs manager
Click to expand...
Click to collapse
Forgot to mention that explicitly, thx.
Dumb question maybe, but does the Samsung stock kernel support Cifs? Is there any kernels out there that will? I really would like to mount my linux server.
Just use an APP??
https://play.google.com/store/search?q=CIFS&c=apps
dipole said:
Dumb question maybe, but does the Samsung stock kernel support Cifs? Is there any kernels out there that will? I really would like to mount my linux server.
Click to expand...
Click to collapse
ES File Explorer (among others) supports samba shares (public and user/pass); it's all I use anymore for moving files between phone & NAS, as well as for streaming video directly (when my PLEX machine is down). Haven't bothered with system-level CIFS mounts in quite a while.
Compulsion Kernel v14 does. Also, I think Civz kernel also has it.
Haven't gotten it to work yet, though.
Update:
Got it to work within the CifsManager app by following These steps.
Unfortunately, other apps can't access the files and show the mount points as empty folders.
However, there's a solution I will try to see if it fixes it.
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- GPS; - need a device owner to configure!
- Camera (both);
- Dock special keys (top row);
- Modem on TG and TL;
- GUI crashes; - occure less often
Currently, no one from Unlegacy Team, has TF300T/TG/TL device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Transformer TF300T
Contributors
Clamor, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
I worked on this for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY! TF300TG/TL users shouldn't use this as it can harm your tablet.
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash Stock or Bootloader 4.2 attached in Downloads section.
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
androidjel said:
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
Click to expand...
Click to collapse
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
androidjel said:
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
Click to expand...
Click to collapse
All needed files you can find in Downloads tab on top of this thread
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Clamor said:
All needed files you can find in Downloads tab on top of this thread
Click to expand...
Click to collapse
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
androidjel said:
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
Click to expand...
Click to collapse
Nothing, you may install Rom to see current project progress (If you have TF300T there will be no sound). For further developement test device is needed, or a developer with TF300T(better solution). Mostly all major functions are fixed, see buglist, and 3.4 works on all transformers on Tegra 3.
That is KANG TWRP with support of updated F2FS
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Clamor said:
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Click to expand...
Click to collapse
I am more than willing to be a tester if you want. Heck, I will even find a cheap TF300T to load only this on. My mornings are relatively free as my business doesn't pick up till noon or so. Just PM me specifics of what you need. Any more development for our tablets is a blessing as far as I am concerned
I would love to help debugging, testing and developing. I'm currently in possession of a tf300t with dock and an me301t. Do you think it will be possible to port this to the ME301t?
@gs-crash-24-7 please write me in PM. Actually ME301t was supported at early stages of 3.4 bringup. I fully excluded it from board since I couldn't test it and Memopad parts made transformers board really messy. I had enough problems with TF stuff at that moment.
3.4 kernel porting and repartitioning before were just a dream, but now they are real. Memopad bringup depends only on your interest in it.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs here from O for now. I know already about all major issues.
I have some good news. Here is mostly working Oreo build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Any possibility of sharing the 3.4 kernel supporting the ME301t...I have that little bugger and the latest software updates from my TV provider and Netflis like programs are all KK dead for the most part. Having unlegacy on the Me301t would be a dream come true and would avoid trashing this one and getting a new one just because I want to see some shows or TV. Thank you for your work. I will assist to the best of my knowledge.
@AlphaDivxMovies nothing impossible, but first of all, I have no MemoPad and it's hardware isn't that close as my Prime is with TF300T. Second is that I put huge amount of my time and afforts in porting transformer board so I have no desire at all to do this once more time, I can help with suggestions but actual development will lie on your shoulders.
P.S. To just boot rom atm you would need only a kernel port, ROM is mostly compatible. Almost all drivers memopad uses are already included. You may contact @gs-crash-24-7 as well, he has memopad and if he agrees, than work in pair is much more simple.
@Clamor , Where is the oreo version? https://builds.unlegacy-android.org/ here i could only find the 7.1.2 version.
The other downloads in this post dont work anymore (oreo).
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Clamor said:
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Click to expand...
Click to collapse
@Clamor But could you launch a O build again? maybe i could try to help, I have some time to do that at the moment.
HI all,
I am looking for kernel or drivers or console script(execute from Tasker) that allows me to achieve HOT SWAP support.
Is it possible to enable "hot swap" with OTG+Charge? Something like timur's host driver. Now to enable OTG+Charge I use ElementalX but "hot swap" isn't work.
7.1.2 has dedicated Glitch kernel for fixed installations in car. 6.x.x has Timur's rom. Is there option for Oreo to achieve OTG+charge(work with ElementalX) and Hot swap?
I have installed this amazing rom, really it works great:
[ROM] [8.1] [UNOFFICIAL] LineageOS 15.1 for Nexus 7 2013
I know my English is funny, but I do my best