Copied from Chainfire 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 (S5830: compiled ext4 as module with ext2, ext3 and ext4 support), and just adds root, busybox, and (unprotected recovery and CWM compatibility) OR (CWM3). S5830: using a modified official CWM4 for Samsung Galaxy Ace.
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. S5830: have a kernel version compiled from Samsung original kernel source using a config file extracted from device.
THIS IS NOT A ROM - it is only a kernel (S5830: boot and recovery image). You need to have a firmware already on your device (S5830: tested on stock Gingerbread XXKPH, XWKPN, and DXKPB). 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 for various devices (1700+ for CF-Root-S5830 b80), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy Chainfire a beer (and use the "Thanks" button!)
Features
Some binary files added:
-- Root, su binary v2.3.2-efgh
-- Superuser v2.3.6.3
-- Busybox v1.17.2 for the boot image and v1.16.2androidminimal for the recovery image (from CWM)
-- A modified CWM
Instructions (short)
- Boot into recovery and flash CF-Root-S5830-v3.7-b82.zip. Done.
Instructions (long)
ClockworkMod
- Booting into recovery will immediately give you CWM4! The standard recovery is completely gone.
- ADB is functional in recovery.
- When connected to ADB in recovery, you will get root directly.
- If you wonder where your bootup sounds have gone, CF-Root probably renamed them.
CWM Manager
Same as Chainfire's CF-Root
Features:
- Boot to CWM
- Backup firmware
- Restore backups (S5830: Do not use CWM Manager to restore any backup for now, use CWM Advance Backup directly!)
- Delete backups
- Install APKs
- Flash CWM update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP) (S5830: you have to rename boot.img to zImage)
Tweak Manager
Same as Chainfire's CF-Root, except:
- Kernel: Scheduler option always disabled on boot. Kernel scheduler tweak not working on S5830.
- Now have "DT: Auto start" option to turn on/off Darktremor a2sd script on boot. Don't worry, Darktremor apps2sd setting is persistent, event you turn off the auto start script. It's safer to turn a2sd auto start off!
Ext4 Manager
Same as Chainfire's CF-Root.
Obviously you should revert back to rfs before flashing a new stock/modified ROM!
S5830: No need to revert back to rfs before flashing a new stock Gingerbread ROM! Tested using XXKPH, XWKPN, and DXKPB.
Custom boot / init scripts
Same as Chainfire's CF-Root.
Mount /dev/block/mmcblk0p2 to /system/sd if the microSD second partition present (ext2, ext3, or ext4), do not remove the microSD while S5830 ON (event after unmounted from "SD card and phone storage settings"), turn off your phone first before eject the microSD! It's safe to connect your phone to PC and mount the first partition (FAT/FAT32) in mass storage mode.
Custom boot animations and binaries
Same as Chainfire's CF-Root. S5830: DXKPB have a bug (or Samsung made it), bootanimation not closed when boot complete, CF-Root fix it!
Dark Tremor apps2sd:
A modified DT's apps2sd to guarantee no longer interfere Wi-Fi, BT, GPS, etc. Flash it using CWM recovery or CWM Manager - Flash update.
CF-Root by default not automatically start DT a2sd script on boot. Run Tweak Manager and select "DT: Auto start" option, then "Apply changes" to reboot your phone. When booting, bootloop will occur several times during DT apps2sd activation for the first time.
Installing busybox over the included version
Don't do it!
How ?
- Base on Chainfire's CF-Root, used a modified mkbootfs in order files in /sbin have the appropriate permissions.
- A modified CWM4 package to make sure ext4 Manager conversion scripts working as expected.
- Boot logo modification, references from here and here.
The original post (in Indonesian): CF-Root-S5830XXKPH.
BUGFIX: b82-ex-fixed
Fix for following bugs:
Auto boot when plugged into the charger/USB from off state or turned off when the device connected to charger/USB
Gallery3D freeze after browsing some pictures, and then fail to display 3D textures in all 3D app
Copy b82-ex-fixed.zip to SD card and then install it via "CWM Manager - Flash kernel"!
UPDATE: CF-Root-S5830 v3.7 b82-ex
swap and BLN support
Using a kernel compiled from source, the config file extracted from DXKPB device (/proc/config.gz) with small modification
Need a patched Service Manager (services.jar) installed on deodexed framework for fully working BLN. Backup your /system/framework/services.jar first!
UPDATE: CF-Root-S5830 v3.7 b82
The original update (in Indonesian): CF-Root-S5830-v3.7-b82
Single *.zip for both boot and CWM recovery image. Flashable using stock or CWM recovery!
Using Samsung Galaxy Ace DXKPB stock kernel (2.6.35.7-perf-CL514579), don't blame me if you got SOD
ext4 as a module
wifi module (ar6000.ko) included, so this version of CF-Root-S5830 will work on all versions of Gingerbread
Busybox installed in /system/xbin
Need the new CF-Root-S5830_ext4-v1.3u3.apk for rfs and ext4 filesystem conversion
Bootanimation fix, kill bootanimation when boot done (DXKPB bugfix?). Android Scribble as demo bootanimation, delete /data/local/bootanimation.zip if you don't like it
cifs.ko and tun.ko included, no need separate package
Since using the stock kernel, have no BLN and swap support
Small size boot and recovery image, ~5MB each
UPDATE: CF-Root-S5830 v3.7 b80
kernel compiled using gcc version 4.5.2 (Sourcery G++ Lite 2011.03-42)
swap support
ext3, ext4 filesystem support
lzma initramfs support
kernel log buffer size: 12 -> 4KB
small-memory-footprint RCU -> Tiny RCU
default kernel command string: mem=330M console=NULL hw=5 fbaddr=0xf6000 quiet
printk without timing information
debug info disabled
alsa debug disabled
unnecessary LCD and battery printk removed
BLN kernel support, modified liblights.msm7k.so
wifi module taken from XWKPN to make a single distribution for both KPH and KPN
recovery b79: fix CSC flashing error
Single distribution for both KPN and KPH. For full BLN support, you have to install KPH/KPN services on deodexed framework. Backup your /system/framework/services.jar first!
UPDATE: CF-Root-S5830 v3.7 b78
Using only 1 system property from the previous 21 (CF-Root + DT apps2sd). Now is guaranteed CF-Root no longer interfere Wi-Fi, BT, GPS, etc. It's a big problem if Android system property reach the 247 limit. You can use "getprop | grep -c ]" to count registered system property.
The tweak script in /system/etc/init.d, it allows advanced users to do further tweaking
New icon for CWM, Tweak, and ext4 Manager. Thanks to moemooo.
Using CWM4 recovery. CWM4 re-packaged to ensure the ext4 Manager script working as expected. The ext4 script also improved, check SD card second partition also.
Modified Darktremor apps2sd to use the CF-Root busybox. Reducing system property need to 0. Method of mounting SD card second partition fixed, false filesystem type detection will not happen.
Turn the button backlight when the CF-Root script starts executed and turn it off upon completion. This could be an indicator of a problem and inform the user how long the CF-Root script is executed. Apparently fast so the already b78 user was not aware of this new feature
Tweaks LCD in Tweak Manager changed as a switch for toggling a2sd script execution when booting.
DOWNLOAD:
CF-Root-S5830-v3.7-b84.zip (12.55 MB)
BUGFIX: Invisible boot animation.
Install CF-Root-S5830-v3.7-b84.zip via "CWM recovery" first and then install b84-fixed.zip via "CWM Manager - Flash kernel"!
CF-Root-S5830-v3.7-b83.zip (12.38 MB)
- Untested since on CyanogenMod 7.2 firmware for now
- Using b82 recovery image
- CPU and system bus overclock enabled
- GPU driver backported from 2.6.35-11 kernel source
- interactive, interactiveX, smart*ss, and smart*ssV2 governor
- Samsung on the fly governor setting disabled
- WiFi driver taken from DXKPD
CF-Root-S5830-v3.7-b82.zip (11.95 MB)
Don't use the older version of CF-Root-S5830, I leave the attachments here since like to see the comparison between the number of downloads and the thanks list
CF-Root-S5830-v3.7-b82-ex.zip (11.83 MB)
The -ex version have swap and BLN support. This version using a kernel compiled from source, the config file extracted from DXKPB device (/proc/config.gz) without alot modification. Need a patched Service Manager (services.jar) for fully working BLN. Only DXKPB Service Manager attached here (CF-Root-S5830_DXKPB-services.zip) for now. You can patch your deodexed services.jar base on neldar's patch or ask me to do it.
A modified ext4 Manager to make it work on Galaxy Ace. Need a modified CWM4 recovery, not sure will work on official CWM4 from illarain/koush. This version show /system/sd partition size.
A reference multi CSC, taken from XWKPN (Europe?) and DXKC1 (Asia?). Default CSC: Indonesia . A good reference for ROM cooker
sec_csc.zip (3.69 MB)
DOWNLOAD RECORD:
CF-Root-S5830-v3.7-b80_cifs_tun.zip: 493 downloads
CF-Root-S5830-v3.7-b80_boot.zip: 1777 downloads
CF-Root-S5830-v3.7-b79_recovery.zip: 1556 downloads
CF-Root-S5830_tweaks-jrs.zip: 284 downloads
CF-Root-S5830_tweaks-default.zip: 151 downloads
Users Say Thank You: 28 Chainfire said, "Don't be a leech".
ganas gan.. porting dari ROM org luar negeri punya yah?
ada yg ditambahin ga asli dari ente?
(wicked cool bro... so you ported the existing ROM from abroad? is there any original mods made by you?)
Can you please explain in short what this is & how this will improve the performance of my ace? I already use the new kernel by coolya & cwm...
Don't Forget to hit Thanks if I helped you!
Sent from my Galaxy Ace.
Does it work for ace European (France) ?
Tib44 said:
Does it work for ace European (France) ?
Click to expand...
Click to collapse
I think it will work if ur firmware based on kph
Yes it works on stock european kph.
App2sd working and my quadrant benchmark shows 1468.Thanks.
ketut.kumajaya
Programs on a SDcard do not work - after reboot(((
Thief777 said:
ketut.kumajaya
Programs on a SDcard do not work - after reboot(((
Click to expand...
Click to collapse
Same here!!!
I can't use wifi connection anymore if I installed this kernel. I tried it several times, with custom rom as base, then stock KPH as per instruction, the result all same. I can't use wifi to connect to the internet as soon I flashed this kernel. The wifi says connected, but can't connect to the internet. Using 3G works fine though.
Apart from that I love it! when converting the rfs to ext4 I can feel the device feels more responsive than ever! I can also use recovery mode to backup/restore ROM! I'm impressed! the only negative thing is the wifi
Found a bug! Remove any application installed on SD card. I will fix this ASAP. About the WiFi, I will try to find the problem, working on me.
Will it work for CodeROM v1b bro ?
Sent from my GT-S5830 using XDA App
ketut.kumajaya said:
Found a bug! Remove any application installed on SD card. I will fix this ASAP. About the WiFi, I will try to find the problem, working on me.
Click to expand...
Click to collapse
I look forward
Hey I had a problem with this kernel...
First I flashed the stock kph & then the cf root file. Then I rebooted my ace & installed the ext4 manager.
In that I selected convert 2 ext4..
But nothing happened.. so I manually flashed the illarean's cwm. After which when I entered the recovery mode it automatically started converting the file system to ext4.. After that when I rebooted it got stuck at the galaxy ace logo.. Then at a black screen..
Is there somthing that I have done wrong?
Sent from my GT-S5830 using XDA App
adiles said:
Hey I had a problem with this kernel...
First I flashed the stock kph & then the cf root file. Then I rebooted my ace & installed the ext4 manager.
In that I selected convert 2 ext4..
But nothing happened.. so I manually flashed the illarean's cwm. After which when I entered the recovery mode it automatically started converting the file system to ext4.. After that when I rebooted it got stuck at the galaxy ace logo.. Then at a black screen..
Is there somthing that I have done wrong?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Expect correction
adiles said:
Hey I had a problem with this kernel...
First I flashed the stock kph & then the cf root file. Then I rebooted my ace & installed the ext4 manager.
In that I selected convert 2 ext4..
But nothing happened.. so I manually flashed the illarean's cwm. After which when I entered the recovery mode it automatically started converting the file system to ext4.. After that when I rebooted it got stuck at the galaxy ace logo.. Then at a black screen..
Is there somthing that I have done wrong?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
CF-Root recovery is a modified version of ilarrain's CWM. CF-Root boot, recovery, and ext4 manager is one package. Not guarantee its working as expected in different combinations. Make sure your SD card in good condition and have enough space (larger than /system partition ~250MB). Don't use ext4 manager with different recovery image!
As I had said earlier that this is fantastic but there are some bugs here.Wifi is not working. Link2sd works but on reboot the sd-ext partition does not get mounted.But on manually mounting sd-ext it works again.
apps in SDcard Issue
hello there
I've just flashed the CF-Root kernel on my ACE, it was fast and very easy to do it, the device booted up without any problem, the only inconvenient was that all my apps located in the SD card had gone. I just had to reinstall everythig which i dont care too much about.
The apps seems to install normally and be functional but after i turn off or reboot the device, all tha apps previosuly installed in the SD card GONE!!!
If i enter in the "Manage Applications menu" i got something like the image attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems like every time a boot up the path to the app SD card files erase or something like that.
Is this normal?? I did something wrong? perhaps i need to format the SDcard in ext4 format or configure something in the CWM3.
Thanks in advance guys.
@Erick_GM
Yes, release 74 have a serious bug. Erase applications on SD card every boot I will fix it in release 75 including CWM Manager as a bonus Hey, your WiFi works?
@skynet28
CF-Root for Galaxy Ace will adopt Dark Tremor's a2sd.
ketut.kumajaya said:
Yes, release 74 have a serious bug. Erase applications on SD card every boot I will fix it in release 75 including CWM Manager as a bonus
Click to expand...
Click to collapse
uuuu what a shame, so there's no solution for that issue at the moment.
If i flash the XXKPH's PDA with the odin i'll recover the original kernel without harming /data or /system??
greetings
EDIT:
yes my wifi works as usual, why?
ketut.kumajaya said:
Found a bug! Remove any application installed on SD card. I will fix this ASAP. About the WiFi, I will try to find the problem, working on me.
Click to expand...
Click to collapse
I just installed CF-Root-v3.7-b75-S5830XXKPH and so far so good! no missing applications, wifi working, ext4 conversion success. Thank you!
Related
Hi All,
first up credit to Z for recovery and providing PoC of dualboot images.
I have worked on base image provided by Z and have removed most of the crap or not so necessary stuff keeping following thing in mind.
1) if we want to use 2.1 that's coz of its camera...
2) we need a basic features to be working on Phone.
I am right now testing this slipstreamed bare bone ROM will upload by tomorrow.
you can expect following from this tread
1) Collection of system.ext2 which you can use for various ROM.
2) Basic guide on how we achieved this size reduction.
3) Instructions + scripts on how to do the same in xrec .0.3 also.
Reserved for Images link
Reserved for FAQ and dev instructions
Instructions to make it runable on Xrec .0.3
1) chargemon editing
1) open chargemon file
find "/system/bin/charger" line in it
replace the line with below code.
Code:
/system/bin/charger
if [ -e /data/local/tmp/dualboot ]
then
rm -rf /data/local/tmp/dualboot
sh /system/kernel/boot.sh
fi
Now your chargemon edit is done
if using adb push do remember ot set the permissions for chargemon again to 04755
i.e. chmod 04755 chargemon
now open the zip file of Z's dualboot..
copy system.ext2 to /system/dualboot/system.ext2
copy data.ext2 to /data/dualboot/data.ext2
copy all files from /system/kernel folder of zip to /system/kernel/ folder
now people here will to the very least post various system.ext2 which you can use as needed.
Once all files are in place you can write a simple gscript for dualbooting.
Code:
touch /data/local/tmp/dualboot
reboot
place this in gscript and add a shortcut on your desktop and you are done with the work.....
hope this helps
hey guys,
i have tried to convert existing ROM backups to working ext2 images... these can be made to work on the proof-of-concept as shown by zdzihu...
basically my aim is to be able to run ANY ROM inside ANY OTHER....
here is the first test release:
dualboot_DooMLoRD_MOD_rdannar_2.1.B.0.1 (for baseband 2.0.xx)
here is the second test release:
dualboot_DooMLoRD_BB67_EWJET_2.1.B.0.1 (for baseband 2.1.xx)
I really love to have dualboot but with xrec1.0 i could not.
I am really looking forward to this. Untill we get a full working camera/videocamera on 2.2 or 2.3 (i.e comparable with stock 2.1 camera/videocamera) this will be an excellent way to get the full functionality of the camera.
Thanks in advance for all your hard work
DooMLoRD said:
hey guys,
i have tried to convert existing ROM backups to working ext2 images...
these can be made to work on the proof-of-concept as shown by zdzihu...
basically my aim is to be able to run ANY ROM inside ANY OTHER....
currently i am working on 2.1 rom by rdannar from: ECLAIR with rdannar flavor
i have modded it so that it can run on baseband 2.0.xx (using bb patch) also included JITv2 (using zip provided by zdzihu) and added a few customizations....
as of now there are some issues with it.... which will be resolved soon (hopefully) then i will release it for u guys to test
Click to expand...
Click to collapse
did you got a method to convert yaffs to ext2 or still the same issue...
anantshri said:
did you got a method to convert yaffs to ext2 or still the same issue...
Click to expand...
Click to collapse
i think i may have found a way...
testing it now....
EUREKA!!!!
it worked....
NOW i think i have a sure way to convert yaffs imgs to ext2 which will actually boot!!!!
DooMLoRD said:
EUREKA!!!!
it worked....
NOW i think i have a sure way to convert yaffs imgs to ext2 which will actually boot!!!!
Click to expand...
Click to collapse
enlighten me
Note: right now going to sleep
anantshri said:
enlighten me
Note: right now going to sleep
Click to expand...
Click to collapse
ofcourse dude!
just waiting for the ROM to cache and installing some apps...
i am going to keep:
/system to 200 MB
/data to 100 MB
dualboot_DooMLoRD_MOD_rdannar_2.1.B.0.1
Since zdzihu wanted to encourage devs & users to switch to new xRecovery I am releasing this proof-of-concept as an Edify update.zip compatible with xRecovery v1.0.0… the concept being that we can convert ANY rom’s (nandroid/recovery) backup to dual boot image (yaffs to ext2 img) which actually boots!!!!
Also I am not saying that this is the only way but rather that this is the way I achieved it…
A BIG THANK YOU TO ZDZIHU FOR GIVING US THIS NEW TOOL TO PLAY WITH
all credits for the base 2.1.B.0.1 ROM goes to rdannar cause I have modded rdannar’s 2.1.B.0.1 ROM from:
http://forum.xda-developers.com/showthread.php?t=1109758
what is changed:
made it to work within ext2 img (dualboot)
changed baseband file to support baseband 2.0.xx
added JITv2
cleaned the ROM
fixed multiple busybox issues (there was one in /system/bin & /system/xbin)
removed redundant symlinks which were creating problems
added LauncherPro (I hate stock 2.1 launcher) & some tweaks for this app
added SpareParts & some tweaks
added some apps
Issues:
Currently there are some issues related to superuser (apps not getting SU permissions) [I think its related to integrated ramdisk in boot-stock.img] but I am sure that this can be sorted out with help from my friends
damn i forgot to change wifi.ko module so wifi currently might not be working
here use this: wifi-fix
just download it, extract it to some folder and use the following command to send it to the modded dualboot OS:
adb push wifi.ko /system/lib/modules/.
Requirements:
Baseband 2.0.52
Main ROM compatible with this baseband (I have tested this on CM7.1.0 RC0 J004 K012b)
U will need xRecovery v1.0.0 for this to work… Grab it from here: xRecovery v1.0.0 Installers for ALL roms
U will need 200 MB free on /system & 100 MB free on /data
How-to Install:
Reboot into xRecovery v1.0.0
Manually mount /system & /data
Go to main menu of xRecovery -> mounts and storage -> mount /system & mount /data
Flash this update.zip
Go back to main menu of xRecovery
Select “boot custom ROM/kernel”
ENJOY the speedy mooded 2.1 ROM!!!
Download Link:
(123MB)
dualboot_DooMLoRD_MOD_rdannar_2.1.B.0.1.zip [mirror]
MD5Hash:
Code:
8fd790dac29b6e976cf158720e51cb68
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great news...
I have some free time at work tomorrow so I will give this a shot when you post the full "how to"
I will test on wolfs v007 test with his custom kernal.
gregbradley said:
Great news...
I have some free time at work tomorrow so I will give this a shot when you post the full "how to"
I will test on wolfs v007 test with his custom kernal.
Click to expand...
Click to collapse
the full how-to is already given!!!!
no need to do anything else to test the file i posted...
wht i meant was:
P.S.: its currently 3:40 AM here… so will write the full how-to for converting on any nandroid/recovery backup (yaffs img) to ext2 files in the morning… sorry to keep to waiting!
DooMLoRD said:
the full how-to is already given!!!!
no need to do anything else to test the file i posted...
Click to expand...
Click to collapse
Sorry...Its late here too and I have to get my weary body into work early....But I will test it tomorrow....
cheers
Big Thanks to Z for this.
Here is my reduced size version of Z's 2.1
system.zip
http://www.mediafire.com/?62zacjq9dv2cq8r
data.zip
http://www.mediafire.com/?v3221o1uwufzc1f
unzip and copy directly to /system/dualboot and /data/dualboot after instualling Z's dualboot package.
system.ext2 -- reduced to < 130mb (I add 20 mb as spare so it's about 150mb)
data.ext2 -- reduced to 64 mb (need about 50mb at least)
Working on system:
- Alarm
- Browser
- Calendar
- Calculator
- Camera
- Market
- Mediascape
- Messaging
- Phone
- Phone Book
- Settings
- JITv2 included
@doom - buddy eagerly waiting for your yaffs to ext2 guide
Edit: Here is the flashable zip (with xRecovery 1.0)
http://www.mediafire.com/?sqebawtf0wsdrvn
DooMLoRD said:
Since zdzihu wanted to encourage devs & users to switch to new xRecovery I am releasing this proof-of-concept as an Edify update.zip compatible with xRecovery v1.0.0… the concept being that we can convert ANY rom’s (nandroid/recovery) backup to dual boot image (yaffs to ext2 img) which actually boots!!!!
Also I am not saying that this is the only way but rather that this is the way I achieved it…
A BIG THANK YOU TO ZDZIHU FOR GIVING US THIS NEW TOOL TO PLAY WITH
all credits for the base 2.1.B.0.1 ROM goes to rdannar cause I have modded rdannar’s 2.1.B.0.1 ROM from:
http://forum.xda-developers.com/showthread.php?t=1109758
what is changed:
made it to work within ext2 img (dualboot)
changed baseband file to support baseband 2.0.xx
added JITv2
cleaned the ROM
fixed multiple busybox issues (there was one in /system/bin & /system/xbin)
removed redundant symlinks which were creating problems
added LauncherPro (I hate stock 2.1 launcher) & some tweaks for this app
added SpareParts & some tweaks
added some apps
Issues:
Currently there are some issues related to superuser (apps not getting SU permissions) [I think its related to integrated ramdisk in boot-stock.img] but I am sure that this can be sorted out with help from my friends
damn i forgot to change wifi.ko module so wifi currently might not be working
here use this: wifi-fix
just download it, extract it to some folder and use the following command to send it to the modded dualboot OS:
adb push wifi.ko /system/lib/modules/.
Requirements:
Baseband 2.0.52
Main ROM compatible with this baseband (I have tested this on CM7.1.0 RC0 J004 K012b)
U will need xRecovery v1.0.0 for this to work… Grab it from here: xRecovery v1.0.0 Installers for ALL roms
U will need 200 MB free on /system & 100 MB free on /data
How-to Install:
Reboot into xRecovery v1.0.0
Manually mount /system & /data
Go to main menu of xRecovery -> mounts and storage -> mount /system & mount /data
Flash this update.zip
Go back to main menu of xRecovery
Select “boot custom ROM/kernel”
ENJOY the speedy mooded 2.1 ROM!!!
Download Link:
(123MB)
dualboot_DooMLoRD_MOD_rdannar_2.1.B.0.1.zip
MD5Hash:
Code:
8fd790dac29b6e976cf158720e51cb68
Screenshots:
P.S.: its currently 3:40 AM here… so will write the full how-to for converting on any nandroid/recovery backup (yaffs img) to ext2 files in the morning… sorry to keep to waiting!
Click to expand...
Click to collapse
eagarly waiting for your conversion script.......
cobrato said:
Big Thanks to Z for this.
Here is my reduced size version of Z's 2.1
system.zip
http://www.mediafire.com/?62zacjq9dv2cq8r
data.zip
http://www.mediafire.com/?v3221o1uwufzc1f
unzip and copy directly to /system/dualboot and /data/dualboot after instualling Z's dualboot package.
system.ext2 -- reduced to < 130mb (I add 20 mb as spare so it's about 150mb)
data.ext2 -- reduced to 64 mb (need about 50mb at least)
Working on system:
- Alarm
- Browser
- Calendar
- Calculator
- Camera
- Market
- Mediascape
- Messaging
- Phone
- Phone Book
- Settings
- JITv2 included
@doom - buddy eagerly waiting for your yaffs to ext2 guide
Click to expand...
Click to collapse
cool work.... I am having something simmilar on my phone right now.... Albiet i have also removed Alarm, and calculator, will post mine by night @ IST.
Not got as much time as i thought today..but will see what i can do.
Just 2 questions to get me going.
I am using wolfs cm6 with his v007 test and the custom kernal from his thread.
if i put on the dual boot will this change my kernal again or will it keep the one i have. (i.e. I know it needs a custom kernal to dual boot but does it need a specific kernal or will any custom kernal do).
Also,
Which of the xrecovery 1.0.0 do i need
"2.2 ROMs (who dont require custom kernel by default. e.g.: FreeX10)
Please use the FreeX10-beta4-hotfix2.zip provided by zdzihu in the FreeX10 thread
2.1/2.2/2.3 ROMs
This is for those ROMs who dont require custom kernel by default but have the option to select custom kernel on next bootup.... basically the ROMs which use FreeXperia Recovery but donot boot custom kernel by default... or users who are using freexperia recovery to test custom kernels can also use this file...
xRecovery-1.0.0-rbt_test_kexec.zip"
The first one for 2.2 who dont require custom kernel by default. e.g.: FreeX10
or the second one for 2.1/2.2/2.3 roms?
EDIT: I just went ahead and did it...seems to boot into 2.1 fine.....will report back on issues later (Hopefully none)
Also, If i make a backup now using 1.0.0 am i right in thinking this should be a correct backup I can restore and it using xrecovery?
Finally just tried to reboot my phone i get a blackscreen that just says "Switched to fastboot mode..."
Any ideas?
EDIT 2: I pulled the battery and it booted into wolfs 2.2....Its looking good.
OK.
I have lost custom kernal on wolfs ROM. Is there any way to get that back and have the dual boot.
Secondly, When using adb to push wifi.ko to wolfs rom i get
cannot stat 'wifi.ko': No such file or directory
Any ideas?
EDIT.
I seeem to have pushed the file now but still get an error....also lsmod does not give me a wifi.ko listed..just the undervolt, twofish, dm_crypt and dm_mod modules....
I have even edited the hw config file to
insmod /system/lib/modules/wifo.ko
I really need wifi, otherwise I will have to give up on the dualboot
Sorry correction
you will miss your current kernel if you want to use your current kernel...
wait for some time i will post update on it.
Introduction
This thread describes an experimental mod that allows you to boot into other boot images stored in your sdcard.
The N1 does not have enough internal memory to store more than one android image, thus we have to use the sdcard for this.
NOTE:
This mod is experimental, and for advanced users only
Requirements (READ THEM CAREFULLY):
- A rooted and unlocked phone
- A FAST enough sdcard. This mod will work with any sdcard but I'd suggest at least a Class 4 card for performance reasons
- Your sdcard should have enough free space. Each 'boot option' that you create reserves 400MB of space in your sdcard
- In order to create a new boot option, you need a flashable zip over CWM of the ROM you wish to boot to. The flashable zip of the ROM is the same that is used for usual ROM installation. Also the zip should be using the latest update-binary format as is scripted in updater-script (e.g. the mount command takes 4 args, etc.)
Advanced Information regarding the process
- The mod requires a boot.img that is flashed by the zip. This is used for extracting the ramdisk, commenting out the mount mtd commands and using this ramdisk for chrooting into the ROM environment
- If no boot.img is existing, the ramdisk is picked up from /sdcard/ramdisk/
- The kernel used for booting all boot options is the one installed in the phone's boot mtd. This means that you need the respective kernel modules (e.g. WiFi) for this kernel, not the one that is bundled in the ROM that is multibooted. For example, if your main ROM is CM, pick the kernel modules from this one and push them to the multibooted ROM's /system/lib/modules/
Multiboot mod Installation
Download: N1_CWM-4.0.0.5-nobodyAtall-r2.img
Install via fastboot
Code:
Copy N1_CWM-4.0.0.5-nobodyAtall-r1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash N1_CWM-4.0.0.5-nobodyAtall-r1.img
Install via adb
Code:
adb push N1_CWM-4.0.0.5-nobodyAtall-r1.img /sdcard/
adb shell 'flash_image recovery /sdcard/N1_CWM-4.0.0.5-nobodyAtall-r1.img'
adb reboot recovery
Multiboot ROM Installation
- Boot into the recovery and navigate to the new 'multiboot' menu. There you'll see the following options:
Boot into selected option!
Select default boot option
Unset default boot option
Create boot option from zip
Delete existing boot option
Flash zip to boot option
- Select multiboot->Create boot option from zip and then pick the flashable ROM zip. Be patient, this step reserves the space and flashes the selected zip to the system.img in the sdcard
- If you need to flash additional zips for this ROM, Select multiboot->Flash zip to boot option, pick your newly created boot option and then pick the zip you need to flash.
- Select multiboot->Select default boot option and pick your newly created boot option
- Select multiboot-> Boot into selected option! (first boot will take some time depending on your sdcard speed).
To verify you have booted to your newly created boot option, check 'adb shell mount', it should say that /system /data and /cache is mounted from /loop* devices and not from mtd*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROMS verified to multiboot
Well, any ROM should be able to multiboot provided the requirements stated above are covered. The following ones have been verified to work:
[ROM] CyanogenMod-7.1 for Nexus One
[ROM] NEXUS N1 Passion MIUI.us Presents MIUI Pure English [AOSP]
CM 7 ExtremeMod ROM by Ken Mood
Uninstall
- Normal reboots will boot from the phone's mtd partitions.
- This mod makes no changes to your phone's mtd partitions. Flashing a new recovery will uninstall the old one obviously.
- To remove installed boot options, navigate to multiboot->Delete existing boot option and pick you choice. Alternatively remove the boot option you want from /sdcard/clockworkmod/multiboot/
Disclaimer:
I can't be held responsible if this mod bricks your device / trashes your sdcard or makes it explode in your hands! Use it at your own risk!
Changelog:
(1/7/11) N1_CWM-4.0.0.5-nobodyAtall-r2.img
Fixed bug that flashed the multiboot ROM kernel in the phones kernel partition
Improved error reporting
(30/6/11) N1_CWM-4.0.0.5-nobodyAtall-r1.img
First version of CWM recovery providing the multiboot options
woww thanks
Well, this could be freaking awesome. I'll check it out at work
Nice one. Can we use CM nightlies that came after the RC?
method77 said:
Nice one. Can we use CM nightlies that came after the RC?
Click to expand...
Click to collapse
You can use it with any CM7 ROM
I am interested in this, i'm surprised that it hasn't created more of a stir.
I have installed the recovery, but don't want to do anything else without Nandroiding first. Only Nandroid seems to get stuck on "Backing up system..."
Any i doing something wrong?
Hello shorza,
To be honest, I've only been testing the multiboot part.
However, I think that backup works fine here:
Also the backup folder is created correctly:
~ # ls -la /sdcard/clockworkmod/backup/2011-07-01.06.49.58
drwxrwxrwx 2 root root 4096 Jul 1 06:52 .
drwxrwxrwx 5 root root 4096 Jul 1 06:49 ..
-rwxrwxrwx 1 root root 93489792 Jul 1 06:52 .android_secure.img
-rwxrwxrwx 1 root root 3670016 Jul 1 06:50 boot.img
-rwxrwxrwx 1 root root 37359168 Jul 1 06:52 cache.img
-rwxrwxrwx 1 root root 184136832 Jul 1 06:51 data.img
-rwxrwxrwx 1 root root 222 Jul 1 06:53 nandroid.md5
-rwxrwxrwx 1 root root 4194304 Jul 1 06:50 recovery.img
-rwxrwxrwx 1 root root 146908608 Jul 1 06:50 system.img
On another note, I'll be doing an update today to fix some bugs related to multiboot.
CWM 4.x has problems backing sd-ext, so that might be the reason why you don't see it (your pic shows you don't have an sd-ext partition to backup) and shorza does. It is also the reason why I haven't tried this yet - if it was based on AmonRa's I'd have jumped immediately, but since it is based on CWM I wanted first to see some feedback here...
Thanks for the help. Backup eventually worked, it just took a long time.
The problem is after zipping a new rom in multiboot, selecting it, then trying to boot into it, it took too long and I lost patience. It looked like it froze.
I'll try again tomorrow.
Maybe my sdcard is too slow.
shorza said:
Maybe my sdcard is too slow.
Click to expand...
Click to collapse
You need to be patient. It takes a long time to boot (especially for the first boot) and if the recovery seems frozen, this is a good sign - it means it's booting.
Posted -r2.
This fixes a bug that would flash the multiboot ROM's kernel to the phone's kernel partition. Also improves logging in case of errors.
Testing this out right now ... just got latest cyanogenmod nightly and latest miui (as of today) going on it and just switched back and forth. sucks about having to go into recovery to switch, needs to have a boot option when starting the phone haha.
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Will this work like a nandroid backup where it saves everythn from my last boot? Or will it save everythn on that same img. when i switch roms
looking at the directory structure, per multiboot rom it saves the boot.img, cache.img, data.img, and system.img .... I don't know how it uses them, but linux is magical in mounting images as a partition, doesn't have to be physical
This is because the ROM is run using the device's kernel and not the one that comes with the ROM as stated in the first post.
To make wifi work, simply copy your wifi kernel module from /system/lib/modules to this same did within the multibooted ROM.
Ellises said:
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
This actually works pretty well, however, the phone get quite hot.
[Q]Bug fixed??
I succeed multibooting
I got miui(main)&CM7(sub)
but subrom,cm7 can't use wifi
so I changed kernel but failed
and display
[mount expects 4 3args]
[error /sdcard/xxx... ]
[ status7 ]<<maybe
If you know what's the problem, plz teach me the way
thx and pardon my English
Before unlocking your bootloader, read this thread
If you brick your device, you are the sole responsible.
Preface:
Read through this post. Don't rush into flashing. Be sure you understand the process before you start
This is a custom kernel developed for Android Jellybean
Do NOT try this kernel on other Android versions - you are totally unsupported
This kernel introduces custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Features:
Forked from nAa-ics-04 (all ICS features are already in there)
Built with linaro-4.7.1 toolchain
CWM-Based Recovery 5.5.0.4
Custom mtd partitioning scheme suitable for JB
Modular recovery flashing support (more on that to come...)
Tracing support for JB
pmem: bring up2date with CAF 2.6.38
genlock/kgsl fixes
Triple buffering support for msm framebuffer
Much more RAM for improved multitasking experience (shakira: 186MB, robyn/mimmi: 187MB)
FAQ:
If you have any issues, please read the FAQ thread first: http://forum.xda-developers.com/showthread.php?p=30297163
Requirements:
Unlocked bootloader --> http://forum.xda-developers.com/showthread.php?t=1254225
MiniCM10 or any JB, source-based ROM (install this kernel first, format /system, /data and /cache, then install the JB ROM)
Flashtool tested to be working with your phone, e.g. from here: http://www.multiupload.com/GYL7A7XQBT Original flashtool thread: http://forum.xda-developers.com/showthread.php?t=920746
Install:
Backup
Unlock your bootloader as described here: http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3 or here: http://forum.xda-developers.com/showthread.php?t=1254225
Download the kernel ftf file from here and move it to Flashtool\firmwares so that Flashtool can pick it up
Flash the kernel via Flashtool
Reboot and you should see the kernel boot animation
[*] (First time only) Get into recovery and format /system /cache and /data manually
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uninstall:
Flash back to stock using SEUS.
OR
[*] Format /system /data and /cache via CWM and THEN flash another kernel via Flashtool
Notes:
Dualtouch (for synaptics):
If you want to enable the fake DT by dx (instead of andrej456's which is the default), you have to insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_dt.ko
Click to expand...
Click to collapse
If you want to remove the fake DT altogether, insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_no_dt.ko
Click to expand...
Click to collapse
Sources:
The linux kernel is GPL'ed, everyone who does modifications should make them publicly available.
https://github.com/nobodyAtall/nAa-kernel-jb
Donate:
If you are enjoying my work please consider donating:
.
Donations are voluntary but allow me to spend more time on this project.
Disclaimer:
I can't be held responsible if this Kernel bricks your device or makes it explode in your hands! Use it at your own risk!
Changelog:
### nAa-jb-02
* Ramdisk changes
* Increase vm_max_readahead to 1024Kb
### nAa-jb-01
* Forked from nAa-ics-04
* Tracing support for JB
* pmem: bring up2date with CAF 2.6.38
* genlock/kgsl fixes
* Triple buffering support for msm framebuffer
* Much more RAM
* Custom mtd partitioning for JB
MTD partitioning for Jellybean:
localhost / # cat /proc/mtd
dev: size erasesize name
mtd0: 10500000 00020000 "system"
mtd1: 00500000 00020000 "cache"
mtd2: 0bfc0000 00020000 "userdata"
mtd3: 00a00000 00020000 "recovery"
localhost / # df -h
...
/dev/block/mtdblock0 261.0M 238.1M 22.9M 91% /system
/dev/block/mtdblock2 191.8M 86.5M 105.3M 45% /data
/dev/block/mtdblock1 5.0M 780.0K 4.2M 15% /cache
...
reserved for FAQ
Read Before Asking Please
FAQ for MiniCM10 and nAa kernel
reading may answer to lots of your questions !
for X10mini, X8 & x10miniPRO
i decided to create a new thread dedicated to Q&A about miniCM10
so please, as usual, read FAQ, use search option or anything else before asking commonly answered questions
the FAQ will be incremented when needed
the Q&A is written as Q are asked
something else that is useful to read before asking :
Here we (nearly all? XDA members, regardless of being devs or only users [like me], me at least ) don't care about your good/bad English the important is trying to be understood and to understand the content of the threads
only ask things you can't find, or you don't understand, please if you don't understand something in any process tell us exactly where is your problem : it will optimize the answer
sometime rephrasing things can make you understand better, feel free to help us for making the most understandable sentence for anybody
BUT if you don't make the effort to read, I won't make the effort to answer (ok, you can't read everything... but read the minimum )
Chatroom for support is now available (http://minicm.ie.tc/)
clic on the red text above
register, and then enjoy ________________________________
clic here for : FAQ
this post will be updated with the very last Questions added to FAQ about the ROM for quick view
________________________________
bug tracking template :
twins.7 said:
#BUG Report
DO
Reboot - Recovery
BUG
the screen stuck in rebooting dialog. It should just rebooting
ACTION
press home key (or any key maybe) to make it reboot
Click to expand...
Click to collapse
_________________________
useful links :
[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
$find other useful link in miniCM7/9 miniFAQs $
Perfomance :
recomended settings :
perf related :
CPU: keep default, but enable UnderVolting (and set on boot if you don't OverClock) (settings>performance>CPU)
RAM : to optimize RAM usage, use KSM, zram (18%, default) and allow purging of assets (settings>performance>memory managment)
I/O : keep NOOP, this is the default and the best for flash memory
other :
in settings>developer options
enable USB debugging,
debug notification,
set all animations to 0.5 (electron beam CRT animation will happen no more)
enable "kill with back button"
________________
for whose who feel the system slow and laggy, just try the SWAP (SDcard class6+ recommended)
SWAP, there is two "kind" of swap : using a partition on the SDcard, or using a swap file
both are good, but some SDcard/phones react better with the one or the other
let us start with the partition way : it is more complicated than the file method, but as some advantages
pros: once it is set up, no need to care about it anymore, the SDcard can be mounted to PC easily without latency
cons: a little complicated to set up, and once it's done, it is as complicated to revert as to set up; to change swap size, you need to repeat the process (formating and partitioning SDcard)
needs a clean install of miniCM10:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size) any data on phone memory will be lost
set up your swap:
==> go to /advanced/Partition SD Card
if you don't want to use a2sd, then choose the minimal size for ext, and the size you want for SWAP
it will FORMAT your SDcard ! any data on SDcard will be LOST
and install the rom
swap partition should work
what doesn't work is the swap info menu
to revert : format SDcard in phone settings : it will FORMAT your SDcard ! any data on SDcard will be LOST
____________________
now, the swap file way : it is really simpler than the swap partition, works great but has some drawbacks
pros: easy to set up, easy to revert, and the size can be choosen at wish at anytime (in settings>performance>memory>Swap settings)
cons: high latency when mounting SDcard to pc, it can take forever (really quicker to use CWM mount and storage capability to use the SD on the PC, than using android way)
you must perform a clean install of miniCM10 (by formating /system, /data and /cache) any data on phone memory will be lost
install the rom zip, the gapps, and boot up your phone
set it up
once your rom is ready to use,
go to settings>performance>memory>Swap settings
choose "enabled"
choose the size
allow system to get SU permissions
wait for the pop up "swap enabled"
enjoy, it is simple and can be disabled on wish
to see if you swap works, open terminal, and type the following :
Code:
free
Sorry, are you some you forgetting where you are!!:silly:
This is a Development thread so treat it like one!
Take this as your warning, any further off spam posts and you will be infracted.
@nobodyAtall
Why there isnt 6.0.1.1 recovery in the kernel? Not possible or you tried and you got errors?
And second thing. Is possible to get 192 MB free in Gingerbread kernel?
whr is kernal?
monu09 said:
whr is kernal?
Click to expand...
Click to collapse
this is kener for CM10
Xmaster8 said:
@nobodyAtall
Why there isnt 6.0.1.1 recovery in the kernel? Not possible or you tried and you got errors?
And second thing. Is possible to get 192 MB free in Gingerbread kernel?
Click to expand...
Click to collapse
This kernel has modular recovery. This means that you will be able to flash any recovery you like without the need to flash another kernel. There's no need to change everything at the same time! Existing recovery is pretty stable.
And 192MB isn't possible for GB without breaking stuff.
I can't download the kernel...
Sent from my E15i using xda app-developers app
me too cant download
DJ_Mike_Jams said:
I can't download the kernel...
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
And neither the ROM
EDIT: Sorry, problem solved
now can download thank you NAa
will try this kernel and cm10
What happens if I use this on MiniCM 9 just curious
RohinZaraki said:
What happens if I use this on MiniCM 9 just curious
Click to expand...
Click to collapse
It's nAa ICS 4 with a new ramdisk and more features i guess, but it won't boot up due the new ramdisk (not sure about it).
Anyway it's working really fine.
Much more RAM for improved multitasking experience (shakira: 192MB, robyn/mimmi: 195MB)
LOL you are the BEST!!!!!!!!!
I have a problem with the kernel. When I reboot after flashing the kernel, the nAa logo appear, the LED turns purple and the phone reboots. What is the solution please ?
Try to flash phone with pccompanion or seus and flash naa jb kernel.
Neur0Nerd said:
I have a problem with the kernel. When I reboot after flashing the kernel, the nAa logo appear, the LED turns purple and the phone reboots. What is the solution please ?
Click to expand...
Click to collapse
I have same problem ;/
Before unlocking your bootloader, read this thread
If you brick your device, you are the sole responsible.
Preface:
Read through this post. Don't rush into flashing. Be sure you understand the process before you start
This is a custom kernel developed for Android Jellybean
Do NOT try this kernel on other Android versions - you are totally unsupported
This kernel introduces custom mtd partitioning with larger /system partition to hold the extra JB calories. If you are moving from another custom kernel to this one, you MUST first format /system /data and /cache via the embedded CWM recovery
Features:
Forked from nAa-ics-04 (all ICS features are already in there)
Built with linaro-4.7.1 toolchain
CWM-Based Recovery 5.5.0.4
Custom mtd partitioning scheme suitable for JB
Modular recovery flashing support (more on that to come...)
Tracing support for JB
pmem: bring up2date with CAF 2.6.38
genlock/kgsl fixes
Triple buffering support for msm framebuffer
Much more RAM for improved multitasking experience (shakira: 186MB, robyn/mimmi: 187MB)
FAQ:
If you have any issues, please read the FAQ thread first: http://forum.xda-developers.com/showthread.php?p=30297163
Requirements:
Unlocked bootloader --> http://forum.xda-developers.com/showthread.php?t=1254225
MiniCM10 or any JB, source-based ROM (install this kernel first, format /system, /data and /cache, then install the JB ROM)
Flashtool tested to be working with your phone, e.g. from here: http://www.multiupload.com/GYL7A7XQBT Original flashtool thread: http://forum.xda-developers.com/showthread.php?t=920746
Install:
Backup
Unlock your bootloader as described here: http://forum.xda-developers.com/showpost.php?p=17384177&postcount=3 or here: http://forum.xda-developers.com/showthread.php?t=1254225
[*]Download the kernel ftf file from here and move it to Flashtool\firmwares so that Flashtool can pick it up
Flash the kernel via Flashtool
Reboot and you should see the kernel boot animation
[*] (First time only) Get into recovery and format /system /cache and /data manually
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uninstall:
Flash back to stock using SEUS.
OR
[*] Format /system /data and /cache via CWM and THEN flash another kernel via Flashtool
Notes:
Dualtouch (for synaptics):
If you want to enable the fake DT by dx (instead of andrej456's which is the default), you have to insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_dt.ko
Click to expand...
Click to collapse
If you want to remove the fake DT altogether, insert the following line in the /system/etc/hw_config.sh file:
insmod /system/lib/modules/synaptics_i2c_rmi4_no_dt.ko
Click to expand...
Click to collapse
Sources:
The linux kernel is GPL'ed, everyone who does modifications should make them publicly available.
https://github.com/nobodyAtall/nAa-kernel-jb
Donate:
If you are enjoying my work please consider donating:
.
Donations are voluntary but allow me to spend more time on this project.
Disclaimer:
I can't be held responsible if this Kernel bricks your device or makes it explode in your hands! Use it at your own risk!
Changelog:
### nAa-jb-02
* Ramdisk changes
* Increase vm_max_readahead to 1024Kb
### nAa-jb-01
* Forked from nAa-ics-04
* Tracing support for JB
* pmem: bring up2date with CAF 2.6.38
* genlock/kgsl fixes
* Triple buffering support for msm framebuffer
* Much more RAM
* Custom mtd partitioning for JB
MTD partitioning for Jellybean:
localhost / # cat /proc/mtd
dev: size erasesize name
mtd0: 10500000 00020000 "system"
mtd1: 00500000 00020000 "cache"
mtd2: 0bfc0000 00020000 "userdata"
mtd3: 00a00000 00020000 "recovery"
localhost / # df -h
...
/dev/block/mtdblock0 261.0M 238.1M 22.9M 91% /system
/dev/block/mtdblock2 191.8M 86.5M 105.3M 45% /data
/dev/block/mtdblock1 5.0M 780.0K 4.2M 15% /cache
...
useful links :
[DEV] miniCM10 debug only thread (shakira, robyn and mimmi)
$find other useful link in miniCM7/9 miniFAQs $
Perfomance :
recomended settings :
perf related :
CPU: keep default, but enable UnderVolting (and set on boot if you don't OverClock) (settings>performance>CPU)
RAM : to optimize RAM usage, use KSM, zram (18%, default) and allow purging of assets (settings>performance>memory managment)
I/O : keep NOOP, this is the default and the best for flash memory
other :
in settings>developer options
enable USB debugging,
debug notification,
set all animations to 0.5 (electron beam CRT animation will happen no more)
enable "kill with back button"
________________
for whose who feel the system slow and laggy, just try the SWAP (SDcard class6+ recommended)
SWAP, there is two "kind" of swap : using a partition on the SDcard, or using a swap file
both are good, but some SDcard/phones react better with the one or the other
let us start with the partition way : it is more complicated than the file method, but as some advantages
pros: once it is set up, no need to care about it anymore, the SDcard can be mounted to PC easily without latency
cons: a little complicated to set up, and once it's done, it is as complicated to revert as to set up; to change swap size, you need to repeat the process (formating and partitioning SDcard)
needs a clean install of miniCM10:
flash JB kernel
in CWM, go to mount&storage :
then, format /system, /data and /cache (so that kernel can use the new partitions size) any data on phone memory will be lost
set up your swap:
==> go to /advanced/Partition SD Card
if you don't want to use a2sd, then choose the minimal size for ext, and the size you want for SWAP
it will FORMAT your SDcard ! any data on SDcard will be LOST
and install the rom
swap partition should work
what doesn't work is the swap info menu
to revert : format SDcard in phone settings : it will FORMAT your SDcard ! any data on SDcard will be LOST
____________________
now, the swap file way : it is really simpler than the swap partition, works great but has some drawbacks
pros: easy to set up, easy to revert, and the size can be choosen at wish at anytime (in settings>performance>memory>Swap settings)
cons: high latency when mounting SDcard to pc, it can take forever (really quicker to use CWM mount and storage capability to use the SD on the PC, than using android way)
you must perform a clean install of miniCM10 (by formating /system, /data and /cache) any data on phone memory will be lost
install the rom zip, the gapps, and boot up your phone
set it up
once your rom is ready to use,
go to settings>performance>memory>Swap settings
choose "enabled"
choose the size
allow system to get SU permissions
wait for the pop up "swap enabled"
enjoy, it is simple and can be disabled on wish
to see if you swap works, open terminal, and type the following :
Code:
free
Thanks!!!!!!!!!!!!!!!!!!!!!!!!!!111
I have a problem trying to go from 2.3 to 4.1:
- i flash the new JB kernel
- restart the phone
- when is loading the "nAa" startup, exact when its on "freed" of "freedom" it freeze and reboot, i cant go into in cwm to flash the JB
if i reflash 2.3 kernel, it boot ok.
any has the same problem?
ty.
(my english suck, sry )
SOLVED: http://forum.xda-developers.com/showpost.php?p=30329524&postcount=16 , thanks he.
after i flashed kernel, the phone turns on but nothing happens. the boot logo doesnt show up. then i tried to flash the ics kernel, wich i used before, and its the same. repaired the phone with pc companion and tried again, same result. :-/ if im condemned to use stock kernel and rom, ill break the phone -.-
MiniCM10 on the way
Sent from my Nexus One using Tapatalk
This Guy can do Anything... nobodyAtall is genious.
First of all, thanks for your great work! :victory:
Then, just a question: i have already unlocked bootloader (in fact, i put MiniCM7-2.2.1 & nAa-13 Custom Gingerbread kernel - both by nAa - on my X10 Mini)...should i to repeat the process describe here? ---> http://forum.xda-developers.com/showthread.php?t=1254225 ?
If i don't understand badly, i have "only" to perform factory reset, wipe cache partition and wipe dalvik cache from recovery, isn't it? Then flash custom kernel & ROM. Like described there ---> http://forum.xda-developers.com/showpost.php?p=30329524&postcount=16
Thanks again
Greetings from Italy
sith.warrior said:
First of all, thanks for your great work! :victory:
Then, just a question: i have already unlocked bootloader (in fact, i put MiniCM7-2.2.1 & nAa-13 Custom Gingerbread kernel - both by nAa - on my X10 Mini)...should i to repeat the process describe here? ---> http://forum.xda-developers.com/showthread.php?t=1254225 ?
If i don't understand badly, i have "only" to perform factory reset, wipe cache partition and wipe dalvik cache from recovery, isn't it? Then flash custom kernel & ROM. Like described there ---> http://forum.xda-developers.com/showpost.php?p=30329524&postcount=16
Thanks again
Greetings from Italy
Click to expand...
Click to collapse
you don't have to relock or reunlock your bootloader, follow the instructions of format /system and others in cwm menu, and then flash the jb kernel. Happy testing
Hey nAa, the link you gave in the OP to download the kernel is the E10 kernel.
That's why many people complain that didn't work.
I downloaded the right kernel on minicm.googlecode.com
EDIT: This thread is right, on MiniCM10 for x10 mini pro Thread, you send people to this Kernel, instead the u20 kernel. that's the thing
first of all... i installed jb via recovery...then installed kernel and came upto home of launcher but the touchscreen is unresponsive...i mean the side buttons home keys etc. work fine but the touchscreen doesnt...help....
Password Protections
Hey nAa, is there anyway so we can password protect the clockworkmod recovery?? Just for security reasons (prevent someone from wiping the data partition)....
Hi,for x10 mini the kernel is E10 or u20?
mauwri37 said:
Hi,for x10 mini the kernel is E10 or u20?
Click to expand...
Click to collapse
Take off your back-cover, you will find a sticker with the model-number of your phone... Download the kernel corresponding to that number.
X10 Mini = E10 (i or a) = Robyn
X10 MiniPro = U20 (i or a) = Mimmi
how to access cwm in this kernel!!! help.... menu button? back button?? just a bootloap..
Flashed wrong kernel
Guys,
I know this will be a really noob question, but still... After spending some time reading this guide, I ended up dowloading X10 Mini (e10 or whatsoever kernel and I installed it to my u20 (X10 Mini Pro. Now FlashTool gives me error - flashing aborted messages every time I want to install the correct kernel.
Is there anything /i can do?
Thanks,
Regards
kog said:
Guys,
I know this will be a really noob question, but still... After spending some time reading this guide, I ended up dowloading X10 Mini (e10 or whatsoever kernel and I installed it to my u20 (X10 Mini Pro. Now FlashTool gives me error - flashing aborted messages every time I want to install the correct kernel.
Is there anything /i can do?
Thanks,
Regards
Click to expand...
Click to collapse
Yes, just flash the correct kernel and you should be fine.
nobodyAtall said:
Yes, just flash the correct kernel and you should be fine.
Click to expand...
Click to collapse
If didn't work, try use SEUS to put phone with default kernel and then try using u20i kernel. Loock for my post above you find it.
The JB XXLSJ leak and the latest XWLS8 official JB releases have introduced a new partition on /dev/block/mmcblk0p12 mounted to /preload.
This was required due to the fact that the /system partition just isn't big enough to hold all the extra apps the JB leak requires.
The problem with this is that with the exception of PhilZ Kernel and Jeboo, CWM backups in bith Siyah and DorimanX omit the backing up this /preload partition. If you regularly try out different ROMs and restore back, this can mean your ROM's getting a little out of step as it would have the /preload files from the ROM you last flashed, with all other files coming from the ROM you performed the backup on.
Currently, if you are on Siyah/Dori, the only way to backup/restore everything via CWM backups is to:
a) reboot into recovery
b) flash PhilZ/Jeboo
c) go to advanced>reboot recovery
d) make your backup in PhilZ/Jeboo/Apolo recovery
and if you want to revert back to Siyah/Dori:
e) flash Siyah/Dori
f) advanced>reboot recovery
If you ever need to restore, and you are using Siyah/Dori then you will need to:
a) reboot into recovery
b) flash PhilZ/Jeboo
c) go to advanced>reboot recovery
d) restore your backup in PhilZ/Jeboo/Apolo recovery
e) flash Siyah/Dori
f) reboot
NOTE: Later versions of PhilZ require you to specifically set the backup/restore of /preload. This is done in PhilZ CWM Recovery:
1. boot into PhilZ recovery
2. Philz settings
3. Special backup and restore
4. Misc nandroid settings
5. Toggle /preload processing (make sure this says /preload will be processed)
To get around this current omission in Siyah and Dori, I have written the following 2 CWM flashable zips:
GS2PreloadBackup
This will backup your current /preload partition.
The backup is made on a per-ROM basis to /sdcard/MyBackups/preload/[ROM-Name]/preload.tar. Therefore, if you backup on several different ROMs, you will get several ROM folders in this preload backup location, one backup per ROMGS2PreloadRestore
This will restore the /preload backup made by the above script for your current ROM.
So if you are on Siyah/Dori and want to make a full backup without flashing between PhilZ, you can now do the following:
1. Boot up into recovery
2. Make your CWM backup
3. Run GS2PreloadBackup.zip
Further down the line, if you ever wanted to restore this, then
1. Boot up into recovery
2. Restore your CWM backup
3. Flash GS2PreloadRestore.zip
The restore is sensitive to the ROM you are currently on, so it will only restore the /preload for you current ROM, provided you have run the backup script previously for the ROM of course.
Changing the backup location
By default, backups are made to the internal SD card in /sdcard/MyBackups as described above. You can change the backup location to the external SD card if required. This can be done by editing /sdcard/MyBackups/HawkerOptions/MyWipeOptions.prop. Within this file there is a line that tells the script where the backups are to be stored. Edit the following line as required:
BKP_LOCATION=int (backs up to INTERNAL SD Card, ie. /sdcard/MyBackups)
BKP_LOCATION=ext (backs up to EXTERNAL SD Card, ie. /storage/extSdCard/MyBackups)
Please note, that if you change the location between int/ext in MyWipeOptions.prop, your backups will not get automatically moved to the new location. You would have to manually move the current backup over to the new location if you do not want to potentially have two copies of the backups.
Test Mode
The script inside the zip file that does all the work is called GS2Hawker.sh. This can be called via adb shell/Script Manager etc. in order to perform a test dummy-run. The Test Mode goes through all the motions as per a standard CWM Recovery run, but it does not remove any files/folders in any way, and merely shows the commands it would have done.
eg. extract GS2Hawker.sh from the zip using 7Zip or similar
adb shell
sh GS2Hawker.sh PreloadBackup
sh GS2Hawker.sh PreloadRestore
Summary of Files Created/Used
1. /sdcard/MyBackups/HawkerLogs/GS2PreloadBackup.log.
2. /sdcard/MyBackups/HawkerLogs/GS2PreloadRestore.log.
These shows the activity log of what the script has done. This gets overwritten the next time you run the script.
3. /sdcard/MyBackups/HawkerOptions/MyWipeOptions.prop. Options file for all my scripts. Currently this contains the option for backup location, internal or external SD card. (See Changing the backup location above)
These scripts are of course only a temporary measure as I am in no doubt that both Siyah and Dori will both also include the /preload partition in their CWM Recovery scripts very shortly, but for now, I hope this might help one or two of you out.
Known Issues
Free space checking prior to performing the backup always returns free space on internal sdcard even when
backing up to external sd card.
For some reason, when I do a df (on Siyah, not sure about other kernels)
I get the following:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p11
12063840 231264 11832576 2% /mnt/.secondrom
/dev/block/mmcblk1p1 12063840 231264 11832576 2% /sdcard
/dev/block/mmcblk0p11
12063840 231264 11832576 2% /sdcard
/dev/block/mmcblk1p1 30648992 17592608 13056384 57% /emmc
It appears /dev/block/mmcblk1p1 is mounted to /emmc AND /sdcard?????!!!!
All file operations on /emmc gets performed on the extenral sd card as expected (ie your backups WILL go to external), BUT when the df command is issued to check for available space, it is performed on /sdcard! Therefore, if the script is trying to find the space left on /emmc, and the device returned from the df command is /sdcard, then an error is presumed, an no space check performed.
Please Note
I use these scripts myself between many flashes of different ROMS, and are provided here, as-is, out of my passion for development. Although every effort has been made to ensure everything works correctly on my handset I cannot be held responsible if things get messed up, or if you put something in your user-definable files that you shouldn't have included. As with everything else on here, you flash anything at your own risk. I always recommend performing a full CWM backup before attempting to flash anything onto your device.
Current Versions
GS2PreloadBackup 1.05 (22/05/2013)
GS2PreloadRestore 1.05 (02/03/2013)
Note: If the latest versions quoted above do not appear in the download devhost site, then please be patient!
ApriliaM3 should soon be uploading them.
Downoad Here
Download Here
My HUGE thanks goes out to ApriliaM3 for hosting the scripts.
Please give him the thanks he deserves.
To Do
....
Work in Progress
....
Changelog
GS2PreloadBackup v1.05 (22/05/2013)
1. Extra free space checking. (See OP for known issues)
GS2PreloadBackup v1.04 GS2PreloadRestore v1.05 (02/03/2013)
1. Backups can now go to either internal or external SD Card. See Post #1 for details
GS2PreloadRestore v1.04 (22/02/2013)
1. Now restores /preload/symlink instead of whole of /preload for greater flexibility in dual-boot systems
2. Current /preload/symlink contents removed before restore giving a better snapshot for the restore point
GS2PreloadBackup v1.03 (22/02/2013)
1. Now backs up /preload/symlink instead of whole of /preload
GS2PreloadRestore v1.03 (22/02/2013)
1. Current /preload contents removed before restore giving a better snapshot for the restore point
2. Progress now given in Mb during the restore process
v1.02 (13/02/2013)
1. Numerous display updates
2. Log file now goes to /sdcard/MyBackups/HawkerLogs so that they are grouped with logs from my other scripts
v1.01 (31/01/2013)
1. Progress now given during backup operation of the size of backup complete
Thanks buddy:thumbup::thumbup:. I just wanted to get in first. :thumbup::thumbup:
Edit. I just ran a backup and it worked and so did the restore :thumbup:
In the meantime I'll leave this picture until I can post something constructive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk 2
Main ROM: Alliance rom v5.2
KERNEL : Dorimanx 7.39
(DEFAULT PROFILE AND SETTINGS )
MODEM : BVLP7
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex
My Guides list to install NeatRom and other ROMS and kernels on LSJ + tools to have a bug free rom + how to back up and RESTORE FOM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Rom Nuke script
http://forum.xda-developers.com/showthread.php?p=36268094
2.Kernel Clean script
http://forum.xda-developers.com/showthread.php?p=34879811
3.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
4. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
Nice guide
Sent from my GT-I9100 using xda premium
Thanks Hawker, great work.
Red you got a nice ass!
Edit. ... I have done a backup and ran the zip after it and it worked great.
Thank you!
Sent From My Galaxy S2 Running
AllianceROM Powered By DorimanX Kernel
Some more great work and another great guide there Paul... well done!
I have now created a directory for your work on my Dev-Host mirror site HERE
ApriliaM3 said:
Some more great work and another great guide there Paul... well done!
I have now created a directory for your work on my Dev-Host mirror site HERE
Click to expand...
Click to collapse
Thanks Pete.
I've updated the links in the OP to yours.
I'll let you know if I update the scripts at all.
Cheers mate!
:good:
Thank you, really usefull script.
deleted
Updated to V1.01
See Changelog for details
hawkerpaul said:
Updated to V1.01 (pending upload to ApriliaM3's host.....)
Click to expand...
Click to collapse
All done Paul.
hawkerpaul said:
Updated to V1.01
See Changelog for details
Click to expand...
Click to collapse
I have been trying to backup preload to my external sd card by modifying /sdcard/MyBackups/MyBakDevice.txt ( see screenshot)
But the backup is stil made on the internal and after every attempt the content of MyBakDevice.txt is set back to the default /sdcard
I'm I doing something wrong here
EDIT: Tried 3 times, same result every time.
Backup to external sd card not possible currently, so I'm looking into getting this working properly. For now, ignore any information relating to MyBakDevice.txt. All backup will go to internal sd card only for the time being.
Updated to V1.02
See post #2 for details
Updated GS2PreloadRestore to v1.03
See post#2 for details
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
This is awesome, thanks for your work!!!!!
May I ask something? (if not, ignore me)
Is it possible to not backup the full /preload partition but only the /preload/symlink part of it? I ask because it would be very helpful with this : http://forum.xda-developers.com/showthread.php?p=38209559
So, a user could backup /preload/symlink/... Then install a 2nd Rom, that will probably format /preload and just restore it easily with your File. This might be a very big step for Dual boot as it makes so many things easier!
Anyways, thank you very much for your efforts!!!
Greetings
Thomas
Sent from my GT-I9100 using xda app-developers app
As far as I'm aware, apart from the generic lost+found folder linux creates under each partition (which 99% of the time will be empty) the only contents of the /preload partition IS the symlink folder.
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
hawkerpaul said:
As far as I'm aware, apart from the generic lost+found folder linux creates under each partition (which 99% of the time will be empty) the only contents of the /preload partition IS the symlink folder.
Click to expand...
Click to collapse
Thanks!
But in my /preload there is the /symlink part of my Sammy Rom (shorted to about 80mb) and the /system of 2nd Rom (MCM's 10.1)
The created Backup with your zip is about 390mb big so I figured that there has to be more than just the symlink stuff.
This could be solved, of course by a clean install of first Rom (Sammy), backup with your file, install 2nd Rom and then restore /preload.
But it would be easier if only /preload/symlink would be backed up and later restored.
But, important, I don't want to bug you, it's awesome as it is, seriously!!
Greetings
Thomas
Sent from my GT-I9100 using xda app-developers app
Ok mate, I'll have a look into it for you.
Edit:
Updated to GS2PreloadBackup v1.03 and GS2PreloadRestore V1.04
See post #2 for details
AW: [CWM UTIL] GS2PreloadBackup/Restore scripts for Samsung JB (22/02/2013)
hawkerpaul said:
Ok mate, I'll have a look into it for you.
Edit:
Updated to GS2PreloadBackup v1.03 and GS2PreloadRestore V1.04
See post #2 for details
Click to expand...
Click to collapse
Awesome, thank you very much!!!
If it's ok I will add a how-to to my thread and link to yours?
To me, this is an enormous step forward great!!
Sent from my GT-I9100 using xda app-developers app