I built a new zImage off the Eclair I5800XXJK1 rom. I assumed it was the best, but if I'm mistaken please tell me =) Though, the zImage should work on other Eclair roms too. I flashed it on my Froyo JPA/JPB hybrid.. Phone boots, but it is very broken.
I included:
- Ext2
- Ext3
- Ext4
- JFS
- CIFS (no module needed)
- Tun (no module needed)
*** I have only partially tested this (on Froyo for fun). Do so at your own risk. ***
I used the factoryfs.rfs, cache.rfs and initramfs right from JK1. No changes.
I'm not including boot.bin, Sbl.bin, or modem.bin to eliminate the chances of bricking your phone. I still cannot be held liable for anything happening to your phone.
If you don't know what to do with this file, then you probably shouldn't be modifying your phone.
(UPDATED) Download from here: http://www.multiupload.com/9QBAZ34454 pass: precurse
Kernel only is posted here: http://www.multiupload.com/E5TM4XWAKF pass: precurse
- Use this if you already have JK1 on your phone, or already have the main files for JK1. Flash a stock JK1 first, and this after.
If people find this works for them and want an ext2 or 4 setup for /data and/or /system, then I may be able to set that up for them.
Ext4 for data would be great man i have to test that kernel but it makes no sense if there is no use of those filesystems. I know it should now be possible to use the loop lagfix, but why doing this if one could get the real thing... there will not be that much quadrant boost using ext4 than using loop, but the smoothness of the system will vastly improve i think
The zImage works... It boots up my hybrid phone. But it's not a good idea to boot Eclair kernel/initramfs with Froyo userland =) All the services started dying on me, but it still did boot nontheless (good sign).
If people actually start using it, then I can probably remove a lot of crap in there (ext3 and jfs mainly). If there's no interest for this rom, then I won't continue it.
It sucks that we need to decide between a nice filesystem with 2.1, versus a newer (albeit beta) 2.2 OS ... I still haven't decided.
Though, I'm picking up a Galaxy S i9000 tomorrow. Trading an iPhone 3G and some cash for one =)
oh!we can't find other power user like you
if the office 2.2 froyo is out ,can you make a zimage.tar with ext2-4 initramfs
and make a update.zip to change all partitions to ext2-4
like z4mod.
hybrid system is useless yet.
http://forum.xda-developers.com/showthread.php?t=797672
precurse said:
The zImage works... It boots up my hybrid phone. But it's not a good idea to boot Eclair kernel/initramfs with Froyo userland =) All the services started dying on me, but it still did boot nontheless (good sign).
If people actually start using it, then I can probably remove a lot of crap in there (ext3 and jfs mainly). If there's no interest for this rom, then I won't continue it.
It sucks that we need to decide between a nice filesystem with 2.1, versus a newer (albeit beta) 2.2 OS ... I still haven't decided.
Though, I'm picking up a Galaxy S i9000 tomorrow. Trading an iPhone 3G and some cash for one =)
Click to expand...
Click to collapse
I will flash it to my gf's g3 asap, to test how it behaves, but without having a ext4 partition it makes not much sense...
I agree. But once we know this setup works, then it's really easy to change the initramfs to something that will load up ext4 partitions for /data and /cache pretty easily.
Ok, problem is my gf left her g3 at a friends house on new year, and will only pick it up later today, so in the evening i will be able to test this...
If only I hadn't recently bought a Galaxy S, I would surely try this on my Galaxy 3..
addicted2088 said:
If only I hadn't recently bought a Galaxy S, I would surely try this on my Galaxy 3..
Click to expand...
Click to collapse
I just got a Galaxy S today - too good of a deal to pass up.... And that screen, wow....
The community for that phone seems a lot more established unfortunately. I was having some high hopes for the G3, but I don't think the development will be nearly as close to that of the SGS..
I might keep the G3 for a while to tinker with it though..
precurse said:
I just got a Galaxy S today - too good of a deal to pass up.... And that screen, wow....
The community for that phone seems a lot more established unfortunately. I was having some high hopes for the G3, but I don't think the development will be nearly as close to that of the SGS..
I might keep the G3 for a while to tinker with it though..
Click to expand...
Click to collapse
Yeah, looking at my G3 after the SGS is horrible.. I'll be giving the G3 to my Dad.
Yeah, the SGS community is very well established. I didn't use the stock ROM on the SGS except when it was getting charged the first time. Soon as it got charged, I put a custom ROM over it.. (Darky's Gingerbread Edition ROM).
Hopefully, the G3 will see development like the Spica i5700, but right now the future's not looking so bright..
precurse said:
I just got a Galaxy S today - too good of a deal to pass up.... And that screen, wow....
The community for that phone seems a lot more established unfortunately. I was having some high hopes for the G3, but I don't think the development will be nearly as close to that of the SGS..
I might keep the G3 for a while to tinker with it though..
Click to expand...
Click to collapse
Hm, to bad, the g3 lost one of the most promising guys with you...
FadeFx said:
Hm, to bad, the g3 lost one of the most promising guys with you...
Click to expand...
Click to collapse
Indeed, I totally agree with you ...
Well, there is one question: How did you build that file ?
ok, tested the kernel on jk1 firmware (flashed only the zimage) and works as intended, got no idea how to test ext4 support...
edit: seems like cifs is not working like intended, do i need to insmod?
FadeFx said:
ok, tested the kernel on jk1 firmware (flashed only the zimage) and works as intended, got no idea how to test ext4 support...
edit: seems like cifs is not working like intended, do i need to insmod?
Click to expand...
Click to collapse
You shouldn't need to insmod. I compiled it statically into the kernel (as with tun):
CONFIG_CIFS=y
CONFIG_TUN=y
I might have to research into that a little further.
Can you do an uname -apm and tell me the output?
Thanks
FadeFx said:
Hm, to bad, the g3 lost one of the most promising guys with you...
Click to expand...
Click to collapse
Sorry to hear that. I sure hope I left enough of a paper tail to let others research and take off with this. I'm too much of a power user to be held back - I have a feeling Froyo will be the only update (and last) for the G3 unfortunately, while the SGS is closely tied with the Nexus S so the updates should continue (Gingerbread is already out for it).
I'm not going anywhere at this moment in time. My next school semester starts up again right away anyways, so I wouldn't have had the same amount of time either way to contribute as much as I have been.
If there's anything unclear with the work I've posted - feel free to ask, and I'll do my best to help spread whatever knowledge I have of this to you guys. I've sent Gsam information about how to build the eclair kernels, so if anyone else feels that they want to as well let me know.
uname -apm
uname: not found
busybox uname -apm
uname: applet not found
Something wrong here
FadeFx said:
uname -apm
uname: not found
busybox uname -apm
uname: applet not found
Something wrong here
Click to expand...
Click to collapse
oh yeh.. It's the stock factoryfs, so no busybox is installed.
What about under Settings > About > Kernel Version ?
Now i got it, Linux localhost 2.6.29 #2 Fri Nov 5 16:05:33 KST 2010 armv61 GNU/Linux
The busybox library was outdated, 1.14.1 or so... think this was installed by titanium backup, could not install it using sterricssons installer, so just copied it over...
FadeFx said:
Now i got it, Linux localhost 2.6.29 #2 Fri Nov 5 16:05:33 KST 2010 armv61 GNU/Linux
The busybox library was outdated, 1.14.1 or so... think this was installed by titanium backup, could not install it using sterricssons installer, so just copied it over...
Click to expand...
Click to collapse
Strange... It should show a date of a few days ago (the day I built it). I'll have to double check that it's the right zImage in that tar file.
... Update...
Yeah I have no idea what happened, but it's the same kernel as stock JK1. Sorry guys!
Kernel only is posted here: http://www.multiupload.com/E5TM4XWAKF pass: precurse
Just flash it as a regular "full" firmware in ODIN.. It only contains the zImage.
I'll upload a full replacement firmware.
Here (flashed it on my froyo setup to see if it booted):
Code:
# uname -apm
uname -apm
Linux localhost 2.6.29 #2 Sat Jan 1 03:53:22 MSK 2011 armv6l GNU/Linux
Ah, will test in the evening...
Related
If my title really needs a slogan to get your attention, then I just didn't make a big enough impression last time
Donations accepted / appreciated. All proceeds will go toward the cost of the myTouch and future accessories for development.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8141983
How I rooted a brand new "perfected SPL" MT3G and installed Hero in 15 min:
http://forum.xda-developers.com/showpost.php?p=4471578&postcount=154
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroSx-6.21s.zip
MD5: a04acee7df4e859bd2012954e1ec5447
Motorolla Blur: http://twistedumbrella.slackdev.com/MotoBlur-1.2.zip
This is an untested update, works in theory...
Sapphire Fixes: http://twistedumbrella.slackdev.com/Deport-1.1.zip
Removed Apps: http://twistedumbrella.slackdev.com/Extended.zip
Extended Apps: http://twistedumbrella.slackdev.com/Incremental.zip
Back your apps up as an update in case you do a wipe using this:
Download Incremental.zip above. Back all the apps up you want.
Open the archive and replace the apps in the data/app directory.
Sign the archive like a regular update and place in root of SD card.
Flash the update you want. When finished, flash Incremental.zip
Reboot the phone and both the update and apps will be installed.
User.conf file can be found as system/bin/hero.conf on any device.
No command needed for device identification. Faster boot (hopefully).
A reboot is no longer needed to use either device. This is all integrated.
Recommended not to overclock below 256, due to the black screen issue.
Compcache is enabled by default, current values were EXTENSIVELY tested.
Please do not contact me asking what values work or giving me others.
I spent 2 weeks changing values, testing, changing, testing. Both devices.
Abreviated Changelog, Full Changelog linked below:
Optimized the entire system app folder using the automated method.
Changed some animations. A lot of new stuff in use from Cyanogen.
This is a very unthemed build. The lock screen and such are generic.
The boot animation is customized and will not port to other builds.
http://forum.xda-developers.com/showpost.php?p=4758619&postcount=960
So much to do so little time, I do feel like the "white rabbit"
Now includes dynamic swap. Rewrote the method of apps to sd for myTouch.
Build will move system apps, user apps, and dalvik to sd on a g1 device.
Build will install completely internal if using the T-Mobile myTouch.
This is a completely new method of doing a merge build so bear with me.
Based on the System Image from Haykuro
Using the Kernel and modules from JacSki
Try rm system/sd/app_s if you feel new apps are not installing.
http://twistedumbrella.googlepages.com/index.htm
All the necessary files can be found there, including my GScripts.
This is also where all the download links to NEW versions are posted
Housekeeping:
Back everything up. This means run some sort of data backup if you want to keep your settings
You may also want to run a nandroid backup in recovery (if all else fails, you can restore it)
Warnings:
You MUST have the newest SPL
You MUST have a Class 6 SD Card
You MUST know how to read
You MUST have 3 partitions
You MUST have at least 256MB EXT
You MUST have Recovery1.4 or above
G1 / MT3G: http://twistedumbrella.slackdev.com/Zero9x-6.18b.zip
MD5: e253ffd6d19aa04e7a75d0ede4a487e1
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.14r3.zip
MD5: Currently Unknown
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.13.zip
MD5: e908408b424835cea75f4f539514fccd
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.12.zip
MD5: 321f92f4e1219979674c5ec85ac1b811
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.11.zip
MD5: 28c474b6ac9d636e5d02f0c18fa3dd13
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.10.zip
MD5: b24c387ec7483acf04f12589aecd09c0
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.2r5.zip
MD5: Currently Unknown
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.2r2.zip
MD5: b8165fe91d777b010db054cbfeb433ae
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.1r2.zip
MD5: 0d10525b55ed6c97b7741a70aa113cdb
http://twistedumbrella.slackdev.com/ZeroXd-5.0r2.zip
MD5: 82a72392e78044ed165448949b9ddfbb
http://twistedumbrella.slackdev.com/ZeroXd-4.5r6.zip
MD5: f1e119e936fb4749f642a69780b4a1c9
http://twistedumbrella.slackdev.com/Resources.zip
Despite what you may have heard, I use SetCPU also.
you can have this spot back hehe
palosjr said:
any screenies coming soon?
Click to expand...
Click to collapse
I posted the thread 30 seconds ago... I just hit upload... Sheesh... didn't even have time to get the third slot for the second rom...
mean cant wait for your casper. also is the led lights like jacs 1.4, like how dere dim, and the lights wont show up on charge?
hiroots said:
mean cant wait for your casper. also is the led lights like jacs 1.4, like how dere dim, and the lights wont show up on charge?
Click to expand...
Click to collapse
Yeah, about that... Wonder where he got the idea to piggyback that script into the boot.img userinit? Do you know? I might... Check ZeroXd...
wow he got it from u or stole it? and published it first?
twistedumbrella said:
Yeah, about that... Wonder where he got the idea to piggyback that script into the boot.img userinit? Do you know? I might... Check ZeroXd...
Click to expand...
Click to collapse
not too many ppl very fond of the new things this JAC's build and the way he is acting about them... tsk tsk... all i can say lol
ummm i think the download links are broken... EDIT- nvm just saw uploading in progress lol
hiroots said:
wow he got it from u or stole it? and published it first?
Click to expand...
Click to collapse
He most likely got the idea on his own. I just think since ZeroXd didn't get any real response he didn't notice it had LED support about a week before the 1.3 refresh was even posted. Ask the kids on twitter about back when I came up with the looney idea and how it killed auto-rotate. I threw in an old version of the codes before someone asked if I had seen the thread. I was still using ones ported from my GScript from months ago. Haha, whatever makes a better build. I'm glad to see both Drizzy and JAC getting SOME use out of something I had a part in. Hell, Shafty figured out the commands, I just got lucky figuring out where to place them.
wow, this is kinda when jac and drizzy was working together and it seemed like jac took all the credit in the built. well thats good we still got devs that supprt each other and not use ones idea and run away with it.
I love this black is a nice color! good **** twisted!
Drizzy Drake Rogers said:
I love this black is a nice color! good **** twisted!
Click to expand...
Click to collapse
Thanks man. I was telling you before, all about the INVERT. Haha. Make it all black, hit invert, all white. Kinda had to go a bit grey though for visibility. I would have left Champion the way it is but I couldn't help it when I figured out that boot animation trick. Anyway, both downloads are live.
Im running it, it seems to run very nice its real smooth think this might be my main rom, Nice work mate.
Sorry to be the first one to post that I cant get past the Hero boot. I wiped, then "rm" my ext4, then wiped again, then applied rom, 3 times now. but all get stick in hero boot. btw its the casper one.
futango said:
Sorry to be the first one to post that I cant get past the Hero boot. I wiped, then "rm" my ext4, then wiped again, then applied rom, 3 times now. but all get stick in hero boot. btw its the casper one.
Click to expand...
Click to collapse
you still need a third partition...
palosjr said:
you still need a third partition...
Click to expand...
Click to collapse
Got 3, 7.2GB Fat32, 400MB Ext4, 32MB Linux Swap
Thanks Twisted, the boot screen is a work of art!
futango said:
Got 3, 7.2GB Fat32, 400MB Ext4, 32MB Linux Swap
Click to expand...
Click to collapse
are you sure? if you did rm to ext4, you removed the partition... did you go into gparted and do print
palosjr said:
are you sure? if you did rm to ext4, you removed the partition... did you go into gparted and do print
Click to expand...
Click to collapse
my bad for not being clear. I did.
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/*
to clear the ext4 from recovery console.
Not really sure what this does..
Its the kernel config file from the fender 1.6 dump. No other rom will use touch screen abilities with this phone except stock so Cursordroid concluded the kernel may be different.
If anyone can use this to make a kernel, or port roms it would be greatly appreciated. Sux having a rooted phone while having to use the stock rom lol
If I knew how to do it I would hop on it... but I is not as smarts as youu guyz
Remove .zip from end of file
EDIT- When the new Mytouch 1.2 comes out in the next couple months, this will be the same build included on it. so nothing like ahead start lol
crypysmoker said:
Not really sure what this does..
Its the kernel config file from the fender 1.6 dump. No other rom will use touch screen abilities with this phone except stock so Cursordroid concluded the kernel may be different.
If anyone can use this to make a kernel, or port roms it would be greatly appreciated. Sux having a rooted phone while having to use the stock rom lol
If I knew how to do it I would hop on it... but I is not as smarts as youu guyz
Remove .zip from end of file
EDIT- When the new Mytouch 1.2 comes out in the next couple months, this will be the same build included on it. so nothing like ahead start lol
Click to expand...
Click to collapse
Going to look at this - thanks
will be so happy if this is an easy fix. Thanks Wes. Didnt even occur to me the changes for the 3.5mm jack output would cause problems
wesgarner said:
Going to look at this - thanks
Click to expand...
Click to collapse
See a few things different in the config
Will have to port over the 3.5mm headphone drivers
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
crypysmoker said:
will be so happy if this is an easy fix. Thanks Wes. Didnt even occur to me the changes for the 3.5mm jack output would cause problems
Click to expand...
Click to collapse
lol yea requires new drivers to get it to work - they are on the MSM .32 git, I will have to backport them - no biggie for that I'm sure
wesgarner said:
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
Click to expand...
Click to collapse
lol Worth a shot.. I already got through the dangourus stuff. I use yours as it is on my spare G1 so no worries about it on here. Ill let you know the outcome.
wesgarner said:
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
Click to expand...
Click to collapse
Argh..
Flashed your newest build, then tried to flash the boot.img.zip file with verification failed. then onto remember that I have the perfected spl on when I tried to flash it lol. Without having a physical keyboard like the g1, and needing to flash the boot.img before boot... is there another way?
Also find that since we had to use a 32B recovery on a 32a phone... nandroid will not work in recovery. Guess ill try fastboot laster
crypysmoker said:
Argh..
Flashed your newest build, then tried to flash the boot.img.zip file with verification failed. then onto remember that I have the perfected spl on when I tried to flash it lol. Without having a physical keyboard like the g1, and needing to flash the boot.img before boot... is there another way?
Also find that since we had to use a 32B recovery on a 32a phone... nandroid will not work in recovery. Guess ill try fastboot laster
Click to expand...
Click to collapse
Try:
adb remount
adb shell
flash_image boot /sdcard/boot.img
reboot
EDIT: I tried that and this is what I got:
mtd: write error at 0x00140000 (Out of memory)
mtd: verification error at 0x00140000 (Out of memory)
mtd: wrote block after 1 retries
mtd: write error at 0x00160000 (Out of memory)
mtd: verification error at 0x00160000 (Out of memory)
mtd: wrote block after 1 retries
darn
Ok... would have just built a kernel for this that should (theoretically) work based off the nexusone kernel...
My battery just died on my laptop
Was a good idea! lol
Will compile in a little while and post
no rush at all guys and I thank those of you that hopped on this much quicker then I expected. eminds me of the old dreamcast homebrew days where everyone actualy worked together rather then who gets the most credit for what.
We got the hard part done.. now onto the fun part. And, at the same time if we dont get a full rom going by the OTA 2.1 update, at least we will have straight dumps off the phones lol
use the custom kernel, and post the dmesg
Compiling the new kernel now lol - sorry for the delay
Will build it into my current git beta build of y-2.7 lol
wesgarner said:
Compiling the new kernel now lol - sorry for the delay
Will build it into my current git beta build of y-2.7 lol
Click to expand...
Click to collapse
Awesome. If possible please let me know once finished for testing.
I cant belive at how many people start bugging you for stuff when your the first to find something. Honestly, My gtalk friends grew 10fold by 3am, of which 6 I had to explain what "stock rom" meant lol How many times can I hear "but whats the point if it doesnt look different" before I want to smackanoob lol
HTC has to release this Kernel source too.
maxisma said:
HTC has to release this Kernel source too.
Click to expand...
Click to collapse
Awwww. noo BOOOO dont tell me that lol. I mean, its fine now because im still using my g1 as to no hurt my wittle fender baby lol.
But once the new mytouch comes out there will be a flood of noobiness over this. But at least I got it out thier early so the good ones can have at it.
By the way, LOVE the quote in yoru sig. Kinda like question I used to get asked back in Xbox 1 modding days. "where is bios and can I take it out?" "I type FTP into my web browser and it wont see my xbox" "
maxisma said:
HTC has to release this Kernel source too.
Click to expand...
Click to collapse
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
wesgarner said:
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
Click to expand...
Click to collapse
Ouuuu. so if its running on same/similar kernel to Nexus one... 2.1 will run with ease.. at least the OTA version will lol.
But, at same time, lot of people going to be ad they grabbed up that nexus one.
wesgarner said:
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
Click to expand...
Click to collapse
You could be right..
http://android.git.kernel.org/?p=ke...118;hb=refs/heads/android-msm-2.6.29-nexusone
-rwxr-xr-x
board-sapphire-gpio.c
blob | history | raw
-rwxr-xr-x
board-sapphire-h2w.c
blob | history | raw
-rwxr-xr-x
board-sapphire-keypad.c
blob | history | raw
-rwxr-xr-x
board-sapphire-mmc.c
blob | history | raw
-rwxr-xr-x
board-sapphire-panel.c
blob | history | raw
-rwxr-xr-x
board-sapphire-rfkill.c
blob | history | raw
-rwxr-xr-x
board-sapphire-wifi.c
blob | history | raw
-rwxr-xr-x
board-sapphire.c
blob | history | raw
-rwxr-xr-x
board-sapphire.h
blob | history | raw
Click to expand...
Click to collapse
crypysmoker,
If we are rocking the same kernel off of the nexus one, what does that mean for us in the future? Are we going to be able to do things quite similar?
Hey all, this is a patch that will change out the kernel for King's SenseHybrid 2.3. I use this rom pretty much daily. It is a cupcake based hero, just this update speeds up the performance a bit.
Instructions:
-Wipe everything!
-Install King's 2.3 SenseHybrid (Please follow his directions.)
http://forum.xda-developers.com/showthread.php?t=563294&highlight=SenseHybrid
- Flash this update immediately after flashing King's rom
- Reboot and enjoy!
ChangeLog:
Updates user.conf (if you don't like it, change it )
Virtual mem settings adjusted
proc_cpu_en=0 # to save battery life
Updates Kernel to CM 4.2.15.1
Removes:
Meebo
HeroLED
AKNotepad
teeter
Adds:
Free Advanced Task Manager (Useful)
****I just posted a 10MB ram hack version in the thread below. It uses CM 4.2.14.1 with CFS instead.****
If you like it, then great! I've been experimenting with using different kernels on different people's roms. I'm new to it, but if anyone has any tips, they are greatly appreciated.
Red.
PS. PLEASE DO NOT ASK ABOUT BT! IF YOU HAVE READ ANYTHING ON THIS SITE CONCERNING HERO ROMS ON A G1/DREAM THEN YOU WOULD KNOW BETTER AND WOULDN'T RISK BEING FLAMED.
Sounds good I was going to flash the sensehybrid soon anyways so this sounds perfect.
Wait a few minutes..
If you can hold off a bit, I am also making a 10MB ram hack version with CM 4.2.14.1 CFS. Just testing now.
Red.
CM 4.2.14.1 10MB Ram Hack with CFS
Here is another one that you can flash immediately after flashing king's 2.3. This uses the 4.2.14.1 CM kernel and the CFS 10MB ram hack. I absolutely hate BFS on G1/Dreams! Anyways, this one should run faster. I would also look into the thread that has been posted recently about speeding up hero roms and change the line in your init.rc to keep rosie in memory. just copy the init.rc onto your sdcard and edit it with notepad++ (windows program, it is great!) and then copy it back to your root over the existing init.rc and reboot. (if this is complicated, then don't try it.)
Otherwise, Enjoy!!
will this work without an ext/swap partition?
Without ext partition...
Honestly, if you are using the Death SPL and you are running this with my ram hack, you should be ok. Unfortunately, the compcache on King's earlier roms are usually broken. I tried pushing ramzswap from the CM kernel and still no luck, but then again, I'm not as savy as some of the other dev's out there. You will just have to edit the user.conf after you finish flashing the two, you want to do the following:
First, before flashing you want to pull the user.conf from the system/bin/ directory in king's zip file. edit the user.conf using notepad++ in windows and change the linuxswap=1 to 0 so that it turns it off. then copy that file to your sdcard.
immediately after flashing the two files,
-go to console from the recovery and type the following
mv /sdcard/user.conf /system/bin/
reboot
this will disable the linuxswap and then you will be able to run the rom. But again it would be better with a swap partition.
Hope this helps.
Red.
would prefer the WG kernel but okay thanks
protomanez said:
would prefer the WG kernel but okay thanks
Click to expand...
Click to collapse
Same here, WG is great. I tried the RH CFS patch, but I got an error while flashing it. Had to restore from switchrom.
where's the wg-kernel patch for 1.5 hero roms?
Also, does multitouch still work with THIS patch?
boot loop...
?
Chabsie, telling me u got a boot loop doesn't help me resolve the problem much. You must have DeathSPL for this rom, Must be full wipe, and EXT4 partition. If that doesn't help, please list the stats for your phone, which hack u are using and where your issue occurs.
Jcarrz, WG kernel version of this is released in another thread. It is on 2nd or third page, just search.
Thanks.
Red.
Just a question, since im not an expert. but how is this cupcake based hero, when CM 4.2.15.1 is donut based? Also thanks i will give it a try now.
Snacky-cakes
domex2k said:
Just a question, since im not an expert. but how is this cupcake based hero, when CM 4.2.15.1 is donut based? Also thanks i will give it a try now.
Click to expand...
Click to collapse
HTC developed the sense UI and this port is from the HTC Hero or the earlier Droid Eris (Prior to upcoming update from Verizon to 2.1.) Both of those phones use Cupcake as the base and then Sense UI is just a pretty cover for it. The kernel I used is from CM's Donut based roms, which is more than compatable, but again, the framework and ramdisk and everything else reflects a 1.5 environment. Enjoy the patch.
Red.
redd12345 said:
HTC developed the sense UI and this port is from the HTC Hero or the earlier Droid Eris (Prior to upcoming update from Verizon to 2.1.) Both of those phones use Cupcake as the base and then Sense UI is just a pretty cover for it. The kernel I used is from CM's Donut based roms, which is more than compatable, but again, the framework and ramdisk and everything else reflects a 1.5 environment. Enjoy the patch.
Red.
Click to expand...
Click to collapse
Got it. Thanks
Yeah it runs pretty smooth, the only thing was the contacts from Gmail did not sync, but im going to later on reflash and see what happens.
sync fix
domex2k said:
Got it. Thanks
Yeah it runs pretty smooth, the only thing was the contacts from Gmail did not sync, but im going to later on reflash and see what happens.
Click to expand...
Click to collapse
Just go back into system menu and re-sync manually and give it a minute. It will work fine. I had that happen on one of the trials.
Red.
redd12345 said:
Just go back into system menu and re-sync manually and give it a minute. It will work fine. I had that happen on one of the trials.
Red.
Click to expand...
Click to collapse
Great i will give that i try Thank you
Suggestion
domex2k said:
Great i will give that i try Thank you
Click to expand...
Click to collapse
You may like this one better.
http://forum.xda-developers.com/showthread.php?t=654789
This is the Wes Garner Ramhack. It should be slightly faster. I think that you still need to have a partition though because of the apps to sd. You would have to do complete wipe for this one again.
Red.
redd12345 said:
You may like this one better.
http://forum.xda-developers.com/showthread.php?t=654789
This is the Wes Garner Ramhack. It should be slightly faster. I think that you still need to have a partition though because of the apps to sd. You would have to do complete wipe for this one again.
Red.
Click to expand...
Click to collapse
Thanks for the link. I will give it a try, because some reason when used the other 2 cm patches the camera and camcorder will FC and so i then just flashed this rom solo and it did not fc
multitouch?
redd12345 said:
Chabsie, telling me u got a boot loop doesn't help me resolve the problem much. You must have DeathSPL for this rom, Must be full wipe, and EXT4 partition. If that doesn't help, please list the stats for your phone, which hack u are using and where your issue occurs.
Jcarrz, WG kernel version of this is released in another thread. It is on 2nd or third page, just search.
Thanks.
Red.
Click to expand...
Click to collapse
Sorry for being vague. I had everything right except ext3 instead of ext4. I'm looking for some directions on how to upgrade. If you have any please let me know, thanks.
So I was a little bored this evening and wanted to mess around.
bml5 contains JUST the Linux kernel (zImage) and wanted to see what I could make it do.
Messing up this block device (/dev/block/bml5) won't actually hinder your ability to reflash with odin. messing up bml1 and 2 will though - those are boot and Sbl.
I grabbed this rom from http://forum.xda-developers.com/showpost.php?p=10040444&postcount=1 (rom cooking for the Galaxy S)..
ripped the zImage out of it, and dd'd it to my bml5 kernel.. Rebooted.. and everything worked.
Code:
Linux version 2.6.32.9 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2009
q3-67) ) #1 Thu Dec 2 00:58:01 KST 2010
This kernel is a couple of MB bigger than the stock one, so I'm not sure what additional functionality it has (if any), but briefly playing around with it doesn't seem like there are any issues.
I'm running JPA currently, but going to try dropping the JPB kernel on it. Keep you guys posted..
...............
Hrm, nevermind.. Looks like after every reboot the kernel gets reverted. There's a tool for the Galaxy S called redbend_ua that's supposed to be used to flash bml live. Trying to get it working.
.............................................
Running JPA with the JPB kernel right now:
Code:
Linux version 2.6.32.9 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2009
q3-67) ) #1 Sat Dec 4 19:45:05 KST 2010
Going see how it runs.. Battery life was my main issue before running JPB.
You could flash a zimage inside a PDA.tar with Odin as it is intended if redbend does not work on the g3... i really like the experimenting that is going on here at this time...
Btw, flashing kernel from sgs wont really work i think, since the sgs has armv7 CPU and the g3 has armv6 with very different instruction set and CPU frequency table. If you want to experiment with kernels you should download sztupys kernel building vm and the i5800 sources from Samsung and build your own one, when this is working you could try some optimizations like hardcore made them and so on.
FadeFx said:
You could flash a zimage inside a PDA.tar with Odin as it is intended if redbend does not work on the g3... i really like the experimenting that is going on here at this time...
Click to expand...
Click to collapse
I figured that would work. I just have a tar file with zImage in it by itself and choose it in the "One Package" and it seems to do the trick.
Flashing the Galaxy S kernel via this method made me stuck on the i5800 screen... So clearly that kernel won't work (assuming it's due to the differences in bml numbering, etc).. I also tried the Gingerbread release for the Nexus S (which supposedly works on the Galaxy S), and the same result unfortunately.
Gonna keep experimenting =)
I also wouldn't mind grabbing the FROYO sources when they're available (only 2.6.27/29 sources are available right now) and maybe adding in fastboot support.. That would be nice compared to requiring to use ODIN... But that also could be a bootloader thing - which in that case would not work.
Huh updated my previous post while you WWW writing this...
precurse said:
I figured that would work. I just have a tar file with zImage in it by itself and choose it in the "One Package" and it seems to do the trick.
Flashing the Galaxy S kernel via this method made me stuck on the i5800 screen... So clearly that kernel won't work (assuming it's due to the differences in bml numbering, etc).. I also tried the Gingerbread release for the Nexus S (which supposedly works on the Galaxy S), and the same result unfortunately.
Gonna keep experimenting =)
I also wouldn't mind grabbing the FROYO sources when they're available (only 2.6.27/29 sources are available right now) and maybe adding in fastboot support.. That would be nice compared to requiring to use ODIN... But that also could be a bootloader thing - which in that case would not work.
Click to expand...
Click to collapse
Fastboot in fact is a bootloader thing. But redbend would be cool, you'd have to look into the install script in that kernel update.zip, there must be a line to call the redbend.ua binary that is included in the zip also, maybe there the bml partition is specified where the zimage has to go to as a parameter...
FadeFx said:
Huh updated my previous post while you WWW writing this...
Click to expand...
Click to collapse
Nice.. Yeah, I already got the sources earlier. Supposedly there is still source code that's unobtainable which is required to get the phone working - so building the kernel alone isn't going to cut it.
I also read (though not how accurate it is) that you could avoid the proprietary rfs that samsung uses, and make this phone work with yffs(2) - which stock Android uses to run on anyways. So there are a lot of options, and getting rid of rfs would be I think - as I've read it's pretty ****ty.
FadeFx said:
Fastboot in fact is a bootloader thing. But redbend would be cool, you'd have to look into the install script in that kernel update.zip, there must be a line to call the redbend.ua binary that is included in the zip also, maybe there the bml partition is specified where the zimage has to go to as a parameter...
Click to expand...
Click to collapse
I tried specifying the bml partition properly and everything - it just errors out. I'll probably try messing around with it further - but it appears ODIN does what I need it to do for now. It would just be really nice to have the option of flashing from other operating systems than just Windows.
Someone was saying Samsung includes Fastboot (Forced upload by keypressing mode) which can be brought up with holding Home + Vol Up + Power. Though, trying it briefly showed no devices in fastboot after I plugged it into my PC. It's not a driver thing.
I don't think forced upload is in any way related to fastboot, since fb gives a console output normally. Redbend may be needed in a armv6 compatible version also. Gona find out...
FadeFx said:
I don't think forced upload is in any way related to fastboot, since fb gives a console output normally. Redbend may be needed in a armv6 compatible version also. Gona find out...
Click to expand...
Click to collapse
The more I read into this, the more I almost wished I went with something like the Nexus series' ... But then they're also like 3-4x the cost.
As long as the bootloader doesn't get flashed, I think it'd be pretty hard to brick this phone unless it gets overclocked and kills hardware =)
precurse said:
The more I read into this, the more I almost wished I went with something like the Nexus series' ... But then they're also like 3-4x the cost.
As long as the bootloader doesn't get flashed, I think it'd be pretty hard to brick this phone unless it gets overclocked and kills hardware =)
Click to expand...
Click to collapse
Oc can only freze but not brick a CPU, over volting is the dangerous thing...
For redbend you'd have to loock in /sbin if the binary is there... i have also read of some open source alternative that can do the same...
Info on redbend for sgs: http://forum.xda-developers.com/showthread.php?t=765724
The unobtainable sourcecode should be in the initramfs as binary, its mostly driver stuff.
Do we have an initramfs anywhere? I only thought there was a zImage..
Is this the open source alternative you're speaking about?
http://www.glassechidna.com.au/products/heimdall/
And there is a redbend_ua file there. However, it doesn't obey any type of command line arguments. That was the thread I was reading about redbend before actually. According to it: "redbend_ua working binary. (some firmware ship a new binary that does not accept command line parameters)"
Perhaps JPA doesn't accept them?
I'm just looking at the /fota.rc file... Like, there are lines commented out for yaffs2.
Code:
mount rfs /dev/block/stl6 /system check=no
# mount yaffs2 /dev/bml6 /data nosuid nodev
mount rfs /dev/block/stl7 /data nosuid nodev check=no
There HAS to be a way to convert from rfs to yaffs2 with the G3
precurse said:
Do we have an initramfs anywhere? I only thought there was a zImage..
Is this the open source alternative you're speaking about?
http://www.glassechidna.com.au/products/heimdall/
And there is a redbend_ua file there. However, it doesn't obey any type of command line arguments. That was the thread I was reading about redbend before actually. According to it: "redbend_ua working binary. (some firmware ship a new binary that does not accept command line parameters)"
Perhaps JPA doesn't accept them?
Click to expand...
Click to collapse
The initramfs is inside the zimage, i think it should be provided along with the sources also. If not, there is a howto for extracting the initramfs from a zimage in the i9000 section.
Heimdall is an alternative to Odin that is platform independent. However it'd have to be adapted to the g3. I already asked Benjamin Dobell to do it, but he wouldn't for some reason.
Maybe we should ask someone using older firmwares to extract a redbend.ua for testing
precurse said:
I'm just looking at the /fota.rc file... Like, there are lines commented out for yaffs2.
Code:
mount rfs /dev/block/stl6 /system check=no
# mount yaffs2 /dev/bml6 /data nosuid nodev
mount rfs /dev/block/stl7 /data nosuid nodev check=no
There HAS to be a way to convert from rfs to yaffs2 with the G3
Click to expand...
Click to collapse
I think yaffs2 wont be an option as it isn't for the i9000, since the devices are built using onenand that takes care of wearleveling by itself and wont accept a pure band filesystem since it emulates a block device to the system if i am not mistaken.
FadeFx said:
The initramfs is inside the zimage, i think it should be provided along with the sources also. If not, there is a howto for extracting the initramfs from a zimage in the i9000 section.
Heimdall is an alternative to Odin that is platform independent. However it'd have to be adapted to the g3. I already asked Benjamin Dobell to do it, but he wouldn't for some reason.
Maybe we should ask someone using older firmwares to extract a redbend.ua for testing
Click to expand...
Click to collapse
Good call.. I assumed that was it if there was actually one..
http://forum.xda-developers.com/wiki/index.php?title=Extract_initramfs_from_zImage
I believe the /sbin directory is in the initramfs, since there is no /sbin in the factory.rfs file (this file is ONLY /system). I'll see if I can extract it from an older firmware to see how it works. It does look like the samsung bootup scripts for OTA updates is in fact calling:
service redbend_ua /sbin/redbend_ua all
oneshot
FadeFx said:
I think yaffs2 wont be an option as it isn't for the i9000, since the devices are built using onenand that takes care of wearleveling by itself and wont accept a pure band filesystem since it emulates a block device to the system if i am not mistaken.
Click to expand...
Click to collapse
Yeah, I was thinking there is more to it. However, I'm thinking it's just a kernel thing... So if a kernel gets built that doesn't require that, and the filesystem matches that - I don't see how that wouldn't work.
I'm just brainstorming. There might really be a technical limitation though.
There in fact is a hardware limitation, since the onenand controller does this on hardware, its not a driver issue at all. That's why the sgs guys use ext filesystems for this... ext4 would be the way to go.
Btw, sorry that i can't help experimenting, but i never have written one line of code in c or c++ nor have i ever compiled a kernel by myself, i am just a Guy reading to much in forums, that's why i know all that for me useless **** and am just happy to share my knowledge to keep others from having to go a way that has already been gone...
All good. Maybe you will start =)
I got the initramfs extracted now.. I'm tempted to make some customizations to it (like the default.prop, etc). I'll grab the redbend from the older ECLAIR firmwares and see how it works.
Btw, you should rename the thread since this has nothing to do with i9000 anymore
Originally this was going to be something I would do for Kyorarom v0.2.0, but I will also let the general public in on my works.
I am currently going through every single file in CM6.2 and seeing if it will work on Froyo with little to no effort. Why? Well think of it as a poor mans alternative to a fully functioning CM6.2. I respect marcellusbes work 100% but there are so many people who are being impatient about the non-existant ETA of CM6.2 and CM7 (BECAUSE IT SAYS THERE IS NO ETA AND THERE SHOULD NOT NEED TO BE AN ETA), I decided to give the people half of what the want: the performance and open sourceness of CM6.2 while still retaining 100% functionality of the Samsung firmware.
Current Status
99% of the bins are working
A few CM apps are working
Some of the libs are working (but they are more just sitting in there)
--- CONSIDER THIS VERY MUCH IN BETA - THIS WILL HAVE A FEW BUGS HERE AND THERE SO PLEASE REPORT ALL OF THEM SO I CAN FIX THEM ---
Now remember, this is by no means an alternative to CM6.2, it is more of a stopgap for people who really want our phone to have CM6.2 on it.
I have been working on this all day today and haven't been able to actually test it properly, but it appears to be stable with the files I have added, and it also appears to be quicker. Not by much, but it feels a little smoother.
Why would I need this?
As I said, it's a poor mans CM6.2. It will give you 90% of the performance of CM6.2 while still giving you 100% functionality (provided I haven't broken anything) from Samsung firmware. Programs run quicker, the system responds faster, and the system just feels smoother in general. It's not like FuguTweaks or V6 Supercharger which gives you a tiny change, the goal of this is to give you a HUGE change.
What is noticably quicker?
Well I need people to tell me that, but what I have noticed is quicker is:
Screen rotate happens quicker
Scrolling through menus
Swiping around websites
System boot time
What do I need to use this?
Well I have only tested this on Kyorarom v0.2.0 alpha (unreleased), so I don't know how your results may go, but it SHOULD work on all JPS based SAMSUNG ROMS.
THIS IS NOT A PATCH FOR CM6.2! THIS IS A PATCH FOR SAMSUNG!
You will also need CWM with update.zip signing disabled. This is provided as an update.zip as there are SO MANY permissions that need to be set in the bins/xbins/libs that it would be ridiculous to tell people to run an ugly script which will probably not work on 99% of peoples computers, so an update.zip without signing is how I will do this. Why no signing? Because every guide I have followed to tell me how to sign a zip or an APK has done nothing useful. SOMEONE TELL ME HOW PLEASE!
How do I install this?
Just put this on your SD Card, go into CWM and tell it to update from an update.zip. Pretty simple. I highly recommend doing a system.img backup first though to be on the safe side in case something goes terribly wrong. Format your /system before restoring the system.img.
What should I do if I get a bug such as a force close or a random reboot
Get your phone right to just before the crash happens
Plug your phone into ADB
Go into ADB SHELL
Type logcat > /sdcard/crashlog.txt
Reproduce the crash
Wait until it has rebooted/force closed
Press Ctrl-C on ADB SHELL
Get the crashlog.txt off your SDcard and paste the last about 20-30 lines in a code box here telling me what you did to cause the crash.
Links
Patch 0.3.1 (requires Samsung firmware, recommended to be on JPS)
CMapps 0.3.0 (should work on Samsung firmware without CMbins)
CMbins Remover (will only replace the bins with the original Samsung bins)
Patch v0.2.0 (requires Samsung firmware, recommended to be on JPS)
Busybox Fix (for in case you installed any of the patches v0.0.3 and below - NOT AN UPDATE.ZIP: THIS IS A BUNCH OF FILES WITH A README)
Please note that this may play up with some custom themes, especially large ones such as MIUI as this replaces a lot of files which these themes may be using or rely upon.
Credits
marcellusbe for his incredibly hard work on CM6.2 and CM7 which sadly seems to not be appreciated as much as it should by some of this community. Please go over to both the CM6.2 and CM7 threads and thank him for his hard work, even if you have already done so.
Change Log
v0.3.1
Removed more pointless stuff such as the etc and libs as they won't provide a performance boost. They were more decoratio.
Fixed install script which removed TW apps but didn't replace them from v0.3.0.
v0.3.0
Removed pointless bins which don't provide any performance boost, such as ping and stuff.
Fixed force close lag bug.
v0.2.0
Added the last few bins that were missing. Only bins missing are the ones that cause the system to break.
Added a few more things from etc from CM. They shouldn't cause any difference.
v0.1.1
Fixed dalvik-cache building.
v0.1.0
Removed xbin. It was causing too many problems
Added a few libs (ones that aren't in Samsung)
Added a few items from etc
Replaced a few stock Samsung apps in order to clean the system up before I remove twframework.
v0.0.3
Fixed the missing meta-inf folder in the update.zip. Sorry guys!
v0.0.2
Fixed the busybox issue. the patch removed the old busybox and replaced it with a broken one. If this doesn't fix it then 'mount -o rw,remount /dev/block/stl6 /system' and 'chmod 755 /system/xbin/*'
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
cdesai said:
I was doing something like this , cm framework on jps
But you did more
np
i didnt have the time to complete it fully(exams)
Best of luck!
Click to expand...
Click to collapse
If you wish to help me then by all means I'll be grateful. I am nowhere near finished as there are a few files in /system/bin that still need checked to see if they cause issues. I just went through the alphabet and if a file such as 'dexopt' caused problems then I left out all of D. However that's just an example. Dexopt is left out, but I left in the rest of D as I found it causing problems later down the track. I know I am missing Q and S. I'm gonna go through them all tomorrow.
EDIT: Not to mention I want to go through frameworks and libs and the etc folder too.
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Sergiales said:
I am not sure if this is helpfull or not... I instaled the update in my phone. At the moment, only issue is that busybox installer is not working after it get superuser permisions, and then i cannot open any other app. I need to reboot my system. If i find any other issue, i will let you know.
Click to expand...
Click to collapse
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
@hillbeast
you also plan to port the framework of cm6?
ale_bot said:
@hillbeast
you also plan to port the framework of cm6?
Click to expand...
Click to collapse
I hope I can. The plan is to get everything that will work from CM6.2 in Samsung firmwares to work.
New version uploaded. See first post for details.
I fixed the busybox issue. I thought I fixed it earlier but aparently not. It was CM6.2s Busybox being in there that killed it. I put the Samsung one into v0.0.2 so it'll fix the grief it caused with version 0.0.1.
If it still causes issues then go into adb shell (or Terminal Emulator) and run this code:
Code:
mount -o rw,remount /dev/block/stl6 /system
chmod 755 /system/xbin/*
Donate and get rewarded
Good work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
You (just caught you user reading this), could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones (dharamg3, marcelubes.. and some of all the other great programmers) donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
(•.•) said:
Gut work, hillbeast.
I wish you would work more togother, i mean most of the main developers in g3.
you know the names.
And some more support from the community with donating and thanks or appriciation.
Yes You, could donate a little bit, so that your galaxy 3 is got tuned with great software, so it worth allmost double the price then you paid for it, because it expands with possibillities and powers.
Just click someones donate button, type the number: 5 or 10 or 20 or 100 +++ etc, log in to paypal and DONATE!
Click to expand...
Click to collapse
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
hillbeast said:
I actually work with dharamg3 on occasion and have given him ideas for G3Mod. I just don't take credit for anything because my contributions have been very minor at best and my credit isn't deserved considering how much more he and marcell have done for our phone.
Click to expand...
Click to collapse
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
(•.•) said:
Yeah, i mean it for all developers, but you included of course. so why not.
Just for every user to remind if he reads my post.
Click to expand...
Click to collapse
Yeah that is the entire point of the XDA: developers helping developers to make our phones incredible and help them reach their true potential.
People bash the Galaxy 3 but undreneith it's actually a really good phone with really good hardware. It's no dual-core Cortex-A9 with 1GB of DDR2 RAM or anything, but it's certainly a very good mid-range phone. It was just held back by Samsung not programming it right.
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
niteshtak said:
Nice vision man...best of luck
To make things easier i guess you can consult marcellusbe about what all stuff is not working in CM6.2...then u'll need to replace only those files instead of going through evry file !!
Click to expand...
Click to collapse
Yes however I also need to find what is compatible with the rest of Samsungs firmware.
hillbeast said:
Hmm, I might have done somethign weird with xbin. Try going into adb shell and run 'chmod 755 /system/xbin/*'. I might have to get it to set permissions in the update.zip for that folder.
EDIT: Try restore your system back to how it was prior the install of the update, and then try the other zip I just put in the first post. I think it'll be the xbin folder doing it.
Click to expand...
Click to collapse
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Guys I totally forgot the meta-inf folder in v0.0.2. You can just use the one from v0.0.1 as there is no signing or anything. I'll see if I can get the link on my phone for v1
Sent from my GT-I5800 using XDA App
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
Well its just a try to get the CM6.2 speed and smoothness on the samsung ROM..without having the bugs of CM6.2 which arent solved yet...
Sergiales said:
I have just installed that 0.1 you told me and now is working good. I am gonna try the 0.2 and tell you if all is ok.
Click to expand...
Click to collapse
Same problem in 0.2 with busybox installer, even trying to fix it with adb.
Darius_AWS said:
But why using cyanogenmod files in samsung firmware ?
You know that CM 6.2 is the most awesome rom for froyo ! I've almost never had any lags and the rom is fast even after installing a tons of app's !
Click to expand...
Click to collapse
As I stated in the OP, Cyanogenmod is incomplete and is buggy. The camera doesn't work, the FM radio doesn't work, no Bluetooth, and some things are buggy. By working in the opposite direction of moving to Cyanogenmod with small steps by using the working components from it, we get a balance.of speed and functionality which is what a lot of people have been moaning about all this time since CM went alpha.
Again, huge respect to marcell for getting it this far. This is a huge achievement from him.
Also here is the mediafire link for v1 so people can grab meta-inf and insert it into the v2. I will fix this in v3 later today.
Sent from my hybrid Kyorarom + Cyanogenmod Galaxy 3