Database Develop

Can't flash radio, no GSM error, need help

Hello
I downloaded the new radio this morning
when tried to flash it to my Trinity I've got "connection timeout" error
now when I start it there is an error "no GSM"
and it freeze in the HTC screen
I searched the forum for all day, flashed alot of radios, hard-spls and so on but didn't manage to flash a working radio
Please give me some instructions or a link the the right thread
I have original HTC rom with SPL-1.30 Olipro
Thanks

exactly the same problem here, need help guys, anyone?

checkout this site for more info that may help you. i had to downgrade/reflash to SPL 1.20 Olipro, flash the new Radio and then reflash to SPL 1.30 Olipro.

I managed to fix it
download this file
http://forum.xda-developers.com/attachment.php?attachmentid=43539&d= 1184192788
in ActiveSync go to connection settings
uncheck the allow USB connections
restart the device in bootloader mode and connect it to PC
run the .BAT file
the device will boot in bootloader SPL 1.2
now you can flash ROM\RADIO
good luck

yes, if you're having trouble flashing radio, please use Hard-SPL 1.20 olipro

wow guys thank you, you saved me 600 eur, i've read around the forum that htc wouldn't have given me warranty rights with the modified rom installed on the trinity, actually the radio update process is around 40% (while it wasn't going further 7% before). So i assume everything is working correctly.
After the radio i'll be installing the UDK4 WM6 again and everything should work correctly now (so to prevent any other less experienced guy to have similar problem, if he wants to upgrade both main rom and radio rom, i suggest is better to upgrade the radio rom before, don't you agree?).
thank you guys, i'll let you know my feedback as soon my trinity is up & running again

thanks you all guys, everything works correctly, i didn't know that we could reinstall any rom with a "bad flash / brick" problem without sending it in htc assistence.
The problem was regarding only the Radio ROM, that was completely missing after the bad upgrade. Didn't have to reinstallo the Main rom (UDK4 In my case).
Thank you all again, i wasn't able to sleep thinking about this thank you can have a good night now
Regards,
Michele!

racerx_ said:
yes, if you're having trouble flashing radio, please use Hard-SPL 1.20 olipro
Click to expand...
Click to collapse
Where to get this? I only find V1.30. Thanks!

download it here .. look at post #85

Thank you very much! I didn't find it!
Bye, Peter

I have a siilar problem. I had flashed radio 1.46 completily the progress were up to 100 %, but when I soft reset the device say "No GSM", only if I put off batery during 10/15 seconds it is all right,
Whats is hapenng????
Any solution????
Thanks

I have the same problem too...
Dispositive info no said nothing about radio version.
I've load Olipro but if I try flash it with a radio version it dont pass of 0%
What can I do?
Best regards

Same 0% problem
Ayasystems, I have the same problem of ROM update not going over 0%... how did you fix it?
Thanks in advance

nirgur said:
I managed to fix it
download this file
http://forum.xda-developers.com/attachment.php?attachmentid=43539&d= 1184192788
in ActiveSync go to connection settings
uncheck the allow USB connections
restart the device in bootloader mode and connect it to PC
run the .BAT file
the device will boot in bootloader SPL 1.2
now you can flash ROM\RADIO
good luck
Click to expand...
Click to collapse
How long does it takes to complete this part of the program?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It seems if he stucks with this part by me. How can I check if it is still working? What do I have to do now? Retry it again? Or..?

I tried many of the solutions here to fix my "no GSM" error message. I even sent it to Pocket PC techs. They "remolded" the chip.?? I don't know what that means or even if I said it right. I recommend their service. BUT, that still didn't solve the problem. I finally bent the sim card brackets down to hold the sim card a little tighter, and it worked. Haven't had any problems since. I spent months and about 100 US to fix this and thank God it works now.
I really think it was a combination of what Pocket PC techs did, plus bending the brackets down. I don't think any of the software fixes helped at all.
Hope this helps out. Blessings all!

