Related
I just received my new 32gb SD card, and am wondering how to ensure that my ext3 partition is also copied over, not just the fat32 files. I have found some other threads regarding this process but I still have some unanswered questions.
FYI, I am using MIUI 1.11.4 on a rooted Acer Liquid E (and malez-recovery, which is based on CM).
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition? **UPDATE: I ran nandroid-mobile.sh, and it eventually said "--ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't figured out a solution yet. Ideas?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
skittleys said:
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
Click to expand...
Click to collapse
1. Do that (just do it ; in case anything goes wrong, you can restore the nandroid backup and have your device up and running easily). If you don't create one (make sure you do) you will have a hard time getting your device to work again (and depending on your device, it may not be fixable).
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here: http://forum.cyanogenmod.com/topic/19160-modhow-to-apps2ext-for-cm7-updated-03312011/.
3. Using GParted is the easiest method (which is why it is recommended): http://gparted.sourceforge.net/.
Theonew said:
3. Using GParted is the easiest method (which is why it is recommended): .
Click to expand...
Click to collapse
Easier than 3 multiple-choice questions in a recovery I've already installed???
Theonew said:
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here:.
Click to expand...
Click to collapse
I doubt that my ROM does an ext backup by default.... I have now run nandroid-mobile.sh and eventually got the following message: "Warning: --ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't yet figured out a solution for this. In the meantime, I have copied /sd-ext to my computer, which might end up being a decent workaround...but I'd still love to know what's going on!
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
skittleys said:
Easier than 3 multiple-choice questions in a recovery I've already installed???
Click to expand...
Click to collapse
According to others, yes .
skittleys said:
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
Click to expand...
Click to collapse
You cannot "fix" it. That is one reason but it also really depends on your device. For example: http://www.jayceooi.com/2011/01/12/...tition-on-sd-card-with-clockworkmod-recovery/ - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Theonew said:
You cannot "fix" it. That is one reason but it also really depends on your device. For example: - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Click to expand...
Click to collapse
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
skittleys said:
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
Click to expand...
Click to collapse
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
skittleys said:
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
Click to expand...
Click to collapse
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Theonew said:
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
Click to expand...
Click to collapse
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Theonew said:
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Click to expand...
Click to collapse
(I don't have enough posts to insert URLs) I am using Malez recovery 0.6.1 (current is 0.6.2, nothing in the changelog suggests any relevant fixes though). I've searched extensively and it seems that I'm the only malez user having this problem.
Also, I can access sbin, but its only contents are adbd and ueventd. /sd-ext just plain doesn't show up in recovery mode.
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
skittleys said:
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Click to expand...
Click to collapse
It shouldn't break, but on some roms it does.
skittleys said:
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
Click to expand...
Click to collapse
What do you mean?
skittleys said:
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
Click to expand...
Click to collapse
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Theonew said:
What do you mean?
Click to expand...
Click to collapse
When you run ls -l the 3rd and 4th columns show the 'owner' and 'group', respectively. It'll say things like root, system, etc., or maybe 0, 1000, 500, etc.
Theonew said:
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Click to expand...
Click to collapse
So there's no point in running a command like ls through busybox, right?
New question:
All that /system/sd contains is a 0-byte file called 'placeholder'. I can't find much info about this, but it sounds like this is intentional. But I know that this is where the ext partition is supposed to mount to. Does yours look like this (in either normal mode or recovery)? (edit: in recovery mode, the placeholder is gone, replaced with another 0-byte file called 'empty')
Also, do you think you could paste the output of mount when run in recovery?
BTW, A2SD seems to work perfectly otherwise. The only oddity I've noticed is that when I run a2sd forcecheck near the end it tries to unmount the partiton and can't.
Code:
[ ] Launching Apps2SD Start Program with forcecheck
[ ] Starting Darktremor Apps2SD in forcecheck mode
[ ] Creating Force Check Flag File...
[ ] Unmounting /dev/block/mmcblk0p2...
umount: can't umount /sd-ext: Device or resource busy
[ ] Rebooting phone...
Ironic that I can't mount it in recovery yet I can't unmount it normally!
Hi there,
is there a solution to make it possible that a microSD-card formatted in ext4 is able to be mounted in CM9?
This one I found for the Galaxy tab here.
I don't use any window systems and I'm not happy to have to format the extSD-card in FAT32 or exFAT.
Regards
Koeti
No one, who has a solution?
Gesendet von meinem GT-I9300 mit Tapatalk 2
There is such a feature, but you have to proceed with EXTREME caution.
You must also have taken a backup of you sd cards' contents.
Firstly, go and flash the Franco Kernel
On his secong post, you can see the instructions required:
franciscofranco said:
Wi-Fi Power Management toggle:
How to activate the special sdwatcher binary:
This binary is special *buzzwords incoming* and will get rid of the fuse mounting and get rid of the /data/media symlink which causes excessive Media Scanning load - basically just mounts the internal sdcard as ext4. Battery life gets a nice boost using this binary. Instructions on how to use it at the second post. All credits go to Greg White, I did nothing but testing it for him.
To activate use ADB or Terminal Emulator:
mount -o rw,remount /system
cp /system/bin/sdcard /system/bin/sdcard.bak
rm /system/bin/sdcard
cp /sbin/sdcard /system/bin/sdcard
chmod 0777 /system/bin/sdcard
reboot
Don't mess with this if you don't know what you're doing.
Click to expand...
Click to collapse
I, however, did this manually using RootExplorer:
Code:
1) Navigate to "/system/bin/" using a root enabled explorer app. Enable read and write access.
2) Rename the "sdcard" file found in that directory to "sdcard.bak" (so you know have a backup).
3) Navigate to "/sbin/". There will be an "sdcard" file there.
4) Copy the "sdcard" file to "system/bin/".
5) Change the permissions to "rwxr-xr-x".
6) Reboot the system.
My guess is that you can flash any kernel you want after this procedure. I have tried Siyah and it's working fine so far. Your mileage will vary.
If you find the camera saying things like "Unable to write to external storage" or whatever, you have to creat a "DCIM" folder in the root of your external sd card manually. It will then be alright (you have to change the storage device back to external in camera options).
Make a note that this is an extremely advanced procedure that I myself am in the process of fully vetting!
Cheers!
Erahgon said:
Firstly, go and flash the Franco Kernel
Click to expand...
Click to collapse
Thanks for your answer, but franco writes: 'This kernel is for Samsung roms only. No plans to make it work with AOSP or CM9'. So unfortunalety it's only runs on stock roms.
Hi, any news on how to get this to work on other kernels?
Thanks
Phk said:
Hi, any news on how to get this to work on other kernels?
Thanks
Click to expand...
Click to collapse
Also, on the mid-step of this, the file "/sbin/sdcard" does not exist...
So here you come. To read and perform this tutorial, you obviously need a first hand experience on flashing a ROM and/or kernels. Otherwise this tutorial and my efforts to get you a device with two OSes running might end up giving you a bricked device. So, if you're hearing the terms "flashing" or 'kernels' for the first time and thinking it's kinda good food, then bro, just go and taste those first.
Something's to remind before we gonna dig deep into this tutorial->
1> Noone but you will be responsible for what you end up with.
2> The warranty of your device will be voided after this if it isn't already after rooting. For MI users, the good news is that you can reclaim it by just flashing the fastboot ROM for your device.
Enough lectures. Bro let's get to work.
This you'll be needing =>
1> One working Windows PC(because I doesn't know any replacement of bootimg.exe on any other OS. If you know, then let me).
2> A class 10 memory card ( I recommend 32GB for the spaces)
3> A custom ROM and kernel for your phone(the second os)
4> Any custom CWM based recovery installed.(since TWRP is most popular, I will demonstrate using it. You can use any other you want overall process will be the same)
5> ADB, fastboot and the device drivers (easily found in XDA)
PART 1: MODIFYING THE BOOT
At first, how does your device boots up? What are the partitions called /data and /system? The answer is quite simple. It's your kernel that points out the location from where the OS should be picked up. So for booting into the second OS we need some modifications to it at first.
Search and download bootimg.exe on XDA, I'll post a link later. Create two folders. Name them "Internal OS" and "External OS" respectively. Put the zip file of the OS you're currently using to the first one and the OS you're gonna use on the external storage to the second one. Rename the second OS to originalExternalOS.zip. Extract originalExternalOS.zip. Pick the boot.img file from the root of the extracted folder and move it to a new folder named "boot2". Extract the IMG using bootimg.exe. Navigate to the initrd folder and you will get a file named 'fstab".
Basically it's the file that tells the kernel which partition does the OS resides in.
Open the file in your favourite text editor.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
Save the file without giving any extension to it. Repack it using the same tool. You'll have boot-new.img and boot-old.img. Rename boot-new.img to boot.img and replace the one in the root folder with this. Basically what we're doing here is replacing the old boot.img with the modified one.
For your knowledge, blocks are the partitions of any storage you have on your device. For example, your internal storage is partitioned to near about 30 different blocks each starting with prefix "mmcblk0p". We here just told the kernel to load the OS from the blocks mentioned. We'll be creating these blocks in the external SD card next.
PART 2: PARTITIONING THE SD CARD
Connect your device with the memory card inserted to your PC. If you haven't installed fastboot, ADB, and the drivers, do it now.
READ THE FOLLOWING CAREFULLY
Reboot the device to recovery mode. Type the commands in cmd:
Code:
adb shell
parted
unit MB
print
quit
umount external_sd
Read and store the minimum and maximum capacity of your card. Since different cards will have different capacities I will point it as variable MIN_SIZE and MAX_SIZE. You'll need to calculate and put the values in the commands. Now type the following commands on cmd:
Code:
parted /dev/block/mmcblk1
rm 1
//START_BLOCK = MAX_SIZE - 5000
mkpartfs primary fat32 MIN_SIZE START_BLOCK
//SYS_START = START_BLOCK+1
//SYS_END = SYS_START + 1200
mkpartfs primary ext2 SYS_START SYS_END
//DATA_START = SYS_END+1
//DATA_END = DATA_START + 3500
mkpartfs primary ext2 DATA_START DATA_END
//CACHE_START = DATA_END + 1
mkpartfs primary ext2 CACHE_START MAX_SIZE
//We have partitioned the memory card. Let's format them. Ignore all "Do you wish to continue" question in the next commands as we're already mentioning yes.
mkfs yes 1 fat32
mkfs yes 2 ext2
mkfs yes 3 ext2
mkfs yes 4 ext2
quit
//Now they are almost ready. Just make the newly created blocks readable by the OS.
make_ext4fs /dev/block/mmcblk1p2
make_ext4fs /dev/block/mmcblk1p3
make_ext4fs /dev/block/mmcblk1p4
//Now you get where does the blocks come in the kernel right?
exit
//You've covered up the hardest part. Let's get some coffee and cheeerssss.
PART 3: MODIFYING THE NEW OS
You've left the OS extracted in the "External OS" folder right? It's time to do some magic in it. We're gonna tell the OS to be installed in the blocks we created just like the kernel. But wait, where does the OS know before installing where it should get installed? Well, the answer hides in the updater-script in the folder META-INF > com > google > android. Navigate yourself in it. Open the updater-script file in your favourite editor ( I use notepad++ ) and modify it in the same way as the kernel.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
Leave the /dev/block/bootdevice/by-name/boot as it's the fundamental block and we can't replicate it. Don't think for the /cache partition as we've already done that in the boot.img file. Now navigate to the root of the folder where you extracted the External OS. Select all files, add them to a zip file using WinRAR. Name the file to newOS.zip. Open newOs.zip and originalExternalOS.zip with WinRAR and compare them if you find any change in the folder tree. They must and they should be exactly the same. You're 80% done.
PART 4: MODIFYING THE RECOVERY
We often flash many zips including very popular Xposed and other mods to our OS right? They also look for the /system partition. So what are we gonna do? Modifying each of them? Nah. Let's modify where they get which one the /system is. The recovery. Extract the img of the recovery you're using with the same bootimg.exe. Modify exactly the same things. I.e.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
in the following files : initrd/fstab.qcom
initrd/etc/recovery.fstab
initrd/etc/twrp.fstab(For TWRP only)
Save them. Repack. And you got your recovery-new.img and recovery-old.img. Put recovery-new.img and newOS.zip in the same folder. Now wake up, it's time for some action.
PART 5 : INSTALLING THE OS
Open cmd in the folder where newOS.zip resides. Reboot the devixe in fastboot mode. Type the following commands:
Code:
adb push newOS.zip external_sd
fastboot flash recovery recovery-new.img
fastboot boot recovery
Now your device should boot up in recovery mode. To check if everything has gone fine mount system using TWRP. Use twrp's built in file manager and navigate to system folder. It's empty? Yup. You've done a great job. Now flash the newOS.zip using TWRP and your device should boot up in the new OS. To cross check again remove the SD card and try to boot. If you're headed towards recovery or bootloop after that then it's a win. Put the SD card back again and watch the new OS to boot.
PART 6: SWITCHING BETWEEN THE TWO
Extract the boot.img from the "Internal OS" zip file and put it together with recovery-old.img. To check if your old system is untouched type the following commands in fastboot mode:
Code:
fastboot flash recovery recovery-old.img
fastboot flash boot boot.img
fastboot boot system
Your device should take you back to the old one. Surprised? Now let's make a switch between the two. There are two methods.
METHOD 1: USING FLASHIFY
Create two folders in your SD card. Put boot.img and recovery-old.img to one and boot-new.img and recovery-new.img to the other. To switch to the external OS, just flash boot-new.img as boot and recovery-new.img using flashify. Ignore reboot now dialog and reboot directly to the system. To go back, first install flashify in the new OS and flash boot.img and recovery-old.img. Easy right?
METHOD 2: USING ZIPS
I'm gonna tell you that tomorrow as I can write no more today.
More to come....
CREDITS:
justzzshadz from MIUI forum for this revolutionary concept. @iamsubhranil for adding TWRP support and rewriting the tutorial.
Unnecessary
Continuation2
........
reserved
For future posts.
reserved
For future posts
"External" is spelled wrong in the title.
God of War™ said:
"External" is spelled wrong in the title.
Click to expand...
Click to collapse
If you read the whole tutorial, then that just doesn't matter
God of War™ said:
"External" is spelled wrong in the title.
Click to expand...
Click to collapse
Have you tried it?
bootimg.exe
"bootimg.exe on any other OS. If you know, then let me)."
please, send bootimg.exe
tim241 said:
Thanks!!
Click to expand...
Click to collapse
Why you quoted the whole post only to say thanks? That thank you button under the post isn't enough?
tim241 said:
Thanks!!
Click to expand...
Click to collapse
Tried?
fstab not found there is a file named fstab.qcom??????
keerten said:
fstab not found there is a file named fstab.qcom??????
Click to expand...
Click to collapse
Try MultiROM man
iamsubhranil said:
Try MultiROM man
Click to expand...
Click to collapse
Ok Bro
iamsubhranil said:
Try MultiROM man
Click to expand...
Click to collapse
Bro, you are working on EFIDROID. Can you give us update that project
abhianand123 said:
Bro, you are working on EFIDROID. Can you give us update that project
Click to expand...
Click to collapse
I've already told it to some people. The project is currently stun for some complications. Will resume.
Pretty useful. Thanks a lot.
Am I right, that when the memory chip on the motheboard holding /system and /userdata partitions died, I can boot the phone from sdcard using this method? I have HM2014813 variant of Redmi 2.
EDIT: I tried this method but I need to use fastboot boot modified.img to boot my phone. Any ideas how to avoid this step?
tulen_kobi said:
Am I right, that when the memory chip on the motheboard holding /system and /userdata partitions died, I can boot the phone from sdcard using this method? I have HM2014813 variant of Redmi 2.
EDIT: I tried this method but I need to use fastboot boot modified.img to boot my phone. Any ideas how to avoid this step?
Click to expand...
Click to collapse
I too have same problem 0 mb internal stoarage
/sbin/sh: parted: not found
---------- Post added at 03:49 PM ---------- Previous post was at 03:43 PM ----------
warrenlobo said:
I too have same problem 0 mb internal stoarage
/sbin/sh: parted: not found
Click to expand...
Click to collapse
they are missing i guess
warrenlobo said:
I too have same problem 0 mb internal stoarage
/sbin/sh: parted: not found
---------- Post added at 03:49 PM ---------- Previous post was at 03:43 PM ----------
they are missing i guess
Click to expand...
Click to collapse
There is no parted on the device anymore, you need to preparation your sdcard on your computer. Do you use Windows or Linux on your pc?
If Windows try to use: FWUL to partition your sdcard.
Move dalvik-cache to /cache
import /disclaimer.md
Code:
I am not responsible for any damage done to your device/SD card/OTG cable/washing machine etc.
You are responsible for what you do.
If something brakes, it's on you!
This has only been tested on a CM13-based ROM. I have no idea how it will function on other ROMs because of the size of the dalvik-cache directory.
I have found that, on CM13-based ROMs, the dalvik-cache directory is small enough to fit in the /cache partition, giving us several MBs on /data
Current state: Beta
Reason: Not fully tested (on all ROMs)
Comment: Stable enough for daily use
Installation:
Busybox required!
Download the attached zip and flash it in recovery.
Or extract the script from the zip, put it in /system/etc/init.d/ , set the permissions to 755 (rwxr-xr-x) and ownership to 0, 2000 (root, shell).
Uninstallation:
Delete /system/etc/init.d/10dc-linker and /cache/dalvik-cache
To-Do:
Add a size checker
Make suggestions
Bugs:
Found one? Let me know!
Changelog:
v1.0:
First release
Reserved
Didn't work for me on CM13 Xperia SP.
kkumar326 said:
Didn't work for me on CM13 Xperia SP.
Click to expand...
Click to collapse
How much space do you have on /cache?
Also, what exactly is not working?
What is the state of SELinux?
Complete Data
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
kkumar326 said:
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
Click to expand...
Click to collapse
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
When I flashed it, google-play-services fc like crazy until I restore a backup
Miasaya said:
When I flashed it, google-play-services fc like crazy until I restore a backup
Click to expand...
Click to collapse
What happens if you flash the zip and wipe dalvik-cache?
Does it still fc?
Didn't work with flash
Vagelis1608 said:
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
Click to expand...
Click to collapse
I flashed zip too but nothing happened. No folder was created or moved.
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
kkumar326 said:
I flashed zip too but nothing happened. No folder was created or moved.
Click to expand...
Click to collapse
Did you wipe dalvik-cache and /cache after flashing?
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Found the Reason
Vagelis1608 said:
Did you wipe dalvik-cache and /cache after flashing?
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Click to expand...
Click to collapse
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
Code:
ln -s /cache/dalvik-cache /data/dalvik-cache
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
kkumar326 said:
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
Click to expand...
Click to collapse
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Vagelis1608 said:
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Click to expand...
Click to collapse
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
kkumar326 said:
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
Click to expand...
Click to collapse
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Script not working
Vagelis1608 said:
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Click to expand...
Click to collapse
Script is not doing anything at all as I told earlier. That's why I did it manually.
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
This is intended to work on a LG G2 Mini, not any other phone.
kkumar326 said:
Script is not doing anything at all as I told earlier. That's why I did it manually.
Click to expand...
Click to collapse
I want the output without it linked.
DISCLAIMER:
I AM NOT RESPONSIBLE FOR YOUR DEVICE OR ANYTHING THAT MIGHT OCCUR WHILE USING THIS TUTORIAL. TRY AT YOUR OWN RISK!
Credits:
[mbm] for teaching me this dd terminal method.
As we all know, for what ever reason, Samsung decided to release the Tab 3 model tablets with 1 GB of ram. I believe this system needs more ram but unfortunately we cannot upgrade the hardware. What we can do is create virtual memory or a "Swap file" that acts like ram to help our Tab 3's out with multitasking and other memory hogging tasks. Below are the steps to:
1. Create a swap file.
2. Create a script file to run at boot from your /system/etc/init.d directory.
3. Create a android system with 1GB of RAM and 1GB of swap file virtual memory.
*Remember whatever device you are using must have a rom with init.d support and be rooted.
STEP 1: TERMINAL COMMANDS PT.1
Download terminal emulator from the play store if you don't already have it.
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Open terminal emulator and execute these commands in order:
1. "su"
2. "cd /system"
3. "mount -o rw,remount /system"
4. "dd if=/dev/zero of=swapfile bs=1m count=600" (be patient, this step takes about a minute)
5. "mkswap swapfile"
6. "chmod 755 swapfile"
STEP 2: INIT.D SWAP FILE TEXT CREATION
Now to create a script to execute at boot every time you boot your phone. I used the app QuickEdit from the play store.
https://play.google.com/store/apps/details?id=com.rhmsoft.edit
Now open that up and put the text below in the file:
"mount -o rw,remount /system
swapon /system/swapfile"
Now save that to your sdcard (/sdcard) as "swap" (remember do not save with the .txt)
STEP 3: TERMINAL COMMANDS PT.2
Now go back into terminal and execute these commands:
1. mv /sdcard/swap /system/etc/init.d
2. chmod 755 /system/etc/init.d/swap
I kept my previous terminal session open but if you closed it for what ever reason you might have to execute "su" and then "mount -o rw,remount /system" before the two commands in step 3.
STEP 4:
Reboot and win. :laugh::good::laugh:
To verify that the process has worked, after reboot, bring up terminal emulator and type "free -m". You should see that swap has more than 600M! This will stick after reboot. If for whatever reason you want to get rid of your swap file just delete the "swapfile" file and the "swap" script. Enjoy!
I'm getting "swap file needs to be a least 40kb" after I "mkswap swapfile"
EDIT:I tied it again now and it seemed to work, for some odd reason
Sent from my SM-N910T using Tapatalk
My swap file reads "399" .... it's not more than 600m. What did I do wrong?
vin_001 said:
My swap file reads "399" .... it's not more than 600m. What did I do wrong?
Click to expand...
Click to collapse
Never mind! I found the solution... when typing "1m" into the command line, the m must be capitalized, "M". If anyone else has this issue, this is where u went wrong! Now I have "999" instead of "399"!
AWSOME. It brought some more life into my lagging P5210 running latest cm13 from Nelson. Cool
Thanks, I can finally use chrome on my tab 3
Is it same to wipe the system partition? , bcuz i want to clean install
Sent from my SM-G7102 using Tapatalk
Devel0per95 said:
Is it same to wipe the system partition? , bcuz i want to clean install
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean, but when you wipe your system folder, you need to make swapfile again.
@ "4." it says: "Read-only file system"
What did I do wrong?
I'm on 13.0-20161121-UNOFFICIAL-santos10wifi
Thanks!
Gesendet von meinem SM-G925F mit Tapatalk
DerLeoLeo said:
@ "4." it says: "Read-only file system"
What did I do wrong?
I'm on 13.0-20161121-UNOFFICIAL-santos10wifi
Thanks!
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
You didn't do number 3 right. That mounts the system read/write
Sent from my SM-N920V using Tapatalk
Thanks! Will try again...
Gesendet von meinem SM-G925F mit Tapatalk
Hi I have still the message...
Any clue?
Thanks a lot
My device is really more usuable with this trick
Added with niels CM custom ROM it is fantastic
Envoyé de mon GT-P5210 en utilisant Tapatalk
I've got to the last step and couldn't move the file as the /system partition is 100% used.
I also notice that the created /system/swap file is only 589M ...
So I guess I could try to use a smaller swap file or clear some /system/** memory? Anyone know the best way to do that? or what i can delete etc?
thanks.
spankycarbowski said:
I've got to the last step and couldn't move the file as the /system partition is 100% used.
I also notice that the created /system/swap file is only 589M ...
So I guess I could try to use a smaller swap file or clear some /system/** memory? Anyone know the best way to do that? or what i can delete etc?
thanks.
Click to expand...
Click to collapse
The last step is where you went wrong, since swap uses space on your system partition. Free up space and redo everything again. You should see 999 ( or more than 600) if you succeeded.
vin_001 said:
The last step is where you went wrong, since swap uses space on your system partition. Free up space and redo everything again. You should see 999 ( or more than 600) if you succeeded.
Click to expand...
Click to collapse
Yes right, I guess I am really asking - what is the best way to clean up the system partition - as i have no idea what i can delete?
spankycarbowski said:
Yes right, I guess I am really asking - what is the best way to clean up the system partition - as i have no idea what i can delete?
Click to expand...
Click to collapse
To free up space in the system partition, try deleting unecessary system apps and bloatware, (I'm guessing you are on stock touchwiz, but it doesn't matter otherwise). You can also find a deodexed rom that you would like. Deodexed roms use less space in your system partition. The last option is to get a download of your rom on a PC and boot into TWRP (3.0.2-0 preferred) and do an advanced wipe as well as your internal storage. Backup everything if needed, then reflash.
Hope any of these helped!
vin_001 said:
To free up space in the system partition, try deleting unecessary system apps and bloatware, (I'm guessing you are on stock touchwiz, but it doesn't matter otherwise). You can also find a deodexed rom that you would like. Deodexed roms use less space in your system partition. The last option is to get a download of your rom on a PC and boot into TWRP (3.0.2-0 preferred) and do an advanced wipe as well as your internal storage. Backup everything if needed, then reflash.
Hope any of these helped!
Click to expand...
Click to collapse
Ahhh. I followed the instructions and installed cm13.0 from nels83 ( https://forum.xda-developers.com/galaxy-tab-3/development-10/rom-cyanogenmod-13-0-t3342017 )
I guess doing this step:
"Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data"
doesn't actually wipe the system partition clean?
spankycarbowski said:
Ahhh. I followed the instructions and installed cm13.0 from nels83 ( https://forum.xda-developers.com/galaxy-tab-3/development-10/rom-cyanogenmod-13-0-t3342017 )
I guess doing this step:
"Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data"
doesn't actually wipe the system partition clean?
Click to expand...
Click to collapse
Ya, that doesn't wipe the tablet clean, wiping all of that and 'internal storage' does the trick. Glad I could help!
I agree with everyone here. This made a big responsiveness change in the tablet. Thank you!