Well, this is the fruits of my labor last night. Took the KG2 ODIN tarball and ran it through the dsixda rom kitchen.
Features that I have added(Haha, funny, huh?):
- Deodexed(Useable as a base for a custom rom)
- Rooted(Used Superuser like every other rooted rom)
- Updated busybox
That's about it...really. I don't need to add screenshots since everyone should know what stock looks like.
Only thing I need to really mention, is if you're using this on Orange CWM...CHECK CHECK CHECK your mounts.(In other words, make certain the mounts are correct)
Follow these instructions as per which CWM you're using. And if on the Voodoo(Red) CWM...disable voodoo or you WILL get a bootloop.
I'm not responsible if your phone is unrecoverable. You voluntarily flashed this yourself and are solely to blame if anything goes wrong. I did not hold a gun to your head and force you to download and flash this package, so don't expect me to replace your phone. Also, any bugs present aren't my fault. Blame Samsung. It is stock after all.
- Put zip file in your /sdcard
- Reboot into cwm recovery
- Wipe Data/Factory Reset
- Wipe Cache Partition
(Optional but recommended to prevent any minor issues)-Wipe Dalvik Cache from advanced menu in CWM
*Now before you Flash, Only if you are on the orange CWM, (Not RED voodoo CWM from Bali) if on red CWM ignore the mounts/unmount part*
MAKE SURE YOUR MOUNTS LOOK LIKE THIS: (Go to mounts and storage from CWM recovery)
UNMOUNT CACHE
MOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM - this is the ONLY mount you pay mind to, not Sdcard or anything else
- Now its safe to Flash the .zip
(AGAIN IGNORE UNLESS IF YOU ARE ON A RED VOODOO RECOVERY) after you flash, go back to mounts and storage and make sure your mounts look like this
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
(Optional but recommended)-Wipe Cache then Wipe Dalvik Cache from advanced menu in CWM before Rebooting.
(To First Time installers, System Needs to be set to Unmount, though it would really be mounted. If you do Not do this you will have a softbrick and will have to ODIN to stock and start all over ....) Once you have Flashed a Custom ROM or Bali 2.2 Kernel you dont have to worry about mounts
Irregardless of what the above says, it's best to worry about mounts anyways. And if it results in a bootloop after flashing this, boot into recovery(should give you the stock blue recovery[uses stock Kernel after all]) and clear all user data. It should boot right up after that.
Download: KG2-DEO-ROOTED.zip
SammaelAkuma said:
Well, this is the fruits of my labor last night. Took the KG2 ODIN tarball and ran it through the dsixda rom kitchen.
Features that I have added(Haha, funny, huh?):
- Deodexed(Useable as a base for a custom rom)
- Rooted(Used Superuser like every other rooted rom)
- Updated busybox
That's about it...really. I don't need to add screenshots since everyone should know what stock looks like.
Only thing I need to really mention, is if you're using this on Orange CWM...CHECK CHECK CHECK your mounts.(In other words, make certain the mounts are correct)
Follow these instructions as per which CWM you're using. And if on the Voodoo(Red) CWM...disable voodoo or you WILL get a bootloop.
I'm not responsible if your phone is unrecoverable. You voluntarily flashed this yourself and are solely to blame if anything goes wrong. I did not hold a gun to your head and force you to download and flash this package, so don't expect me to replace your phone. Also, any bugs present aren't my fault. Blame Samsung. It is stock after all.
- Put zip file in your /sdcard
- Reboot into cwm recovery
- Wipe Data/Factory Reset
- Wipe Cache Partition
(Optional but recommended to prevent any minor issues)-Wipe Dalvik Cache from advanced menu in CWM
*Now before you Flash, Only if you are on the orange CWM, (Not RED voodoo CWM from Bali) if on red CWM ignore the mounts/unmount part*
MAKE SURE YOUR MOUNTS LOOK LIKE THIS: (Go to mounts and storage from CWM recovery)
UNMOUNT CACHE
MOUNT DATA
MOUNT SDCARD
UNMOUNT SYSTEM - this is the ONLY mount you pay mind to, not Sdcard or anything else
- Now its safe to Flash the .zip
(AGAIN IGNORE UNLESS IF YOU ARE ON A RED VOODOO RECOVERY) after you flash, go back to mounts and storage and make sure your mounts look like this
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
(Optional but recommended)-Wipe Cache then Wipe Dalvik Cache from advanced menu in CWM before Rebooting.
(To First Time installers, System Needs to be set to Unmount, though it would really be mounted. If you do Not do this you will have a softbrick and will have to ODIN to stock and start all over ....) Once you have Flashed a Custom ROM or Bali 2.2 Kernel you dont have to worry about mounts
Irregardless of what the above says, it's best to worry about mounts anyways. And if it results in a bootloop after flashing this, boot into recovery(should give you the stock blue recovery[uses stock Kernel after all]) and clear all user data. It should boot right up after that.
Download: KG2-DEO-ROOTED.zip
Click to expand...
Click to collapse
Cool base.
Sent from my SGH-T999 using Tapatalk 2
I'll download this and maybe use it for my DangerZone rom. BTW, does flash work within the web browser?
ASDF.
Forgot to add the modified recovery file. So to anyone who uses this as a rom base or as a regular rom between 12/23/12 and whenever I update it...grab the /system/bin/recovery from any other custom rom and either adb push it to /system/bin or use a root file manager to paste it over the current on and reset the permissions to 775(I think)[Just check what it is before you use the second method]
And as far as I know, Flash should work. I haven't had any issues, personally.
Sent from my SGH-T839 using Tapatalk 2
Related
Is it simply wipe /data /system or do we have to do something like on the captivate and return to stock first?
How about if we switch kernels etc - does the process change?
Thanks
psufan5 said:
Is it simply wipe /data /system or do we have to do something like on the captivate and return to stock first?
How about if we switch kernels etc - does the process change?
Thanks
Click to expand...
Click to collapse
When switching ROMs, the easiest way is to do it with ClockworkMod Recovery. You download the .zip of the ROM you want to your SD card, boot to recovery, wipe data, cache (this step is only necessary when going from one ROM to another, not if you're just updating a ROM), and dalvik cache, choose install zip from SD card, point to the .zip you downloaded and install. If you have a kernel you want to install, then you boot after you flash the ROM, reboot to recovery, and flash the kernel .zip from cwm recovery
Hi all, I just flashed CM7 using the newest clockwork mod recovery. Now it says my internal memory is full. I havnt deleted anything internally since I got the phone. What is the best way to format that memory and reinstall a fresh copy of CM7?
Kaczman said:
Hi all, I just flashed CM7 using the newest clockwork mod recovery. Now it says my internal memory is full. I havnt deleted anything internally since I got the phone. What is the best way to format that memory and reinstall a fresh copy of CM7?
Click to expand...
Click to collapse
Go to recovery......in recovery go wipe cache, factory reset/data, go to mounts/storage and format system, data, cache....go to advance and delete dalvik cache..... then just install zip from sd, choose zip, flash taht **** and reboot your phone
Awesome!! thanks bud!
I don't mess with CWM wiping partitions anymore, I wrote a flashable script for that - a long time ago there was an issue with that on CWM 4.0.0.8
A member has confirmed that A01 wipe will be okay if you turn off and have no ROM installed, you will still be able to get to CWM and flash whatever you want.
A01 wipe will format /cache, /data and /system
B01 wipe will format /cache and /data
Use as needed.
I keep a backup memory card with my phone at all times that has A01 wipe, B01 wipe, and my original CWM backup of my stock system on it, in case I ever need to go back to stock if something goes wrong.
Attached are the scripts, just throw these on your sdcard and flash like normal in CWM if you need to, before installing a ROM or patch if needed.
Blue6IX said:
I don't mess with CWM wiping partitions anymore, I wrote a flashable script for that - a long time ago there was an issue with that on CWM 4.0.0.8
A member has confirmed that A01 wipe will be okay if you turn off and have no ROM installed, you will still be able to get to CWM and flash whatever you want.
A01 wipe will format /cache, /data and /system
B01 wipe will format /cache and /data
Use as needed.
I keep a backup memory card with my phone at all times that has A01 wipe, B01 wipe, and my original CWM backup of my stock system on it, in case I ever need to go back to stock if something goes wrong.
Attached are the scripts, just throw these on your sdcard and flash like normal in CWM if you need to, before installing a ROM or patch if needed.
Click to expand...
Click to collapse
hey Blue just outta curiosity has anyone confirmed having issues with wiping through CWM with the new recovery or has the issue carried over from the 4.0.0.8/9?
I'm pretty sure I don't remember anyone having issues directly with cwm 4.0.0.9, and it was only a problem with 4.0.0.8 - even then not everyone experienced it.
I haven't tried the new recovery available yet, I meant to get to it this weekend, but it doesn't look like i'll get a chance to fit it in my schedule. I haven't seen my lady in just over a week, so spending the weekend with her.
Hopefully over the next week i'll get a chance to bring myself up to speed with it, I don't expect to go back to 4.0.0.9 once I move up to the new CWM recovery.
Ok, with all of the talk about making sure folks do a full wipe before installing ICS, I would like to get some clarification on all of the different wiping methods and which is the best way...
I know of these ways:
1. Via custom recovery - you can wipe data, system, cache, etc.. individually.
2. Via holding Power+VolumeDown until bootloader text appears,, then wait until menu appears and select the Wipe Data option (instead of the cold boot option).
3. Via AARD SuperWipe full script
And then of course, there is the "Reset to factory defaults" in the OS itself...
Which is the best to use? I would assume the AARD SuperWipe full would be the most thorough as it recreates the partitions and everything (instead of just formatting them).
FOr users that have the ability, would an NVFlash of the OS be "more thorough" than CWM method?
Opinions/Experiences?
Thanks!
Don't use super wipe script. A lot of people reported having problems of some ROMs not flashing correctly after using it. There is no reason to use the "full" version anyway. It formats the /media partition(your internal storage partition) which you don't want to nor need to format.
Wipe Data in your #2 does pretty much the same thing as "Reset to factory defaults". They both wipe /data and /cache but do not touch /system.
The most thorough way of wiping that I use is via CWM.
I do all of this within CWM if I want to ensure a clean install of a new ROM and it has never failed.
- wipe data/factory reset
- wipe cache partition
- advanced / Wipe Dalvik Cache
- Mounts and Storage / format /system
I am not sure how NVFlashing a ROM does a clean install? As far as I know, it just flashes whatever it's told to flash. It wouldn't even touch /data if you were just flashing a ROM with it.
horndroid said:
Don't use super wipe script. A lot of people reported having problems of some ROMs not flashing correctly after using it. There is no reason to use the "full" version anyway. It formats the /media partition(your internal storage partition) which you don't want to nor need to format.
Wipe Data in your #2 does pretty much the same thing as "Reset to factory defaults". They both wipe /data and /cache but do not touch /system.
The most thorough way of wiping that I use is via CWM.
I do all of this within CWM if I want to ensure a clean install of a new ROM and it has never failed.
- wipe data/factory reset
- wipe cache partition
- advanced / Wipe Dalvik Cache
- Mounts and Storage / format /system
I am not sure how NVFlashing a ROM does a clean install? As far as I know, it just flashes whatever it's told to flash. It wouldn't even touch /data if you were just flashing a ROM with it.
Click to expand...
Click to collapse
I've tried ALL of the above methods - all with the exact same results, to be honest...
Even if I revert back to honeycomb (even after a full wipe), I STILL exhibit the reboot issues (it's not just me - look around). This was NOT happening before with the exact same version of Revolver. This tells me that there is still yet something else that was changed during the ICS updates. We know the bootloader was updated - i'm now testing ICS with the old bootloader.
Other than the bootloader, what else could have changed?? Unless they upgraded the firmware on a particular device during the ICS update (wifi chip, bluetooth chip, etc). Other than that, I just can't come up with an explanation as to why Honeycomb won't even run properly anymore!
Sent from my Transformer TF101 using Tapatalk
horndroid said:
I am not sure how NVFlashing a ROM does a clean install? As far as I know, it just flashes whatever it's told to flash. It wouldn't even touch /data if you were just flashing a ROM with it.
Click to expand...
Click to collapse
If you use the --create flag, nvflash will format ALL the partitions and then flash them. If you use the --download flag, it will just overwrite the partitions you send it.
That being said, I agree at your wiping method is more than enough. Most times, I don't bother wiping, especially data.
sent from my cyanogen(mod) vision
idk why im confused. can someone please verify. want to flash erikmm rom
ummu - unmount system, mount cache, mount emmc, unmount sdcard?
is this what we want to see and leave everything else the same?
if we did have to flash stock rom. do we mess with these again?
Yep to your first question. And if restoring a backup you don't need to worry about them. Otherwise I'm not sure? Sorry.
Sent from my SGH-T769
trevor7428 said:
idk why im confused. can someone please verify. want to flash erikmm rom
ummu - unmount system, mount cache, mount emmc, unmount sdcard?
is this what we want to see and leave everything else the same?
if we did have to flash stock rom. do we mess with these again?
Click to expand...
Click to collapse
Hey, I can answer your question
In erikmm's thread, he said:
erikmm said:
Installation Instructions:
1. Must have efs backup on desktop * just in case *
2. Nand Backup
3. Format System
4. Set Mounts to UMMU. *unmount cache, mount data, mount sdcard, unmount system*
5. Wipe Data/Factory Reset
6. Flash Rom
7. Reboot
8. Let the phone sit for 10 minutes then enjoy.
Click to expand...
Click to collapse
First, you want to flash this ROM. You should odin back to stock, and odin recovery ( for a full wipe )
Make sure Battery is full charged before odin these things
Second. Go to recovery. Volume up + Down + Power.
1.Backup ( of course )
2. After that, format system, try to format 3 times.
3. Go to Mounts & USB Storage
You'll see a lot of things. Make sure you check in this
unmount cache
mount data
mount emmc
unmount system
is correct.
If you see one of these option is different than erikmm said, you'll try to correct them. Ex: You see in CWM "unmount data", you can correct by press Power button to changed it to " mountd data "
And the same as another options
4. Make sure you correct right things in CWM. After that, do an wipe data/fatory resets ( 3 times, I think ) and flash erikmm's ROM in your SDcard
5. Reboot, wait for 10 minutes, and enjoy
Maybe the confusion is this... inside the "Mounts and Storage Menu" lists as follows...
mount /efs
unmount /data
unmount /cache
unmount /emmc
mount /sdcard
mount sd-ext
format /data
format /system
format /cache
format /emmc
format /sdcard
format /sd-ext
mount USB storage
+++++Go Back+++++
thus the UMMU stated is not in that order and what about the others?
Be safe and have fun.
You no longer need to mess with the mounts when installing erikmm's ROMs.
Hi !
I have flash CyanogenMod 9.1 beta 2 cooperve (galaxy ace s5830i). First I try it from CM 7.2 RC4 : flash kernel biels 4.0, reboot CWM after that mount data,system and install zip from SD card and reboot phone.
I try it from stock rom too - Download EXT4 tool, the Kernel and the Rom on device,
Flash on Samsung recovery Biels temp. CWM.
When you are on the Temp. CWM, flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS)
After the installation, flash my kernel you have downloaded before.
When the Kernel is installed, go, on the CWM, to advanced --> reboot recovery (this will reboot the device, and turn it on on the new CWM of kernel)
Wipe data, cache and dalvik
(IMPORTANT) Go to mounts and storage, and make sure system is mounted (will show unmounted), if it shows unmounted, click it twice, to make sure!
Go to install zip from SD Card, after that reboot phone.
In both cases i have got the same problem. In the first case rom boot up, but too many bugs, force closes...(It doesnt look like HW is fixed fully)
In second case, I got bootloop or rom boot up but it shows - setup wizard.it force closes on setup wizard.
What did i do wrong ???
bocseko said:
Hi !
I have flash CyanogenMod 9.1 beta 2 cooperve (galaxy ace s5830i). First I try it from CM 7.2 RC4 : flash kernel biels 4.0, reboot CWM after that mount data,system and install zip from SD card and reboot phone.
I try it from stock rom too - Download EXT4 tool, the Kernel and the Rom on device,
Flash on Samsung recovery Biels temp. CWM.
When you are on the Temp. CWM, flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS)
After the installation, flash my kernel you have downloaded before.
When the Kernel is installed, go, on the CWM, to advanced --> reboot recovery (this will reboot the device, and turn it on on the new CWM of kernel)
Wipe data, cache and dalvik
(IMPORTANT) Go to mounts and storage, and make sure system is mounted (will show unmounted), if it shows unmounted, click it twice, to make sure!
Go to install zip from SD Card, after that reboot phone.
In both cases i have got the same problem. In the first case rom boot up, but too many bugs, force closes...(It doesnt look like HW is fixed fully)
In second case, I got bootloop or rom boot up but it shows - setup wizard.it force closes on setup wizard.
What did i do wrong ???
Click to expand...
Click to collapse
EDIT:
DONT INSTALL AS YOU GOT 5830i ?!?! <----------------------------------------------------------------------------------------------