I think I bricked him :(

Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.

jackaz said:
Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
Click to expand...
Click to collapse
Yes, its gone. You need to install the radio update before the SPL update. Don't know why you would install the update that kills so many phones without reading up on it...

for the record: cm4.0.4 and all cyanogen mods do not require the DangerSPL, hardspl works fine.

Wow you get a big ol' F for not doing your homework and thinking that you needed the newest thing, good job screwing yourself

Just like everyone else said your toast. I was first thinking why would you need to go back to rc29 because of an apps2sd issue or really any issue, you should have just reflashed a rom. Second (like the others said) you didn't need the new spl.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

WTB - spare batt and batt cover!

Whoa, didn't need to jump down my throat - I already flashed the new radio after HardSPL, but I suppose it doesn't matter anyway.
The phone bricked after installing that app, and upon restart it was stuck at the G1 screen, I had to leave the office so I reflashed to RC29 (as it was the only ROM I had on my laptop) while I was on the road (so no internet access) because I desperately needed my phone for a job I was attending. When I got back to the office I must have mixed up my update.zip files somewhere in the process.
Thanks for the help from the people that weren't dicks about it, at the end of the day it's only a phone. Time for a shiny new one.

It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.

Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?

dcorrea said:
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
Click to expand...
Click to collapse
Correct......

downgrading by using rc also downgrades the radio and spl, does not matter what spl you are using. it takes it back. you will not brick by using the rc dreaimg.nbh

r4d14n7 said:
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Click to expand...
Click to collapse
Thanks for that information.
I'd play the stupid card but I'm guessing that being in Australia makes that pretty difficult eh?

hey you guys have an awesome prime minister

He gave use all $900 just for the fun of it. Great guy.
I guess I can try contacting HTC and see if they'll repair it, I'm expecting to pay for it but i guess it's better than paying for a new phone.

i was talking about his policies, like telling everyone that this is our country and that we will not bend over backwards to appese you and if you don't like it then get the **** out. we need someone like that guy here instead of ass kissing obama
sorry small rant
yeah you could call htc

Haha I know you were
I've got in contact with the repair center in my area and they're going to 'get back to me'.

Flashed another device´s ROM into Rhodium and bricked :(

Hi,
A friend has a CDMA Sprint Rhodium, and he tried to install with a Raphael ROM into Rhodium and since that device won´t turn on.
When connected to PC turns the led in red and it says "Qualcomm CDMA MSM driver needed" but nothing happens...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there anything I can do to help him? or device can´t be repared?
Any advice is welcome
Thanks in advance,

i think you should contact jockie

Thanks for the advice, I´ll contact him.

Can he get the phone into the bootloader ?
Not sure that driver message is connected with the problem though, when you turn on a GSM Rhodium connected to the computer it normally wants a CDMA driver.

well, if the device is making a connection with the computer, then it's turning on. it may not be displaying anything, but at least you know it's still working. so, remove any SD card you may have and if you have a SIM card, remove it (i believe you said CDMA, but you are in the GSM forum, so...) Now, this will take some dexterity. first, remove the battery. Now, while depressing the volume down key slip the battery into the phone and quickly press and release the power key while still holding down the volume down key. either instantly or within a few seconds you should get the tri color screen. once this occurs, try hooking the phone back into your PC and running a custom ROM that is for the proper make and carrier style

guys, hes not a newbie, and knows about bootloader mode
this case isnt regular, so i advised a man who can really help with it, as i got help in similar situation

The "Qualcomm CDMA" driver installation comes up on your PC even on GSM phones.

try to download this driver from internet, it's for windows xp
then inter the bootloader and flash the original rom

hehe, the problem is not in drivers, drivers isnt a problem, you can use practically any qualcomm device driver (e.g. motorola Q)
the htc usb interface cant be found here (htc usb sync)

Can you get into bootloader screen or wont that even come up? If it does best thing would be to put a stock rom on an Sd card and flash from there.

I guess this is the problem that Nykoon had few days ago.
See, the phone has Raphael's bootloader. The CPU aren't the same (MSM7200A vs 7201A), nor the rest of the board. The bootloader can't make USB sync, so it somehow probably goes into some failsafe bootloader... but without proper files from HTC it can't be recovered.
Maybe jockyw can do something about it, but all at all - JTAG will work fine.
For all - that device doesn't go even to bootloader probably. If it went into bootloader, you would see at least HTC USB Sync (or microsoft usb sync). We tried with Nykoon on ICQ many things, but no way of flashing anything on it.

Thanks a lot guys, with your guidance we were able to bring it alive!!!
Thanks a lot to all
-----------
Vote, check my sig!

Hi, can you help me please, i have 1 with the same problem, please help me to flash the device, thanks in advanced

orb3000 said:
Thanks a lot guys, with your guidance we were able to bring it alive!!!
Thanks a lot to all
-----------
Vote, check my sig!
Click to expand...
Click to collapse
Please post the solution.
May help others in the future.

this has happen twice to me, fixed both times
all you got to do is put it in bootloader Mode (hold down vol down and push power button) then go to att, or tmobile .com and download the original factory ROM, (with original .exe) load it and the phone works perfect, then you can load any custom rom you want after that
for some reason, over time, with all the flashing, files just don't transfer correctly, one file here, one file there, and it takes the original factory ROM built by IN-HOUSE team at Phone Carrier. and not the made in the basement
Roms we have on here, I have flashed all of them, and love Energy, but for
some reason, Agent47 Valkarie roms, usually after some use, make my phone
Brick and lock and all kind of stuff, but reload ATT factory exe rom and Re-Flash
with NRG and thats it,
let me know how it works out

Absolutely bricked?

Story, in key point format:
-Just moved, no internet at home yet (in fact I've been using tether since I only check e-mail and use FB anyway)
-At cafe... Already closed, but they agreed to let me stay about 5 minutes past closing time, no time to search. NO N00B/"SEARCH FIRST" COMMENTS PLEASE.
-Don't have any old phones
-Just got a new girlfriend and didn't think much about emergency expenses and spent most of my $ on wine n' dine with her (but at least I got some worthy "dessert", but that's another story).
-Just lost my job a week after meeting her (I stayed up all night, eventually gave into a "food coma" [see above] and came into work late) LOLOL... Woulda had a new phone budget if I was around for another 2 weeks, but noooo....
Anyway:
-Tried to install CM5 onto G1
-Installed it with the CM bootloader (or something like that, it had an orange font)
-Downgraded to RC29, successfully loaded AMON_RA
-Installed DangerSPL, rebooted per the instructions
-Stuck on the boot screen for almost exactly half an hour (5 mins after 8PM until 8:30PM), said "WTF" and pulled battery out
-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work (although when you push end+trackball the blue light turns on, whatever that means)
With that in mind, what should I do? Any hope?

Hmm well Im not an expert like most of these other guys by ANY means, but in my experience I've learned that removing the battery during a percieved "hangup" is a sure fire way to brick a G1. Trust me Ive done it, not fun.
If you can make it to the recovery screen somehow, theres still hope. On the Cyanogen Wiki, I believe theres a type of method for reflashing a rom, by booting while holding the camera button. I would recommend researching that.

Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.

You forgot to flash a compatible radio!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BoomBoomPOW said:
You forgot to flash a compatible radio!
Click to expand...
Click to collapse
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.

DAMNITS!! I only read the "steps" portion of the instructions on the Cyanogen Wiki, which didn't even include the "radio" portion of the equation (I edited it just to avoid other people having the same problems).
lbcoder said:
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
Click to expand...
Click to collapse
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Acecalibur said:
...by booting while holding the camera button. I would recommend researching that.
Click to expand...
Click to collapse
"-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work"
lbcoder said:
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
Click to expand...
Click to collapse
Well, I was (somewhat) following the steps of the Cyanogen wiki.

EdWaRdW818 said:
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Click to expand...
Click to collapse
Your information is wrong. There's no baking, there's no removing chips. There is just interfacing with the board. If you're handy with a soldering iron, its a cakewalk.
Well, I was (somewhat) following the steps of the Cyanogen wiki.
Click to expand...
Click to collapse
Finding all your information in one location? What makes you think that your SINGLE SOURCE of information was accurate or correct? For all you know, it was written with the INTENTION of screwing you up.

Fix bootloader without goldcard

Requirement:
-Y Cable
-USB Memory (I used USB adapter and SDcard 8Gb)
1.- If you don't have Y cable you can make it
2.- Test your Y cable
2.1.- Put the USB adapter on your pc to test it, if the windows read the SD card, your cable working!!.
3.- Format the SDCard (FAT32)
4.- Copy the NBH file to USB(I used RUU_Schubert_HTC_Europe_1.54.401.01_Radio_5.51.09. 29_22.32.50.10U_by_ansar)
5.- Rename the file (SPL_signed.nbh --> SCHUIMG.nbh)
6.- Conect the cable with USB adapter (turn off phone)
7.- Put your phone on "usb mode" (Vol Down + Camera botton + Power)
the phone will start read the memory immediately, sometimes the phone don't start on "usb mode", for a few minutes don't happen nothing, after that the phone autorestart and read the sdcard
When the phone upload the SCHUIMG.nbh, you will fix the bootloader and Downgrade after all process used DFT_XSPL_WP7FG1 and change the Rom!

u mean use a sdcard to usb adaptor?
any pictures to show?

does this work on semi-bricked devices?
has anyone tried this?

biernes_atrece said:
does this work on semi-bricked devices?
has anyone tried this?
Click to expand...
Click to collapse
Yes this can work for semi/small bricked devices.
It's basicly the the same process and principal as the goldcard method except that you don't use the goldcard tool and image to turn the SD card into a goldcard.
You should also use your devices specific stock/shipped rom. The rom in the OP is for Europe devices.
You can find out which specific rom you need to use by the last 3 digits of your "Firmware Revision Number" eg, .401 = HTC Europe operator. .531 = TMOUS operator.
If you want you can post back your devices Firmware revision # and I can tell you which rom you need to use.
If you use a device specific Pre-NoDo or NoDo rom and downgrade the devices SPL to at or below 3.xxx you can then install XSPL (RSPL/HSPL) to the device and then flash a custom rom of your choice.
There's the goldcard tutorial here, which also will repair semi/small bricked devices too and it has the links to the stock/shipped roms.
http://forum.xda-developers.com/showthread.php?t=1597837
If you need any help just let me know!

xdrc45 said:
Yes this can work for semi/small bricked devices.
It's basicly the the same process and principal as the goldcard method except that you don't use the goldcard tool and image to turn the SD card into a goldcard.
You should also use your devices specific stock/shipped rom. The rom in the OP is for Europe devices.
You can find out which specific rom you need to use by the last 3 digits of your "Firmware Revision Number" eg, .401 = HTC Europe operator. .531 = TMOUS operator.
If you want you can post back your devices Firmware revision # and I can tell you which rom you need to use.
If you use a device specific Pre-NoDo or NoDo rom and downgrade the devices SPL to at or below 3.xxx you can then install XSPL (RSPL/HSPL) to the device and then flash a custom rom of your choice.
There's the goldcard tutorial here, which also will repair semi/small bricked devices too and it has the links to the stock/shipped roms.
http://forum.xda-developers.com/showthread.php?t=1597837
If you need any help just let me know!
Click to expand...
Click to collapse
thanks for reply.
my frn is 2250.21.51201.728
but i cant do a thing right now since i sold my laptop and wanted to buy a new one. i only got the surface right now.
ill tinker with my phone after i get the new pc

biernes_atrece said:
thanks for reply.
my frn is 2250.21.51201.728
but i cant do a thing right now since i sold my laptop and wanted to buy a new one. i only got the surface right now.
ill tinker with my phone after i get the new pc
Click to expand...
Click to collapse
Oh ok.. Well when your ready and if you need help just let me know.
.728 = HTC Asia SEA operator.
So you can use this rom to extract the ruu_signed.nbh file and rename it to SCHUIMG.nhb for the Y cable method or goldcard method.
http://www.mediafire.com/?w5x5y51fst2gccy

Here some pictures!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Work in semi-bricked!

my device firmware revision number is 2250.21.40505.502
its bought from AT&T us
and imported in india...
pls tell me which rom I must used to recover my device...
thanks

Try this: RUU_Schubert_HTC_Europe_1.54.401.01_Radio_5.51.09. 29_22.32.50.10U_by_ansar

Again and again, the troll...
Magpir said:
u mean use a sdcard to usb adaptor?
any pictures to show?
Click to expand...
Click to collapse
This user really shows some attention deficit or a mental disorder, sometime he's a "newbie" and other times he's an expert at ROM flashing...
Some examples of the not so newbie:
Magpir said:
4.5 allows u to downgrade to nodo
1) flash downgrade to nodo
2) run the cotulla DFT tool
3) install custom rom
Click to expand...
Click to collapse
Magpir said:
u dont need to downgrade to NODO or any earlier version but however take care not to unkowingly update yr bootloader by flashing a stock rom
This happens if u update yr phone in zune or flash a stock rom that comes with the bootloader inside it
because zune updates come with bootloader
Updated bootloaders will lock yr phone and prevent u from flashing custom roms
Click to expand...
Click to collapse
Diagnostic: posting just to increase his numbers...
Total Posts: 1,536
My advice help whoever ask for help, except this so called "newbie"...
Now I know why some developers have left XDA...