Related
There are three things need to be changed to make the bluetooth working on (MyTouch 3G, Magic or Saphire) 32B phone.
1- Radio should be changed from 32B type to 32A type.
2- Kernel should be changed to kenel 2.6.27 (the Kernel should support BT e.g. HoFo-12. Note that not all Kernels support BT). "This only for developers to change Kernel"
3- Recovery should be changed to recovery-RA-magic-v1.2.3H.img
There are three options avalibale to change the phone from 32B to 32A mode:
Option 1:
If the device is not yet rooted, First root the 32B device according to below link:
http://forum.xda-developers.com/showthread.php?t=547133
Please follow above link and stop at Revert to 32B Radio and ROM i.e. do not go and apply this step and beyond.
Option2:
If the phone is already rooted and has 32B radio (radio 2.22.19.26I), execute below steps to change the radio to 32A radio (radio 3.22.20.17). Also flash the Recovery RAv-magic-v1.2.3H.
Put the phone is fastboot (hold back button and press end button)
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery (does not matter)
fastboot flash recovery recovery-RAv1.2.3H.img
1- Press MENU to power off! (do not reboot)
2- Hold HOME and POWER to boot into recovery mode
3- Apply 32A ROM.zip
Option 3:
Even if your phone was already rooted as 32B device with 32B Radio, above link will still work if followed to set the 32B device in 32A mode to accept 32A ROM’s with working Bluetooth.
Now the 32B device is ready to accept 32A ROM’s, choose one among 32A ROM’s in below links (These ROM's have already a working BT in their Kernel 2.6.26) :
1- http://forum.xda-developers.com/showthread.php?t=552274
2- http://forum.xda-developers.com/showthread.php?t=534415
3- http://forum.xda-developers.com/showthread.php?t=548837
4- http://forum.xda-developers.com/showthread.php?t=575501
Pleas follow the link associated with each ROM to update the device with chosen 32A ROM to flash desired 32A ROM in the phone.
Note that these three ROM’s are little bit slower because they are based on HTC Kernel 2.6.27.
I prefer two ROM's which are:
1- http://forum.xda-developers.com/showthread.php?t=552274
2- http://forum.xda-developers.com/showthread.php?t=575501
This is because there is a way to optimize it by using the “Swapper” application available at Android Market.
The steps to optimize this ROM is to two partitions FAT32+SWAP or even FAT32+EXT2+SWAP in Sdcard. Easiest way to create the 3 partitions, is to use recovery-RA-magic-v1.2.3H.img at below link:
http://forum.xda-developers.com/showthread.php?t=530492
Set the device in the Recovery Mode (Hold HOME and POWER to boot into recovery mode) to create the 3 partitions.
Then download Swapper application from Android Market to the phone. Start Swapper on the device and go to:
Configuration/ Settings/ Advanced preferences and check Use swap partition. Then set the swapper on. Finally close the Swapper.
Note using RA-magic-v1.2.3H.img enables only 32 MB swap while recommended is 128 MB swap. An alterantive is to use Paragon Partition Manager or any other avaliable methods to create the swap partition.
Note that whenver the phone get restarted the swapper has to set on again.
These ROM’s can also run in regular Home or Sense. Home is faster than Sense if someone does not like to use swapper. Please download and install “AdvancedLauncher” application from Android Market to help choosing the preferred Home, Sense or AdvancedLauncher. Note the device has to be restarted to choose the desired home.
Now the 32B device should be working on 32A ROM with Bluetooth sound.
Note that the 32B device will only accept 32A ROM’s now.
If Revert to 32B Mode is desired, please follow below link:
http://forum.xda-developers.com/showthread.php?t=547133
Start at Revert to 32B Radio and ROM to revert the phone to 32B mode to accept 32B ROM’s again.
Enjoy your 32B phone with working Bluetooth.
Interesting. How safe is this? Changing device radios is usually where bricks happen and it makes me nervous.
I have changed my phone mode I. e. Radio many times as I mentioned without no issues at all. I always switch between 32A and 32B.
But how's the speed ?
Let's say this posts recommended MyHero 2.0.4 (with swap enabled) for 32A against other SenseUI ROM's for 32B (which it is actually/hardware wise is).
This is very interesting...
I want to see a proof of 32A Radio running on 32B before flashing..
Maybe this owuld fix BT for g1 too?
Would love to see Proof of this.
Oh, and for G1 users, they would have to fastboot the content of the sappimg..
i can vouch for this. when i first rooted my 32B MT3G i used this rooting method (before any other where discovered). I ran 32A Roms on my mytouch for a few days before switching to the 32B radio (since there where more options for 32B at the time)
Wasn't there a lot of discussion when the mt3g first got root, that you could stay on the 32A radio? I got mine the day they came out, and I think I remember that the original way we rooted left us with 32A radio. I seem to remember that the flash back to 32B radio was discussed as optional? Don't go on my memory though, I'm going to re-read those old threads.
pbaird said:
Wasn't there a lot of discussion when the mt3g first got root, that you could stay on the 32A radio? I got mine the day they came out, and I think I remember that the original way we rooted left us with 32A radio. I seem to remember that the flash back to 32B radio was discussed as optional? Don't go on my memory though, I'm going to re-read those old threads.
Click to expand...
Click to collapse
yeah flashing back to 32B was optional. But 32A roms didnt run great since their kernel was optimized to run with more RAM.
To OP... hows the speed in comparison to say... evils nano rom?
dills84 said:
yeah flashing back to 32B was optional. But 32A roms didnt run great since their kernel was optimized to run with more RAM.
Yep, I went back and re-read the original thread that Amon-RA posted, and I also ran 32A for a few days, because I had to decide if it was worth the risk to flash the radio again if I didn't have to.
BTW, are we talking about stereo bluetooth, handsfree phone bluetooth, or both?
Click to expand...
Click to collapse
The attached screenshot proves that 32a RADIO works on 32B device.
arahma said:
The attached screenshot proves that 32a RADIO works on 32B device.
Click to expand...
Click to collapse
Thanks,
Going to test it out now. Just wanted a little proof was all, lol.
Thanks for the Picture man!
We Dream users would love you forever if you you'd give us BT in hero with this!
pbaird said:
BTW, are we talking about stereo bluetooth, handsfree phone bluetooth, or both?
Click to expand...
Click to collapse
Ya i'd like to know that same because if i can get my bt headset working wit a hero rom i'd b tha happiest man alive!
Flashing 32a Rom now. Will Find out shortly if BT is working.
BT IS WORKING< I REPEAT BT IS WORKING NOW BT IS WORKING
On 32b Hardware. Fastboot and Flash the Radio, then Recovery. Then Flash the 32a as suggested!!
pbaird said:
dills84 said:
yeah flashing back to 32B was optional. But 32A roms didnt run great since their kernel was optimized to run with more RAM.
Yep, I went back and re-read the original thread that Amon-RA posted, and I also ran 32A for a few days, because I had to decide if it was worth the risk to flash the radio again if I didn't have to.
BTW, are we talking about stereo bluetooth, handsfree phone bluetooth, or both?
Click to expand...
Click to collapse
BT PHONE is working after Flashing the Radio, then recovery.
BT WORKING ON 32b Hardware!!
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
Click to expand...
Click to collapse
Tools Below
Radio & Recovery Img needed. BT_Fix_32b.rar
USB Driver + 64-Bit usb_driver.rar
Click to expand...
Click to collapse
Oke but now , how do we get 32a working? anyone
read read read read....
Okay my phones info is as follows:
UK Vodafone running Donut 1.6
Code:
SAPPHIRE UNKNOWN 32B SHIP S-ON G
HBOOT-1.33.0007 (SAPP10000)
CPLD-10
RADIO-2.22.19.261
Jul 31 2009, 15:49:25
Now is this or is this not a perfected SPL "1.33.0007" as I cant do jack with it nor can I get any computer to recognize it when it's in fastboot connected to a PC...*sigh* (although it will when it's turned on)
Now assuming the above is correct and it is a perfected spl will the below work:
Step 1
Flash the phone with the 32A ROM v2.53.707.2 (Engineerings SPL v1.33.2010) this being a higher rom version than my own from Amon_RA's thread (http://forum.xda-developers.com/showthread.php?t=548218)
Step 2
Change the radio (any recommendations?) back to that of a 32B HTC Magic device and install CyanogenMod using the info again from a different Amon_RA thread (http://forum.xda-developers.com/showpost.php?p=4314039&postcount=1)
Step 3
Sit back and bathe in the glory of my finally rooted HTC Magic?
Thanks in advance for any and all help even if it's just a quick reply to tell me I'm off my trolley and it's a sure fire way to brick my phone
Has anyone managed to get anywhere with this hardware. I have exactly the same version of hardware and have not been able to get it to connect to the pc in fastboot.
I would imagine that a lot of people are in the same position, with the same hardware so could someone point us in the right direction please.
dreamsofubuntu said:
Now is this or is this not a perfected SPL "1.33.0007" as I cant do jack with it nor can I get any computer to recognize it when it's in fastboot connected to a PC...*sigh* (although it will when it's turned on)
Click to expand...
Click to collapse
Yes, 1.33.0007 is a perfected SPL, but nevertheless you should get fastboot to recognize your phone. Did you properly install the Android SDK USB drivers?
Thanks in advance for any and all help even if it's just a quick reply to tell me I'm off my trolley and it's a sure fire way to brick my phone
Click to expand...
Click to collapse
I had the same perfected SPL on my 32B but (luckily) with Android 1.5 CRC24.
I think it should work if you flash a "official" vodafone 1.5 CRC24 1.33.0007 image, then install flashrec on Android, change the recovery Image, boot into recovery mode and flash an engineering spl. Thats basically what I did, except for the downgrade to 1.5.
AFAIK on 1.33.0007 you should be able to downgrade without a goldcard.
Same Version
Hello everybody,
i have the same phone with the same SPL, too.
My Problem is when i try to flash the sappimg.zip with the POWER on and Volume down methode, everything wents fine.
But after reading the Update File i end up with an error like:
"Main Version is older".
Don't know what to do...
Phone HTC Sapphire (Magic) 32B Ship S-ON G
SPL(hboot): 1.33.0007 (SAPP10000)
CPLD-10
I already tryed a Goldcard, but no luck at all
Any Ideas.
I readed 2 Threads, they got a problem with theire devices,
it also was an 32B Magic and they wanted to do an update, too.
And they ended up with the same error message, so they tryed
to flash a 32A Image, and then the 32B, and it worked.
But i am worried, don't want to brick my device.
Anybody out there, with an idea?
Greeting
ZabbensX
i got the exact same problem. waiting for answers...
If you are running Donut Rom DRC92 then at the moment you are stuck. We need to wait until a higher firmware with a non-perfected SPL is released. If you are running a Cupcake Rom (starts with a C) then you can upgrade fine. I'm in the same situation after bricking my first phone using a RUU (they are for 32As only). Luckily Vodafone replaced it under warranty but I have ended up with the perfected SPL.
After having root and now unable to get root I can't say I miss it much. It makes you think what do you need root for? One of the reasons was the ability to flash custom roms but no disrespect to all the Hero Rom developers but NONE of them run well on a 32B Magic. Cyanogens software is good but what does it do that stock firmware doesn't? Any way hopefully Eclair won't be long, a new Rom will be released and we can all change to an engineering SPL and all will be jolly again.
what's ur OS ? Can HTC sync read ur device ?
No HTC Sync doesn't recognize my phone
Wayneh73 said:
If you are running Donut Rom DRC92 then at the moment you are stuck. We need to wait until a higher firmware with a non-perfected SPL is released. If you are running a Cupcake Rom (starts with a C) then you can upgrade fine. I'm in the same situation after bricking my first phone using a RUU (they are for 32As only). Luckily Vodafone replaced it under warranty but I have ended up with the perfected SPL.
After having root and now unable to get root I can't say I miss it much. It makes you think what do you need root for? One of the reasons was the ability to flash custom roms but no disrespect to all the Hero Rom developers but NONE of them run well on a 32B Magic. Cyanogens software is good but what does it do that stock firmware doesn't? Any way hopefully Eclair won't be long, a new Rom will be released and we can all change to an engineering SPL and all will be jolly again.
Click to expand...
Click to collapse
Thats the reason I want to use the 32A rom as it's newer then my current rom and so it *should* hopefully flash the phone including the spl and then I can change the radio back to that of a 32B device
also what do you mean about being able to change to an engineering spl in Eclair?
Also I've never been able to get HTC Sync to work ever =[ in both xp or vista, and never been able to get the drivers working properly however I am yet to try with Ubuntu
dreamsofubuntu said:
Thats the reason I want to use the 32A rom as it's newer then my current rom and so it *should* hopefully flash the phone including the spl and then I can change the radio back to that of a 32B device
also what do you mean about being able to change to an engineering spl in Eclair?
Also I've never been able to get HTC Sync to work ever =[ in both xp or vista, and never been able to get the drivers working properly however I am yet to try with Ubuntu
Click to expand...
Click to collapse
You should be able to get both fastboot and adb to recognise your phone although you won't be able to do anything. That sounds like a driver issue. If you go to the HTC website and download the latest drivers (pick the ones for the HTC branded magic) you should be ok. Try the link below.
http://www.htc.com/uk/supportdownloadlist.aspx?p_id=267&act=sd&cat=all
As for flashing a 32a rom then changing the radio, good luck with that after already bricking one phone I haven't got the balls to try. If you do try and it works please post here exactly what you done as many people will thank you.
Lastly what I'm waiting for is a higher rom version which will probably be eclair (Android 2.0) which comes with a non-perfected SPL. Then the devs on here can get the relentless rooter to work on our phones.
Wayneh73 said:
You should be able to get both fastboot and adb to recognise your phone although you won't be able to do anything. That sounds like a driver issue. If you go to the HTC website and download the latest drivers (pick the ones for the HTC branded magic) you should be ok. Try the link below.
http://www.htc.com/uk/supportdownloadlist.aspx?p_id=267&act=sd&cat=all
As for flashing a 32a rom then changing the radio, good luck with that after already bricking one phone I haven't got the balls to try. If you do try and it works please post here exactly what you done as many people will thank you.
Lastly what I'm waiting for is a higher rom version which will probably be eclair (Android 2.0) which comes with a non-perfected SPL. Then the devs on here can get the relentless rooter to work on our phones.
Click to expand...
Click to collapse
Okay thanks =] will see if I can get the drivers working with Ubuntu via the Android SDK although I cant try the Goldcard method until I get hold of another memory card as I've misplaced the one that came with the phone
dreamsofubuntu said:
Okay thanks =] will see if I can get the drivers working with Ubuntu via the Android SDK although I cant try the Goldcard method until I get hold of another memory card as I've misplaced the one that came with the phone
Click to expand...
Click to collapse
u cant access it unless u enable USB debugging. If u cant pass activation, then ur screwed until u activate it with 3G
hacker1 suggested this:
Okay I post this as a private message because I don't know if I can post the links to the images on an official board.
There are basically 2 methods for flashing/rooting the 1.33.0007.
Method 1:
1.Download Android 1.5 CRC24 NBH
2. rename to sappimg.nbh and copy to sdcard
3. start magic with volume down+power
4. confirm with trackball
5. If everything works ok, follow 8. on method 2
If this fails with "Main version older" then copy sappimg.nbh to a goldcard and try again. (Some brands of SD-Cards are known to be incompatible with a goldcard, so you might need to try some different ones)
If it fails to flash with a goldcard you need method 2:
1. Download Android 1.5 CRC24 NBH (if you don't have it already)
2. Download 32A Image
3. rename 2.53.707.2_-_sappimg.zip to sappimg.zip and copy to goldcard
4. start magic with volume down+power and confirm flashing with trackball
5. turn off phone
6. delete sappimg.zip from goldcard and copy the "Android 1.5 CRC24 NBH" as sappimg.nbh to sdcard
7. start magic with volume down+power and confirm flashing with trackball
8. after restarting you should now be at Android 1.5 CRC24, install flashrec.apk to phone, change recovery image, boot into recovery and flash engineering spl.
Hope this will help you.
Click to expand...
Click to collapse
hasnt worked for me yet.
IsmailBhai said:
u cant access it unless u enable USB debugging. If u cant pass activation, then ur screwed until u activate it with 3G
Click to expand...
Click to collapse
USB debugging was one of the first things i turned on =]
In the same mess....
I hope someone can figure this out soon, I'm also in the same boat and cannot root my mt3g. It has the following specs:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.2007 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
Jul 31 2009, 15:49:25
Click to expand...
Click to collapse
I have tried the following methods...
sappimg.zip + goldcard
Model ID incorrect!
Update Fail!
SAPPIMG.nbh
Main Version is older!
No luck, just errors. Anyone got any suggestions?
xepergod said:
I hope someone can figure this out soon, I'm also in the same boat and cannot root my mt3g. It has the following specs:
I have tried the following methods...
sappimg.zip + goldcard
Model ID incorrect!
Update Fail!
SAPPIMG.nbh
Main Version is older!
No luck, just errors. Anyone got any suggestions?
Click to expand...
Click to collapse
Not yet and the fact that none of the senior members are bragging any where they can do it I think we are pretty much stuck. In fact no-one is talking about trying to hack this so I think it maybe in the too difficult bin! Time to save up and get a Nexus One
nooooooooooo
Wayneh73 said:
Not yet and the fact that none of the senior members are bragging any where they can do it I think we are pretty much stuck. In fact no-one is talking about trying to hack this so I think it maybe in the too difficult bin! Time to save up and get a Nexus One
Click to expand...
Click to collapse
Dream killer
32A Rom on your 32B may brick your phone
dreamsofubuntu said:
Thats the reason I want to use the 32A rom as it's newer then my current rom and so it *should* hopefully flash the phone including the spl and then I can change the radio back to that of a 32B device
also what do you mean about being able to change to an engineering spl in Eclair?
Also I've never been able to get HTC Sync to work ever =[ in both xp or vista, and never been able to get the drivers working properly however I am yet to try with Ubuntu
Click to expand...
Click to collapse
*IF* you load the 32A radio and SPL and ROM on your 32B, you may only succeed in bricking your phone.
They are different devices. You can try it if you like, but be ready to throw the phone away.
dreamsofubuntu said:
Okay my phones info is as follows:
UK Vodafone running Donut 1.6
Code:
SAPPHIRE UNKNOWN 32B SHIP S-ON G
HBOOT-1.33.0007 (SAPP10000)
CPLD-10
RADIO-2.22.19.261
Jul 31 2009, 15:49:25
Now is this or is this not a perfected SPL "1.33.0007" as I cant do jack with it nor can I get any computer to recognize it when it's in fastboot connected to a PC...*sigh* (although it will when it's turned on)
Now assuming the above is correct and it is a perfected spl will the below work:
Step 1
Flash the phone with the 32A ROM v2.53.707.2 (Engineerings SPL v1.33.2010) this being a higher rom version than my own from Amon_RA's thread (http://forum.xda-developers.com/showthread.php?t=548218)
Step 2
Change the radio (any recommendations?) back to that of a 32B HTC Magic device and install CyanogenMod using the info again from a different Amon_RA thread (http://forum.xda-developers.com/showpost.php?p=4314039&postcount=1)
Step 3
Sit back and bathe in the glory of my finally rooted HTC Magic?
Thanks in advance for any and all help even if it's just a quick reply to tell me I'm off my trolley and it's a sure fire way to brick my phone
Click to expand...
Click to collapse
I do not know if this helps you guys.http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/
All phones are diffrent I have perfect spl too and I manage to flash in fastboot.
I've found something which I think might help on a German android forum and it looks like the guy succeeded in doing something similar to what I posted originally in this thread from what I can gather from google translate
http://www.android-hilfe.de/root-hacking-modding-htc-magic/11285-flashen-mit-1-33-0007-spl.html
can anyone help me out and post a translation for me? (I mean someone who can give a translation not from a website unless it's blindingly better then google)
Current translation via google...
edit -
it should be called "flashed with SPL 1.33.0007"
--
Hello, nice forum you have here
I have the following problem:
Recently I wanted to flash my Vodafone Magic (Android 1.6 SPL 1.33.0007) with Cyanogenic Mod.
Since I have a "perfect" SPL, I've tried it with a gold card. Everything went well so far. Only apparently I had made a version for the 32A, then stood for in fastboot Ship S-OFF H and I could only make recovery for the HTC version of RA, rather than the Google version. I had taken here -> ROM v2.53.707.2 (SPL engineering had v1.33.2010) the rom but works as well and booted normally.
anyway I wanted to be the recovery of RA have wrote -> HTC_ADP_1.6_DRC83_rooted_base.zip CM 4.2.5 and later.
The flash itself went well, but I stayed in the HTC bootscreen Magic hang himself and it did nothing more.
In another forum I was told that what I have by gold card (power + vol down) flashed (the sappimg.zip) was just for the 32A, and it therefore did not go.
Jetz, I wanted to ask what am I then can take the 32B, then to flash it to the cyanogenic mod? Because irgednwie I'm a little confused at the 10,000 versions at XDA dev .....
I hope someone can help me there. I'm just glad that the phone because I did not have gebricked garkeine backup (duchzufall had found it here in the forum, the firmware vodafone stock and re-flashed)
thank you in advance
-edit -
ah, I'm stupid.
The stock firmware I had was re-flashed V1.5 .. have then by Flashrecovery the CMrecovery flashed and book now funzt everything.
no offense
Click to expand...
Click to collapse
So from what I can gather this guy succeded in rooting and flashing his HTC Magic 1.33.007???????????
I bricked my 1st magic;
now i have 2nd and i have no idea how to run adb and all the stuff around and after my first very bad experience i decided to to try again.
I would like to know if is possible load any rom without using nandroid.
/BTW if someone in Toronto put recovery and change radio for me;i'd pay for it/
thanks.
Like I tell everyone who posts a very vague question. What model is yours?
Pick one (32[] is shown on fastboot screen back+power)
A) MyTouch 3G 32A (Magic 32A)
B) MyTouch 3G 32B (Magic 32B)
C) MyTouch 3G Limited Edition (Fender) or 1.2 (with headphone jack on top)
Pick Radio
A) 2.xx
B) 3.xx
C) 6.xx
Hboot (usually something like 0006, 0010, 0007 etc
So on (Basically could just list your Fastboot screen)
Also clarify if you can enter fastboot (back + power) and if you can enter recovery (holding down Home + Power)
So you bricked your first.... still dont know what you are doing... obviously have no clue what Nandroid really is...
I suggest DONT DO IT....
But thats just my logical opinion
Mine is 32A and radio is 3.22.; hboot 0009
kbeezie said:
Like I tell everyone who posts a very vague question. What model is yours?
Pick one (32[] is shown on fastboot screen back+power)
A) MyTouch 3G 32A (Magic 32A)
B) MyTouch 3G 32B (Magic 32B)
C) MyTouch 3G Limited Edition (Fender) or 1.2 (with headphone jack on top)
Pick Radio
A) 2.xx
B) 3.xx
C) 6.xx
Hboot (usually something like 0006, 0010, 0007 etc
So on (Basically could just list your Fastboot screen)
Also clarify if you can enter fastboot (back + power) and if you can enter recovery (holding down Home + Power)
Click to expand...
Click to collapse
Yes you're Absolutely right. That's why I started this thread. I had my first rooted and had RA recovery.and I did it by myself.but that time I used "one click method" from unlockr. But my current phone doesn't work with that method.that's why I'm lost.
I'd like to have custom recovery and 6.35 radio and nice ROM but I know I don't know how to do it. That's why I'm asking for your help.
thanks anybody for any help.
crypysmoker said:
So you bricked your first.... still dont know what you are doing... obviously have no clue what Nandroid really is...
I suggest DONT DO IT....
But thats just my logical opinion
Click to expand...
Click to collapse
rony05 said:
Yes you're Absolutely right. That's why I started this thread. I had my first rooted and had RA recovery.and I did it by myself.but that time I used "one click method" from unlockr. But my current phone doesn't work with that method.that's why I'm lost.
I'd like to have custom recovery and 6.35 radio and nice ROM but I know I don't know how to do it. That's why I'm asking for your help.
thanks anybody for any help.
Click to expand...
Click to collapse
Not sure why you want the new radio, is there specifically a rom you're looking to load?
Also just to clarify, the new magic, is there a headphone jack on top?
kbeezie said:
Not sure why you want the new radio, is there specifically a rom you're looking to load?
Also just to clarify, the new magic, is there a headphone jack on top?
Click to expand...
Click to collapse
the magic is "old kind" without jack on top. i was thinking to get new radio b/c i saw much more new ROM's are coming in new radio and old is getting to be forgotten.
rony05 said:
the magic is "old kind" without jack on top. i was thinking to get new radio b/c i saw much more new ROM's are coming in new radio and old is getting to be forgotten.
Click to expand...
Click to collapse
There's about 1 stable rom for the new radio. Two at the most.
kbeezie said:
Pick one (32[] is shown on fastboot screen back+power)
A) MyTouch 3G 32A (Magic 32A)
B) MyTouch 3G 32B (Magic 32B)
C) MyTouch 3G Limited Edition (Fender) or 1.2 (with headphone jack on top)
Pick Radio
A) 2.xx
B) 3.xx
C) 6.xx
Click to expand...
Click to collapse
Ignore below, I misunderstood kbeezie
I thought 32A uses 3.xx. 32B can also use 3.xx, correct me if I'm wrong. From what I know, I wouldn't flash a 2.xx radio to a 32A.
Can't you just use the goldcard method? Try unlockrs one click root and try to flash an engineering SPL
i bought this 2nd magic from a guy and he already has custom ROM in it. but he has not put recovery image in it. so i wonder how he did it. all im looking for is change ROM's .
so back to my first post; is it possible load without using nandroid?
thank you
KAwAtA said:
There's about 1 stable rom for the new radio. Two at the most.
I thought 32A uses 3.xx. 32B can also use 3.xx, correct me if I'm wrong. From what I know, I wouldn't flash a 2.xx radio to a 32A.
Can't you just use the goldcard method? Try unlockrs one click root and try to flash an engineering SPL
Click to expand...
Click to collapse
You need to use fastboot/adb to push new ROM images to the phone.
You need to post all the information from your phone. I need to know if it's an eng or perfected spl as well. Getting Hboot 0009 isn't enough.
Also, can you please do me a favour before I act like a jerk.
crypysmoker said:
So you bricked your first.... still dont know what you are doing... obviously have no clue what Nandroid really is...
I suggest DONT DO IT....
Click to expand...
Click to collapse
No kidding. I also suggest you don't do it. So please, do this before I become an asshole
Go find out what the nandroid stuff does.
I'm just surprised that you've bricked your first Magic, yet you still continue not to do much research before rooting.
Another theory (unconfirmed, but seems logical): Safely change between ANY SPLs using recovery.
http://forum.xda-developers.com/showpost.php?p=6535848&postcount=87
The short version: You go into recovery, set it to write the new radio/hboot update.zip, then before rebooting, WIPE THE RECOVERY PARTITION. When it reboots in boot-recovery mode after updating the radio/hboot, it'll fail properly and force you into fastboot rather than ending up in limbo. This *should* be safe, even against mismatched radio/spl.
This is the (confirmed) theory regarding the relationships between the radio/hboot/recovery:
That ALL radios are compatible with ALL SPLs.
That bricks are NOT caused by radio/spl incompatibility, but by FAILURE TO BOOT RECOVERY.
I realize that that sounds bold and goes against the grain and what people think that they know.
Up until now, there have been some wild theories about bricks. One of the early ones is that there was a relation between the mainboard code and the chance of bricking -- specifically, that a mainboard labeled as "DVT" will brick whereas a mainboard labeled as "PVT" will not. This theory, though still widely believed, is FALSE. There are conclusive reports of DVT boards being successfully loaded with the deathspl. The simple fact that there are very very FEW DVT boards in the wild contributes to the lack of proof.
A second, and much more conclusive theory, is that the RADIO version affects the chances of bricking. While in general, having a 2.x or 3.x radio seems to reduce the chances of bricking, there are STILL observable instances of bricks despite this. In other threads, I have referred to the "unknown factor" that triggers this.
While I haven't been able to isolate this unknown factor, I have been able to come to a theory regarding overall radio compatibility based on the results of experimentation by forum member ezterry, who has been able to both successfully REVERSE a brick, as well as ESCAPE the current rogers firmware lockdown.
His work can be found in the following two threads:
http://forum.xda-developers.com/showthread.php?t=591048
http://forum.xda-developers.com/showthread.php?t=649431
Specifically, the results are as follows;
Observed in a BRICKED PHONE containing a 1.x radio and deathspl:
The phone was jammed into boot mode 3 -- recovery, and ignored boot-time signals to alter boot mode -- specifically, the camera button, which should, under normal circumstances, activate FASTBOOT. It appears that boot-time signals are ignored when the device is not in normal boot mode. The solution was from bluelight mode (trackball+power) to override a security lockout using jtag, and force it into fastboot using serial console. And yes, the deathspl's fastboot mode was successfully activated from a boot through a 1.x radio.
What is not clear at this moment is why a recovery boot is unsuccessful. This is the unknown factor. Under certain circumstances, I'm sure that the specific recovery image installed may not be compatible with either the radio or the spl -- this could be due to an EBI 0/1 kernel issue. Or possibly some effect of the deathspl's partition remapping. I suggest a possibility that the radio/spl *combination* may not be compatible with the recovery. In any event, the solution may be to FORCE the thing to go to FASTBOOT mode upon reboot and then using fastboot to flash known good system images. This, though not isolating the unknown factor, will make it irrelevant.
First, I suggest flashing radio and SPL using FASTBOOT ONLY.
Second, I suggest WIPING ALL PARTITIONS (obviously with the exception of radio and spl) -- this is supposed to force the device into fastboot mode, HOWEVER, it is not clear if this would work in the event that the device is already stuck in recovery-boot. It might.
THIRD, I suggest completing this step with a "fastboot reboot-bootloader".
Also note this:
Under normal circumstances, when leaving fastboot mode, the device should be configured for a NORMAL BOOT. I therefore introduce another possibility: That when using FASTBOOT to install the radio and/or SPL, you are GUARANTEED NOT TO BRICK (not guaranteed at this point since it has not been verified). A normal bootup will obviously fail, however, when rebooting from a "softbrick", it will again try normal boot mode -- which means that it WILL accept boot time signals, like the CAMERA button to enter fastboot.
Specifics on boot mode:
There are three selectable boot modes;
Normal boot,
recovery boot,
fast boot.
Normal boot mode is fine since it will accept boot time signals. Fast boot mode is fine since it will both allow you to flash anything you want as well as clear any set boot flags. It is only the RECOVERY boot mode that is dangerous. In fact, it is SO dangerous, that in my opinion, it should NOT be possible to set this flag. Recovery mode should ONLY be accessible through boot-time signalling.
So the solution to avoid bricking is in ENSURING that the device does NOT get the "recovery" boot mode flag set. The other solution is in developing (as ezterry has expressed a desire to do...) an SPL that IGNORES the boot mode 3.
I feel smarter just from reading all of that.
+1
I wish there was a thread "like" button like on fb lol nice thoery
My name is Sheldon and I support this message.
Recently bricked a G1 for the first time (And I have done many SPL/Radio flashes before on multiple G1's) and it was only during reboot into recovery after a flash that the battery got pulled by mistake causing it to brick.
Reason I support this theory is because at that moment the phone was flagged to recovery boot and did not complete this process successfully after flashing a new SPL. It was the ENG spl I was flashing too.
A+ on the write up to OP.
+1 nice theory and well written out
Not so sure about any SPL + radio combination working.
Specifically there were some really weird cases of bricks for users flashing new radio and SPL for Magic (1.76.X HBOOT, 6.35.X RADIO) on a 32B Magic. Afterwards their ROM authentication always failed for some reason.
So there are combination that actually do not work?
I have to admit, I feel cleverer after reading the whole thing
+1 for good writeup.
xxmonsterx said:
I wish there was a thread "like" button like on fb lol nice thoery
Click to expand...
Click to collapse
Sorry, digression:
Can we petition for one? Seriously, I have been seeing comments on having a 'like' button over XDA since the new revamp.
I might disagree with this theory because my g1 used to run with a broken recovery image. A couple of months ago I tried to figure out what was the max size of an recovery image. A way of testing this was by flashing an image that was very large and seeing how much will be copied. So let's say the recovery image can only be up to 10 mb but instead I flashed a 70 mb image. It will get flashed but no error massage will appear. So then I rebooted and went into recovery mode. It didn't work out and got stuck on a black screen. So I rebooted, reflashed ra-recovery image, test it out, and it worked out perfectly. Sadly I didn't recovery any speific amount of size for the recovery image. If the android OS runs much like a computer, First it will check the bios, bootloader, recovery, and then load the rom, or start to run the enviroment for the android operating system. Can someone check what those the update-script say in the deathspl.
Hrm ... didn't see this thread was made
may want to check out my update.
http://forum.xda-developers.com/showpost.php?p=6037188&postcount=398
mohsinkhan47 said:
.... Sadly I didn't recovery any speific amount of size for the recovery image. If the android OS runs much like a computer, First it will check the bios, bootloader, recovery, and then load the rom, or start to run the enviroment for the android operating system.
Click to expand...
Click to collapse
"The phone was jammed into boot mode 3 -- recovery, and ignored boot-time signals to alter boot mode -- specifically, the camera button, which should, under normal circumstances, activate FASTBOOT. It appears that boot-time signals are ignored when the device is not in normal boot mode."
I maybe completely off but here is why I support this theory:
G1's don't have a "BIOS" to be checked upon starting that determine where or what type of boot up to perform so you can quickly change the settings by pressing F2 to say "Boot Normal Boot first, then Fastboot, then Recovery, etc" like a computer can. What the OP is stating is that when the phone is bricked, it could be due to it being "Flagged" at trying to boot into recovery and not taking ANY other boot commands....even if the Recovery Image may have been corrupted (which if it did have a BIOS like a computer it would attempt to boot the next in line option you've set if previous option failed)...so this causes the phone to be rendered useless ie: Bricked.
SOOO thats why the last part of the original post says it would be nice to develop (if possible) a SPL that would not allow this flag to be set at Boot recovery thus helping avoid possible bricks. Since if it can't flag Boot Recovery, then if the image were corrupted it would at least accept other boot signals for Normal boot and FastBoot which in turn allow you to fix said failed image.
Does any of that make sense? its late and I feel like I'm rambling.
the way i had envisioned it was IPL (radio) having a list of boot locations for SPL. Remember that SPL is the one that listens to user-input boot modes. The radios that are not compatible with the death spl were released before this spl was released (remember, it was originally the sapphire spl). Since the dream and sapphire share radio chipsets, the dream was able to use sapphire spls once a radio capable of booting it (starting with 2.22.19.26I) and had that particular spl available in it's boot list, then the spl could be booted with the appropriate parameters. Since on earlier radios the SPL hadn't been created yet, it wasn't on the list of the spls allowed to boot.
I haven't studied spl/ipl much codewise, but my findings come from theoretical analysis of spls among other htc handsets (my idea originally came from trying to figure out a hex-hack to spls that allowed them to be booted by any radio, then we could toss an android spl into a winmo device and have it boot the linux kernel).
The boot modes mentioned are spl dependent, so if the ipl can't find an spl, then the only option is to get the ipl to find the spl and boot it.
The real question would then be, how is the ipl finding the spl, and is there something we can do with spls (again, as a hex-hack) so that the appropriate value is returned to ipl when trying to boot spl and to boot that spl?
---edit---
Further (this had occurred to me before but I just remembered), keep this in mind, all dream IPLS are capable of booting all Dream SPLs, regardless of board version (not to delve into t-mo dream and rogers dream, different radio, so for this purpose, different device). I'm pretty sure too that, had there been as many IPLs/SPLs for the sapphire, the same would have been true (and we'd have more death spls to try on the dream).
What that tells me is that whatever the IPLs of all radios are reading for in SPLs, it's present across stock/eng/hard SPLs. If that thing that is being read from or booted to in those SPLs can be copied over to the Death SPL, then we'd have a death SPL that's bootable by all radios. Doesn't fix any current bricks though >.<
mohsinkhan47 said:
I might disagree with this theory because my g1 used to run with a broken recovery image. A couple of months ago I tried to figure out what was the max size of an recovery image. A way of testing this was by flashing an image that was very large and seeing how much will be copied. So let's say the recovery image can only be up to 10 mb but instead I flashed a 70 mb image. It will get flashed but no error massage will appear. So then I rebooted and went into recovery mode. It didn't work out and got stuck on a black screen. So I rebooted, reflashed ra-recovery image, test it out, and it worked out perfectly. Sadly I didn't recovery any speific amount of size for the recovery image. If the android OS runs much like a computer, First it will check the bios, bootloader, recovery, and then load the rom, or start to run the enviroment for the android operating system. Can someone check what those the update-script say in the deathspl.
Click to expand...
Click to collapse
When you went into broken recovery, you did so using the HOME-POWER boot-time signal rather than using the forced/stuck mode. Therefore your observations don't relate to the issue at hand.
Sheldonjace said:
"The phone was jammed into boot mode 3 -- recovery, and ignored boot-time signals to alter boot mode -- specifically, the camera button, which should, under normal circumstances, activate FASTBOOT. It appears that boot-time signals are ignored when the device is not in normal boot mode."
I maybe completely off but here is why I support this theory:
G1's don't have a "BIOS" to be checked upon starting that determine where or what type of boot up to perform so you can quickly change the settings by pressing F2 to say "Boot Normal Boot first, then Fastboot, then Recovery, etc" like a computer can. What the OP is stating is that when the phone is bricked, it could be due to it being "Flagged" at trying to boot into recovery and not taking ANY other boot commands....even if the Recovery Image may have been corrupted (which if it did have a BIOS like a computer it would attempt to boot the next in line option you've set if previous option failed)...so this causes the phone to be rendered useless ie: Bricked.
SOOO thats why the last part of the original post says it would be nice to develop (if possible) a SPL that would not allow this flag to be set at Boot recovery thus helping avoid possible bricks. Since if it can't flag Boot Recovery, then if the image were corrupted it would at least accept other boot signals for Normal boot and FastBoot which in turn allow you to fix said failed image.
Does any of that make sense? its late and I feel like I'm rambling.
Click to expand...
Click to collapse
Yes. Sortof. Except that you mistake what a BIOS is. You are assuming the BIOS to be the setup program, whereas the BIOS is actually the first bootloader, at about the same level as some of the stuff in the radio image. The SPL on the phone would be roughly equivalent to GRUB.
Now as it happens, the phone's firmware actually *does* share some interesting similarities with your computer's bios -- specifically, that it *does* allow for you to flag different conditions. The problem with it is that it lacks the convenient SETUP program that your computer has... Note that it ***DOES*** have a setup program still though -- BLUE LIGHT MODE!!! Only problem is that we don't know the "password" for blue light mode! So it is like having a blank hard disk, a bios configured to boot that blank hard disk, and a PASSWORD you don't know on the bios configurations!
jubeh said:
the way i had envisioned it was IPL (radio) having a list of boot locations for SPL. Remember that SPL is the one that listens to user-input boot modes. The radios that are not compatible with the death spl were released before this spl was released (remember, it was originally the sapphire spl). Since the dream and sapphire share radio chipsets, the dream was able to use sapphire spls once a radio capable of booting it (starting with 2.22.19.26I) and had that particular spl available in it's boot list, then the spl could be booted with the appropriate parameters. Since on earlier radios the SPL hadn't been created yet, it wasn't on the list of the spls allowed to boot.
I haven't studied spl/ipl much codewise, but my findings come from theoretical analysis of spls among other htc handsets (my idea originally came from trying to figure out a hex-hack to spls that allowed them to be booted by any radio, then we could toss an android spl into a winmo device and have it boot the linux kernel).
The boot modes mentioned are spl dependent, so if the ipl can't find an spl, then the only option is to get the ipl to find the spl and boot it.
The real question would then be, how is the ipl finding the spl, and is there something we can do with spls (again, as a hex-hack) so that the appropriate value is returned to ipl when trying to boot spl and to boot that spl?
Click to expand...
Click to collapse
That is actually the same way that I *used* to envision it.
Which has now been PROVEN incorrect. Or at least not applicable to the dream-bricks.
ezterry has conducted an experiment in the jtag thread based on this theory I have presented here. What he found is that a 1.x radio ***IS*** able to boot 1.33.2005 SPL SUCCESSFULLY!!!!
In other words, this theory I have presented has been confirmed through experimentation!
We don't know if this combination is suitable for actually booting a kernel, but we DO know that when flashing this combination in a manner where the recovery-boot flag is NOT set, that we ARE able to get into fastboot mode and flash the radio image! Meaning NOT BRICKED!!!! Despite a radio/SPL combination that was previously assumed to be a GUARANTEED brick!
Further (this had occurred to me before but I just remembered), keep this in mind, all dream IPLS are capable of booting all Dream SPLs, regardless of board version (not to delve into t-mo dream and rogers dream, different radio, so for this purpose, different device). I'm pretty sure too that, had there been as many IPLs/SPLs for the sapphire, the same would have been true (and we'd have more death spls to try on the dream).
What that tells me is that whatever the IPLs of all radios are reading for in SPLs, it's present across stock/eng/hard SPLs. If that thing that is being read from or booted to in those SPLs can be copied over to the Death SPL, then we'd have a death SPL that's bootable by all radios. Doesn't fix any current bricks though >.<
Click to expand...
Click to collapse
Keeping in mind of course, that there is still a possibility of a radio/SPL mismatch brick, what I believe at this point is that EVERY 32A/B radio image can be installed in conjunction with EVERY 32A/B SPL withOUT any kind of risk of bricking!
As long as the boot-recovery flag is NOT SET!!!!
xaueious said:
Not so sure about any SPL + radio combination working.
Specifically there were some really weird cases of bricks for users flashing new radio and SPL for Magic (1.76.X HBOOT, 6.35.X RADIO) on a 32B Magic. Afterwards their ROM authentication always failed for some reason.
So there are combination that actually do not work?
Click to expand...
Click to collapse
I wouldn't consider that weirdness to actually be a brick. At least not of the same caliber as the dream bricks where it won't respond to anything. Lets call something like that -- "borked".
Reason I wouldn't want to call it bricked is that it is still responding and doing *something*, despite the fact that what it does is failing.
In this case, you cite an authentication failure... suggesting that the 1.76.X SPL is *not an engineering SPL*. Use of a non-engineering SPL, I believe, will always leave you vulnerable to signatures and authentication errors.
I also have to believe that if the 1.76.X SPL *was* an engineering SPL, then it wouldn't worry about authentication.
My first recommendation to everyone is that they ALWAYS use an engineering SPL (i.e. with UNLOCKED FASTBOOT). In fact, the FIRST thing I would recommend to ANYONE rooting their phone is that their first step be to flash a "compatible" engineering SPL -- by compatible, I mean if your stock SPL was 0.95.0000, then you first flash SPL 0.95.3000 by whatever means necessary -- if it gets jammed into boot-recovery using such a similar SPL, then it won't be a brick. Following that, one can change to ANY engineering SPL using FASTBOOT to again be guaranteed not to brick.
If there is no engineering SPL available that is similar enough to the stock SPL to guarantee that the recovery will be compatible, then all bets are off -- in that case, you could end up borked.
xxmonsterx said:
I wish there was a thread "like" button like on fb lol nice thoery
Click to expand...
Click to collapse
erlern said:
Sorry, digression:
Can we petition for one? Seriously, I have been seeing comments on having a 'like' button over XDA since the new revamp.
Click to expand...
Click to collapse
If you look at the top of the screen, you will find a "rate thread" tab.
lbcoder said:
Yes. Sortof. Except that you mistake what a BIOS is. You are assuming the BIOS to be the setup program, whereas the BIOS is actually the first bootloader, at about the same level as some of the stuff in the radio image. The SPL on the phone would be roughly equivalent to GRUB.
Now as it happens, the phone's firmware actually *does* share some interesting similarities with your computer's bios -- specifically, that it *does* allow for you to flag different conditions. The problem with it is that it lacks the convenient SETUP program that your computer has... Note that it ***DOES*** have a setup program still though -- BLUE LIGHT MODE!!! Only problem is that we don't know the "password" for blue light mode! So it is like having a blank hard disk, a bios configured to boot that blank hard disk, and a PASSWORD you don't know on the bios configurations!
Click to expand...
Click to collapse
Thank you kind sir for clearing that up for me!
I'm thrilled to hear this is confirmed to be true as well.
Wow. Way to keep an open mind, both OP and ezterry. So any time we change radio or SPL versions you recommend doing so through fastboot instead of recovery zip flashes?
r4d14n7 said:
Wow. Way to keep an open mind, both OP and ezterry. So any time we change radio or SPL versions you recommend doing so through fastboot instead of recovery zip flashes?
Click to expand...
Click to collapse
Unless you know FOR CERTAIN WITHOUT ANY DOUBT WHATSOEVER that the recovery image you currently have installed will work with the new radio or SPL that you are flashing, then ABSOLUTELY I suggest (1) sticking with fastboot, and (2) sticking with engineering SPLs (of whichever variety you prefer, be it 0.95.3000 or 1.33.2xxx).
The cases where you DO KNOW with absolute certainty that you will have no compatibility issues is when changing the SPL from a "consumer" version to ***ITS*** corresponding "engineering" version, i.e. from 0.95.0000->0.95.3000 or from 1.33.0005->1.33.2005.
You should ONLY use recovery IF you have this degree of certainty.
Note: 1) I would recommend that you ***NEVER*** write a radio image using recovery, (2) ONLY EVER update from consumer SPL to ITS corresponding engineering SPL using recovery.
If you are running (any radio) + (consumer SPL) and are ABLE to use recovery to update to (same radio) + (engineering SPL corresponding to consumer SPL), then you can be certain that it ***WILL*** work.
So the process for going from, for example, a current version tmobile firmware right through to 1.33.2005 SPL + whatever is this:
1) ROOT as normal (i.e. RC29NBH+telnet, install custom recovery image)
2) copy engineering SPL 0.95.3000 update.zip to sdcard, reboot recovery, write 0.95.3000 -- this is safe because you KNOW that the recovery is compatible/functional with 0.95.x000 since that's what you have and you are using recovery,
3) reboot in FASTBOOT mode,
4) fastboot flash the desired SPL and/or radio image.
Doing this, I personally guarantee to within 99.999999% that, barring unexpected errors, like power failure during write or other equipment failure, that this procedure will *definitely not brick* (to within 99.999999% certainty -- I leave myself 0.000001% uncertainty, so don't hold me accountable).
After the installation of Radio (radio-32A-6.35.08.29) through Power+Home, I restarted telephone and it was not turn on, also any combination of button (Power+Home, back, camera) does not work. Telephone is charging, but nothing is reacting. What to do? What is for telephone GOOGLE G1?
Sounds like you bricked your phone... Sorry to tell you
EDIT:// Actually I might be wrong,, But I doubt it
I'm sorry that I can't really help you, but unless your G1 is from Rogers Canada, this is the totally wrong version of the Radio to install on the G1. I don't know if this can be helped still -- there might be a chance to rescue it, search for a thread containing "JTAG Endpoints" (or perhaps just "JTAG") in it's subject and see the status of that.
--Tim
you are bricked
why did you flash a radio for a 32a to your 32b?
smooth move genius. should have researched first.
http://shop.ebay.com/?_from=R40&_trksid=p3907.m570.l1313&_nkw=jtag+adapter&_sacat=See-All-CategoriesThis link should help.
tsk tsk tsk..
that's why i better be a noob-like man asking alot of questions b4 doin such things, specially like that.
than loosing everything coz of self-understanding
always ask ask ask
it wouldn't kill you
u should learn now fron ur mistake :/
Firerat said:
you are bricked
why did you flash a radio for a 32a to your 32b?
Click to expand...
Click to collapse
Probably because radio version 6.35.08.29 seem more "updated" than 2.22.23.02.
I'm sorry for that guy's lost...
tnleeuw said:
I'm sorry that I can't really help you, but unless your G1 is from Rogers Canada, this is the totally wrong version of the Radio to install on the G1.
Click to expand...
Click to collapse
Wrong, the rogers dream supports the same software as dreams elsewhere in the world.. the newer HTC (ie. Non Google branded dreams) happen to use the 3.x radio rather than the 2.x radio.
Google branded dreams can run the 3.x radio but that is uncommon.
In short I don't think any dream can run the 6.x radio and be happy,
tnleeuw said:
I don't know if this can be helped still -- there might be a chance to rescue it, search for a thread containing "JTAG Endpoints" (or perhaps just "JTAG") in it's subject and see the status of that.
--Tim
Click to expand...
Click to collapse
Yes.. the 6.x oemsbl does still run on the dream.. but the spl wont boot. (Ie charges battery while off and can enter blue light mode.. but black display on boot)
This means jtag can be used to fix it. Just take note of the magic 32a w/ 6.x radio section in the jtag wiki page.
Did this a while back (um with the jtag testing phone not my primary phone) determined the radio booted oemsbl, but refused to start the spl, and when I forced it to load crashed nicely on boot.
So the only useful information achieved was how to flash back to 3.x.. and while that information is important for magic users that bricked with the 6.x radio.. dream users ought to stick with the 1.x, 2.x, 3.x radios.