I'm really looking for an app that I can use to SSHFS essentially, so that I can sorta' use a mounted remote dir as an extension of my phones storage, much like you would do in normal, every-day linux.
Is there such a thing? To date, I have not been able to find anything...
You would first need to get Fuse working with the kernel. If/once we can boot custom kernels, it's possible one might ship with Fuse enabled but according to
http://groups.google.com/group/android-kernel/browse_thread/thread/096dda136ce772cb
stock does not have Fuse. Stock does support modules though and I'm fairly sure you can compile Fuse as a module. You'd need to get ahold of the Droid 3 stock kernel source, cross compile a module for Arm and try and get it to not kernel panic the phone. Once you have Fuse in there, it shouldn't be too bad to build a copy of sshfs.
In the mean time, I have found https://market.android.com/details?id=nextapp.fx to be an incredible file manager that support SSH, SMB, and FTP. The only thing missing would be root.
Anyway, I think Fuse support would be awesome but don't have time to work on it at the moment. Do we have the D3 kernel source somewhere?
Naex said:
You would first need to get Fuse working with the kernel. If/once we can boot custom kernels, it's possible one might ship with Fuse enabled but according to
http://groups.google.com/group/android-kernel/browse_thread/thread/096dda136ce772cb
stock does not have Fuse. Stock does support modules though and I'm fairly sure you can compile Fuse as a module. You'd need to get ahold of the Droid 3 stock kernel source, cross compile a module for Arm and try and get it to not kernel panic the phone. Once you have Fuse in there, it shouldn't be too bad to build a copy of sshfs.
In the mean time, I have found https://market.android.com/details?id=nextapp.fx to be an incredible file manager that support SSH, SMB, and FTP. The only thing missing would be root.
Anyway, I think Fuse support would be awesome but don't have time to work on it at the moment. Do we have the D3 kernel source somewhere?
Click to expand...
Click to collapse
Yes, D3 source has been released. There's a thread on it here on XDA in the dev section. Thank's for the info!
Related
Hello everyone,
I am trying to create a CWM flashable zip that will disable the charge led. My wife hates the led shinning all night long on the bedside table.
Consider this a 1.0 version that does not work.
Any help correcting the zips would be greatly appreciated!
http://dl.dropbox.com/u/56179974/Disable green charge LED.zip
http://dl.dropbox.com/u/56179974/Disable red charge LED.zip
http://dl.dropbox.com/u/56179974/Enable charge LEDs.zip
Thanks!
You shouldnt be modifying /sys files in that manner, you should be echoing values into them via a script.
Unfortunately there's no particularly reliable way of execing scripts on boot,
not all the kernels have the init script or install-recovery.sh
Depending on the kernel you could plug the entries into that and have them feed values into /sys
Edit: /sys is a virtual filesystem, it gets built on boot at every boot. You cant write to it during recovery as it disappears when you reboot.
What would be a good kernel to try?
From what I gather I could for instance use a terminal emulator to change the value or I could modify the init script to apply the value at boot?
It's not the kernel specifically, it's the ramdisk it includes.
Here's a quick rundown of how booting works:
Device is powered on -> bootloader starts loading kernel -> kernel loads ramdisk -> ramdisk scripts start loading android core -> boot time scripts and services are loaded
Dell devices have an init.device.post-boot.sh (or something along those lines), but a quick peek though the stock 5xx ramdisk shows that it's not enabled in it (I believe)
They also have flash-recovery.sh, but it might be missing in the HS kernels, so it's the same situtation.
I'd say the simplest way is to make them in scripts and just use a script pharser (like gscript) and load them that way.
Otherwise you would need ramdisk mods and reflash the kernel with the new ramdisk that lets you load more scripts at boot.
/data, /cache, and /system are mounted
/dev and /sys are spawned as they're virtual FS's containing telemetry from the kernel.
Thank you again for the useful information!
When you say "the stock 5xx ramdisk shows that it's not enabled in it (I believe)" does that mean that the init scripts are inaccessible after boot? I am working with the devs on getting Boot Manager working for the DS7 and we keep running into issues building the file system.
The ramdisk has a whitelist of scripts to exec:
The init.<device>.post-boot.sh script was added by dell in most kernels, they simply didnt add it into the stock 5xx ramdisks as they didnt have anything to put into them apparently.
If you check init.<device>.rc or init.rc on "/", look for these two entries:
Code:
service streak-post-boot /system/bin/sh /system/etc/init.streak.post_boot.sh
user root
disabled
oneshot
and
Code:
on property:init.svc.bootanim=stopped
start streak-post-boot
As it demonstrates, it feeds /system/etc/init.streak.post_boot.sh to sh when the boot animation has completed.
But they removed those entries from the stock 5xx ramdisk, they're simply not there anymore.
It still loads /system/etc/install-recovery.sh, you could use that as it does get loaded by the stock kernel.
At least on my rom the file doesnt exist at all, so you could simply replace it.
But if you were to do that the right thing to do is simply have the user modify it themselves, if they already have one with things they added. (this isnt that likely though)
Thanks again TheManii!
I would be working on this but unfortunately my DS7 bent a pin so as of now it is out of commission
I have new connectors on order (10 pack was the minimum) so I am hoping to have it going again soon
why not just implement duct-tape over the light? low-tech solution to your high-tech approach
Because that wouldn't involve me learning to code, etc
Too bad it isn't a problem now anyway considering my DS7 is a goner....
Wetzel402 said:
Because that wouldn't involve me learning to code, etc
Too bad it isn't a problem now anyway considering my DS7 is a goner....
Click to expand...
Click to collapse
check batterystats.bin, it might be related, didnt get a good look at it with my battery dying on the train home
I would but as I stated my DS7 took a dive. The charging port bent a pin and is now shot. A parts tablet on ebay maybe....
Wetzel402 said:
I would but as I stated my DS7 took a dive. The charging port bent a pin and is now shot. A parts tablet on ebay maybe....
Click to expand...
Click to collapse
How much would you want for parts?
PM sent
suggest removing block "# Eric Liu+" -> "# Eric Liu-" in init.rc might help those who are still using their S7.. the nexus7 probably stole the interest though
Anything proceeded with a "#" is a comment and doesnt do anything
Hi,
does the HTC One has CIFS support?
So that the CifsManager can be used on a rooted device?
THX
Well the app is showing as compatible on the Play Store, so I'd presume so.
No it does not.
Just because cifs manager can be downloaded doesn't mean it has Cifs support.
You need a custom rom / Kernel for that.
There are two kernels out there claiming cifs support, however I cant get either one to work.
http://forum.xda-developers.com/showthread.php?t=2235085&highlight=cifs
and
http://forum.xda-developers.com/showthread.php?t=2233665&highlight=cifs
Let me know if you get one working.
Update: there is a 3rd Kernel claiming Cifs support.
http://forum.xda-developers.com/showthread.php?t=2229300&highlight=cifs
I will try it our soon.
Any updates on this? Would love to have CIFS support and TAP network driver support. I'm thinking about trying to compile my own kernel modules but I have almost zero experience with doing this...
cifs.ko loads, but no success
jaybombz said:
Any updates on this? Would love to have CIFS support and TAP network driver support. I'm thinking about trying to compile my own kernel modules but I have almost zero experience with doing this...
Click to expand...
Click to collapse
I've gotten a cifs module to load on 3.4.10 after modifying the module final version string to reflect my specific kernel (3.4.10-geb45596) but still no success. I had success doing the exact same thing on my old EVO, but CifsManager on the HTC One throws "invalid argument", and the mount command (via terminal) says "no device", although lsmod confirms that cifs is loaded.
Any advice is welcome.
I'm also stuck trying to get CIFS.
Can you flash any kernel, regardless of ROM, or does it have to match? I'm using an Android Revolution HD GPE ROM, which doesn't appear to have CIFS support ("invalid argument", cifs.ko nowhere to be found in the filesystem according to ES File Explorer, /proc/filesystems/cifs (or something like that) does not exist, etc).
Maybe I could just flash one of the above kernels and see if it works, or does it not work like that, i.e. it has to be integrated with the ROM?
Hello XDA,
Im back again with another personal project I'm having some issues with. First, a bit of explanation as to why I've chosen to attempt this.
I was running a heavily modified stock rom with nethunter 5.1.0 that was incredibly unstable, and eventually crashed right out on me (modified using root based apps so the crash was my fault) .
So I grabbed the CM13 snapshot for hammerhead, and layered on nethunter 3.0 (big fan since BT3), only to find out my wifi card isn't supported. On 5.1.0 I also had this issue
(see here http://forum.xda-developers.com)/showpost.php?p=64400679
which I managed to fix with a simple source build with a few extra options checked in menuconfig.
Sadly it doesn't seem to be quite that easy with CM13 and marshmellow.
I'm using the DWA160-b2 wifi adapter, which from my research, uses the rt2800usb chipset, which supposedly points to the rt5572 driver. So, I enabled the corresponding options in menuconfig , although I cant remember the exact wording at this moment (using winblows to write this, and not my linux) and I still have no life in my wifi card.
So, after even more research, I found out I should be able to cross-compile the required drivers using the arm-eabi tools. However, after trying I've come to the conclusion that there is no arm based config for this driver. So then I tried backports, and recieved an error about incomplete linux headers (I assume because of the chroot, because my headers are all installed).
Now finally my question:
How do I go about compiling this driver for arm? Or is there a know working arm driver for this particular card? As I have not come across one in my searching. Also please dont say get a new wifi card lol I have a few different usb wifi cards, all with the same issue (albeit different chipsets).
Are u trying to port kali kexec to cm13 kernel?
Sent from my fx-82MS with CM-CAF
I am wondering about a KRACK Fix for the R1 HD. I'd like a way that we can replace the KRACK affected version of wpa_supplicant, but. keep whatever Rom we were running, LineageOS 13.1 in my case. I there a way we can make a replacement wpa_supplicant that is not vulnerable to KRACK and flash that as an independent zip?
not sure if that is enough. Most, if not all of the fixes I have found for other devices also include an updated kernel as well.
but, If the only thing needed is an updated "/system/bin/wpa_supplicant" then you could find a similar device(same soc chipset) with available updated rom , and copy its "/system/bin/wpa_supplicant" file to your device either with a twrp script or with root explorer.
Dont have any proof this will work or not. You will need to try for yourself.
Also if wi-fi works after the swap, you will need some way of testing if krack is actually patched.
mrmazak said:
not sure if that is enough. Most, if not all of the fixes I have found for other devices also include an updated kernel as well.
but, If the only thing needed is an updated "/system/bin/wpa_supplicant" then you could find a similar device(same soc chipset) with available updated rom , and copy its "/system/bin/wpa_supplicant" file to your device either with a twrp script or with root explorer.
Dont have any proof this will work or not. You will need to try for yourself.
Also if wi-fi works after the swap, you will need some way of testing if krack is actually patched.
Click to expand...
Click to collapse
This is BS. That's opensource software. They should be releasing the source code. Where is the src for that version?
So I'm running the latest version of Evervolv Android Pie and I'm trying to hide root for apps that can detect it. At first I looked into Magisk as that has it built in, but upon reading, as well as trying it myself, it doesn't want to install. Is there a way to install it that I'm not aware of or is it just not possible? I've also looked into suhide, however I cannot get that to work either. Any info and help would be greatly appreciated, and I can provide any info that's needed. Thanks
Magisk does not work on the Hp Touchpad, it needs to modified the RAMDISK to have access to the Kernel and patch it.
This could be better, I do not know if it could be merge into the current Kernel.
https://www.xda-developers.com/kernel-assisted-superuser-kernelsu/
https://forum.xda-developers.com/android/software/root-backdoor-android-kernel-development-t3870559
Thanks for the reply, and appreciate the help. How would I go about merging it with the kernel? I know you said you didn't know if it could, but I'd want to try to see? Also, is there anyway of installing SuperSU in systemless mode so su-hide would work?
Camry2731 said:
Thanks for the reply, and appreciate the help. How would I go about merging it with the kernel? I know you said you didn't know if it could, but I'd want to try to see? Also, is there anyway of installing SuperSU in systemless mode so su-hide would work?
Click to expand...
Click to collapse
You are welcome,
The developers will have to merge the kernel Assisted SuperUSer ( kernelSU ) into the kernel branch of the Android ROM. Then it will need to be recompile, I provided a guide on how to recompile the HP Touchpad kernel:
Click HERE for the Guide
About Systemless: The boot image ( Ramdisk and Kernel ) is read only and it gets loaded into memory each time. There is no program that will be able to modified the boot image for the HP Touchpad, but the RAMDISK can be modified manually, here is a guide on how to do it:
Click HERE for the Guide to unpack and repack the Ramdisk
The Ramdisk modification only allows /system to have read and write access for SuperSU to work, it does not modified the kernel.
To modified the Kernel for systemless this is what is required and then recompile the kernel.
Click HERE to compile the kernel with root permission.
I have not look into this on the HP touchpad Kernel and I know that all I have posted on here is a lot to do, but if you want, let me know the version of Android you want to have the kernel with root access and the CPU speed and I could try to compile that and then you test it.