yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] anon1ski:
max, if you can give me a rundown on the "best" way (in your opinion) to try this on my g1 ill give it a go. im getting a cliq next friday so i dont mind THAT MUCH if i screw it up.
[G1 Android Development] Wii60:
http://alldroid.org/viewtopic.php?f=130&t=423

Godspeed.
[G1 Android Development] anon1ski:
yea but from what i believe that is for the 32a. i was asking if there is a better way i should try specifically for the dream/g1.
[G1 Android Development] anon1ski:
i mean i dont even run hero roms honestly , ont find them worth all the hype but i dont give much back to the community so i figured why the hell not lol.
[G1 Android Development] dython:
32b=dream and the hack is flashing 32a radio
[G1 Android Development] Fictionles:
I just tried this. After flashing the 32a radio and the new recovery, it does not get past the G1 screen.

Had to revert. Maybe someone else will have better luck.
[G1 Android Development] dython:
did you reinstalled a hero rom a 32a one?
[G1 Android Development] Fictionles:
It wouldn't even let me get to the new recovery to flash a 32a ROM

I followed these steps Eugene posted. Maybe I missed something. Good news, its recoverable at least:

fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.2.0G.img

- press MENU to power off! (do not reboot)
- hold HOME and POWER to boot into recovery mode
- apply update

EDIT: I'm thinking it didn't quite take the radio image even though it said it did. It still thought it was a Dream 32B instead of 32A.
[G1 Android Development] anon1ski:
i got a bootloop. im pretty sure i followed the post almost to the T twice i tried. sounded good in theory....
[G1 Android Development] anon1ski:
even went to a hero rom (king) prior to instillation just to give it a little more hope.
[G1 Android Development] Cresho:
bootloops are caused by no sd card in the drive or damaged ext3 or what ever. I seen this before.
[G1 Android Development] anon1ski:
uhhhhh........ WTF!?
[G1 Android Development] Wii60:
If you're rocking Cyanogen's recovery repair the ext filesystems and retry. Thanks for taking the plunge too!
[G1 Android Development] anon1ski:
no i was just wondering if he had read what we were talking about at all before posting that lol.

and i always repair when wiping AND flashing just to start fresh.

how bout clearing EVERYTHING in general. wiping ext, dalvik, wipe, everything. can some one tell me how to clear dalvik NOT on sd from console?

maybe starting from a fresh everything will give it a hand
[G1 Android Development] eugene373:
You Have to Pulle the Battery, Hold down Home key while putting the Battery back into the Phone to Boot into recovery.

My MyTouch 3G Does this. Not sure Why, but this Method worked for me in oder to flash the 32a Rom. Now I have working BT.

Also, It's Going to say 32B still in Fastboot, all your Doing is Changing the Radio & Recovery.
[G1 Android Development] Fictionles:
Hmmmm....I turned it off via the menu key, then did the Home/Power key to try recovery.

Didn't try it your way. I'll give it a shot.

EDIT - No luck for me a second time.
[G1 Android Development] eugene373:
Give me about 30 minutes and I'll have a Rom for you guys to try that is getting boot loops
[G1 Android Development] eugene373:
Yeah Could have Been a Bad Flash then.

Might Pull battery and Try the Home + Red Button, Just trying to Help.

Are you able to get into Fastboot?
[G1 Android Development] eugene373:
Uploading a Rom for you to try Now.

You are Running the New Radio Correct? Just want to clarify that you was able to flash and get into recovery.
[G1 Android Development] Fictionles:
I can get to fastboot and flash both the radio and recovery. Both present a progress bar and both say they are successful.

Hitting menu to shut down and then home and power to recovery results in hanging at the TMO G1 screen.

Pulling the battery and plugging it back in still requires me to hit home and power for recovery. Same result.

Your download came with the H revision instead of Ra's recovery instead of the G revision. Is there a difference?
[G1 Android Development] eugene373:
Yeah the H version is Built for 32a Radio, if you didn't flash the H version then this is the Problem.

Or, If you did Flash the H version, you Might try the G Version, but I doun't think it will work then.
[G1 Android Development] Fictionles:
I did use the H version unfortunately...
[G1 Android Development] Wii60:
Damn.

We really need a new phone guys...
[G1 Android Development] anon1ski:
can you guys tell me how to clear dalvik not on sd anyway, i think i should probably clear it and RA's rcovery only does it on sd.
[G1 Android Development] holysmokesbatty:
mount -o rw,remount -t yaffs2 /dev/block/mtdblk3 /system
rm /system/dalvik-cache

