Related
I bought new SD card i want to wipe my phone completely and install Darkys Rom. I formated my new SD card to ext2 in Ubuntu but my phone didn't recognize the file system. Then i used Clockwork to format my (external) SD card and what i did i formated my internal SD card. I'm completely failed. Can somebody give me step by step tutorial how to format external SD Card to ext2 or ext4. Also i would like to know if i will be able to copy data under windows when the phone is connected through USB.
Thank you
Sorry for my English
Hi! Please tell me why do you want to format your SD card to ext2 or ext4? There is no need for that. Just format it tu FAT and that's it. If you want to apply lagfix then do it under recovery with the lagfix option under advanced features.
Greets from Croatia.
DanXo said:
Hi! Please tell me why do you want to format your SD card to ext2 or ext4? There is no need for that. Just format it tu FAT and that's it. If you want to apply lagfix then do it under recovery with the lagfix option under advanced features.
Greets from Croatia.
Click to expand...
Click to collapse
I would like to have option to transfer bigger files than 4GB.
+1
how do I format my external SD card to ext2? I have Samsung Captivate. I got Cygwin, since I use Windows. Does anyone know what commands to type in cygwin?
I want to put files larger than 4GB on my card as well.
I think this will be useful for a lot of people.
I found a thread http://android.modaco.com/content/h...an-i-bind-mount-e-g-system-sd-xxx-sdcard-xxx/
But I am a noob in Linux, and it would be GREAT to have step by step commands I would have to type in to format my external SD card, while its in the phone, etc
Possible problem I see is that the phone might not recognize external card if its ext2/3/4 . We might have to have small FAT32 partition on there as well? Or may be Froyo has that ability...
I'm looking into doing this myself, in my case so I can use symlinks to copy apps "data" folders (not the "data" partition, but the folders in /mnt/sdcard where apps put different things) onto the larger, external sdcard. It seems like it could be possible, just need to make sure the /etc/fstab file is updated properly, and of course make sure your kernel has the ext2 and/or ext4 modules loaded and running (which you probably will if you have a lagfix installed). I will play with this and post back my results here...
I have been looking for this myself for a while aswell, but on 4 different kernels and CWM v2.5 and CWM v3.0, I couldn't find any option on how to change the ext. SD to Ext4. If anyone knows how to then please post it here!
Sent from my GT-I9000 using XDA Premium App
So, progress report...
Still no success in this matter, although I have learnt a bit today about Android's internal workings. After backing up my system with CWR, I first tried formatting my ext sd card with gparted on my computer. Bad choice... Even though no config files were stored in it as far as I could tell, Android "panicked" and decided to restore all my configs to default, severely crippling my system and making a lot of apps force close when I restarted the phone.
At that point I thought, since it is now broken, might as well play with it So the next thing I tried was formatting my internal sd card (only the vfat partition that gets mounted in /mnt/sdcard) to ext2, but this time using the "busybox mke2fs" command, on the terminal emulator on the phone. This seemed to be successful, and I could read and write to the new ext2 partition, although for some reason, I got the feeling that apps kept resetting their settings (not sure what caused this, didn't really looked into it much). So once that was up and running, I decided to modify the /etc/fstab file, like I would do in a normal linux environment, to automount this partition on boot, as ext2.
At this point I rebooted the phone, but hmm... Android converted the partition back to vfat. Not good. This leads me to believe there must be some kind of "recovery" commands run on startup, in case the system detects the partition is not the default file system, or something along the lines of that. At this point it got kinda late, so I decided to document my progress, restore (which thankfully left my phone the way it was at the beginning of the day) and call it a day.
So, things that I still need to find out:
1) How does the system convert the partition back to vfat on startup and how could I avoid it from doing it? Maybe by having a small vfat partition to fool it into thinking all is good and normal?
2) When I had my partition as ext2, I couldn't see it on my computer when connected via USB (I'm on a linux system so the fs being ext2 is not a problem). Wonder why...
3) If I had a small vfat partition, how would I go about mounting the ext2 partition on the same mount point after the system checks the vfat one? Maybe by binding it? Gotta look into that as well.
4) Finally, have to check why the apps couldn't maintain their settings after a certain amount of time (for example, if I opened terminal emulator and changed the colors, these would stay if I closed and opened the app again right away, but if I closed it for a while, say half an hour, and opened again, it would be back to default...)
I'm on a Galaxy S btw. If anyone has any insight on any of these matters, would be much appreciated!
Any progress? Would really like to use +4 GB files.
morow said:
I would like to have option to transfer bigger files than 4GB.
Click to expand...
Click to collapse
It is immpossible because of hardware limitations of the SD card And often if the file is big it just fail!
Hristov1 said:
It is immpossible because of hardware limitations of the SD card And often if the file is big it just fail!
Click to expand...
Click to collapse
Not true, read the rest of the thread before u post! Its not a hardware limitation, its because Android uses fat32 as filesystem.
hello everyone,
I just wanted to check to make sure that there is no solution for this 4gb limitation with Android yet? I too have been looking for something besides resizing files.
thanks
uki
I have ext2 on my external 32GB SDCard, just formatted it on my PC and put it in the phone, working without any problems. I just watched a full length 720p movie with DTS sound on my phone without having to re-encode the mkv
I'm using CM7.1 on my phone which auto-mounts the SDCard even with ext2. It won't work on stock ROM, but any kernel that has ext2 support should be able to read ext2-formatted cards but they might not auto-mount the sdcard.
On my PC I had to install a ext2 file system driver (google ext2fsd) for Win7 to be able to read the card when attaching the phone to the PC.
Is there a way to force mount my external SD card as read only? I'm fed up of constant loss of music and the lost.dir file going up. I have tried all sort of troubleshooting, this is just an android problem ( I never had an issue with my blackberry ).
I don't use my external SD memory for anything else since the phone has built in 16GB anyways, and was hoping there is a way to lock writes to the external card. I am rooted. Thanks!
You should be able to use root explorer or a pc, and change the properties of your music folder to read only. Root explorer option is under permissions with a long press on the folder, groups needs write unchecked, not sure what a read only sd card will do, might generate errors, not sure. Quick question, did you reformet the card using the cards format option when you moved it out of your blackberry?
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
verkerria said:
You should be able to use root explorer or a pc, and change the properties of your music folder to read only. Root explorer option is under permissions with a long press on the folder, groups needs write unchecked, not sure what a read only sd card will do, might generate errors, not sure. Quick question, did you reformet the card using the cards format option when you moved it out of your blackberry?
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
Click to expand...
Click to collapse
This ^ You could also do it via a command prompt or disk management. Depends on your skill set.
You can't set those properties on an SD Card. I will try to set the read-only checkmark on the filesystem, but it is FAT32 and file permissions aren't very good... I tried using an NTFS filesystem to no avail...
busybox mount -o remount,ro /mnt/sdcard-ext , it could be added to /system/bin/loadpreinstalls.sh for a permanent solution.
Could we just change permissions on the folder we keep music in? That way the phone can still write to the card if needed
I tried running chmod 055 /sdcard-ext/Music but when I check the permission in my file manager nothing has changed
Sent from my rooted xt860
Endroid,
The problem is that the FAT32 filesystem is too basic for anything including file permissions. The filesystem becomes corrupted because it isn't being properly dismounted (for whatever reason), so even if you denied write access to specific files using a different file system, I'm sure the the corruption would still happen.
danifunker said:
Endroid,
The problem is that the FAT32 filesystem is too basic for anything including file permissions. The filesystem becomes corrupted because it isn't being properly dismounted (for whatever reason), so even if you denied write access to specific files using a different file system, I'm sure the the corruption would still happen.
Click to expand...
Click to collapse
So ultimately no matter what I do my music is gonna keep moving to lost.dir. even if I reformat to NFTS
Sent from my rooted xt860
The phone doesn't even read NTFS... It only takes FAT32 as the SDCard. The best option is the one that was outlined by eww245, mounting the card as a read-only to avoid file corruption.
Although I am relieved to see that my device isn't the only one that is experiencing this sort of issue.
has anyone tried remount the sdcard-ext yet. does it work and did it cause any issues?
also will this affect the usb transfer
edit: seem to be getting alot of high CPU usage warnings. gonna try a reboot to see if it will fix, then rerun command
Did a reboot and reran the command. No CPU issues now, however already some files have moved into lost.dir. i have no experience writing/editing scripts. If anybody wants to write a quick script i could set to run on boot that would be appreciated.
Actually someome earlier mentioned to throw that into the loadpreinstall.sh under /system/bin
But there seems to be a caveat. If you plug the phone in through USB when the phone gets unplugged the device will get re-mounted. I'd like to change the properties of the internal mount instead of overwriting it each time. I have done a lot of checking around and found the vold.fstab file but don't really know how it works.
Another point of interest, what kind of MicroSD card are you using? I've got a Lexar 32GB SDHC10 card installed.
Lexar 16GB 4.
Do I just put
Busybox mount -o remount,ro /mnt/sdcard-ext
At the end of the script?
Sent from my rooted xt860
So this may be completely unrelated, but I ran the command Sunday, and my CPU went nuts. Rebooted tried again and all was good. Didn't use my phone much that day. Today(Monday) my phone died in 4 hours! I did notice my CPU seemed busier than normal. Did a bit of twitter websurfing then my phone went in my pocket for use as a music player. I use my phone with headphones everyday for music for 4-5 hours and I still have at least 30-40 battery left. Only got 3 hours of music. Now, is it possible that my music player(poweramp) is trying to write to the card, or someother app/system process is trying to write to the card, and since it can't it keeps trying. Is there a log I can pull on adb to figure this out? Has anyone else tried this and experienced anything similar?
Sorry for the ramble but I wanna get this figured out
Sent from my rooted xt860
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card(EDIT: PS: both partitions should be Primary). Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Edit:
Simplified installation if you do not care for easy accessibility to your orig internal memory:
Use this video tutorial by ashwin123:
The only exceptions are that, you need to partition your card,
and you have to use the file 'mountSdFailSafe.txt' instead of the file in the package mentioned by him.
Nice
Waiting for someone to test it n confirm it successfully works
Still here
N!geR -> E!ch0
NisJ said:
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card. Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Click to expand...
Click to collapse
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
grim_ripper said:
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
Click to expand...
Click to collapse
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
NisJ said:
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
Click to expand...
Click to collapse
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
grim_ripper said:
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
Click to expand...
Click to collapse
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
grim_ripper said:
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
Click to expand...
Click to collapse
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
E!ch0 said:
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
Click to expand...
Click to collapse
Creating a video will take time at least til sat... prob more.
Will see if I can create a simplified install instructions once i reach home.
NisJ said:
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
Click to expand...
Click to collapse
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
grim_ripper said:
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Click to expand...
Click to collapse
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
grim_ripper said:
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
Click to expand...
Click to collapse
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
NisJ said:
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
Click to expand...
Click to collapse
For whatever reason, my /etc folder is actually a link from /system/etc
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
grim_ripper said:
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
Click to expand...
Click to collapse
The apps are behaving funny because you have lost their data as I had warned in the original post.
To fix do either of the foll:
1. reinstall app, and start fresh.
or
2. restore from Titanium backup if you had created...
or
3. copy paste 'Android' folder from sdcard2 if it is created to 'sdcard0'
To remove and revert, just delete the files from int.d, and stop scheduling it in SManger.
Note: to un schedule it from smanager, you first have to remove memory card, un schedule and then put in your memory card (this is coz when phone boots up, it is in standard way, with 8gb internal but, after script is executed SManager looses its data too.
How complicated will it be to make this compatible with 4.2.2?
grim_ripper said:
How complicated will it be to make this compatible with 4.2.2?
Click to expand...
Click to collapse
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
NisJ said:
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
Click to expand...
Click to collapse
I did try but nothing happened, am guessing it has permission issues or something on those lines
grim_ripper said:
I did try but nothing happened, am guessing it has permission issues or something on those lines
Click to expand...
Click to collapse
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
NisJ said:
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
Click to expand...
Click to collapse
on the 4.2.2 update, it doesnt recognize the second partition even if it is formatted to primary and set to active. there r definitely some updates done in that field and plus i cant get the init.d rights on the phone as the test.log file is absent in the data folder..no matter what i do i just cant get it straight with the present procedure. please try it on 4.2 and there r more frequent updates on the nordiac then the local version. so i decided to flash it rather than waiting for ota update
I managed to update my rooted stock 4.1.2 to 4.3 today. After replacing my recovery with stock, the update went off without any problems.
I have hit a wall now however.
When I attempt to access by sdcard from within android, I am getting a small set of empty folders (download, data etc.). I've attempted to download the SuperSU package to multiple locations.
Problem is when I attempt to install superSU from within CWM. In CWM, I see my old sdcard files.
Is there any reason I can't see my existing sdcard files within android?
This is proving most frustrating.
I'm swapped out to TWRP, which shows the same files on the sdcard as I can see within android, so I've been able to obtain root.
I do note that there is still 12GB tied up in "other" files on my system however, so my original sdcard files must be someplace. I just can't seem to locate them.
**********
Update:
I flashed CWM back after getting root in place. CWM is still mounting my old sdcard. So it's still on the device, but I'm thinking it's not being mounted by my rom for some reason.
Looks like I've solved it.
For some reason, 4.3 and TWRP are mounting my old sdcard as /shell/emulated and my new sdcard as /shell/emulated/0
I've heard of similar things happening, but was under the impression that updates from 4.1.2 moved existing sdcard folders into the "0" folder
Regardless, I'm going to just bulk copy and paste my way back to sanity.
Is there a way to change what CWM is mounting as sdcard?
SD360 said:
Looks like I've solved it.
For some reason, 4.3 and TWRP are mounting my old sdcard as /shell/emulated and my new sdcard as /shell/emulated/0
I've heard of similar things happening, but was under the impression that updates from 4.1.2 moved existing sdcard folders into the "0" folder
Regardless, I'm going to just bulk copy and paste my way back to sanity.
Is there a way to change what CWM is mounting as sdcard?
Click to expand...
Click to collapse
you could use a symlink: http://forum.xda-developers.com/showthread.php?t=1991657
Though I think newer versions of the recovery fixed that, but I haven't updated my recovery so I just use the symlink method.
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
PMrjn83 said:
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
Click to expand...
Click to collapse
Have you looked over this guide ? or this ?
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
Thanks. I'll try when I get home to my desktop. For some reason, my laptop does not recognize the phone through adb. It shows "SGH-i897" in device manager with an exclamation mark. And yes, I have tried quite a few drivers, etc... :/
I might need to try this...
http://forum.xda-developers.com/showthread.php?t=1761968
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
PMrjn83 said:
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
Click to expand...
Click to collapse
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
gsstudios said:
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
Click to expand...
Click to collapse
Well, I tried. If it doesn't mount at all, how can you format?