yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] asb123:
when it says you need 2.xx radio, it is usually false, what it should say is that you need the latest radio (ebi1 works)

you dont need to change anything to work a 2.1 ROM, just follow the instructions in the original post, if you do not yet have amon's recovery, follow the post above this.

p.s. I dont think you can change the radio now that you have flashed your SPL, it will BRICK yor phone.
[G1 Android Development] asb123:
well, the only reason they focus in the sapphire section is because nobody took charge and made a EBI1 thread in the g1 section, we could always use "supported roms" we just needed kernels.
[G1 Android Development] Macmee:
Ok. What about SPL, will the one from the cyanogen tut work?
[G1 Android Development] asb123:
yeah, follow that guide for your SPL, if you have root i think you can just skip the first part (as its about getting root, if i remember correctly)
[G1 Android Development] Macmee:
erm. Follow what guide?
[G1 Android Development] asb123:
once you have root and have amon's recovery,

go here:

http://wiki.cyanogenmod.com/index.p...ers_Dream_EBI1_to_CyanogenMod#SPL_Replacement

skip down to the SPL replacement part to get the 1.33.2005 SPL
[G1 Android Development] Macmee:
Oh I already have that. And the recovery, is that an essential? I already have the one from cyan.

I read somewhere that if I flash a rom before a radio then it bricks me, something like that, do I have to be concerned about that?
[G1 Android Development] asb123:
you are a bit mixed up, what the major rule is:

You cannot flash a different RADIO after flashing your SPL. This WILL brick your phone.

Roms are fairly safe, but there is always a slight chance of error, most of the time if there is a problem when flashing a rom, a nandroid backup will fix it up.

And yes the amon recovery is essential, itis the best and is great if you have EBI1 (because you need to flash multiple zip files without a reboot).

Get the amon recovery ("R" version is for EBI1),

once you have that, do a nandroid + ext backup under the "backup" option.

Then go back to the main screen, then to "wipe" wipe rotation settings, factory data, ext, and dalvik.

then flash the ROM you want, then flash the EBI1 kernal (this step is why the amon recovery is great)

On a side note:

if you are going to be running 2.1 you need to have your ext up to ext3, have you already partitioned your ext?
[G1 Android Development] xaueious:
The whole 'community applauds these devs' is really cheesy. It isn't that hard to make the kernel patch. Devs who are releasing roms at all should be appreciated period.

Actually you are wrong. You can change the radio after flashing your SPL as long as you know what you are doing. I've done it enough to know this.

On radio flashing

You can brick your phone flashing the radio if:

1) your radio is not compatible with your spl

2) you do not have a compatible recovery/system installed with the radio you are flashing. In otherwords if you have a working recovery on the EBI0 kernel radio, and you flash to the EBI1 radio without changing your recovery, you have a guaranteed brick

3) if you interrupt the radio update process

Hence, the recommendation is to not flash your radio unless there are definite advantages to doing so for you (such as bypassing the Rogers post 911 device check).

On recovery images

I've only used Amon_RA recovery because I know which one works for EBI0 and which one works for EBI1, and I see no reason to try CM recovery out. I'm not sure if that recovery even works on EBI1.

Edit: CM-1.4 does not work on with the 3.x radio. Just tried to fastboot boot it, and it gets stuck at the Rogers screen. So it is EBI0. So you do need the 1.5.2R Dream recovery if you have the EBI1 kernel radio installed.
[G1 Android Development] Macmee:
Nope, I haven't partitioned yet. Not sure what partitions are required where:p
[G1 Android Development] asb123:
^^ yeah you need the "R" version.

also, thats why it is basically a "rule" not to flash a new radio because odd are that most users WILL make a mistake and have a new paper weight, that is good info though. Do you want me to add that info to the OP?
[G1 Android Development] asb123:
once you get the amon recovery on your phone, it becomes very easy to partition.
[G1 Android Development] Macmee:
I must be going nuts because I only see an "RA" download.
[G1 Android Development] asb123:
http://rapidshare.com/files/320335174/recovery-RA-dream-v1.5.2R.img

notice at the end it is v1.5.2R instead of the one which was ontop of it v1.5.2
[G1 Android Development] Macmee:
I'm downloading it now, thanks. Once recovery is installed how do I partition, will I be able to just hit the partition button?
[G1 Android Development] asb123:
you are going to see an option called partition or format or somthing similar, you then partition it (you will lose all data on the card so save anything you want on your computer), then select what sizes of what you want, when it asks for swap size make it 64 or 96/92 for ext i recommend 528

