Related
i am trying to figure out how to flash Voodoo for 2.2 EA11 and i cant figure it out for the life of me. HELP PLEASE!
sinhealer said:
i am trying to figure out how to flash Voodoo for 2.2 EA11 and i cant figure it out for the life of me. HELP PLEASE!
Click to expand...
Click to collapse
I am going to assume you are on a mesmerize. If you are on a showcase I don't think there is a voodoo kernel available yet.
Ok, first thing you need to do is download the clockwork mod recovery. It can be found in the OP of both the EA11 and the EB16 threads.
The downloaded zip will contain 2 files. One is a .tar that you need to flash in odin. This allows the stock samsung recovery to flash the cwm recovery. The other file in the downloaded archive is a zip file, which you must name update.zip (if it isn't already, it's been a while since I've flashed it) and place it in the root directory of your sdcard. Also, download the EA11 voodoo kernel and put it on your sdcard.
Next, boot into recovery and select "install update.zip". This will install and push you to the clockwork recovery (note: every time you boot into recovery before you install the voodoo kernel you will get the samsung recovery and must install update.zip to access clockwork). Once in the clockwork recovery you need to select "install .zip from sdcard" then select "choose .zip from sdcard". Navigate to the EA11 voodoo kernel and install it.
Now reboot, and should hear the creepy voodoo chick tell you what a
she is doing. Once the phone is done booting (which will take a couple minutes) voodoo will be installed and lagfix will be enabled.
P.S. In the samsung recovery the home button is used to select items,in clockwork recovery the power button is used to make selections.
I hope this helps.
Sent from my voodoo froyo Mesmerize
And remember the volume rocker is your up and down keys while the menu button acts as "back".
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
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
Q. Why there is a need to repack the firmware?
A. As you may know, the stock kernel in the stock firmware has the emmc hard brick feature enabled which is believed to be the reason of 2 hard brick incident reported in the forum. And even worse, the emmc hard brick bug (mmc_erase) can be called @ anytime after the system is booted with a buggy kernel, which means that your device can immediately get bricked after the first reboot.
Q. So is it okay to flash the ROM via odin with a different bootloader (i.e. boot.img)?
A. Theoretically, yes. But the problem is that when we repack the odin package with a modified boot.img. The download counter will rise and a yellow triangle will appear on every boot.
Q. So is there any way to flash the stock bootloader but without letting it get booted?
A. Yes. There is a way to do so. After you have successfully flashed a package via odin, the odin bootloader (based on BCT partition) will invoke the recovery bootloader to finish the install process. And if you are not using the stock recovery, the process will get halted and then leave you at the recovery (CWM) screen. And then you can flash a kernel via CWM at this point.
Q. Is there anything that I should aware of?
A. Yes. Just like flashing any firmware, After flashing the ICS package, it is important for you to backup all the important files before flashing.
Guideline 1 [For people who is willing to use CWM6 (provided by Adam77Root)] (prefered way) :
1. Turn on your device and connect it to a computer
2. Place the kernel file, superuser file (which can be flashed via CWM) and new_sec_csc.zip into your internal SD card first and make sure all your important data on /sdcard are backed up (You are free to select any kernel but make sure the mmc erase part get disabled from the kernel completely)
3. Turn it off and remove the external sdcard from the device
4. Download the ICS firmware files which contains GB kernel and CWM6
5. Put the device into download mode and flash the above package via odin 3.07. Place the package file (*.tar.md5) into PDA part (You can now flash with pit file as well, however the internal sdcard data will get wiped so it is important for you to make a backup for important files before flashing) (DO NOT attemp to flash any ICS package via odin 1.85 as there is a high risk that the download process get stuck in odin v1.x series, and you have to unbrick your device with nvflash tool if error occurs)
6. After the device is restarted, it will get into recovery (CWM) mode. And the script provided by Samsung will be failed to execute due to a assert call. (Don't worry, you can execute the script again by using the patched new_sec_csc.zip)
7. Backup any important data in /sdcard (external sdcard) now if you didn't do so. You can do this @ 'Mount and storage' -> 'Mount USB devices'.
8. 'Wipe cache' and 'Wipe data / factory reset' (make sure you have all your important data on /sdcard backed up and your have removed your external sdcard device)
9. If the above stage has wiped your CWM flashable zip file as well, you can mount the device to a computer via mount menu and you can place the zip file to the phone as mass storage again.
10. Install the CWM flashable zip file (superuser, new_sec_csc.zip and your kernel file) from sdcard (For an unknown odd reason, all the packages you gonna install in this step will have signature verification error, but it is safe to proceed. Just switch off the signature verification from the menu or choose to 'Install untrusted package'.)
11. After you flashed kernel, you are free to flash anything and free to reboot now.
12. If you have used a pit file for flashing the package in odin, a message will be appeared in notification center telling you the filesystem on /sdcard cannot be recognized. Just click on it to format the sdcard and then you are free to use anything now.
13. If you are still afraid of breaking system integrity as you were not using the samsung recovery script to finish the update process, navigate to 'Options -> Back up and reset -> Factory data reset' and totally reset the device there.
P.S. If you accidentally pressed reboot the system now in CWM 6, don't worry, the system will not be able to boot into normal mode. And you can redo all the things since the beginning.
Update #1 : During testing the flash process, I have found that the repacked firmware cannot be flashed with odin 1.83. It is important to get all the ICS firmware being flashed with odin 3.07 (or 3.x sereis) instead v1.x series. Otherwise you have made a risk that your partition (PIT) table is messed up so srsly that you have to use nvflash tool to restore everything. I will tell this to cooleagle to get everyone knows of it.
XXLQ9 :
Stock package with GB kernel and CWM6 which is based on safe stock GB ZSLE6 kernel (just extract the file in the splited zip files) : http://www.mediafire.com/?uq5tg9o7nli04b2 and http://www.mediafire.com/?b5i571br0x07c38
CWM flashable package :
- Superuser CWM flashable package : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip or Superuser-3.2-RC3-arm-signed.zip in attachments (But you will be unable to update with the 3.2 RC3 build, use 3.1.3 one if you want)
- My own kernel (flashable via CWM) : UnknownzD_Kernel_with_superuser.zip (with superuser, good for first time install) and UnknownzD_Kernel.zip in the attachments
- Patched Samsung install script (the one which failed to run) : new_sec_csc.zip in the attachments
Odin v3.07 : Odin307.zip in the attachments
Credits go to Adam77Root for his CWM image and someone(!?) who has uploaded odin 3.07 to xda forum. Will try to check his name later.
Short change log about my kernel (The longer one will get posted when I start another thread for it) :
4 IO scheduler added
Voodoo sound patch added
Full fp calculation based on hardware fp opcode only (which should makes the device consumes less energy while providing the same performance level)
MMC erase function tootally disabled
Default.prop get modified to increase the performance
Based on ICS 3.x kernel src code released by Samsung
If you gonna use my kernel, please make sure that you have efs_backup.img backed up safely after flashing my kernel package, as it contains your device's IEMI info, which can save you from future disaster as you can use the unbrick tool with it. You can backup the efs_backup.img by :
1. Flash my kernel in CWM
2. Mount and storage -> Mount USB devices
3. Copy the efs_backup.img from the sdcard to your own computer (it is vital for you as you can use the unbrick tool later)
Now I am stuck @ finding a proper file host to upload the files.
waiting for this!
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
coldbeermt said:
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Click to expand...
Click to collapse
You can root it on your own with superuser zip file. And busybox binary is not yet dropped into /sbin/ as I believe it comprise the system integrity back in GB kernel. Init.d will be supported in near feature. All the things that I changed is just inside the kernel and recovery and provide a safe envrionment for user to continue to flash their own desired kernel. Nothing more.
For kernel development, I will make a separate thread in dev section later.
Sorry I have to postpone the release as I have to repack everything with the nordic release (XXLQ9) now.
Ok, I'm sure you know I asked just for general information. I supposed your answer yet
Anyway, I'm sure its a good job. With the new version (nordic) I suggest you to upload releases to dropbox our something easier. Anybody could make a mirror in other servers later :thumbup:
Sent from an GT-I9103 with ICS and Tapatalk 2
UnknownzD said:
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
Click to expand...
Click to collapse
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
xlm13x said:
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
Yea I just saw the PM, it is really useful for me tbh. Thanks for your help.
Okay after many hours of testing, I am happy to release the ICS XXLQ9 package with GB kernel and CWM 6 (based on the one posted by Adam77Root) that should be able to let you flash your own kernel after flashing it. Download links will be up shortly.
So after 5~6 times of srs bricking, I finally get it working correctly after working overnight.
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
UnknownzD said:
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
Click to expand...
Click to collapse
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
vipul12389mehta said:
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
Click to expand...
Click to collapse
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Nice work! Thanks!
Sent from my GT-I9103
nedooo said:
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Click to expand...
Click to collapse
Basically the things you mentioned above are included in the package / guide already. Tbh this should not be dangerous. But I want more people to test it first because last time when I released the GB kernel, a lot of people complained about the things that do not occur on my phone.
oh btw about the zero free space in system space, I believe it is just a bug in the filesystem. You can fix it easily by using e2fsck, which is actually included in my kernel script.
This is just explanation about staying stock. Your work and effort is well above this. Thanks in name of all flash addicts
So after many times of tests, I guess it is safe to use the build already, just make sure you have everything backed up before updating (actually you should do this for any fimrnware update). If you have found any problem, just report the problem here. I will repack every stock firmware following the same method until Samsung acknowledge that the MMC_CAP_ERASE is removed from stock kernel.
If you have found your device bricked after using any ICS update (for example, unable to flash the device any more via odin protocol), please let me know via pm please so that I can guide you to fix your phone in IRC.
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
Click to expand...
Click to collapse
When you are updating the ROM from GB to ICS better to wipe data or else you face some Force Closes and other issues....
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
"I like spelling my name backwards"
Click to expand...
Click to collapse
The wiping cache part is actually a part of odin download process. Everytime when you flash a new firmware in odin, the odin bootloader will invoke some scripts stored in /cache within recovery mode, and then wipe out these scripts / the whole partition as they are no longer needed.
However the wiping /data part is actually an essential part of firmware update and you should do it on your own if you are using CWM based firmware. This is because if you flash a firmware via odin, the data partition gets wiped after the device rebooted.
tbh it should be safe if you didn't wipe the /cache partition but not for the /data partition. Just some usls scripts and T9DB left behind in /cache. But incompatible binaries may still stays in /data if you didn't wipe it.
Sent from my GT-I9103 using xda app-developers app
I would like to install CM7 alpha9 MTD from this thread http://forum.xda-developers.com/showthread.php?t=2309390
The process I imagine is as following:
- backup things (I'm not sure how exactly this part works, if you know how to backup application data please help)
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar kernel with ODIN without repartitioning (as PDA I'm guessing, unless there's an option for "kernel" in which case it's kernel, which one is it? )
- boot to recovery
- format /system, /data, /preload
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- install SuperSU ? is this necessary with CM? Although I have doubts, as it was never mentioned unlike for Omni, so I guess not for this one
- reboot phone
- enjoy CM7
So basically I'm asking, am I missing out on anything basic but important that would result in bricking? And
- how to backup application data to be retrieved after flashing
- is the kernel a "PDA" or is there another thingy for it in Odin that needs be done?
- do you need to install any previous versions of CM7 for this MTD thing to work?
- does the kernel provide a recovery with which this ROM can be installed?
If you managed to get to the end, thank you - And thanks in advance for the help
Installing a rom
Zhuinden said:
I would like to install CM7 alpha9 MTD from this thread http://forum.xda-developers.com/showthread.php?t=2309390
The process I imagine is as following:
- backup things (I'm not sure how exactly this part works, if you know how to backup application data please help)
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar kernel with ODIN without repartitioning (as PDA I'm guessing, unless there's an option for "kernel" in which case it's kernel, which one is it? )
- boot to recovery
- format /system, /data, /preload
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- install SuperSU ? is this necessary with CM? Although I have doubts, as it was never mentioned unlike for Omni, so I guess not for this one
- reboot phone
- enjoy CM7
So basically I'm asking, am I missing out on anything basic but important that would result in bricking? And
- how to backup application data to be retrieved after flashing
- is the kernel a "PDA" or is there another thingy for it in Odin that needs be done?
- do you need to install any previous versions of CM7 for this MTD thing to work?
- does the kernel provide a recovery with which this ROM can be installed?
If you managed to get to the end, thank you - And thanks in advance for the help
Click to expand...
Click to collapse
Reboot to recovery, make a backup (you'll find in the menu)
Make a full wipe(in recovery)
- install the ZIP of the ROM: https://cm7-i5800.googlecode.com/files/CM7.2.0-GT-I5800_Alpha9_MTD_CWM.zip
- install the ZIP of the google apps for 2.3.7: http://www.devfiles.co/download/wBDwQIzb/gapps-gb-20110828-newtalk-signed.zip
- flash the https://cm7-i5800.googlecode.com/files/CM7_Kernel_MTD_OC1Ghz.tar
Install all these 3 zip with One Package ticked
Reboot and enjoy
Good luck
to install CM7 alpha 9 MTD you first need to be running CM7 alpha 9, which you flash with ODIN http://forum.xda-developers.com/showpost.php?p=14240212&postcount=1
then follow the instructions in the previous reply from sakenas to update to CM7 alpha 9 MTD using clockwork mod recovery.
only flash the 1ghz kernel after you have updated to CM7 alpha9 MTD.
you flash the kernel with ODIN using the one package method, exactly the same way you will have flashed CM7 alpha 9.