Related
Hi Everyone,
Has anyone gotten A2SD from this thread:
http://forum.xda-developers.com/showthread.php?t=670087
To work on an Aria.
Please let me know.
I would love to know too. I'm tempted to try it, worst case scenario, I have to restore a backup.
It won't work with the stock kernel. Unless you can build a kernel to support it which I do not know how to it will not work for you.
this would be great, thinking of toying around with it myself.
I just go gave it a quick run through to no avail using rom manager to format the sd card into the proper partitions and then flashing the zip file in clock work as directed. I will try it again tomorrow when I'm not so damn tired. Apparently it works on the stock sprint hero 2.1 rom so maybe I'll research more into how that was accomplished as there is no reason this method needs a specialized kernel.
Sent from my HTC Liberty using XDA App
I've been playing with it a little this morning. It appears it is having trouble initializing a mount point in /system/SD. I will try a symlink from /sdcard to a created sir named /syste/SD until I figure out why the userland differs so much from the other ''stock'' 2.1 roms this appears to run on.
Sent from my HTC Liberty using XDA App
It won't work, the stock htc kernel does not support it.
Quit being a naysayer and read the list of stock based roms that support this particular method. There are several app2sd methods and there is no reason this one shouldn't support the stock kernel unlike the cyanogen style methods. I may not be able to do it yet but I defer the possibility of figuring it out to users who may be more skilled than myself rather than regurgitating the same thing over and over without research.
Sent from my HTC Liberty using XDA App
I have a2sd working on attn's liberated_aria b005
step 1: download Rom Manager from the Market
step 2: select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
step 3: reboot phone into clockwork recovery; select partitions menu and mount /system.
step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this [or TextWrangler for OS X] ) :
*
*
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plugin your cable and connect your aria to your computer so ready to use ADB
at prompt type:
"adb push install-recovery.sh /system/etc/install-recovery.sh" <-- push file to your aria
"adb shell" <-- shell to your phone.
*
*
Code:
* * #cd /system/etc/
* * #chmod 555 install-recovery.sh* * * * * *
* * #mkdir /system/sd
* * #mount -t ext2 /dev/block/mmcblk0p2 /system/sd* * * * *
* * #mount* * * * * * * *
( if everything is ok, you should see something like this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0 )
now type #exit
Step 6: Test to make sure that it will be automounted after reboot.
on your PC, from command prompt you can type: "adb reboot"
Step 7: After rebooted, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt: "adb shell"
# mount
"/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0" means you EXT2 partition is mounted after reboot.
Step 8: download Darktremor Apps2SD 2.7 Update 3r1 and place it at the root of your sd card.
Step 9: boot into recovery and select flash zip from sdcard
Step 10: In flash zip from sdcard, select the a2sd package file you downloaded earlier. Press home to flash; now reboot your phone
Step 11: now reconnect to your phone through adb.
#su
#a2sd install
Don't panic-- your phone will reboot as the script finishes
Step 12: adb back to your phone and type ls -l /data
You should see
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
a2sd cachesd (move dalvik to sd card)
a2sd cachepart (move dalvik to cache partition)
Now you should have even more internal space left. Enjoy.
Note: moving dalvik to sd card may produce instability in certain apps or force quits. If it isn't working for you just pull up "adb nocache" to move it back to internal storage while still installing apps to the ext partition on your sd card.
Credits to semigod, tkirton and thanks to attn1 (for making good stuff for us)
mosamjc
mosamjc said:
step 1: download Rom Manager from the Market
step 2: select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
step 3: reboot phone into clockwork recovery; select partitions menu and mount /system.
step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this ) :
*
*
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plugin your cable and connect your aria to your computer so ready to use ADB
at prompt type:
"adb push install-recovery.sh /system/etc/install-recovery.sh" <-- push file to your SmartQ
"adb shell" <-- shell to your SmartQ. Now you are at your SmartQ shell
*
*
Code:
* * #cd /system/etc/
* * #chmod 555 install-recovery.sh* * * * * *
* * #mkdir /system/sd
* * #mount -t ext2 /dev/block/mmcblk0p2 /system/sd* * * * *
* * #mount* * * * * * * *
( if everything is ok, you should see something like this:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0 )
now type #exit
Step 6: Test to make sure that it will be automounted after reboot.
on your PC, from command prompt you can type: "adb reboot"
Step 7: After rebooted, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt: "adb shell"
# mount
"/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0" means you EXT2 partition is mounted after reboot.
Step 8: download Darktremor Apps2SD 2.7 Update 3r1 and place it at the root of your sd card.
Step 9: boot into recovery and select flash zip from sdcard
Step 10: In flash zip from sdcard, select the a2sd package file you downloaded earlier. Press home to flash; now reboot your phone
Step 11: now reconnect to your phone through adb.
#su
#a2sd install
Don't panic-- your phone will reboot as the script finishes
Step 12: dab back to your phone and type ls -l /data
You should see
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
a2sd cachesd (move dalvik to sd card)
a2sd cachepart (move dalvik to cache partition)
Now you should have even more internal space left. Enjoy.
Credits to semigod, tkirton and thanks to attn1 (for making good for us)
mosamjc
Click to expand...
Click to collapse
way to stick to your guns, ill try this later after i return from dinner
Please do. I'd like to know if it works for others as well. I can wait for a fully fleshed cm6 port with all working features (or a legitimate froyo for that matter), but additional space for applications is something that I desperately needed now (and now I do).
mosamjc said:
Please do. I'd like to know if it works for others as well. I can wait for a fully fleshed cm6 port with all working features (or a legitimate froyo for that matter), but additional space for applications is something that I desperately needed now (and now I do).
Click to expand...
Click to collapse
Just so happens this is the same day that CM6 from attn1 came out so i jumped the gun and ended up playing with his alpha Rom. So i have not validated this, BUT I can confirm apps2sd work on Attn1's new rom
Ha. I picked a hell of a day to try get creative. Hopefully it will be of use to someone until the cm6 build gets all its bugs ironed out.
Sent from my HTC Liberty using XDA App
dalvik cache issue
All of this worked fine, except for the dalvik cache part which had an error about not enough space while copying files.
How can moving dalvik cache be undone? It doesn't seem that "adb nocache" is a valid command.
Edit: Oh it should be "a2sd nocache" that seems to have fixed it
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
I am not very linux or android savy, but I will have to give this a try. It was the only thing missing from the Liberated rom. Now all is well. Thanks!
Hopefully, next we can get a Froyo w/ Sense UI! And our Arias can keep on rocking.
You may try the 2.7.5 RC1 and see if that helps the issue. There were fixes regarding copying files (permission issue...didn't tell it to retain permissions...didn't see that until 2.7.5 PF4A).
Glad to see you guys progressing on this. If someone knows the boot image base address for the Aria, I will modify a stock boot image for apps2sd.
Need any help, feel free to ask me. Any help I can give you to getting this program working on your rom I will be happy to do.
mosamjc said:
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
Click to expand...
Click to collapse
Here is a slightly modified version, mainly just changed formatting and fixed a few typos. Also my phone didn't automatically reboot after step 11. Thanks for the great guide!
Step 1: Download Rom Manager from the Market
Step 2: Select partition sd card; select whichever size ext partition you desire (you can also create larger ext partitions doing this manually on a linux box but I won't cover it.
Step 3: Reboot phone into clockwork recovery; select partitions menu and mount /system.
Step 4 (borrowed from Semigon at SmartQ MID forums):
Create a file called install-recovery.sh at <your android SDK installation>/tools/ on your PC with this code (MAKE SURE YOU CAN SAVE IT AS UNIX, ANSI TEXT , I use TextPad to do this ) :
Code:
Code:
#!/system/bin/sh
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
Step 5:
Plug in your cable and connect your Aria to your computer so it is ready to use ADB. At prompt type:
Code:
adb push install-recovery.sh /system/etc/install-recovery.sh # push file to your Aria
adb shell # shell to your Aria. Now you are at your Aria shell
Code:
Code:
cd /system/etc/
chmod 555 install-recovery.sh
mkdir /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount
If everything is ok, you should see something like this:
Code:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
Now type:
Code:
exit
Step 6: Test to make sure that it will be automounted after reboot. On your PC, from command prompt you can type:
Code:
adb reboot
Step 7: After rebooting, you can either use adb or use "Terminal Emulator" to see if your SD EXT2 partition is mounted.
Connect as in step 1)
On your PC, from command prompt:
Code:
adb shell
mount
If your EXT2 partition has been mounted after reboot you will see:
Code:
/dev/block/mmcblk0p2 /system/sd ext2 rw,errors=continue 0 0
Step 8: Download Darktremor Apps2SD 2.7 Update 3r1 and place it in the root of your sd card.
Step 9: Boot into recovery and select "install zip from sdcard"
Step 10: Select the a2sd package file you downloaded earlier. Press power button to flash; now reboot your phone
Step 11: Now reconnect to your phone through adb:
Code:
adb shell
su
a2sd install
Don't panic-- your phone may reboot as the script finishes
Step 12: Connect with adb back to your phone:
Code:
adb shell
Then type:
Code:
ls -l /data
You should see
Code:
lrwxrwxrwx root root 2010-07-27 14:56 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-07-27 14:56 app -> /system/sd/app
Now check your phone storage. You should see that you have significantly more available then you did before. If you see it slowly decrease this is because the dalvik cache is still on the internal memory. This too, however, can be moved to the sd.
The following is from tkirton's main set of instructions found at hxxp://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
If you want to move the dalvik-cache to the sd card, type:
Code:
a2sd cachesd # move dalvik to sd card
a2sd cachepart # move dalvik to cache partition
Now you should have even more internal space left. Enjoy.
Note: moving dalvik to sd card may produce instability in certain app or force quits. If it isn't working for you then move it back to internal storage while still installing apps to the ext partition on your sd card with:
Code:
a2sd nocache
Credits to semigod, tkirton and thanks to attn1 (for making good for us)
mosamjc
Click to expand...
Click to collapse
mosamjc said:
Well, I'm glad I have at least one happy customer. The cache transfered over fine for me but caused highly irregular behavior in 90% of the apps that cleared up the second I transfered it back. Could be a permissions issue or simply one that could be solved by reinstalling all your apps into the new sd environment. I'm not terribly concerned as installing the apps on the sd leaves plenty of space free for the caches to do their thing.
Click to expand...
Click to collapse
Sounds very similar to what happened for me. The script completed even with a few copy errors, but then many applications had FC after reboot. There is more than enough space from moving the apps, so it was not a big problem.
tkirton said:
You may try the 2.7.5 RC1 and see if that helps the issue. There were fixes regarding copying files (permission issue...didn't tell it to retain permissions...didn't see that until 2.7.5 PF4A).
Glad to see you guys progressing on this. If someone knows the boot image base address for the Aria, I will modify a stock boot image for apps2sd.
Need any help, feel free to ask me. Any help I can give you to getting this program working on your rom I will be happy to do.
Click to expand...
Click to collapse
Will give the the newer version a try, by installing the new zip then running the cachesd and cachepart commands again. Thanks!
@MikeChelen Way to polish the tutorial. Looking good! I hammered that out in in only a few minutes originally after pulling together all the parts that made it tick for me. I just wanted to release it to the masses quickly to prove jznomoney wrong (am I a bad sport? Probably).
@Tkirton I will give the new version a go after lunch and see what happens. As far as the boot image address, I believe it is the same as the Legend, as almost all legend roms flash and boot successfully on the Aria. So I would give 0x12c00000 a try on Attn1's Liberated_Aria.
mosamjc said:
@MikeChelen Way to polish the tutorial. Looking good! I hammered that out in in only a few minutes originally after pulling together all the parts that made it tick for me. I just wanted to release it to the masses quickly to prove jznomoney wrong (am I a bad sport? Probably).
@Tkirton I will give the new version a go after lunch and see what happens. As far as the boot image address, I believe it is the same as the Legend, as almost all legend roms flash and boot successfully on the Aria. So I would give 0x12c00000 a try on Attn1's Liberated_Aria.
Click to expand...
Click to collapse
Haha, well I am glad you did! It meant the guide was available for me a little sooner. Score another point for stubborn resolve
It was more than clear enough for me to follow, hopefully the edits will help newer users though.
It might also be worth noting that ANSI is not an encoding itself, but a set of encodings? The normal Linux text editors seem to use US-ASCII or UTF-8 and these should probably both work.
Assuming other users don't have any problems, hope this gets added to the Aria sticky topic ^_^
Thanks again everyone!
Hi all,
is it possibile to modify the content of the files fills with the content of the partitions read from the Tegra of my LG P990 with nvflash?
I had read the partition from the board with
Code:
nvflash -r --read <-partitionID-> my_partition.img
Unix's command file said to me that the output file is data:
Code:
$ file my_partition.img
my_partition.img: data
But if the correct img file is provided to 'file', for example the file that nvflash returned when we asked it to read the partition 23, the APP partition, 'file' said:
Code:
23_APP.img: Linux rev 1.0 ext4 filesystem data, UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (needs journal recovery) (extents) (large files)
How i can mount this type of image file ?
Easily with the 'mount' Linux utility
Code:
mount ./my_partition.img ./tmp_directory
Now, if I add the su binary of chains_dd compiled for my platform in the system partition image file and after,
reflash the image file on my O2X I should able to get root, right?
It seems too easy...
Any help is appreciated.
Thanks!
Yes, it is "easy" like that. I made similar staff (extract partition image from official update, mount, extract selected files).
Edit: Only I remember that I need to specify mount parameters related to partition format and mounting access.
Have you really gain root access only by copyng (and launching ) su binary in xbin directory?
tryin said:
Have you really gain root access only by copyng (and launching ) su binary in xbin directory?
Click to expand...
Click to collapse
Y E S . . .
Indeed, if you only want a root prompt, chains_dd's binary is too much...
tryin said:
Y E S . . .
Indeed, if you only want a root prompt, chains_dd's binary is too much...
Click to expand...
Click to collapse
Take a look at this...
http://forum.xda-developers.com/showthread.php?t=2280447
Hey guys! Today i am showing to you how to create a swap file for ram expansion without any app. Easy and simple!
Also i will give you an init.d script that will enables and starts the swap at all the boots!
What you need:
- Installed Kernel with Swap function and init.d (NOT the stock one!!! This metod is tested on my thunderkernel RC1)
- Root
- A file explorer (ES File Explorer recommended!)
- Terminal Emulator
- An sdcard (recommended class 10)
- A Galaxy Ace-i
OK LET'S START!
FIRST METHOD (Create a swapfile on your sdcard)
1) Open terminal emulator and type this things (type enter at the and of any line!)
NOTE: "count=700000" creates a 341MB swap file! "count=300000" creates a 146 MB swap file!
Code:
su
dd if=/dev/zero of=/sdcard/swapfile count=700000
chmod 777 /sdcard/swapfile
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
2) Ok!!! Now you have created the swap file and you have activated it! Now it is time to download the init.d script in the attachment. (For the first method!)
3) Extract the 99_swap on your phone sdcard.
4) Open ES File Explorer and copy 99_swap in /system/etc/init.d. Then go to terminal emulator and type
Code:
su
chmod 777 /system/etc/init.d/99_swap
5) Reboot your phone!
6) With this method you can see on logcat the status of the activation of swap, search for swap in the logcat. Also if you can't logcat you can open /data/swap.log!
7) NOTE: with this method when you will connect the phone to the pc, the mount will fail. You have to go tho terminal emulator and type
Code:
su
swapoff /sdcard/swapfile
Then when you will disconnect usb cable you will have to type this for reactivate swap
Code:
su
swapon /sdcard/swapfile
SECOND METHOD (Using csc partition, thanks to rafael.baugis and domnic79)
1) Open terminal emulator and type
Code:
su
dd if=/dev/zero of=/dev/stl10
mkswap /dev/stl10
swapon /dev/stl10
2) Ok!!! Now you have created the swap file and you have activated it! Now it is time to download the init.d script in the attachment. (For the second method!)
3) Extract the 99_swap on your phone sdcard.
4) Open ES File Explorer and copy 99_swap in /system/etc/init.d. Then go to terminal emulator and type
Code:
su
chmod 777 /system/etc/init.d/99_swap
5) Reboot your phone!
THANKS TO:
- Me for first method, init.d scripts and this guide
- rafael.baugis and domnic79 for second method
I AM NOT RESPONSIBLE FOR DEAD SD CARDS! DO IT AT YOUR OWN RISK!!!
is there easy method for make swap partition? Partition creating on sd is easy by using some partition tools on pc, but how to mount it on phone?
With this method you don't have to create a swap partition on your sdcard! It uses a file instead of a partition!
Posted from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip... : P
yeah i know it just asking for 3rd method. Anyway, can you tell me how much swap file reduce sdcard life?
drumiec said:
is there easy method for make swap partition? Partition creating on sd is easy by using some partition tools on pc, but how to mount it on phone?
Click to expand...
Click to collapse
Mini tool partition wizard for creating the swap partition.
Swapper2 app for mounting the partition, set swappiness, save unmount, ...
Sent from my GT-S5830i using xda app-developers app
drumiec said:
yeah i know it just asking for 3rd method. Anyway, can you tell me how much swap file reduce sdcard life?
Click to expand...
Click to collapse
michielvDroid said:
Mini tool partition wizard for creating the swap partition.
Swapper2 app for mounting the partition, set swappiness, save unmount, ...
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
But this guide is for creating a swap file without apps! Anyway you can use also CWM for create swap partition... But yuou will lose all your files on sdcard.
A swap partition, or swapfile, on the sdcard will reduce the life of 25/50% but if you have a class 10 i think the life will be more longer lasting!
Posted from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip... : P
i created swap partition when i create ext2 for link2sd, but i never mount it
While typing first command in both methods it shows write error...
Sent from my GT-S5830i using xda premium
Have you got root? And have you typed the exact words?
Posted from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip... : P
edit:
72MB of swap is installed with busybox (pro).
I've a question Lopi, if I'm on stock ROM and install custom Kernel, keeping in mind that stock ROM uses the CSC, won't it be better to use on a ROM that actually doesn't use the CSC? or it doesn't hurt the ROM to break the CSC area?
El_Dark said:
I've a question Lopi, if I'm on stock ROM and install custom Kernel, keeping in mind that stock ROM uses the CSC, won't it be better to use on a ROM that actually doesn't use the CSC? or it doesn't hurt the ROM to break the CSC area?
Click to expand...
Click to collapse
CSC area is not important
Inviato dal mio Nexus 7 con Tapatalk 4
Hi everyone, I modified the stock uRamDisk for CM11 by decompressing it, editing the fstab.encore.rc file, and switching up the part with sdcard0 and sdcard1.
P.S. I removed the zram (compressed RAM) option in the fstab because the Nook Color has a crappy enough CPU as is, so it wont help with zram. Use a swap partition on SDcard if needed.
P.S.2. This ramdisk is from the most recent nightly build (Jan 11, 2015). It may or may not work with older CM11 builds.
It's attached here. It wont let me upload the file as is, so I renamed it to uRamDisk.7z; rename it back to uRamDisk. After that, follow these steps:
0. MAKE A BACKUP OF THE /boot PARTITION IN YOUR RECOVERY JUST IN CASE. If anything happens, restore the /boot partition's backup.
1. Mount /boot partition at /root (it's an unused mountpoint in Android)
adb root && adb shell
# mount -t vfat /dev/block/mmcblk0p1 /root
2. Change directory to /root, rename the original ramdisk
# cd /root && mv uRamDisk uRamdisk.orig
3. Copy over the new ramdisk
adb push uRamDisk /root/
4. Reboot and profit
The internal sdcard will now be seen as external. You no longer need to have an SD card inside to have many apps like Kodi (XBMC), Firefox, etc, asking for external SD.
If it doesn't work for you for some reason, remount the /boot partition again, and copy over the original uRamDisk ( # cp -f uRamDisk.orig uRamDisk ).
I used parts of this script to figure out how to mod the ramdisk: https://gist.github.com/aperezdc/6533546
Any feedback on this one?
les02jen17 said:
Any feedback on this one?
Click to expand...
Click to collapse
Huh, what do you mean? If you have feedback for me, please do post it.
hi,could you compile a flasheable zip file?because many people like me dont know how to use adb or you can explain these steps a bit better, other thing is that i cant change the name to uramdisk(i cant delete .7z) windows 7 and winrar wont let me
btw good work!!
omars44 said:
hi,could you compile a flasheable zip file?because many people like me dont know how to use adb or you can explain these steps a bit better, other thing is that i cant change the name to uramdisk(i cant delete .7z) windows 7 and winrar wont let me
btw good work!!
Click to expand...
Click to collapse
1. Do you have adb installed for Windows? If not, do that first.
2. I don't know how to make a flashable zip. Someone else might. Anyone wanna do that? I don't have time atm since college started. Sorry for the late reply.
3. The instructions are about as simple as they get. You should study the "mount," "cp," and "mv" commands. They are, respectively, for mounting partitions, copying files/folders, and moving/renaming files/folders.
4. You can't rename the file because by default, Windows doesn't show file types' endings (like .exe, .zip, .rar, etc). You need to enable that. Google it.
hello, maybe you still have this nigtly cm11 system of 11Jan, 2015? thank's
There have been quite a bit of people with issues with Systemless root, there are some apps that are not recognizing root, i had this issue with my Oneplus One on COS 13.1 and now the same thing works with our OnePlus 3 on OxygenOS
I had come across this on another forum, i don't recall where so i don't want to take the credit for this, i just want to provide the fix for people who have this phone and having issues
Download Terminal from app store and type
Code:
su
mount -o remount,rw /system
touch /system/bin/su
mount -o remount,ro /system
reboot
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
I belive it creates a dummy file bc some apps require it to show as a system file
SDMU said:
Thank you ! Before I try this , can you tell me what this method is doing ? All I can tell is that it is mounting something as read only instead of read write
Click to expand...
Click to collapse
Code:
1. su
2. mount -o remount,rw /system
3. touch /system/bin/su
4. mount -o remount,ro /system
5. reboot
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Squabl said:
1. To get root privileges
2. Remounts /system partition in writable mode
3. Creates an empty file called su to /system/bin/ folder
4. Remounts /system partition to read only mode.
5. reboot
Edit. As stated above, some apps still check root access by looking su file in /system/bin folder
Click to expand...
Click to collapse
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
candiesdoodle said:
This defeats the purpose of a system less su, I.e., not modifying the system partition. Step 3 modifies the system partition.
The reason apps are not seeing the su in system less state is because they have been written incorrectly. Chainfire already said these apps should be re written
Click to expand...
Click to collapse
Yes, it "disables" systemless root and afterwards it is just a root and banking apps and ota updates etc will fail. I don't need systemless root so I have modified my system partition to get some poorly coded apps to function. This method is not recommended if you need systemless root and it's a good thing that you pointed that out!