Hello,
I recently acquired an i-mate and before doing anything, decided to perform a ROM upgrade. It started with ROM version 1.66.00WWE and Radio version 1.10.00. I followed all the instructions on the clubimate website. The ROM upgrade (Step 1) went well, until I started the English Language customization (step 2). That program froze on my computer and left the i-mate in bootloader mode, even before starting the Extended ROM upgrade for the customizations. When trying to upgrade the main 1.72 ROM again, it gets stuck at the Radio Stack Upgrade (to version 1.14) at 14%, then either exits with no message (Win XP), or gives a Radio Stack Upgrade error message (Win 98 ME). The phone meanwhile says that it is perfuming the radio stack upgrade and to please wait. Waiting for an hour yielded no change. The following is the log file entries of the part for the Radio Stack upgrade:
03:06:42 Connection with USB
03:07:52 Begin Stage 4
03:08:22 Radio Erase retry 1
03:08:59 Radio Erase retry 2
03:09:15 Stage 4 Complete
03:09:15 Begin Stage 5
03:09:15 Write block1
03:09:26 Write block2
03:09:32 Write block3
03:10:08 Radio Update data retry 1
03:10:16 Write block4
03:10:24 Write block5
03:10:32 Write block6
03:10:40 Write block7
03:10:49 Write block8
03:11:25 Radio Update data retry 2
03:12:01 Radio Update data retry 3
I tried many times, but get the same result. I followed all advice on this forum and searched all over for solutions, from getting the device into bootloader mode (power button + action button + reset), making sure that my PC does not have any other USB device connected, that the only programs running are the upgrade utility and ActiveSync 3.7.1, etc.
I also notice it takes approx 1 hour from start of upgrade until the Radio Stack Upgrade, instead of the advertised 30 minutes. Someone mentioned that this Radio Stack Upgrade problem may be caused by a security feature on the Radio Stack ROM preventing the installation of older versions. However, I am installing the newest (ver 1.14), so this should not be a problem. With a hunch, I decided to try the English Language Customization (1.72.800) upgrade again, and the extended ROM upgrade worked, but still no Radio Stack. So now I ave everything upgraded, but a blank Radio Stack.
Now when performing a hard reset, I get the blue screen with "i-mate" written on it. In the bottom right only the version of the ROM "D 1.72.00 WWE" is shown, but it says "No GSM" right above it. It takes approx. 15 minutes to boot (with blue Bluetooth LED flashing), then goes through the screen alignment and intro procedure. After that, it installs customization and boots again. It takes another 15 minutes to boot and the phone functions only as a PDA. Even a soft reset takes 15 minutes (with Bluetooth LED flashing). I tried upgrading again after that, but no use. Going to "Device Information", I see the versions of ROM and Extended ROM, but the Radio and Protocol are blank.
I tried phased upgrading, where I would include the main ROM upgrade file into to the directory where the archive was extracted, then extended ROM, then radio stack. Everytime the radio stack upgrade failed (i.e. stuck at 14%), I would try to upgrade that part only, since all others upgraded successfully.
I am really out of options. Any help would be highly appreciated.
Thanks!
I asked Carrier Devices (clubimate) about this step 2 because on the official download page all I saw was the step 1, no step 2 and no link to download.
The answer I got was there is no english customization 800, only a beta. The customization or step2 would be presented for arabic or telstar etc based on your IMEI # not for english it is contained in the first .exe
So you MUST have got this 800 customization and maybe the main upgrade from on here because it was never on the offical download page. Only the BETA from the FTP which some hacked into on clubimate and posted on here.
Go to the official download page on clubimate (register if you havn't) and dowload the official .exe upgrade (one file) and see if it will run. Don't get it from here.
RUU172126WWE_imate.exe
Hard reset a couple times and that should be it. The upgrade does take a LONG time to do.
If that does not work, you might have to do a warranty repair, I would use the online chat support on clubimate, just watch for when they are online and ask. I don't think you can just flash the radio portion.
I find 1.72 VERY stable and fast. Good luck!
Hmm.. All files were downloaded from the official clubimate website (I had to register in order to download). Talking to customer support, they were aware of the Step 2 customization file on their site (they recommended it, too). I doubt I downloaded hacked ones.
Still a loss on what to do, other than take it to a service center, that is (anybody do that? was it expensive? took too long?).
I tried a suggestion where I extracted the Radio Stack ROM upgrade file from version 1.66 and installing it separately. Still stops at 14%. I also tried a full reflash back to 1.66, but also same result. Took it to an i-mate service center nearby, was surprised that they didn't even know how to put the i-mate into bootloader mode (I had to show them)! All they could do was try reflashing using the same utilities we use (still no luck). They said that anything more elaborate would require sending it to Dubai. So much for "service" center. So, no luck there, either.
Also tried to reflash to the orginal 1.00 ROM with 1.05 Radio: The upgrade utilitiy that came with that version won't go past the small "please wait...." screen. Just sits there.
Really sad. I didn't even use this phone (figured that the best start is to perform a ROM upgrade). I'm not that impressed with how fragile ROM upgrading is (and I am careful with using only official releases). I thought after the Wallaby, things would be more robust. Maybe I shold dump this thing and get an HP h6300 series.
Note that I managed to successfully upgrade to 1.72 at least once. It was only when trying the 1.72.800 customization did things start to go south.
Also, does it matter whether the SIM card is in the phone or not while upgrading? Instructions are not clear, although they did mention that the phone will behave as if it is out of area.
Another question (desperate and a long shot, maybe stupid), Do SIM cards from say T-Mobile have an effect on i-mate phone Radio Stack ROM (i.e. lock it, etc.?)
ANY help would be appreciated!
i-mate and bootloader
I just got to see the problem as I am going through the same search for answer. How to get to the stage of bootloader? Somehow I feel that the device has crashed: While I was trying to install the upgrade RUU172126WWE_imate, my laptop, and for some odd reason, shut itself down, then auto restarted. The i-mate from that point on did not respond and in fact all lights on the device went blackout. I tried soft and hard resets but to no avail. I even removed the battery for several hours and when I re-installed it, all what it gave me was the word i-mate (but no backlight). Any advise on how I can get the device functional again.
Thank you.
Put your device in bootloader (press the Jog button and the Power button at same time and press the reset switch). Place it in the cradle and re-run the upgrade. That should work OK.
Jog
Thanks for the quick reply.
Power and reset button I know, but I am not familiar with the Jog button on the i-mate (Pocket PC PE). Appreicate your help.
Its the multi-directional button in the middle at the bottom. Press it straight down.
Related
They basically told me you guys over here at this forum are more intelligent in this area. I've searched this forum and couldn't find any solutions to this problem so I have posted this message with hope that it will be solved.
Here is a copy of my message I posted on www.clubimate.com
ORIGINAL: dhilgaertner
This is absolutely rediculous. After upgrading to 1.66 my iMate has stopped working entirely. After talking to iMate support on 4 different occasions, I've gotten the same responce over and over.
Here it is:
Dear Mr. Dustin,
Regarding the online chat, please find below the necessary steps to reload your device with the ROM image.
1. Make sure your I-mate Pocket PC is not connected to the PC
2. On your Desktop PC, open Microsoft ActiveSync, then go to File > Connection Settings > Remove the Selection from “Allow USB Connection… “
3. Make sure your Device is on Boot loader Screen* (start up screen)
4. Reconnect your I-mate Pocket PC to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle ( Don’t use the IrDA for the Upgrade )
5. Run the Upgrade again and it will work fine without any problems
*Boot loader Screen – Hold the navigator button (round button in the middle of the answer/hang up buttons) and do a Hard Reset (Hold the power on/off button while pressing the small whole button on the bottom left of the device) simultaneously.
For any clarifications/queries, please do fell free to contact us and we shall be glad to be of assistance to you.
Regards
Sunil Kumar
Technical Customer Support
i-mate™ from Carrier Devices
Office No. 207-213
Building 11
PO Box 500085
Dubai Internet City
Dubai, UAE
Fax: 00 971 (0) 4 390 4428
Tel: 00 971 (0) 4 390 1989
www.carrierdevices.com www.clubimate.com
This E-Mail Message is confidential and intended solely for the addressee. If you are not the intended recipient, please return to sender. You must not copy, distribute or disseminate the information, or take any action in reliance of it. Any information, opinions or statements expressed in this transmission are those of the individual sender and, except where the sender specifically states them to be the views of Carrier Devices Ltd, does not represent the view of Carrier Devices Ltd. Warning: Computer viruses can be transmitted by E-Mail, it is strongly recommended the recipient should check this E-Mail and any attachments for the presence of viruses as Carrier Devices Ltd accepts no liability for any damage caused by any virus transmitted by this E-Mail.
Click to expand...
Click to collapse
Each time I've replied with "I've already done that and it still doesn't work. The rom update errors when it tries to update the radio image. Then it doesn't complete the rom update and the imate still doesn't work. No matter what I do or what version I try to update to it always gives me an error during the rom update. I can't even get into my phone anymore. I now have a $850 paper weight and tech support that isn't even worth a dime. I've talked with Ali and Karl at iMate Support both were unhelpful and eager to get me off the line. Ali even told me to call him tomorrow because he had to go home!!!! You call that tech support?
Now for the last time here is my problem:
[ul]
[*] My iMate will not boot past the blue screen.
[*] I've followed the steps above of disabling usb on activesync and installing rom
[*] 30 Minutes into the rom install (right where it starts doing the radio update) it errors.
[*] The error comes from the rom setup, not the imate, not activesync.
[*] The error tells me to do the above steps and try the rom update again.
[*] Once again the radio part of the rom update fails and tells me to try again.
[*] Infinite Loop!!!!!!!!!!!!!!!!!!!!!!!
[/ul]
I apologize for being angry, but this device is crucial to my job and is costing me thousands of dollars in lost sales and marketing revenue while it doesn't operate.
Click to expand...
Click to collapse
When you run the ROM update, are you still trying to run the 1.66.131 ROM? If so, you might want to try the 1.52.113 ROM to see if you can at least get your device back.
When the Radio update failed how far did it get into the Radio update, (what percentage?)
I had a similar problem when trying to downgrade, the Radio failed at 12%, (which I was told was a security feature)... either way, what I did was in this...
1.66.131 - Update, (which worked for me)
1.03.00 - Downgrade (which failed at the radio stack and would not boot)
I then went into bootloader, (reset, power, up) and you should see Serial/USB 1.01 screen...
Then put the device in the cradle and ran the 1.52.113 'update' and the device was fine (back to 1.52.113)
I had a similar problem were the upgrade failed part way through updating the Radio stack (after the Erase).
Fortunatly the main ROM had upgraded OK and I simply hard reset and started again.
Some things I have noticed:
1) Never leave the PC unattanded - stop it from going into screen saver
2) Make sure all programs are shut down on the PC - Too much activity causes my USB ActiveSync link to close
3) Close Firewall software - I use ZoneLabs and the upgrade hates it
Just a few things to try
The other thing you can try is performing the ruu when the device is in Bootloader. Press and hold power, the Actio key (in the middle of the Joystick) and soft reset.
Connect your device to the PC and run the ruu update.
That should work.
Where do I get a RUU for iMates? iMates website doesnt have one.
Also the radio stack update fails at the beginning of the erasing part, it is still at 0% when it errors.
The clubimate site does have the RUU for both 1.66.131 and for 1.52.113, goto Tools\Device\iMates\Full Device etc...
Its towards the bottom...
Yes that is the same update that gives me the error when I get to the Radio stack part of the update. It leaves me with a 1.66 rom and a blank radio and protocol version (if you were to look in device information).
??
Did you recently get your device? Did it come with 1.66.131. if not, then this really should have worked; unless there is something actually wrong with your device? Did you possibly put a different ROM on before the 1.66.131 like a TMobile, or MDA or O2 rom, or a 1.60.x derivative?
Also, you could try this....
http://forum.xda-developers.com/viewtopic.php?t=7384&highlight=
This is a link to the ORIGINAL ROM 1.03.00, but this DOES NOT work for me, but it did get as far as erasing the Radio Stack, (maybe if it can erase yours the other updates will be able to continue)....
Upgrade fails during radio upgrade
I had this same problem when I was upgrading my O2 Rom. Now, I have had just about every possible ROM on my system and have had to revert back to the original and before being able to install and upgrade a few of them.
Assuming you have done all of this, I did have success with a phased upgrade. The upgrade executable creates a folder in the temp directory. I moved this folder to my desktop and launched the upgrade program directly from my desktop but each time only putting one rom file in the directory. There are three (One for extender, OS, and Radio) By doing it one ROM at a time I was able to have success.
Just another idea.
Djm
I have only had my XdaII for a month, but last week it locked up and upon a soft reset it took 5 minutes to get past the O2 screen, then there was no responce to any screen taps, i decided to do a full reset, once rebooted still no response to screen taps, so i couldnt calibrate the screen or go any further, i connected the xda to activesync this still worked fine and was responding normally. I then decided to reload the rom from myxda.com, biggest mistake as it crashed halfway through now it just says Serial v1.06 or USB v1.06 if its in the cradle, now before i get bashed for just asking this question the same as a lot of other people have, i have spent the last 4 days go over this site trying anything that relates to getting any image back onto my xda, nothing has worked i have tried any nbf or nb1 image i can find on here with orginal or modified himaupgradeut.exe same response every time error 100: incorrect device type, i have tried any image i get can get onto an SD card, they either dont boot or wont allow upload, so my question is i have seen several people on here ask about bring v1.06 back from the dead but so far noone has had any instructions on how to this when a normal boot isnt possible.
I don't know if this is any help,but I had something similar.
I concluded that the rom on xda2 was newer than one being upgraded? with,so it says it won't work.I sent mine back to o2,but think that rom 172 or something, might be accepted.People say that you leave it 30 mins before it starts to upgrade.
There is a problem with bootloader v1.06 in that it will not allow 'downgrades'. It seems to have appeared on devices around the same time that ROM versions 1.72 appeared. I have read that it will allow installation of version 1.66 but nothing less than that (and that may apply only to T-Mobile). However, you should be able to install a version 1.72 ROM without to much problem.
My help
You can make the unit work again by downloading the rom version:
1. Ensure that the main battery has enough charge to make the unit in bootloading mode.
2. Execute the bootloading mode and connect the unit to the docking station(cradle), you will see the "Serial" in the upper portion of the screen will switch to "USB" this is an indication that there's a connection established between the pocket pc and your pc.
3. Then download the latest Rom version(1.72 is a better choice).
Thanks dcs and Juni
The 1.72 rom did get it going again .... but i still have no response on the screen so im guessing ill have to return it.
Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.
Thanks agian guys for your help
Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.[/quote]
talk to this person in here: :lol:
http://forum.xda-developers.com/viewtopic.php?t=12044
Hi,
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
Please help.
Thanks
If your device is still working ok as a PDA then hopefully it just screwed up the radio update of your device.
Try reflashing the Radio only
Look Here
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Post back with results
Regards
S.K
EDIT: Sorry only works on 1.04 bootloader only. Afraid your gonna have to wait for Pof to come up with a 1.06-1.04 workaround
Hi S.K,
Thanks for the info. I have now tried installing the HERM_1.20.31.10_type2_radio_fixed upgrade but unfortunately the radio upgarde crashes also. It all seams to go well, (after using MaUpgradeUt_noID.exe twice) the phone says "Upgrade Radio Stack Please wait" and the progress bar appears on the PC but then after 10 mins I get an ERROR 114: RADIO ROM UPDATE ERROR.
Do you think this might be becuase the last upgarde partly installed bootloader 1.06?
Any other suggestions - I'm desperate to get the hpone on M3100 working again.
Thanks
Read here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Please post USB monitor capture, otherwise can't help u.
Hi Pof,
Thanks for the offer, I will sort out the usb software on Monday. Are there specific actions that I should try, obvioosly I will usb monior everthing I do but I want to keep it to the point and not waist yr time trailing through huge log files.
Cheers
BTW - I have tried all options of recovery, such as attempting to install the latest radio and trying to install the new rom from an sd card, trying several roms and using imei unlocker - all without any joy.
I think the problem is that I have partially installed radio and bootloader 1.06 so I can't fix the problem.
Thanks again.
@wotthefok:
For me is faster to look at the usb log file, then I exactly know why the upgrade fails, otherwise I have to decode it from your feedback and I can't be really sure. Check the "upgrading problems" page on the wiki, if none of the steps there seems to fix your problem, post USB monitor log please.
Log Files as requested
Hi,
I have captured information using usb monitor and attached the zipped log files for your attention.
The first is called USB_monitor_log_Herm_120Radio_twice. This log details attempting to install the HERM_1.20.31.10_type2_radio_fixed upgrade, and running it twice - just in case.
The USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_twice.zip details attempting to install the RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship upgrade, simply using the standard ROMUpgradeUt.exe method. This generates the expected Vendor ID error.
My primary focus is to install the radio upgare or download my bootloader to 1.04. The PDA part of my m3100 does now freeze occasionally but at least functions whereas the phone is completely dead.
Thanks in advance.
Please attach capture in *ANSI TEXT FORMAT*, the .lgs file you zipped is totally unuseful
Edit -> Export and Save as type "ANSI Text files".
Also make sure you export in "COMPLETE" view, see the wiki for more details.
OK, Spot the novice.... I have now created a txt log file that captures activity of me running the 120 Radio upgarde - but only once this time. I still had to zip the file due to it's size. Hope this is OK.
I'll send the other logs within the next couple of hours. Please let me know if the output I have sent so far is acceptable?
Thanks
wotthefok said:
Please let me know if the output I have sent so far is acceptable?
Click to expand...
Click to collapse
No, it's a "basic" capture, you have to export a "complete" capture:
Start USBMonitor.
File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
In the upper part there are two tabs: basic and complete. Click on "Complete".
Right, Try again (duh!) OK, I've tried to keep the log files names as self-explanitory as possible... USB_monitor_log_Herm_120Radio_run1.zip is the r20 radio upgrade, 1st run and USB_monitor_log_Herm_120Radio_run2.zip the second run - without disconneting or resetting the device.
USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_ran_twice.zip is the Cingular upgrade run via the ROMUpgradeUt.exe, again run twice without disconneting the device.
Hope I got it right this time.....Please let me know if there is anything else I can do.
Thanks.
This time you got the captures right
- You're on bootloader 1.06: You don't have 'rtask' command, you won't be able to do any radio upgrade only.
- Your device is not CID unlocked (Security level=FF, unprivileged)
- The bad flash caused the CID area to corrupt (CID: Wait interpreter timeout)
- When flashing a full ROM you get a CID not allow (255) this is because your corrupted CID doesn't match the CID on the ROM.
The radio part is screwed, you could have fixed this if you where in bootloader 1.04 by flashing a full ROM, but as you are in 1.06 you can't because of CID checking. But you're lucky because the OS ROM is intact and you can boot the OS, you should be able to downgrade to bootloader 1.04 from OS and flash a full ROM after, which will hopefully fix your radio.
Just wait until a solution to downgrade bootloader is available (I'm working on it).
Hi,
As I suspected.... Suppose it's not all bad news though - just means that I have to be patient and use my communicator once more. Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
I have already got a IMEI-CHECK sim unlock from where I originally got the M3100 unlocked from Orange to work on o2. That said, I have run either unlocker 2 or 3 with the .unl that I know worked I now get
HTC HERMES v3c unlock
Starting communication.........
Checking device..............ERROR
The device you try to unlock is not supported.
Please contact your supplier site.
Device is rebooting
Press any key to quit this application.
I'm currently chatting to the guys at IMEI-CHECK re this problem.
Anything else I can do to assist you in anyway??
Cheers
wotthefok said:
Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
Click to expand...
Click to collapse
They have it (M3100v3cUnlock.exe), but it will not work on your device because your IMEI is corrupted and their unlocker will not be able to read it and to check/compare with the .unl key file.
Hi,
Just a quick update. The guys at MIGsofT LTD have VERY VERY generously said they'll have a look at the problem for me so my phone will be winging it's way to them today.
Thanks for your assistance and helping me be certain of the problem and to better understand the root cause.
Hope this information will prove useful to others.
Another quick update...
The guys at IMEI-CHECK (MIGsofT LTD) have rectified problems with my handset and managing to reinstall bootloader 1.04 in the process!!
They also turned my phone around in under three days and only charged me the cost of postage! I had previously been a customer of theirs but it was still a very generous and helpful offer and I would certainly pay for the service than have a duff handset - after all £250 + for a paperweight is rather excessive....
If you're experiencing a problem like mine why not get in touch with them and offer them money to have a look at your handset? No Guarantees but it seemed like my last chance, for a while anyway.
Praise to IMEI-CHECK for a brilliant service - they are King of the day !!
Hi all,
First of all I want to let you know that I did search the forum for a solution. In fact, I found a lot of workarounds but none of them actually worked.
Let me give some details about my problem: My Hermes was working fine. I was running the official WM6 ROM supplied by HTC, so no customized ROM here.
It was going fine until the WM frozed. Then I soft reset the device and after that I never got cellular signal again.
While booting the device I got the message: "no GSM".
First thing I tried was to flash a new radio ROM. In all the attempts the progress bar never moved from 0% and after a while I got the communication problem error.
Then I tried flashing a whole ROM. This time the progress bar stopped at 81%. Apparently in the first 81% it flashes the OS and in the last 19% it writes the radio. Anyway, I tried this a few times and never finished.
In fact, after every communication error message I got stuck in the bootloader screen.
The only thing that works is to flash a ROM WITHOUT the radio!!
Is there anything I can do to save my phone or am I condemned to use my Hermes as a phone-less pda?
I tried everything I found in the wiki/forums, but I couldn't find a working solution.
I suspect that the blocks of memory where the radio data reside got corrupted, could that be possible?
PLEASE HELP!
thanks in advance!
Chris
A similar thing happen to me several months ago. While on a call my phone froze and when I soft-reset it the dreaded 'No GSM' issue appeared. I tried flashing radios/full roms/etc, but nothing worked. I ended up sending my phone to the htc repair facility and they fixed it at no cost. (Other than not having a phone for ~10 days)
Thanks dang, but I don't have a HTC service center where I live (Argentina, LATAM)
I'm faithful that the people of this wonderful community will be able to help me.
Just for curiosity, where did you send your device? Is it in the US?
cheers
sounds like a hardware problem to me...
Hi, there! I found that a lot of us who have bricked our Hermes, don't have a responsive radio bootloader, so when they try to flash a full rom, the progress bar hangs to 13%, or 81%. This is because at that time the flasher is trying to enter the radio bootloader, but because it's corrupted, it hangs. Till today there is no known solution to this one. I'm far away from England where I bought my Hermes, so I'm not thinking to send it back for repair. I'm a programmer, so my knowledge may be usefull here. The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
How can I try that?
windshearx said:
The first thing I must know is if i can use the "lnb" command without being SuperCID. I mean if there is something like a Hard-SPL with an "lnb" command - (or renamed for security reasons). Maybe there is hope!
Click to expand...
Click to collapse
You can use 'lnb' in HardSPL without having a real SuperCID; however you will not be able to flash a radio with 'lnb' command. The radio chipset has its own bootloader, the and the SPL just acts as a pass-through sending the data directly to radio chipset through the s2410 UART.
I had one device with non-responsive htc_boot and tried all kinds of SPL patches to flash htc_boot again on radio, without success. The only known method to fix this is to take the BGA chip out with hot air and reflash it with special hardware, as it is not common to have this equipment at home, your only option is to send it somewhere to do it for you.
However, I don't want to discourage you to research on it, maybe you find something i didn't
I have a similar problem
I also have a NO GSM and corrupted CID but I can access KITL and use it with PB 5.0. and I followed this steps here but the phone doesnt boot completely. It stops just after the two boot screens on Black WM6 ending on a white screen and the debug window on PB after loading all sort of things begin showing these lines over and over:
@@@@@@ HUB state changes now @@@@@@
[HDC]HubStatusChangeThreadPN TRUE
[HDC]HubStatusChangeThreadPN FALSE
Is there any hope for me? I have the cingular 8525
thanks
Gents, do you think the solution presented in http://forum.xda-developers.com/showthread.php?t=280425 could help me?
Please advise.
thanks again
chriscec said:
Just for curiosity, where did you send your device? Is it in the US?
Click to expand...
Click to collapse
I sent it to the HTC service center in Texas, US.
I just got my replacement from ATT.. Had the same problem. Its a hardware problem.. I wouldnt waste anymore of your time.
first, i'm sorry for my english
I've the same problem with a V1605 (french SFR), i've tried every solution but flash radio doesn't work.
I can flash cooked os without any problem, but it's impossible to put official
It's only a pda now, it's better than a brick
My hernes use to be the same as you 'NoGSM'.I tried to install the official rom,but it 's not work at all.I called to service center ask this problem,so they said that it must be only changed the mainboard. That 's terrible!!!
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
otoro_315 said:
for ALL -that has NO GSM and stuck at OS boot,
please follow this link -
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
the link above help me to bring back my hermes alive (about four hours work).
Click to expand...
Click to collapse
That only works with phones with KITL...which I don't seem to have.
Sorry, how to config the phone with KITL and solve the no gsm problem.
No GSM but when sim inserted
Hi all, First sorry for my bad english.
I also have 2 bricked Tytn Hermes 200. Its not my personal ones Its my company's property, which pple were using this phones. So i'm facin with problem which many pple here having but with exception. both phones having no gsm error when sim inserted but without sim its fine. In other words , device info showing every info including IMEI when sim unavailable. And some times works with sim but after making few call and receiving phone hangs(not system) and goes off from network but anthena signal still showing few bars. I'm thinking maybe the radio hangs totally and goes off, and after soft restart NO GSM. I also tried many flashing upgrading those things nothing can really help me.
When im flashing original rom from HTC (the latest one HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108) its hanging on 12% and doing 3 or 4 times recovery , but its finishes succesfully. So what exactly happening in 12th%?. Maybe its started flashing radio and stopped on bad block ? But then why its finishes succesfully after few retry?. Ok so if any one wants to experiments on the phones except radio welcome. I'll help. And some can give me quick example of how to check bad blocks?.
Tnx.
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
otoro_315 said:
@akarandomjames -
#1. have you try the comm button+reset button hold for 2-3 seconds
#2. OR try the comm button+OK button+reset button hold for 2-3 seconds
anyway, i'm not sure if KITL is dependend on the ROM version. because when my device was in NO GSM status, SPL is 1.04, HTC bootloader is 0108, and lost SuperCID. Because of my device is still has SPL 1.04, i was able to load WM5 full ROM upgrade using WWE HTC English QTEK_001 2.05.255.1 01/17/07 version (ROM available on this site under HERMES Upgrade link), run it twice. once you have successful load the WM5 ROM then try to do step #1 or #2 above to get KITL USB display on your screen device.
Note: i don't think KITL mode is not available once your device is in Production Mode. anyone here can verify this?
Click to expand...
Click to collapse
My device is still SuperCID and I know I don't have KITL...I have SPL 1.04 as well and HTC Bootloader is 0108. I can't install any ROMs with radios as they will hang at 11/12%. I will attempt this "overload" method where it seems some people have had luck with it...after a few recoveries it just finally installs...but I don't think that will be the case.
If I can't fix this in a few days, I will most likely use my warranty or just wait for the Kaiser.
My variation of No GSM
I feel like I have problem 1A...where I am able to boot into OS but no GSM.
I am still SuperCID, SPL 1.04, HTC Bootloader 0108. Last known radio before corruption was 1.48.00.00. ROM where this problem occured: VP3G 3.60.1.
I was not even in the middle of an upgrade...just a soft reset after my phone ALREADY lost GSM capabilities during a tether session. It was stuck with no signal in Phone Mode...I put it in Flight Mode...then tried to move it back to Phone Mode and it wouldn't do so. I soft reset...and the no GSM stuck.
I tried to reinstall radio...many errors...stuck on bootloader. At first, OS's only were not installing as well but I got past that. Now I am able to boot into OS's with limited capabilities...and they will NOT ACTIVESYNC at all. Regardless of how old or new the ROM is. I tried older OS's that I knew worked in the past for me...but they refused to activesync.
Due to that, I am not able to install latest HardSPL 2.10Oli via SSPL. That seems to be the only way to do it according to my knowledge and what I've read. Maybe mtty was capable but I'm not sure. HardSPL 1.40Oli wasn't giving me any problems though, but I just wanted to have the latest one so I can avoid IPL damage.
I can only install anything if I start the device in bootloader...and I'm only limited to the OS since my Radio Bootloader seems corrupted.
I'm not sure what caused the corruption in the first place...but I feel annoying now posting on different parts of the forum with a problem that seems to be growing in the community.
I made an attempt to what I thought was an upgrade to my x7501, i have wm6 i wamt 6.1. I ran the unlocker oilpro and the phone seemed fine, then I rebooted the device. I never noticed any thing other than a program that installed on the phone. The oilpro never completed. Now I can not start the device. it seems like i have no power. I have $300 to the person who can fix it this week. I live in washington dc and I need this phone fixed. my email is [email protected] no bull ****ters please, I dont have time. there is no 3 color bars etc...
Hi,
After using athena_unlocker, my X7500 also ran black after reboot without any loading screen, but since the x7501 is now supported by athena_unlocker (I presume you've downloaded the latest version at XDA), it should be possible to re-update a x7501 ROM.
You should at first try to download the original HTC x7501 ROM and re-update your device:
http://download.america.htc.com/RUU_Athena_HTC_US_2.19.453.4_105_1.47.51.00_Ship.exe
or one of those ROMs at xda (which are for x7500, though)
http://forum.xda-developers.com/showthread.php?t=314672 ; reply#4, I used T-MOB005 - version with spl,ipl and etc
- press power on button on the x7501 for at least 3 secs even if you can't see a thing
- connect x7501 with USB and make sure that ActiveSync is running (of course, it won't connect!)
- start ROMUpdateUtility.exe from the downloaded ROM-version (you must have administrator rights)
In case the ROMupdateutility doesn't find the x7501 (connection error, still black scren), try the following:
- press the camera button on the right, hold it and press reset button for some time - the boot loader screen (Olinex v1.20 in your case) should appear, then you can proceed with the original ROM re-update.
- accept all warnings and update, with me, it did connect and updated the ROM since the SPL had already been installed by the unlocker before (just no ROM => black screen)
Afterwards, my device at least started again so I could finish the unlocking process, it finally worked.
I can only tell that it worked for me 2 times, first original ROM => Olinex SPL1.2 => Athena AP4.0/Olinex SPL3.5, in both cases the same black screen occured (however, the bootloader is already installed on the device, so an update will work). It seems that the boot loader has some problems to upload the ROM itself, so only the new boot-loader version is on the device, you have to upload the ROM separately...just give it a try.
Regards,
Will_990
hgreen70 said:
I made an attempt to what I thought was an upgrade to my x7501, i have wm6 i wamt 6.1. I ran the unlocker oilpro and the phone seemed fine, then I rebooted the device. I never noticed any thing other than a program that installed on the phone. The oilpro never completed. Now I can not start the device. it seems like i have no power. I have $300 to the person who can fix it this week. I live in washington dc and I need this phone fixed. my email is [email protected] no bull ****ters please, I dont have time. there is no 3 color bars etc...
Click to expand...
Click to collapse
Remove sim and SD card
Remove battery for few mins then replace battery(sometimes it doesn't seat properly)
Plug in the mains charger and see if the charging light comes on.
If so try to boot into bootloader.
If you see the tricolor screen, connect to the computers usb port and run the original rom from the links above.
Good luck