Database Info

[GT-P6200][CWMRecovery][ROOT]ClockworkMod Recovery and Root

****** USE AT YOUR OWN RISK *******
This is NOT SUPPORTED SOFTWARE. This is purely for my amusement and entertainment. I'm making it available to download for those who might like to examine my work, but if you install it, you are on your own. I can't even test this myself. (I don't have a GT-P6200.)
Seriously - this has not been tested enough for me to be happy with it, and I'm unable to test it myself. Please read the thread for the GT-P6210 for instructions, known issues, warnings, etc.
If you do decide to install this anyway, please let me know how it works out for you. If no one is using it, I WILL NOT MAINTAIN IT AND WILL DROP IT.
If people do start using it, and the reports are that everything is working okay, then it'll get merged into what I'm already doing with the other two 7 plus models (meaning it'll get updated as needed when they do.)
Again, PLEASE READ the thread for the 6210 for everything you need to know: http://forum.xda-developers.com/showthread.php?t=1379532
..and here's a link for a CWM recovery.
Link: http://www.mediafire.com/download.php?do5jkna3dpas1tq
Take care
Gary

Hi! I'm a placeholder.

garyd9 said:
Hi! I'm a placeholder.
Click to expand...
Click to collapse
Hi, Placeholder. I'm a placeholder, too. Good meeting you here.

Pm'ed you. went straight in CWM, looks nice. able to make a full backup and md5. fails to restore in the middle of restoring /data
also getting UDIDs are inconsistent , fixing permission is supposed to take care of this.
and Im pretty much factory reset after reboot.
EDIT: appears as if Location cache map app by remy in market I had set to block wifi and cell caches. restoring a backup in CWM got permissions error, trestoring /data fails and Im left with pretty much a factory reset. went back to market and reinstalled suspicious app, installed and still says caches blocked removed app, rebooted, made back up and successful restore! woo hoo! Thank You Gary!
Note: should we make a note for 7+ CWM users beware blocked location caches, or re-write recovery to take care of this, and/or email the app dev?
anyways, pretty excited. Thanks so much Gary.

Anyone else want to help test the CWM Recovery for this tablet? (GT-P6200 only)
The current tester has had mixed results, but it _may_ have been the result of a third party app causing problems. I'd like to get someone else to test in addition to ensure there aren't any other issues.
In order to test, I need someone who has "adb" installed on their PC, is comfortable with linux commands, already knows how to use adb for commands such as "adb shell, adb push, and adb pull", doesn't mind using ODIN to restore their tablet to a factory state if it soft-bricks, and already knows how to use ODIN and CWM Recovery.
As a side-note; the third party app that MIGHT have been causing the problem is "Location Cache" by "remydemy." I don't use this app myself, but apparently it has some function to block the google/android location caches and it appears to do that by messing with the permissions on the files... which is somehow causing an error when the recovery tries to clean the /data directory in order to restore.
Thanks
Gary

link posted for testing.

thanks again gary loving it.

when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
So i just used root ecplorer to delete entire contents of folder. : )
is this not linked properly or CWM issue, or is this normal function?
thanks so much for your help.

chrisrotolo said:
when I select wipe dalvik cache in CWM options it says dalvik cache wiped awfully fast. and after reboot and removing some bloatware.apks there are still loads of .dex files in /data/dalvik-cache including bloat that i removed.
Click to expand...
Click to collapse
I'll look into it. Please try this alternative to test that function: Boot your phone normally, and then reboot into recovery. Using the recovery menu, mount the /data partition. Then use 'adb shell' to shell into the device and manually look in the /data/dalvik-cache directory. Then "cd /" and from within recovery choose the advanced->wipe dalvik-cache. Then look in /data/dalvik-cache directory again to see if it did what it should have done.
It's possible, based on the ordering of your above description, that the dalvik cache rebuilt after you wiped it (during the reboot) but before you removed your bloatware.
Take care
Gary

thank you. Gary tried not to get Banned OK? we need you buddy. lol

chrisrotolo said:
thank you. Gary tried not to get Banned OK? we need you buddy. lol
Click to expand...
Click to collapse
Where you able to run those tests yet?
thanks
Gary

not as of yet, sometime today though.
---------- Post added at 03:13 PM ---------- Previous post was at 02:23 PM ----------
so yeah, you must be right. dalvik-cache was full with /data mounted. cd / then wiped dalvik from CWM, which finishes in a split second; a list (ls) shows no dalvik-cache folder after wiping, completly gone.
Answers my question.
One other issue I ran into, that you're may be aware of is somehow I disabled the power button in CWM, it said something about back button disabled. I think I had to hold power for 10 sec. to reset device.
Thanks.

chrisrotolo said:
...somehow I disabled the power button in CWM, it said something about back button disabled.
Click to expand...
Click to collapse
That one I'm not sure of and really can't help much with. No 'power' button means you can't select anything which would really be annoying.

it works great! instant root and cwm within 2 minutes! i highly recommend gary's method than the other one. i also don't seem to lose root access by clearing ram memory. SWEET.

Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?

lvsw said:
Not working:
- format internal sd-card
- update CSC
- installing pre-apps
how to remove CWMRecovery and install stock recovery?
Click to expand...
Click to collapse
formatting the internal SDCard isn't going to happen with this version of CWM (that's designed for GB.) Honeycomb devices don't have a seperate /sdcard partition to format. Formatting the "internal sdcard" can be done from within the settings menu via a factory reset.
The other two items aren't broken - they simply don't exist in CWM recovery, and probably never will... Is having the pre-loaded samsgung sample video and music files repushed to your device over and over actually more important to you than the ability to do a nandroid backup? Do you even know what the CSC is that isn't being updated?
Have you bothered to seach around BEFORE installing this? Have you bothered to search around AFTER installing it to find out how to restore to factory?
I'm NOT going to answer your specific question on the basis that it's been answered already and I honestly feel that a user of XDA needs to have the ability to SEARCH before posting.
Take care
Gary

