[Q] MCR fr17 Fear Kill Edition is based on ext3 or ext4 - LG Optimus 2x

Hi All,
Sorry for such a noob question but the MCR fr17 Fear Kill edition runs on ext3 or ext4 ?
Also, is there a way to check if its ext3 or ext4? Many thanks in advanced.

You can check with by running mount from a terminal.
Being an MCR based ROM it should be EXT4 though.

T_T Pardon me for being ignorant but I'm very new to the terms used here.
Terminal <-- this meaning? I believe this is an external program run using the computer to SSH into the phone right? Or if I'm wrong, any guides for me to follow or can help to pinpoint to a link where I can learn all this?
Thanks in advanced.

Terminal = https://market.android.com/details?id=jackpal.androidterm
Install it, fire it up and at the prompt just type 'mount'
You'll be greeted with a couple of pages of gibberish, scroll to the top of it, and you'll see system & data mentioned:
Code:
/dev/block/mmcblk0p1 on[B] /system type ext3[/B] (ro,relatime,errors=continue,data=writeback)
/dev/block/mmcblk0p8 on [B]/data type ext3[/B] (rw,nosuid,nodev,noatime,errors=continue,data=writeback)
As you can see, my system is EXT3

Rusty! said:
Terminal = https://market.android.com/details?id=jackpal.androidterm
Install it, fire it up and at the prompt just type 'mount'
You'll be greeted with a couple of pages of gibberish, scroll to the top of it, and you'll see system & data mentioned:
Code:
/dev/block/mmcblk0p1 on[B] /system type ext3[/B] (ro,relatime,errors=continue,data=writeback)
/dev/block/mmcblk0p8 on [B]/data type ext3[/B] (rw,nosuid,nodev,noatime,errors=continue,data=writeback)
As you can see, my system is EXT3
Click to expand...
Click to collapse
Mine says ext4
Using fear 10
Sent from my LG-P990 using XDA App

Related

Problems running a Blur rom on my G1