On a side note:

has anyone gotten a kernel for a good hero ROM(which isnt hero eclair) or can tell me how to make one. The reason i ask is because hero is 1.5, when you use magic port, it makes the kernel for a donut rom, this makes the launcher constantly force close.
[G1 Android Development] Macmee:
When I follow the instructions for that custom recovery

Copy recovery-RA-dream-v1.5.2.img to the root of your sdcard

start the terminal app

$su (not required if you have root already)

#mount -a

#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img

when I do mount -a I get

mount: mointing /dev/block/mmcb1k0p2 on /system/sd failed: no such file or directory

mount: mounting /system/modules/modules.sqf on /system/modules failed: no such file or directory

mount: mounting /system/xbin/xbin.sqf on /system/xbin failed: no such file or directory
[G1 Android Development] asb123:
you still need to do su, even if you have root. Do that and try again.
[G1 Android Development] Macmee:
I used fastboot. I got the entire rom working. This is really cool :) thanks for all of your help, I appreciate it :)

the only problem I have is I get a force close on the camera every several minutes
[G1 Android Development] asb123:
Yeah, the 2.1 ROMs have problems with video and stuff (sometimes camera)

Make sure you are making nandorid+ext backups before flashing ROMs incase something goes bad.
[G1 Android Development] MasterOSX:
Good post,tnx for all the explanations.

One question. If I want to make my own porting I need the kernel source, but except cyanogen, do you have the link of the other repositories (KK, etc)??

Tnx
[G1 Android Development] asb123:
I am not sure about how to port kernels without the tool which are not cyanogen. Perhaps someone else shall know. Or you can ask brian crook in his thread.
[G1 Android Development] :
First thing I want to say is this is an awesome and much needed thread. Thank you for taking the initiative.

There is a lot amount of information out on xda regarding flashing recovery files, upgrading / downgrading your radio, flashing boot loaders, 32A port files and of course flashing ROMs. It's nice to see that information compiled in one post now.

What is missing big time IMHO is information about ROM compatibility with the new radio 6.35.10.18.

In particular, it is clear how to (1) flash a 32B ROM on a 32A phone and (2) create and flash a 32A port file on a 32A phone (for a 32B ROM). It would be HUGE if someone could provide a guide or steps on how to make the necessary changes so that a ROM for an old 3.x radio can be modified to run on a 32A phone with the new radio 6.35.10.18.

If someone can step up it would be greatly appreciated.
[G1 Android Development] asb123:
that would be great and i would add that information into the op for sure (with credit of course)

Unfortunately I myself am not very knowledgeable about the new radio as it is not for the dream only the magic. Hopefully someone comes around this thread with the answer for your question!
[G1 Android Development] Macmee:
Now all we need is a super super fast 1.6 rom and we're set for life.

edit: super d, but I can't find the ebi1 port for 1.9.2. Damnit
[G1 Android Development] carz12:
Really? you search?

http://xdaforums.com/showthread.php?t=633780
[G1 Android Development] Macmee:
I guess I'm just incredibly stupid to miss something that obvious. Thank you :)
[G1 Android Development] carz12:
You are welcome, runs great too.
[G1 Android Development] Sumanitu:
Why would having the wrong recovery brick your phone? Am I wrong in thinking you can just hold camera + power to go into the SPL, then use fastboot to flash the proper recovery image?

Sure you can't use the recovery to save your phone, but you should still be able to save it with fastboot as the SPL is loaded before the recovery image.
[G1 Android Development] asb123:
perhaps, i am not sure and added that based on what the other user said:o
[G1 Android Development] surfwaimea:
boot.img

It's great to have a Dream thread to remind devs that their ROMs could be used by EBI1 people with just a patch... Thanks @asb123 ;)

I think that some things should be added to the info given here. One is what should be different in ROMs to make them EBI1 compliant. In particular, beside of wlan.ko, what should be changed in boot.img?
[G1 Android Development] asb123:
uhh, yeah theres 2 things one is the wlan (wifi) the other i remember reading just the other day :eek:

does anyone remember what the other is?
[G1 Android Development] ottawanate:
CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1 is the only difference between Dream/32B Magic and Rogers Dream/32A Magic kernels.

minimum requirements for porting a ROM to EBI1 are

1) wlan.ko patch or wifi wont work

