Database Info

Bionix Black Ice Voodoo, Ext4, Bali3.1uv Guide

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

How Can I Switch/Update my Kernel/CWM/ROM?

With the recent update of CWM/PBJ kernel I'd like to update to the latest ones and I'd also like to switch ROMs to test some other ones out. Can someone guide me through this? I've never switched before I just followed (http://forum.xda-developers.com/showthread.php?t=1122657), that's it(as far as flashing and such goes). I'd just like an easy to follow guide on updating the Kernel/CWM and installing a new ROM(If and when I'd need to disable Voodoo, if flashing something will reset all my contacts/apps, etc) I'd really appreciate it and thanks will be in order for anyone and everyone who is helpful :]
Info: I'm running 6/15 PBJ OC kernel with 1.8.5 Gummycharged ROM

There's not much to it. kernel and Rom can be updated in CWM.
Download the rom you want to flash to /sdcard (root of your sdcard)
reboot into recovery. If you do not have the option holding down the power button and hitting restart. Dl a terminal emulator and type:
Code:
$su (to gain root)
#reboot recovery
Wipe Cache and factory data reset
Go to advanced: Wipe Dalvik cache and battery settings
scroll to flash with a zip
choose: select zip from sdcard
choose the zip that you downloaded
once the install is complete reboot phone. let rom install
Follow same thing for Kernel. Just make sure you remember what the name of your kernel is.

dragonstalker said:
There's not much to it. kernel and Rom can be updated in CWM.
Download the rom you want to flash to /sdcard (root of your sdcard)
reboot into recovery. If you do not have the option holding down the power button and hitting restart. Dl a terminal emulator and type:
Code:
$su (to gain root)
#reboot recovery
Wipe Cache and factory data reset
Go to advanced: Wipe Dalvik cache and battery settings
scroll to flash with a zip
choose: select zip from sdcard
choose the zip that you downloaded
once the install is complete reboot phone. let rom install
Follow same thing for Kernel. Just make sure you remember what the name of your kernel is.
Click to expand...
Click to collapse
That works a treat thank you.

Easier way to get into CWM: hold down Power+Volume Up+Home until you see SAMSUNG, let go, and you'll boot straight into recovery. No need to mess around with terminal commands.
Also, when flashing a kernel only (not a ROM), there's no need to wipe data.

[Release]FeaMod Recovery 1.4 - based on CWM Recovery v. 5.5.0.4.