I know, I know, first post, blahblah...

At least I think that's how it runs, but it's been EONS since I've run Dalvik internally.

Someone please correct (not flame) me if I've screw up the code somewhere.
[G1 Android Development] B-man007:
Dalvik-cache is on the data partition im pretty sure
[G1 Android Development] maxisma:
It worked on my 32B Magic, followed these steps:

http://xdaforums.com/showpost.php?p=4893724&postcount=18

Any G1 user please try these steps too.
[G1 Android Development] unchainedrssr:
If this works for the Dream, someone should post the steps (that worked) and all required links for eager noobs like me!
[G1 Android Development] jubeh:
I'm all for trying new things... but flashing the radio with a different device's?... Last time I checked, doesn't the radio call on the SPL? And with a bad radio unable to call the SPL, no way to flash the radio back? I mean, if it works, then we should be able to flash a 32a SPL too (since the 32a radio can start it) and maybe have a larger system and userdata, but I'll wait for you guys to try it out :D. Sounds interesting though (I could careless about Hero or BT, I want more space in /system and /data, less in /cache)
[G1 Android Development] pbaird:
I wouldn't do that.... I'm sure this is a 32b magic solution only.
[G1 Android Development] maxisma:
Yes, but at least Haykuros SPL (which is required for Hero) is compatible with it, as it's just a Magic SPL.
[G1 Android Development] Geniusdog254:
All of this will flash fine, this just installs an EBI1 radio (think Rogers Dream) and an EBI1 recovery. I have done it on my ADP1 and my Rogers Dream but haven't had a chance to try bluetooth with it yet on Hero. However for some reason I can't make the recovery image boot with it.

I had already had a 32a rom installed on my Rogers Dream so I can still boot it. I don't know why the Amon_RA recovery doesn't work (Yes I'm using the H version), but here is a copy of the old CM recovery ported for 32A that works fine.

Also: to Amon_RA, I love your recovery image, but do you have any ideas why even the H version won't boot on an EBI1 Radio on a Dream device? Are you using the old hacked kernel locations or the true EBI1 support HTC released with their source?

EDIT: Attachment didn't work. Here is a 4Shared Link
[G1 Android Development] Cresho:
I need to understand a few things here first and if anybody can kindly answer these questions. This will most likely help others as well who are newbs like me.

I have a t mobile g1 with king k rom 2.2. It is overall the best rom in performance including video, gaming and also regular usage. The other ones are much faster or the rossie is faster but for video or gaming, sucks.

anyway, here are my questions. I would like bluetooth:

1. does a working bluetooth allow bluetooth headphones, or bluetooth speakers to work properly with a g1 besides the earpiece? I have a bluetooth stereo system and would like access to my phone instead of burning cd rw since my microsd card is much bigger than 8gb,

2. what's a 32a and a 32b?

3. any working tutorials to get this working on a g1 with king k rom?
[G1 Android Development] JAguirre1231:
The only answer I know is to #2 :o

32a is the original magic, with more ram, it has 288?

32b is the MT3G, with less ram, 192?

The 32a is sold everywhere BUT in the U.S., where we have the crippled, slower version
[G1 Android Development] Fictionles:
Ahhh....this could've been my problem last night. Both would flash successfully, but could not boot to recovery.
[G1 Android Development] Geniusdog254:
That probably is why. I just updated my earlier post because I forgot to upload the CM 1.4 EBI1 recovery. I just now got it uploaded & I know that this recovery image boots fine on EBI1, so just flash it and please try BT, I don't have time atm to flash a Hero ROM but everything should work in theory with this recovery & a Hero rom.

EDIT: Well the attachment didn't work for some reason. Here is a 4Shared Link And to the OP, it would be REALLY nice if you could post this link in the first post (http://www.4shared.com/file/148141897/b3ee999c/cm_recovery.html) so that people can get a working recovery image and this can actually work ;) *not meant to sound sarcastic or rude lol*
[G1 Android Development] Fictionles:
That CM_Recovery worked!

Flashing a 32A rom now.

EDIT - Attempting a boot.
[G1 Android Development] afbcamaro:
The CM recovery definately worked, however I cannot get a succesfull boot out of any of the roms. I was using ext2 partition. It may be the problem... dont know..
[G1 Android Development] Fictionles:
The console option doesn't work from recovery. Nor does my adb work.

It picks up the drivers, so that's a good thing. Trying to reflash again.
[G1 Android Development] Geniusdog254:
OK I've been experimenting. This is weird, none of the 32A hero ROMs boot, however the 32a port of CM 4.3.2.1 runs fine. The CM recovery runs fine, however Amon_RAs doesn't.

It probably has something to do with the way the kernel is configured. What we need to do is figure out what memory offsets they are using. The Dream/32B Magic use one set, and when we flash this we use the Rogers Dream/32A offsets. I couldn't give you the address of the offsets but I do know that in the beginning of custom Magic kernels they used hacked memory offset addresses because they didn't have kernel source. See (http://xdaforums.com/showthread.php?t=548061) for info on the differences between the hacked offsets and the real offsets. The main difference seems to be:

I think that if the kernels are compiled using the hacked offsets they fail to load on our devices. Can someone contact one of the chefs and see if they can whip us up a boot.img using the proper MSM_EBI_SMI32_256MB_SIZE config in the kernel if they aren't already.

This is probably what is causing it since the 32A CM port runs fine and I KNOW that in the post it says that it uses that config in the kernel.

Also, ADB works for me, but it is known that the terminal from recovery fails. This is because normally there is a terminal buffer bank in RAM and with this radio it is in a different address or non-existant.
[G1 Android Development] Cresho:
IM GONA..OOPSX damn caps. im gona flash this recovery on the king k rom currently being used. then illl start updating as. backing up everything right now.

do as he says..reflash. I had problems flashing a third g1 phone. for some reason, it was stubourn with a cyanogen rom but after the 4th try, its fine.

reflash!
[G1 Android Development] Fictionles:
Some good news....

UPDATE

Sorry for the delay, I went out for a liquor run. On a whim, I decided to flash one of Case's 32A EBI1 patched kernels he has for the latest SenseHero ROM. I then left since I figured I'd be staring at a TMobile G1 screen for the whole trip. Until it booted....

But it Bootlooped on me after that. Was going to clean up my ext3 partition, didn't, and I'm off to do it now and flash again.
[G1 Android Development] Fictionles:
My drivers must need updating from Windows. I'm feel like I'm flying blind while its booting.
[G1 Android Development] Fictionles:
I'm at the Select your language screen.

:):):):)
[G1 Android Development] Geniusdog254:
Awesome! Which ROM are you using? So far finding a bootable HERO ROM has been my only problem. And also, about the drivers, I don't know if you got them going or not but I just used the drivers from SDK level 3 (Cupcake) as I used before and they were fine.