2) boot.img with Kernel config file marked for CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y
[G1 Android Development] Zoltair Wright:
1) Speed was okay, not amazing. I wanted to try this 2.0 ROM since it said video was working. Video worked sort of but I couldn't get video recording to work.

2) King Klick was nice enough to post a version of the kernel without the RAM hack. So I took that kernel (the one without the RAM hack) and then used Faruq's tool on it. I went into Amon_RA's 1.5.2R and flashed the ROM and then the kernel that Faruq's tool produced. And it worked! But I don't have the RAM hack because the kernel I modified doesn't have it.

I should note, I've moved on to the Super D 1.9.2 ROM because it has a kernel posted here that we can use on our EBI1 Dreams. I like this better because it has the 10 mb RAM hack built-in, and everything works. The only thing I miss is the neat lock screen, but oh well. It's very, very fast.
[G1 Android Development] asb123:
you used the tool on the kernel not the rom?
[G1 Android Development] ruqqq:
can anyone verify if the screenshots on that port thread is from the rom port/rom itself? if so, the kernel the port is using cm42 - cyanogen kernel compiled by me. no, it doesn't have the 10 mb RAM hack. ;)
[G1 Android Development] asb123:
I dont think we can have the ram hack, can we? because that kernal is replaced in the porting?
[G1 Android Development] :
The dev of the MAGIC Port is adding a lot of features for his next release including a radio port for new radio, support for more kernels, etc.

http://xdaforums.com/showthread.php?t=601033
[G1 Android Development] asb123:
sweet, he said it should hit any moment now. Hopefully it has the ability to patch 1.5 (hero) roms
[G1 Android Development] Zoltair Wright:
That's right, I used Faruq's tool on the kernel, not the ROM. In the instructions it tells you to upload only a boot.img.

Fair enough. SuperD is still faster than anything I've tried before, though, so you must be doing something right. ;)

Is that how it works? I assumed since the RAM hack was listed in the port, that it would apply to the "old radio" version as well. Is it possible to apply the RAM hack to a EBI1 ported ROM? Or not?
[G1 Android Development] asb123:
I have been porting ROMs differently than you, your method seems very interesting.

What I have been doing is extracting the boot.img from the ROM zip itself and running that in the tool.

You have been extracting the boot.img from the kernel used with the ROM and running that in the tool.

With the method i have been using there is no chance of any original kernel remaining. With your method i am wondering if any parts of the original kernel remain?
[G1 Android Development] ruqqq:
I believe both of you are using the right way. Haha. Don't worry about it.

The kernel is extracted from boot.img and no way parts of it is retain when porting. The kernel is just one file. 10MB Ram hack doesnt matter on EBI1 because of the ram size we already have. A port of the code for the Ram hack should be possible but it's pretty waste. We should have enough for both normal apps and GPU accelerated apps.

And btw, I don't mind people not giving me credit, but they shouldn't anyhow state information such as "using latest cm kernel source" because it's misleading to the community. The cm42 kernel which i compiled, by today, should be very outdated already. the person taking the credit should change that piece of information.
[G1 Android Development] beav_35:
The ram hack would be useful for dream users with an EBI1 radio. If no one does it first, I might try building one my self.
[G1 Android Development] asb123:
I'm not sure if you are referencing to me but I have now added your name into the OP:o

Arctu, he is right, the 10Mb ram hack may not be of much use to EBI1 magic/mt3g users, but it IS usful to EBI1 dream users because our phones are 32b ebi1 we dont have extra Ram.

Please reply to confirm that you now know this and may consider it!
[G1 Android Development] ruqqq:
@asb123

i wasn't referring to you. was referring to the superd port - http://xdaforums.com/showthread.php?t=633780

see the Kernel Version screenshot (root@thor-localserver). just take a note that it's not the latest cm source.

in regards to EBI1 G1, i don't know much the difference between that, and the usual G1. The EBI1 flag changes the start point of the memory area in the kernel and also define the end point and hence as a result, specifying the size to use for the 'ram' and 'gpu'. Isn't Rogers/EBI1 G1 256MB ram?
[G1 Android Development] xaueious:
The Rogers Dream (G1) has the same amount of RAM as the T-Mobile G1.

Hardware wise there is supposedly a missing hardware radio amplifier in the Rogers Dream that prevents it from getting the 1700 MHz band from what I heard, but I have not confirmed this for myself. But as far the firmware and software is concerned the two devices are identical. If a TMobile G1 has a 3.x radio installed they must flash an EBI1 kernel port to boot the phone. This whole EBI1 business isn't very clear even to a few of the devs I asked.

