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
Do you also need to do this before flashing a new kernel via CWM? Or is this only needed when you flash a new rom? And another question: what is the fastest and most stable kernel for Gingerbread Galaxy S Plus Stock Rom? And if I do everything like the guide, is there no risk? Thanks in advance:
Do this every time before flashing a stock- or custom-rom!
Attention!
You will delete everything on your phone! Your phone will not even be able to boot! Only Clockworkmod and the Download-Mode will be left! (Your SIM-Card will be untouched)
Please make sure that you saved only your backups on another device before formatting your phone (like on your computer)
This is the best method for using the full experience of every custom rom! I recommend this method because in the past a lot of users had issues with custom roms. They had installed a lot of different custom roms before and they didn´t format their phone correctly before flashing the new rom. This caused a lot of problems
Enter in the Clockworkmod
Choose "advanced"
Choose "Wipe Dalvik Cache"
Go back to the main-menu by pressing the back button
Choose “Mounts and storage”
Select all after all
Format /system
Format /cache
Format /data
(Format /emmc)
(Format /sdcard)
Formating "emmc" and "sdcard" is not a duty! You will need it if you installed a mod on your internal or in your external card
Hi everyone,
I have been thinking of selling my Infinity but I need some confirmation in some things with regards to wiping the device clean.
I am currently running the latest CROMI-X. So what I wanted to do is wipe everything in my internal storage (all the datas or any kind of prints that shows my usage) and then flash back the latest CROMI-X.
So a couple of things in wipe. I am using TWRP 2.5 as of the moment. So if I wanted to achieve the one I mentioned above which kind of wipe should I do?
If I go to Advanced Wipe: I can see that Dalvik Cache, System, cache, Data and Micro SDcard is present there... If I go ahead and check all of these (except for the Micro SD Card) I believe that I this would also delete the OS itself. Am I correct? If this does it, will I still be able to install a ROM for my infinity? There's also the option of Format Data,which I think wipes clean my internal storage (pictures, videos, etc). This won't affect the System, right?
If you guys have a better suggestion on how to actually do this, please let me know as well. I apologize if there's a lot of question here... I just wanted to make sure that I am doing this right as I don't want to brick my device before actually selling it. Thanks.
To delete all user data, format /data. This automatically includes dalvik-cache and /data/media aka /sdcard. You don't need to format /system as it contains only the ROM.
If you are paranoid that a potential buyer could use "undelete" tools and piece together fragments of your data on the block level, then before formatting /data, you can completely overwrite the data partition from the recovery with the following command (in the "advanced" menu or via adb shell): "dd if=/dev/zero of=/dev/block/mmcblk0p8 bs=256k".
Prerequisites:
You need to be on the 10.6.1.14.10 bootloader
You need to know how to flash a recovery
Some background reading on f2fs: http://en.wikipedia.org/wiki/F2FS
Step 1:
Backup all your data off the tablet because it will get wiped!!
Step 2:
Install a recovery that supports conversion to the f2fs file system
You can use the official TWRP 2.8.x from here:
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Do not use TWRP 2.8.5 - it has a bug with the f2fs conversion - or 2.8.6 for that matter. It has another bug: won't reboot to anything from recovery...
For Transformer users I would highly recommend to install @lj50036 TWRP Kang version from here:
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
His Kang TWRP allows you to format/convert/backup external partitions or entire cards which will come in very handy for data2sd or rom2sd users.
It even supports the dock SD!
Step 3
Flash your chosen recovery in fastboot and reboot.
Optional but recommened
Since you are at it anyway I would recommend you format your /data partition before you convert to f2fs. The TWRP build-in "Format data" option does a "a secure erase" which trims and wipes every single block. A great way to start with a fresh and clean data partition. This process takes time - could be upwards of 60 minutes - do not interrupt it!!! You find the option under the Wipe menu
Step 4:
Enter TWRP, choose Wipe > Advanced Wipe
To Convert INTERNAL /data to f2fs
Check the box for "data"
Tap "change or repair file system"
Tap "Change file system"
Tap "F2FS"
Swipe the button
DATA2SD/ROM2SD users only:
To Convert EXTERNAL /data to f2fs (with lj's Kang TWRP TF700T only - official TWRP does not support this)
Check the box for Ext/data
Proceed as above
Step 5
Go back to TWRP Home screen, and reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!! Like: your microSD
Notes:
With /data on f2fs you need to run your ROM with a kernel that supports that file system. Read the OP of your ROM thread
Convert ONLY /data to f2fs. Do NOT convert /system (or anything else for that matter)
If you forma /data back to ext4 for any reason it will take up to 90 minutes. Do not interrupt it!!!
DATA2SD/ROM2SD ONLY
If you have the official TWRP installed and do not want to flash lj's Kang TWRP, you can - as always - use the data2sd1.zip/rom2sd1zip to have TWRP act on your external partitions.
MINE ......
Cool!
berndblb said:
Convert EXTERNAL /data to f2fs (lj's Kang TWRP TF700T only)
Check the box for Ext/data
Proceed as above
5. Step
Go back to TWRP Home screen, and reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!!
Click to expand...
Click to collapse
Convert EXTERNAL /data to f2fs
-- > ??? Is this a folder or a partition as stated in " post #2 Using GParted to setup a micro SD for ROM2SD or DATA2SD support"
reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!!
--> ??? It must be on external, I presume?
Where could it be located? If on external i suppose it is on:
--> ??? 14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
eRPeeX said:
Convert EXTERNAL /data to f2fs
-- > ??? Is this a folder or a partition as stated in " post #2 Using GParted to setup a micro SD for ROM2SD or DATA2SD support"
Click to expand...
Click to collapse
It's the second partition if you are running data2sd/rom2sd
data2sd:
1. partition fat32 = your microSD storage
2. partition f2fs (or ext4) = /data
rom2sd
1. partition fat32 = microSD storage
2. partition f2fs or ext4 = /data
3. partition ext4 = /system
[*]reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!!
--> ??? It must be on external, I presume?
Click to expand...
Click to collapse
The fat32 partition on the microSD (or just plain microSD if you don't run data2sd/rom2sd) is probably the safest place, yes.
Where could it be located? If on external i suppose it is on:
--> ??? 14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
Click to expand...
Click to collapse
Yes
berndblb said:
It's the second partition if you are running data2sd/rom2sd
data2sd:
1. partition fat32 = your microSD storage
2. partition f2fs (or ext4) = /data
rom2sd
1. partition fat32 = microSD storage
2. partition f2fs or ext4 = /data
3. partition ext4 = /system
The fat32 partition on the microSD (or just plain microSD if you don't run data2sd/rom2sd) is probably the safest place, yes.
Yes
Click to expand...
Click to collapse
So for f2fs you always need a Gparted formatted SD.
f2fs only on internal /Data is not possible?
Sure it is. Read step 4
I just only converted Internal /data to f2fs.
Flashed beta 4.
Seems to be possible to have f2fs only on internal.
eRPeeX said:
f2fs only on internal /Data is not possible?
Click to expand...
Click to collapse
berndblb said:
Sure it is. Read step 4
Click to expand...
Click to collapse
eRPeeX said:
I just only converted Internal /data to f2fs.
Flashed beta 4.
Seems to be possible to have f2fs only on internal.
Click to expand...
Click to collapse
Where does it say you can't????????????????
Edit: Ahhh! I see where your thinking went off track. You thought you had to convert both internal and external data for f2fs to work, right?
Nope - external data only concerns data2sd/rom2sd users. Edited OP to make that clear - I hope.
berndblb said:
Where does it say you can't????????????????
Edit: Ahhh! I see where your thinking went off track. You thought you had to convert both internal and external data for f2fs to work, right?
Nope - external data only concerns data2sd/rom2sd users. Edited OP to make that clear - I hope.
Click to expand...
Click to collapse
Yes, you could read my mind.
Just thought I'd share my experience, in case someone else makes the same mistake I did ...
I put the card into my computer and ran gparted to create the partitions. I fiddled with it for a while, resizing partitions while trying to decide how much space to allocate to each and what format to use for /data. I ended up with what graphically looked like the right layout:
I---sdcard---II--------------data--------------II---system---I
The rom2sd install seemed to go fine (Crombi-kk at the time). However I couldn't get it to boot.
Turns out in my fiddling I managed to get the second two partition table entries switched - partition 1 was fine, partition 2 pointed to the rightmost block graphically, parition 3 pointed to the middle block. I don't really know whether it was the installer or TWRP that got confused, or if it installed ok but the boot got confused.
In any case, deleting the partitions and re-creating them in order worked.
I have Zombi-X on a TF700T. I picked the F2FS option during install but didn't realize I had to have the /data partition formatted to F2FS first. So I'd like to minimize my update time. Can you tell me if this is how to proceed?
I have TWRP 2.8.4.0 already installed,
When you say backup data do you mean do a TWRP backup of the system/data/boot or just the /data section?
Or do you mean copy files to an SD card or PC?
I would then do the "optional" format of the /data partition using the existing data format ext4.
Then choose Wipe > Advanced Wipe
Check the box for "data"
Tap "change or repair file system"
Tap "Change file system"
Tap "F2FS"
Swipe the button
"Go back to TWRP Home screen, and reflash your ROM"
Do I have to do this? I don't want to change anything, the original install had F2FS enabled?
If I do have to do it, do you mean TWRP "restore" the ROM backup (system/boot/data) or actually TWRP
"install" the ROM zip file?
Then I would TWRP "restore" the /data backup and the tablet would work like it did before the reformat or would I have to reinstall apps, photos etc.?
Thanks for your help.
The easiest would be if you nandroid system/boot/data to your microSD. You gotta have it off internal storage. Nothing in internal /data will survive a format.
Then do the formatting and convert to f2fs
Restore your nandroid
You may get a warning from TWRP that the nandroid is off a different file system but you can safely ignore it.
Now, I do not quite remember where in Aroma the f2fs option was, but I think it's on that page about data journaling... So I'm not sure what selecting that option in Aroma actually does and if it gets implemented when the preinit script finds an ext4 partition instead.
But you can try it. Just restore the nandroid, pay attention during boot and read the script under the penguins.
If then your nandroid doesn't run as expected, reflash the rom with the same options, then restore only data from the nandroid you made earlier (during restore just uncheck boot and system). That also would give you an identical installation to what you have now.
berndblb said:
The easiest would be if you nandroid system/boot/data to your microSD. You gotta have it off internal storage. Nothing in internal /data will survive a format.
Then do the formatting and convert to f2fs
Restore your nandroid
You may get a warning from TWRP that the nandroid is off a different file system but you can safely ignore it.
Now, I do not quite remember where in Aroma the f2fs option was, but I think it's on that page about data journaling... So I'm not sure what selecting that option in Aroma actually does and if it gets implemented when the preinit script finds an ext4 partition instead.
But you can try it. Just restore the nandroid, pay attention during boot and read the script under the penguins.
If then your nandroid doesn't run as expected, reflash the rom with the same options, then restore only data from the nandroid you made earlier (during restore just uncheck boot and system). That also would give you an identical installation to what you have now.
Click to expand...
Click to collapse
Perfect, thanks. I will let you know my results. Might be a few days away.
IIRC the option is to turn on/off data journaling (one or two "l"s?) on ext2/3/4 partitions, with a final option of "f2fs user" where journalling is unnecessary. But it will not automatically format to f2fs in any case.
Hello. Yesterday I rebuilt my TF700 from the ground up. My intent was to get to Zombi-Rom with data2sd, to get a performant system. Here's what I did:
- started with twrp 2.8.6.x and Zombi-Rom beta 6, internal data, nice but laggy
- created two partitions on my samsung class 10 microSD card using gparted: 1. FAT32 at approx 4GB, 2. F2FS at approx 24GB
- flashed lj's kang twrp 2.8.6.1 recovery to replace 'standard' twrp 2.8.6.x
- formatted internal data using the kang twrp to f2fs (but it only took a second?) (I think this step was unnecessary, I meant to go to data2sd...)
- i *think* i formatted the new f2fs partition on the ext sdcard again using kang twrp, but don't recall. Rem: it was formatted f2fs by gparted already...I may have assumed I didn't need to do it again.
- flashed Zombi-Pop Android 5.1 beta 6, choosing the only kernel which has _that in the name
-- choosing f2fs
-- choosging data2sd (the ultimate goal of the exercise - get rid of TF700's awful lags/freezes)
-- choosing overclock (said it was required since _that kernel is selected)
-- choosing rest of default options
However I find performance is worse? I am sure I have done something wrong.
I have no data to protect or worry about tryig to restore. Before I do it all over again, do the steps above look correct, or am I making a mistake somewhere?
Thanks in advance.
Some people - me among them - have reported that data2sd doesn't work that well with ZOMBi-POP anymore. I do not get any performance improvement out of it with the same card that did well on other roms.
Could also be just your specific card - hard to tell.
I see no mistakes in your procedure but did you at any point do the secure erase the "Format Data" option provides? Read the "Optional but recommended" section in the OP.
Try different kernels. I like the Omni kernel best so far.
So my advice is: format internal data, then convert it to f2fs again, flash the rom with the omni kernel and all tweaks.
My TF700 runs very well with those options but it's still slower than my TF701 or my HTC M8 (there's actually no comparison to the latter..) and it always will be.
This is a what - almost 3 year old device now. These roms improve it by 300% but nothing will turn the TF700 into a smooth-as-silk-under-any-circumstances device....
berndblb said:
Some people - me among them - have reported that data2sd doesn't work that well with ZOMBi-POP anymore. I do not get any performance improvement out of it with the same card that did well on other roms.
Could also be just your specific card - hard to tell.
I see no mistakes in your procedure but did you at any point do the secure erase the "Format Data" option provides? Read the "Optional but recommended" section in the OP.
Try different kernels. I like the Omni kernel best so far.
So my advice is: format internal data, then convert it to f2fs again, flash the rom with the omni kernel and all tweaks.
My TF700 runs very well with those options but it's still slower than my TF701 or my HTC M8 (there's actually no comparison to the latter..) and it always will be.
This is a what - almost 3 year old device now. These roms improve it by 300% but nothing will turn the TF700 into a smooth-as-silk-under-any-circumstances device....
Click to expand...
Click to collapse
Same here Bernd - I see no improvements with data2sd anymore on zombi-pop.
I think we got internal running as sweet as can be
Bernd and dags,
thanks for the input, and again for all the great work to get it running the way you and your teammates have. Wish I had your know-how. At any rate I re-built it as originally posted and it's now working well. Backed that up and am trying it on internal today.
One more, maybe trivial question - the version of Nova Launcher says 'mod'. I can't install any other wallpaper with it. (I use Nova all the time, never seen this before.) Do you know if there something in the mod that makes it the default zombi-rom wallpaper or nothing?
just fyi. cm13 has no option to decrypt once you've encrypted it, twrp cannot mount encrypted drives (atleast most of the time i've heard a few say it can that's why i tried it but 2.8.7.0 doesn't even ask for a password or try to decrypt in my case)
so pretty much once you encrypt your stuck with the rom you have unless you have this magical twrp that asks for decrypt password.
also to make things worse, twrp can't format and cm13 changes the sdcard path so although it sees the external sd it can't flash files from it (atleast on g3)
so the only way to fix is to boot into android, backup your internal storage to sdcard or computer
reboot into twrp run a manual format on /data/ from terminal command, then reboot, copy your twrp backup to internal sd, go back to recovery and flash backup, then copy internal sdcard files back to internal drive (from sd or computer backup)
the command to format is the following
mke2fs -T ext4 /dev/block/mmcblkXpXX (NOTE: REPLACE THE XpXX with the proper values for your device) you can find these values by asking in your device forums, or downloading a partition info app that will tell you and i'm sorry i can't remember the one i used, but this is the best way to be sure because even diff device variants sometimes have diff partition tables based on phone provider.
*edit* just for personal peace of mind i remind everyone that every device is diff and i cannot guarantee positive results but this 100% worked for me everything is back to normal.
I did this a few months back and ended up flashing factory images via adb and starting all over again which sucked
Very useful information. :good:
TWRP v3.0.0 can use the adopted storage device (encrypted SD card) now.
Seems it's been fixed because I am successfully using cm13 with twrp 3.0, albeit with visible performance loss.
I just want to say thanks a lot for this. I can once again mount my /data partition.