Related
Hey everyone,
I am writing this because a day of research and playing about with my phone has resulted in nothing.
I recently rooted my G1 european (UK) phone and ended up with the JesusFreke build absolutely no problems...
Today I updated to the latest radio and SPL (again, no problems) and went to put on the Virtudude Roger's mod first and it froze on the splash screen, so I reverted back to original Android, rooted again and went back to JesusFreke's build.
This time I tried Cyanogen mod, which also freezes on the splash screen.
I have tried going to both these builds straight from Android 1.0 or from the JesusFreke build with no success - it just freezes on the splash screen every time.
Anyone have any advice? Maybe theres something I'm doing wrong on the way?! I use recovery mode to format and load the flash images on
So much thanks in advance!
After rooting the phone and then putting it on JesusFreke's build, you were trying to update the radio and SPL with the 2.22.19.26I radio and the 1.33.2005 SPL (Haykuro's "special" SPL - http://forum.xda-developers.com/showthread.php?t=517593)?
You do risk bricking your G1 with this SPL, but if you follow the directions in the thread exactly, you should be fine (do this at your own risk).
Also, make sure to do a wipe (Alt+W) in recovery before you try to apply (Alt+S) the build update.zip.
Nickizzle said:
Hey everyone,
I am writing this because a day of research and playing about with my phone has resulted in nothing.
I recently rooted my G1 european (UK) phone and ended up with the JesusFreke build absolutely no problems...
Today I updated to the latest radio and SPL (again, no problems) and went to put on the Virtudude Roger's mod first and it froze on the splash screen, so I reverted back to original Android, rooted again and went back to JesusFreke's build.
This time I tried Cyanogen mod, which also freezes on the splash screen.
I have tried going to both these builds straight from Android 1.0 or from the JesusFreke build with no success - it just freezes on the splash screen every time.
Anyone have any advice? Maybe theres something I'm doing wrong on the way?! I use recovery mode to format and load the flash images on
So much thanks in advance!
Click to expand...
Click to collapse
What SPL do you have? Are you wiping before you update?
Thanks for the great advice, I was actually following the instructions you provided and have 1.33.2005 SPL.
I just had no idea why it wasn't working, but I have now sorted it...
I put on the recovery utility from JFv1.43, format/flashed the image for Virtudude, restarted and then just left the house for a couple of hours whilst it was on the splash screen....just came back and it had booted in fine.
Now it boots fine every time (does take a few minutes to boot but worth it!)
So, all sorted now - again, so much thanks for the help - I honestly thought it was because I had an EU model or something like that; unfortunately, searching the forums for "EU" or "UK" doesn't bring up much because of the minimum character limit!!
So I guess it really is easy to brick a MT3G - can't fastboot, can't enter recovery.
Just stays on the MT3G boot screen.
I've tried all the boot key combinations, does anyone have any magic solutions that may work?
It was rooted just fine (from the first day rooting was discovered, using the gold card method). Tried to upgrade to a CyanogenMod, and somehow messed things up. I suspect I screwed up when I flashed the radio.
Hmph.
Why did you flash a "new" radio...?
The radio that comes standard as a packaged feature for the T-Mobile USA version of the HTC Sapphire (MT3G) is 2.22.19.26I - there was NO NEED for that adjustment. I'm not suggesting that flashing a new radio is what corrupted your device, but it certainly could have contributed to the eventual cause.
The One-Click Root Method is the safest way (until patched via Google 1.6 build - also known as Donut) to ROOT your MyTouch. I've used that for three various Android devices, all of which functioned properly immediately after. No flashing of upgraded radios, SPLs, etc.
Finally, from the beginning - as any ROM flasher should know, you SHOULD HAVE backed up your STANDARD, T-MOBILE PROVIDED, Cupcake v1.5 build using NANDROID from the Recovery image. If that is the case, restore those settings and start all over with the "rooting" process using the One-Click method via the Recovery Flasher application.
Good luck.
damn i think i brick my phone after loading a radio ugh it sux
Again.
Tobi87 said:
damn i think i brick my phone after loading a radio ugh it sux
Click to expand...
Click to collapse
Re-read what I posted previously.
The MyTouch comes standard with the latest radio and and SPL (even if considered PERFECT) doesn't prevent you from running any of Cyanogen's latest builds. I don't see why you thought that flashing a "new" radio was going to do something special. As for the "Gold Card" method...I don't see why you didn't think to try the easier, safer, much less work type of method. THE ONE-CLICK ROOT METHOD!
Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition
That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer
You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!
Turn your phone off, hold the camera button down, and power on your phone.
What do you see?
each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.
speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer
speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer
Hi,
Already posted part of the situation in Amon_RA's recovery thread but neither of the answers there seem to solve my problems. Decided to post it here since the problem seems to involve aspects other than the recovery itself.
Here's the complete situation:
Had problems with RA recovery freezes since the start and with different versions. I could (and can) enter recovery mode (v1.6.2), scroll down the options but after 15 seconds the recovery just freezes and reboots every single time. Checked the version (H) and the MD5, they where all correct. Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Tried booting the latest RA recovery trough fast-boot and it worked fine the first two times I did it (scrolled down the options for like 10 minutes and it didn't freeze). After that it did not work and got the freezes+rebooting problem back again. Tried ADB, Flash-rec and flashed the recovery but got the freeze+reboot problem once again. Re-checked the version and MD5 and they where all correct.
Why does this happen? Any clues?
Thanks for your help!
I'm kind of lost here...Could it be a radio or SPL problem? Should I re-flash/update it? I never had problems with the stock ROM so this situation is really odd...
Can anyone help?
Thanks in advance!
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
But anyways, I'm a bit confused. What rom are u using?
noroses said:
Hi,
Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Click to expand...
Click to collapse
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
I have no idea dude but what I would do if I was in your situation:
1) Flash ENG SPL, something like 1.33.0010 (double check everything, i dont like advising people to play with their spl/radio so dont just take my word)
2) load up recovery and give it a try! if all that fails...
3) I'd backup your phone via nandroid in recovery (i pray that it doesn't freeze lol)
4) Wipe wipe wipe
5) Go into fastboot, fastboot erase system -w and then try another rom! And if the rom is good, then go back to your old one. Try to find out what the prob is.
It appears that you're able to flash roms still even with your recovery freezing (so weird) so I dunno. Just give it a try I guess lol
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Hi,
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
Click to expand...
Click to collapse
Will try this. Can I flash the SPL trough the recovery?
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
Click to expand...
Click to collapse
Will have to check and recheck this complex process.
But anyways, I'm a bit confused. What rom are u using?
Click to expand...
Click to collapse
Now I'm using stock 1.5. I tried cyanogen, superD and other 1.6 Roms and they all freezed at the android setup process. Used myhero for a week with no problems whatsoever. Since I have a nandroid backup done with CM's recovery I restore everything back as it was.
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
Click to expand...
Click to collapse
The Amon_Ra recovery freezes every time. It doesn't give me enough time to do anything...Now I'm using CM's recovery and I have no freezing problems while in recovery mode. The problem is after I flash a Rom and reboot. The ROM experiences freezing problems (just like the Amon_Ra's recovery).
Thank you for your answer and suggestions!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi,
Thanks for your answer.
I have never tried with the phone plugged into a socket but did it with the phone running on battery and connected via usb to the computer. Should it make a difference?
Could it be a hardware problem? I never had problems with the stock ROM or with the myhero ROM...
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
digitaljeff said:
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
Click to expand...
Click to collapse
Checked that guide but I'm unsure about this part:
If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
Click to expand...
Click to collapse
This part I can do within the recovery to enable flashing via fast-boot right?
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
digitaljeff said:
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
Click to expand...
Click to collapse
Will try that tomorrow.
Thanks for your help!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi again,
Still didn't mess with SPL and Radio. I'm still afraid I'll brick the phone..However yesterday tried a few simple things like using another sd card or entering recovery while plugged in. These two things seem to influence the behavior of the latest Amon_RA recovery but don't solve my problem completely. Example: When I enter recovery using the original SD card (2gb) the recovery would freeze within 20 secs max. Using another SD card (128mb) most of the times it would take longer to freeze (4 or 5 minutes). Sometimes it would not freeze at all. Although this seemed to influence what happened it wasn't constant and could not find a pattern. The same with the phone plugged into computer. Sometimes it helped. One thing is certain: with the original SD card and unplugged from the computer the recovery freezes within 20 secs every single time.
With the CM 1.4 recovery never had any freeze problems. It seems to work great while in recovery mode. The problem is after a flash a ROM I have freeze problems with the ROM itself (tried different ROM's, CM, SuperD, etc and got the same freeze problem). The only Rom that worked fine was myhero 2.0.5.
This is a very strange situation and I'm starting to think that this could be hardware..
Would that be a SD card problem?
try using another SD card and see if the problem still occurs
I am having exactly the same problem, did you ever find a solution?
Went from a fully updated magic 32A (1.76.0009H) now i'm at 1.76.0008
UPDATE: I just found that the hero recovery works (I would post link but xda doesn't allow new users to do that) however it may still be necessary to downgrade radio and spl
I had also same problem. My device is Magic 32A radio 6.35. Solution was to reflash recovery-RA-hero-v1.6.2.img.
Hi,
First time posting so please excuse my ignorance
Here is the problem.
I am (was) the happy owner of a HTC Magic 32B, which I successfully upgraded to CM 6.0, with radio 2.22.19.26I and SPL 1.33.2005.
It worked well but quite sluggish so I decided today to upgrade to CM 6.1.
I did, it was incredibly smoother but I had some troubles with the internet connection: sometimes, the phone would start uploading (the little upload arrow was on, on the icon of the taskbar) while the download stayed flat.
I thought I should try a new radio and SPL.
Now I'm stuck with this:
- radio 2.22.27.08
- SPL 1.33.0013d
- I am able to get to the fastboot and recovery (Amon RA 1.7.0)
- the phone keeps booting in loop
Besides, I can't flash anything from fastboot (or recovery for that matters) because I get this message:
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
Is there anything I can do to get my phone back?
Thanks in advance!
EDIT:
OK well, fixed it.
Reflashed radio 1.33.19.26I and SPL 1.33.2005 through recovery...
I might have skipped a reboot while first flashing which would explain why it wasn't working.
Still, this radio doesn't seem very good : wifi is not reliable, UMTS/HSDPA neither.
I saw somewhere that the radio 1.33.19.26I is for non-US (which is my case) and others are for US versions.
What are the radio versions I could use?