Related
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.
I was trying to upgrade to radio v1.43 in the hope that battery life was improved over 1.41 however when it got to 8% it stopped and gave me an error i can't remember After atempting to recover, it got off the three colour screen now the 3100 stalls on the blackshadow version4 screen (bootloader screen?) and goes no further. I tried reflashing but got a 260 and using mtty, only getting 2 com port options, didn't offer any help.
I'm really sorry to have not been able to sort this with reading through the relevant post but I haven't found a solution. What else can I try?
Hi,
Could you pls advise what is your device made, model, SPL version ... etc.
Also did you try to do Hard reset?
I'm using now black MAJIK (and few days ago black shadow) with radio 1.43 with no problem.
its the SPV m3100 When I decided to go Black shadow I read up on mr vanx and made sure I had all the things I needed. If I remember right, when I came to upgrade to Majik the auto detect found the second option down
SPL-1.04/1.10 - 1.09 Bootloader. I've realized since I had a spaz and ran the RUU from the archive this time. From what I've since read thats not too cleaver.
I have tried a hard reset and took the battery out instead of pressing space.
I dont know if this information on the starter screen is of use
M 05
S 04
B 05 D 3lak
I'm not sure, but hard reset doesnt mean you take the batery out.
Please check that link:
http://wiki.xda-developers.com/index.php?pagename=Hermes_For_Beginners#hardreset
I was in your position (hanged on booting) few days ago, and when i did hard reset, it changes every thing to basic normal condition.
i meant when i did a hard reset when it asked me to press space to reboot I took the battery out. I tried again this time pressing space to reboot but I still get stuck on the loading screen. I can't connect by USB to the PC I'm guessing the drivers on the phone haven't loaded and I'm stuck as to what to do.
Does anyone have any ideas?
try look at it http://forum.xda-developers.com/showthread.php?t=286755
ok I've tried everything I can think of to connect the 3100 to the computer so I can reflash it but mtty gives only com 1 and com2 but no USB and neither those two work, active sync wont connect so I disabled it as suggested and running the radio ruu and wrapper wont querry the device. I am now at a loss as to what to do next someone must know what I should do. Please?
what is your SPL?
try this http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
sl is 1.09 i'd updated it on the previously successful black shadow flash
msn [email protected]
icq 150277111
AIM TazmanFH9
Yahoo bigfathairyboggart
I have tried changing KITL trasport but I am unable to select or chose either option. I have also tried the rversion command in the tri colour screen but nothing happens. I hope I'm missing something nice and simple but I get the feeling I'm not going to be that lucky. Please help
tcSPVm3100 said:
sl is 1.09 i'd updated it on the previously successful black shadow flash
Click to expand...
Click to collapse
I suggest you check again, press and hold the side OK button and the power button...then put the stylus into the hole in the bottom of the unit.
yeah I've done that it's "SPL-1.09"
I had this exact problem yesterday, with the same bootloader too. The phone would not pass the splash and IT refused to upgrade. I ended up downgrading to a shipped wm5 rom (in my case the cingular 1.30.502.1_1.11.00.00) which to my surprise actually worked as no rom radio or spl upgrade moved at al on my phone. Then upgraded back to black majik. I hope this helps.
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
tcSPVm3100 said:
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
Click to expand...
Click to collapse
Just download a WM5 ROM from the wiki page!
ok tried this too no luck.
Trying to use the one from orange (linked to through wikki) I get an 294 invalid vendor error however active sync cannot connect yet of course so is this to be expected?
I have however gotten a connection with mtty which is a step forward dunno what to do with it yet though except trying the password 0000000000000000 command but it not disabling the password. This then lead me to read for a further hour how to change it and I've got to be honest; it beat me. I have No idea what the hell its talking about. My head hurt with so much reading.
I get a no gsm pop up v briefly on loader. I so want my phone back
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
tcSPVm3100 said:
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
Click to expand...
Click to collapse
can u flashing HARD V7?,i think better u have IPL 1.04 SPL 2.10olipro first ,then try to flashing radio?
and did u try SD card.
In bootloader can anyone here connect with active sync? I can't so updating rom and radio flashes in the usual way isn't possible. Trying the hard spl again it tells me to make sure active sync is connected and as it isn't it throws back a 262 update error. 0% on the hermes and that's currently as far as I can get. I have no means with which to access the memory card.
The reason you get an invalid vendor ID is because your CID doesnt match....download a ROM which is for your device (an orange one?)...then try.
You need to read the wiki alot more before trying anything else since you are not aware of the vendor ID error...nor the fact you MUST use HardSPL.
I linked to the orange ROM from wikki and tried installing it. it was while installing THIS ROM SPV_M3100_ROMUpdate_0407.exe I got invalid vendor error.
Installing a recent DL on HARD spl v7 I get a 240 open file error that's one I haven't had before.
With all other attempts they all say they want an active sync connection.
I can not connect to the phone through active sync
so all attempts by me to flash anything to the phone using an RUU fails.
Please help me. I recently upgraded to the Black satin rom and everything was fine. However the touchscreen on my M3100 has started to go haywire.
After being on for about 5 minutes the touchscreen doesn't work. It seems like the top right hand corner is faulty as the close button keeps being pressed again and again. I think it is probably the phone that is faulty rather than the ROM.
Anyway I need to revert back to the original Orange ROM (WM5) so I can send it back to orange. I've only had the phone about 3 weeks so its still under warranty.
I tried to load the ROM off the orange business website but it errors when trying to load the rom on. I assume I need to downgrade the bootloader thingy.
Any help much appreciated!
www.mrvanx.org
Look for "downgrade guides"
I'm in a similar boat mdavix!
I've just tried flashing an original T-Mobile WM5 ROM using MrVanx's guide but it doesn't progress beyond the bootloader page. Instead the update times-out and gives Error 260 - "Cannot connect to PDA"
Getting late (that's when Bad Mistakes Happen lol!) so will come back to it at the w/e I hope. Let us know if you have any luck!
sim
--
T-Mobile MDA Vario II / schaps 3.57a / Radio 1.41 / HardSPL
interestingly, I put black satin on my new M3100, and the screen started going. So I put it back to the latest Orange release (from the website) 2.11.61.1, but it was still screwy. Sent it back to Orange, and got a different recodnitioned phone back. They said the ROM was the issue, and the one they gave me had 2.11.61.3 on it. This version is not available for download... has anyone else seen it?
Do orange know what is happening to the screens? Is something getting burnt out? does 2.11.61.3 have a fix?
Well... I'm too scared to put WM6 back on, now, although I really want to. I at least want to wait till I can get hold of the update for 2.11.61.3, and even then, I'm not sure.
I have looked at the downgrade guide but don't really fancy the re-compiling the nbh business.
The strange thing is that if I take the battery out for a couple of minutes, then replace and boot up, the screen works for a while!
Is it worth trying a different rom?
mdavix said:
Is it worth trying a different rom?
Click to expand...
Click to collapse
No, it's a hardware problem, I assure you.
Ok, thanks vp3G.
So I still need to get back to WM5.
I'll have to give mrvanx's downgrade guide a go!
Is this still current? Is this the correct one to try?
I carried out the steps in the downgrade guide and attempted to flash the resultant rom onto my M3100. It started to update got to 1% and failed with a transfer error!
Now when I turn the phone on it just comes up with the three colour screen!
Have a broke it forever? The screen reads:
HERM100
IPL-1.01
HERM100
SPL-2.10.Olipro
Please help!
Phew! Panic over, I've managed to get the Black Satin rom back onto my phone.
I'm stuck at the screen alignment screen again but at least its got an OS on now!
I still need to load WM5 on tho. I think I'll try re-doing the downgrade guide and see if that helps.
I'm looking at duttys nbh tool and notice that the device id is HERM200. My phone is an M3100 so a HERM100. I'm going to change the value to be HERM 100 and re-compile. Hopefully that was the problem last time!
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.
Hi guys. Mass apologies for my stupidity, but here goes...
I have now spent over 2 days on this site reading all that I can, but I am at a loss and desperate for your expertise!
I am running a UK Tmobile Vario 2. I was having problems with the phone crashing constantly and not getting any signal at all so I installed WM6 yesterday hoping this would help. Its not crashing as much, but its still not getting any signal.
After reading loads of threads and posts all over the place (I have read enough WIKI to make my eyes bleed), I think I need to update the radio version. This is the information I can gather from my phone:
Bootloader info-
Herm300
IPL-1.04
SPL-2.03
I cant figure out how to enter commands in bootloader to gather any more info I tried the mtty.exe thing with no avail. When I go to "device information" it reads like this:
ROM version: 3.60.110.4
ROM date: 09/05/07
Radio version: SAYS NOTHING!!!!
Protocol version: SAYS NOTHING!!
IMEI: SAYS NOTHING!!
When I do a soft reset I get red letters and numbers appearing and not the "no gsm" message.
This is a 2nd hand phone off of ebay as my original phone was stolen. I have contacted Tmobile, but they refuse to help me as its not the original phone that I bought.
I would be most grateful for any help you can give me!!
Thanks,
April
OK, firstly.....flash hardspl.........instructions here
Next flash ANY radio......try version 1.48.00.10.
with the device booted up and synched with Activesync, download the radio ROM, unzip and run the RUUprogram (the only exe in the zip).
select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box.
go through each screen and accept everything......the radio will be flashed.
Hopefully your device will work properly after this.
uh oh...
Thanks so much for your speedy response. Obviously I managed to screw this up.
got to this stage
"select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box."
It didnt autodetect, so selected SPL v2.10 and ticked "HardSPL" box manually. Went through all the other bits and when it starts to do its thing it just sits at 0% then i get error message "ERROR 262: UPDATE ERROR. The rom update utility has encountered communication errors during the update process. THe program will guide you step by step to recover from the errors so you can continue with the update."
So I followed the recovery process instructions several times. Nothing has worked. Have tried restarting my computer and doing a hard reset on phone, and stuck with the bootloader screen reading IPL 1.04 and HERM300 SPL-2.10.01Olipro.
Manage to get back to this stage
"select autodetect, it should highlite SPL v2.10 and tick the "HardSPL?" box."
and go through the ticks but always ends up with error message 262.
SORRY!
Sorry to hear about your problems.
Was it the official T-Mobile WM6 ?
If so it was another 1.50 Radio!
I have same now!
http://forum.xda-developers.com/showthread.php?t=357275
I read in another thread try putting phone in fridge for 15mins first without the battery.
Good Luck
fridge vs. floor
Yes, it was the official WM6 from T-Mobile.
Im worried now that my limited experience with flashing, cooking, and now crying will leave me with a proper "brick".
I will try the fridge thing, if I ever get it to loads WM6 again but for the mean time, I will continue to throw it on the floor.
What do you mean by it was another 1.50 radio? I dont know what version I once had, but as suggested by mrvanx, I was trying to upload the 1.48.00.01.
Again apologies for my complete ignorance, but Im sure there are others that share my stupidity and will benefit from me asking goofy questions. If anyone else has any more simpleton advice on how to revive my poor phone, I would be much obliged!
Thanks,
April
The 1.50 radio bit; If it was the official T-Mobile WM6 upgrade, then your radio will have been 1.50 (I am pretty sure)
I dont know what else to do!!??
Ok since trying to update my radio from nothing to 1.48.00.01 and receiving error message 262 during the update, my phone now only goes into bootloader mode reading the following:
HERM300
IPL-1.04
SPL-2.10.0lipro
I have tried the following to bring it back to life (but not in any particular order):
- restarted my pc several times
- made sure my Windows XP SP2 was up to date
- made sure I had .net framework up to date
- hard reset on phone
- soft reset on phone
- leaving battery out overnight
- updating SPL to 2.10.0lipro (again) doesnt get to any percentage, just straight to error 260
- updating radio to 1.48.00.01 (again) - wont autodetect. tried radio button SPL2.10, then just force safe, then just HardSPL. each option dies at 0% then error message 262)
- reinstalling TMobile version WM6 (again) - dies at 11% - error message 262
I saw the post by pof "How to unbrick your bricked hermes" and the solution was to "Flash any radio in NBH format", but I cant figure out how to do that!? (I have tried clicking on the nbh file in the downloaded radio folder, but dont know what program to use to unload all the info. Have also looked at all the links on "Radio sudden death issue knowledge consolidation" and nothing has helped.
Sorry again guys, but can someone please help
If not, does anyone want to buy my brick?
alachlan said:
Sorry again guys, but can someone please help
If not, does anyone want to buy my brick?
Click to expand...
Click to collapse
Dude - there are enough bricks around these parts to build a 500 story repair centre! All we need is MS to merge their NT, CE and ME technologies into CEMENT then we can hold all the bricks together
Error 260 (comms error) is usually caused by using Vista without "fixing" it or Win2K/XP without the .net framework on it
Error 262 is USB port not available - turning hermes off and on (or removing the battery if that fails) at that point and putting it manually into bootloader usually cures that one then continuing with the flash.
Incorrect.
Its more than likely this Vario II was irepairably bricked before the TC bought it, the Radio upgrade is failing on a Tmobile official ROM (which includes a radio) and on a standard CustomRUU upgrade for the radio only.
A "checkimage" command in mtty would probabaly return a failed radio checksum and following on from that the mtty commands to get into the radio bootloader will fail (rtask a......then rversion).
Also there may be a corrupted CID on the device which again isnt good.
Ive seen these types of bricks MANY times.
Sorry dude, looks like your Hermes was a paperweight when you bought it.
Never thought of that - shameful given the amount of radio investigating I've done recently Too busy on 260's with part flashes from people not installing .net (also the amount of hits you should be getting to your vista guide now is scary!)
Still say we should collect up all the bricks and build a repair centre
Mikeapollo said:
.....the amount of hits you should be getting to your vista guide now is scary!....
Click to expand...
Click to collapse
73039 hits according to the site
Pretty much the only fatal brick now is a damaged radio/CID flash. If there was a way for Olipro/Pof/Us to flash a hardspl type package in place of the radio bootloader then it would be solid.
What type of mortar should we use?
mrvanx said:
73039 hits according to the site
Pretty much the only fatal brick now is a damaged radio/CID flash. If there was a way for Olipro/Pof/Us to flash a hardspl type package in place of the radio bootloader then it would be solid.
Click to expand...
Click to collapse
Yup.. Must admit I think that's the one thing that will not happen anytime soon as the interactions between bootloader, radio bootloader and the radio PLA/PIC is a tad complex... It'll be a very difficult thing to test and even finding a suitable vunerability is difficult - certainly beyond my abilities presently. Though the same was said 12 months ago about the No-Wifi issue and Olipro led some excellent progress in that area...
Mind you - the key to fixing CID/radio bricks is to educate the masses not to make them in the first place and not to just blindly execute whatever they stumble across - more of a challenge than rewriting the bootloader by hand on paper tape and almost as frustrating
Oh... as for Mortar... we could have a mass scrape of all that weird dirt stuff that "grows" under the "invisible-until-you-open-it" edges of the screens and around the battery cover and add a drop of water
Wonder if it's the electronic equivelent of belly button fluff?
does that mean its dead?
Thanks for all the entertaining posts guys. Just to clarify things, Im running XP SP2, and the phone did actually work for about 3 months until suddenly one day it gradually started dropping signal, until the signal vanished completely.
Are you guys trying to tell me that my phone is completely dead then? Could I have prevented this by knowing what the hell I was doing or was it a fault of the phone?
With regards to the mortar issue I think a combination of tears and sh*t would do. I think I would build a big wall around the jackasses who release products that arent completely stable but still charge us an arm and a leg for them. (excuse my grumpiness)
Oh and just wanted to say that since my vario has been out of action, I have been relying on the trustiest brick Ive ever owned, my XDA IIs. This thing has been dropped so many times and is held together with super glue, but it does the job and gets on with things, just not very quickly.
Thanks again for all the help.
alachlan said:
Thanks for all the entertaining posts guys. Just to clarify things, Im running XP SP2, and the phone did actually work for about 3 months until suddenly one day it gradually started dropping signal, until the signal vanished completely.
Are you guys trying to tell me that my phone is completely dead then? Could I have prevented this by knowing what the hell I was doing or was it a fault of the phone?
With regards to the mortar issue I think a combination of tears and sh*t would do. I think I would build a big wall around the jackasses who release products that arent completely stable but still charge us an arm and a leg for them. (excuse my grumpiness)
Oh and just wanted to say that since my vario has been out of action, I have been relying on the trustiest brick Ive ever owned, my XDA IIs. This thing has been dropped so many times and is held together with super glue, but it does the job and gets on with things, just not very quickly.
Thanks again for all the help.
Click to expand...
Click to collapse
By the sounds of it you might have a permenant brick but unless i had your device here and actually went through everything myself i cant be sure. take a read through the sticky thread above this one about unbricking......it will take some time to read through but you will see what techniques are used to try and revive the device.
when cid corruped with spl 2.03 and not have gsm no solution can not flash with sd card when you see that level=fff only when level=0 in mtty console can use sd card for flashing rom.
THIS TIME ONLY SOLUTION TO UNBRICK HERMES WITH SPL 2.03 NO CID AND IMEI -
SENT Imei-check to fix this ??
?
uuuummm....
Thanks mbsshop1302gsm for the response, but did I mention that I have limited knowledge on this stuff? So the more basic the instructions are, the better.
Thanks,
April