I've ported the CWM Recovery v. 5.0.2.7 to the Samsung Galaxy I9001 device.
Download it here and follow the instructions to install it. I will post any changes or updates again in this very first post.
Disclaimer: Flashing software onto your device might void your guarantee and may brick your phone. Use the attached software on your own risk. I am not responsible for any bricked device due to this software. You've been warned.
Credits and huge thanks go to:
Koush - for writing the original ClockworkMod Recovery
Ilarrain- for patching graphics.c for the Galaxy Ace device
YardE - providing init.d support to the custom kernel
Riversource - for providing scripts which make the handling of smd files super easy
All the users on this forum who have tested my former versions and helped to debug it - you're great
Are there any differences to "stock" CWM recovery which I can see?
Yes, there are. I've removed additional "No"'s in some functions. I've also changed the background logo and the name of the recovery (though "CWM Recovery" is still there due to make proper credits and copyright thing things). And of course there is the custom kernel included!
How to install/update
If you already have a FeaModRecovery version on your device it's simple:
Download one of the update.zip packages (starting with version 1.3) and copy it to one of your sdcards. Reboot into recovery and install the package (install zip from sdcard -> choose zip from ...).
If you're still on stock recovery or another one follow the the step-by-step instructions on the bottom of the post.
What about the version numbers?
The first number represents major updates (for example update to CWM 6 thus FeaMod v. 2)
The second number represents minor updates. For example if CWM goes up to 5.0.2.8 or I change something on my version.
The third number on some versions represents the kernel since it's a custom one and included in the whole package. So if only the last number changes, I have made "only" changes to the kernel.
Downloads
SMD files to flash via Odin
download FeaMod v1.1: http://www.mediafire.com/?oxxn0676fikkdaw
download FeaMod v1.2: http://www.mediafire.com/?u9996yn6i7rc92z
Hint:
For those who experience boot loops. Before you flash a new version copy the content of your external sdcard onto your pc and format it afterwards. This should help. After you've successfully flashed and rebooted into your system you can copy the files back on your external sdcard.
zip files OC/UV kernel to flash via FeaMod Recovery
WARNING:
Applying the FeaMod Recovery with the FeaCore_OC/UV kernel is dangerous and may brick your phone. In any case it will drain your battery faster when running on 1.8 GHz all the time. Only install it when you know what you are doing! Otherwise install a package without a OC/UV supporting kernel.
FeaMod Recovery 1.3.1 with FeaCore Phoenix OC stable release: http://mediafire.com/?al9s0abvdjrmg6e
FeaCore Phoenix includes:
-BFQ I/O scheduler 2 r1
-SIO I/O scheduler
-OC up to 1.8 GHz
-smartassV2 governor (ondemand is default)
-JFS and CIFS support
-tun included
-bootanimation support
-new boot sound
- I8150 GPU librarys
-cleancache
FeaMod Recovery 1.4 with FeaCore Phoenix OC stable release: http://www.mediafire.com/?jqfbvxflev1jcoz
zip files without OC/UV kernel to flash via FeaMod Recovery
FeaMod Recovery 1.3.1 with FeaCore Phoenix nonOC stable release: http://mediafire.com/?5unogie5i58x85r
FeaMod Recovery 1.4 with FeaCore Phoenix nonOC stable release:http://www.mediafire.com/?ben9s5a8bz1d3gc
if you wanna change your bootanimation, copy your downloaded bootanimation.zip to /system/media/sanim.zip (yes you have to rename it to sanim.zip). Change the modus to 644 (rw-r--r--).
How to change the bootanimation:
Copy the bootanimation.zip to your sdcard and start adb shell:
Code:
mount -o rw,remount /system
cd sdcard
dd if=bootanimation.zip of=/system/media/sanim.zip
chmod 644 /system/media/sanim.zip
Changelog:
FeaMod v.1.1:
+ Performing a factory reset aka wipe data now doesn't delete the external sdcard anymore.
+ Performing a backup with no changes in the mount menu will automatically backup .android_secure as well.
+ The external sd card will no longer be "backuped" unless you manually mount the sd-ext in the mount menu.
FeaMod v.1.1.1:
+Kernel changes: initd support - implemented by YardE. BFQ I/O Scheduler implemented by me
FeaModRecovery v.1.2:
-Included the rest of the changes made by Koush
-You can now select wheter you wanna make the backup onto internal or external sdcard
-I've decided to let go the backup of the external sdcard (save .android_secure of course). Because it can destroy your internal sdcard when not properly handled and backing up the external sdcard on the external sdcard doesn't make any sense at all.
FeaModRecovery v.1.3:
- fixed a bug which led to a md5 mismatch when recovering only single partitions (advanced recovery).
- reimplement the reboot into recovery option. This option now makes sense again (see next point).
- I provide you from now on with update.zip packages to update FMR from within an already installed FMR.
FeaModRecovery v.1.4:
- https://github.com/CyanogenMod/android_bootable_recovery/commits/ics/
Kernel (FeaCore_1.0 and FeaCore_1.0_OC/UV):
- update to jhash3 (for better reliability on data connections)
- implemented BrainFuck Scheduler as main scheduler (CFS is gone for the moment)
- implemented interactive governor (ondemand is still default and already very aggressive)
- implemented BFQ I/O
- init.d support (thx to YardE)
Kernel FeaCore Phoenix (OC and nonOC):
-jhash (battery drain is too high with jhash3)
-CFS as CPU scheduler
-SmartassV2 as new governor (ondemand is default)
-CFQ, BFQ, SIO and Deadline as I/O schedulers (SIO is default)
-supports Boot animation
-custom Boot sound
-cleancache patches
-I8150 GPU libraries
How to use
Start the FeaMod Recovery by pressing your Power Button and the Volume Up button simultaneously. Hold both keys until the Samsung Logo appears. Release both keys after additional 2-3 seconds and wait. The system now boots into FeaMod Recovery.
Navigate in the menu: Volume Up/Volume Down buttons
Select item: Menu Button
Return to start screen: Return button
Additional hints
Old versions (all versions until v.1.1.1): To backup your external-sd too, you need to mount the sd-ext partition in FeaMod Recovery:
Select mounts and storage -> mount /sd-ext.
Warning:
Don't backup your external sdcard if its content is larger than the space on your internal sdcard left!!!
If not manually mounted only your apps on the sd-ext will be saved.
In case the system won't recognize your external sdcard: Copy the content of your external sdcard to your PC and format it within your ROM. Copy the files back onto the newly formatted external sdcard. Thx to Igor_999 for stumbling across that problem
Sources on github:
https://github.com/manveru0/FeaMod-Recovery
Have fun with it!
Do it step by step ;-)
For Odin related things, look also at the attached image.
Important: You have to install busybox under /system/xbin/ in order to get the init scripts working.
Get "Busybox Installer" from the market. That version let you choose the location to install it.
1. If you don't have at least XXKP4, download it from samsungmobile (you need to register, but it's worth it)
Browse through the forum and go to our devices, there you'll find the ROMs. If your comfortable with your ROM
go to step 3.
2. Download Odin 4.43 from here and flash the files. If you have a one package file, download AriesVE.ops from this post and select that one in Odin
under OPS file. If you downloaded XXKP4 select the bootloader.tar as the BOOT file, the MODEM file as the phone file, the PDA file as the PDA file and the CSC file as the CSC file. Flash it and wait until your phone has rebooted back into the system.
3. Download FeaMod Recovery v.1.2.
4. Open Odin again and select the AriesVE.ops as the OPS file. Tick the one package option under OPTION. The select the FeaMod file as the One Package file. Flash it! After 10 to 15 secs your device will reboot into your system.
6. Copy the Universal Adrenaline v.13 zip file (download it from here: http://forum.xda-developers.com/showthread.php?t=1236779) to your internal or external sdcard.
5. Shut your device down and reboot into FeaMod Recovery v.1.2. by holding the Volume up and Power Button simultaneously until the Samsung Logo appears, hold it for 2,3 seconds longer and release both buttons. Welcome to FeaMod zone :-D
6. Make a full backup either to your external or internal sdcard (look at the options you got) just to be sure.
7. Go to mount and storage -> mount /system
8. Go to advanced and select fix permissions.
9. Go to install zip from sdcard and select your fresh copy of adrenaline shot v. 13.
10. Reboot into system.
you got it! You now have FeaMod Recovery v.1.2. with the latest kernel from YardE and me which supports init.d and has BFQ as the default I/O scheduler. And you should have the applied adrenaline shot by now. Test it either with a terminal (you should have the /system/etc/init.d folder) or by the quadrant benchmark (you should get at least 2500 points). In case there are any questions left, ask for.

Nice. I just flashed it and its backing up right now. It seems to work like a charm. Thanks!

it's looks like this right??

hi. sorry i don't get it. what is the function for this? is it to backup my current ROM?

OK, I had a bad day today, but this made my day!
Thank you sooo MUCH!
So, now... Custom ROMs much more easily?

budakmaran said:
it's looks like this right??
Click to expand...
Click to collapse
Yes, thats correct!

AWESOME
I've said it before and i'm saying it again You are awesome!!! Thnx a lot.
And also a big thank you to netchip without whom i dont think we could have had this
I'm soooo happy! now cyanogen mod to look forward tooo

Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001

Blumdum said:
Nice cwm works but somehow my sdcard is causing problems.... I will format it in windows and try it again
Because the problem is that my phone freezes and turns off when my sdcard is in my device
Sent from my GT-I9001
Click to expand...
Click to collapse
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext

sweeeeeeet ill try this later looking forward to cyanogen mod now we have working cwm

manveru0 said:
You can also format your sdcard in CWM Recovery if your phone doesn't freeze in CWM:
mounts and storage -> format /sd-ext
Click to expand...
Click to collapse
ok the ext-sdcard seems to work after i formatted the card
just have to copy back the files

Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.

traedre said:
Hi manveru0,
wonderful job dude! Thanks a lot! (I've clicked on the thanks button but when you see the number of users on this part of the forum I dare write you a note )
I've installed and backuped my device and it worked like a charm.
Click to expand...
Click to collapse
you are welcome. Thank you, good to hear

Am I right that there is init.d support included?
Sent from my GT-I9001 using XDA App

Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.

Works like a CHARM! LOVing it!

Very nice work! There is one problem. Members from the site 4pda.ru actively using CWM. Only for Skype both cameras are becoming as rear, front camera disappears. The guys were asked to write about this issue. It is strange that this is not who did not notice. Itself is not using Skype. Check it out please.

quest221 said:
Nice work! Thanks for all the guys!
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Hi,
the file I downloaded from http://www.mediafire.com/?1wbb668gs2t7d0k has a different MD5.
Click to expand...
Click to collapse
Yep, that's perfectly okay because I have uploaded a new file with a fixed bug yesterday evening. See also the first post

manveru du bist ein konig
thanks for one package
i will test it today
btw what for a cpu government was there setted up before?

problem this cwm in skype. 2 back camera, no working front camera, only back... fix it please.
sorry my english...

[Released][ROM][ODIN] ICS Stock firmware XXLQ9 repacked with CWM 6

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

[Q] help with custom ROM installation process of CM7 a9

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.