Related
First of all, all credits for this tutorial go to wolfilein and batemann
wolfilein's original app2sd thread - http://forum.xda-developers.com/showthread.php?t=804574
Since the other "how to" thread is a bit cluttered, I decided to tell the community how I got app2sd running on my phone flawlessly, in details.
I'm assuming that you have already rooted your x10 mini/pro and you are familiar with partitioning your SDcard, running ADB tool and root explorer.
If not, then please refer to these threads
For rooting your phone -
http://forum.xda-developers.com/showthread.php?t=739874
How to use ADB -
http://forum.xda-developers.com/showthread.php?t=502010
So lets get going -
Step 1) Create 2 partitions on your SDcard, a) Fat32 b) ext2. I used Mini Tool Partition Wizard to create partitions. Remember if you are a windows user, you need to create first partition as Fat32 and second as ext2 other wise windows will not recognize your SD card when you will connect your phone/card reader.
A detailed tutorial on how to partition your card can be found here-
http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning
Step 2) Download attached rar file and extract them on your SDcard root (not inside any folder)
Step 3) Open ADB Shell and type - busybox. If you see the list of busybox commands you can move to Step 5. Otherwise refer to Step 4
Step 4) If you do not have busybox installed or recognized on your system, you need to install it. I found that best way to install busybox is the manual one, so even if you mess up with busybox installation, your phone is not bricked, yet.
So to install Busybox please enter the adb shell and type su, prompt should change to # sign, confirming that you have entered rootshell successfully.
Now type :
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
Code:
cat /sdcard/busybox > /system/xbin/busybox
Code:
chmod 755 /system/xbin/busybox
Code:
/system/xbin/busybox --install -s /system/xbin/
Once you finished the installation, typing busybox from rootshell should list busybox commands. If you can not get the list of busybox commands, or get message like permission denied, or busybox not found, please confirm that you can see busybox in /system/xbin/ and the permission is set to 755. you can use root explorer for this.
Step 5) Now its time to run App2sd.sh
So from rootshell, type:
Code:
sh /sdcard/app2sd.sh
and PRAY.. Its very important to pray, because anything goes wrong here, you will end up with a PROPER bricked phone. Nah, just kidding.
Your phone should reboot itself upon finishing. and when it comes back online, app2sd should be running on your phone..
good luck.
Disclaimer: I'm not responsible for anything that happens to your phone. You take the sole responsibility of your phone, if it gets bricked, vanished or turned into cheese in the proccess.
great .. and PRAY.. LOL
I tried this procedure last week. And it went wrong cause my transcend sdhc (class 2) was faulty OMG!!!
So I bricked my phone, repaired it, and now I'm waiting another 16Gb (class10) card ... so I can brick again my phone.. ROTFL.. no no.. I'm sure this procedure is going to be ok
Thanks to titanium backup I have not lost one bit
Mate seems like a great tut, I'm just flashing my phone to follow this properly =]
P.S. what is rootshell?
Manny- said:
Mate seems like a great tut, I'm just flashing my phone to follow this properly =]
P.S. what is rootshell?
Click to expand...
Click to collapse
You enter into rootshell When you type su on adb shell. the prompt in rootshell is #.
Thanks, I thought so just making sure so anyways I'm about to try this way now will report back soon
PS. lil mistake, should be 'sh /sdcard/app2sd.sh'
PS.2 check your inbox please
IF rooted using universal androot app
1. Does this work if phone is rooted with universal and root??
2. I don't have a card reader to format the sdcard.
I formatted using the Phone itself (through usb cable), but the card didn't mount, and prompting to format it
sridharrn said:
1. Does this work if phone is rooted with universal and root??
2. I don't have a card reader to format the sdcard.
I formatted using the Phone itself (through usb cable), but the card didn't mount, and prompting to format it
Click to expand...
Click to collapse
1. Yes it will work regardless of the rooting method.
2 .Make sure that first partition of your SD card is fat32.
Thanks for a great guide!
Finally got it working on my mini pro.
Don´t know if it´s your script or my phone but it didn´t want to run for me.
When I hit "sh /sdcard/app2sd.sh" the command-window just turns to # again without doing anything.
So I ended up running all commands manually instead and that worked nicely.
Same happened with me... how did you run the commands manually?
Manny- said:
Same happened with me... how did you run the commands manually?
Click to expand...
Click to collapse
Opened the app2sd.sh-file in an text-editor, then I can see all commands listed.
Then I just Copy-And-Paste the commands line by line (Not all at once) in the command-window.
@OP
please delte this
i and batman are already working on an picture howto
i've invested many time and this and now..... yes you scribe on you post that all credist go to us but why we must have 2 threads if you so interestet to help you easy can send me an pm or write an post
@other
I woukd making a howto on monday but batman has no time so i will do it whit him tommorow
and you script doen't work if you have an sdcard malfunction
yes you made a failsafebut you don't use it in ln.sh
if you run this script without an sdcard you will brick your phone !!
and by the way please ask before you edit/use my script
you coukld write a pm
wolfilein said:
@OP
please delte this
i and batman are already working on an picture howto
i've invested many time and this and now..... yes you scribe on you post that all credist go to us but why we must have 2 threads if you so interestet to help you easy can send me an pm or write an post
@other
I woukd making a howto on monday but batman has no time so i will do it whit him tommorow
and you script doen't work if you have an sdcard malfunction
yes you made a failsafebut you don't use it in ln.sh
if you run this script without an sdcard you will brick your phone !!
and by the way please ask before you edit/use my script
you coukld write a pm
Click to expand...
Click to collapse
Mate, I only made this thread to help the community. Since this is the method I used to get a2sd running on my phone. And I did not edit/changed your script, I wrote it down, which involved my own corrections and researchs (which I contributed to your thread as well). True that ln.sh was provided by batemann, that's why I gave you two full credit.
I can not delete the thread as there are posts there, however if you claim all the rights on the method, I'll pm the moderators and ask them to merge this thread with yours.
As for helping with picture how to, I would be more than happy to help the community.
Sent from my U20i using XDA App
Manny- said:
Thanks, I thought so just making sure so anyways I'm about to try this way now will report back soon
PS. lil mistake, should be 'sh /sdcard/app2sd.sh'
PS.2 check your inbox please
Click to expand...
Click to collapse
Replied to your pm. Manny, mate tell me do you have a mini or mini pro?
Sent from my U20i using XDA App
Ive got a Mini, btw I sent you some msgs on MSN but you went offline it should still be there, I wrote the output there too.
and wolfilein, I cant get it to work from looking at your thread this just makes things easier in my eyes, and hes right it is too cluttered that thread
@OP
i don't say don't do this i only ask why you hadn't write me an pn or some other info about this ?
and btw i and batman are aktually working on the picture howto please let us time
/system/bin/shcd: not found
Everything is OK, but when I run the script returns # so i run commands manually but first command returns "not found this command"
can somebody help me please ?
thanks
SOLVED, thanks anyway
Manny- said:
Ive got a Mini, btw I sent you some msgs on MSN but you went offline it should still be there, I wrote the output there too.
and wolfilein, I cant get it to work from looking at your thread this just makes things easier in my eyes, and hes right it is too cluttered that thread
Click to expand...
Click to collapse
Mate, I checked msn, but I did not get your msg there.. I'm online now, try sending it again..
Sent from my U20i using XDA App
so I've made a picture howto so now it's verry easy even with my howto
With app2sd, can i pick where i want to install an app?
on Main memory or SD?
and what would happen if i removed my SD card when its on?
or when i plug it in to the PC to add files?
thanks!
if you use this your phone won't not boot after reoving the sdcard
but if you use the orginal howto (my) my script makes a failsafe by installing app2sd and use that,
I've read through the threads in the dev section about running linux on our Atrix either off of the sd card or chroot but didn't get a clear picture of what is possible with this technique using our phones on the laptop dock.
I'm about to give this one a go where it walks you through installing Ubuntu on our phones.
how-to-install-ubuntu-on-android
Does it work well? Does the touchpad and keyboard work without issues? Do the usb ports function correctly? And finally, does it play nice with Webtop if you have Webtop installed and enabled?
Thanks in advance for any info.
Update: The install script for this method failed when ran. It appears it is looking for a specific kernel version. The error I received was "FATAL: Could not load /lib/modules/2.6.32.9/modules.dep: No such file or directory". When I looked in the /lib/modules directory on the phone I only found a 2.6.29-arm2 directory.
you can just use WebTopScripts and Webtop2SD.
You can see how it works on my video [Polish language on video only]
http://www.youtube.com/watch?v=MGfZe4jOdfo
ovitz said:
you can just use WebTopScripts and Webtop2SD.
You can see how it works on my video [Polish language on video only]
http://www.youtube.com/watch?v=MGfZe4jOdfo
Click to expand...
Click to collapse
I checked out your video and I wish I could understand Polish.
Anyway, I just installed webtop2sd and when I launch it I get a force close error popup saying...
"Sorry! The application webtop2sd (process net.toreishi.webtop2sd) has stopped unexpectedly. Please try again."
I'm running stock 4.5.141 build with root and unlocked bootloader. Any idea on why I'm getting this error?
I can translate this video if you want to
yes, you have to instal bussybox installer form Google Play Store, then you need to change permissions of busybox in/system/bin/
Open permissions and uncheck "Set GID" permission, save changes.
ovitz said:
I can translate this video if you want to
yes, you have to instal bussybox installer form Google Play Store, then you need to change permissions of busybox in/system/bin/
Open permissions and uncheck "Set GID" permission, save changes.
Click to expand...
Click to collapse
Thanks for reminding me about Busybox. I didn't bother to install it since when I updated my Superuser binary it said it was installing a custom Busybox so I thought that would be all I would need. I guess I was wrong and had to install Busybox anyway.
I'm running the WebTopScripts at the moment. It seems to be going well.
Thanks for your help.
help please
Ok first off let me say that I am very new to android so I am a noob. Lately I have received my Atrix 4G lapdock and I have been scouring over these forums attempting to install ubuntu or some other desktop linux distro on my device for the past week.
I have installed Webtop2sd 1.1.2 (I was getting force close with 2.0 version so I downgraded :/ ) I want to partition my sdcard but it is not being recognized by webtop2sd. I have changed permissions to uncheck set GID in busybox which is installed in systym\bin ...\xbin. Still no recognition.
I have attempted to ext3 partition my sdcard with Windows Mini Tool Partition Wizard but I get and error during processing and the partition cannot be created. Currently sdcard is fat32 format.
Can anyone please provide some assistance in this it would be most helpful!
Thank you!
Device stats:
unlocked BL, rooted, and ROM Nottachtrix 4G and faux 1.3 Ghz Kernal installed
Fixed!!!
For some reason the partition tool was acting up so I used another software which did the trick.
Information and Modules description
I was in the need to add some missing kernel modules to my Xperia Mini Pro sk17i with v4.0.2.A.0.58, but I could only find modules compiled form ICS sources, so I decided to build them myself.
All modules have been compiled from official sony Xperia v4.0.2.A.0.58 kernel sources, using Android NDK r5, and they should be fine with any GB based Xperia 2011 device (with that kernel version at least).
This is the list of modules, with some interesting programs using them:
fuse.ko: Cryptonite (used to create encrypted EncFS or Truecrypt volumes, adds support to mount drives so that are visibile to the whole Android system. Note: Cryptonite is not currently able to load the module automatically, you need to load it from Terminal Emulator..se more below)
usb-storage.ko, nls_utf8.ko, ntfs.ko (compiled with write support, currently untested): USB OTG Helper (used to mount external USB drives with USB On The Go cables).
cifs.ko, slow-work.ko, md4.ko: CifsManager (used to mount network shares)
ext4.ko, jbd2.ko: if you wish to use the EXT4 filesystem
tun.ko: needed by VPN clients, like OpenVPN or DroidVPN
Installation Instructions
Attached to this post you will find a ZIP that can be used along with CWM Recovery to install the modules in system.
Download the module, put it inside you SD card, reboot your phone in CWM (which you can install with the Xperia CWM Auto-Installer) and select install zip from sdcard, and browsed to the ZIP. Reboot your phone when install finishes.
Loading Modules
No module is automatically loaded at system startup: this saves your memory and battery (some of those modules are known to drain your battery if always loaded).
To manually load a module you have to open the Android Terminal Emulator and tap:
Code:
su
insmod /system/lib/modules/MODULENAME.ko
where MODULENAME is the name of the module you want to load.
Other useful commands:
Code:
lsmod
to see currently running commands
Code:
rmmod MODULENAME.ko
to unload a module.
If you wish to manually load a module at phone startup you should use init.rd or any other method (?) to run custom scripts at startup.
Load Order
Some modules need to be loaded in a specific order:
slow-work.ko must be loaded before cisf.ko
jbd2.ko must be loaded before ext4.ko
Other Firmware Versions
I've released the same package for other firmware versions, click on the firmware version to go to the specific thread:
ICS v4.1.B.0.587 Kernel Modules package by zxp
Changes
v2 - 2012.07.19
===========
- customized, built and added slow-work.ko, which is needed to load cifs.ko
- added jbd2.ko, which is needed to load ext4.ko
v1 - 2012.07.12
===========
- First release
Thanks for this..
Fuse, and the rest as required, are automatically loaded as required by USB OTG Helper if found in /system/lib/modules.
shardul_seth said:
Thanks for this..
Fuse, and the rest as required, are automatically loaded as required by USB OTG Helper if found in /system/lib/modules.
Click to expand...
Click to collapse
Yes, the same applies to CifsManager, even if it requires some fiddling in options, while your USB OTG Helper does it automagically...by the way, it would be really nice of you if you could add the same auto-load code to Cryptonite, which is open source somewhat related to your work! :good:
zxp said:
Yes, the same applies to CifsManager, even if it requires some fiddling in options, while your USB OTG Helper does it automagically...by the way, it would be really nice of you if you could add the same auto-load code to Cryptonite, which is open source somewhat related to your work! :good:
Click to expand...
Click to collapse
I have my own encryption script, and I am happy with it.. So no fiddling with cryptonite for me
Updated both install and uninstall packages to fix cifs.ko and ext4.ko that couldn't be loaded because of missing dependencies (slow-work.ko and jbd2.ko).
You can find the updated zips in the first post.
where i can find the ext4.ko module for Xperia 2011 ICS?, i can't find it nowhere, can you help me with it?
sorry for my bad english
lightdesiny said:
where i can find the ext4.ko module for Xperia 2011 ICS?, i can't find it nowhere, can you help me with it?
sorry for my bad english
Click to expand...
Click to collapse
I don't know where to find it, I don't have upgraded to ICS yet, sorry.
If you are sure that no one have released it I may build a package similar to this one once I upgrade to ICS, in the coming weeks. Keep an eye on this forum :cyclops:
hi when I type the cod say me that not found that I istall it with recovery please help me
my phone xperia ray
my rome is 2.3.4 - 4.0.2.A.0.58 GB
hadics1 said:
hi when I type the cod say me that not found that I istall it with recovery please help me
my phone xperia ray
my rome is 2.3.4 - 4.0.2.A.0.58 GB
Click to expand...
Click to collapse
Don't complain if none will answer you.
hadics1 said:
hi when I type the cod say me that not found that I istall it with recovery please help me
my phone xperia ray
my rome is 2.3.4 - 4.0.2.A.0.58 GB
Click to expand...
Click to collapse
Can you please explain your problem better?
I can't understand your post.
zxp said:
lightdesiny said:
where i can find the ext4.ko module for Xperia 2011 ICS?, i can't find it nowhere, can you help me with it?
sorry for my bad english
Click to expand...
Click to collapse
I don't know where to find it, I don't have upgraded to ICS yet, sorry.
If you are sure that no one have released it I may build a package similar to this one once I upgrade to ICS, in the coming weeks. Keep an eye on this forum :cyclops:
Click to expand...
Click to collapse
I've just released the same package as this for Xperia ICS v4.1.B.0.587, you can now use ext4 on the latest ICS firmware
This is great
Sent from my WT19i
mount nfs share works with busybox - but won't with cifsmanager
Hello folks,
as this is my first post here, i'd like to thank all of the contributors for the excellent Guides and Howtos on this platform. Based on the instructions in this forums i was able to root my Xperia Mini Pro sk17i and greatly expand my devices applicability. Thanks to all of you!
Sorry, that the post got that long - hope that someone is still so kind to read and answer to it. I just wanted to be as precise as possible in the desription of my problem.
And here it comes. As the title of my post already implies, my ultimate goal is to mount nfs shares of my NAS and Router in my private network as user-friendly and simple as possible.
So far, I tried the following to achieve this goal:
Install busybox to generally expand linux capabilities of the device
install the Android Terminal emulator also from Google play
as previuosly mentioned, the device is rooted and Super user capabilities are set
created a mount-point for the nfs share
installed cifsmanager for mounting/unmounting with one click later
I tried to manually mount the share in the terminal. Without busybox i had no luck, but actually that was not sursprising at all. With busybox however, it worked instantly - what indeed surprised me, because this thread here implied somehow the kernel, as is, wasn't even capable to do it without additional modules. I could easily browse the share with ES file manager etc. and make use of my shares. So far, so great. :good:
But opening a terminal, get super user rights and mount manually by typing the whole sequence of
Code:
busybox mount -o nolock,vers=3 -t nfs 192.xxx.xxx.x.x:/my/nfs/share /mnt/MyLocalFolder
is not what you'd call simple or user-friendly at all.
So i aimed to improve the mount procedure with cifsmanager, but I always fail. And do no not understand what i am doing wrong. Initially i tried it without further kernel modules, encouraged by the success i had with busybox. But i always got a "Invalid argument" reply.
During the troubleshooting I stumbled upon this post, and thx to zxp's files, i managed to add the kernel modules to my /system/lib/modules folder (and yes, I have the exact same original/stock GB kernel version they are intended for).
But still no luck - even after i added slow-work.ko to the list of modules loaded by cifsmanager in the properties (placed before cifs.ko as it was suggested by another thread found somewhere in the forum). The info tab states the modules are loaded, but i still receive the same crooked "Invalid argument" message. What the heck am I doing wrong?
Seems to me there is some sort of general syntax issue - here is what info I give the app:
Share: 192.xxx.xxx.x.x:/my/nfs/share
Mount Point: /mnt/MyLocalFolder (tested with and without the mount point prefix in properties)
User: guest (default - without it, it wont work,app description states it will be ignored for nfs shares anyway)
Pwd: left empty
Options:nolock, vers=3 (tested with and without these - but where generally considered essential in some threads + my shares are nfs_v3)
Does somebody have an idea what is going wrong and might point me in some useful direction?
Thanks and Cheers to you all,
Nix
Use script manager and create a script!
Nixblicker said:
Hello folks,
as this is my first post here, i'd like to thank all of the contributors for the excellent Guides and Howtos on this platform. Based on the instructions in this forums i was able to root my Xperia Mini Pro sk17i and greatly expand my devices applicability. Thanks to all of you!
Sorry, that the post got that long - hope that someone is still so kind to read and answer to it. I just wanted to be as precise as possible in the desription of my problem.
And here it comes. As the title of my post already implies, my ultimate goal is to mount nfs shares of my NAS and Router in my private network as user-friendly and simple as possible.
So far, I tried the following to achieve this goal:
Install busybox to generally expand linux capabilities of the device
install the Android Terminal emulator also from Google play
as previuosly mentioned, the device is rooted and Super user capabilities are set
created a mount-point for the nfs share
installed cifsmanager for mounting/unmounting with one click later
I tried to manually mount the share in the terminal. Without busybox i had no luck, but actually that was not sursprising at all. With busybox however, it worked instantly - what indeed surprised me, because this thread here implied somehow the kernel, as is, wasn't even capable to do it without additional modules. I could easily browse the share with ES file manager etc. and make use of my shares. So far, so great. :good:
But opening a terminal, get super user rights and mount manually by typing the whole sequence of
Code:
busybox mount -o nolock,vers=3 -t nfs 192.xxx.xxx.x.x:/my/nfs/share /mnt/MyLocalFolder
is not what you'd call simple or user-friendly at all.
So i aimed to improve the mount procedure with cifsmanager, but I always fail. And do no not understand what i am doing wrong. Initially i tried it without further kernel modules, encouraged by the success i had with busybox. But i always got a "Invalid argument" reply.
During the troubleshooting I stumbled upon this post, and thx to zxp's files, i managed to add the kernel modules to my /system/lib/modules folder (and yes, I have the exact same original/stock GB kernel version they are intended for).
But still no luck - even after i added slow-work.ko to the list of modules loaded by cifsmanager in the properties (placed before cifs.ko as it was suggested by another thread found somewhere in the forum). The info tab states the modules are loaded, but i still receive the same crooked "Invalid argument" message. What the heck am I doing wrong?
Seems to me there is some sort of general syntax issue - here is what info I give the app:
Share: 192.xxx.xxx.x.x:/my/nfs/share
Mount Point: /mnt/MyLocalFolder (tested with and without the mount point prefix in properties)
User: guest (default - without it, it wont work,app description states it will be ignored for nfs shares anyway)
Pwd: left empty
Options:nolock, vers=3 (tested with and without these - but where generally considered essential in some threads + my shares are nfs_v3)
Does somebody have an idea what is going wrong and might point me in some useful direction?
Thanks and Cheers to you all,
Nix
Click to expand...
Click to collapse
that works, but...
Well, yeah - that was an option. I already did, and it works with the busybx mount as stated.
But i would have to write another to mount another share, unmount them, and one to prevent ES file manager to somehow occupy the mount to make it busy before unmounting etc.
I hoped that cifsmanager would smooth and ease the mounting/unmounting.
Thank you for your suggestion, anyway!
Cheers, Nix
shardul_seth said:
Use script manager and create a script!
Click to expand...
Click to collapse
Hi
I've installed CM10.2 (last update) (http://forum.xda-developers.com/showthread.php?t=2499796) on my Archos 80G9. It also runs the SDE firmware from Archos (http://forum.xda-developers.com/showthread.php?t=1653566). So far, so good, it runs quite nicely, all things concerned. Here's a screenshot to the system info: https://www.dropbox.com/s/0ri8n4jb6gyrfz7/Screenshot_2014-11-17-20-56-01.png?dl=0
Now I'm trying to install X-posed Framework, but this won't work. When I try, I get an error that tells me /system can't be mounted. (Screenshot: https://www.dropbox.com/s/ryaryqkie023sl4/Screenshot_2014-11-17-20-40-16.png?dl=0 )
When I take a look is ES3 if the folder is mounted, it looks like this: https://www.dropbox.com/s/4kwv0ja16qz52tq/Screenshot_2014-11-17-20-49-21.png?dl=0 . I can't tick the other boxes here, I get the message "sorry, operation failed" when I try.
I've already tried to use the "mount -o remount,rw /" command, to no avail...
I have no idea how I have to fix this problem and if it's even fixable.
Does anyone have any idea? Thanks in advance!
Same here...
No solution for that yet.
Before you type the mount command did you type "su" first (without the quotes)?
Just opening up terminal gives you regular user permissions which will not let you run the mount command. You need to become root/superuser first and that's what su does.
Yes I did ... Terminal emulator gives a notification that It's been granted superuser permission, but it still doesn 't Work.
Sent from my Ascend Y300 using XDA Free mobile app
Can you send a screenshot of the "mount" comand and response?
Did the prompt change from $ to #? What was the output of "mount"?
If terminal doesn't work try with superuser adb (allow superuser not only from applications, but from adb). Connect to the device with "adb shell" and issue this command.
Hi, thanks for your response. Here are two screenshots: the first is of the mount command in Terminal Emulator, the second of the same via abd shell. No results.
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Bor-ka said:
Very strange, since filesystem seems to be remounted rw Ok.
In fact, I've installed xposed some two days ago on 101g9/cm10.2, so this should work.
Let's try to sort it out.
1) What version of xposed do you try to install? I've used latest stable (2.6 IIRC).
2) Do you use "standard" installation mode in xposed settings (just under the popup window on your screenshot)?
3) Try to issue the following commands in shell after remounting "/" (terminal or adb - doesn't matter)
# touch /system/bin/mytest.tmp
# ls -la /system/bin/mytest.tmp
If the file is created Ok, then the filesystem is mounted read-write correctly.
You can delete this file afterwards with
# rm /system/bin/mytest.tmp
4) Did you grant permanent or one-time superuser permission for xposed? If one-time, try permanent: it can be so, that "cp" fails due to lack of superuser permission.
Click to expand...
Click to collapse
1) I had 2.7 Experimental, so I uninstalled it and installed 2.6 Stable instead.
2) I do indeed use the "classical" option for installing Xposed.
3) Tried it, gave the following result: the file is created in /System/bin, so I guess /sytem is mounted okay. (see screenshots)
4) I use SuperSU, XPosed had root acces (see screenshot)
Seems to me /system is mounted fine, but Xposed just doesn't know it...
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Bor-ka said:
Ok.
The problem is with xposed, obviously.
For me, it complained that it can not remount /system (obviously), but then installed Ok.
So, what I would do
1) Check the filesystem mounts. May be, for some reason, you have /system mount (quite improbably, but nonetheless). Try in the terminal
# mount
It will show a list of all active mounts with the following format
[what is mounted] [where mounted] [blah-blah and stuff]
For example, from anothe device
/dev/block/platform/hi_mci.1/by-name/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
You can see that something is mounted at "/system" readonly ("ro" attribute)
2) Check if the /system/bin/app_process.orig already exists
# ls -la /system/bin/app_process.orig
3) Try to use logcat to obtain info. That is tricky
a) On the PC issue command "adb logcat > logcat.txt"
b) Start xposed installer, try to install, get an error
c) on PC press Ctrl-C
Click to expand...
Click to collapse
Alright, did all of it.
1) Don't fully understand what is listed here, but in the first screenshot is the list of mounts.
2) Checked it, doesn't seem to exist, see second screenshot.
3) Logcat is attached.
Ok, it appears that I got the problem. Need a little time to think how to solve this.
The problem is rather technical. In newer androids supersu has isolated filesystem mounts for different processes.
It means that if you remount filesystem rw in one process, it (read-write-ness) is not accessible to the other process.
I have a little older cm10.2 build (for low-memory devices), perhaps, this was enforced later.
http://su.chainfire.eu/#how-mount (3.5)
So you're saying there's a good chance that if I install version 22_12_2013-13_29_20 (which i was planning anyway), instead of the latest one, the problem could be fixed?
Hmm, I installed the previous version of CM10.2, the problem seems to be persisting...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work. Seems I do have rw access to /system, but not with all apps...
I noticed something today. I can create and remove files in /system using the emulator. I can't however do this using ES3 file explorer, even though it has root access. I was trying to edit the build.prop file, but it wouldn't let me save my changes.
I then tried to copy a file to /system in es3, this didn't work. Creating a tmp file using emulator did work (permission denied). Seems I do have rw access to /system, but not with all apps...
Well, it seems like what I've said, filesystem mount encapsulation.
I've noticed one thing - you are using the standalone supersu application. And for me superuser mode is integrated in the system settings near the developer options. May be this is the case, internal superuser is patched already.
Alright, I'll uninstall superSU for now, give it a go with the built-in superuser app. I'll let you know!
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself.
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Bor-ka said:
Supersu application, theoretically, could have replaced libsuperuser and other stuff integrated in the CM.
So, if just uninstalling does not work, perhaps it will make sense to reinstall CM itself..
Click to expand...
Click to collapse
Eureka! I re-installed CM, issued the mount-command i used earlier and installed X-posed! I used the built-in superuser app, no such problems as before. I did have to issue the mount-command, but that isn't a problem Is it normal I have to re-issue the mount-command each time I want to access /system rw?
Thanks a million! I can't believe it was something this trivial But I'm so glad it's solved, thanks!
Bor-ka said:
P.S. I have mixed feelings with CM. On the one hand it is definitely more fluid, than 3.* or 4.* stock ROMs. On the other hand deep sleep works, well, strange, and the tablet sometimes freezes in the sleep or turns off by itself.
Yes, I have enabled deep sleep, but the battery drains definitely faster in the sleep. For me it is essential, since I mostly use it as a amazon kindle / google books / pdf reader terminal. And most of the time it just sleeps.
Click to expand...
Click to collapse
I don't use the deepsleep-option. I do use Greenify to ensure certain apps (like Youtube or Chrome) aren't active in the background. Boot manager to be sure only essential apps boot in the first place. This seems to save me some battery life. Airplane mode as well.
I got this tablet from my dad because it was so slow he couldn't work with it. Even after factory reset, it very quickly became sluggish again. With CM, it feels like it's a new tablet. So no doubts about CM for me
I do have another issue: My pc won't show the tablet in explorer. I can access it via ADB, but I can't access the storage via explorer... I suppose I best start a new topic for that...
Glad the issue was solved. I wonder why the superuser application didn't work.. Deepsleep - it allowed the tablet to lose, say, 10-15% charge during a week sleep. Very handy if the tablet is used not often - really miss it.
Explorer connection - if I remeber correctly, you should go to settings -> storage (where the size of apps/pictures etc is shown). Then press the three dots in the upper right corner, select "usb computer connection" and select MTP.
P.S. I wonder also if CM12/Android 5.0 in the "development" section is worth a try...
Hello all, I got my Amazfit Pace a few days ago and the first thing that I wanted to do after flashing PACEified was get proper on-device root, as you know right now PACEified comes with adb root shell so we can modify the watch however we want from and adb shell but that means we're always dependent on another device for doing so, apps on the watch have no way of getting root access.
I am actually amazed that no one else even seemed to have any interest in achieving this as it was somewhat easy for me to figure it out and now I'm sharing it with y'all.
Requirements: being on a ROM that has adb root (ex: PACEified) or ability to boot the temproot kernel.
WARNING: If the stock kernel has dm-verity the temproot then install SuperSU method will lead to the device refusing to boot, I do not know whether it does or not.
Disclaimer: I am in no way responsible for any damage this can or will cause to your watch and/or phone, you are the only one responsible for your own actions.
Anyway here's the steps to getting SuperSU 2.79 fully working on your watch:
Download the attached zip file.
Copy the zip file to the watch.
Open a terminal/cmd/powershell in the folder where your adb binary is located.
Run the following commands in order:
Code:
adb root
Code:
adb remount
Code:
adb shell
Now you are running shell commands on the watch itself so do:
Code:
busybox unzip /sdcard/SuperSU-2.79-amazfit.zip
Code:
cd /sdcard/supersu/
Code:
sh root_amazfit.sh
Done, reboot and enjoy!
I hope this helps others as it did help me and I do hope I didn't make any mistake.
Credits:
Chainfire for SuperSU
Neuer_User for PACEified
KevinX8 for the SuperSU 2.79 zip for Android Wear (I used that one cause it already is setup to allow all by default)
Everyone else that I can't remember right now
List of useful root apps for the Amazfit:
MiXplorer-useful file manager with addons and root file management options: https://forum.xda-developers.com/showthread.php?t=1523691
Kernel Adiutor 4 Wear-very popular kernel options management app, won't give too many options since the stock kernel is actually quite limited but still allows tweaking a few things like changing the schedulers and their options, enabling init.d and other such stuff: https://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122 (I only tested this version but the latest normal Kernel Adiutor version might also work perfectly since the interface seems pretty friendly with low resolutions)
Advanced Settings for Watch-provides a plethora of options like Bluetooth and WiFi settings management, reboot menu and most importantly PACKAGE MANAGEMENT and by that I mean it doesn't just have the normal app settings menu that allows you to clear data/cache, force stop or disable/uninstall apps but ALSO INCLUDES A PACKAGE INSTALLER for installing apks straight on the watch: https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en (get the wear apk from inside the main apk, it is located in /res/raw just open the phone apk as an archive also WARNING: many menus/options make it crash cause this is not Android Wear)
Another one.
Wich are the benefits of doing that?
jmpcarceles said:
Wich are the benefits of doing that?
Click to expand...
Click to collapse
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Ranomez said:
Same as on any other rooted Android device.
A few apps I have on the watch that use root are:
MiXplorer-file manager
Kernel Adiutor-can improve battery life/performance by messing around with it a bit
Root Essentials (the wear part sent from inside the phone apk)-it's great for uninstalling apps and such
Click to expand...
Click to collapse
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
lfom said:
Hello. Stock ROMs can boot "temproot kernel"? Could you please like to where it's explained? Thanks.
Click to expand...
Click to collapse
Stock ROM can boot temproot kernel only if old enough version to not have the bootloader locked OR you unlocked the bootloader after, to get the temproot kernel go to the PACEified thread and read the install instructions, it has you booting the temproot kernel on order to flash it and it might be possible to just boot it, root and reboot but I am not entirely sure, if the Amazfit has dm-verity it will refuse to boot after altering the system, I actually didn't think about that when I wrote this guide cause it was 5AM so would recommend flashing a custom ROM.
@Neuer_User does the Amazfit have dm-verity?
Also would you consider adding SuperSU to PACEified in the future?
Double post cause mobile XDA is messed up, delete.
jmpcarceles said:
Nice.
MiXplorer is my mobile favourite Android explorer.
I don't know the other apps, i must learn about it.
Any suggestions about them, Kernel auditor seems very interesting. I have very much problems with my Amazfit battery, last month suddenly i don't get more than 2 days of autonomy
Thx.
Click to expand...
Click to collapse
To be honest MiXplorer just about works but isn't really 100% usable cause things don't fit on screen, looking for a better root file explorer for the watch.
The stock kernel doesn't really allow you to control much cause the stock kernel doesn't seem to have too many features but can still change governor and a few other stuff and if nothing else it can enable init.d if you don't already have it enabled, I use the Kernel Adiutor 4 Wear version but TBH I think the normal one should be just as usable.
For your battery problem you could try deleting some unneeded apps like the Mi Home or the Chinese radio one (if on Chinese ROM/PACEified) and maybe Greenify will also work but wouldn't really put my bets on it, perhaps try using some battery saving scripts?
Right now I'm looking for an apk installer...I have a solution already but it's probably the worst one possible: a init.d script that checks if there are apps in a folder on the internal storage then installs all of them and deletes the apk files but that means you need to reboot in order to install apps, could make crond run the script every hour or so but that would also not be too convenient so either a script runner or a apk installer would be best.
BTW after uninstalling apps from the watch using a root app you need to crash the launcher or it will still show the icons for the uninstalled apps.
Also I'm working on improving the script to add safety checks (if someone tries to run it without the other files in the same folder right now it would most certainly end up in a mighty bootloop, fortunately a bootloop with adb access so easy to fix but still not great, I made that script in like 5-10 min after I manually did it on my own watch) and add more features like installing a newer busybox version and linking missing applets (unzip for example).
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Ranomez said:
Updated 2nd post with a few useful apps, one of them finally giving us the power to install apps straight on the device, will publish the new version of my script in a few days, have been working on adding A LOT of new features and now I kinda need to concentrate on the project for my Android class for a bit, sorry for the delay.
Click to expand...
Click to collapse
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
jmpcarceles said:
Hi Ranomez,
When do you plan to publish the new script for local root?
Thx in advance.
Merry Xmas.
Click to expand...
Click to collapse
Most probably next week, haven't really had time to work on it with the last week of college before the holidays and the fact that I bought Xenoblade Chronicles 2 on launch day and it's been eating most of my free hours, lol, sorry for the delay, anyways the current script still works for simply rooting but will give a no such file or directory error if init.d isn't already enabled, just ignore that.
Thank you @Ranomez
I've just tried your local root using the temproot kernel on the latest stock rom, and it worked great. So, I can say my pace doesn't have dm-verity enabled?
btw, SU was added to Stockfied, Pacefied and Stratosfied, just needs to be enabled.