Database Info

Rogers, heres your real root

---
hyeprofile requested i link to his rooting for dummies guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
---
edit: almost forgot to include the gr33tz! D:
this hack brought to you by dream_kill, and myself.
---
edit: for those of you that don't know how to get to SPL 1.33.2005 i recommend reading here: http://forum.xda-developers.com/showthread.php?t=532224 (under Rooting Rogers).
---
(note: this is for the dream, the method works for the magic you just need to flash a magic compatible recovery.img)
This requires that you use SPL 1.33.2005. (this is safe on all rogers dream devices.)
so if you don't have that already, go get it here.
once you are at SPL 1.33.2005 (AND ONLY THEN)
download this
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
extract both images wherever you'd like.
IMPORTANT: make sure you have the rom you'd like to install in the root of your sd card as update.zip (YOU WILL NOT HAVE A ROM INSTALLED AFTER YOU COMPLETE THE FOLLOWING STEPS, YOU WILL HAVE TO USE THE UPDATE.ZIP TO GET ONE)
boot into spl and fastboot (power off, hold camera button, power on, press the back arrow to get into "fastboot" mode)
type in the following:
Code:
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
POWER OFF (not reboot, power it off) THE DEVICE. (you can do this using the corresponding button [it says it on the screen] or just pull the battery [make sure everything is done flashing of course])
(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)
now hold down the HOME button and power it on, you should boot into recovery mode now, go ahead and ALT+S to flash your rom, and enjoy! now you can flash anything you see in the forums
EDIT:
So i noticed people were talking about reverting back (not sure why you'd want to )
Regardless, heres the original radio (3.22.20.17) and the original recovery (WARNING: UNROOTED) from rogers dream:
http://www.stevebirstok.com/android/losemyroot.zip
Code:
fastboot flash radio rogersradio.img
fastboot flash recovery rogersrecovery.img
fastboot erase system -w
and flash the update.zip found somewhere on this forum ;P
EDIT 2:
as far as this ram / memory loss goes:
C:\Users\haykuro\Desktop>sha1sum radiog1.img radioion.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radiog1.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radioion.img
radiog1.img is the radio.img i provide in the givemeroot.zip, radioion.img is straight off here there are no specific radios between 32A and 32B boards, so that isn't why you're losing memory. i'm trying to figure it out, so if anyones willing to do some testing and post results, please do so.

nice! a whole new crop of modders inbound
cheers

Trying this right away .. no words ... thanks again H !!
EDIT: well not RIGHT away ... need a rom lol

newbie question................Will this fix the iptables issue to allow for tethering?

Thanks alot, this is awesome, Will I be able to flash 32b roms onto my 32a rogers magic? Anything goes??

RezaREX said:
newbie question................Will this fix the iptables issue to allow for tethering?
Click to expand...
Click to collapse
I believe the ROM image contains everything including kernel. So if the kernel in the ROM is IPtables enabled ... you bet

Awesome job Hay!
Now... What is that radio and where does it come from? Will I still be able to get HDSPA on Rogers Bands with this?

Thanks haykuro.
Anything is good as long as it expands the android community on XDA.
Let's go Roger developers!

and I sold mine for a us g1 haha!"now I feel like an idiot" good Job Haykuro!
what else you releasing today"I now you have something special sitting on your desktop"

Drizzy Drake Rogers said:
and I sold mine for a us g1 haha!"now I feel like an idiot" good Job Haykuro!
what else you releasing today"I now you have something special sitting on your desktop"
Click to expand...
Click to collapse
Oooh I love a good mystery.....

Sounds pretty exciting for our fellow rogers dream owners. Haykuro, have you thought about rooting myTouch yet? Or will this work on myTouch as well?

Now that us lowly Rogers Dream owners are able to flash ROMs, does anyone have any suggestions for a good ROM to flash? I'm thinking something Hero ...

RezaREX said:
newbie question................Will this fix the iptables issue to allow for tethering?
Click to expand...
Click to collapse
yes.
rajeevsudra said:
Thanks alot, this is awesome, Will I be able to flash 32b roms onto my 32a rogers magic? Anything goes??
Click to expand...
Click to collapse
yes.
hellfenix said:
Awesome job Hay!
Now... What is that radio and where does it come from? Will I still be able to get HDSPA on Rogers Bands with this?
Click to expand...
Click to collapse
the radio is 2.22.19.26I (comes with all the new g1 roms, came with the ION, and with some other devices.) and it should have 0 effect on HSDPA or bands (that's at a hardware level and has to do with the crystals on your phone )

jackkerouac said:
Now that us lowly Rogers Dream owners are able to flash ROMs, does anyone have any suggestions for a good ROM to flash? I'm thinking something Hero ...
Click to expand...
Click to collapse
Hero for eye candy, cyan for performance, cyan with hero theme for a good mix of both

I forgot to say thank you! So, THANK YOU!

Success
First of all, Haykuro, thank you for all your work (and those that helped you), this is excellent!
I have just completed all the necessary steps from H's first post. Worked like a breeze, I am up and running now. If only I knew we would get access to new ROMS this early, I would have started downloading them a few days ago.
Haven't had time to test everything yet, I randomly downloaded JackHeroV1.0, and it loaded no problem.
Good luck to all on Rogers, this should bring some new life to our phones now.

Great stuff indeed! Has anyone tried this on a 32a magic ?

Thanks for the awesome work haykuro and dream_kill. I can't wait to try this out tonight.

This is awesome, you guys rock! I can't wait until I get home to flash some cyongen-y goodness on my Dream

This is unbelievable haykuro.
Not only did you give us the ability to do custom ROMs ... they don't need to have special mods.
I always expected that every time a new ROM came out we would need someone to do some kernel hacks to make it Rogers compatible.
Great job.

New Rogers Root

Haven't seen this over here yet so thought i'd post it.
Seems The Rogers guys don't have to pick and choose any more for ROMs.
Heres the good news.
Clinton

I can confirm it works, but you need to use a 32B (Google) branded recovery, otherwise it gets all screwy.

Wow, that's fantastic news! Going to really open up what we can put on our phones.

just to clarify, haykuro has made it so we can flash 32B or 32A roms on a 32A magic?
Can we also flash Dream roms or would that be fubar due to the keyboard/radio?
Cheers,
Frank

Will this work on a 32A HTC Magic??

Just a note, in case people are wondering, 32A roms will no longer work with your phone after doing this.

So, it means after flash this radio, my 32A machine seems become 32B ?? I am update my original 32A rom, I think I need to reinstall rom after this... Thanks a lot...

skittleguy said:
Just a note, in case people are wondering, 32A roms will no longer work with your phone after doing this.
Click to expand...
Click to collapse
I have a 32A Magic & am considering doing this. I thought you could use both 32A & 32B roms, but if not why would I want to do it? Does 32B have more/better ROMs?

The new radio doesn't have the boot offsets that are present in the original Rogers radio, and as a result the 32A roms don't work. The main benefit of doing this, is that the majority of roms released are for 32B Magics (which is what most people seem to be devving for) so as a result you don't need to wait for ports in order to enjoy the new roms. If you're perfectly comfortable with your current rom, or would rather just port the roms yourself, then you don't need to root.

skittleguy: So it becomes a 32B with 288MB of RAM? Also, do you happen to know how to backup the radio? I'd like to be able to restore to stock should the need arise . Thank you!

daandman said:
I have a 32A Magic & am considering doing this. I thought you could use both 32A & 32B roms, but if not why would I want to do it? Does 32B have more/better ROMs?
Click to expand...
Click to collapse
32B have all the ROM's out for Dream with slight modification...

Wysie said:
skittleguy: So it becomes a 32B with 288MB of RAM? Also, do you happen to know how to backup the radio? I'd like to be able to restore to stock should the need arise . Thank you!
Click to expand...
Click to collapse
If I knew how to I would
And yeah, it essentially becomes a 32B with more memory, so all the optimizations that were made make the roms crazy fast.

The only thing stopping me now is the lack of a radio backup . I'd love to be able to switch it back to a 32A if possible.

Wow. Interesting. Thanks for taking the time to answer these questions skittleguy. And your Roger's ROMS repo thread is awesome!

One more thing, does this mean we can run the Dream ROMs as well (instead of the usual 32B ported ROMs)?

Wysie said:
One more thing, does this mean we can run the Dream ROMs as well (instead of the usual 32B ported ROMs)?
Click to expand...
Click to collapse
They still require porting, probably due to the boot.img-kernel being different between the Dream and Magic.

skittleguy said:
They still require porting, probably due to the boot.img-kernel being different between the Dream and Magic.
Click to expand...
Click to collapse
Nope, the kernel is the same...
All that changes is the file in boot.img init.trout.rc gets renamed init.sapphire.rc and everything (wifi/bluetooth etc) works perfectly. i think the file is the hardware setup file and luckily the dream and magic are the same hardware, different case and keyboard

dazcox5181 said:
Nope, the kernel is the same...
All that changes is the file in boot.img init.trout.rc gets renamed init.sapphire.rc and everything (wifi/bluetooth etc) works perfectly. i think the file is the hardware setup file and luckily the dream and magic are the same hardware, different case and keyboard
Click to expand...
Click to collapse
Hmmm...the Dream rom I flashed didn't work. I think I need to try something...

skittleguy said:
Hmmm...the Dream rom I flashed didn't work. I think I need to try something...
Click to expand...
Click to collapse
with 32A or B? If 32A need the wlan.ko and maybe wpa_supplicant to go with it
32B works perfect for me
(unzip rom, unpack boot, rename file, repack boot, rezip, sign, flash )

Ok it works now. Patience and repairing the ext filesystem seem to have done the trick.

MT3G now rooted, What now?

just wondering, now that the MyTouch 3G is rooted, what ROMS(If any) currently work, or are we going to need to wait for some compatible ones to be made?
Thanks!
I will edit with a current list of what ROMS do and don't work with the MyTouch as word comes in...
Current ROMS reported to work:
fatalitys hero rom
cyanogens
Qtek Hero (Works very very well for me.)

This thread could be a good starting point for roms that have been tested on the MT3G. I think I read that one of the Cyanogen roms was installed. I'm interested in getting more HTC software on it (read; HTC Sync).

ive tried fatalitys hero rom, and cyanogens, and both work fine on my rooted MT3G

sounds like a great idea!
yeah, we MyTouch owners need to know whats next for us! If theres any good starting point for determining what current roms will work, this thread should try to help out with that.....
Now, i have a 32B board, so is it safe to say the magic 32B ROMS are fine for it? or is there enough of a difference to where it wont work?
From what I understand(which is not much, mind you) the only difference between the 32B Magics and the newer MyTouch was the SPL. With that now not an issue, shouldn't the current ROMS work, or am i wrong?

dills84 said:
ive tried fatalitys hero rom, and cyanogens, and both work fine on my rooted MT3G
Click to expand...
Click to collapse
how well is the hero? slow, or not too bad?

ChaoticEko said:
yeah, we MyTouch owners need to know whats next for us! If theres any good starting point for determining what current roms will work, this thread should try to help out with that.....
Now, i have a 32B board, so is it safe to say the magic 32B ROMS are fine for it? or is there enough of a difference to where it wont work?
From what I understand(which is not much, mind you) the only difference between the 32B Magics and the newer MyTouch was the SPL. With that now not an issue, shouldn't the current ROMS work, or am i wrong?
Click to expand...
Click to collapse
Hi,
I just flashed back the original mytouch rom for my brothers mytouch and everything is well with root access.

ttran001 said:
Hi,
I just flashed back the original mytouch rom for my brothers mytouch and everything is well with root access.
Click to expand...
Click to collapse
Where is the original myTouch ROM? i've been digging for it so i can root my phone and be able to go back if i goof it up.
Also what do you mean everything is well with root access after flashing the original myTouch ROM?? shouldn't the root go away when you reflash the OEM ROM.

flamingblue8z said:
Where is the original myTouch ROM? i've been digging for it so i can root my phone and be able to go back if i goof it up.
Also what do you mean everything is well with root access after flashing the original myTouch ROM?? shouldn't the root go away when you reflash the OEM ROM.
Click to expand...
Click to collapse
Here is the original link:
MyTouch Rom Thread
I'm only flashing the update.zip file and so I'm only flashing the OS part.
So the SPL, Radio, and etc stay the same.
Now I'm going to strip it down for him and see if it runs better.
Also, don't forget to wip the system befor flashing the new rom.

Cool I downloaded that one earlier. Have a friend making me a gold card to root with. Now where can I get the original SPL? I read that the ION radio is the same as the myTouch, is that right?

Are you guys flashing back to the 32b radio before you flash 32b roms , or you going straight after getting root to flashing roms ?

fivestar0234 said:
Are you guys flashing back to the 32b radio before you flash 32b roms , or you going straight after getting root to flashing roms ?
Click to expand...
Click to collapse
I installed 1 32A rom before flashing the radio and jumping on the 32B bandwagon. All was fine either way.

Question, I just finished rooting my mytouch, I have done all the steps except for the 'daredevil' portion which reverts to the 32b I think.
From my current position what roms can I use? and if I do the 'daredevil' approch what can i use?
Thank you.

Mi|enko said:
I installed 1 32A rom before flashing the radio and jumping on the 32B bandwagon. All was fine either way.
Click to expand...
Click to collapse
So just to clarify , I can flash 32a roms now on my rooted mytouch, and when I want to go to 32b roms just flash the radio and 32b Rom correct ? Thanks

fivestar0234 said:
So just to clarify , I can flash 32a roms now on my rooted mytouch, and when I want to go to 32b roms just flash the radio and 32b Rom correct ? Thanks
Click to expand...
Click to collapse
Yup. That's the difference between utilizing the GiveMeRoot.zip or not. Without it 32A, with it 32B. I know you probably got that already, but if anybody else is reading I want to make sure there's no confusion. lol

Cyanogen flashed properly, although the accelerometer isn't working any longer for some reason. I have no idea of the fix, but the one listed in the FAQ is not working. Other than that, it's great.

Awesome thanks !

i tried flashing fatality's hero rom after doing the "basic" 32A root and i get stuck on the vodafone splash screen... i followed all the directions to the T, so no, fatality's rom does not work for everyone... would not recommend trying just yet

Ugh I'm totally lost with 32a vs 32b I mean I understand the memory difference or whatever, but I just want a ROM like what JF did to the G1. The default firmware with the addition of root. Nothing taken out, nothing added in. Except the kernel patched for tethering. Any suggestions? Everything I've seen is heavily modified.
And of course I still want factory images in case of a brick.

motivecc said:
i tried flashing fatality's hero rom after doing the "basic" 32A root and i get stuck on the vodafone splash screen... i followed all the directions to the T, so no, fatality's rom does not work for everyone... would not recommend trying just yet
Click to expand...
Click to collapse
worked for me... but it does take a LONG time to boot.

Mi|enko said:
Yup. That's the difference between utilizing the GiveMeRoot.zip or not. Without it 32A, with it 32B. I know you probably got that already, but if anybody else is reading I want to make sure there's no confusion. lol
Click to expand...
Click to collapse
I would be careful running the 32a stuff on your phone. Even though you have the 32a radio and recovery your phone still has a 32B board in it. I flashed back 32b stuff, prefer not the have a brick. Just an FYI and my .02.

Hero ROM that will work on a EBI1 Dream

A friend of mine purchased a Dream. Even though it has a 32B motherboard, it has the same SPL (1.33.0010) and Radio (3.22.20.17) as my 32A Magic. Since it has the perfected SPL I used the Flashrec program to flash a new recovery image. However all the Amon Ra recovery images for the dream didn't work. Eventually I let Flashrec automatically download a recovery image. It said that the phone was an EBI1/32A and downloaded Cyanogen 1.4.32A recovery image. This recovery image actually worked, so I tried loading a few Hero Roms for the Dream. Unfortunately none would boot.
I've scoured the forums can't really find a solution. This post http://forum.xda-developers.com/showthread.php?t=574561 suggests that a ROM with a 32A kernel is required. Would this mean that 32A magic ROMS would work with an EBI1 Dream? Which ROM should I try?
Also I'm not really keen on changing the SPL or radio as my Magic works perfectly running MyHero 2.0.5 and RAv1.2.1H recovery ROM

ramka said:
A friend of mine purchased a Dream. Even though it has a 32B motherboard, it has the same SPL (1.33.0010) and Radio (3.22.20.17) as my 32A Magic. Since it has the perfected SPL I used the Flashrec program to flash a new recovery image. However all the Amon Ra recovery images for the dream didn't work. Eventually I let Flashrec automatically download a recovery image. It said that the phone was an EBI1/32A and downloaded Cyanogen 1.4.32A recovery image. This recovery image actually worked, so I tried loading a few Hero Roms for the Dream. Unfortunately none would boot.
I've scoured the forums can't really find a solution. This post http://forum.xda-developers.com/showthread.php?t=574561 suggests that a ROM with a 32A kernel is required. Would this mean that 32A magic ROMS would work with an EBI1 Dream? Which ROM should I try?
Also I'm not really keen on changing the SPL or radio as my Magic works perfectly running MyHero 2.0.5 and RAv1.2.1H recovery ROM
Click to expand...
Click to collapse
Questions are best answered in Q&A section, and anyway do you have the danger spl and new radio. You need these to run hero

Oops my bad, perhaps a moderator could move it. It has the perfect SPL and version 3 radio. The exact same ones I have on my Magic which runs a Hero Rom

ramka said:
Oops my bad, perhaps a moderator could move it. It has the perfect SPL and version 3 radio. The exact same ones I have on my Magic which runs a Hero Rom
Click to expand...
Click to collapse
Well the g1 needs the new radio and Danger spl.

JAguirre1231 said:
Well the g1 needs the new radio and Danger spl.
Click to expand...
Click to collapse
Sorry, don't mean to sound rude...but you don't understand the question. He's asking if it will work as-is, since other devices with 32A radio/recovery run Hero ROMs just fine.
To the OP, this is something currently being discussed in the following thread:
http://forum.xda-developers.com/showthread.php?t=581165
I'd suggest reading up on that thread to see what progress they've made with getting ROMs to boot on a 32B Dream with 32A recovery/radio. Hopefully that will help you out!

TemporalShadows said:
Sorry, don't mean to sound rude...but you don't understand the question. He's asking if it will work as-is, since other devices with 32A radio/recovery run Hero ROMs just fine.
To the OP, this is something currently being discussed in the following thread:
http://forum.xda-developers.com/showthread.php?t=581165
I'd suggest reading up on that thread to see what progress they've made with getting ROMs to boot on a 32B Dream with 32A recovery/radio. Hopefully that will help you out!
Click to expand...
Click to collapse
It's ok always open to corrections

I would recommend trying a kernel and 32B ROM combination in this thread:
http://forum.xda-developers.com/showthread.php?t=564949

myTouch 3G 32b Official OTA Froyo 2.2 link provided - next stage for us?

Sorry if this is already being discussed in our G1 forums, had a look but one thread created was closed (therefore hope I'm not doing something I shouldn't be by opening this one, apologies if so!)
I found the link for an untouched OTA Froyo update for the myTouch 3G:
http://android.clients.google.com/packages/ota/tmobile_opal/e059adc603a3.signed-opal-ota-60505.e059adc6.zip
I read the forum over there and they talk of perhaps needing another file, as the update supposingly comes in 2 parts. Is it the case that we need a different radio/spl etc? What is the next step for us?
Hopefully one of our genius developers can get this working and ready to flash on our G1's, an official Froyo!

Wohoo!
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?

AdrianK said:
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?
Click to expand...
Click to collapse
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!

cd993 said:
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!
Click to expand...
Click to collapse
Im guessing they are either working on it now or we are the only ones home on a sunday afternoon lol

All the magic (pun intended) seems to be going on in this thread.

From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.

I'm really excited bout this...perhaps recompiled with latest nightly CM kernel could work....!!!

ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
ezterry, join us here http://www.stinto.net/pages/chat.htm?id=4hlqu
and anyone else who wants to/is knowledgable

ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
one point of your thing here is wrong. i don't know about the others, they're probably right knowing you.
In the chatroom i posted, I successfully booted this ota with a cm kernel. duh.
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.

jcarrz1 said:
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.
Click to expand...
Click to collapse
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)

we need a working sense ui 2.2 rom with bluetooth and touch focus

ezterry said:
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)
Click to expand...
Click to collapse
that's it?? and then the tmobile kernel will work on a g1?

XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
I guess i heared theat somwhere...:-D
sorry for OT...

jcarrz1 said:
that's it?? and then the tmobile kernel will work on a g1?
Click to expand...
Click to collapse
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.

so what do i have to download and what do i have to do with it, to run it on my G1?

ezterry said:
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.
Click to expand...
Click to collapse
I agree on that speculation... you mean you haven't tried it yet? i thought you did...

jcarrz1 said:
I agree on that speculation... you mean you haven't tried it yet? i thought you did...
Click to expand...
Click to collapse
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root

woot, thank you!

XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
No we don't.

ezterry said:
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root
Click to expand...
Click to collapse
is there any improvement on memory/memory management with this change?