For the last couple of weeks i'm trying to get a Blur-rom working on my G1, but sadly it's giving me alot of problems.
I mainly tried flashing it from scratch, which means im running the following setup:
Running a class 6, microsd card;
fat32 (7200mb)
ext3 (500mb)
linux-swap (128mb)
Click to expand...
Click to collapse
I also tried the same setup, except i used ext2 instead of ex3.
The problems I have;
After flashing the rom everything works ok. I sign in to motoblur, and set everything up. But after doing a reboot, the problems start. Right after I enter my pincode, and the homescreen starts loading, i'm getting force closes all over. In the end all I see is a blackscreen, and the white taskbar.
Is my setup wrong? If you ppl want more information, I can flash it again, and will try to collect some logs.
Thx in advance.
*bump*
Still having the same problems, also when running the newest blur rom around (Motorola Blur / S-Blur_1.071 - Bluetooth).
Here is more info (my logs)
http://pastebin.com/m1b544f9c
Hopefully somebody can help, since I wanna run this one on my phone badly
FREAKJAM said:
*bump*
Still having the same problems, also when running the newest blur rom around (Motorola Blur / S-Blur_1.071 - Bluetooth).
Here is more info (my logs)
http://pastebin.com/m1b544f9c
Hopefully somebody can help, since I wanna run this one on my phone badly
Click to expand...
Click to collapse
First what kind of phone do you have? G1/MT3G/Hero ?
Next, did you make sure and do a COMPLETE wipe on your phone?
This means erase:
/system/sd/app_s
/system/sd/dalvik-cache
/system/sd/app
/system/sd/app-private
All of /data
You would do that from the Recovery screen. You can't just go into Recovery, then choose Drop to a terminal and then type
Code:
busybox rm -rf /system/sd
That won't work, when you boot into Recovery none of your partitions are mounted. And choosing "Do a data wipe" from the recovery menu DOES NOT erase your /system/sd partition. You need to mount /system/sd before clearing everything off of it.
As far as your partitions are concerned, keep it as ext2 and not ext3. Read the first post in the Blur thread and it explains how your sdcard should be partitioned.
You should also probably run a fsck on your ext2 partition to make sure it's still functional.
Code:
e2fsck -fy /dev/block/mmcblk0p2
And also verify your swap is still good
Code:
mkswap /dev/block/mmcblk0p3
Given the errors you're having it sounds like you did not do a complete wipe as explained in the first thread, or your ext2 partition is corrupt and you just need to run a fsck on it
I installed the rom completely fresh on a G1 (dream), formatted my sdcard and made 3 new partitions using parted on the recovery console.
So basically saying this isn't enough?
reformatting my sd card now and did the following;
mkpartfs primary fat32 0 7200
mkpartfs primary ext2 7200 7700
mkpartfs primary linux-swap 7700-7828
busybox rm -rf /system/sd
e2fsck -fy /dev/block/mmcblk0p2 (no errors)
mkswap /dev/block/mmcblk0p3 (swap information 128mb, so seems good)
Click to expand...
Click to collapse
will flash now, and get back to you when i have more info
FREAKJAM said:
I installed the rom completely fresh on a G1 (dream), formatted my sdcard and made 3 new partitions using parted on the recovery console.
So basically saying this isn't enough?
Click to expand...
Click to collapse
Technically yes that is all you would need, but once again follow the steps I outlined. No need to blow away partitions. I don't know your level of expertise so I don't know if you're doing it correctly. For all I know you could be creating the partitions, then forgetting to format /dev/block/mmcblk0p1 as fat32, or forgetting to format /dev/block/mmcblk0p2 as ext2, or forgetting to mkswap on /dev/block/mmcblk0p3.
Since you are the only one having this issue it basically means you are missing a step somewhere along the way. The ROM does not hate your phone, lol.
Please follow the regular ROM flashing guidelines. After you create the partitions make sure you can manually mount the fat32 partition at /sdcard and the ext3 partition at /system/sd. Also make sure you didn't somehow screw up the phone parititions, IE /dev/block/mtdblock[1-5]
I think I flashed my phone atleast 200x in the last 6 months..
I'm very addicited to flashing, and I setup a hero rom just like that using parted.
I always reformat my sdcard to start "fresh".
Anyways, flashing now
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: SD USD (sd/mmc)
Disk /dev/block/mmcblk0: 8017MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 7200MB 7200MB primary fat32 lba
2 7200MB 7700MB 500MB primary ext2
3 7700MB 7828MB 128MB primary linux-swap(v1)
Click to expand...
Click to collapse
e2fsck -fy /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p2: 11/244320 files (0.0% non-contiguous), 30701/488281 blocks
Click to expand...
Click to collapse
mkswap /dev/block/mmcblk0p3
Setting up swapspace version 1, size = 127995904 bytes
Click to expand...
Click to collapse
FREAKJAM said:
I think I flashed my phone atleast 200x in the last 6 months..
I'm very addicited to flashing, and I setup a hero rom just like that using parted.
I always reformat my sdcard to start "fresh".
Anyways, flashing now
Click to expand...
Click to collapse
K lemme know how that goes. If it crashes like that again do something for me, open up a shell using "adb shell" and do "cat /data/a2sd.log" and tell me what it says
Here is my log, phone is still booting tho, but seems a2sd is done already.
Beginning a2sd at 05:50 06/16/2009
Does post install script exist: No
Does /dev/block/mmcblk0p2 exist: Yes
Running fsck ....
e2fsck 1.41.6 (30-May-2009)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is mounted.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p2: 11/244320 files (0.0% non-contiguous), 30701/488281 blocks
Mounting /system/sd : Ok
Changing owner on /system/sd to app user: Ok
Changing permissions on /system/sd to 771: Ok
Cleaning up any symlinks in /data
Moving apps to SD finally....
Created /system/sd/app
Changed uid/guid to app user on /system/sd/app
Changed permissions to 771 on /system/sd/app
*****CRITICAL / Watch below for errors ******
Moving /data/app: Ok
Deleting /data/app: Ok
Creating symlink to /system/sd/app: Ok
***** CRITICAL DONE ******
Created /system/sd/app-private
Changed uid/guid to app user on /system/sd/app-private
Changed permissions to 771 on /system/sd/app-private
Created /system/sd/dalvik-cache
Changed uid/guid to app user on /system/sd/dalvik-cache
Changed permissions to 771 on /system/sd/dalvik-cache
*****CRITICAL / Watch below for errors ******
***** CRITICAL DONE ******
Mounting dalvik-cache: Ok
Setting owner to app use for /data/dalvik-cache: Ok
Setting permissions to 771 on /data/dalvik-cache: Ok
Finished 05:50 06/16/2009
Click to expand...
Click to collapse
Still splashscreen on my phone atm.. booting takes longer then normal! Waiting for around 5 mins now.. will wait a bit longer
FREAKJAM said:
Here is my log, phone is still booting tho, but seems a2sd is done already.
Still splashscreen on my phone atm.. booting takes longer then normal! Waiting for around 5 mins now.. will wait a bit longer
Click to expand...
Click to collapse
Well what is adb logcat showing? Is it still progressing? Is it throwing errors?
Redid a total new format and flash cuz it was taking pretty long..
here is some stuff from the logcat;
http://pastebin.com/d2fef07f0
still on the splashscreen for some minutes now..
FREAKJAM said:
Redid a total new format and flash cuz it was taking pretty long..
here is some stuff from the logcat;
http://pastebin.com/d2fef07f0
Click to expand...
Click to collapse
The ONLY way to get the errors you got there are from a pre-existing installation on your phone.
#
E/PackageManager( 1714): Package com.arcsoft.mediagallery has no signatures that
#
match those in shared user android.media; ignoring!
Click to expand...
Click to collapse
Your md5sum for the update should be:
62b9b3925e95b70eda1c77e8317dc7a9 S-Blur_1.071-full.zip
If it is not then re-download the update again and try flashing.
Redo a wipe and when you are positive you have wiped, check manually that all the files are gone. Don't re-partition/format. Just do the following from recovery shell
Code:
mount /system/sd
busybox rm -f /system/sd/app_s/*
busybox rm -f /system/sd/dalvik-cache/*
busybox rm -f /system/sd/app/*
busybox rm -f /system/sd/app-private/*
umount /system/sd
mount /data
busybox rm -f /data/app/*
busybox rm -f /data/app_s/*
umount /data
mount /system
busybox rm -f /system/app/*
umount /system
Phewww, then do a flippin flash of the ROM. That should GUARANTEE that you have a clean wipe.
G:\>md5 S-Blur_1.071-full.zip
62B9B3925E95B70EDA1C77E8317DC7A9 S-Blur_1.071-full.zip
Click to expand...
Click to collapse
did the whipe just like u said..
and now flashing again.. pfew
will keep u posted!
thanks for the help so far!
It installed, and I logged in to gmail etc.
after first reboot, again FC all over. This rom really must hate my phone
http://pastebin.com/dc9c4e47
E/AndroidRuntime( 1844): java.lang.NullPointerException
E/AndroidRuntime( 1844): at java.util.Locale.setDefault(Locale.java:855)
did you make it through set up?
can u make it into settings and mess with that?
what blur rom are you flashing? it may be messed up
I can set everything up, all the info bout what rom I am currently trying to flash is found in the 2nd post.
After the first reboot, it's giving all the force closes.
FREAKJAM said:
It installed, and I logged in to gmail etc.
after first reboot, again FC all over. This rom really must hate my phone
http://pastebin.com/dc9c4e47
Click to expand...
Click to collapse
Where are you located? The US/Europe/somewhere else? It's having issues setting your locale. When the setup first comes up, are you selecting US English?
I'm from Holland. I select US English yes, but I vaguely remember that it jumped to Deutsch, and that I can't change it back to English.
Perhaps it won't let me run this rom since i'm from the EU.
FREAKJAM said:
I'm from Holland. I select US English yes, but I vaguely remember that it jumped to Deutsch, and that I can't change it back to English.
Perhaps it won't let me run this rom since i'm from the EU.
Click to expand...
Click to collapse
Hmmm there's a very good chance that it wouldn't work if you chose anything but English. You may need to use a different libril.so since the one in the ROM is for US. Or Motorola might have designated this only for US users as they will have a different device (the Dext ?) for Europe. Basically it's the Cliq but for overseas. Anyways, erase everything again, reflash and this time make sure you select US English and everything else US just in case Motorola is not allowing anyone outside of US. If that doesn't work you might be out of luck.
You would need to unpack the ROM and hack it to work on your device. Kind of how we hack it to work on G1's
I don't have to skills to "hack" system files. I'll try one more time, trying a US setup. Otherwise ill just have to live with it. Thanks for all the help, esp shafty.
So I tried this baby again after playing with Hero Eclair for a while.
The problem is that the setup-language during the first setup keeps jumping back to German. What files do I have to edit to remove the languages I dont need?
Thnx.

Swap

Hi guys. can you please help me on swap. how can i enable it and disable it. and also set it to the amount that i want it. im still a bit new to this and i have also tried to look for a guide but cant find 1. thanks
Rawdi said:
Hi guys. can you please help me on swap. how can i enable it and disable it. and also set it to the amount that i want it. im still a bit new to this and i have also tried to look for a guide but cant find 1. thanks
Click to expand...
Click to collapse
If you are on Kings rom, it may be running already.
Type #free in terminal and see if it shows swap.
Rawdi said:
Hi guys. can you please help me on swap. how can i enable it and disable it. and also set it to the amount that i want it. im still a bit new to this and i have also tried to look for a guide but cant find 1. thanks
Click to expand...
Click to collapse
bbuchacher said:
In Terminal:
echo 30 > /proc/sys/vm/swappiness to change swappiness to 30 replace number with any number 1-100
cat /proc/sys/vm/swappinesss to see a current level
Click to expand...
Click to collapse
bbuchacher, just wrote it
thanks but the rom that im using is not using swap. how to i setup swap? can i push a user file?
Rawdi said:
thanks but the rom that im using is not using swap. how to i setup swap? can i push a user file?
Click to expand...
Click to collapse
It definitely depends on the rom. Some King roms he has a script you run. Other roms, all you do is go to Spare Parts and set what you want. It may be best to ask in the thread for that rom.
I remembered using this when I used CM:
http://forum.xda-developers.com/showthread.php?t=581328&highlight=swap
Enable swap
I used the method to enable swap in Linux on this and it worked fine on Cyanogen and Super-D.
I used Amon_RA Recovery 1.52 to partition my SDCARD and the new recovery lets you choose the size of your partitions.
so I created a 256MB Swap.
from a console/terminal do the following after creating your swap partition the size you want it:
1. mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (makes system dir writable)
2. mkswap /dev/block/mmcblk0p3 (formats the swap partition on SD with swap format)
3. vi /system/etc/init.d/05userinit (make a new line at the bottom and add "swapon -a" with out the quotes this forced the swap to mount on boot if it is disabled in a kernel)
4. vi /system/etc/fstab (add a line that says "/dev/block/mmcblk0p3 swap swap" with out the quotes)
5. reboot
Hope you know how to use vi editor If not google it. "I" is insert mode and push track ball and hit 1 at the same time and that will esc you to command mode, in command mode do a :wq! and hit enter and that will save the file.
This works on all roms i have run into and no matter what others say it does help the performance.
I can make it easier (short of putting this in a script). Type each line in order and hit enter after each.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkswap /dev/block/mmcblk0p3
echo "swapon -a" >> /system/etc/init.d/05userinit
echo "/dev/block/mmcblk0p3 swap swap" >> /system/etc/fstab
reboot
TGA_Gunnman
The UNIX Dude

[Q] Unable to Chmod my galaxy tab. SGH-T849

Hi,
I get through this with my eye's closed but when I have to type in the chmod line,and hit enter, it says, "unable to chmod : / Read-Only file system / I've asked this on many different forms, and researched it and tried a lot of code to fix it, none of witch worked, so now I'm just asking strait out if anyone knows how I can fix this, It's done this on 2 separate computers so It's doubtful that it's a PC problem.
Thanks for reading this and perhaps helping me, I'm about to rip my hair out, lol,
Kn0t
Wait what?
So it's rooted tab yeah and your? Terminal or abd? Into the system. So you have super user rights huh? And the system files are mounted as read/write? If you said yes to these questioned which I assume you will as it sounds like you are savvy with permissions and how android mounts its system files from the "eyes closed" part then its a new one on me, I have never heard of this problem?
Oh and what kernel you running? is it gingerbread or froyo?
Sent from my GT-P1000
Don't forget to grant superuser its permissions. Check if the app is asking for it. Perform adb with tab on, superuser will pop up.
I felt for that couple of times.
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
speldenaar said:
Don't forget to grant superuser its permissions. Check if the app is asking for it.
I felt for that couple of times.
Click to expand...
Click to collapse
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
And lastly I'm thinking this doesn't qualify to be in the development section bud .. its a little cause and general and should be in General section not Here.
Sorry but its out of control on these boards.... these threads shouldn't be in the development section unless you are developing something or are replying to a development thread about, well.... a development ... or finally, ahhhhh....ummm, bah... development... just had to say it one more time and couldn't get a third reason... I don't want to be harsh or you think I'm flaming you its just my 2 cents....
Sent from my GT-P1000
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
it's adb,, and I have super permissions, yes and it says it's a Read-only file system when I go to write my chmod. The "eye's closed" part of my post was just me being sarcastic about the amount of phones I've done this too and the amount of time I've done it with zero problems.. that's all.
Yup, I did that.. thanks a lot for the advice..!!
nobleskill said:
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
Click to expand...
Click to collapse
Yes I agree but I don't know how to fix it that way.. thanks for helping
Sorry man. It was supposed to be moved to Q and A some time ago and it just never happened. My fault, my mistake. sorry to all that this bothers, and thank you to all that are helping me out.
~k~
nobleskill said:
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
Click to expand...
Click to collapse
Thanks a lot for this advice, I tried it and got a message that says, "System permissions cannot be changed because the file system is Read-only"
Thanks again, it was worth a try.
~K~
quick question....
When do I enter that into my command prompt? right before I try to chmod or right after????
thanks a lot
~K~
mchampeli said:
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
Click to expand...
Click to collapse
I think you have to put on a new rom that does that. try http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
good luck
~K~
GldRush98 said:
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Yea I tried that and it said "system permission cannot be changed becausethe file system is Read-Only" so I don' know. But I do really appriciate you trying to help me out.
knotrkr said:
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Click to expand...
Click to collapse
Whoops, I thought the file you were chmod'ing was in the system partition.
The data partition is already mounted with read/write.
Your chmod command is incorrect... there is an extra space in there.
It should be:
chmod 755 /data/local/bin/flash_image
I don't think the data partition is mounted as read only (I could be wrong, but I didn't think it was)

[Q] how to set up Android as a primary booting os

So the question is:
how to set up Android as a primary booting os?
There is a solution, maybe somebody can share ?
Thanks!
Android is normally the OS that boots by default when you first install it, but if it is not on yours I guess you could try this method (in reverse, since it is a guide to boot webOS by default):
http://forum.xda-developers.com/showthread.php?t=1435318
Or if you have preware on webOS, install an app called CyBoot and its super easy to change.
ANtiHazarD said:
So the question is:
how to set up Android as a primary booting os?
There is a solution, maybe somebody can share ?
Thanks!
Click to expand...
Click to collapse
Do the following from terminal emulator app or adb:
su -
mount -o rw,remount /
mkdir /boot
mount /dev/block/mmcblk0p13 /boot
echo "Cyanogenmod" > /boot/moboot.default
install cyboot from webos and make android default. now, if android goes to a boot loop for some reason, u are stuck in android unless you know how to fix it. you'll have to weigh your options.

How to swap internal to external sd card in Android 4.3

I think a huge number of users will be helped greatly if there will be a guide to swap internal sd card to a larger external.
In 4.2 versions and before, the process was fairly easy in Note, with the use of root explorer and just changing some values in vold.fstab file.
In 4.3 what will be the process and which values you should change?
Sent from my Transformer TF101 using XDA Premium 4 mobile app
That would also be of interest for me. In fact, there ar still no instructions, how to do that (external to internal SD).
there are use the search for crying out loud
Sent from my GT-N7000 using Tapatalk 2
Android 4.3 Swap External With Internal
Since baz is an obvious douche. Here's how you do it (and yes it's posted *somewhere* on the xda threads)
Pull your build.prop from your phone and add the following lines to the bottom: (adb pull /system/build.prop)
Edit the build.prop with Notepad++
If it contains the line remove ro.vold.switchablepair=/emmc,/storage/sdcard0 (or any variant - remove it)
Paste the following at the bottom of the build.prop.
# Switch External With Internal
persist.sys.vold.switchexternal=1
# Storage configuration
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
Save the file, (at command prompt type)
adb root
adb shell mount -o rw,remount /system
adb push build.prop /system
adb reboot
These instructions are obviously not completely in depth and don't hold your hand all the way. You'll need to somewhat know what you're doing.
As always make sure to make a nandroid backup in the rare case that something goes wrong.
help
viiron said:
Since baz is an obvious douche. Here's how you do it (and yes it's posted *somewhere* on the xda threads)
Pull your build.prop from your phone and add the following lines to the bottom: (adb pull /system/build.prop)
Edit the build.prop with Notepad++
If it contains the line remove ro.vold.switchablepair=/emmc,/storage/sdcard0 (or any variant - remove it)
Paste the following at the bottom of the build.prop.
# Switch External With Internal
persist.sys.vold.switchexternal=1
# Storage configuration
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
Save the file, (at command prompt type)
adb root
adb shell mount -o rw,remount /system
adb push build.prop /system
adb reboot
These instructions are obviously not completely in depth and don't hold your hand all the way. You'll need to somewhat know what you're doing.
As always make sure to make a nandroid backup in the rare case that something goes wrong.
Click to expand...
Click to collapse
Can someone explain this a little better I download the app and changed the settings but how do I change the build number
bigevil124 said:
Can someone explain this a little better I download the app and changed the settings but how do I change the build number
Click to expand...
Click to collapse
I dont know which app You're taking about, but You can do it without using adb. Just copy build.prop to Your pc (make a backup copy), edit necessary lines and paste it paste back (and set good permissions).
Sent from d605
Sorry im really a newbie when coming to 4.3 I downloaded the root external 2 sd app and I thought thats where I change these settings. Im not sure down to edit the permissions or build numbers or linesÉ when running 4.1 I flashed a zip and it changed my storage so this is all new to me. Sorry for the hassel but your help is much appreciated
Hi all!
That's the trick i'm looking for! I have an Archos 45 Helium 4G with Android 4.3. I've just tried to edit my build.prop. I have rebooted the phone and..... nothing....
That method is OK with all android 4.3 devices or just for the Samsung Galaxy Note GT-N7000?
Also i've got that on my build.prop
Code:
# system prop for storage test
ro.external.sd.path=/storage/sdcard1
Maybe i have to change that one... but i don't know...
or maybe the solution is in the fstab.qcom but i'm afraid to touch that one.... and there are other fstab files, so i don't know which one is used....
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,check,encryptable=footer
/devices/msm_sdcc.1/mmc_host /storage/sdcard0 vfat nosuid,nodev wait,voldmanaged=internal_sdcard:25
/devices/msm_sdcc.2/mmc_host /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=external_sdcard:auto
#/dev/block/mmcblk0p11 /system ext4 ro,barrier=1 wait
#/dev/block/mmcblk0p12 /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc wait,check,encryptable=footer
or the last thing i know is "the ADB method" > techgage.com/article/moving_your_non-movable_android_apps_to_an_sd_card/
but it seems a not working all the time... I'm also a bit afraid to completely mess up that new phone i don't really know in depth for now.....
Some advices???
try this:
Before
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=0
After
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=1
if it dont work you have to edit the void fstab:
http://forum.xda-developers.com/showthread.php?t=2229848
btw: forum search is the box on the upper right

Categories

Resources