Related
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
e) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) If you are not using a2sd and want to setup swap, please enter the below command in the terminal otherwise continue to step 9.
su
sh /sdcard/fr-patch140.txt sdext
reboot the phone.
9) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 9 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apk
Also there are some apps which I don't prefer, as I don't use android native keyboard, Android browser, POP email, amazon MP3 etc. So I have created a script for my use which has been shared and it can be run from the terminal..
download remove-app-v1.0.txt and store it to root of your sd card. than enter below commands in terminal
su
sh /sdcard/remove-app-v1.0.txt
currently this script will remove below mention apps based on user input.
Amazon MP3, Live Wallpaper picker, CM Wallpapers, POP Email, Android Native Browser, Android Native Onscreen Keyboard, Genie Widget...
Note: - Before removing browser and keyboard please make sure you have a replacement for them.
I do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat, Lbcoder for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
If you like my guide and want to Donate
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
supa2001 said:
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
Click to expand...
Click to collapse
Yes, swap can be there without A2sd..
Do you have Fr-Patch139.txt script or any other version...could you please reboot and so the step 8 again
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
supa2001 said:
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
Click to expand...
Click to collapse
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
G1sanju said:
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
Click to expand...
Click to collapse
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
G1sanju said:
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
d) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 8 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apkI do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
Click to expand...
Click to collapse
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
supa2001 said:
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
Click to expand...
Click to collapse
"danger detected" message is for SPL, It checks for the SPL first and you have danger spl installed.
By default CM6 does not mount ext partition as it does not support a2sd right now. sdext creates a mount point for ext partition. a2sd internally does that but as you are not using a2sd this was not done.
vermaekansh said:
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
Click to expand...
Click to collapse
Thanks, If you use this guide then please provide your feedback and suggestion towards it.
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
supa2001 said:
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
Click to expand...
Click to collapse
In the terminal
sh /sdcard/fr-patch139.txt rev swap
this will turn the swap off.
Watch out...newbie in the room
Okay, you are going to love this.... I'm sorry if this is too long but I hope you can help a newbie trying to learn this stuff!
I am REALLY new to all this, and did a Root and Rom Update as the Unlockr.com videos taught me, to get CM6. And then also added the gapps file because I read a thread that that was needed to get gmail and the market on my phone. Once rebooted, everything worked ok but slow. Then I noticed that my gmail wasn't syncing, and then it started to force close. So I did a wipe and loaded CM5 because I saw on a thread that that was faster for the G1. With all of this, after reading your thread and suggestion, I am wondering...
1. Is CM6 slow for you?
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
3. Should I stick with CM5 or try CM6 following these suggestions??
And big ones.... I wish there was a website somewhere with definitions to all the terms and apps used. Lol.. I Google all of them but don't always find anything that actually describes what they are.
Swap and app2sd were mentioned on the video instructions for loading a new ROM but do they automatically come in the ROM zip files? Because in the video they didn't load them separately. They partition the card "for" them, but don't show installing them. Obviously I assume App2sd is a program to store your apps on your sd card. Is this something that I SHOULD install? Is swap something I should install?
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
I know this is a lot of questions... I decided to ask them all here because they pertain to this thread because I'm wondering if I should do this...
Thanks for any and all answers!
I would assume that you have a G1, and my answer is based on that assumption. If you have different phone let me know.
1. Is CM6 slow for you?
If I don't use a2sd and swap, answer is yes. I install lot of apps, with cutomMTD it works fine in starts but slows down after some time. With a2sd and swap it is worth a try.
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
CM roms does not distribute google apps with the rom as its not legal. So if you want gapps then yes that file has to be flashed. CM6 can be run without gapps, but you won't get gmail, market etc..once you have gmail it should sync automatically.
3. Should I stick with CM5 or try CM6 following these suggestions??
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
G1 was build with a low memory and the way internal memory has been partition todays rom can't fit into it. That's why dangerSPL, but there is a risk involved in installing dangerSPL. If you don't follow the instruction you can brick your phone. CustomMTD is a safe method. This increase the size of data partition so you can install more apps internally. link for that thread is in first post.
a2sd is a way to store apps on sdcard, sdcard needs to be partitioned to support that..step 1 - e in my guide. That's a manual way of doing it. If you have AmanRA recovery then it will have a menu option for that. Most of the rom supports it automatically, so if you have sd card partition then rom will automatically do that.
CM6 does not support a2sd so it has to done in different way. CM5 supports it but in settings - application - a2sd has to be checked on to move your apps to sdcard.
Swap is kind of extra memory to help running the applications. if you run multiple application together then you need swap on CM5 and CM6.
G1sanju said:
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
Click to expand...
Click to collapse
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
vermaekansh said:
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
Click to expand...
Click to collapse
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
G1sanju said:
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
vermaekansh said:
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
Click to expand...
Click to collapse
Roms are personal preferences, I also tried lot of roms before settling on CM... and for CM there are no eta it will be released when it's done...
Sent from my HTC Dream using XDA App
WOW!
THANK YOU!!! You are awesome for going through all of those!
Yes, it is a G1.
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
CM6 is based on froyo, latest version of android...its good and yes speed is comparable. Also CM has added new stuff in it, like fully customizable power bar and other stuff...Full changelog is there in CM6 thread.
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
For CM6 a2sd is through script, instruction is in first post. I have included customMTD also there. So if you follow the guide, you will be having customMTD, a2sd and swap...swap require an partition on your sdcard, if you don't have that partition then it will ask for swap file.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
you can wipe and start over again, first post should be good for you.
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Oh I forgot about the fastboot, fastboot and adb are tool, which give an option to control, flash and do other thing on the phone from PC. The link for setup guide is in first post.
Thanks again!!
Man! You are great! Thanks again for all your help! Now let's see if I can manage to follow your thread and not brick my phone! Lol
Until next time....
[RECOVERY][MOD][9.25.11] Clockwork 5.0.2.3 New wipe & confirm menus. For ALL variants
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
5023-cyan.img
20f1c842ed20ae637ecd4e4874ffd678
5023-green.img
5f24361c962383df5a7855f90eb54faa
NS4G Versions
ns4g-5023-cyan.img
5988836a66f535c4a7d499ee417ee9c5
ns4g-5023-green.img
3d79a7b5b0441ef635081656429b541b
Option for no confirmation at all. Just flash in recovery.
signed-noconfirm.zip
All source is on Github. Feel free to do whatever you want with it. If you make any changes that will work on all devices, send me a pull request! https://github.com/j-r0dd/android_bootable_recovery
Change log:
3/14
- capacitive back button now works properly
3/20
- updated to 3.0.1.9 source
3/22
- reverted back to stock 2.3 recovery kernel
3/24
- update 3.0.2.4 source
- removed "apply update from sdcard" (/sdcard/update.zip)
- recovery killed by pkill now instead of ps & grep (BlaY0)
- versions for i9020 & i9023
3/28
- new wipe menu. see screenshots below
3/29
-put the "no" above the yes in confirm menu
-fixed recovery.fstab so format radio, bootloader & misc no longer show
4/16
-reverted recovery.fstab due to Cyanogen's proper code fix for the mount menu for all phones
-updated to 3.0.2.5 source
5/17
-started fresh with 3.1.0.1 sources
-added color versions
6/4
-removed the home button from toggling menu and added back the function for the capacitive buttons to navigate through menus also
-updated to 3.2.0.0 sources
6/11
-updated to 4.0.0.2 source
8/3
-fixed battery stats confirmation of completion
-updated to 4.0.1.4 source
9/25
-updated to 5.0.2.3 sources
-removed orange. just going to stick with cyan and green.
j_r0dd said:
I just built this from the latest CM7 source. I take no credit for the recovery whatsoever. We all know this is Koush's hard work. Just one thing was driving me personally crazy, the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. see the attached screenshot for my change.
http://www.mediafire.com/?g1od5wzaw604tc2
Click to expand...
Click to collapse
God bless you lol. Nice job, looks and works great.
Very interesting project lol. I like it!
Sent from my Nexus S using XDA Premium App
nice! thanks
Yay!!!!!!!!!!!!!
can not find it on rom manager
this is always fun...
i flashed it in the terminal emulator on the phone. after all those errors, i just typed the script again. it flashed fine the second time
btw, to flash it through the terminal on the phone, put the file on the main part of the sd storage, open the terminal app, then type...
su(press enter)
flash_image recovery /sdcard/3014cw.img(press enter)
reboot recovery(press enter)
i renamed mine cw14 for ease.
simms22 said:
this is always fun...
i flashed it in the terminal emulator on the phone. after all those errors, i just typed the script again. it flashed fine the second time
btw, to flash it through the terminal on the phone, put the file on the main part of the sd storage, open the terminal app, then type...
su(press enter)
flash_image recovery /sdcard/3014cw.img(press enter)
reboot recovery(press enter)
i renamed mine cw14 for ease.
Click to expand...
Click to collapse
flash_image has given me that error recently when flashing boot.img. fastboot never fails me.
Sent from my Nexus S using Tapatalk
can you fix the wipe delvak too?
Sent from my Nexus S using XDA Premium App
LordPhong said:
can you fix the wipe delvak too?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
yea its still broken. ive gotten used to just deleting the files in it manually.
Good idea, nice job. Thx.
LordPhong said:
can you fix the wipe delvak too?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Wipe dalvik has always worked fine for me. What's your issue?
Sent from my Nexus S using Tapatalk
Thanks!
Flashed it trough fastboot, really easy. It's going to save me my volume rocker and thumb.
I didn't knew a new version of CWM was available, until I saw this.
Thanks!
j_r0dd said:
Wipe dalvik has always worked fine for me. What's your issue?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
When you attempt to wipe it'll pop a error like unknown volume /sd-ext/
Sent from my Nexus S using Tapatalk
zephiK said:
When you attempt to wipe it'll pop a error like unknown volume /sd-ext/
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
That will always pop up if there is no ext2/3/4 partition on the sdcard. That is what sd-ext is linked to. Wipe dalvik still works in spite of that error. Just wipe dalvik and see how long it takes to boot. On second thought wipe dalvik and run a logcat while it's booting and you will see it building the dex files.
Sent from my Nexus S using Tapatalk
j_r0dd said:
That will always pop up if there is no ext2/3/4 partition on the sdcard. That is what sd-ext is linked to. Wipe dalvik still works in spite of that error. Just wipe dalvik and see how long it takes to boot. On second thought wipe dalvik and run a logcat while it's booting and you will see it building the dex files.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
It actually doesn't do anything. after getting the error message, the cache is still there.
Sent from my Nexus S using XDA Premium App
LordPhong said:
It actually doesn't do anything. after getting the error message, the cache is still there.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
After the error you have to confirm the dalvik wipe.
Sent from my Nexus S using Tapatalk
j_r0dd said:
After the error you have to confirm the dalvik wipe.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
you're right. I was just going by what people have been saying. So, I finally did a test and used adb to check the before and after wipe. Sure enough, it actually DOES wipe. Sorry to add to the confusion.
Simms - that means you can stop doing it manually. Just wipe from CWM. It DOES work despite what people have been saying.
LordPhong said:
you're right. I was just going by what people have been saying. So, I finally did a test and used adb to check the before and after wipe. Sure enough, it actually DOES wipe. Sorry to add to the confusion.
Simms - that means you can stop doing it manually. Just wipe from CWM. It DOES work despite what people have been saying.
Click to expand...
Click to collapse
aw man, theres goes the fun part
Soft back button not working for me in this recovery. It acts as the power button would instead.
Net scrolling is the same because now I have to scroll down to "go back" each time
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, version compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the LG Optimus 2X. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for most of the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-p990.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-p990.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
Now that Koush added backup support for internal/external sdcard I'll only build onw version (exernal sdcard in file lists) If you really want one build for internal sdcard, let me know and I'll do it.)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
As of this version, I'll only be providing one img file. It seems 5.0 has native support for internal/external SD card. Need confirmation of this, as I don't have this phone myself.
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Reverted back to ext3 for the meantime, since I didn't get ext4 working. Any suggestions are welcome!
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Two versions. One for internal storage and one for external microSD card (same zip file)
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
This recovery bricked my phone
Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
Anybody with same problem?
Hell_97 said:
This recovery bricked my phone
Click to expand...
Click to collapse
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk
Updated recovery.fstab to allow ext4. Might work better. Try at your own risk.
zyonee said:
How did you install it? Can you still boot into whatever ROM you were running before? What happens when you start to phone now? Exactly what did you do? Please be a bit more specific so we might have a chance of helping you fix the problem.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I tried to change kernel and the device is locked on the LG screen, I solved with smartflash.
that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.
So can someone please test the newest recovery version? I'd like to know if ext4 works as it should.
Sent from my Nexus S using Tapatalk
klubipiff said:
that's not even related to this recovery mod.... I had the same problem with "original" 4.0.0.5 and after flashing vorkernel had the same problem.... I solved it with restoring nandroid backup. The kernel does not work for me with CM latest nightlies.
Click to expand...
Click to collapse
I installed vork kernel with "original" 4.0.0.5 on CM53 without problem.
To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App
peewster said:
To have ext4 you also need a kernel with ext4 support (correct me if im wrong) So which kernel has the ext4 support?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk
If you've changed recovery.fstab, then it should be OK with EXT4, that's all I had to do with my releases to get it working.
zyonee said:
Please stay on topic. This thread is about the modified ClockworkMod recovery and possibly its ability to work with ext4, not about custom ROMs or kernels...
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App
Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App
peewster said:
Just flashed the recovery, all ok. The confirmation menu is much better now with just 1: no line
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Very glad to hear it. Wipe, nandroid backup/restore and ext4, did you test all these?
Sent from my Nexus S using Tapatalk
peewster said:
Just asking because it looks nice but then i need to know wich kernels i can use?
Sent from my Optimus 2X using XDA App
Click to expand...
Click to collapse
Well, see, the problem isn't really which zips you can or cannot flash. It's more about whether you can flash at all or if ext4 works properly. If nandroid backup and restore works or not. I'm fairly certain that all kernels can be flashed, but how well they work is something that I don't see would be affected by this recovery.
Sent from my Nexus S using Tapatalk
Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?
That is the easiest way.
xAdaM-- said:
Hmm doesnt seem to wipe correctly...after doing a clean install of CM7 I still have all my old apps and settings. That said I did install it in an odd way (replaced Paul's recovery with it and ran his .bat script). What is the easiest method to flash recovery?
Click to expand...
Click to collapse
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.
zyonee said:
Exactly how did you wipe? Did you use the "format" commands in "mounts and storage" or did you use "clear data/factory reset"? I'm starting to think that the format command is not working.
Click to expand...
Click to collapse
Didn't go near the format command in mount and storage. In the specific "Wipe" menu --> tried factory reset etc/cache partition...all seemed to work way to quickly to actually be doing anything. Like I'd select wipe data/factory reset, hit yes and it would say completed after like 1 second (usually takes more than 5 with regular recovery). And then of course when I rebooted my device my data was still there, nothing wiped (except perhaps dalvik, but who knows).
SAFESTRAP v3.05 (2nd-System Bootstrap / Recovery)
PRIOR TO UPGRADING TO V3.x FROM V2.x MOVE THE /sdcard/safestrap FOLDER FROM YOUR /sdcard TO THE /sdcard-ext. THIS OPENS UP VALUABLE INTERNAL EMMC SPACE WHERE ROM SLOTS ARE CREATED. AND KEEPS YOUR V2 BACKUPS SAFE IN CASE YOU WANT TO REVERT TO V2 AND USE THEM TO RESTORE.
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the "Droid3Safestrap-3.05.apk" Installer Here for "DROID 3"
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the DROID3 VERSION ]
CHANGES:
[10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
[10/17] (3.05) Fixed recovery installation/removal from ROM-slots
[10/14] Updated to v3.04 BETA.
[10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
[10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
[10/14] Nearly instant swapping from ROM to ROM
[10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
[10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
[10/14] Charging in recovery
[10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
The entire TWRP team who has built an AMAZING recovery system.
The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always, let me know what you think!
A quick note about why I made a MotoBlur 5.6.890 ROM .zip for Safestrap:
1. This is the stock version of our Phone's software. If you want to swap back and forth between CM7 and the standard software, but NOT turn off "Safe System" then you need a stock ROM to use. This is it.
2. Devs can use this ROM as a sort of base for making their skinned ROMs without fear of bootlooping into an SBF. Feel free to tweak and hack away.. nothing you can do to the ROM will force you to fastboot restore. At worst you're looking at a battery pull -> bp-tools -> recovery -> restore.
3. I know some people are checking dev servers for future Moto updates. In theory I will pull the /system images from those updates and put out updated MotoBlur ROMs in the future as a way of test driving upcoming Moto patches w/o fear of leaving yourself stranded on an upgrade path that won't be supported.
So, im just curious, if I wanted to...
I could run say steel droid, then install safestrap, flash cm7,
And by turning safestrap off/on, I could technequally go back and forth
between 2 custom roms? Or do I have to keep the /system partition clean?
Sent from my DROID3 using Tapatalk
Actually the idea for Safestrap is to keep the main system clean.
I'm working with ChevyCam to get a Safestrap version of SteelDroid. Then you can use Safestrap exactly like regular recovery where you would swap from ROM to rom via backup and restore. The advantage being your method of recovery entry and ROM booting is always protected.
Great news !!!
Safestrap works on the XT883 rom too at least w/o the ota update, I'm going to test it on the updated system.
Thanks so much for clarifying, and thanks a million times over for all the great work you've selflessly done for the Droid3 community. I look forward to future CM7 updates.
hey hashcode, just a clarification, we can use safestrap like koush's bootstrap, but we just must turn safe system off right? cause your post makes it seem as if we cant do this
Right now, zips applied with Safestrap are applied to the 2nd-system only. In theory I could make some adjustments to allow for applying zips to the original system as well.. and while I understand the idea of "dual booting" a phone seems fantastic, it's really just an unrecoverable bootloop waiting to happen.
I'd rather that Droid 3 users turn on "Safe System" and never turn it off again (or need to). If all of our ROMs were installable via Safestrap I really feel that we would see alot less "I've bootlooped" postings on the boards.
For the recovery portion of Safestrap: it does NOT backup the original system. Only the 2nd-system, data and cache partitions. (Remember the idea is that you basically root your original system, toss on Safestrap and then enter recovery and toss a .zip onto your 2nd system)
I'm considering changing this in the next version of Safestrap so that backups from Safestrap can be used for full system recovery.
Another question with which to bother you...
When you have the option to do a backup, will you have the ability to choose the destination where the backup is stored as well as the location from where the backup can be restored (either internal or external storage)?
Thank you for your time.
Excellent work, I think this is a fabulous idea and should be the de facto standard for these locked devices. Were you still thinking about using a 2nd data/cache partition as well?
I think it would be pretty sweet if you could loopback mount file system images stored on internal storage for the system/data/cache partitions to implement a proper and safe multiboot system. I don't know how much of a performance hit this would take though.
Anyway, the one suggestion I would make about backing up the original system is to not do it as part of the regular backup/restore. Since system should rarely change, it'd be a waste of time and storage space to back it up every time. Could you either make it a separate option, or perhaps only back it up if the partition's checksum changed?
Besides, if you hose your system and need to restore it, you're probably not going to be using this recovery anyway.
The Solutor said:
Great news !!!
Safestrap works on the XT883 rom too at least w/o the ota update, I'm going to test it on the updated system.
Click to expand...
Click to collapse
I can confirm it works on the updated system too, btw for some odd reasons I'm unable to do a nandroid backup.
I''m investigating what's going on...
So in order to switch to another ROM (from CM7), that is not Safestrap compatible, I just need to toggle safe mode in recovery?
Sent from my DROID3 using XDA App
Yes. But beware of bootloops caused by not wiping your data between ROM switches.
To prevent that from happening you currently need to maintain copies of your data via backup/restore.. This will get addressed in the next version of Safestrap.
I have a version of Steel Droid that is supposed to be safestrap compatible. Im uploading it now. Will test it really quick, to be sure, and if its all good, will post a link!
The Solutor said:
I can confirm it works on the updated system too, btw for some odd reasons I'm unable to do a nandroid backup.
I''m investigating what's going on...
Click to expand...
Click to collapse
Ok I spoke too soon, backup and restore doesn't works on XT883
The backup folder is created correctly on the SDcard, the backup process starts normally with the /system partitons and then the process fails telling that there was an error while backing up the system partition.
Hashcode do you have any idea ?
The only differences in the partitioning between the two systems are the mount options
this is the 862
/dev/block/system on /system type ext3 (ro,noatime,nodiratime,barrier=1,data=ordered)
and this the 883
/dev/block/system on /system type ext3 (rw,relatime,barrier=1,data=ordered)
Do we install the MOTOBLUR Rom via safestrap or can we install it via bootstrap if coming from another Rom?
Sent from my DROID3 using XDA App
I guess it's safe to assume that this is not OK for international Droid3's like the XT860 / ME863?
Just a few short hours later I'm feeling adventurous, but the backup step indicates the MD5 generation failed. Any ideas?
Sent from my DROID3 using XDA App
LaZiODROID said:
I guess it's safe to assume that this is not OK for international Droid3's like the XT860 / ME863?
Click to expand...
Click to collapse
There would probably be radio issues.
Joe.cotto said:
Do we install the MOTOBLUR Rom via safestrap or can we install it via bootstrap if coming from another Rom?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
This MotoBlur ROM is specifically for Safestrap to run as 2nd-system.
The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium
I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.
the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.
Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.
hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.