EDIT: Oh and of course lol the all important question. Does BT work?
[G1 Android Development] Fictionles:
No dice. Same behavior as before. But...I have a 2.6.29 kernel, not a 2.6.27 one..

You just need the right kernel. Once you said EBI1, I went here and picked the one for the SenseHero ROM: http://xdaforums.com/showthread.php?t=564949

I think I need to find another ROM/kernel combination.
[G1 Android Development] Geniusdog254:
That is probably the problem. When you read thru the ROM threads one of them (I forget which, I think MyHero). Has the choice of several kernels and it says all but the stock 2.6.27 kernels have issues with BT. So, who is game to contact a ROM chef and now that we have our order known ask for them to whip up a 2.6.27 kernel with proper EBI1 kernel support, no need for fancy BFS or the memhack, just the basic netfilter (we want tethering right ;) ) and and EBI1 support.
[G1 Android Development] Fictionles:
I'm going to try Eugene's ROM with his 32A patch before I revert back to 2.26.29

Then I'm going to fix my usb drivers to get adb to work.
[G1 Android Development] Geniusdog254:
OK, if you can't get a working 2.6.27 kernel going tonight I will contact probly eugene tomorrow and ask if he can make a custom one for us. Also I have zipped the USB drivers and uploaded them to 4Shared, heres the link:

http://www.4shared.com/file/148213822/c40d818d/usb_driver.html
[G1 Android Development] Fictionles:
I had this issue before when I upgraded the radio and SPL. It would pick up the drivers correctly, but adb wouldn't work.

I did find steps to completely blow away the existing drivers so it Windoze picks it up as a new device, but I've yet to find them.

I'm back on the 2.26.29 kernel, couldn't find a 32A one that would work.
[G1 Android Development] Geniusdog254:
Hmmm okay. Would you be willing to contact eugene? Also, did you try the Hero3G Uni with the 32a patch that is in that post? I might download it later if I get a chance.
[G1 Android Development] Cresho:
I tried replacing my current cm recovery 1.4 with the cm_recovery.zip on in terminal under king k rom under super user it worked. rebooted and now a problem! It wont boot into "android system recovery" on my g1. So..i booted up king k and in terminal replaced and back to cm recovery 1.4 and now i boot into it just fine.

