Database Info

32a on 32b?

Do roms designed for 32a work on 32b phones? I'm assuming no, or there would be no reason to label them 32a...

???
i am also curious about this. based on what it says here
http://forum.xda-developers.com/showthread.php?t=547133
it shows that it works. so basically what we did was flash a 32a sappimg.zip to the MT3G and then can over write it with any 32a ROM, at least any rom that I've tried so far (cyanogenmod 3.9.9.1 & RAv1.1.0H)

A 32a ROM will not boot on a 32b phone and vice versa. When the MT3G is rooted the radio is flashed to a 32a radio which will allow you to boot 32a roms. 32a rogers owners can also flash a 32b radio and we can boot 32B ROMs. The 2nd step in the mt3g rooting procedure is to flash the radio back to 32B., meaning it can only boot 32B ROMs.
Now, there is no reason why someone with a 32b phone should want a 32A ROM. The kernel source for the 32A has not been released (illegally, mind you) which means that the 32A roms are limited to non-kernel based modifcations (ie. No netfilter/iptables for tethering, custom fixes, etc). Cyanogen’s 32B/Dream ROM uses a custom kernel that has extra features over the 32A version of the same ROM. In order to boot a 32B rom on a 32A phone the kernel has to be swapped, therefore losing all of the kernel features.
If you have a 32B phone you are gaining nothing by running a 32A ROM. The 32B ones are much more customized.
I am not sure if this made sense…sorry if I am confusing.

bcrook said:
A 32a ROM will not boot on a 32b phone and vice versa. When the MT3G is rooted the radio is flashed to a 32a radio which will allow you to boot 32a roms. 32a rogers owners can also flash a 32b radio and we can boot 32B ROMs. The 2nd step in the mt3g rooting procedure is to flash the radio back to 32B., meaning it can only boot 32B ROMs.
Now, there is no reason why someone with a 32b phone should want a 32A ROM. The kernel source for the 32A has not been released (illegally, mind you) which means that the 32A roms are limited to non-kernel based modifcations (ie. No netfilter/iptables for tethering, custom fixes, etc). Cyanogen’s 32B/Dream ROM uses a custom kernel that has extra features over the 32A version of the same ROM. In order to boot a 32B rom on a 32A phone the kernel has to be swapped, therefore losing all of the kernel features.
If you have a 32B phone you are gaining nothing by running a 32A ROM. The 32B ones are much more customized.
I am not sure if this made sense…sorry if I am confusing.
Click to expand...
Click to collapse
It made sense. I was just curious it was possible.

The kernel source for the 32A has not been released (illegally, mind you)
Click to expand...
Click to collapse
Illegally? Care to elaborate?

cursordroid said:
Illegally? Care to elaborate?
Click to expand...
Click to collapse
It's open source it has to be released that's what the Linux kernel ( Android) is all about.
Clinton

cursordroid said:
Illegally? Care to elaborate?
Click to expand...
Click to collapse
Under the GPL license a company has to make the source code available upon request (which HTC has not done). Its too bad Google doesn't go after them.
Someone with law experience can probably comment further.

Most of 32B ROM's works with 32A Sapphire and Magic

