Related
Does anyone have a link to a guide/tutorial about converting ext3 partitions to ext4? Now that we have a CWM image that supports ext4 and several ext4 kernels, it would be really nice if someone could also explain how to convert Android partitions (specifically the ones on the G2X) from ext3 to ext4. Thanks in advance!
baldwinguy77 said:
Does anyone have a link to a guide/tutorial about converting ext3 partitions to ext4? Now that we have a CWM image that supports ext4 and several ext4 kernels, it would be really nice if someone could also explain how to convert Android partitions (specifically the ones on the G2X) from ext3 to ext4. Thanks in advance!
Click to expand...
Click to collapse
When you use a kernel or ROM that uses ext 4 it will automatically convert it. If you nandroid back to a ROM that uses ext 3 it will convert it back.
CrazyCharlie said:
When you use a kernel or ROM that uses ext 4 it will automatically convert it. If you nandroid back to a ROM that uses ext 3 it will convert it back.
Click to expand...
Click to collapse
Hmmm okay thank you! I'm just curious though...isn't there some kind of script or executable that can be used through the terminal to manually convert them? I believe I heard that one version is included in CyanogenMod and that there's also a version on desktop versions of Linux.
baldwinguy77 said:
Hmmm okay thank you! I'm just curious though...isn't there some kind of script or executable that can be used through the terminal to manually convert them? I believe I heard that one version is included in CyanogenMod and that there's also a version on desktop versions of Linux.
Click to expand...
Click to collapse
That would be a bit outside my technical know how. Maybe somebody better versed in Linux could chime in here. Anybody?
I didn't find a guide, but I tried this and it seems to be working.
flash ext4 recovery using nvflash: http://forum.xda-developers.com/showthread.php?t=1086687
in recovery flash normal cm7 nightly, gapps, and an ext4 kernel from: http://forum.xda-developers.com/showthread.php?t=1073626
run the following commands from adb shell:
Code:
umount /cache
umount /data
umount /system
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p1
/sbin/e2fsck -p /dev/block/mmcblk0p1
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
/sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p7
/sbin/e2fsck -p /dev/block/mmcblk0p7
then reboot and it should work... at least it seems to be working for me
sainth said:
I didn't find a guide, but I tried this and it seems to be working.
flash ext4 recovery using nvflash: http://forum.xda-developers.com/showthread.php?t=1086687
in recovery flash normal cm7 nightly, gapps, and an ext4 kernel from: http://forum.xda-developers.com/showthread.php?t=1073626
run the following commands from adb shell:
Code:
umount /cache
umount /data
umount /system
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p1
/sbin/e2fsck -p /dev/block/mmcblk0p1
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
/sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p7
/sbin/e2fsck -p /dev/block/mmcblk0p7
then reboot and it should work... at least it seems to be working for me
Click to expand...
Click to collapse
Awesome! Thank you very much!
To go with this post, does anyone know the commands for converting partitions back to EXT3? Thanks!
well if u just re flash the nightly ur using it will be ext3. cm isnt ext4 setup yet so pretty much all the roms rite now are ext3 so if u just flash the nightly or rom over what u have u will be fine it will install kernel too all u have to do is wipe cache then dalvik n flash rite on top n ur golden
now if u want the trinity kernel or faux kernel there ext 4 when u flash those kernels it converts everything to ext4 so dnt flash those if u wanna stay ext3 ext4 is faster tho y ext3?
sarni84 said:
now if u want the trinity kernel or faux kernel there ext 4 when u flash those kernels it converts everything to ext4 so dnt flash those if u wanna stay ext3 ext4 is faster tho y ext3?
Click to expand...
Click to collapse
Oh okay thanks a lot for your response! And to answer your question, in order to have EXT4, you have to use a custom kernel (clearly -- CM doesn't support it yet). Anyway, the CM kernel is updated with every nightly whereas the custom kernels aren't necessarily updated each time. So if you want to have the most recent fixes, etc. the CM kernel is the way to go (in my opinion).
Thanks that cleared my confusion....
do roms, such as CM7 come with there own kernals? (im a noob)
lbpiscool said:
Thanks that cleared my confusion....
do roms, such as CM7 come with there own kernals? (im a noob)
Click to expand...
Click to collapse
Read the post above yours......... most rims do have their own kernel......
Sent from my LG-P999 using Tapatalk
Here's the scenario: say you try out encryption on a ROM, either because your employer makes you or because you want the extra security. What happens when you can root your phone, like we can (easily) with the S3, and you want to flash a different ROM? The problem you will find yourself in very quickly is that you cannot do a successful wipe. You can't format an encrypted /data in CWM or any other recovery. If you cannot format /data, you can't flash a ROM - it fails, because /data is encrypted, and it cannot proceed. It turns out none of the recoveries can format an encrypted /data. You also cannot reverse encryption once you've done it. You're stuck, all because you flipped the switch on encryption.
I found myself in this problem as others have in many other forums (like this one for the GNex) (and another one, more detailed).
I also tried, admittedly somewhat out of desperation, the soft-brick instructions here. That didn't work because Nand Erase All fails. You can flash on top, and luckily you can use your same password to decrypt your /data (which I did) but you're still not going to have a clean ROM. Dirty flashes = lots of problems down the road.
I finally found a simple way to do this and wanted to save anyone else the trouble of digging. You can do it using CWM and adb and a few commands. Credit goes Shawn Webb's blog and utkanos on FreeNode's irc at #cyanogenmod.
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Thanks for this. I fell into the same scenario yesterday but after reading a lot of helpful posts from people like yourself I have managed to solve the issue. Basically I found two ways of doing it, one is as you have suggested and the other is by just replacing the custom recovery with the stock recovery. The SGS3 toolkit available on XDA made the 2nd option just slightly simpler for me and by spending less than 10 mins (excluding time for backups and downloads) the issue was resolved.
Just to share this option to save others from the headache of looking for a solution:
1) Get the toolkit
2) Install drivers as recommended and follow instructions to choose the build, or closest build, for your S3
3) Restore stock recovery with toolkit via ODIN (follow instructions)
4) After rebooting, go into Android and reset to factory settings, this would bring you to the stock recovery and wipe
5) Restore custom recovery with toolkit via ODIN (follow instructions)
6) Restore your system (luckily for me I had a nandroid backup before I encrypted)
Note: I did "lose" my internal sdcard files (pictures/documents). But I backed that up on my external sdcard before starting the process. My sdcard was not encrypted.
kitleon said:
Thanks for this. I fell into the same scenario yesterday but after reading a lot of helpful posts from people like yourself I have managed to solve the issue. Basically I found two ways of doing it, one is as you have suggested and the other is by just replacing the custom recovery with the stock recovery. The SGS3 toolkit available on XDA made the 2nd option just slightly simpler for me and by spending less than 10 mins (excluding time for backups and downloads) the issue was resolved.
Just to share this option to save others from the headache of looking for a solution:
1) Get the toolkit
2) Install drivers as recommended and follow instructions to choose the build, or closest build, for your S3
3) Restore stock recovery with toolkit via ODIN (follow instructions)
4) After rebooting, go into Android and reset to factory settings, this would bring you to the stock recovery and wipe
5) Restore custom recovery with toolkit via ODIN (follow instructions)
6) Restore your system (luckily for me I had a nandroid backup before I encrypted)
Note: I did "lose" my internal sdcard files (pictures/documents). But I backed that up on my external sdcard before starting the process. My sdcard was not encrypted.
Click to expand...
Click to collapse
You just saved my month. Drop me a message if I can get you a beer via paypal for this.
Cheers!
THANKS!
olm3ca said:
Here's the scenario: say you try out encryption on a ROM, either because your employer makes you or because you want the extra security. What happens when you can root your phone, like we can (easily) with the S3, and you want to flash a different ROM? The problem you will find yourself in very quickly is that you cannot do a successful wipe. You can't format an encrypted /data in CWM or any other recovery. If you cannot format /data, you can't flash a ROM - it fails, because /data is encrypted, and it cannot proceed. It turns out none of the recoveries can format an encrypted /data. You also cannot reverse encryption once you've done it. You're stuck, all because you flipped the switch on encryption.
I found myself in this problem as others have in many other forums (like this one for the GNex) (and another one, more detailed).
I also tried, admittedly somewhat out of desperation, the soft-brick instructions here. That didn't work because Nand Erase All fails. You can flash on top, and luckily you can use your same password to decrypt your /data (which I did) but you're still not going to have a clean ROM. Dirty flashes = lots of problems down the road.
I finally found a simple way to do this and wanted to save anyone else the trouble of digging. You can do it using CWM and adb and a few commands. Credit goes Shawn Webb's blog and utkanos on FreeNode's irc at #cyanogenmod.
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Click to expand...
Click to collapse
Just wanted to say thanks very much for this. I'd tried the method of reloading the stock ROM as described by a previous poster, but this way worked.
I did run into a small issue I was wondering if you could shed some light on. When I entered "mount /data", I got the following:
Code:
~ # mount /data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
I bullied ahead and entered the last line "mount /dev/block/mmcblk1p1 /data/media" and got this:
Code:
~ # mount /dev/block/mmcblk1p1 /data/media
mount: mounting /dev/block/mmcblk1p1 on /data/media failed: No such file or directory
However after doing this, I was able to perform a complete wipe of /data using CWM and load a new ROM without issue.
I'd curious to know what might be causing these Invald argument responses.
My Device: HTC One (GSM)
Thanks again! :laugh:
olm3ca said:
Here is how to do this on our Verizon S3:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p15
mount /data
mount /dev/block/mmcblk1p1 /data/media
If adb doesn't work in CWM, reboot recovery. You might need to create /data/media after mounting /data in order to do the last step, which I opted not to do. I hope this saves someone else a few hours of frustration, and I also hope that someday one of our recoveries can handle formatting encrypted data. Until then... I'm just not using encryption, period. There already is a lot of documentation against it, and this is one more reason in my book.
Click to expand...
Click to collapse
I'm trying to follow your instructions but fail at finding out my mount points.
Sorry for the noob question, but who do I find out what the mount points of internal and external SD card are on my device (Samsung Galaxy S4 Mini International 4G)? I found this post
stackoverflow. /questions/6824463/how-to-get-all-the-mount-point-information-for-android-device
which seems to include the answer but I don't know what tool / software they use. I'm no programmer.
My phone is encrypted and doesn't turn on, it doesn't accept my password saying it's wrong, though I know it's correct. OS is Cyanogenmod 10.1 stable. Booting into CWM v6.0.3.7 is possible though.
I appreciate everyone's help.
Stephan
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
andreas1996 said:
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
Click to expand...
Click to collapse
Only one that can mount it will be twrp 2.7.1.1 (or the f2fs twrp released in dev)
If it has corrupted just format it back to ext4 and start again.
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Sent from my GT-I9505G using XDA Free mobile app
andreas1996 said:
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Click to expand...
Click to collapse
That's not a log, it's a screenshot. The log is in /tmp/recovery.log, so you can use adb pull to get it and post it. Or you can probably use the "copy log to SD card" option in the advanced menu.
Here is the log.I compressed the file because the log format is not supported to attachments.
andreas1996 said:
Here is the log.I compressed the file because the log format is not supported to attachments.
Click to expand...
Click to collapse
According to the log, your recovery can't access any partitions on your eMMC. To find out more, reboot to your recovery again and run on the connected PC:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
and read/post the resulting files.
Here is the two files your commands gave me
andreas1996 said:
Here is the two files your commands gave me
Click to expand...
Click to collapse
Your tablet's eMMC seems to have no partitions at all:
Code:
<6>[ 4.770320] mmcblk0: unknown partition table
What exactly did you do for "a F2FS conversion to Data Partition"? Did you format mmcblk0 instead of mmcblk0p8?
The only thing I did after f2fs conjversion is in Philz recovery I select wipe to install a new ROM.And the problem began.
andreas1996 said:
The only thing I did after f2fs conjversion
Click to expand...
Click to collapse
If you expect help, you need to answer my question. I did not ask what you did *after* the f2fs conversion - what exactly did you do to convert /data to f2fs?
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
andreas1996 said:
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
Click to expand...
Click to collapse
Friend! You got the attention of one of the few people who may be able to help you get your tab back! Use it!
Post DETAILED steps of what you did or _that is going to ignore you!
Which recovery and version thereof did you use?
What did you do afterwards? You mention 3 recoveries. Did you flash all of them?
What did you do in which order in each of them?
Provide as many details as you can!
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
Define "full wipe".
Which CROMi-X version did you try to flash?
Details, details....
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
sbdags said:
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
How would you format data without a data partition?
sbdags said:
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
andreas1996 said:
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
Click to expand...
Click to collapse
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
sbdags said:
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Click to expand...
Click to collapse
When I doing the command (make_ext4fs /dev/block/mmcblk0p8) I receive the message : Need size of file system.
Something seems to be wrong with your GPT. Unfortunately the busybox tools don't support big offsets to read it, so let's first see if the Tegra-specific partition table (which is not used by the kernel) is still there - that won't help you immediately but will show if the eMMC can be read at all and where the partitions are supposed to be. Post the output file of this command:
adb shell hexdump -s 0x300000 -n 2048 -C /dev/block/mmcblk0boot0 > pt.txt
Hi all
I was trying to upgrade from TWRP 2.8.50 to higher whan I got this message...and now I don't know how to fix fhat..;
TWRP gives me access to the mount section. It accepts mounts for System, cache and External SDcard but rejects mount for data.
Any idea welcome to overcome this problem
Thks in advance
solution found googling for it...
zorglub! said:
solution found googling for it...
Click to expand...
Click to collapse
what was the solution?
i have that problem
Follow the instructions:
open terminal in twrp recovery and type :
mke2fs -T ext4 /dev/block/mmcblk0p8
Wait a few minutes and that's it!!!
This solution bring back to life my TF300T!!!
Hello!
Recently I recevied "Encryption Unseccesful" message on my phone. I tried to restore backup, but twrp says: "failed to mount /data". So, internal storage is dead. Found this. But cant find "repartition" menu in the cwm.
Questions is:
1. Do I need older versions of cwm to repartition sdcard? (If you have one, please share )
2. Is there any ways of recovering phone?
Thanks in advance!
no, just go to TWRP, Wipe, Format internal sdcard
sandpox said:
no, just go to TWRP, Wipe, Format internal sdcard
Click to expand...
Click to collapse
tried this, but I think internal storage is corrupted. Is there a way to use sdcard as internal storage?
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
I made 2 partitions on sd:
4gb fat32
4gb ext4
But I cant bind /data to this ext4 partition. Can you help, please?
What i did:
With TWRP's terminal:
Code:
mount -t ext4 /dev/block/mmcblk1p2 /data
- Invalid argument (dunno why)
Code:
ln -s /dev/block/mmcblk1p2 /data
- but on phone boot i receive same "encryption unsuccesful" screen.
Edited /etc/fstab - same result.
Files and mount after reboot turn back to its previous condition.
Also installed stock ROM - same message screen.
[/QUOTE]
I got advice that i must do this things with init.d scripts. How can I do this? Already tried "xda's app2sd scripts" but they works if phone completely boots in OS.
remosam said:
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
Click to expand...
Click to collapse
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
blind_aquila said:
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
Click to expand...
Click to collapse
asked sostk or noname
@blind_aquila
try to flash stock rom with odin