Database Info

KingKlick's new Kernel

I wanna try his new kernel out but im having some difficulties.
the link to it is:
http://thedroidsector.com/roms?id=42
First difficulty is when I type in:
rwsystem
it says:
rwsystem: not found.
how can I fix this?
sorry if I posted this in wrong section. still kinda new to this =/
Some Extra Just in Case info:
REQUIREMENTS:
His New AOSP 2.1 v1.3 ROM
1. Might need to make the directories to put the ramzswap.ko and xvmalloc.ko files in.
2. If rwsystem and rosystem doesnt work try:
rwsystem alternative: mount -o rw,remount /dev/block/mtdblock3 /system
rosystem alternative: mount -o r,remount /dev/block/mtdblock3 /system
**Thanks for the Help guys**

do you runned it by root?

yokonunz said:
do you runned it by root?
Click to expand...
Click to collapse
Did I run it in root?
yes
first thing I did.
I am currently trying it on the recovery console and it doesnt work either.

Not all roms have rwsystem, the default way would be
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system

Is possible flash this kernel with adb?

JAguirre1231 said:
Not all roms have rwsystem, the default way would be
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Ahh ok thanks man so that does the same as rwsystem?

Macrophage001 said:
Ahh ok thanks man so that does the same as rwsystem?
Click to expand...
Click to collapse
Yep, and then when you do the rosystem just make that
[cod]mount -o r,remount -t yaffs2 /dev/block/mtdblock3 /system[/code]

JAguirre1231 said:
Yep, and then when you do the rosystem just make that
[cod]mount -o r,remount -t yaffs2 /dev/block/mtdblock3 /system[/code]
Click to expand...
Click to collapse
Thanks dude that helps a lot.
Hmm I hope he posts that up for other people that dont know like me lol.

Wouldn't the following work the same?
su
mount -o rw,remount /system
and then
mount -o ro,remount /system

ciwrl said:
Wouldn't the following work the same?
su
mount -o rw,remount /system
and then
mount -o ro,remount /system
Click to expand...
Click to collapse
It should, but the longer way is always more fun

are the instructions kind of wrong on the droid sector site...

s0mep00p said:
are the instructions kind of wrong on the droid sector site...
Click to expand...
Click to collapse
No certain roms support the rwsystem and rosystem commands...its a truncated way of doing what me and jag posted

no i mean with these two commands:
# cp -f /sdcard/ramzswap.ko /system/modules/lib/modules/2.6.29.6-king/compcache
# cp f /sdcard/xvmalloc.ko /system/modules/lib/modules/2.6.29.6-king/compcache
there are no folders that exist as "2.6.29.6-king", i looked inside the zip for 1.3 and its "2.6.29.6-jac"

crap -.- now my fone is stuck at the g1 screen. I think its cuz I flashed the boot.img.
any suggestions?

Macrophage001 said:
crap -.- now my fone is stuck at the g1 screen. I think its cuz I flashed the boot.img.
any suggestions?
Click to expand...
Click to collapse
How did you flash it?

s0mep00p said:
no i mean with these two commands:
# cp -f /sdcard/ramzswap.ko /system/modules/lib/modules/2.6.29.6-king/compcache
# cp f /sdcard/xvmalloc.ko /system/modules/lib/modules/2.6.29.6-king/compcache
there are no folders that exist as "2.6.29.6-king", i looked inside the zip for 1.3 and its "2.6.29.6-jac"
Click to expand...
Click to collapse
He probably made a mistake on the instructions. try it with -jac instead of -king

JAguirre1231 said:
How did you flash it?
Click to expand...
Click to collapse
Through terminal emulator

Macrophage001 said:
Through terminal emulator
Click to expand...
Click to collapse
Then you should be having no problems. He did say it could take a while to boot

JAguirre1231 said:
Then you should be having no problems. He did say it could take a while to boot
Click to expand...
Click to collapse
yeah true i guess im just impatient.
ima post again after about 20 minutes to say whether it worked or not...
...although I was only able to flash the boot img nothing else then I turned off and wiped everything but I dont think thats gunna affect anything...is it?