I have been trying to use 32B ROM's with 32A Sapphire and Magic device. I found that most of 32B ROM's works with 32A. How? Just do full wipe using Recovery RA-magic-v1.3.2 at below link:
http://forum.xda-developers.com/showthread.php?t=530492 (thanks Amon_RA)
Perform the following wipes using RA-magic-v1.3.2 before flashing the 32B ROM on 32A device:
1- Wipe data partition.
2- Wipe cache partition.
3- Wipe Dalvik-cache
4- Wipe SD:ext partition
Then flash any 32B ROM zip file on 32A regular way using recovery mode.
Then apply without a wipe 32A_UPDATE_Stable.zip (Thanks eugene373's)from below link.
http://alldroid.org/viewtopic.php?f=130&t=449
Reboot the phone and wait for 5 to 8 mins.
unfortuantely it is only 32B's SenseHero ROM series that is not flashable to 32A so far.

arahma said:
I have been trying to use 32B ROM's with 32A Sapphire and Magic device. I found that most of 32B ROM's works with 32A. How? Just do full wipe using Recovery RA-magic-v1.3.2 at below link:
http://forum.xda-developers.com/showthread.php?t=530492 (thanks Amon_RA)
Perform the following wipes using RA-magic-v1.3.2 before flashing the 32B ROM on 32A device:
1- Wipe data partition.
2- Wipe cache partition.
3- Wipe Dalvik-cache
4- Wipe SD:ext partition
Then flash any 32B ROM zip file on 32A regular way using recovery mode.
Then apply without a wipe 32A_UPDATE_Stable.zip (Thanks eugene373's)from below link.
http://alldroid.org/viewtopic.php?f=130&t=449
Reboot the phone and wait for 5 to 8 mins.
unfortuantely it is only 32B's SenseHero ROM series that is not flashable to 32A so far.
Click to expand...
Click to collapse
I did exactly what you did and SenseHero's latest works just fine.

Very interesting. Thanks..

Is that means that I can use the Vodafone ROM on a HTC device?

I wouldn't encourage this, as you're effectively replacing the ROM's original ramdisk with the one from eugene's 32A update, which might create unforseen problems. And most often than not you're also mixing different versions of kernel and kernel modules thus creating a bad "hybrid" while stripping the ROM of possible additional functionality.
If you want to make 32B ROM run on 32A, at least do it properly instead of encouraging hacks such as this one...:/

But regarding speed and other features (besides BT) is there any difference do I run some 2.6.29 kernel on 32A radio or 32B radio ?
I have native 32B (with 96MB swap set up on my SD). Shall I run:
- 32A radio and ROM (w 2.6.29, as BT filetransfer don't work on Sense anyway)
- 32B radio and ROM
Well which radio, ROM and kernel combo is "fastest" (regarding ringtone-lag, 3G, Wi-Fi, GPS etc.) ?

Kernel has to match the radio always, so if your radio is 32A radio you must use 32A Kernel. The advantage of 2.6.27 32A Kernel is it has working BT compared to 2.6.26 32A kernel.

arahma said:
Kernel has to match the radio always, so if your radio is 32A radio you must use 32A Kernel. The advantage of 2.6.27 32A Kernel is it has working BT compared to 2.6.26 32A kernel.
Click to expand...
Click to collapse
Thank you. But I know this .
My question was - is there anything ELSE which is different besides possibility to get BT working ?

The answer is no. Bluetooth does not work on any Hero 32B ROMs.

Why BT works on some ROM's when same 32A's Kernel and Radio used with 32B device?

I noticed that when I apply same 32A mode Radio and kernel i.e. Radio: 3.22.20.17 & Kernel: 2.6.27 to differnt 32B Hero ROMs and use them with 32B device in 32A mode, bluetooth sound works only on some of Hero ROM's and not on most of the ROM's. Does anyone know why?

[Recovery] [08-Feb-2010] RA-hero-v1.5.3.1

http://forum.xda-developers.com/showthread.php?t=561124
Just wanted to know if 1.5.3.1 is working on 32A?
Amon_RA's first post is unclear to me:
"This recovery if for the HTC Hero only, so NOT the Sprint Hero!!!, it will also work on the 32A Sapphire if you flashed the 6.35.x.x radio and 1.76.x SPL, ..."

shadow_empire1 said:
http://forum.xda-developers.com/showthread.php?t=561124
Just wanted to know if 1.5.3.1 is working on 32A?
Amon_RA's first post is unclear to me:
"This recovery if for the HTC Hero only, so NOT the Sprint Hero!!!, it will also work on the 32A Sapphire if you flashed the 6.35.x.x radio and 1.76.x SPL, ..."
Click to expand...
Click to collapse
It will only work on Magic's with Radio version 6.35.x.x and SPL version 1.76.x
In other words, only if you have the latest radio running (from the latest HTC updates).
edit: lol.. just saw your signature.. it will work on your Magic since you are running CursorSense rom.

ok, verified
just put it on my magic:
In fastboot-mode:
fastboot erase recovery
fastboot flash recovery recovery-RA-hero-v1.5.3.1.img
fastboot oem powerdown

nice
nice recovery

i need help

iam do update to my radio and hboot
its now
hboot-1.33.0013d
radio-2.22.27.08
but when i flash rom CyanogenMod-6.1
its not open frized in screen G1

Flash the right kernel from here.
Either the cm kernel or the anykernel.