Related
Have compiled cifs.ko and slow-work.ko for Infused 2.0.0.
Thanks to gtg465x for kernel sources on GitHub, Entropy512 for initial help and http://forum.xda-developers.com/showthread.php?t=837170&page=6 for help on slow-work.ko
[email protected] said:
Have compiled cifs.ko and slow-work.ko for Infused 2.0.0.
Thanks to gtg465x for kernel sources on GitHub, Entropy512 for initial help and http://forum.xda-developers.com/showthread.php?t=837170&page=6 for help on slow-work.ko
Click to expand...
Click to collapse
Thanks for posting!
I will be posting a Daily Driver kernel update that includes these when I get around to it. It'll probably be my last DD targeting Rogers firmware for a while as I'm running CM7 now.
[email protected] said:
Have compiled cifs.ko and slow-work.ko for Infused 2.0.0.
Thanks to gtg465x for kernel sources on GitHub, Entropy512 for initial help and http://forum.xda-developers.com/showthread.php?t=837170&page=6 for help on slow-work.ko
Click to expand...
Click to collapse
What do these do?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Looks like it lets you access samba shares. Not 100% on that however.
Yup. Lets you use the CifsManager app to access Samba shares
Entropy512 said:
Yup. Lets you use the CifsManager app to access Samba shares
Click to expand...
Click to collapse
Wat is samba shares?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
WeezyFBaby17 said:
Wat is samba shares?
Click to expand...
Click to collapse
SMB protocol, which is what Windows uses to share folders.
LinuxBozo said:
SMB protocol, which is what Windows uses to share folders.
Click to expand...
Click to collapse
Sweet
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Is this GB only or will it work on 1.5.3 as well? If so is it an install zip from CWM procedure to install?
Blackberrynomore said:
Is this GB only or will it work on 1.5.3 as well? If so is it an install zip from CWM procedure to install?
Click to expand...
Click to collapse
I've compiled it using Infused 2.0.0 kernel and it is Gingerbread. So it might not work with other ROMs.
Generally you do not need to install the modules. Just place them anywhere on sdcard and load them via insmod (root required). Please see CifsManager application description for more details.
How to install?
So, with this CIFS support, I can play my video files (AVI/DivX/RMVB...)
on local NAS via Wifi? (Just like use BuzzPlayer in iPhone)
Great!
The question is... how to install it? any document about install?
leedashone said:
So, with this CIFS support, I can play my video files (AVI/DivX/RMVB...)
on local NAS via Wifi? (Just like use BuzzPlayer in iPhone)
Great!
The question is... how to install it? any document about install?
Click to expand...
Click to collapse
Read [email protected]'s instructions, or use SGS Kernel Flasher to flash my 8-13 Daily Driver kernel (Note: For instructions on THAT, read the SGS Kernel Flasher docs. CWM can flash the zip too.)
modprobe the cifs module (Module autoloading MIGHT work in the daily driver kernel so this might not be needed, I haven't tested this much)
Install the CifsManager app from the market.
I attempted to install this via CWM and it installed so fast I wasn't sure if it worked or not. So I rebooted and installed CIFS Manager and ran it. I setup a test share on my laptop on the same network subnet and shared it out to everyone. I created a new share in CIFS Manager and then attempted to browse to the share and I get an error.
Share: 192.168.3.202/download
Mount Point: /mnt/cifs/download
Username: my username
Password: my password
Options: blank
I get an error stating:
Mounting the share has failed with an error.
{mount: No such device or address}
{mount: mounting the share failed the host is down}
Any help would be greatly appreciated.
I copied the cifs.ko and slow-work.ko to /system/modules and changed the mod path in CIFS manager. I also checked/changed permissions on those two files as well. Am I missing something???
NooB apologies extended to OP.
Since they're small files, it would flash fast.
Using ADB or Android Terminal Emulator, run lsmod - do you see cifs.ko in the list?
Entropy512 said:
Since they're small files, it would flash fast.
Using ADB or Android Terminal Emulator, run lsmod - do you see cifs.ko in the list?
Click to expand...
Click to collapse
I am not very familiar with Android terminal mode or commands but I did install terminal emulator from the market and typed: lsmod at the prompt. I did not see Cifs.ko in the output?
Blackberrynomore said:
I am not very familiar with Android terminal mode or commands but I did install terminal emulator from the market and typed: lsmod at the prompt. I did not see Cifs.ko in the output?
Click to expand...
Click to collapse
Hmm, it probably isn't loaded then. So you may need to run the following in a terminal:
Code:
insmod /wherever/you/put/cifs.ko
Hello,
This is a new root method.
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
[COLOR="Red"]Mod Edit: removed link[/COLOR]
EDIT: This has been confirmed working on the TF201 and TF101 so its a Universal root for all transformers
EDIT: Adding a step by step guide here.
A) Install an app from market any app. (I choose rootchecker)
B) Open the app-draw and select the asus backup utility and backup rootchecker
C) follow the scripts instructions
D) When it asks you to do another backup. Go into the backup utility from the TF101/TF201 (from the app-draw) go to back and RE-BACKUP the SAME app (Rootchecker in my case)
E) The system will reboot and you will have root. Do this all while the script is running. It will pause and ask you do the above items.
Thanks!
Reserved for later
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
chan32167 said:
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
Click to expand...
Click to collapse
Both you and the OP are legends. worked like a charm.
THANK YOU
bungknees said:
Both you and the OP are legends. worked like a charm.
THANK YOU
Click to expand...
Click to collapse
Thanks............
I'm already rooted, but I like the technique- it's quite clever and a wonderful hack.
I don't recall there ever being so many root exploits for a single device. It's like a tablet with a free puzzle that keeps giving. People are going to start buying the TF just to root it.
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
frankwhite8536 said:
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
Click to expand...
Click to collapse
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
sarreq said:
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
Click to expand...
Click to collapse
Yes, This roots the current OTA as stated in the OP / Thread Topic
but what kernel version is in the FOTA?
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
2.6.39.4-00002
Neptune #1
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
Kernel is 2.6.39
rhcp0112345 said:
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
Click to expand...
Click to collapse
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
frankwhite8536 said:
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
Click to expand...
Click to collapse
Nice, Good
frankwhite8536 said:
2.6.39.4-00002
Neptune #1
Click to expand...
Click to collapse
rhcp0112345 said:
Kernel is 2.6.39
Click to expand...
Click to collapse
thank you both.
you'd think they would've updated that, since ICS proper is supposed to run on a 3.x kernel.
so, will a honeycomb CIFS.KO work with the FOTA? or is there an ICS specific CIFS module somewhere out there? / nevermind, found it here nope, wrong again, that's for the tfprime, and causes a bootloop when it loads. i guess we have to wait for one to be ported, then?
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
rhcp0112345 said:
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
http://www.mrcellphoneunlocker.com/V2/tf101_ics_root.tar.gz
Click to expand...
Click to collapse
Great job! thanks
tomdot said:
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
Click to expand...
Click to collapse
what's this utility? never seen it before
WOrks!
Working Perfectly.
hi,
how can get or compiled cifs.ko and md4.ko modules for 10.4.4.16 JB ?
ali.jabbar said:
hi,
how can get or compiled cifs.ko and md4.ko modules for 10.4.4.16 JB ?
Click to expand...
Click to collapse
I'm interested in this as well.
+1
Sent from my Asus Eee Pad Transformer Infinity TF700T
ali.jabbar said:
hi,
how can get or compiled cifs.ko and md4.ko modules for 10.4.4.16 JB ?
Click to expand...
Click to collapse
You can use the attached modules. I tested them with CifsManager on 10.4.4.16 JB and they worked for me...
MarioGirotti said:
You can use the attached modules. I tested them with CifsManager on 10.4.4.16 JB and the worked for me...
Click to expand...
Click to collapse
thank you .
MarioGirotti said:
You can use the attached modules. I tested them with CifsManager on 10.4.4.16 JB and the worked for me...
Click to expand...
Click to collapse
They work fine here, too. But it took a while to figure out how to enable it.
For other people, the steps I took was as follows (all quotes are for clarification purposes only and should not be entered in settings):
1) Download the files above.
2) Unpack them to your internal SD card
3) Use a root file explorer to copy both the extracted files to "/system/lib/modules" (remember to enable R/W access to system partition and to disable it afterwards)
4) Download and install CIFS Manager.
5) Run it and allow it to gain root access
6) Go to CIFS Manager's settings and enable the following options:
7) Enable "Load cifs module"
8) Enable "Load via insmod"
9) Edit the option "Path to cifs.ko[:<modpath>]" to say "/system/lib/modules/cifs.ko:/system/lib/modules/md4.ko"
10) Disable "Load cifs module"
11) Enable "Load cifs module"
12) Go back to main screen of CIFS Manager
13) Pull up the menu and select "About..."
14) Click on "Modules..." and verify that both cifs and md4 are listed as "Live".
You might be able to use another directory to load the modules from - that, I haven't tried.
When you need to create a new link:
1) Run your root file explorer and create the link directory in /mnt/cifs/<MountName>
2) Then run CIFS Manager, pop up its menu and "Add new share"
3) Enter the value "<ServerIP>/<ShareName>" in option "Share path"
4) Enter the directory you created in step 1 above
5) Enter your user credentials in the "Username" and "Password" fields
6) Press "Save Share"
The share should now be listed in your list of shares. Click on the share you want to mount and it should be mounted at the specified mount point.
Thanks
MarioGirotti said:
You can use the attached modules. I tested them with CifsManager on 10.4.4.16 JB and they worked for me...
Click to expand...
Click to collapse
Thank you, works great.
You are now my hero of the week.
---------- Post added at 07:44 PM ---------- Previous post was at 07:38 PM ----------
ali.jabbar said:
thank you .
Click to expand...
Click to collapse
Say thank you AND give him a "Thanks" please. (by pressing the Thanks button)
mp1405 said:
Thank you, works great.
You are now my hero of the week.
---------- Post added at 07:44 PM ---------- Previous post was at 07:38 PM ----------
Say thank you AND give him a "Thanks" please. (by pressing the Thanks button)
Click to expand...
Click to collapse
Or dont say thanks just hit the button. The reason there is a thank you button is because threads get too full of thank you posts, people couldnt see useful content because of the spam.
Leaving all that behind, someone mind explaining what all this is about? What are CIFS modules?
pileot said:
Or dont say thanks just hit the button. The reason there is a thank you button is because threads get too full of thank you posts, people couldnt see useful content because of the spam.
Leaving all that behind, someone mind explaining what all this is about? What are CIFS modules?
Click to expand...
Click to collapse
Cifs (Common Internet File System) support is needed to mount Windows or Samba shares under Android.
If Cifs support is not compiled as feature into your the kernel you can load Cifs support later at any time if you have a kernel module available for cifs support. Since Asus did not delivere Cifs support with their kernel we have compiled the corresponding kernel module from the original kernel sources
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
HeartWare42 said:
9) Edit the option "Path to cifs.ko[:<modpath>]" to say "/system/lib/modules/cifs.ko:/system/lib/modules/md4.mo"
Click to expand...
Click to collapse
Might want to edit that last to .ko not .mo
Still thanks a ton. This issue was buggin the hell out of me.
It would be great if somebody could post a compiled nls_utf8.ko
Thanks'
Jack Daniel's said:
It would be great if somebody could post a compiled nls_utf8.ko
Thanks'
Click to expand...
Click to collapse
nls_utf8 support is included already in the kernel:
CONFIG_NLS_UTF8=y
Anyhow I compiled it again as module (see attachment). At least the module was loadable on my side
It's working yay.
But horribly slow
On par with Es explorer. Unusable for watching videos.
1.5-3 Mbit,a few peaks at 5Mbit.
Using the same router for downloads from the net, gives me sustained 10Mbit (my net
connection speed).
Could you recommend another way to access my shares?
kosmarnik said:
It's working yay.
But horribly slow
On par with Es explorer. Unusable for watching videos.
1.5-3 Mbit,a few peaks at 5Mbit.
Using the same router for downloads from the net, gives me sustained 10Mbit (my net
connection speed).
Could you recommend another way to access my shares?
Click to expand...
Click to collapse
Mount the volume with the options 'noatime,nodiratime' That may help. It did for me for at least browsing my volumes (expected) but not sure if it will help for streaming. Anyway, give it a go. If your using cifs manager there is a options box to enter them in. or you can make it part of hte mount command if your doing it that way manually.
calisro said:
Mount the volume with the options 'noatime,nodiratime'
Click to expand...
Click to collapse
Or just noatime, since nodiratime is implicit.
briankb said:
Or just noatime, since nodiratime is implicit.
Click to expand...
Click to collapse
on normal linux yes... on busybox I'm not sure so I add both. can't hurt but your probably right.
Works also for Clean Rom
It might be obvious for the experts, but in case that other noobs like me are reading here and are afraid to ask : the cifs module works also perfectly with Clean ROM 2.5.5.
HeartWare42 said:
They work fine here, too. But it took a while to figure out how to enable it.
For other people, the steps I took was as follows (all quotes are for clarification purposes only and should not be entered in settings):
1) Download the files above
2) Unpack them to your internal SD card
3) Use a root file explorer to copy both the extracted files to "/system/lib/modules" (remember to enable R/W access to system partition and to disable it afterwards)
4) Download and install (removed)
5) Run it and allow it to gain root access
6) Go to CIFS Manager's settings and enable the following options:
7) Enable "Load cifs module"
8) Enable "Load via insmod"
9) Edit the option "Path to cifs.ko[:<modpath>]" to say "/system/lib/modules/cifs.ko:/system/lib/modules/md4.ko"
10) Disable "Load cifs module"
11) Enable "Load cifs module"
12) Go back to main screen of CIFS Manager
13) Pull up the menu and select "About..."
14) Click on "Modules..." and verify that both cifs and md4 are listed as "Live".
You might be able to use another directory to load the modules from - that, I haven't tried.
When you need to create a new link:
1) Run your root file explorer and create the link directory in /mnt/cifs/<MountName>
2) Then run CIFS Manager, pop up its menu and "Add new share"
3) Enter the value "<ServerIP>/<ShareName>" in option "Share path"
4) Enter the directory you created in step 1 above
5) Enter your user credentials in the "Username" and "Password" fields
6) Press "Save Share"
The share should now be listed in your list of shares. Click on the share you want to mount and it should be mounted at the specified mount point.
Click to expand...
Click to collapse
Brilliant. Working on a stock 4.1.1. And I went through hell to get there, rooted, unlocked, bricked by using the wrong cifs (put me into a reboot loop I couldn't escape from), debricked, gave up for a week, started looking again today and was trying to figure out if I needed a tweaked ROM, kernel, or both - then I found your post and it turns out I had covered everything I needed to, I just didn't have some of the details right.
I don't really have a use for this but knowing it could work and that the only constraint to such cool technology was my lack of understanding, was not an acceptable situation. In other words thanks for resolving my latest OCD obsession
Many roms and kernels have cifs built in now I know I used this excellent guide to build it into cleanrom inheritance.
Hello, is there please somebody, who succesfully compiled CIFS and MD4 modules for JB 4.2.1?
I've tried, but all I was able to produce using different toolchain versions was either "uncompatible exec format" message, or instant reboot.
Which toolchain version should I use for compiling for JB4.2.1?
Thanks
Sent from my Asus TF700 using TapatalkHD
is it possible to run any linux images in kitkat or say particularly in our tab?
ive tried everything from easy setup using linux installer but it wont mount
i tried to use packaged images with scripts it mounts in terminal but got a grey screen only in vnc
but everything works in my other device running jellybean....ubuntu and backtrack5
rap0307 said:
is it possible to run any linux images in kitkat or say particularly in our tab?
ive tried everything from easy setup using linux installer but it wont mount
i tried to use packaged images with scripts it mounts in terminal but got a grey screen only in vnc
but everything works in my other device running jellybean....ubuntu and backtrack5
Click to expand...
Click to collapse
may be its fault of rom
sharingan said:
may be its fault of rom
Click to expand...
Click to collapse
ok well i will try asking in the rom thread if they had something to say about this
rap0307 said:
ok well i will try asking in the rom thread if they had something to say about this
Click to expand...
Click to collapse
yeah you can try that
This should probably go in some general Q&A forum, but this is by far the most helpful community I've come across so I wanted to try here first. I've finally got my Ubuntu box up and running again (upgrading to 14.04 wasn't pretty) and was able to build for both my 700t and my n5 without error, but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen? I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible. Any insight you may have would be most appreciated.
Thanks in advance!
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen?
Click to expand...
Click to collapse
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
psudeke said:
I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible.
Click to expand...
Click to collapse
That's normal - ARM devices are just too different, and the emulator is just another different device.
psudeke said:
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Click to expand...
Click to collapse
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
_that said:
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
That's normal - ARM devices are just too different, and the emulator is just another different device.
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
Click to expand...
Click to collapse
Thanks _That, I appreciate your help! After reading your post and the f2fs post, i thought i was in the clear, but i still managed to screw something up. i'm unable to get the tablet to boot off of external, regardless of whether its my ROM or CROMBi. I see a "segmentation error" listed in the output from the the preinit, and then it always boots to internal. I thought maybe i got the mount points reversed in recovered, so i reflashed recovery, but no luck. i also tried deleting the preinit script and then reinstalling CROMBi, but i still get the same error. any thoughts?
psudeke said:
I see a "segmentation error" listed in the output from the the preinit
Click to expand...
Click to collapse
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
You still get that fault with a static busybox but it seems to copy files fine.
@psudeke you can compile the static busybox yourself simply with make static-busybox in your build folder - or just steal mine from /system/boot
sbdags said:
You still get that fault with a static busybox but it seems to copy files fine.
Click to expand...
Click to collapse
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
it comes from the ls -l /init* which indeed doesn't have the busybox prefix but if I do it gives some other error I forget now
Anyway it doesn't harm the boot process - just an error message
_that said:
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
Click to expand...
Click to collapse
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
psudeke said:
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
Click to expand...
Click to collapse
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
sbdags said:
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
Click to expand...
Click to collapse
Ahh, thanks sbdags! that fixed the issue with ROM2SD. i got that impression when i pulled the preinit and saw it only had an entry for internal. but, i'm still very much in a learning phase so i didn't want to jump to a conclusion.
and after getting crombi to boot on external, i swapped sd cards and my build of CM11 actually booted! now the real learning process begins as i figure out how to customize it.
Thanks again to both you and @_that, you guys are the best:good:
@sbdags and @_that
Just wanted to thank you both again for your help. After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
https://www.dropbox.com/s/khq17h04b715eyd/C11%20Benchmark%20ART.png
Hats off to both of you! :good:
--- Guess I can't insert an image directly from my DropBox, link is to a screenshot of my score ---
psudeke said:
After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
Click to expand...
Click to collapse
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
_that said:
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
Click to expand...
Click to collapse
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
psudeke said:
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
Click to expand...
Click to collapse
Just ask away and congrats! :good:
sbdags said:
Just ask away and congrats! :good:
Click to expand...
Click to collapse
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes your unwanted apps
note apps can be installed into 2 folders /system/app or /system/priv-app
similarly you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
sbdags said:
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes you unwanted apps
note apps can be installed into 2 folders /system/app or /systempriv-app
similar you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
Click to expand...
Click to collapse
Thanks again! i can see how this becomes addicting fast :fingers-crossed:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
psudeke said:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
Click to expand...
Click to collapse
just zip the /meta-inf folder, and flash that to test. obviously comment out any format commands as they will fail. That is what I do.
Hey @psudeke you ever need any help with anything to do with source or git let me know
I am also willing to help out
and just a FYI be careful of @sbdags :cyclops: LOL
Just kidding....
Let me know thx Josh