ANY THOUGHTS ON THIS?

I need to know why this cm_recovery.img will not boot with home and power. it just stays stuck in t mobile g1 emblem at boot. my g1 is fine thank you very much! just need some answers. I'm very expirienced linux user but these terms and roms, images are new to anybody who don't know like myself. It's a little scary flashing stuff from people who you don't know but at least i know that the recovery image has nothing to do with the rom i boot up. ...boot wise.

ill be playing etqw..be back in an hour~!
[G1 Android Development] Fictionles:
I sent him a "hello" on twitter from my "new" 32A device.
[G1 Android Development] Geniusdog254:
Ok awesome fictionles.

And cresho, the cm recovery I posted won't boot unless you flash the 32a radio in the first post. Since you are still using the kingxkx rom you haven't flashed it. at the moment this is still pretty advanced so you should probably wait a little longer to do this until we get it worked out unless you know what you are doing.
[G1 Android Development] Fictionles:
I got adb working...however the kernel I picked doesn't appear to have logging enabled:

>adb logcat

Unable to open log device '/dev/log/main': No such file or directory

I had to manually set it as well to get it to even recognize adb:

setprop persist.service.adb.enable 1

So, I'm at least back to where I started. Not bad...

Oh and just for proof ;)
[G1 Android Development] Geniusdog254:
Lol I haven't had any problems so far, if you need a working phone I still recommend the cm4.2.3.1 port.
[G1 Android Development] Fictionles:
No issues here either. Wifi/2G/3G works. Dialing works. Apps work.

I honestly don't think I'm any worse off than I was before.

I picked SenseHero cause I knew it had A2SD and wouldn't blow up my internal memory. Plus its the one I was using before I flashed the radio.

Tomorrow may be another story, but I honestly think I'm in good shape.

Good to know about the CM port. I may try that at some point in the future.

Thanks for your help. I think we're onto something big.
[G1 Android Development] Cresho:
jUST OUT of curiousity, how is the hexene games running on this? or 3d games or HD movies or flash videos? is the g1 running these fine under the 32a rom after the bluetooth fix?

thanks for the advice Geniusdog254, i think ill just ask how the rom runs instead of flashing it. It funny though but for hero roms, the king k is the only rom that can run HD converted movies in my phone and also play 3d games. the other ones fart!

ill be playing etqw and be back in an hour.
[G1 Android Development] Geniusdog254:
Currently this isn't true bt fix, it should be, but the 2.6.29 kernel doesn't work with bt and we can't find a 2.6.27 kernel that has the right offsets. We are going to try to get a custom kernel from a chef but that will be tomorrow at the very earliest.

