Database Develop

Google Maps 3.2.0 and New Youtube App

OK, for those on any cupcake or donut build, I've included instruction to get the new Maps 3.2.0 and the new YouTube app from Eclair (Android 2.0).
1. Download the zip file. View attachment 2.0_Apps.zip
2. Extract and place Maps.apk and YouTube.apk on the root of your SDCard
I'm using CyanogenMod 4.2.2 with CM-Recovery 1.4
In CM 4.2.2 the apps are found in /system/app ***while the phone is on and operation, if it's off or in recovery the symlink won't be active so please make sure your phone is completely booted. Don't do this from Recovery Console***
If you're using a different rom... go through your phone and locate Maps.apk and YouTube.apk update the links below accordingly
Windows users (with ADB working)
1. Open a CMD (command promt window)
Type:
- adb remount
- adb shell
- rm /system/app/Maps.apk
- rm /system/app/YouTube.apk
- cd /sdcard
- cp Maps.apk /system/app
- cp YouTube.apk /system/app
Phone Users:
1. Open a Terminal Window:
2. Type the following:
- su
- mount /system -o remount,rw
- rm /system/app/Maps.apk
- rm /system/app/YouTube.apk
- cd /sdcard
- cp Maps.apk /system/app
- cp YouTube.apk /system/app
You don't need to reboot... Apps will show up immediately in your menu. (You'll need to put them back on your Home Screen if you had them there though)
You're done... enjoy!

Is this the new maps with turn by turn?

You might want to change from
rm /system/app/Maps.apk
rm /system/app/Youtube.apk
to
mv /system/app/Maps.apk /sdcard/Maps.apk.old
mv /system/app/Youtube.apk /sdcard/Youtube.apk.old
the youtube app isn't all that stable and it never hurts to keep a backup, also I believe you need to remove any .obex files for maps and youtube to avoid problems although I didn't see any under CM 4.2.2
edit: I also believe these don't work on 1.5 might be worth pointing out in the OP

persiansown said:
Is this the new maps with turn by turn?
Click to expand...
Click to collapse
No just the one from the sholes dump, its faster to load and has layers for wikipedia, latitude and things like that
edit: more info here http://forum.xda-developers.com/showthread.php?t=574329

will this in a Hero rom? thanks!

Moved to apps location

might have to give this a shot

Totally doesn't work for me:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\DamianV>adb remount
remount succeeded
C:\Users\>adb shell
# rm /system/app/maps.apk
rm /system/app/maps.apk
rm failed for /system/app/maps.apk, No such file or directory
# rm /system/app_s/Maps.apk
rm /system/app_s/Maps.apk
rm failed for /system/app_s/Maps.apk, No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
#

I tried a few different variations.

remember to remount first and make sure you have the correct directories.
some roms uses system/app, some roms uses data/app_s

NguyenHuu said:
remember to remount first
Click to expand...
Click to collapse
Yeah I did do that...odd

do u have the origional file.. i made a booboo and didnt back up. forgot to backup origional file.

can u use a file explorer and browse and double check which directories the files are actually in? i see you tried both system/app and app_s. and i see you have lowercase for maps.apk. it could be uppercase, case sensitive.
for example your first cmd #rm /system/app/maps.apk, it should be Maps.apk
also for the copying part you need to do adb push, dont do it from shell. if you do from shell it would have to be from sdcard to that directory. i noticed in your log you didnt change directory to sdcard.

IronCross1788 said:
do u have the origional file.. i made a booboo and didnt back up. forgot to backup origional file.
Click to expand...
Click to collapse
Hahah yeah I made the same mistake--was getting 'Cross-Linked' errors so I said ehh fudge it and just wiped the original out. After that I was able to get the new Maps.apk loaded up though and DAMN, definitely an improvement

I thought these apps wouldnt work on anything below android 1.6?