s0mep00p said:
no i mean with these two commands:
# cp -f /sdcard/ramzswap.ko /system/modules/lib/modules/2.6.29.6-king/compcache
# cp f /sdcard/xvmalloc.ko /system/modules/lib/modules/2.6.29.6-king/compcache
there are no folders that exist as "2.6.29.6-king", i looked inside the zip for 1.3 and its "2.6.29.6-jac"
Click to expand...
Click to collapse
EDIT: Huh, apparently my blind guessing is wrong. Go about your business.
THE FOLLOWING STATEMENTS ARE DEPRECATED BY THE EXPERIENCES OF OTHERS:
I'm going out on a limb and guessing that if you were to boot the new kernel, `uname -r` would expand to "2.6.29.6-king". Follow the directions, creating the folders if needed. That's where the kernel is going to go looking for its modules. Best to keep your kernels separate. If you boot the new kernel with the modules in the wrong folder, you won't have anything that's built as a module (wifi, compcache, etc.)

[i5500] Guides & Resources

Ok so there doesnt seem to be much work being done on the little gem that is the Samsung GT-i5500/Europa.
So i've done a rummage around and tracked down a few useful things that can be done for any users of the phone.
Since we have no dedicated forum category yet if anyone finds any more details of useful modifications being done on the device then dont hesitate to drop me a PM and i'll add it to the original post.
Flashing and Firmware Updates
-----------------------------
ODIN + Firmware Packages - http://forum.xda-developers.com/showthread.php?t=781149
Rooting
-------
Rooting can be done using UniversalAndroot, works like a dream without any problems even after flashing the latest firmware.
Busybox
-------
Busybox - http://www.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=de&DownloadId=96485
Ok so I found numerous different reports on Busybox stating different mount commands some of which didn't work so well for me.
So here is how I personally got busybox installed and working.
First off grab a copy of busybox from the above link and place it in the root of your SDCard.
The do the following from a command line:
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
dd if=/sdcard/busybox of=/system/bin/busybox
chmod 4755 /system/bin/busybox
mkdir /data/busybox
/system/bin/busybox --install -s /system/bin/
This differs from the /system/xbin instructions I mostly found however works fine and i've yet to find any issues with it.
Market Patch
------------
Market Patch Guide - http://forum.xda-developers.com/showthread.php?t=834959
The above market patch removes the issue of not being able to see all app's on the market.
Apps2SD
-------
Apps2SD Guide - http://forum.xda-developers.com/showthread.php?p=9087708
Works fine however it requires partitioning to be done from linux since we currently don't have a modified recovery.img with parted available.

Ubuntu Maverick

Hi! Did anyone tried booting Ubuntu 10.10 in your Nexus S this way??
http://forum.xda-developers.com/showthread.php?t=962023
I tried booting it but I can't, it says it will boot but it doesn't respond, is it compatible? Anyone got success with this? Thanks!!

NOTE: YOU NEED SPEEDMOD KERNEL FOR THE GALAXY S FOR THIS TO BOOT
i think thats the problem...

Do you think so? But this kernel is not used only to increment the speed of the phone so that it can handle this version of Ubuntu?? I think the Nexus S is quite fast to handle this! As I'm not a developer I don't know it... I'll keep investigating, thanks!!

i have tried this like 2 months ago its not so hard to do and works pretty good on Nexus S but you will need an on screen keyboard because the one i installed had some keyboard issue with VNC..also as far as i now CM7 rom doesnt support this you can use stock rom though..

you can use the guide (and the iso) @ nexusonehacks.
i currently use this script to launch pastebin.com / F1ULPVYw
and
Code:
if [ ! -f /.lockterm ];
then
export USER=root
cd /
rm -r -f tmp
mkdir tmp
cd /
vncserver -geometry 800x480
touch /.lockterm
fi
just to avoid a 2nd launch of vncserver.
You should have to change loop5 to loopN (N=7,8,9,...) if the script fails.

[GUIDE] How To Convert ODIN Tars to System.imgs for CWM (and vice versa)