Anyway to your performance question. Everything will run the same for you on a 32a radio except the normal differences you'd find in roms. The kingxkx rom won't load on the 32a radio as it has a 32b kernel. If you get a good hero rom (there are some fast ones in the magic forums) you should notice no difference with a 2.6.29 kernel that is optimized with bfs. However to get bt you need a 2.6.27 kernel that works for us (we don't have this atm). This would make it slightly slower as bfs is jst designed for 2.6.29 & over (there have been backports to 2.6.27 but they are buggy). Also, the 2.6.27 kernel isn't as optimized as 2.6.29. That is the price you pay for bluetooth.

Now completely off tangent of that. People act like they are so scared of a brick with this, but newsflash! This is how you root the Rogers Dream (albeit in reverse). You have to convert it from an EBI1 radio to an EBI0 radio to flash normal ROMs. That is where I got the CM rooted recovery that works here. I believe it is also the same radio being flashed as the latest Rogers update but don't hold me to that.

This has nothing to do with anything bluetooth related lol it just bugs me how ignorant people are sometimes.
[G1 Android Development] ccyrowski:
This seems like the anti-fix. But I may be persuaded to cook a 2.6.27 kernel with latest BFS. Maybe.
[G1 Android Development] Christopher3712:
Lol, stop playing around and do it. You know you're going to do it anyway... :)
[G1 Android Development] Geniusdog254:
Haha you rock man. We don't even need BFS really because isn't it just designed for 2.6.29+? I thought I read somewhere that the backport was buggy but if not then lets go for it.
[G1 Android Development] Geniusdog254:
So ccyrowski did u get that kernel compiled yet? I am dieing to flash it, I don't need a whole rom just a basic 2.6.27 boot.img to flash.
[G1 Android Development] amossam:
Hey everybody!

I'm following this forum for 2 months or little less, but this is my first post here.

I'm living in Europe, Croatia, and I got my hands on G1 from USA (yes, 32B).

So, this is only my report.

I flashed 32A radio and cm_recovery for it, and I was able to enter recovery, but i was not able to boot any rom! i tried myHero 2.0.5 and SuperMagicv2r3, and none of them don't go past G1 boot screen. adb logcat only stays at "waiting for device" prompt.

I'm sure that I flashed correctly radio because in fastboot it shows different version numer for radio image.

Since I currently don't have time/will to continue trying, I reverted back to 32B and CyanogenMod 4.2.3.1. Lucky, i yesterday found switchrom script so reverting back to old system was painless. :)

If someone knows/thinks/sees what I have done wrong, please tell me! :D

Thx

P.S. I'm not new to flashing, i had N95 (with different software's and 'cracked' to allow any proggs) and currently have N810 (witch I'm thinking to switch to android :cool: ). Also, I'm linux user for 6-7 years, so console and shell scripts are not new to me... :D

Thx again, and thaks everybody on this great forum!!
[G1 Android Development] maxisma:
Guys, I have some ideas, and will post them tomorrow, too tired atm and have to study.
[G1 Android Development] scoobrel:
Is there another way to install the radio and recovery without fastboot? when i try the commands it says "waiting for device".
[G1 Android Development] fastludeh22:
Assuming you have the following: h spl on phone currently, skd and/or adb installed and working, windose xp (others may work, but what I can confirm)

Have usb connected and boot w/camera button down. Should enter hboot. Press back to enter fastboot. At this point windows should say new device found. Let search for drivers on ur comp, should find and say htc bootloader installed.

To confirm worked type fastboot devices and should list ur device.

Follow previous steps for what u were doing and should work.

Report back or pm me if doesn't work, may have to add a step or 2.
[G1 Android Development] scoobrel:
thanks for the help, i got it working now.
[G1 Android Development] mrjay:
ok so i followed the steps and got stuck at G1 screen. can't go in recovery mode. not sure why. fastboot is working. any ideas?
[G1 Android Development] :
flash rc29 dreaimg.nbh and do the rooting process again
[G1 Android Development] mrjay:
i went back by flashing radio 22.26I and amon_ra 1.2.3 recovery. nandroid and back to enomther.

i really wanted to try BT on hero. only thing that keeps me from any hero rom so far.
[G1 Android Development] fastludeh22:
First suggestion is to go back and read the entire theard. For some reason ra's recovery is not working. You have to use cm 32a ported recovery. Then u can enter recovery. The next wall people are hitting is a boot loop, thought to be a kernal issue. Once a custom kernel for 32a on 32b g1 is made that will be next step. Maybe u can find a 32a one that works?

Anyone with a 32b mt3g w/32a "hack" running on it want to do a nandroid backup and post it up. We can try fastboot flashing it instead of an update.zip. also can try different boot img combos. Just an idea.
[G1 Android Development] Fictionles:
I'm running a 32B kernel now with the HTC EBI1 patch for 32A devices. Bluetooth is still broken.

What *may* work is a 2.6.27.x kernel with Dream support....but I dunno.
[G1 Android Development] Fictionles:
In the midst of all my testing I was finally able to port RA's Dream Recovery v1.2.3 with all of its extra goodness.

The console still doesn't work, but I have more recovery options at my disposal.
[G1 Android Development] Geniusdog254:
Console isn't going to work because the console buffer isn't allocated right in memory. This is probably fixable but I don't know exactly how.

Also, can you please post the Amon_RA recovery that works?
[G1 Android Development] Fictionles:
I just took the kernel from the recovery you posted and merged it with RA's ramdisk. Nothing fancy.

EDIT - having trouble uploading the file. Here's the link

http://www.sendspace.com/file/o72ki5
[G1 Android Development] kingklick:
do u have gtalk fictionless
[G1 Android Development] Fictionles:
Yeah - Check your PM.
[G1 Android Development] fastludeh22:
bluetooth turn on?

Question for my fellow g1 users. What happens when u try to turn bluetooth on? Does it turn on and not work or does it just keep saying turning on? I didn't think it ever turned on. Well last night I was playing around and got it to turn on! Look here: xdaforums.com/showpost.php?p=4929441&postcount=1864

****ty thing is I didn't have another device to test with. I did however do a system state dump if that will help anyone. Hopefully I stumbled onto something that can help.

For ref I am using 32b g1, all standard 32b radio/recovery blah blah, bfs 300 kernal w/10mb hack, sense hero 1.3r3 (mutt).
[G1 Android Development] Fictionles:
The icons at the top aren't from that ROM.