I already put what I understand about this EBI1 option in my post (#2 in this topic).
[G1 Android Development] ruqqq:
i see. thanks for the info. will need to do more research on G1 EBI1.
[G1 Android Development] asb123:
yeah, our hardware has no benifits, unlike the whole mt3g situation, this is why it would be great if you could figure out how to keep/get a 10MB ram hack going for us.
[G1 Android Development] drawz:
So why not just convert over to EBI0 and use any ROM you want?

I bought a used Rogers Dream that already had EBI0 and it seems to work great with AT&T 3G or EDGE. Speedtest shows the same speeds as on my iPhone 3G.
[G1 Android Development] asb123:
realisticaly, I dont use 3g or anything so there is nothing stopping me except for the fact that I have no idea how to, does anyone have a link?

Once problem would be the precautions behind first flashing my spl (danger) then now flashing a different radio.
[G1 Android Development] asb123:
with the help of forum member xaueious i now have my phone running the ebi0 radio. i may not need the ebi1 radio but i kow a lot of you still do, for this reason I hope this thread does not die and I will continue to provide and work towards EBI1 help.
[G1 Android Development] beav_35:
I have built a CyanogenMod EBI1 port with the ram hack. I have tested it on my Rogers dream and it seems to be working without any problems so far. It gives about 8mb extra ram. Let me know how it works for you.

http://hotfile.com/dl/31513041/311dd48/beav_35-4.2.15.1-ebi1-RamHack-signed.zip.html
[G1 Android Development] asb123:
interesting, how you plz explain how you built this?
[G1 Android Development] beav_35:
Its wasn't that hard really. I just built it from cyanogen's source with the patch from daproy's github applied.
[G1 Android Development] xxxchargerxxx:
trying it out

flashed it...seems to work fine...

Pre-flash:

$ adb shell free

total used free shared buffers

Mem: 98956 96788 2168 0 4832

Swap: 56140 27580 28560

Total: 155096 124368 30728

Post flash:

adb shell free

total used free shared buffers

Mem: 107084 105508 1576 0 744

Swap: 58172 6404 51768

Total: 165256 111912 53344

Nice! thx!

M
[G1 Android Development] asb123:
yes in deed, very nice!

this was one of the main reasons left ebi1, but it now seems that we can indeed have the ram hack on ebi1!
[G1 Android Development] drawz:
Anyone have links for converting to and from EBI0 and EBI1?

I'm currently EBI0 on my Rogers HTC Dream (purchased that way) running on AT&T, and considering going back to EBI1 to see if it helps with connectivity issues (data portion of EDGE not consistently working).
[G1 Android Development] asb123:
follow this:

http://wiki.cyanogenmod.com/index.php/Upgrade_Rogers_Dream_Radio

when going back to ebi0 use the ebi0 radio and ebi0 recovery instead

Remember: this is dangerous stuff and you could brick your phone if you don't know what you are doing, I take no responsibility over what you do :o
[G1 Android Development] drawz:
Thanks! Just over the last couple days I've been having issues with EDGE (3G working perfectly). Seems odd since the EDGE frequencies are the same between the Rogers Dream and the T-Mobile G1. I haven't tried the latest T-Mobile G1 radio though. It was working fine before though, so I am a little confused.
[G1 Android Development] carz12:
I'm on the superd 1.9.3 ebi1 port with ramhack, it's nice having my ram back
[G1 Android Development] drawz:
Updated to the 2.22.23.02 radio and EDGE is working again. Maybe a coincidence since I didn't check it immediately before the update. EBI1 will have to wait for the next time I have connectivity problems.
[G1 Android Development] Fallen Spartan:
MOD EDIT - Temporarily made thread sticky to see what response it gets
[G1 Android Development] Jugstah:
Any chance someone can whip up a EBI1 rom of Bluemagic. I asked in its thread but did not get any response. Its supposed to be really fast, eager to try it while I wait for open eclair 2.0! :)
[G1 Android Development] Macmee:
I'm on my hands and knees here asking for help to go from my ebi1 radio to an ebi0 so I can actually flash a rom that doesn't die on my device.
[G1 Android Development] beav_35:
Download:

RA Recovery without the R (http://xdaforums.com/showthread.php?t=566669) - rename to recovery.img

2.22.19.26I Radio (http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip) - extract from zip

update.zip for your rom on sd card

Follow these steps:

boot into fastboot

fastboot flash radio radio.img

fastboot flash recovery recovery.img

boot into recovery

flash the rom again to get rid of the EBI1 port (wipe is not necessary)
[G1 Android Development] asb123:
Why would ebi1 roms die on your device? they are the same rom just with a compatible wlan and such.

could you try explaining what is happening?
[G1 Android Development] Macmee:
Just a hairy situation with Super D. I'm running OpenEclair now. When the 3d comes out I'll switch to an EBI0 radio and use that :)

Wow it's really that easy? I thought I would of had to do something with SPL or something :)
[G1 Android Development] asb123:
just the recovery and radio, they must be fastbooted in and no reboot inbetween.
[G1 Android Development] Jugstah:
beav,

I need the latest rogers radio or they will get all pissy kill my 3g and i'll have to sign their waiver. Why not compile a EBI1 version, its just a flag and a recompile is it not?
[G1 Android Development] beav_35:
EBI1 version of what?
[G1 Android Development] Jugstah:
I had asked for an EBI1/32B of Bluemagic.
[G1 Android Development] beav_35:
Theres a link to an EBI1 port tool in the first post.
[G1 Android Development] Jugstah:
I saw, but won't that just blow away any custom tweaks to the kernel the developer may have made?
[G1 Android Development] beav_35:
Yes, but you need the kernel source to compile the kernel. Try the beta port tool and use the Wes Garner kernel.

http://faruq.yandao.com/magicport/indexBETA.php
[G1 Android Development] domenukk:
Do 32a roms run on EBL1?

If yes, then I have a fix for you :)
[G1 Android Development] Jugstah:
I'm not sure, i was wondering if magic rom's would work but i have not tried. The phone is 32B/EBI1.

Edit: I guess given its the magic port tool they will. I'll give the beta link a try later since it has way more kernels to choose from.
[G1 Android Development] asb123:
32a magic rom are ebi1 so they work with ebi1 g1s
[G1 Android Development] asb123:
Because i am no longer ebi1 i am wondering if you guys can get Overclocking on your phones. Doesnt the OC replace the ebi1 kernel?
[G1 Android Development] beav_35:
You can use the 32A OC kernel from pershoot:

http://droidbasement.com/db-blog/
[G1 Android Development] asb123:
Horray, for those of you with the 911, just incase you didnt know, you can now root your phones!
[G1 Android Development] sharpt71:
@asb123, I just wanted to express my appreciation for your helpful information. Since I tried to follow what [HOW-TO] Compile AOSP Froyo + [ROM] Latest AOSP Froyo for Sapphire did to compile a ROM for myself, I stucked on the compilation of a kernel for Magic 32A for over a month and now it is solved. Thanks!
[G1 Android Development] asb123:
no problem, I am not sure if the tool for making kernels will work with the newer roms though.
[G1 Android Development] ASSMO:
Hey, ive been going on around websites trying to find someway to contact someone to help me. Hope this is the right place. Well i rooted my dream using the universal root. Got Rom Manager and flashed clockwork. Now when i reboot or turn off my phone and hold the home button to try and turn the phone on into recovery. nothing happens but i get stuck at the Rogers Screen. I am just wondering why cant i get in? cus i need to flash the danger spl. But really, I cant without getting into recovery because that adb stuff is hardcore lol. I can get into fastboot though. So i dont understand what to do. I've tried a billion times lol and its not booting into recovery, Any help would be awesome. THANKS!
[G1 Android Development] beav_35:
Your recovery has to be compatable with your radio version. You must have flashed an EBI0 recovery on your phone with an EBI1 radio. I don't think clockwork has an EBI1 version. Download Amon_RA's recovery (The one with the "R") and flash that from fastboot. If you really want to keep the clockwork recovery you could flash an EBI0 radio but if you are with Rogers they won't like that unless you sign their waiver.

http://xdaforums.com/showthread.php?t=566669
[G1 Android Development] asb123:
I pm'ed you, but just reply in this thread.
[G1 Android Development] ASSMO:
Ok sounds good but can someone walk me through how to flash the Amons with Fastboot?? i dont know what im doing once i get into that screen.
[G1 Android Development] ASSMO:
Ok, so i just read your pm and i can get into fastboot. So its not bricked. Hm and you said something about a kernal? lol i dont know **** man. im so beginner its crazy. If you could help me that would be amazing! Thank you!!!
[G1 Android Development] ASSMO:
Anyone help me? lol I'm stranded in the desert. With no food or water lol.