 |
|
| ROMs y desarrollo Samsung Galaxy S I9000 ROMs y desarrollo Samsung Galaxy S I9000 |
«
Tema Anterior
|
Siguiente tema
»
|
|
Herramientas |
|
#1
12/04/11, 13:21:57
|
||||
|
||||
[11.04.2011][CF-Root 3.1] JP*,JS*,JQ3,JV1/K - su+bb+2e/CWM - rfs+ext4
Esto es una recopilacion de kernels modificados con root,para todas las roms o casi todas,un trabajo realizado por chainfire de XDA gracias por su trabajo. fuente: http://forum.xda-developers.com/showthread.php?t=788108 IMPORTANTE No esta traducido por falta de tiempo, pero con el traductor de Google se puede leer y los enlaces hay que estar registrasdos en XDA para poder bajarlos, si alguien tiene ganas y tiempo, se puede ir poniendo en este post This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, unprotected recovery, and CWM compatibility. If you are looking for highly optimized kernels or kernels that perform specific functions, look elsewhere. All CF-Root's are based on original Samsung kernels, they are NOT recompiled, and thus ensure maximum compatibility. THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. MAKE SURE YOUR PHONE CAN ENTER DOWNLOAD MODE USING THE KEYCOMBINATION WHILE BOOTING BEFORE FLASHING CF-ROOT (or anything, really) Donate There have now been over 200.000 downloads of CF-Root and many more if you include ROMs, kernels, ect that use it. Don't be a leech, buy me a beer(and use the "Thanks" button!) Features - The kernel is fully stock and taken from the original firmware, with just the following added: - Root - Superuser 2.3.6.1 FROYO ( CF-Root < 2.4 versions ) ---- Busybox 1.15.3 or 1.17.1 (if not mentioned in the filename it is 1.15.3) ---- "2e" recovery (can flash unsigned update.zip's) ---- Integrated fix for ClockworkMod's nandroid (2.5.0.4+) GINGERBREAD ( CF-Root >= 2.4 versions, JVK and newer ) ---- Busybox v1.16.2androidminimal (from CWM) ---- Integrated CWM 3.0.0.5 / RFS Instructions (short) - Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done. Instructions (long) - Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch! - Unzip the attached CF-Root-xxx-vX.X.zip - (USB) Disconnect your phone from your computer - Start ODIN - Click the PDA button, and select CF-Root-xxx-vX.X.tar - Put your phone in download mode - (USB) Connect the phone to your computer - Make sure repartition is NOT checked - Click the START button - Wait for the phone to reboot - Done (if it took you more than 30 seconds, you need practise!) Instructions (alternative if you are already running CF-Root 2.5 or newer) - Copy the zip file to your SD card - Stop sharing SD card with computer over USB, unplug the cable, etc - Applications -> CWM -> Flash kernel. Select the ZIP file on your SD card. - Done Other kernels Replacing CF-Root with other kernels (speedmod, voodoo, etc) and vice-versa sometimes works, sometimes it doesn't. I don't have a list. When going from CF-Root to another kernel, root will usually stay, while 2e recovery will be lost (unless the other kernel also includes it), but there should not be issues. CF-Root is made to be applied on a stock kernel. Going from a lagfixed kernel to CF-Root usually does not work. Unlagfix first. Voodoo If you are running the latest Voodoo, you probably do not need CF-Root at all. Voodoo has the basic root features in place, but not the applications. Voodoo does not come with 2e recovery, but it does come with CWM, so there is no need for 2e on Voodoo. To get Superuser and Busybox on Voodoo, simply open Market and search, download, and install them ! Voila ! ClockworkMod on FROYO ( CF-Root versions < 2.4 ) CF-Root is ClockworkMod compatible, it does not include CWM itself. It uses 2e recovery, which means it can flash unsigned update.zip's, like CWM. To use CWM, either place the update.zip in the correct location ( /sdcard ), or install it through the ROM Manager application. When you boot into recovery, you will get the 2e recovery, even if CWM is installed. It does not boot directly into CWM (though it may do so when you boot into recovery from the ROM Manager application). Select "flash update.zip" in recovery to start CWM. Important note: The very first time you do this on a ROM, it will usually not work. The phone will reboot normally after you flashed the update.zip. You need to reboot into recovery a second time and flash update.zip again. Then you will be launched into CWM. After this, it will work the first time you select it. ClockworkMod on GINGERBREAD ( CF-Root versions >= 2.4, excluding JV1 on which CWM is broken ) CF-Root includes a special version of CWM3, modified to work with RFS. CWM3 by default does not support RFS, koush' versions are all based on ext4. The RFS compatibility is done with heavy scripting, the same method used on CF-Root for Galaxy Tab. For SGS CWM3 is also recompiled from source with some slight modifications to handle key input correctly. CF-Root/CWM3 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly. - Booting into recovery will immediately give you CWM. The standard recovery is completely gone. - A "CWM" icon is added to your applications, which will reboot your device into recovery mode (CWM). - ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery. - When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally. - Version jumped from 1.3 to 2.4 to keep the cross-device CF-Root versioning in-sync (CF-Root is also available for Galaxy Tab). - If you wonder where your bootup/shutdown sounds have gone, CF-Root probably removed them to make sure it has enough space available. - ( CF-Root versions < 2.6 ) Make sure to boot up your device fully at least once before flashing CF-Root. This is because the device may have some code it needs to run at first boot. CWM disables this code. CWM Manager on GINGERBREAD ( CF-Root versions >= 2.5 ) Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011) and beta. You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options. Features: - Boot to CWM - Backup firmware - Restore backups - Delete backups - Install APKs ( CF-Root versions >= 2.8 ) - Flash CWM3 update.zip's - Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP) Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility ! At this version of CWM Manager this does not produce errors, it just doesn't do what you expect it to  Tweak Manager on GINGERBREAD ( CF-Root versions >= 2.8 ) CF-Root includes a number of tweaks that are applied on startup. From CF-Root versions 2.8 and up a "Tweaks" application is included you can use to select which tweaks to apply. Ext4 Manager on GINGERBREAD ( CF-Root versions >= 2.8 ) CF-Root supports ext4 mounts for the main mount points. Converting between rfs and ext4 however requires a secondary external package (which you can find in the download area a great many posts below this one), because it is all too large to fit inside the kernel. Download the APK from below, put it on your sd card, start CWM Manager, select "Install APK", find the APK and tap to install. Now you can use the "ext4" app to convert between filesystems, manually check the filesystem, etc. Obviously you should revert back to rfs before flashing a new stock ROM. A lot of custom ROMs support ext4 as well, but it is still advised to revert to rfs before installing them. Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed. Features: - Show current filesystem status - Convert between rfs <=> ext4 and back - Manual fsck - Selects either internal or external sdcard for temporary storage, depending on which has the most space - Automatically reverts on conversion failure - If it tells you to PANIC !, please do so Custom boot / init scripts on GINGERBREAD ( CF-Root versions >= 2.8 ) CF-Root will execute the following scripts if present, in the order listed: - /system/etc/init.d/* (there can be many files here, no extensions! use #!) - /system/bin/customboot.sh (busybox sh) - /system/xbin/customboot.sh (busybox sh) - /data/local/customboot.sh (busybox sh) Please make sure you chown / chmod the scripts correctly so they can be executed. Custom boot / init scripts on GINGERBREAD ( CF-Root versions >= 2.9, broken in 2.8 ! ) CF-Root also supports custom boot animations: - /system/media/bootanimation.zip - /data/local/bootanimation.zip CF-Root v3.0 and up also support: - /data/local/bootanimation.bin Installing busybox over the included version on GINGERBREAD ( CF-Root versions >= 3.0 ) It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to/systemxbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying. Notes - (FROYO) ADB in recovery is flaky. Sometimes it works, sometimes it doesn't. If you go into ClockworkMod it usually works, though. - (FROYO) An older version of BusyBox is used (in some versions) because the newer versions drive me absolutely crazy with throwing color codes into the shell while it isn't supported. How ? I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops Help! I don't know which file to pick! The filenames confuse me! First thing: don't panic! It's all rather easy, and you won't easily do something bad! I am personally attentive to use the exact same version as the ROM I am running, but it's not that important. First, go to Settings -> About phone -> Build number. It should say something like FROYO.xxJPy. It's primarily the JPy that we are interested in. Try to match that with a download link available in this (and the next few) posts. Some of the downloads dont just have JPy file name format, but are called xx_xxx_JPy. Let me explain that. Samsung isn't always very precise in naming/marking their different (leaked) firmwares. CF-Root's are modified kernels, the filenames explain in more detail which exact firmware ROM the base kernel was taken from, for those experts who understand. If you are not one of those people, go back to the JPy thing. The "y" in JPy is 0-9, A-Z. If they run out of numbers, they use letters. So A would be 10 (9 + 1), while Z would be 35 (9 + 26). Find the one that is closest to yours, if yours is not present, and flash that one. The truth is, these kernels, they don't differ all that much. It's quite likely that the very latest version (at time of writing: JPY) will work perfectly fine on your ROM. There are some small differences, but using a different version is unlikely to cause serious issues. The closer the versions are, the less likely there are to be issues, BUT it is still quite possible that the latest version will work better for you than the matching version (or not!). If you are just installing CF-Root to flash a custom ROM like Darky, make sure you have ROM Manager already installed, ClockworkMod flashed, then simply install the latest CF-Root, reboot once normally, then reboot in recovery and run the Darky update.zip. In this case it does NOT need to be a near match at all! Download LOOK WELL AT THE FILENAMES, MAKE SURE YOU ARE GETTING THE RIGHT VERSION !
ROOTING JV1: The JV1 version is not compatible with ANY version of ClockWorkMod (CWM).
Note: it is NO PROBLEM to flash new JVK version over old JV1 or JVK version! Release notes for v2.8: http://forum.xda-developers.com/show...postcount=1332 Release notes for v2.9: http://forum.xda-developers.com/show...postcount=1400 Release notes for v3.0: http://forum.xda-developers.com/show...postcount=1536 Release notes for v3.1: http://forum.xda-developers.com/show...postcount=1663
The ext4 tools addon for CF-Root requires CF-Root version 2.8 or later Release notes for v1.0: http://forum.xda-developers.com/show...postcount=1332 Release notes for v1.1: http://forum.xda-developers.com/show...postcount=1400 (non-essential update) Release notes for v1.2: http://forum.xda-developers.com/show...postcount=1536 (non-essential update)
|
| Los siguientes 9 usuarios han agradecido a vvaleta su comentario: | ||
|
|
|
#2
12/04/11, 13:41:06
|
||||
|
||||
 LICENSE for CF-Root v3.0+, ext4 tools v1.2+As it seems a number of kernels are being based on CF-Root, and CF-Root is being included in custom ROMs, I'm going to set up a number of rules. The rules are meant to be fair to both you and me, and futher cooperation, not limit it. If you are an end-user, do not distribute kernels based on CF-Root, and do not distribute ROMs using it, you can skip this post, it is not for you. If you make kernels based on CF-Root, or your ROMs include CF-Root, read this post and follow the rules. I don't mind you using the CF-Root hacked kernels, in fact I think it's great All parts of CF-Root are free to use/include in your own stuff, if these rules are followed.If something doesn't work for you, feel free to PM/ask for a change. None of these rules are set in stone, maybe you have a good reason to want something different. Usage of "CWM Manager", "Tweak Manager", and "ext4 tools" apps - You may not modify these APKs in any way, if you include or redistribute them. Modifying icons to match your firmware/ROM theme is however allowed, but must be stated. - You may not re-post these files anywhere else (separately from CF-Root), but you may of course link to the post (not the download directly!) in the CF-Root thread containing these files. In other words, either you include them or you don't, but you can't offer them as a separate download. - You must use the appropriate versions, released at the same time as the kernel, or any newer version released by me. For example, if you are using CF-Root v3.0, if you use/include these apps, you must use CWM Manager 1.50+, Tweak Manager 1.20+ and ext4 Manager 1.20+. - You must test that their functionality remains 100% intact regardless of your (kernel/ROM) modifications. If the functionality is not as expected with your (kernel/ROM) modifications but you still include the apps, you must clearly state what you know is broken. If you are just using CF-Root in your custom ROM, but do not modify the CF-Root kernel in any way (except icons) - You must include a notice that the ROM uses CF-Root, and the version of CF-Root used. - You must also include a link to this thread ( http://forum.xda-developers.com/showthread.php?t=788108 ) - You should (not required) include a link to donate to me, Chainfire ( http://www.jongma.org/dx.php ) - You should (not required) inform me that you are using it either by posting in the CF-Root thread or sending me a PM. (Thanks!) - As you are not modifying CF-Root in any way (except icons), you can skip the rest of this post If you are using any part (that I have written) of CF-Root, basing a kernel on CF-Root or including it in your ROM and modifying it - You must include a notice that the kernel/ROM is based on or uses CF-Root, and the version of CF-Root used. - You must also include a link to this thread ( http://forum.xda-developers.com/showthread.php?t=788108 ) - You must include a link to donate to me, Chainfire ( http://www.jongma.org/dx.php ) - You must keep the Android properties correct (see below) - You should (not required) inform me that you are using it either by posting in the CF-Root thread or sending me a PM. (Thanks!) customkernel.* Android properties These properties are used by various scripts and apps to detect/control features, and are generally (IMHO) a good thing to have and keep correct. In CF-Root these are set in /sbin/boot-patch.sh, or /sbin/boot/properties.sh, depending on CF-Root version. These properties must be set by a script or binary that is inside initramfs. They may not be set by anything on a "normal" partition - like a script in /system or /data. This way replacing the kernel will clear the values. customkernel.cf-root - Either "false", "true". May only be "true" if fully compatible with CWM Manager, Tweak Manager, and ext4 Manager / tools. The idea is to add your own as well. If you make "uberkern", for example, set "customkernel.uberkern" to "true" as well. customkernel.base.cf-root - Either "false" or "true". Must be "true" if the kernel uses anything from CF-Root. customkernel.name - Kernel name without version numbering. Somewhat an identifier. "CF-Root" in CF-Root. customkernel.displayname - Kernel name including specifics, in case of CF-Root is it "CF-Root ...version-name...". Used to display "current kernel version" in various tools. Could be "UberHackers UberKernel v89 with Extra Monkeys" in your case customkernel.version.number - This is an internal build number, incrementing. Newer versions always have a higher number than older versions. In CF-Root v3.0 this number is 50. customkernel.version.name - The named version. In CF-Root v3.0 this would be "3.0". customkernel.bootani.zip - Either "false" or "true". Whether the kernel supports "bootanimation.zip" in /data/local customkernel.bootani.bin - Either "false" or "true". Whether the kernel supports "bootanimation.bin" in /data/local customkernel.cwm - Either "false" or "true". Whether the kernel has ClockWorkMod included customkernel.cwm.version - CWM's version. Must include at least the major version. Example values: "2", "2.0.1.0", "3", "3.0.0.5" customkernel.fs.* Android properties Filesystem support flags. RFS and VFAT are special case. RFS can only be used on "internal" partitions, VFAT is supported by all kernels. Therefore, RFS only has the "basic" flag, and VFAT is not listed at all. Values are always either "false" or "true". The * should be replaced by the filesystem name, in lowercase, with a maximum of eight characters. In CF-Root these are set in /sbin/boot-patch.sh. customkernel.fs.* - Filesystem supported on ALL basic internal partitions: system, data, dbdata(datadata), cache. customkernel.fs.*.sd.int - Filesystem supported on internal SD card, if such a thing exist on the device. customkernel.fs.*.sd.ext - Filesystem supported on external (removable) SD card, if such a thing exists on the device. CF-Root ext4 (in v3.0): Código:
customkernel.fs.rfs true // RFS supported on basic internal partitions customkernel.fs.ext4 true // ext4 supported on basic internal partitions customkernel.fs.ext4.sd.int false // ext4 NOT supported on internal sd card customkernel.fs.ext4.sd.ext false // ext4 NOT supported on external sd card persist.tweak.* Android properties (only applies if you include Tweak Manager APK) These properties are used by Tweak Manager and CF-Root startup scripts (/sbin/boot-patch.sh) to perform tweaks. - You may not significantly modify behavior based on these tweak properties. You can further tweak a tweak, but the result should still fit the intent of the original tweak. For example, the noatime tweak should always apply noatime, and should not be changed to change default screen rotation or something. - If including a new tweak which is controlled by a persist.tweak.* setting, the boot script must set a default value for this property.
|
| Los siguientes 3 usuarios han agradecido a vvaleta su comentario: | ||
|
#3
12/04/11, 14:07:20
|
||||
|
||||
|
Listo
 si veis algo mal o mejorable, mencion a cualquier mod/coord y se modificara.@Lorse @Miorat @alvhergon Vosotros que estáis mas atentos, lo que veáis. 
|
| Gracias de parte de: | ||
|
#4
12/04/11, 14:13:15
|
||||
|
||||
 cagontooo voy a tener que retomar mis clases de inglés 
|
|
#5
12/04/11, 16:30:19
|
||||
|
||||
|
He instalado el 3.1 sobre la V29 de Criskelo y todo correcto. Y aunque no uso el ext4.apk (ahora mismo el SGS va tan fluido que no hace falta) al arrancar la aplicación dice que no encuentra particiones ni RFS ni EXT4. Tengo RFS, y no tengo necesidad, pero tengo curiosidad
Ya lo he resuelto, he tenido que instalar busybox. Ya lo tenía desde la ROM, pero parece que es necesario reintalar desde apk Última edición por artikeln Día 12/04/11 a las 16:34:17
|
|
#6
15/04/11, 13:16:51
|
||||
|
||||
|
Perdonad si estoy preguntando algo muy obvio
 pero no encuentro cuál sería el archivo para la 2.2.1 española. En el post de xda hay un JS8 pero pone que es NEE. ¿Sería este el que hay que flashear o hay que esperar a que saque el archivo específico para nuestra 2.2.1?Edito: me respondo yo mismo. He visto que el archivo que colgó Lorse en el hilo de la 2.2.1 española es el de la JS8 NEE, por lo que ya está claro que es ese. Última edición por soubrier Día 15/04/11 a las 13:22:59
|
|
#7
19/04/11, 22:45:09
|
||||
|
||||
|
??????????????????
Para esto, con poner solamente el link original hubiera bastado. 
|
|
#8
19/04/11, 23:24:22
|
||||
|
||||
|
Si, pero como no es un hilo que se actualice mucho, queda mejor así.
|
|
#9
17/06/11, 20:45:57
|
||||
|
||||
|
hola buenas tardes, de donde podría descargar el Tweak Manager de chainfire es que no lo encuentro por ninguna parte
gracias
|
| Respuesta |
Estás aquí
|
||||||
|
||||||
«
Tema Anterior
|
Siguiente tema
»
|
|
Hora actual: 15:40:53 (GMT +2)
HTCMania: líderes desde el 2007