Related
For those of you who keep trying to follow the instructions for 2000 quadrant score stock and keeping having to odin because it freezes at the sg4gs screen, you can blame the Voodoo zip.
1) Odin to a clean KD1 install and make sure you have rfs formatted.
2) Edit the Bionix Black Ice Voodoo release and delete the Tools folder and the Scripts folder.
3) Place the modified release zip on the sd card as well as the Bali 3.1uv zip, update.zip, ext4converter, rfsformatter(just in case you need to go back), any modems (like KF2),
4) Reboot to Recovery and choose install zips and choose the update.zip
5) Set mount points
unmount cache
unmount data
mount sdcard
unmount system
6) Goto install zip and choose the ext4converter.
***************Warning******************
7)You need to go back out and reset mount points.
unmount cache
mount data
mount sdcard
unmount system
8)Goto install zip and choose the modified zip you made of Black Ice .
9)Reset to mount settings in 7
10) Goto install zip and choose the Bali 3.1uv kernel
11) Reset to mount settings in 7
12) Goto install zip and choose KF2 modem
13) Goto advanced and choose recovery reboot
14) Voodoo cwm will show up, goto voodoo and disable all lag fixes.
system lag fix should be disabled
voodoo lag fix should be disabled
debug off
15) choose restart from main cwm menu
16) You will have to wait 3 minutes but you will hear the linda voice during this time.
Hey, just wanted to say that these instructions are great! I wanted to switch back to Froyo from GB and thought I'd put Black Ice on again. This worked flawlessly, my friend. Thanks!
I've said this a million times already, but Odin'ing to KC1 would be better than KD1, since KD1 supposedly has a corrupt /system partition.
bkoon1218 said:
I've said this a million times already, but Odin'ing to KC1 would be better than KD1, since KD1 supposedly has a corrupt /system partition.
Click to expand...
Click to collapse
Ya that's the main thing I changed. Whenever I see "Odin to KD1" anywhere, to me I replace it with Odin to KC1, root, recovery fix, then CWM flash drhonk's KD1.
fideli. said:
Ya that's the main thing I changed. Whenever I see "Odin to KD1" anywhere, to me I replace it with Odin to KC1, root, recovery fix, then CWM flash drhonk's KD1.
Click to expand...
Click to collapse
You don't even need to flash to KD1. You can flash ROMs straight from KC1! Good stuff, huh? XD
Sent from my awesome SGS4G
from what raver has said (and i trust his word), you can fix the faulty system partition if you flash the ext4converter prior to flashing a rom, so in the end, it may not matter. but i would agree that flashing to kc1 is the safer choice because you never know what errors may pop up
I'm quite new to all of this flashing stuff-- sorry if I sound like a complete newbie.
So I'm trying to get CyanogenMod on my Samsung Mesmerize (Galaxy S), though to no avail. I tried to follow the guide on the wiki located at http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide though it's not working. I can't even get CWM Recovery on it.
To get CWM Recovery, I'm following http://forum.xda-developers.com/showthread.php?t=734166 -- it says flash back to a stock kernel first, which I did via Odin and by following http://forum.xda-developers.com/showthread.php?t=881064 (I downloaded the "EC10 Full Froyo Restore Package"... not sure what the difference is between that one and EE19 but it seems to work.)
I'll go over my steps from the beginning, starting from when I'm flashing back the stock kernel on my phone:
Flash back stock kernel (EC10 Full Froyo Restore Package) using Odin (I've also tried flashing the EE19 one)
It starts up after this, however it briefly displays "FOTA wipe failed" in red and "wipe_data failed" in yellow (along with some other stuff too, but no other errors - when I use EE19 these errors occur as well)
It starts up into the default Android system recovery - I choose reboot system now
Root my phone using SuperOneClick ('yes' to install Busybox prompt)
Insert SD card, Download & install ROM Manager from the Market (following this guide which I linked up above)
Select "Flash ClockworkMod Recovery" (Current/Latest Recovery: ClockworkMod 2.5.1.2)
Select "Galaxy S i9000"
Superuser prompt appears, I click accept
ROM Manager freezes for a bit, then displays "Successfully downloaded ClockworkMod recovery!"
Choose "Backup Current ROM" - freezes for a bit, then phone begins to restart... enters default Android Recovery mode:
Install from package... Finding/opening/verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted.
When I reboot and enter the recovery mode by holding volume-power-home,
it displays "E:Can't mount /dev/block/mmcblk0p2 (No such file or directory)" at the bottom.
Also, when I try to "wipe data/factory reset" in the stock Android recovery mode, it gives this error:
E:Can't mount /dev/block/mmcblk0p3 (No such file or directory)
E:install_application_for_customer:Can't mount HIDDENSDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
I also know there's a "Manual Flash Overrride" option in ROM Manager - could I flash CWM Recovery manually and go that route somehow?
My final goal is to get CyanogenMod installed on my Mesmerize, though-- however, I need CWM Recovery to do that. Any ideas as to why CWM Recovery isn't getting installed, and how to fix the mmcblk0p2 error message in recovery mode (and if that's affecting anything)?
Thanks!
MOD EDIT:
FORUM RULES:
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Yes, and i will add ROM manager only works for Mesmerize MTD systems, and CM7 IS MTD. SO, technically you need to be on CM7 already to use ROM manager.
You don't need to use ROM Manager period.
Just making a new thread that has download links for ClockworkMod Recovery (CWM) that are readily apparent.
First to explain to anyone who does not know what ClockworkMod Recovery is:
quoting from this post:
What Is ClockworkMod Recovery And How To Use It On Android [Complete Guide]
ClockworkMod – also known as Clockwork and CWM – is a custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
The download links are at the end of this post.
Installation Instructions:
*****************************************************
To install CWM, do the following. If you wish to UPGRADE an existing CWM recovery that you already have installed, you still follow the following steps or alternatively, you can try the steps at the end of the post in the UPGRADE CWM USING FLASHABLE ZIP IN RECOVERY section:
1. Download the CWM Recovery file using one of the links at the end of the post. I recommend one of the latest versions--currently version 5.5.0.4. Unzip the recovery.img file from the Zip file you downloaded (using WinZip, 7-Zip, or another zip utility) onto your desktop so it is easy to find.
2. Turn OFF your Motorola Triumph (MT) phone.
3. Once the phone is off, make sure that it is not plugged into anything at this time.
4. Hold down the Power + Volume Down buttons simultaneously until the phone vibrates. (I usually hold the phone in one hand and then simultaneously press one button with my thumb and the other button with my forefinger)
5. The phone will boot into Download Mode. You will see the following types of messages on the screen:
polling, get oemsbl_mode=1
6. Now plug the phone into your computer. A drive labeled MOBILE will appear in your computer (MAC or Windows. Not sure about Linux)
7. Open the MOBILE drive and you should see a folder named image.
8. In the image folder, you will now see the recovery.img file.
9. Rename the file to recovery.img.old (or something like that) so you have a backup in case you ever want to revert back to the stock recovery.
10. Copy the recovery.img file that you unzipped in step 1 into the MOBILE folder on the phone.
11. After the copy is complete, unplug the phone from the computer and take out the battery, wait a second, and put the battery back into the phone.
12. To boot up into CWM, hold down the Power + Volume Up and Volume Down simultaneously until the phone vibrates.
Please note: DO NOT be alarmed if you see these types of error messages. Many people (including me) get them and none have reported that the errors affect the operation of ClockworkMod Recovery:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The MT should boot up into CWM. The latest stock version 5.5.0.4 will have blue lettering.
The controls for CWM 5.5.0.4 (as well as all previous Isaacj87 versions) in the MT are:
Volume up --> up
Volume down --> down
Power --> turns screen black
Menu --> select
Home --> nothing
Back --> back
Search --> nothing
If you want to view a video of how to install CWM on the MT, Minus5252 put together this video on this post -- just don't download the version shown in the video as that version is old:
http://androidforums.com/triumph-al...-recovery-motorola-triumph-4.html#post3021427
Download links:
Current Base CWM recovery.img:
CWM 5.5.0.4 (20120527) --RECOMMENDED VERSION
MT_CWM_5504_20120527.zip
MT_CWM_5504_20120527.zip
MD5: 0f847a44474b3cad5663b4409c089826
This Zip file is a flashable Zip file in clockworkmod recovery or follow the instructions above to install if you do not already have a previous version of clockworkmod recovery installed.
This version will recognize the .no_confirm or .one_confirm files in your clockworkmod folder when wiping data and cache also in addition to installing zips. See this post for instructions if you are interested in using the .no_confirm or .one_confirm:
http://androidforums.com/triumph-al...od-recovery-motorola-triumph.html#post4293429
Changelog from previous 5.5.0.4:
-Added "Power off" menu option back to main menu.
Themed CWM Versions based on sources from Tickerguy and Isaac:
b_randon14 5.0.2.7 (themed to be lime green):
recovery.img
agentc13 5.0.2.7 (Doctor Who theme using mostly blues):
http://www.mediafire.com/?p7oz58f6i9s95ro
Older versions linked here for posterity:
CWM 5.0.2.8:
MT_CWM_5028_recovery.zip
CWM 5.0.2.6 (thanks to isaacj87 and tickerguy) supports ext4
recovery-cwm-5.0.2.6-triumph.zip - reposting Isaac's link from Isaac's MIUI thread.
recovery-cwm-5.0.2.6-triumph.zip
recovery-cwm-5.0.2.3-triumph.zip
http://tinyurl.com/7ddvpcb
CWM 4.0.1.5 (thanks to isaacj87) supports ext 4
http://tinyurl.com/82f6qup
CWM 4.0.1.4 (thanks to isaacj87)
http://tinyurl.com/7e682nk
CWM 4.0.0.9 (thanks to tjstyle)
http://tinyurl.com/7cnrjyn
UPGRADE CWM USING FLASHABLE ZIP IN RECOVERY:
If you already have a Recovery on your MT and wish to flash a newer or different recovery version, b_randon14 has provided the following flashable ClockworkMod Recovery Zip files that you can just put on your SDCard and flash as normal--I have not tested them so, as usual, do so at your own risk:
Themed CWM Versions in flashable Zip:
b_randon14 5.0.2.7 (themed to be lime green):
b_randon14_CWM_5.0.2.7.zip
Stock CWM versions:
Here is the v5.0.2.3:
Isaacj87_CWM_5.0.2.3_signed.zip
v4.0.1.5(isaacj87's):
Isaacj87_CWM_4.0.1.5_signed.zip
v4.0.1.4(isaacj87's):
Isaacj87_CWM_4.0.1.4_signed.zip
Triumph STOCK RECOVERY in flashable Zip:
MT_stock_recovery.zip
CWM Recovery - NO TOUCHSCREEN - in flashable Zip:
MT_CWM_5504_20120527_yellow.zip
MT_CWM_5504_20120527_yellow.zip
MD5: a3e40a036d6123ebbb2065c8ddb6286b
Changelog:
MT_CWM_5504_20120527_yellow.zip
-Changed menu and text color to YELLOW.
-Always show the "Go Back" menu options on submenus.
-The keys for this version are:
Volume up --> up
Volume down --> down
Power --> select
Menu --> nothing
Home --> nothing
Back --> back
Search --> nothing
Huge thanks to Koush on whose work all CWM is based on. Thanks to isaacj87 who did the original port to the MT on which these are based. If I missed anything or forgot to thank anyone, let me know and I'll update this.
I'm a slow adopter and I think my clockwork is still at 4.0.0.9. Thank you for posting this relatively informative compilation of info.
Any outstanding features you want to mention right off the bat? The kind of stuff that would belong in OP?
Sent from my ADR6400L using Tapatalk
The main reasons to upgrade are:
1. The newest versions support ext 4 partitions which are necessary if you want to flash the latest CM7 ROM.
2. This may or may not be true, but I think they sync'ed the latest CWM code from the CM code and that was how it got updated to the 5.0.2.3. So there may be bug fixes that got pulled down--I could be wrong though--just guessing here.
3. I read some people report that in the CWM 4.0.0.9 there was an option to "format /fat" which they did and semi-bricked their phones. This option does not exist in the Isaac/Tickerguy CWM versions and so there's less chance of a user accidentally bricking their phones.
I tried all of these recovery imgs
I followed all of the directions and once I boot onto cwm I see below some errors
CWM-based Recovery v5.0.2.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I've never experienced that but i've seen other people report the same thing. However, they also indicate that it doesn't seem to cause them issues. Try doing a backup and then a restore to see if that works for you.
Sent from my MOTWX435KT using XDA App
Mine always says can't mount cache/recovery/command
Hey llorn I'm making some cwm flashable zip recoveries tonight and ill pm you the links so you can add them to the open! I finally figured out how to flash recoveries from cwm!
Sent from my OC'ed Triumph!
Hey llorn, sorry but would you mind guiding me a bit, i would usually find a way to this without help but how should i backup and restore? Isnt that done through cwm? Whenever cwm loads i try pressing power for any option and all i get is a screen with nothing but a hat. Any suggestions?
jjuanml22 said:
Hey llorn, sorry but would you mind guiding me a bit, i would usually find a way to this without help but how should i backup and restore? Isnt that done through cwm? Whenever cwm loads i try pressing power for any option and all i get is a screen with nothing but a hat. Any suggestions?
Click to expand...
Click to collapse
As stated in the OP:
The controls for CWM 5.0.2.3 (as well as the Isaacj87 versions 4.0.1.5 and 4.0.1.4) in the MT are:
Volume up --> up
Volume down --> down
Power --> back
Menu --> select
Home --> nothing
Back --> back
Search --> nothing
And yes, you would do the backup and restore in the "Backup and Restore" option.
Older versions remove the menus if you push the...back button, I believe. They are returned if you push the button again but it's still disconcerting.
I wonder if there's any issues with wiping cache if you decide to do so... It's rather difficult to properly mount things on the Triumph, it seems!
Sent from my ADR6400L using Tapatalk
llorn do you know how embarrassed I feel. I can't believe i overlooked this. I'm an idiot! Just booted up cm7! I wish I could still install a custom kernel though....
Nah ur good wiping anything(besides fat!!!!) With these recoveries! Yeah this phone is partitioned weird but I haven't had a problem getting stuff to mount in my update zips!
Sent from my OC'ed Triumph!
updated OP to include the latest 5.0.2.6 CWM posted by Isaac.
No need to update if you don't want to if you are already using 4.0.1.5 or 5.0.2.3 -- unless you're like me and just have to have the latest versions...
jjuanml22 said:
I followed all of the directions and once I boot onto cwm I see below some errors
CWM-based Recovery v5.0.2.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I got the same, by a mistake i picked an older version 4.0.1.5, and that worked just fine, but flashed to v5.0.2.3 and I got these errors and if I try to use any command it freezes. If I go back to 4.0.1.5 again it works. What can be causing this? Will a wipe first fix it?
i followed the directions but volume down and power doesn't boot me into download mode. I just get an exclamation mark and an android guy...suggestions?
edit: nevermind, i figured it out.
jjuanml22 said:
I followed all of the directions and once I boot onto cwm I see below some errors
CWM-based Recovery v5.0.2.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I too am getting this on my Triumph with v5.0.2.6. I was able to load the CM7 Beta 8 after making a backup, but am wondering what these errors could mean for trying to restore from the Backup I created at the beginning.
vsanch24 said:
I too am getting this on my Triumph with v5.0.2.6. I was able to load the CM7 Beta 8 after making a backup, but am wondering what these errors could mean for trying to restore from the Backup I created at the beginning.
Click to expand...
Click to collapse
They won't affect anything. you should be fine.
llorn said:
They won't affect anything. you should be fine.
Click to expand...
Click to collapse
I got them too, but everything worked fine.
When i try to boot into recovery the phone vibrates endlessly until i do a battery pull. I followed the instructions but i did rename the CWM file from Recovery to Recovery.img could that be why its doing this?
Edit: Nevermind. That was the problem
jerenater10 said:
When i try to boot into recovery the phone vibrates endlessly until i do a battery pull. I followed the instructions but i did rename the CWM file from Recovery to Recovery.img could that be why its doing this?
Edit: Nevermind. That was the problem
Click to expand...
Click to collapse
If you were in windows 7 you named the file Recovery.img.img
Sent from my Revolting Revolution. Powered my mtmichaelson.
llorn said:
UPGRADE CWM USING FLASHABLE ZIP IN RECOVERY:
If you already have a Recovery on your MT and wish to flash a newer or different recovery version, b_randon14 has provided the following flashable ClockworkMod Recovery Zip files that you can just put on your SDCard and flash as normal--I have not tested them so, as usual, do so at your own risk:
Here is Isaac's 5.0.2.6:
http://www.mediafire.com/file/6kl88wot71do07l/Isaacj87_CWM_5.0.2.6_signed.zip
Here is the v5.0.2.3
http://www.mediafire.com/file/muzezh1mu9okmok/Isaacj87_CWM_5.0.2.3_signed.zip
v4.0.1.5(isaacj87's):
http://www.mediafire.com/?kl86quxsblcc6g7
v4.0.1.4(isaacj87's):
http://www.mediafire.com/?8sgd567mt86utan
If I missed anything or forgot to give anyone credit, let me know.
Click to expand...
Click to collapse
None of these links work for me
Hello, I have the voodoo cwm lagfix v3.0.2.8x Recovery. I can use [KERNEL] Modified Stock subtly with CWM5 + Voodoo lagfix? I have the GB Rom 2.3.6 Octane KJ6 CIQ V3.0 XPLOD EDITION NO. It is possible, I can use? What are the steps to install?
jorgeciprian said:
Hello, I have the voodoo cwm lagfix v3.0.2.8x Recovery. I can use [KERNEL] Modified Stock subtly with CWM5 + Voodoo lagfix? I have the GB Rom 2.3.6 Octane KJ6 CIQ V3.0 XPLOD EDITION NO. It is possible, I can use? What are the steps to install?
Click to expand...
Click to collapse
Yes you can simply flash the new kernel package with your CWM recovery.
Keep in mind that flashing this new kernel will update your CWM to 5.x, which uses a different backup format than 3.x, your current version, so any backups you have made with your old recovery are not usable with this new version.
This means if something happens and you need to restore an old backup you will need to revert your CWM to version 3.x by flashing drhonk's GB kernel.
Hope this helps.
Sent from my SGH-T959V using xda premium
Thank you. I never made a backup to the Recovery. I have a doubt. I have to use the update from sdcard, or install zip from sdcard? Forgive my ignorance and my English. I'm from Dominican Republic.
Thanks again ´´crackpot´´.
Make sure you have a back up of your efs folder before you do anymore flashing!
* * Do NOT extract the contents of .zip files. When flashing - we flash the .zip.
Go to market, download and install SGS Kernel Flasher
Download the kernel and copy it to the root of your sdcard.
o Directions to flash the kernel:
Open the SGS Kernel Flasher app.
First select [backup kernel].
When it if finished you will still be on the same screen and it will see a green vertical bar at the bottom of the screen next to - Backed up as.....
Now select [choose kernel] and a file manager will appear.
Select [parent directory] and you will be on the root of your sdcard.
Navigate to the bottom and find the kernel .zip file you copied over.
Once selected you will be back at the main screen of SGS Kernel Flasher.
Select [flash kernel].
The kernel will flash and your phone will reboot.
You will hear Linda speaking on the Galaxy S 4G boot screen.
Wait and wait some more! She will keep talking to you!
Eventually the phone will reboot.
Ready! Muchas gracias. Va de maravilla...
Sent from my SGH-T959V using Tapatalk
For rooted Charge owners, some are on the RFS file system, others are on EXT4. The Charge comes as RFS stock, so unless you have converted to EXT4, chances are that your phone is still on RFS. What's the difference? Click on this link to view a discussion among some of the original developers including IMNUTS: RFS to EXT4 - Page 3 - xda-developers
Keep in mind that nobody except YOU are responsible for what happens to your phone. Past performance is no guarantee of future results, always read the instructions carefully before flashing, feel free to ask questions.
Note: the kernels mentioned below are for FP1 & FP5 ROMs - currently, there are only two ROMs with this build, Eclipse and Tweaked
FP5 build is currently only supported by the Tweaked ROM - thanks to kynalvarus for developing the FP5 custom kernel!
Before you begin the conversion:
- make sure that you have root access and can enter the Clockwork Recovery Mod (CWM)
- download and install Terminal Emulator from the market
- once in there, type "SU" then "Mount" (without quotes)
- scroll to the top and look for the text after the following folder names: "/system", "/data", "/dbdata", and "/cache"
- if you see RFS, then you are on RFS, if EXT4, then you are on EXT4
- download Imoseyon's kernel (http://rootzwiki.com/topic/3426-kernel-gb-imoseyon-kernel-stock-repacked-v400-11611/)
- make sure that you've got plenty of battery life on your phone (or plug it in during the process), for me, the process cost me ~5-10% of battery life, but your experience may vary
below are the steps to convert RFS to EXT4:
check to see if you have a folder called "sdcard/VooDoo/disable-lagfix; if so, then delete it, if not proceed to next step
1. boot into CWM
2. mount system
3. install zip from SDcard
4. select Imoseyon's kernel
5. re-boot system (process can take about 10 minutes, you'll hear a robot lady voice telling you that the system is partitioning, and will give you an estimated time of completion)
6. check to ensure that the conversion took place by entering into Terminal Emulator and looking for EXT4; if still RFS, then:
a. Download and install voodoo control from market
b. Check all ext4 boxes then reboot
c. Re-check with Terminal Emulator
7. boot back into CWM
8. mount system
9. install zip from SDCard
10. select your flavor of PBJ kernel (note: stock FP1/FP5 will NOT work on EXT4)
a. FP1: tonsit
b. FP1: 0502 PBJ (no longer posted, ask a member of this community for the file)
c. FP1: 0504 PBJ (no longer posted, ask a member of this community for the file)
d. FP1: 0524 PBJ
e. FP5: Lazarus Recharged
11. be sure to "Fix Permissions" in CWM before rebooting or you could lose root (if you still lost root, then simply flash SuperUser/SuperSU via CWM)
below are the steps to convert from EXT4 to RFS:
1. check to see if you have a folder called "sdcard/VooDoo/disable-lagfix" (without quotes); if not, then create it; if so, proceed to next step
2. if you have a custom boot animation, change it to read "sanim.zip.bak"
3. boot into CWM
4. mount system
5 .install zip from SDcard
6. select Imoseyon's kernel
7. re-boot system (process can take about 15 minutes, you'll hear a robot lady voice telling you that the system is partitioning, and will give you an estimated time of completion)
8. check to ensure that the conversion took place by entering into Terminal Emulator and looking for RFS, if still EXT4, then:
a. Download and install voodoo control from market
b. Un-Check all ext4 boxes then reboot
c. Re-check with Terminal Emulator
9. boot back into CWM
10. mount system
11. install zip from SDCard
12. select your kernel
a. Stock FP1
IMPORTANT: you can only convert to a stock kernel from another stock kernel or the 0524 PBJ kernel (presumably the Lazarus kernel as well). For example, if you are on the 0504 PBJ kernel and want to go to stock FP1, you will need to flash the 0524 PBJ kernel first, and then flash the stock FP1. IMNUTS setup this kernel to help prevent issues when folks wanted to flash back to a stock kernel
b. FP1: tonsit
c. FP1: 0502 PBJ (no longer posted, ask a member of this community for the file)
d. FP1: 0504 PBJ (no longer posted, ask a member of this community for the file)
e. FP1: 0524 PBJ
f. FP5: Lazarus Recharged
g. Stock FP5
be sure to "Fix Permissions" in CWM before rebooting or you could lose root (if you still lost root, then simply flash SuperUser/SuperSu via CWM)
below are the steps to convert RFS to EXT4:
check to see if you have a folder called "sdcard/VooDoo/disable-lagfix; if so, then delete it, if not proceed to next step
1. boot into CWM
2. mount system
3. install zip from SDcard
4. select Imoseyon's kernel
5. re-boot system (process can take about 10 minutes, you'll hear a robot lady voice telling you that the system is partitioning, and will give you an estimated time of completion)
6. check to ensure that the conversion took place by entering into Terminal Emulator and looking for EXT4; if still RFS, then:
a. Download and install voodoo control from market
b. Check all ext4 boxes then reboot
c. Re-check with Terminal Emulator
7. boot back into CWM
8. mount system
9. install zip from SDCard
10. select your flavor of PBJ kernel (note: stock FP1/FP5 will NOT work on EXT4)
a. FP1: tonsit
b. FP1: 0502 PBJ (no longer posted, ask a member of this community for the file)
c. FP1: 0504 PBJ (no longer posted, ask a member of this community for the file)
d. FP1: 0524 PBJ
e. FP5: Lazarus Recharged
11. be sure to "Fix Permissions" in CWM before rebooting or you could lose root (if you still lost root, then simply flash SuperUser/SuperSU via CWM)
Click to expand...
Click to collapse
somewhat easier method for me anyways...
MAKE SURE YOU HAVE A NANDROID FIRST!!!
or PBJ FP5 and your ROM of choice
1. boot into CWM
2. make nandroid
3. flash selected formatter
4. restore said nandroid or flash ROM AND kernel! (make sure it is a supported kernel or you WILL boot loop)
5. reboot
6. enter terminal and type "SU" and then "mount" to check and see if you are EXT4
this method has worked for me every single time.
je2854 said:
somewhat easier method for me anyways...
MAKE SURE YOU HAVE A NANDROID FIRST!!!
or PBJ FP5 and your ROM of choice
1. boot into CWM
2. make nandroid
3. flash selected formatter
4. restore said nandroid or flash ROM AND kernel! (make sure it is a supported kernel or you WILL boot loop)
5. reboot
6. enter terminal and type "SU" and then "mount" to check and see if you are EXT4
this method has worked for me every single time.
Click to expand...
Click to collapse
I do not recommend trying this shortcut. I made my Nandroid in CWM, flashed the ALL Flasher, went to restore the nandroid, and was told my file system format was incorrect. I am now stuck in a bootloop, unable to access CWM or Download mode.
I was running Tweaked 3.2 with Laz's Kernel
Update: Yea, this has SERIOUSLY screwed up my phone. I am now able to get into CWM, but I am told I cannot mount /system, so I can't mount it to reflash the ROM, nor can I format it back to RFS. I also cannot install any zips from my sdcard, as the screen simply goes blank when I click "install zip from sdcard".
So....can anybody help me? Now that I can get into CWM, I figure I can prolly get into download mode, so maybe a full Odin would help? Does anybody have a PIT I can use?
The Amorphist said:
I do not recommend trying this shortcut. I made my Nandroid in CWM, flashed the ALL Flasher, went to restore the nandroid, and was told my file system format was incorrect. I am now stuck in a bootloop, unable to access CWM or Download mode.
I was running Tweaked 3.2 with Laz's Kernel
Update: Yea, this has SERIOUSLY screwed up my phone. I am now able to get into CWM, but I am told I cannot mount /system, so I can't mount it to reflash the ROM, nor can I format it back to RFS. I also cannot install any zips from my sdcard, as the screen simply goes blank when I click "install zip from sdcard".
So....can anybody help me? Now that I can get into CWM, I figure I can prolly get into download mode, so maybe a full Odin would help? Does anybody have a PIT I can use?
Click to expand...
Click to collapse
I have never had problems but here is the PIT you asked for
The Amorphist said:
I do not recommend trying this shortcut. I made my Nandroid in CWM, flashed the ALL Flasher, went to restore the nandroid, and was told my file system format was incorrect. I am now stuck in a bootloop, unable to access CWM or Download mode.
I was running Tweaked 3.2 with Laz's Kernel
Update: Yea, this has SERIOUSLY screwed up my phone. I am now able to get into CWM, but I am told I cannot mount /system, so I can't mount it to reflash the ROM, nor can I format it back to RFS. I also cannot install any zips from my sdcard, as the screen simply goes blank when I click "install zip from sdcard".
So....can anybody help me? Now that I can get into CWM, I figure I can prolly get into download mode, so maybe a full Odin would help? Does anybody have a PIT I can use?
Click to expand...
Click to collapse
full Odin with PIT should do the trick.
This guide needs to be removed voodoo doesnt have the option format to ext4 anymore.
barn25 said:
This guide needs to be removed voodoo doesnt have the option format to ext4 anymore.
Click to expand...
Click to collapse
Are you sure? The options are only displayed when you have a voodoo kernel, the last of which was Imoseyon's 4.0 (EP1W IIRC) hacked kernel. This will not work on any of the GB PBJs.
barn25 said:
This guide needs to be removed voodoo doesnt have the option format to ext4 anymore.
Click to expand...
Click to collapse
That's interesting, because I followed this exact guide back in December and it worked perfectly fine for me, just as described in this guide.
Sent from my SCH-I510 using Tapatalk 2
Yup running lazarus ReCharged kernel for FP5E which is voodoo and EXT4 enabled. http://rootzwiki.com/topic/37854-kernel2013-01-09lazarus-recharged-kernel/ Whoops forgot to post a screenshot from my charge.
barn25 said:
Yup running lazarus ReCharged kernel for FP5E which is voodoo and EXT4 enabled. http://rootzwiki.com/topic/37854-kernel2013-01-09lazarus-recharged-kernel/ Whoops forgot to post a screenshot from my charge.
Click to expand...
Click to collapse
That's because you need to flash this kernel first... http://rootzwiki.com/index.php?/top...-(Stock-Repacked,-V4.0.0,-11/6/11)#entry79247 it will convert everything. Use Voodoo and make sure, then flash Lazarus.
Sent from my AOSPA N7 controlled by Metallice's a36 Kernel.
I did do that nothing happened. Which was odd...
barn25 said:
Yup running lazarus ReCharged kernel for FP5E which is voodoo and EXT4 enabled. http://rootzwiki.com/topic/37854-kernel2013-01-09lazarus-recharged-kernel/ Whoops forgot to post a screenshot from my charge.
Click to expand...
Click to collapse
Lazarus has support for voodoo sound, not voodoo lagfix. This app displays voodoo lagfix controls when it is available.
I didnt know that. So what FP5E kernel does support Voodoo lagfix?
barn25 said:
I didnt know that. So what FP5E kernel does support Voodoo lagfix?
Click to expand...
Click to collapse
None of them do. You gave to get imoseyon 4.0 kernel, which is for a really old leaked gb build but works well enough to boot and convert partitions, from rootz.
Once you are done setting up lagfix you can flash the kernel of your choice.
Sent from my SCH-I510 using Tapatalk 2