Related
This is an EBI1 port of CyanogenMod and SuperD with the Ram Hack
It is compatible with radio version 3.22.20.17 or 3.22.26.17(latest from Rogers).
To root your Rogers Dream see: CyanogenMod Wiki - Full Update Guide - Rogers Dream EBI1 to CyanogenMod
To install this port first flash the EBI0 rom:
CyanogenMod:
http://forum.cyanogenmod.com/index.php?/topic/295-cyanogenmod-for-dream-magic-v4215-03032010/
SuperD:
http://forum.xda-developers.com/showthread.php?t=613809
http://www.benbuchacher.com/superD/2010/04/29/super-d-1-11/
It doesn't matter which one you pick any version will work.
Then download and flash the EBI1 port file:
CyanogenMod 4.2.15.1:
Beav-CM-4.2.15.1-EBI1-RamHack-signed.zip: http://www.multiupload.com/3GO3ID129A
SuperD 1.11 with Merlos' WGv4 kernel:
Beav-SuperD-1.11-EBI1-GM-WGv4-RamHack-signed.zip: http://www.multiupload.com/N93MKLKAZB
The kernel in this SuperD port is built from Merlos' fork of Wes Garner's v4-beta tree.
You can also just flash this on top of another port file without a wipe.
The ROM version must match the port file version.
The ram hack gives you about 8mb extra ram
Before hack: 98956
After hack: 107084
Thanks Daproy for the patch
Thanks to Cyanogen, Wes Garner, bbuchacher, merlos and all the other great devs out there!!
Testing this now! Will report back soon.
EDIT: It works! Thanks! Been waiting for this for a long time! My HTC Dream has never been snappier!
EDIT2: Will this kernel boot work for 32A Magics as well?
No wireless on Super D 1.9.3. I think you forgot the wlan.ko
SilentTweak said:
Testing this now! Will report back soon.
EDIT: It works! Thanks! Been waiting for this for a long time! My HTC Dream has never been snappier!
EDIT2: Will this kernel boot work for 32A Magics as well?
Click to expand...
Click to collapse
No problem
I think it should work on a 32A Magic but I don't have one to try it.
xaueious said:
No wireless on Super D 1.9.3. I think you forgot the wlan.ko
Click to expand...
Click to collapse
Sorry about that. Try it again.
Looks like you used magic port and added a ram hack
both these kernels exist wo ramhack already in sapphire development which is wherethis should be posted
Works now as expected. Saved lazy old me some time
This hack applies to any Magics and Dreams with a 3.X series radio, so this does fit here.
Difference is noticeable on my phone
alan090 said:
Looks like you used magic port and added a ram hack
both these kernels exist wo ramhack already in sapphire development which is wherethis should be posted
Click to expand...
Click to collapse
The RAM hack is not very useful for Magic users because their phones already have enough RAM. Because this port is only useful for Rogers Dream users, I posted it in the Dream section.
xaueious said:
Works now as expected. Saved lazy old me some time
Click to expand...
Click to collapse
Great!
alan090 said:
Looks like you used magic port and added a ram hack
both these kernels exist wo ramhack already in sapphire development which is wherethis should be posted
Click to expand...
Click to collapse
Why? The Sapphire doesn't really need the extra RAM, but the Dream does. Besides, some of don't know how to add a RAM hack to anything
Zoltair Wright said:
Why? The Sapphire doesn't really need the extra RAM, but the Dream does. Besides, some of don't know how to add a RAM hack to anything
Click to expand...
Click to collapse
BECAUSE 3.x radio is technically 32a which is sapphire / ebi1 dreams
6.X radio is hero/sense 32a radio
32B is 2.x radio aka dream / g1
EBI rogers dream users should be in the sapphire section for roms as they are compatible with any 32a rom
OR
sign the data waiver and use the REGULAR 32b roms?
THERE IS NO REASON TO USE EBI1 radio on rogers dreams other than making life difficult for yourself
There are two versions of the Sapphire/Magic. One has less RAM than the other.
alan090 said:
BECAUSE 3.x radio is technically 32a which is sapphire / ebi1 dreams
6.X radio is hero/sense 32a radio
32B is 2.x radio aka dream / g1
EBI rogers dream users should be in the sapphire section for roms as they are compatible with any 32a rom
OR
sign the data waiver and use the REGULAR 32b roms?
THERE IS NO REASON TO USE EBI1 radio on rogers dreams other than making life difficult for yourself
Click to expand...
Click to collapse
You don't know what you are talking about with regards to 32A/32B. There's a lot of confusion at XDA about this though.
Also, the Dream forum has traditionally been the place to be for 32B Magic ROMs, due to the hardware similarities between the phones.
This is getting off topic. If this port isn't for you, you may ignore this thread.
This port is universal among Dream/Magic and is dependent only on radio version.
alan090 said:
BECAUSE 3.x radio is technically 32a which is sapphire / ebi1 dreams
6.X radio is hero/sense 32a radio
32B is 2.x radio aka dream / g1
EBI rogers dream users should be in the sapphire section for roms as they are compatible with any 32a rom
OR
sign the data waiver and use the REGULAR 32b roms?
THERE IS NO REASON TO USE EBI1 radio on rogers dreams other than making life difficult for yourself
Click to expand...
Click to collapse
You signed your soul away to Robbers. That's all I have say. I refuse to let Robbers make me sign anything besides voice contracts.
xaueious said:
There are two versions of the Sapphire/Magic. One has less RAM than the other.
You don't know what you are talking about with regards to 32A/32B. There's a lot of confusion at XDA about this though.
Also, the Dream forum has traditionally been the place to be for 32B Magic ROMs, due to the hardware similarities between the phones.
This is getting off topic. If this port isn't for you, you may ignore this thread.
This port is universal among Dream/Magic and is dependent only on radio version.
Click to expand...
Click to collapse
Too true. Someone should make a post about that on the wiki. It gets so confusing with all the guides about "How To Change SPL, Change Radio, Change Recovery" There should be a list of what's compatible with what. Like a combinations list.
Been running sweet with superd since release, thank you, I wanted my ram back, phones aren't for playing 3d games as far as I'm concerned.
beav_35 said:
This is an EBI1 port of CyanogenMod and SuperD with the Ram Hack
It is compatible with radio version 3.22.20.17 or 3.22.26.17(latest from Rogers).
To root your Rogers Dream see: CyanogenMod Wiki - Full Update Guide - Rogers Dream EBI1 to CyanogenMod
To install this port first flash the 32b rom:
CyanogenMod:
http://forum.cyanogenmod.com/index.php?/topic/295-cyanogenmod-for-dream-magic-v4215-03032010/
SuperD:
http://forum.xda-developers.com/showthread.php?t=613809
http://www.benbuchacher.com/superD/downloads/roms/
Be sure to download the NON Ram hack version
Then download and flash the EBI1 port file:
CyanogenMod 4.2.15.1:
Hotfile.com: Beav-CM-4.2.15.1-EBI1-RamHack-signed.zip
uploaded.to: Beav-CM-4.2.15.1-EBI1-RamHack-signed.zip
SuperD 1.9.3:
Hotfile.com: Beav-SuperD-1.9.3-EBI1-WGv3-RamHack-signed.zip
uploaded.to: Beav-SuperD-1.9.3-EBI1-WGv3-RamHack-signed.zip
The kernel in this SuperD port is built from Wes Garner's v3-cfs tree.
You can also just flash this on top of another port file without a wipe.
The ROM version must match the port file version.
The ram hack gives you about 8mb extra ram
Before hack: 98956
After hack: 107084
Thanks Daproy for the patch
Thanks to Cyanogen, Wes Garner, bbuchacher and all the other great devs out there!!
Click to expand...
Click to collapse
Hey would you shoot me the memory addresses for the EBI1 with RAMHack? Will post it to github
Isn't it this?
beav_35 said:
Isn't this it:
http://github.com/daproy/dp-kernel/commit/2f1d3a3fc8ce7ccf5b09f291d791350083801ff5
Click to expand...
Click to collapse
xaueious said:
Isn't it this?
Click to expand...
Click to collapse
Yes, it is
thanks works great
Now that all the bugs have been worked out of Super D 1.10 I built my ram hack port for the latest release.
SuperD 1.10.2:
Hotfile.com: Beav-SuperD-1.10.2-EBI1-WGv3-RamHack-signed.zip
uploaded.to: Beav-SuperD-1.10.2-EBI1-WGv3-RamHack-signed.zip
Click to expand...
Click to collapse
Thanks for doing this again and saving me some time.
Edit:
Flashed. No wipe. Only wiped dalvik cache. Rom is fine.
1.10.3 ??
Can we use this on superD 1.10.3?
If not, can we expect the port soon?
Boomgawd said:
Can we use this on superD 1.10.3?
If not, can we expect the port soon?
Click to expand...
Click to collapse
Yes, it will be out soon.
Hello,
first, scuse me for my very bad english, but I'm 15, Swiss and my native language is French!
I have a question....how can I make a port? Because it got many ROM for 32A [6.35], and they are very good, but I can't have those. If I have a 32A without BT, OK, but how can I make a port?
I've tried to repack boot.img using a 32B (eris ROM) kernel to port a 32A [6.35] ROM, but, it don't freeze, but it restarted many times, and then, it go to recovery!
If anyone can help me....
The 6.35 radio are a bit tougher to build for. But you can take a working 6.35 kernel and repack it with the ramdisk from the ROM you want to port. A port basically has the following:
1) Kernel that matches the device you want to port TO (ie. 32A)
2) ramdisk from the ROM you are porting
You then have to pack those files together using mkbootimg --base 0x19200000
Here are two posts that take you through the steps:
http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
http://androidspin.com/forum/showthread.php?t=2207
Here is an old guide, where it says to use mkbootimg-H, use mkbootimg --base 0x19200000.
http://rapidshare.com/files/249740980/Guide_nk02ion_r4_LITE.txt
i used the kitchen linked in my sig to make my current rom, which i ported from 32A to 32B.
By the way, I wanna ask you two questions that always confused me.
First, what is a PORT?
And does every ROM need a port?
THX
nabor said:
By the way, I wanna ask you two questions that always confused me.
First, what is a PORT?
And does every ROM need a port?
THX
Click to expand...
Click to collapse
I don't know how to define port for you so ill use examples!
I'm a 32A user, and since there are a ton of 32B roms.. I need a port to use a 32B rom.
There are also ports for other things like... if I'm using a 6.35 radio, people like giant_rider can port over a g1 rom over to a 32a. Does this make sense LOL sorry if I confuse you more!
But users like myself need these ports since there aren't many 32A roms for my radio (3.22 and 6.35)
So hopefully you understand that not every rom needs a port after reading the above..
nabor said:
By the way, I wanna ask you two questions that always confused me.
First, what is a PORT?
And does every ROM need a port?
THX
Click to expand...
Click to collapse
in general terms, a port is making a piece of software or code designed to work on one particular type of hardware work on a different type of hardware.
in this case the HTC magic uses two different types of motherboard. 32A and 32B.
a rom might be built specifically for the 32A board and so it will not work on the 32B unless it is ported first.
therefore, not all rom's need to be ported. you only need to port a rom if you wish to use it on hardware that it was not originally designed for.
not all rom's can be ported.
bcrook said:
The 6.35 radio are a bit tougher to build for. But you can take a working 6.35 kernel and repack it with the ramdisk from the ROM you want to port. A port basically has the following:
1) Kernel that matches the device you want to port TO (ie. 32A)
2) ramdisk from the ROM you are porting
You then have to pack those files together using mkbootimg --base 0x19200000
Here are two posts that take you through the steps:
http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
http://androidspin.com/forum/showthread.php?t=2207
Here is an old guide, where it says to use mkbootimg-H, use mkbootimg --base 0x19200000.
http://rapidshare.com/files/249740980/Guide_nk02ion_r4_LITE.txt
Click to expand...
Click to collapse
hey what are the advantages to using mkbootimg... because i've been using the so called old port tools
Sphaerophoria said:
hey what are the advantages to using mkbootimg... because i've been using the so called old port tools[/QUO
Only advantage is that you can build with diff offsets. Only need one binary for all packages u might build. If the "old" one works, keep using it.
Click to expand...
Click to collapse
So, I'm testing it, I say you later if I can make a port!!! And if yes, I will upload it!
OK, I think I weren't clear. Can I port a 32A 6.35 to 32B?
Artifex14 said:
OK, I think I weren't clear. Can I port a 32A 6.35 to 32B?
Click to expand...
Click to collapse
only if you change a bunch of things and move apps around in the build usually
6.35 radio is nearly identical to porting from hero as it is very easy to port to 6.35 radio - would reccomend you just port from hero roms because it would be the same effort with more work having been done on hero
OK, just one question more. Can I flash the 6.35 radio? "only if you change a bunch of things" ??, and which kernel can I use?
Thank you
OK, just a thing... don't use the "--base 0x19200000" parameter..., because otherwise, the ROM won't boot!!
Apparently it boot!!! This ROM!!
I say you latter
Hi,
I'm going to try an alternative approach to Richard's (excellent) kernel, by porting across the HTC patches to the 2.6.32.9 kernel.
I presume, first of all, that there is a Froyo branch of this kernel (although it doesn't seem to be public in GIT yet), though it would be useful if I could get hold of this as a starting point.
What source are people using as a baseline for the N1 kernel mods?
Help appreciated.
Thanks
Martin
try searching for kernels
[DEV] Desire 2.6.32.9 kernel [25/06/10]
just wondering if any kernels are incorporating the fact that the new htc kernel source makes more system ram available...havnt seen it yet and dont know why
Hello everyone,
I'm trying to compile my own source ROM for my Sensation 4g (TMOUS) My HBoot is 1.17.000 revolutionary unlocked. My compile from google source gingerbread 2.3.4 (to match version htc is using) went ok however with no lunch or envsetup option for the Sensation my full-user make showed compiling for generic. I have tried fastboot flashing my compiled userdata and system img files to my phone along with my default sense kernel (kernel from TMOUS rom 1.5 made from clockwork recovery) to find that it doesn't get past the white htc screen. I'm interested in compiling and sharing this ROM with the public however finding I'm a little lost on next steps.
In the court of public opinion, what would my next steps be? Is my lack of booting due to the sense kernel and instead should I try using a kernel like trinity cm7/asop kernel? Is my lack of booting even kernel related?
Any advice I would greatly appreciated and once I can get this thing running I will be glad to give credit where due and distribute any modified files. Also, if I run across any additional information that might help anyone I will update this post.
PS - I know ICS is out and it might seem odd to try with gingerbread to start (along with using 2.3.4 instead of 2.3.7) however my rationale is that by trying to stay as close to the gingerbread rom HTC provides version wise I might have the best shot at compatibility.
Thanks everyone.
Various ROM developers have IRC channels. It might be worthwhile trying and asking a developer on there, just don't bug them too much.