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!
THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
IF YOU DON'T WANT THAT TO HAPPEN, MOVE ALONG, THIS AIN'T FOR YOU!!!
AS WITH ANY FLASHING PROCESS, SOMETHING COULD GO WRONG!!!
NEITHER I NOR XDA SHALL BE HELD RESPONSIBLE FOR ANY DAMAGE
THAT YOU CAUSE BY FLASHING THIS ZIP!!!
Now that's out of the way, let me explain the reasons for this zip's existence.
I personally do not like having things left hanging around on my phone's SDcard
after I flash a new ROM onto it, I usually back up my data and format the card too.
It struck me that due to the nature of having an internal SDcard in the Prime
There most surely be stuff hanging around in there from all the flashing I've done.
I also find that hunting down application folders for apps that I have since deleted
can be rather tiresome as they are not always labelled as expected.
Maybe I'm just lazy, but there you go.
Now you can simply install this Zip and all of your partitions will be fresh and clean.
So that's why this zip was born unto the world.
ONCE AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
BEFORE STARTING, MAKE SURE YOU CAN ACCESS YOUR PRIME THROUGH ADB IN RECOVERY!!!!
INSTRUCTIONS: (THIS GUIDE ASSUMES YOU KNOW HOW TO SETUP AND USE ADB)
1. Download prime-full-wipe.zip to your Prime.
2. Backup everything from your internal SDcard to a location that exists outside of your Prime. USB Hard drive, flash drive or another SDcard.
3. After making certain that your data is safe, reboot your Prime to recovery. (zip will work in both CWM and TWRP)
4. flash the zip.
5. Once complete, you will need to reboot to recovery manually otherwise ADB push will not behave correctly.
6. After a successful reboot to recovery, open up Terminal or Command Prompt.
7. Push a new ROM.zip to your Prime via the command
Code:
adb push /path/to/rom.zip /sdcard/
If "/sdcard/" doesn't work, which sometimes happens use
Code:
adb push path/to/rom.zip /data/media/
for some reason it seems that "/sdcard/" is not seen all the time. So far seems to be a windows issue only.
8. Install your new ROM and enjoy that factory fresh taste.
I hope that these instructions are clear enough. If anyone needs help I or someone else will be happy to assist.
I STRESS AGAIN, THIS ZIP WILL FORMAT YOUR INTERNAL MEMORY CARD ALONG WITH SYSTEM AND CACHE. YOU WILL HAVE NOTHING BUT RECOVERY ON YOUR PRIME!!!
Credits to mero01 for the original idea and Team Virtuous for some sexy code used in the zip file.
KOUSH for CWM and Team Win for TWRP
Big thanks to swiss-prime and anthonyexmouth for being patient men/windows guinea pigs!
Thanks to Nandrew for pointing out that users may need to reflash CWM if experiencing ROM Manager errors after flashing this ZIP!.
UPDATE: 31/05/12
OK, so to anyone that has had problems pushing a new rom to the SD card after using this zip file. I have found some rather odd behaviour that sometimes occurs when formatting the Prime.
After many hours of testing yesterday, I found that when using CWM I simply couldn't push a file to the sdcard no matter whether I was pushing to "/sdcard/" or "/data/media/"
The only way I was able to get a rom onto the sd card was to eventually flash TWRP using fastboot and push the file after booting into TWRP. However after doing so and then getting a rom installed on the Prime, when looking through the file structure with Root explorer I found that the sdcard symlink had not actually been re-created properly, the file was there, but it was not showing as a folder, and as such, I believe that this is where the problem some people are having stems from.
The only solution that I found was to re-flash the full-wipe.zip again in TWRP and then push a rom onto the sdcard again. After successfully getting back into a working rom, I checked out the file structure and the alias had been properly re-created this time.
The behaviour is very weird and there seems to be no rhyme or reason to it. However, if you have had issues pushing to the sd card after using my zip, I can only apologise for your worry.
I hope that the above makes sense and helps people out who feel that they are now up sh*t creak without a paddle.
To be clear I do not believe this to be an issue caused by CWM, I believe it to be a Prime issue.
Update 01/06/12
Nandrew pointed out to me that you will receive non-critical error messages from CWM about a missing log file after using this ZIP. Once you have made a backup, a log file will be created and these error messages will cease.
You may also need to reflash CWM if you experience rom manager errors.
I think I should give it a shot!
john9 said:
I think I should give it a shot!
Click to expand...
Click to collapse
I'm heading out for about 20 minutes, but I'll be around after that. If you run into any issues.
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
paddycr said:
This looks really helpful Dok - thanks! I seem to have accumulated a mass of crap on my SD card and I was wondering what to do with it...
I do have one question (not directly related to your zip). I have all this stuff on my SD card but I don't know which folders contain app user data and what can be safely deleted. Will TiBu restore all necessary user data to /sdcard after using this (obviously after copying the TiBu folder back to /sdcard ) or do I need to figure out what user data I need to keep for each of my apps before I wipe?
Hope that makes sense! Thanks again for this.
Click to expand...
Click to collapse
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
<Edit> Nevermind... I read the whole post!
Doktaphex said:
I haven't used TiBU yet, I made this zip and flashed it last night, then just flashed it again earlier, so I am currently with a Prime with no ROM.
I think though that TiBU should behave as normal, You may need to re-download app data for some of the biggies like games that have a separate download after the install.
Before I flashed it last night, I backed up the entire contents of the card to a USB hard drive, to make certain that I didn't lose anything at all.
Click to expand...
Click to collapse
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
paddycr said:
Thanks. I guess I am just not quite sure how TiBu works. When you do an normal factory reset thru CWM and leave /sdcard intact does TiBu restore a link to app user data located on /sdcard or does it completely rewrite it based on whats in /sdcard/TitaniumBackup/?
Doesn't really matter. I will just back everything up before I use this. I know I need to clean up /sdcard but am a bit chicken to use this
Click to expand...
Click to collapse
Just finished restoring my TiBU and all my apps and relevant data are intact after only copying across the TiBU folder.
Im glad someone finally made this for everyone else. I had once had a problem with my prime that no matter how many times i wiped and reflashed my status bar was not working and when i tried to return to my back up of stock it was giving me read errors restoring the data section and would stop. I had to modify a zip to format what this does and then reflash and then everything worked again. Wiped my tf201 clean but hay it worked again and thats what mattered.
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
acdcking12345 said:
I would love to try this out but I am absolutely too scared of this ADB thing to work on pushing the Zip to the Prime...I figure I will brick it..
Click to expand...
Click to collapse
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Doktaphex said:
What operating system do you use on your computer?
adb is easier on Linux and Mac than on windows.
Click to expand...
Click to collapse
It is windows. :-(
acdcking12345 said:
It is windows. :-(
Click to expand...
Click to collapse
I would have a look at the naked ADB driver thread here very useful for windows users and should help put some of those fears to rest.
Yes and if you follow this guide to install ADB it will be easy:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Yeah, I dont think I am that gutsy to take this risk. But Ill keep researching it. I would like to start fresh as possible..
anthonyexmouth said:
ok, when you say reboot into recovery do you mean "fastboot"
cant find device in adb. using win7 with naked drivers.
Click to expand...
Click to collapse
No I mean exactly as I said. After flashing in recovery, you have to reboot back into recovery. It is a funny quirk that I may need to look into further.
No then, to your problem. Do you have an irc client on your computer? If so, come over to #asus-transformer on freenode irc and we can talk in real time.
If not, then I will endeavour to assist you here.
Gonna take the zip down for a moment until we can sort this out.
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
anthonyexmouth said:
ok, rebooted into recovery and it now sees it in adb. i get a load of E: cant open lines but i guess thats cuz they aint there.
adb push "rom" /sdcard
all looks like its doing it but been stuck there for 20 mins.
leaving it just in case.
Click to expand...
Click to collapse
I assume that you are abbreviating when you say adb push "rom" /sdcard
It should take no more than 3 minutes to push the rom
yeah full path is adb push c:\android\virtuousprime.zip \sdcard
I got a nook tablet recently, i registerested it already which i understand you have to do... now i want to backup everything and run regular android as in not B&N version. Im not sure which way to go from here, i see there is an sd option and a regular option?
i was reading this
http://forum.xda-developers.com/showthread.php?t=1439630
as i was getting ready to do it, i started to double think if it was what i wanted.
i want to be able to run the latest android rom possible.
appreciate any help, thanks.
The process you are linking to is very simple and "safe". With the card you create you can startup CWM (ClockWorkMod - utility for flashing and backup and more) and not only root your device, but also make a backup, should you want to go back to where you were prior to flashing whwaever you decide to flash.
The rooting alone lets you install apps from other sources than BN. I think rooted stock tweaked a bit isn't too bad to run actually!
To try out other options completely risk free you can run CM10 (ICS) from an sd card. I do that while I wait for CM10 to be more stable/bug free. It runs incredibly well from sd, and I doubt performance will be greatly enhanced onec I install it internally (as I probably will do at som point.
To run from sd card you don't have to root the device unless you want to.
Great guides for making a sd-card are here and there. For example http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
The first thing I would suggest is to make a bootable recovery SD card using the process and files from here (use the MLO_u-boot_flashing-boot.rar and one of the packages with sdcard.zip suffix), and backup your current stock config and safely save/archive the backup folder -- you'll be glad you have it around one of these days. Make sure that you also keep a copy of whichever recovery program version you choose to use together with the backup folder, since different recovery programs and versions use different backup file archive formats.
If you want to root the NT I would recommend using the update.zip referenced in this post (by liquidzoo) which is more up-to-date than the rooting package you saw (I had used the latter version and had problem updating its Google Store app). Just put this zip package on the same recovery SD card and use the recovery program to install it.
Having tried out the rooted form of the NT for about a week I think it's just marginally better than a stock NT -- there are just so many common apps that are no longer available for the NT's Android version. You would be much better of investing time in going full-fledge CM10, either running off an SD or natively. If you choose to go native CM10 you can revert back to stock using the backup discussed above.
Can you please verify if I am doing the correct thing
@digimax,
I just got my Nook Tablet today, so just wanted to be very clear to make the backup of the current stock config. Here's what I propose to do. Please correct me if I am doing anything wrong.
1) As per you post, I downloaded 3 files
a) MLO_u-boot_flashing-boot.rar,
b) CM9-10_CWM_V6.0.1.2_8-16gb_tools_sdcard.zip,
c) CM9-10_TWRP_v2.2.2.0_8-16gb_tools_sdcard.zip
2) Unzip all the above 3 files
3) Rename the CWM file to recovery.img
4) Rename the TWRP file to altboot.img
5) Copy recovery.img and altboot.img and MLO, flashing_boot.img and u-boot.bin to the root of the SDCard.
6) Insert the SDCard into the Nook Tablet and boot the Nook into one of the recovery and make a backup.
Please let me know if this is the correct procedure.
Thanks!
It looks right, make sure that your boot partition is Primary FAT32 (type 0x0C) with LBA and Active flags set (you can check and set all this using a partition management tool such as MiniToolPartition).
Also, to boot into SD: just turn off the NT and insert a powered-USB cable, and the NT will boot up after a few seconds (assuming that the SD is bootable).
Once CyanoBoot comes up, hold the "N" button to get the boot menu from which you can select one of the two recovery programs.
a lot of this is going way over my head, i need to make sure i go slow and read carefully.
thanks for all the info.
Snjperman said:
a lot of this is going way over my head, i need to make sure i go slow and read carefully.
.
Click to expand...
Click to collapse
Remember that you can make CM10 run totally risk free from am SD-card. That way you can have a smooth running device to explore while you keep reading up on diffrent options. That's what I do! The Tablet doesn't even have to be rooted to do this (mine is though).
asawi said:
Remember that you can make CM10 run totally risk free from am SD-card. That way you can have a smooth running device to explore while you keep reading up on diffrent options. That's what I do! The Tablet doesn't even have to be rooted to do this (mine is though).
Click to expand...
Click to collapse
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Snjperman said:
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Click to expand...
Click to collapse
This is the website I used:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Look through the comment sections for further clarity on the process.
If that is beyond you, then I suggest getting a pre-made image for the size of SDCard you have and burning your own image. Google AndroidforNook or N2A for the website links.
Snjperman said:
thats exactly what i want to do, can you link me to the tut you used?
thanks!
Click to expand...
Click to collapse
To install and run CM10 off SD card: http://forum.xda-developers.com/showpost.php?p=35245689&postcount=7
To install and run CM10 internally on NT: http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
attiato year
thank you guys so much!
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
No Luck So Far
Been working for hours trying to figure this one out. Things to note is that now there are two mount points.
1) /mnt/media_rw/sdcard1 / sdcard0 (this has the actual /dev/block/vold/179:1 origin
2) /dev/fuse /storage/sdcard1 / sdcard 0
I've been unsuccessful trying any of the old build.prop tweaks. Hopefully someone smarter will come along and bang this one out.
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
I've asked the compiler of the NeatKernel if he would fork it and swap out the sdcards in fstab.aries, but have yet to receive a reply....
Perhaps if you two went and posted the same, it might motivate him to do so.
Me too
alkspo said:
Bump..... Stuck on 4.3 till a solution arises
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You got Company!
vivin007 said:
You got Company!
Click to expand...
Click to collapse
Same here! I upgraded to 4.4 and then realised that the build.prop 's changes made in 4.3 doesn't work for 4.4. Downgrading to 4.3 till there is a solution.
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
alkspo said:
Still no "real" solution. but pretty convenient for me.
@fusionjack integrated swap option in the rom i was using which is slimsaber, so now i have swap
unfortunately, its only for this rom unless other rom makers incorporate it as well
Click to expand...
Click to collapse
Good news, so it's not impossible, it's just about time to see the swap method for 4.4 floating around.
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
anatoliy0813 said:
I found an application that allows you to move the data from games to external sdcard, but you have to run the game through the application to play it though. Its called gl to sd, your phone must be rooted though.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know it, but DirectoryBind is better m8. Once it moves and link the data to external you can forget about it.
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
bigevil124 said:
I've been trying to swap the storage on my note 2 on 4.3 can abtobetell me how to do this tried so many methods and nothing works. I would really appreciate some help guys. Thanks in advance
Click to expand...
Click to collapse
Try file, called "fstab.sun6i" in / folder. I keep trying, but all the changes, I made was unstable...If I'll make some progress I'll write it down
Hi im not sure if this helps but someone released a script for cm11 to swap sdcards. Worked fine on resurection for me all I tested.the thread is somewhere in galaxy2 forum I posted to his thread so one of my last replys. I will find the link and edit
http://forum.xda-developers.com/showthread.php?t=2595756
Sent from my GT-I9100 using XDA Premium HD app
swap internal sd to external
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
rictec said:
Hello
did anyone come up to a solution for this or have any info about it?
i want to swap mine too and nothing seems to work on Kitkat
thank you
Click to expand...
Click to collapse
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
tried that but it failed
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
rictec said:
thank you for you reply i already try that had some trouble to flash back the boot and when i manage to do it fstab got ignored
i m currently doing that with a boot script but have to run it every time the table reboots
its not a samsung is a storex A31 based device
Click to expand...
Click to collapse
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
thank you
seb_131 said:
Hi
on kitkat, you should unpack your boot.img file, update the fstab.* files inside, repack it, and flash it.
The way the img file is built depends on your device manufacturer. I did it successfully on my mtk tablet with the tools I found in this forum.
I am pretty sure that unpack/pack tools exist for samsung as well (for example: http://forum.xda-developers.com/galaxy-s3/help/how-to-unpack-split-samsung-boot-img-t1810907 )
Good luck in your search.
Click to expand...
Click to collapse
seb_131 said:
You have to look for the dev kit dedicated to your processor. Have a look there : http://www.slatedroid.com/topic/73913-onda-kitchen-a31-a31s/
I have a mtk based device. I found the tools in this forum. I edited the 3 fstab.* files I found, and then all worked fine.
Click to expand...
Click to collapse
i have those thank you did not wanted to do a entire img just to change some files on boot but it looks like i have to maybe i do some more twicks and be great
Foldermount maybe a good solution
alkspo said:
with the massive overhaul that is kitkat, google changed alot of files, and therefore a new way must be discovered to switch internal/external storages.
The editing vold.fstab option from 4.1-4.2 no longer works as vold.fstab was removed in 4.3, and the editing build.prop method for 4.3 no longer works.
Anyone know how to do it for 4.4?
thanks in advance
Click to expand...
Click to collapse
Before 4.4 I could do it by "Android Internal to External sdcard" app, but this app couldn't do the trick on 4.4 KitKat OS, so "Foldermount" could be a good solution for you. All this app does is make a image of your apps (that you want to) to sdcard. The real files are located in external sdcard and only the clone file ( of max few KB) will residue at internal sdcard. If you are a gamer, this will help you until the real solution arrives.
Good Luck.
There is real solution! Or at least it works for me.
biopsin said:
Since Android 4.2 and the intro of multiusers there is a problem with bind folders across sdcards, making any attempt on mount bind folders as root would result in visible to root only.
Solution is to fool Android with temporary hijack debuggerd to create the mount binds for us. Thanks Chainfire for this workaround!
* Download both files and rename without .txt
* edit debuggerd.mnt to suit your needs (using any other dir then /emulated/legacy/ will result in read only if browsing folders from sdcard0)
* move debuggerd.mnt to /system/bin
* move mount.sh to any place with execute permissions
* execute mount.sh with any preferred method.
cheers!
Click to expand...
Click to collapse
Quoted from http://forum.xda-developers.com/showthread.php?t=2718760.
Thank You biopsin! Thank You Chainfire!
I'm including my files, but 'mount.sh' was not really changed in practical sense.
In case of 'debugger.mnt' it all depends on Your device. You need to check which block for You is internal and which external storage. Just 'mount' command should help.
You can also use it to mount only one folder - like 'obb', which will let You keep applications data on external card.
Just use "mount -o bind /storage/sdcard1/Android /obb /storage/sdcard0/Android/obb" command in debuggerd.mnt file.
You can also have different 'debuggerd.mnt' files (of course called somehow different - like 'debuggerd02.mnt') and different 'mount.sh' files which will let You mount different things whenever You like.
Enjoy!
-----
And for easier usage You can try $cripter - https://play.google.com/store/apps/details?id=sites.mjwhitta.scripter&hl=en .
It's the best I found.
Good afternoon. As the 8 GB aren't enough for me, I've been looking for a solution. While doing so, I found the INT2EXT4 script, which mounts /data on the second partition of the SD card. The first time I flashed it (after enabling init.d support with an app) it didn't work at all. Then, I realised this script is written assuming that the second partition of the card is mmcblk0p2. But on the M4, it's mmcblk1p2 (found it out with another app).
I changed those lines on the script, but it didn't work either. I analyzed all the lines, and I can't see where the problem could be. Has anyone tried this, or could somebody help me with this issue? I think it could be really useful for a lot of users.
Another thing: flashing the file through TWRP gave me an error, so I copied the file directly to /system/etc/init.d and set the permissions manually. I hope this is not a problem, but let me know if it could be...
sounds interesting... ill take a look at it soon!
Have you checked the "adress" of internal sd? In the script there is a connection between internal and external storage so i would assume that both "adresses" need to be correct in order for the script to work. Just an opinion....
Sent from my SM-G901F using XDA Free mobile app
vader20 said:
Have you checked the "adress" of internal sd? In the script there is a connection between internal and external storage so i would assume that both "adresses" need to be correct in order for the script to work. Just an opinion....
Sent from my SM-G901F using XDA Free mobile app
Click to expand...
Click to collapse
several1989 said:
sounds interesting... ill take a look at it soon!
Click to expand...
Click to collapse
I think there's a problem with the commands that the script uses. If I try to do umount from the terminal, nothing happens. So maybe the script doesn't work in this phone, but if any of you are able to make it do so, let me know. So I think it's better to build the kernel from source, but before that make changes in the fstab file. With that, /data will be mounted at the second partition of the sdcard directly at boot time. Trying to do this now, but I'm facing some difficulties building the kernel. If I make it work, I'll post it
Testé folder Mouth playstore