FP1 - All packages up to date

Nitro just released a new version of FP1 stock deodexed/debloated/rooted, that it, nothing else. So we now have the following:

-----------------------------------------------
ODIN DOWNLOAD:
http://www.mediafire.com/?d6x9p9lykprtq49
Instruction how to use Odin:
http://xdaforums.com/showthread.php?t=1372414

ClockMod(CWM): DOWNLOAD:
http://imnuts.net/zU2jkn
Instruction how to use Clockmod (cwm):
http://xdaforums.com/showthread.php?t=1587607
-----------------------------------------------
A. FP1 stock image (pure stock and kernel - factory stock, no root..nothing else) by Themortalwombat
http://www.mediafire.com/?zxnfxmmcoky81sz

B. FP1 radio update only - Just radio, no rom, no kernel ( https://www.dropbox.com/sh/jza13ebilffzyxx/fAbJhxD-wI/EP4DtoFP1Modem.zip ). by Dwitherell
Flash with CWM
*** Stock FP1 Kernel Only (ODIN version) - By Shrike1978 - http://www.mediafire.com/?ns38atiw1d7er5x
*** Stock FP1 Kernel Only (CWM version) by Dwitherell - http://goo.gl/pGgxT

And the rest of credits go to Nitroglycerine33
C. FP1 stock deodexed/bloated/rooted - No kernel (http://eclipserom.com/mods/click.php?id=89 )
D. FP1 stock deodexed/debloated/rooted - No kernel (http://eclipserom.com/mods/click.php?id=91 )
E. FP1 Deodexed/Debloated/rooted with Eclipse AOSP apps - No kernel ( http://eclipserom.com/mods/click.php?id=90 )
http://eclipserom.com/vforum/forumdisplay.php?39-Roms-and-Development

THEME for FP1:
F. FP1 Blue Theme for FP1 Deodexed/Debloated/rooted with Eclipse AOSP apps (The first theme ported for FP1 called True blue theme by ztkryan) -
Boot and shutdown animations added to this theme.
http://xdaforums.com/showthread.php?p=23955677#post23955677 . Flash with cwm.

G. FP1 Core Droid Theme for FP1 Deodexed/Debloated with Eclipse AOSP apps - By ztkryan
http://xdaforums.com/showthread.php?p=24217473#post24217473. Flash with cwm.

H. Purple Moon Theme for FP1 Deodexed/Debloated/rooted with Eclipse AOSP apps By ztkryan
http://xdaforums.com/showthread.php?p=24515816#post24515816

I. Additional Themes/Bootanimation for TweakStock and Eclipse - http://xdaforums.com/showthread.php?t=1532466

-----------------------------------------------
*** NEW CUSTOM ROM (No kernel)

ECLIPSE ROM 2.0 FOR FP1 -- (Rom only, no kernel) -- By Nitro -- http://eclipserom.com/vforum/showthread.php?997-ROM-FP1-Eclipse-Charge-v2-0-(4-3-12)
** Ad-on for Eclipse 2.0 - http://rootzwiki.com/topic/22855-lidroid-toggles-for-eclipse/

TWEAKSTOCK ROM 2.0 FOR FP1 (Rom only, no kernel) -- By Dwitherell -- http://xdaforums.com/showthread.php?p=24681087#post24681087
-----------------------------------------------

I want to keep all in one place to make them more convenience to everyone. because it's hard to trace back where they are!

SOMETHING EVERYONE SHOULD KNOW ABOUT FP1 (information collected from reading many posts, credit goes to OP):

*** Stock EP4D (Factory rom/kernel/radio) flash with ODIN:
http://www.imnuts.org/odin-packages/ - ODIN
look for this " EP4 (Android 2.3) CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 "

1. Issue with FP1 rom using custom kernel - If you are on FP1 and using custom kernel like PBJ, Tweakstock, Imoseyon 4.0, your wifi will not work. Currently there is no solution, some suggested methods,but didn't work. We just have to wait for a new/mod custom Kernel to support the Fp1 wifi. If wifi is critical to you and you want to stay on Fp1, you have no choice but use FP1 stock kernel.

2. Custom rom upgrade to FP1 deodexed/debloated/rooted rom (NO FP1 kernel) - If you are on custom rom with CWM installed and want upgrade to Nitro's deodexed/debloated/root or deodexed/bloated/root, "Easiest thing to do is take Nitro's stock deodexed/rooted/debloated or bloated rom and place it on your sdcard. Then use clockworkmod to flash this rom. Nitro has removed the script that overwrites the stock recovery in this rom so you do not need to worry about it coming back.

3. Custom rom upgrade to factory FP1 with root and cwm (with FP1 kernel) - If you are on Tweakstock/Eclipse and would like to move to FP1, first you have to ODIN back to stock EP4D, then download the Factory FP1 package (http://www.mediafire.com/?zxnfxmmcoky81sz), rename the this package to update.zip, place it on your SD card, then use STOCK recovery to flash this update.zip. Reboot phone then shut it back down then Odin cwm (0302 blue latest version- http://imnuts.net/zU2jkn) with "reboot" option unchecked, after completed, pull the battery, reinstall battery, hold down volume up+home+power to boot into cwm, flash Super user package zip (Superuser-3.0.7-efgh-signed.zip - http://www.mediafire.com/?dowo6gy34oclutq ). Reboot phone. Use root explore go to /system/ect/install-recovery.sh script, tab on mount R/W button (upper top). long press on the script and in the popup menu, select permission, unchecked all permission. Shutdown phone, re-Odin cwm again, once done reboot, now cwm should stick. If some how you lost root permission, download superuser fix from the market and run it.(no reboot required).

4. Cutom rom upgrade to FP1 radio only (NO FP1 kernel) - If you are on Tweakstock/Eclipse and just want to update the new FP1 radio, simply just download (http://bit.ly/GE6IVa) and flash it using cwm. Make sure mount /system before flashing (wipe cache/davik cache are recommended). The key here you must already on EP4D radio for this patch to work. You can update your modem to EP4D (EP4 modem can be found here -( http://bit.ly/uZljNM ) . Unzip and Odin this EP4D modem file before you flash FP1 radio with cwm.You can be on custom rom or kernel while flashing this. It should work fine.

5. How to root a pure stock FP1 and make CWM stick after reboot - Turn off your phone, use ODIN to flash CWM (0302 blue latest version - http://imnuts.net/zU2jkn) with "reboot" option unchecked,
After completed, disconnect the usb cable, pull the battery, reinstall battery, hold down volume up+home+power to boot into cwm,
(if you failed to boot into cwm and your phone boot up you have to redo the process). Now flash Super user package zip (Superuser-3.0.7-efgh-signed.zip - and su-bin-3.0.3.2-efghi-signed.zip (both can be download from here (look for Gingerbread) : http://androidsu.com/superuser/
Reboot phone. Use Root explore (or Root browser lite or ES file explorer) go to /system/ect/install-recovery.sh script, tab on mount R/W button (upper top). Long press on the script and in the popup menu, select permission, unchecked all permission then save the file.
Shutdown phone, re-Odin cwm again, once done reboot, now cwm should stick. Once phone came up, to verify root on your phone, you can download "root checker basic" from the Market. If you have issue, download "superuser update fixer" app from the market and run it.(no reboot required). That's it.
*** There is a quicker way to root, is just flash cwm, without reboot phone, boot straight into cwm then flash rom from item C (bloated/rooted) or D (debloated/rooted).. Once rooted, just remove permission from file "install-recovery.sh" with root explorer or something similar, turn off phone, then Odin cwm again. Reboot and you're done.

6. Stop OTA notification fix - by RWnube
http://rootzwiki.com/topic/21207-stop-ota-notification/page__p__571859#entry571859
Basically, just change the word EP4 to FP1 in this line (in the build.prop file):
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/EP4:user/release-keys
change to:
ro.build.fingerprint=verizon/SCH-I510/SCH-I510:2.3.6/GINGERBREAD/FP1:user/release-keys

7. Upgrade from rooted pure stock EP4D to FP1 - Most of ppl mistaken that they have a pure factory rooted EP4D, when they tried the OTA update they ended up with boot loop. OTA upgrade will work with pure factory stock rom with root, meaning factory rooted stock EP4D kernel, stock EP4D rom and stock EP4D radio. After the upgrade you will lose root, just follow the instruction #5 to get root and cwm back. If you don't have what I listed above, you should follow instruction #3 to first get back to stock EP4D then upgrade to FP1, (the following FP1 rom already have root build in - Item C,D,E).

8. ***A better way to upgrade since the release of stock FP1 kernel by shrike1978 (http://www.mediafire.com/?ns38atiw1d7er5x - Odin version) and Dwitherell (http://goo.gl/pGgxT - cwm version) - If you have custom EP4 rom with custom kernel or stock rooted EP4 rom, you can:
1. Flash item C,D,E or FP1 Eclipse 2.0 (your choice, pick one that you like).
2. Flash FP1 kernel with either Odin or cwm
3. Flash FP1 radio (you must have EP4D radio already installed in order to flash this radio).

...

buhohitr said:

If I remembered correctly, one of post, posted in Tom's world (tom-world.org). If you can't find it let me know. Basically, people have different opinion about rfs and ext4. Samsung has re-tune rfs in GB and it's pretty much almost as fast as ext4, but it's better on battery, more stable and a lot less stress on memory compared to ext4(ext4 hits hard on memory). Most of people mistaken that it's faster due to quadrant score raised after install ext4. Day to day usage, you see no different between the two. Ext4 is only good if you have a good kernel driving it. Now there is a small percentage that ext4 can corrupt and brick your phone, the question is will you want to take that chance?? and for what gain??

Click to expand...

Click to collapse

Here is the article (try not to provide extra link from this site):
Should I use EXT4?

First, a little background information... I'm going to cover some technical stuff here so try to hang on.

RFS and EXT4 are both file systems. They are what tells the system where in the memory of the phone to find files. Both RFS and EXT4 have different methods on how they store file system meta data that describes how the files are stored, indexed, etc.

Let's first cover RFS. RFS has it's roots in FAT and FAT32, you'll probably remember this from the dark old days of DOS, Windows 3.1, and Windows 9x.

In order for Android to run safely, the system must have file system permissions to make sure that no process can read/write to a file that it doesn't have the permissions to operate on. This is done through a series of permissions sometimes known as POSIX permissions, from Linux. Another thing Android must have to run safely is something called File System Journaling. File System Journaling is a system that keeps track of the changes that will be made in a journal (usually a circular log in a dedicated area of the file system) before committing them to the main file system. In the event of a system crash or power failure, such file systems are quicker to bring back online and far less likely to become corrupted.

RFS, because it's based on FAT/FAT32, didn't have all of the above features needed to run Android properly and safely. Samsung, in the development of their Android systems, made RFS by taking FAT/FAT32 and bolted on POSIX permissions and File System Journaling. Some say that this has made for an ugly file system.

EXT4 is another file system, if you know Linux then you're going to definitely know what this is. EXT4 was built with File System Journaling and POSIX Permissions from the very start and by doing so some people say that it doesn't suffer from the performance issues that RFS has because of it's "bolted on" nature.

What does this all mean for me? The user of the Samsung Droid Charge?

Well, some people say that by converting to EXT4 via something called "Voodoo Lag Fix" will increase the performance of the phone. This was the case when we were running Froyo-based ROMs. Now that we are running Gingerbread-based ROMs, the performance difference isn't as large of a gap between RFS and EXT4. Back when Froyo was the norm, RFS performance was atrocious and converting to EXT4 dramatically increased the performance of the phone.

Fast-forward to Gingerbread on the Droid Charge. The performance of RFS isn't that bad, in fact it's close to the performance of EXT4 due to some major tweaks to the file system driver that Samsung made for RFS. Granted, it's no EXT4 but it's definitely not as bad as it once was in the dark old days of Froyo.

So... the question that everyone has on their minds is; Should I use EXT4?

In my opinion, the answer is no and I stand by that answer. There is no reason to convert to EXT4 now that the performance of RFS is close to the performance of EXT4. Most people will not be able to tell the difference between a phone running RFS and a phone running EXT4. Yeah, you might get better Quadrant Scores but Quadrant Scores aren't the end-all-be-all of phone performance. If my phone runs well, is stable, and does what I want it do, that's all that should matter and not some Quadrant Benchmark Score.

There have been reports that people who have converted to EXT4 later ended up with a phone that's completely bricked. I mean, it's about as good as a doorstop. It turns out that a part of the phone's internal flash memory has been shown to become so badly corrupted under EXT4 that you can't read it, wipe it, delete data from it, etc. This results in the inability to flash any ROM to the phone since the flash memory itself is corrupted beyond repair and the only thing you can do is swap the hardware out.

This is why my opinion is that it's best to simply stay on RFS and forget about converting to EXT4.
Page Last Modified On: February 19, 2012 at 2:19 pm
--------------------

deafptl4ever said:

Your screwed buddy. That's the norm here.

Sent from my SCH-i705 using xda premium

Click to expand...

Click to collapse

Howdy sunshine - come to spread your joy again today?

nitroglycerine33 said:

You are perfectly fine deleting install a recovery.sh. You actually want to delete this if you are running a custom recovery with a stock kernel. That script pulls the recovery from the kernel and overwrites the custom recovery.

Sent from my GT-I9505G using Tapatalk 4 Beta

Click to expand...

Click to collapse

This. If you are leery to delete that file for whatever reason you can always throw a .bak on it or the like as well, or change permissions on it to 000, etc. Like Nitro said, if you are running a stock (or modified-by-you version anyway) build you'll want that gone. Note though that some use that file to do other things - recent supersu installs use it to get around 4.3 root issues, you can use it to allow init.d support on an unmodified stock kernel, etc. In those cases you'd want to leave it be, but that likely doesn't apply here - just thought I'd point it out regardless

shrike1978 said:

Can you verify if they've fixed the issue where you have to reboot after tethering to get wifi back?

Click to expand...

Click to collapse

I checked this myself and the latest version still NOT WORKING CORRECTLY. Once you turn off, you need to reboot in order to use it again.
So the best wifi tethering stills:
wifi_tether_v3_0-pre12
http://code.google.com/p/android-wi...tail?name=wifi_tether_v3_0-pre12.apk&can=4&q=
Settings:
Device profile= Samsung Fasinate
setup method= softap for samsung(master)