If you're having trouble finding the app and want to check the directory you're in you can use ls (that's LS) to list the contents of the current directory. ROMs store things in different places so if you haven't already try....
adb remount
adb shell
cd /data/
ls
At that point see if you have app, app_s, app-private etc then if you do you can ....
cd app or app_s etc
Then do..
ls Maps.apk (this is case-sensitive)
If you get nothing do
cd ..
That'll take you back one directory, so if you're in /data/app it'll put you in /data
With those few commands you can probably find it. I don't use Linux enough to know what if there's a 'find' command available in console. The other option that might be quicker would be to find the .zip of the ROM you're using, create a new folder for it, move the .zip file to the new folder and then extract it there. That way you can browse through directories more easily or use Windows / OS X / Linux search functions to find Maps.apk
Phew...

Dyonas said:
If you're having trouble finding the app and want to check the directory you're in you can use ls (that's LS) to list the contents of the current directory. ROMs store things in different places so if you haven't already try....
adb remount
adb shell
cd /data/
ls
At that point see if you have app, app_s, app-private etc then if you do you can ....
cd app or app_s etc
Then do..
ls Maps.apk (this is case-sensitive)
If you get nothing do
cd ..
That'll take you back one directory, so if you're in /data/app it'll put you in /data
With those few commands you can probably find it. I don't use Linux enough to know what if there's a 'find' command available in console. The other option that might be quicker would be to find the .zip of the ROM you're using, create a new folder for it, move the .zip file to the new folder and then extract it there. That way you can browse through directories more easily or use Windows / OS X / Linux search functions to find Maps.apk
Phew...
Click to expand...
Click to collapse
Sound advise, one last thing for anyone who didn't know the remount command is
mount -o rw,remount /system (assuming your apps are in /system/app)
so full instructions for a CyanogenMod install from the sd card would be as follows
- su
- mount -o rw,remount /system
- cd /sdcard
- mv /system/app/Maps.apk /sdcard/Maps.apk.old
- mv /system/app/YouTube.apk /sdcard/Youtube.apk.old
- cp Maps.apk /system/app
- cp YouTube.apk /system/app
To revert back to old apps if you decide you don't like the new ones
- su
- mount -o rw,remount /system
- cd /sdcard
- cp Maps.apk.old /system/app/Maps.apk
- cp Youtube.apk.old /system/app/Youtube.apk

Breakthecycle2 said:
Totally doesn't work for me:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\DamianV>adb remount
remount succeeded
C:\Users\>adb shell
# rm /system/app/maps.apk
rm /system/app/maps.apk
rm failed for /system/app/maps.apk, No such file or directory
# rm /system/app_s/Maps.apk
rm /system/app_s/Maps.apk
rm failed for /system/app_s/Maps.apk, No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
# cp Maps.apk /system/app
cp Maps.apk /system/app
cp: cannot stat 'Maps.apk': No such file or directory
#
Click to expand...
Click to collapse
If you have a2sd, try mapping to /system/sd/app or /system/sd/app_s
Make sure you remount before doing so.

hey guys!
for those who are having problems...
I just put the apk files in my sdcard and then upgraded it using ASTRO.. it worked fine!

yeah well every1 is doing this mad confusing lmfao i just installed with appsinstaller and it worked like a charm lol why is everything always confusing

CM6 Apps2ext

so ive been trying all day to get my /sd-ext to mount . ive added mount commands to the init files in /system/etc/init.d but none of them seem to run on boot. what should i do?

are you talking about app2sd or am i misunderstanding you?

yes trying to implement commands for a dirty ext apps2sd on cm6 nexus

the builders have said it will be in a future release when they are happy with performance

superg81 said:
the builders have said it will be in a future release when they are happy with performance
Click to expand...
Click to collapse
wow that was not helpful in any way

well **** me,i was trying to be nice.piss off
ahronzombi said:
wow that was not helpful in any way
Click to expand...
Click to collapse

just incase someone else runs into douches who dont help
I spent all night trying to do this so im going to document this.
-None of this stuff is my work , thanks to Pershoot, teamdouch and cyanogen for the files to push
-This is a very ugly hack. Maybe someone else can make this simpler by making a flashable rom with this already applied. I'm not knowledgeable enough at this point to make this any easier or i would.
-I dont dev , i dont make roms and i dont claim to be good at this. !!!!PLEASE USE AT YOUR OWN RISK!!! BACKUP!!!!
-Feel free to take this and fix my flaws, dont need to give me credit.
okay this is how i got apps2ext in cm6 nexus
Im doing this right after flashing cm , haven't installed apps or registered my account on the phone. i have a existing ext partition.
1.Symlink
(copy any of your apps to the new location if you already have a running system without this hack)
Code:
adb remount
Code:
adb shell mkdir /sd-ext
Code:
adb shell mkdir /sd-ext/app
Code:
adb shell rm /data/app
Code:
adb shell ln -s /sd-ext/app /data/app
2.init files
Okay i added this to a few init files. but you need to add this line to an init file in
/system/etc/init.d/
Code:
busybox mount -t ext2 /dev/block/mmcblk0p2 /sd-ext/
any may work for example this is /system/etc/init.d/00banner
Code:
#!/system/bin/sh
#
# Print startup info
#
busybox mount -t ext2 /dev/block/mmcblk0p2 /sd-ext/
L="log -p i -t cm"
$L "Welcome to Android `getprop ro.build.version.release` / `getprop ro.modversion`";
$L " _ ";
$L " __ __ _ ___ _ _ __ ___ __ _ _ _ _ __ __))";
$L "((_ \\(/'((_( ((\\( ((_)((_( (('((\\( ((\`1( ((_)((_( ";
$L " )) _))";
$L " ";
3.flash boot.img of kang-o-rama froyo. its in the (final) update zip at http://forum.xda-developers.com/showpost.php?p=6973422&postcount=2139
extract and copy the boot.img file to your sdcard
Code:
adb shell flash_image boot /sdcard/boot.img
Code:
adb shell reboot recovery
4. Now you have apps2ext, but wifi wont work
So........
flash pershoots nexus froyo kernel from http://droidbasement.com/db-blog/ using your recovery
THIS IS UGLY I KNOW
If your smarter than me please make this easier for all of us, this took me hours to figure out on my own + twitter
Thanks ahead of time to whom ever helps with this

What was the need for the boot.img step? I believe after creating the symlink you don't need anything else

right on bro, thanks a bunch for ur research, i was looking for something like this. U da man

i would also like to know why is the boot.img necessary

xxmonsterx said:
i would also like to know why is the boot.img necessary
Click to expand...
Click to collapse
Because Kang-o-rama has Apps2sd in the ramdisk (not the zImage) inside of boot.img.
So, flashing Kang-o-rama's boot.img will give you K-O-R's kernel with integrated Apps2sd. But ofcourse it breaks wifi, because you have not yet replaced the /system/lib/modules/bcm4329.ko file.
Now, Pershoot's kernel flash (as well as nearly any kernel flash) actually pulls the ramdisk out of your existing boot.img, integrates it with his zImage, and then repacks a new boot.img - and, critically, it also copies in the matching bcm4329.ko driver.
So, you don't have to actually flash Pershoot's kernel - you should just need to pull the /system/lib/modules/bcm4329.ko file out of Kang-o-rama when you take out the boot.img. Then flash the boot.img AND replace the .ko at the same time, and you ought to be golden.
So, assuming that you put the .ko file in the root of your SD card :
Code:
adb shell flash_image boot /sdcard/boot.img
adb remount
adb shell
su (if you are not already root in the ADB session for some reason...)
cp /system/lib/modules/bcm4329.ko /system/lib/modules/bcm4329.ko.bak
cp -f /sdcard/bcm4329.ko /system/lib/modules/bcm4329.ko
chmod 644 /system/lib/modules/bcm4329.ko
reboot
And you should be good to go - using Kang-o's kernel if that is acceptable for you.

[Q] dsifix.ko applied to stock milestome froyo rom

hello, basically my question is that, how to apply the fix to a stock froyo rom...i think that it must be done trougth open recovery but i wanted to be sure. thankss

it can be done through the console of open recovery, or through a terminal editor if you have root.
edit: simpler way for stock roms
copy the dsifix.ko to your sdcard
mount the /system partition as read/write
run these commands:
Code:
cp /sdcard/dsifix.ko /system/lib/modules/dsifix.ko
chmod 644 /system/lib/modules/dsifix.ko
echo "insmod /system/lib/modules/dsifix.ko" >> /system/etc/rootfs/init.mapphone_umts.rc

correct me if im wrong, but the second directory, system/rootfs/, isnt that only for cyano based roms?? because in stock roms it doesnt exist. thanks for the reply.

ah you're right, sorry
hmm you could try using the 'install mods autostarts - not needed in many roms' script thats in androidiani openrecovery, and then running these commands:
Code:
cp /sdcard/dsifix.ko /system/lib/modules/dsifix.ko
chmod 644 /system/lib/modules/dsifix.ko
cd /system/etc/init.d
touch 1dsifix
echo "insmod /system/lib/modules/dsifix.ko" > 1dsifix
chmod 750 1dsifix
I'm not entirely sure this will work, but try it and see.

Hi,
to sum it up:
To use additional kernel modules (e.g. dsifix.ko) you need to tweak the startup scripts (e.g. init.mapphone_umts.rc)
To use tweaked startup scritps like modified init.mapphone_umts.rc you'll need a ROM that makes use of 2nd init process.
Stock ROMs do not use 2nd init, because it's a hacked feature and stock ROMs are usually not hacked
On stock ROM there's also no /system/etc/init.d nor /system/etc/rootfs directory, because they are no used there.
Hope this helps
P.S.: Don't know about this androidiani stuff ...
EDIT: Search button is so nice... http://forum.xda-developers.com/showthread.php?t=1003338
Regards,
scholbert

great i will try this evening, thanks for the repliess.
Sent from my Milestone using XDA App

the androidiani mod enables 2nd-init, which means it checks for scripts in the init.d folder
that link is only for the display update fix, which causes tearing, not for the kernel module fix thats popped up recently. However, we can modify coldsphinx's instructions to suit our purposes.
as usual, you'll need to move the dsifix to /system/lib/modules
Code:
cp /sdcard/dsifix.ko /system/lib/modules/dsifix.ko
chmod 644 /system/lib/modules/dsifix.ko
then rename the mot_boot_mode file to mot_boot_mode.bin
Code:
mv /system/bin/mot_boot_mode /system/bin/mot_boot_mode.bin
then create the file /system/bin/mot_boot_mode
and add this to the file:
Code:
#!/system/bin/sh
export PATH=/system/bin:$PATH
mot_boot_mode.bin
insmod /system/lib/modules/dsifix.ko
and then finally set the permissions
Code:
chmod 755 /system/bin/mot_boot_mode
it will work.

GReat! thanks!

[GUIDE][i9100g/i9100] HOW TO DEODEXED ICS STOCK ROMS

The general API level for odexed apps and framework in ICS and Jellybean is higher (15) than the Gingerbread so the apps in ICS and Jelly bean need to be deodexed differently. Here's is a much general and 100% successful way of deodexing those apps and pushing them into system. I know some of you might suggest dsixda kitchen but thats just limited to Linux or cygwin users. So i am gonna talk fully about how to deodex them samsung apps.
First of all what is deodexing:
Here's a good guide:
http://www.wugfresh.com/guides/deodex/ (do not use the guide to deodex you might brick your device)
Now let us actually proceed with deodexing system files:
1. Gain the actual .odex files be it by copying from actual system files or by extracting the firmware fresh
2. Download the following tool (auto deodex tool 1.0.3): (thanks to xavierjohn22)
http://forum.xda-developers.com/showpost.php?p=13254199&postcount=3
3. Extract it inside a folder.
4. Place the respective system/app files to be deodexed in _app
and system/framework files to be deodexed in _framework
5. Run Autodeotoolmain.bat
6. First deodex jar files (ie _framework files) ress 5
7. It will take some time.
8. Your deodexed files will be in deodexed_jar folder
9. Deodexing apps requires some extra steps
10. Download the attached file java.awt.jar
11. Place the java.awt.jar file in deodexed_jar folder
12. Now to deodex .apk files press 4.
13. Use the following as your boot class path:
Code:
am.jar:android.policy.jar:android.test.runner.jar:apache-xml.jar:bmgr.jar:bouncycastle.jar:bu.jar:com.android.future.usb.accessory.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.google.android.media.effects.jar:com.google.widevine.software.drm.jar:com.samsung.device.jar:core.jar:core-junit.jar:ext.jar:filterfw.jar:framework.jar:framework2.jar:GlobalConfig.jar:ime.jar:input.jar:javax.obex.jar:libvtmanagerjar.jar:minimode.jar:monkey.jar:pm.jar:sec_feature.jar:seccamera.jar:secframework.jar:sechardware.jar:secmediarecorder.jar:services.jar:svc.jar:twframework.jar:java.awt.jar
14. Press enter and drink some coffee or do something else it takes very long time.
15. After completion those apps will be stored in deodexed_apk
16. Now some jars and apks remain in _framework those do not need to be deodexed. Copy those files in deodexed_jar
17. Now copy deodex_jar folder and deodexed_apk folder to your phone (make sure unknown sources and usb debugging are on)
18. Unplug your phone once and let media scanning run
19. Plug you phone again and in windows command prompt fire in adb and type in following code:
adb shell
su
stop
mount -o remount,rw /dev/block/mmcblk0p9
/system rm
/system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/deodexed_APK/* /system/app/
busybox cp /sdcard/deodexed_JAR/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/mmcblk0p9 /system
sync
reboot recovery
Click to expand...
Click to collapse
20. In recovery wipe cache, dalvik and do a factory reset. Reboot (initially may take some time be patient)
21. Congratulations you are deodexed

thats nice

nice....

Thankyou ( +1 :good: )im looking this one!

Thnx ^^

thanks...

I found an options to optimize app, is it helpfull?

samyam2002000 said:
The general API level for odexed apps and framework in ICS and Jellybean is higher (15) than the Gingerbread so the apps in ICS and Jelly bean need to be deodexed differently. Here's is a much general and 100% successful way of deodexing those apps and pushing them into system. I know some of you might suggest dsixda kitchen but thats just limited to Linux or cygwin users. So i am gonna talk fully about how to deodex them samsung apps.
First of all what is deodexing:
Here's a good guide:
http://www.wugfresh.com/guides/deodex/ (do not use the guide to deodex you might brick your device)
Now let us actually proceed with deodexing system files:
1. Gain the actual .odex files be it by copying from actual system files or by extracting the firmware fresh
2. Download the following tool (auto deodex tool 1.0.3): (thanks to xavierjohn22)
http://forum.xda-developers.com/showpost.php?p=13254199&postcount=3
3. Extract it inside a folder.
4. Place the respective system/app files to be deodexed in _app
and system/framework files to be deodexed in _framework
5. Run Autodeotoolmain.bat
6. First deodex jar files (ie _framework files) ress 5
7. It will take some time.
8. Your deodexed files will be in deodexed_jar folder
9. Deodexing apps requires some extra steps
10. Download the attached file java.awt.jar
11. Place the java.awt.jar file in deodexed_jar folder
12. Now to deodex .apk files press 4.
13. Use the following as your boot class path:
Code:
am.jar:android.policy.jar:android.test.runner.jar:apache-xml.jar:bmgr.jar:bouncycastle.jar:bu.jar:com.android.future.usb.accessory.jar:com.android.location.provider.jar:com.google.android.maps.jar:com.google.android.media.effects.jar:com.google.widevine.software.drm.jar:com.samsung.device.jar:core.jar:core-junit.jar:ext.jar:filterfw.jar:framework.jar:framework2.jar:GlobalConfig.jar:ime.jar:input.jar:javax.obex.jar:libvtmanagerjar.jar:minimode.jar:monkey.jar:pm.jar:sec_feature.jar:seccamera.jar:secframework.jar:sechardware.jar:secmediarecorder.jar:services.jar:svc.jar:twframework.jar:java.awt.jar
14. Press enter and drink some coffee or do something else it takes very long time.
15. After completion those apps will be stored in deodexed_apk
16. Now some jars and apks remain in _framework those do not need to be deodexed. Copy those files in deodexed_jar
17. Now copy deodex_jar folder and deodexed_apk folder to your phone (make sure unknown sources and usb debugging are on)
18. Unplug your phone once and let media scanning run
19. Plug you phone again and in windows command prompt fire in adb and type in following code:
20. In recovery wipe cache, dalvik and do a factory reset. Reboot (initially may take some time be patient)
21. Congratulations you are deodexed
Click to expand...
Click to collapse
thanks mate now i used it XD

ICS_XD said:
thanks mate now i used it XD
Click to expand...
Click to collapse
so that means the GAME HAS BEGUN

incarnation95 said:
so that means the GAME HAS BEGUN
Click to expand...
Click to collapse
Yeah XD
Sent from my GT-I9100G using xda premium

delete java.awt.jar from deodexed_JAR after DEODEXED?

Can someone help me? i dont know why i get permission denied
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>adb shell
[email protected]:/ # su
su
[email protected]:/ # stop
stop
[email protected]:/ # mount -o remount,rw /dev/block/mmcblk0p9
mount -o remount,rw /dev/block/mmcblk0p9
[email protected]:/ # /system rm
/system rm
sh: /system: cannot execute - Is a directory
126|[email protected]:/ # /system/app/*.odex
/system/app/*.odex
sh: /system/app/AccuWeatherDaemonService.odex: cannot execute - Permission denie
d
126|[email protected]:/ #
Click to expand...
Click to collapse
I solved it already.

need help
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\user>adb shell
[email protected]:/ # su
su
[email protected]:/ # stop
stop
[email protected]:/ # mount -o remount,rw /dev/block/mmcblk0p9
mount -o remount,rw /dev/block/mmcblk0p9
[email protected]:/ # /system rm
/system rm
sh: /system: cannot execute - Is a directory
126|[email protected]:/ # /system/app/*.odex
/system/app/*.odex
sh: /system/app/AccuWeatherDaemonService.odex: cannot execute - Permission denie
d
126|[email protected]:/ #
i'm stock in this one..can someone tell me how to resolve it?

Refer to the guide by superatmos...this guide has typos...but can't remember exactly...

Use dsixda kitchen
Sent from my GT-I9100G using Tapatalk 2

this metod can be used to deodex leaked JB XXLSJ rom !?

Can I also deodex leaked Jellybean XXLSJ stock ROMS?

Not sure but why take the trouble? Legendk95 already released a deodexed version of that ROM...

I keep getting
I keep getting this error message when running the .bat: Java was not found, you will not be able to sign apks or use apktool
Press any key to continue . . .
I have the newest JAVA and even Java dev tools on my laptop. What should I do?

Java is not set in your home path...

How to get root access from kernel, with no busybox and not building any sources

Hi folks,
On my way trying to get 10 usefull posts to access the developers forums, I have writen this easy tutorial. xD
THIS IS FOR S5830i DEVICES. init.rc used belongs to S5830i ramdisk
Whats all about? Well, in this tutorial I will so you how to get root access directly from Kernel only modifing init.rc and adding su to tmp folder.
THIS IS NOT UNSECURING THE BOOT.IMG TUTORIAL
Question: Axyllum why are you posting this, if there are so many tutorials on how to do this for other devices?
Answer: Simple, as you all ready imagine, partition for boot.img is just 5MB Oh my god.
Then, if my boot image is all ready 4.28MB, how can I use a busybox thats 836KB (I compiled a busybox with mount, cp, mkdir, chmod and chown that is the minimum to get root: image = 836MB). Cant use this beacuse I exceed total mounting point size.
Kernel + ramdisk = 4.28MB if you pull stock boot.img from your device.
Minimum busybox explained before = 836KB
SU image 25KB to 86KB depending on the su image you use.
This makes a total of: 5.2MB. Try to flash it. It fails? Yes, you exceeded the mounting point size.
And the solution? Follow my tutorial.
Abilites you will need to follow the turotrial:
Know how to: Un pack & repack boot.img
Know how to: Decompress Ramdisk and compress it back. (to get the famous newramdisk in many many tutorials) newramdisk is just a name, you can compress back to any name, for example axyllumramdisk or yourramdisk or how ever you want to call it.
Asuming you know how to do the explained above and after my wierd chat, lets gooooo:
1. Open init.rc in your favourite text editor.
2. Go to this line in init.rc:
mount rfs /dev/stl9 /system check=no
You should see this:
mount rfs /dev/stl9 /system check=no
mount rfs /dev/stl9 /system ro remount
Got it? lets go to step 3.
3. Overwrite both lines with this:
mount rfs /dev/stl9 /system check=no
mkdir /system/xbin
copy /tmp/su /system/xbin/su
chown root root /system/xbin/su
chmod 06755 /system/xbin/su
mount rfs /dev/stl9 /system ro remount
Make sure you are not overwriting other lines or your ramdisk could not work.
4. Paste SU image file to tmp folder. Make sure SU image has execute permissions.
5. Compress back ramdisk (the famous newramdisk).
6. Repack boot.img
7. Flash it.
8. Restart device.
9. Download superuser.apk and busybox form market and.... there you go you made your kernel with root access and no need of a busybox.
Ok, this was simple, but i imagine more than one will like to know what we did.
I'll explain:
As we cant add a busybox, how the hell am i going to mount system rw, mkdir xbin, cp su from tmp to xbin, chmod / chown permissions?
I started reading the init.rc file (i was bored and my wife wanted to go shopping --> no way i have an init.rc file to mess up with), and I saw many mkdir, copy, chmod etc... commands. (Opened a beer)
So i thought, great, there is all ready a busybox with the least i need to make this. Then why dont i use this preinstalled commands?
And i did this:
mount rfs /dev/stl9 /system check=no --> first I checked this, this instruction is where init.rc mounts system. At this point system is mounted RW.
mkdir /system/xbin --> Then as system is rw, I will create xbin folder. how? with mkdir comand.
copy /tmp/su /system/xbin/su --> Great I did not find a cp command, but found a "copy" command someware in init.rc. Search for it, you will see its used. Then why dont I use it to copy SU in tmp folder to the just created xbin folder? It worked.
chown root root /system/xbin/su --> Owner of su in xbin is: yes, root.
chmod 06755 /system/xbin/su --> Set the right permission to su. You need to chmod with 06755. --> 09364, 66666, 83823 will not work looooolll just a joke i imagine you all ready know what setting permissions is all about.
mount rfs /dev/stl9 /system ro remount --> Remount system with ro (this is the read only remount command).
I dont know if there are any other tutorials doing this, this way, i just did it my self. I Found tutorials on doing the same, but busybox, and .sh script and su were needed. To much for our small boot.img partition.
Enjoy.
Tip, dont mess your init.rc if you do not understand it.