This will probably get moved, but I do believe it is development related because it is important to everyone who flashes ROMs but can't use ODIN for whatever reason (ie Linux/Mac users).
Seeing all the ROM cookers get asked so much to make system.imgs or update.zips to cater to the Linux/Mac users, I decided it was time to tell people how to just convert an ODIN Tar.
I will tell people how to do it on Ubuntu seeing that is what I have (in a VM), but once I have the patience to install Mac OS in a VM, I shall make a guide for that.
Please note that if the factoryfs.rfs is in RFS format (ie it's a stock ROM or it's a ROM by someone who doesn't like EXT4 for whatever reason), you will not be able to do this. The format the factoryfs.rfs is in (EXT2, 4, JFS, whatever) needs to be supported by your Linux kernel. You can check that by doing cat /proc/filesystems
After a lot of investigating, I have learnt that RFS is a broken version of FAT. You could poke around with it and try mounting it as vfat but I don't guarantee success.
ODIN TAR -> System.img
Download your TAR and save it to your Desktop (I will use Kyorarom Ascendency Beta)
Open the TAR with Archive Manager (or whatever you use) and extract the factoryfs.rfs from it to your desktop. You don't need anything else
Open Terminal (under Applications > Accessories)
Go into superuser mode:
Code:
sudo -s
Make a mountpoint for the system:
Code:
mkdir /mnt/system
Mount the image
Code:
mount -o loop ~/Desktop/factoryfs.rfs /mnt/system
Change directory to /mnt and make the tarball for the system.img
Code:
cd /mnt
tar cvf system.img system
Unmount and clean up
Code:
umount /mnt/system
rm -rf /mnt/system
Copy the system.img to your phone
System.img -> ODIN TAR
Download a TAR from another ROM, and the system.img to your desktop.
Open the TAR with Archive Manager (or whatever you use) and extract the factoryfs.rfs from it to your desktop. You don't need anything else
Open Terminal (under Applications > Accessories)
Go into superuser mode:
Code:
sudo -s
Make a mountpoint for the system:
Code:
mkdir /mnt/system
Mount the image
Code:
mount -o loop ~/Desktop/factoryfs.rfs /mnt/system
Change directory to /mnt and make the tarball for the system.img
Code:
cd /mnt
rm -rf system/*
tar xvf ~/Desktop/system.img
Unmount and clean up
Code:
umount /mnt/system
rm -rf /mnt/system
Put the factory.rfs into a TAR and flash it with ODIN.
Done! Hopefully this should all work nicely for everyone.

Nice One... Should be helpful for ROM Developers to provide system.img for their ROM's...

Nice one. Thanks. Though I don't use .imgs still was quite Informative.
Sent from my GT-I5800 using xda premium

Nice tut, on windows they can use adb and dd/ mkyaffs2img
From my fingers to your eyez

cdesai said:
Nice tut, on windows they can use adb and dd/ mkyaffs2img
From my fingers to your eyez
Click to expand...
Click to collapse
Can u pls explain tht furthur.

vsoft11 said:
Can u pls explain tht furthur.
Click to expand...
Click to collapse
Pretty much do the same thing but from in ADB shell, and instead of the command:
Code:
sudo -s
with
Code:
su
and
Code:
tar cvf system.img system
gets changed to
Code:
tar cvf /sdcard/system.img system
Also I'm pretty sure on the phone, /dev/loop0 is called /dev/block/loop0.

I'll probably have to wait until you put up a mac tutorial..

harkan89 said:
I'll probably have to wait until you put up a mac tutorial..
Click to expand...
Click to collapse
As MacOS is basically Unix you should be able to do the same with/on/in a mac when you open a Terminal/Console (forgot how it's called exactly)....

Wouldnt it be easier if you run this commands?
Code:
mount -o loop factoryfs.rfs ~/Desktop/system
tar cvf system.img system
the mount command mounted it succesfully for me

mankokoma said:
As MacOS is basically Unix you should be able to do the same with/on/in a mac when you open a Terminal/Console (forgot how it's called exactly)....
Click to expand...
Click to collapse
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..

TearsDontFalls said:
Wouldnt it be easier if you run this commands?
Code:
mount -o loop factoryfs.rfs ~/Desktop/system
tar cvf system.img system
the mount command mounted it succesfully for me
Click to expand...
Click to collapse
Because I am foolish. I shall improve the guide later today.
harkan89 said:
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..
Click to expand...
Click to collapse
I got my Mac VM working so I will use that and make a Mac guide.

hillbeast said:
I got my Mac VM working so I will use that and make a Mac guide.
Click to expand...
Click to collapse
Yaay! Finally!

harkan89 said:
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..
Click to expand...
Click to collapse
You can use adb too (but these commands should work on a Mac too, as Mac | Linux -- UNIX (based on)
Or you can always use cwm!

is there also a way to convert system.img to tar files...

cdesai said:
You can use adb too (but these commands should work on a Mac too, as Mac | Linux -- UNIX (based on)
Or you can always use cwm!
Click to expand...
Click to collapse
I have superuser enabled on mac.. WHen I try the first command.. mkdir /mnt/system.. it says no such file or directory found.. and losetup is apparently not a command recognized by mac terminal..

mohsin2cool said:
is there also a way to convert system.img to tar files...
Click to expand...
Click to collapse
Yes, I shall make a guide for that after Christmas.
harkan89 said:
I have superuser enabled on mac.. WHen I try the first command.. mkdir /mnt/system.. it says no such file or directory found.. and losetup is apparently not a command recognized by mac terminal..
Click to expand...
Click to collapse
Macs don't use a /mnt directory. They use /Volumes, just like how Ubuntu is moving over to /media.
And I don't think the mach kernel supports losetup type stuff. I will make a Mac guide after Christmas.

HI
If u got the time, Can u pls make a tutorial video for this using adb. Would have bn very helpful.

devc0ol said:
If u got the time, Can u pls make a tutorial video for this using adb. Would have bn very helpful.
Click to expand...
Click to collapse
Sure. I will do it in the coming days.

nice guide, but will it also work if you convert it with CWM recovery?

JasonPurungrit said:
nice guide, but will it also work if you convert it with CWM recovery?
Click to expand...
Click to collapse
What do you mean?

Root update.zip

So I was wondering if anybody knew if the root update.zip works on the samsung infuse 4g. if u dont know what it is you can look for it on google.com. I was wondering if it actually worked on my phone?
Thanks, ReEvolution

Or is it only for gingerbread devices

Try and find out and report back
Sent from my SGH-I997 using xda premium

Probably
Reevolution said:
So I was wondering if anybody knew if the root update.zip works on the samsung infuse 4g. if u dont know what it is you can look for it on google.com. I was wondering if it actually worked on my phone?
Thanks, ReEvolution
Click to expand...
Click to collapse
Probably if it is the right one. In order to root Infuse 4G gingerbread (which you probably have), I believe the only or easiest way is to flash a rooted kernel temporarily in order to setup the right files.
This worked for me and it is FYI without warranty. I went the scenic route by:
1) extracting a Rooted Gingerbread Kernel from a ROM found on the Infuse 4G Super Everything Thread
2) flashed it, the Rooted Kernel zImage only with pit file (no reformat), using heimdal in download mode. Note, I am running linux plus "zImage" and "infuse.pit" are the actual names of the files extracted from the rooted kernel rom mentioned earlier with an archiver like 7-zip)
Code:
$ sudo heimdal flash --pit infuse.pit --kernel zImage
3) after normal reboot, I used adb to push busybox, su and Superuser.apk (i got them from a SuperOneClick package) to /data/local/tmp/ on the Infuse 4G
4) connected via adb shell command which starts with root privilages ('#' instead of '$') on the console.
5) remounted /system read+write:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
6) used busybox to copy itself, Superuser.apk and su to the right place via:
Code:
#cd /data/local/tmp/
# busybox cp busybox /system/bin/busybox
# busybox cp Superuser.apk /system/app/Superuser.apk
# busybox cp su /system/bin/su
7) changed permissions with:
Code:
# chmod 6755 /system/bin/busybox
# chmod 6755 /system/bin/su
8) rebooted to download mode
9) flashed the stock gingerbread kernel back in.
Finally, in flashing a rooted kernel, /system/etc/vold.fstab may have changed with the rooted kernel so the external sd does not get mounted correctly. To fix this, I reversed the process I found on another thread and changed the second to last line from:
Code:
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
...to:
Code:
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
The only difference being the last character is to be a '1' instead of '2'. I read it was a known bug.
I just did this a few hours ago on my Infuse 4G so I, for myself, am sure it works and hope this helps.

I have froyo though thats what im trying to root for to install gb than ics and than jb

mkthundrwd said:
Probably if it is the right one. In order to root Infuse 4G gingerbread (which you probably have), I believe the only or easiest way is to flash a rooted kernel temporarily in order to setup the right files.
This worked for me and it is FYI without warranty. I went the scenic route by:
1) extracting a Rooted Gingerbread Kernel from a ROM found on the Infuse 4G Super Everything Thread
2) flashed it, the Rooted Kernel zImage only with pit file (no reformat), using heimdal in download mode. Note, I am running linux plus "zImage" and "infuse.pit" are the actual names of the files extracted from the rooted kernel rom mentioned earlier with an archiver like 7-zip)
Code:
$ sudo heimdal flash --pit infuse.pit --kernel zImage
3) after normal reboot, I used adb to push busybox, su and Superuser.apk (i got them from a SuperOneClick package) to /data/local/tmp/ on the Infuse 4G
4) connected via adb shell command which starts with root privilages ('#' instead of '$') on the console.
5) remounted /system read+write:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
6) used busybox to copy itself, Superuser.apk and su to the right place via:
Code:
#cd /data/local/tmp/
# busybox cp busybox /system/bin/busybox
# busybox cp Superuser.apk /system/app/Superuser.apk
# busybox cp su /system/bin/su
7) changed permissions with:
Code:
# chmod 6755 /system/bin/busybox
# chmod 6755 /system/bin/su
8) rebooted to download mode
9) flashed the stock gingerbread kernel back in.
Finally, in flashing a rooted kernel, /system/etc/vold.fstab may have changed with the rooted kernel so the external sd does not get mounted correctly. To fix this, I reversed the process I found on another thread and changed the second to last line from:
Code:
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
...to:
Code:
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1
The only difference being the last character is to be a '1' instead of '2'. I read it was a known bug.
I just did this a few hours ago on my Infuse 4G so I, for myself, am sure it works and hope this helps.
Click to expand...
Click to collapse
Easiest way in my opinion is to flash the kernel to get cwm recovery
Boot into recovery
Flash any of the Roms here as they are all rooted (there are complete stock Roms that are rooted...uclb3)
Sent from my SGH-I997 using Tapatalk 2

But I dont have a comp

Reevolution said:
But I dont have a comp
Click to expand...
Click to collapse
dont flash anything if you dont have a comp...
seriously...

Alright ill kep looking any ideas

Reevolution said:
Alright ill kep looking any ideas
Click to expand...
Click to collapse
currently, without a pc, you can't root. you cant get gb or gb bootloader.
when on gb, you cant root.
if you mess up, you've got a soft brick.
no pc=be happy with froyo
here's a old thread:
http://forum.xda-developers.com/showthread.php?t=1815687
old funnies for bigjoe and pony.

mkthundrwd said:
Probably if it is the right one. In order to root Infuse 4G gingerbread (which you probably have), I believe the only or easiest way is to flash a rooted kernel temporarily in order to setup the right files.
This worked for me and it is FYI without warranty. I went the scenic route by:.
Click to expand...
Click to collapse
yeah..this is the hard way.
here the easy way: post #2
http://forum.xda-developers.com/showthread.php?t=1629079
one click heimdall then use the root pack ..easy peasy

qkster said:
here's a old thread:
http://forum.xda-developers.com/showthread.php?t=1815687
old funnies for bigjoe and pony.
Click to expand...
Click to collapse
If someone starts an XDA Infuse Hall of Fame (or museum) thread, that one surely belongs.
And maybe http://forum.xda-developers.com/showthread.php?t=1820792