worked like a charm...backup and restore works perfectly...
thanks gary !!!

Hey Gary-
Question -
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
I could just flash a new recovery from ROM Manager, but I don't want to screw anything up.
Thanks!
Sent from my Galaxy Tab Plus using Tapatalk

jeffcavicchi said:
Is it possible to get ROM manager to recognize the recovery flashed here? I'd like to flash the new version of CWM, which claims to fix the internal SD card problem, but when I install ROM Manager it doesn't recognize that I have CWM flashed.
Click to expand...
Click to collapse
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary

garyd9 said:
This recovery is CWM Based - it is not an official ROM Manager supported recovery. I have no idea what "internal SD card problem" you are referring to, as I had internal sd card issues resolved with this CWM-based recovery before I posted it (there's only a single version for the P6200.)
I'd actually advise against using the "ROM Manager" program on this device. It's not a supported device, and things can go terribly wrong when messing with recovery and firmware partitions that aren't explicitly supported.
Take care
Gary
Click to expand...
Click to collapse
Got it - sort of what I figured.
Am I wrong that Recovery still sees the external SD card as an internal SD card? I thought the last time I flashed a zip (boot animation) Recovery showed it as being on the internal card, even though it was actually on the external card. I could be wrong, though - and I don't have the device in front of me to check.
Not a big deal either way - thanks for the response, and your hard work!
*Edit*
Just realized I posted this in the wrong thread like an idiot - I have a P6210. guess that's what happens when you start posting things bc (before coffee).

[GUIDE] Flashing ROMs correctly, every time

***original post copied verbatim******************************************************************
So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers

Ah yes i get random freeze screen with some ROM installer

why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?

Very nice guide. Extremely helpful for beginners
Sent from my GT-N7100 using xda premium

And please have to say that use a wipe script it's such a kind of blasfemy ...

Alienator9191 said:
why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?
Click to expand...
Click to collapse
agreed
since nand ram has its life time of cycle. wiping the nand for more than needed is some kind of suicide mission to your droid....

I disagree. If you are the type that flashes a ROM 5 times a day then yes that might be a factor.... might be. Each android device I have owned I have flashed a ROM/kernel to it literally thousands of times and nothing was ever damaged because of scrubbing the disk too much and flashing to it too much. Sorry, but misinformed about just how robust these disks are.

It needs to a must read for noobs
Sent from my GT-N7100 using xda premium

Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.

First of all thz for this step-by-step guide, for newbie is useful.
Phistachio said:
Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.
Click to expand...
Click to collapse
I agree, why repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND...
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:

zenzip said:
First of all thz for this step-by-step guide, for newbie is useful.
I agree, why to repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND ?
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:
Click to expand...
Click to collapse
1 wipe is more than enough
plus this thread should be in general section

I never face any problem with these steps (surely more then 100 flashing)
1.Downoad and flash ROM with Odin (odin doesn't check md5??)
2.Reboot, nevermind if stuck
3.Reboot to recovery, wipe cache and data.
Thats it.
If your counter is already raised, first make sure you have stock kernel and recovery
Reset counter
Start from step 1 above.

**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard

BullHorn7 said:
**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard
Click to expand...
Click to collapse
Lol... this is Sheldon wiping style...
Inviato dal mio GT-N7100 con Tapatalk 2

My phone wont boot into Cmw recovery, Please help.

My phone is rooted (With Super One Click) and when tap the "boot into recovery" option in Rom Manager it just send me to the stock recovery (with Blue text and what not). I have flashed Rom Manager with my Sidekick 4g before I tried to boot into recover. Please, someone help me. The answer is probably right in my face, but my noobish eyes just cant see it. :crying:
Please don't bash me this is my first post. I made sure there wasnt any post like this before i started a new tread.

Don't use ROM Manager with Sidekick 4G as CWM doesn't work the same way. When you reboot you always go into Samsung recovery from where you gotta reinstall packages to 'fake flash' the CWM recovery. If it says permission denied, the recovery file wasn't pushed to /system properly. You gotta reinstall every single time .. till of course you install a custom ROM. I think most come with voodoo CWM which replaces stock recovery, allowing you to go into CWM directly when you go to Recovery.
Firstly you need root, which I'm assuming you already have. Then you have to move a custom recovery to your phone's /system to allow you to install unsigned packages. You can do this using root explorer (paid app, but its the most simple and easy way of doing it) or you can do it using other similar apps that give you R/W (read and write) access. You also need to have a custom recovery file, the update.zip which when you hit reinstall packages (given you pushed the custom recovery file to the phone's system) would bring up clockworkmod recovery.
Read the noob guide here -> link. Its REALLY good and gives you a step by step of how to root / get custom recovery and install custom ROM.
Go here -> link. For more in depth information about getting a custom recovery. And here -> link. for Krylon's recovery files (links on his thread aren't all working).
Edit: Looks like the links on Krylon's page aren't working .. if someone can give an alternative it would be great!

I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app

Those guided really helped me out I spent ages reading up different things so when I finally went and did it, I didn't face any problems!
Important notes:
1. Root, obviously I personally didn't use the latest edition of SuperOneClick (at the time) on the website, but the file the dev posted on his XDA Thread.
2. Don't use ROM Manager or any other 'one click' kind of recovery for this phone. You need to download a custom recovery file and update file (links above, thanks Krylon) and go into CWM Recovery through the official Samsung Recovery through reinstalling the custom update file. This is the only way to access Orange CWM. Most custom ROMs come with the Red Voodoo CWM which is permanent in the sense that when you go into recovery, you should go into CWM (Red), instead of having to go through Samsung.
3. Orange CWM (and some say Red CWM as well) has some mounting issues. Always remember to check your mounts such that System, Data (well just to be safe, all of the items in the list) always say UNMOUNT. Basically when its mounted, means CWM has access to the partition. It says UNMOUNT because it is MOUNTED. I know thats a bit confusing, but think of it like this - there is a light switch that says ON so when you press it, turns the lights on but then the writing changes to OFF because you need to push the switch to turn it off. Erm .. hope that helps?! Lol.
4. Basically if your partitions are showing up as MOUNT, means you need to MOUNT them. Otherwise whatever changes you did won't apply! Instead of getting confused like I did, just make sure the screen says UNMOUNT SYSTEM and so forth for the rest of the items on the list.
5. Before installing a custom ROM, I always wiped x 3, before and after. Means after checking mounts, wipe data / dalvik, etc. 3 times. So for me, after checking mounts I would go to wipe date - yes - done 1; wipe data - yes - done 2; wipe data - yes - done 3. Followed by wipe dalvik and whatever else you want to wipe. Then I'd check mounts again (they usually get unmounted after a wipe .. well for me they always have anyway) before installing the ROM. Oh, sometimes I installed the ROM twice. Then I'd check mounts, wipe x 3, check mounts again before finally rebooting and letting it stand still for around 20 minutes or so. I don't really know if there is a logic or if doing it so many times makes a difference but I know some other people have done this and (other than wasting time) it doesn't really do any harm (someone correct me if I'm wrong) so why the hell not? I think the basic reasoning behind double / triple wiping and installing is to make sure that the changes are properly written as sometimes the system still retains old data.
6. Some people have SD card partitioning issues apparent. I can't remember why everyone went around partitioning in the first place (it must have been for some important reason, completely slipped my mind right now .. I personally did it to link my apps / data to SD card and save internal memory / space) but I personally used Gparted to partition my card on a computer (rather than CWM on the phone as I've heard people have issues with this) and never had a problem.
But I think thats it. I know there is a lot of information but its really worth having a look at the guide and other posts on that thread as that and the ROM thread (I personally use GOV 3.2) really had me prepare for any possible issue beforehand so I started off in a position where I could avoid them.

WTF_IsA_Android said:
I'm thinking about ODIN my device and start over but this time following one of the guides provided. I got cwm working but now I get a long script of code with a error that saids that it can't mount this and stuff like that. Ill try to post a image to give you a little better look at my problem. And for some reason the cmw logo isn't coming up behind the orange text.
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
can someone update the sidekick 4g stuff everything is either dead or does not lead anywhere to download any of the required files, thanks.

[Q][HELP] convert EXT4 to F2FS

Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
lotherius said:
...on my 2012 Nexus 7 I was having a lot of lag issues using stock/Faux123. It was painfully slow at times, even just waking the screen. I converted to F2FS (data only, not system), and the problems evaporated. [...] It was slow before, then it was fast. I had tried multiple other solutions prior to F2FS that didn't work. Many other users on the N7 2012 have also reported the same experience.
Click to expand...
Click to collapse
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]

Narciso Neto said:
Hi all, I'm reading some things about f2fs vs ext4 and I'm really looking into it...
Recently, I've flashed a LOT of ROMS (CM10, 10.1, 10.2, Stock 4.1 and stock based ones) trying to get 'that smoothness' that I had some times ago, but it always started lagging 2 or 3 days after clean flashing.
I started to see things like this:
So this is exatcly the 'fix' that i'm looking for, if it really does bring it...
Can someone help to do this? I saw some kernels on development thread but I didn't get the convertion part... [N0ob]
Click to expand...
Click to collapse
Have you find solution?

I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.

Will it delete all the files in internal storage?

shsagnik said:
Will it delete all the files in internal storage?
Click to expand...
Click to collapse
Yes, it'll as we'll format the partition as F2FS. Make a backup if you have important data on there.

willianalberto said:
I found a tutorial (can't post links yet) that shows how to convert. You'll need the most recent TWRP for your device and a ROM compatible with F2FS (CM12 for sure is). You can use flashify to install the custom rom.
Boot into recovery
Make backup of your files (just for security reasons)
Go to Wipe > Advanced Wipe > Data > Repair or Change Filesystem > Change Filesystem > F2FS
I didn't tried it, but you can do the same thing with /cache partition
Restore your backup, if you did it
Go to Advanced > Fix Permitions
Reboot.
I'm going to test it and see if works.
EDIT: It works but DO MAKE a backup because it'll wipe all your data.
Click to expand...
Click to collapse
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.

jcooler said:
I have tried the this procedure on my tab 2, and was not able to get it working. I have done this on my old Galaxy Nexus phone, and it made a huge difference in the performance. I was really hoping I would be able to make this work on the tab 2.
I was able to convert the data partition to F2FS, using Android-andy's twrp 2.8.1f2fs recovery. Then flash CM12. But after a reboot, it came up to a screen saying "Encryption Unsuccessful", and the only option available is to reset tablet. When I choose to reset, it would reboot into recovery, the attempt to mount /data, but would fail. It would reboot before I could read the exact errors.
I tried several time to get this to work, but every attempt failed.
Click to expand...
Click to collapse
Have you tried converting AFTER CM boots the first time? Also, are you using the latest build? It can be TWRP's fault too (just read on a thread on ASUS) or maybe our device don't support F2FS yet.

I have managed 2 convert many ROMs for the tab 2. I've spent hours reading about it in the past. As far as I'm aware no lollipop ROMs can convert yet as u also need a custom kernel that supports f2fs. U should be able 2 convert most KitKat ROM s with the right tools. Its only about 4 lines of the updater script 2 edit then find a kernel that supports ur ROM and f2fs like agni,dhollmen or blackhawk. Youll also need custom recovery thats f2fs ready, theres a twrp and philz download around. pitty easy once you do it ab couple of times. Hope that helps u......

Are there performance improvements?

There was quite a bit improvement, first sign of any custom kernel for lollipop that support's f2fs I'll be trying 2 convert the ROM to see the comparison's. Think that might be a little time away yet tho........

I've opo and like to migrate on CM12 nightly with F2Fs but stopped on boot logo with AK kernel any suggestion??
-cm-12-20150312-NIGHTLY-bacon.zip
-AK.128.OPO.SKULL.CM12.zip
-formatted cache, data, system, sdcard as f2fs by philz_touch_6.59.1
what's wrong?

[Q] Incredibly slow to start but runs OK after that

Hello all,
I'm a bit of a newbie at this stuff, but I hope this is enough information:
I recently installed CROMBi-KK on my TF700T. I don't think I've done any other relevant "mods" and certainly none after changing the ROM.
The tablet is connected to the optional keyboard.
I think the hard drive is about 2/3 full. Not sure about SD card. (I haven't tried starting system without SD card installed.)
It typically takes 15 minutes to start up!!!!
But once it starts, in part thanks to using Cleaner Master to block automatic startup of many programs, it typically runs fairly well. If it gets laggy, I can use the "phone boost" part of Cleaner Master (or of similar functioning programs) to get it running fairly well again.
Can anyone please offer me advice on what to do in order to get to a reasonable startup time?
Thanks very much for any help!

That sounds as if you did not install CROMBi-KK clean or clean enough. Or you are on the wrong bootloader...
So post your bootloader version and recovery version, which rom you came from and how and what you wiped before installing the rom.
Start backing up all your data off the tablet, 'cause no matter what your answer is, I'm going to recommend you move to ZOMBi-POP anyway. And that takes a full format of data and a change of /data to f2fs.
CROMBi-KK is no longer supported for a good reason: ZOMBi-POP is much better - especially better over time where CROMBi tended to really bog down.
You should not use (and need) CleanMaster on this rom. That app is for stock roms loaded with bloatware.
Post the info I asked for and I can help you to get this tablet flying again
This may be some helpful reading: http://forum.xda-developers.com/showthread.php?t=2688891
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471

Info you request
Thanks for your help...how do I find the bootloader and recovery versions? I don't remember which ROM I came from. I want to say 4.2 but I don't know for sure.
What's the best way to back up data?
Thanks again!
berndblb said:
That sounds as if you did not install CROMBi-KK clean or clean enough. Or you are on the wrong bootloader...
So post your bootloader version and recovery version, which rom you came from and how and what you wiped before installing the rom.
Start backing up all your data off the tablet, 'cause no matter what your answer is, I'm going to recommend you move to ZOMBi-POP anyway. And that takes a full format of data and a change of /data to f2fs.
CROMBi-KK is no longer supported for a good reason: ZOMBi-POP is much better - especially better over time where CROMBi tended to really bog down.
You should not use (and need) CleanMaster on this rom. That app is for stock roms loaded with bloatware.
Post the info I asked for and I can help you to get this tablet flying again
This may be some helpful reading: http://forum.xda-developers.com/showthread.php?t=2688891
http://forum.xda-developers.com/transformer-tf700/development/rom-t3006593
http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Click to expand...
Click to collapse

Read the threads I linked to.
Bootloader: post 3 under the first link
Recovery: fire it up, read he header
Data: copy it to a microSD or PC
Sent from my TF700T using Tapatalk

Is this the info you asked for?
Sorry, was away for a couple of days...please let me know if this is the information you said I should get to you:
[UPDATE: Did Titanium Backup to SD card]
Bootloader (very tiny and hard to read): "US_epad-10.6.1.14.10-20130801" A03
TWRP 2.8.5.0 (found by using RCP boot option)
briefly on screen at restart, under 4 funny looking little birds:
[ 4.134409] preinit: ######### starting ###########
(and then more stuff, then a few lines of stuff, then)
mmcblk0p8: ext4
mmcblk1p2
mmcblk1p3
ro.cm.version=11.0-20140921-crombi-kk-tf700t
berndblb said:
Read the threads I linked to.
Bootloader: post 3 under the first link
Recovery: fire it up, read he header
Data: copy it to a microSD or PC
Sent from my TF700T using Tapatalk
Click to expand...
Click to collapse

You're good to go on the bootloader side. But TWRP 2.8.5 has a bug with the f2fs conversion, so if you want to go for ZOMBi-POP on f2fs you have to update your recovery.
Instructions are all in my f2fs conversion guide (3rd link I posted earlier).
But first make a nandroid of your CROMBi-KK installation - just in case you should not like ZOMBi.
Get the recovery and rom files together on your microSD, then
Flash the Kang TWRP by lj
reboot
format data in TWRP
convert file system on /data to f2fs
flash ZOMBi-POP
enjoy
Sent from my K00C using Tapatalk

So since I don't know what nandroid means and don't want to figure it out, I'm going to take your word for it that ZOMBi is better than CROMBi!
I'll work through this with your instructions and let you know how it goes.
Thanks very much!
berndblb said:
You're good to go on the bootloader side. But TWRP 2.8.5 has a bug with the f2fs conversion, so if you want to go for ZOMBi-POP on f2fs you have to update your recovery.
Instructions are all in my f2fs conversion guide (3rd link I posted earlier).
But first make a nandroid of your CROMBi-KK installation - just in case you should not like ZOMBi.
Get the recovery and rom files together on your microSD, then
Flash the Kang TWRP by lj
reboot
format data in TWRP
convert file system on /data to f2fs
flash ZOMBi-POP
enjoy
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse

Rossputin said:
So since I don't know what nandroid means and don't want to figure it out, I'm going to take your word for it that ZOMBi is better than CROMBi!
I'll work through this with your instructions and let you know how it goes.
Thanks very much!
Click to expand...
Click to collapse
A nandroid is a full system backup. In TWRP touch 'Backup", choose your microSD as destination (remember you will totally format your internal storage) and swipe the button. That's it.

It worked!
Still figuring out Zombi but it sure does boot up a lot faster.
Thanks so much for your help!
berndblb said:
A nandroid is a full system backup. In TWRP touch 'Backup", choose your microSD as destination (remember you will totally format your internal storage) and swipe the button. That's it.
Click to expand...
Click to collapse